[Bugme-new] [Bug 11386] New: p54 always causes BUG under high traffic in interrupt handler

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=11386

           Summary: p54 always causes BUG under high traffic in interrupt
                    handler
           Product: Drivers
           Version: 2.5
     KernelVersion: 2.6.27-rc3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: network-wireless
        AssignedTo: drivers_network-wireless at kernel-bugs.osdl.org
        ReportedBy: sean at mess.org


Latest working kernel version: never (although prism54 driver does work)
Earliest failing kernel version: 2.6.26 (have not tested earlier versions)
Distribution: Ubuntu (but mainline kernel)
Hardware Environment:

AMD Elan (http://www.embeddedarm.com/products/board-detail.php?product=TS-5500)

sean at tiger:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] ELanSC520 Microcontroller
00:0b.0 USB Controller: OPTi Inc. 82C861 (rev 10)
00:0c.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
00:0d.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compat)
01:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism
Duette)
sean at tiger:~$ lspci -n
00:00.0 0600: 1022:3000
00:0b.0 0c03: 1045:c861 (rev 10)
00:0c.0 0607: 104c:ac56
00:0d.0 0200: 1282:9102 (rev 40)
01:00.0 0280: 1260:3890 (rev 01)

Software Environment:

dmesg:
p54: LM86 firmware
p54: FW rev 2.7.0.0 - Softmac protocol 4.1
p54: unknown eeprom code : 0x1
p54: unknown eeprom code : 0x1007
p54: unknown eeprom code : 0x1008
p54: unknown eeprom code : 0x1100
p54: unknown eeprom code : 0x3
p54: unknown eeprom code : 0x1905
phy0: Selected rate control algorithm 'pid'
phy0: hwaddr 00:04:e2:aa:48:d2, isl3890
firmware: requesting isl3886

Problem Description:
Under high traffic, e.g. ftp a large file, after about 10 to 50MB, a BUG
occurs. Also tried 2.6.25 and 2.6.26 but those fail too in the interrupt
handler.

CONFIG_PRISM54 does work however. 

Steps to reproduce:
Just done a git-pull.

BUG: unable to handle kernel NULL pointer dereference at 00000088
IP: [<c01ccf4c>] skb_put+0x4/0x2e
Oops: 0000 [#1]

Pid: 836, comm: ftp Not tainted (2.6.27-rc3-00632-g1bbe44f #1)
EIP: 0060:[<c01ccf4c>] EFLAGS: 00010202 CPU: 0
EIP is at skb_put+0x4/0x2e
EAX: 00000000 EBX: 00000000 ECX: 80000012 EDX: 00000622
ESI: 00000003 EDI: c1c0ace0 EBP: c1c9d044 ESP: c0883a68
 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process ftp (pid: 836, ti=c0882000 task=c1c3f440 task.ti=c0882000)
Stack: 00000000 00000003 c01aa419 c1c0a180 c1c9d000 c103e4c0 c1f26aa4 00000011
       00000004 00000002 c1c13c60 00000000 00000000 0000000a c01245d1 c0277aa4
       0000000a c0883adc 00000230 c0125569 00000000 0000000a c0104027 c0277aa4
Call Trace:
 [<c01aa419>] p54p_interrupt+0x129/0x1de
 [<c01245d1>] handle_IRQ_event+0x1a/0x3f
 [<c0125569>] handle_level_irq+0x7a/0x8d
 [<c0104027>] do_IRQ+0x4e/0x64
 [<c0102c03>] common_interrupt+0x23/0x30
 [<c0163c8e>] ext3_test_allocatable+0x20/0x2d
 [<c0163e88>] ext3_try_to_allocate+0x9d/0x227
 [<c016474c>] ext3_try_to_allocate_with_rsv+0x2c0/0x38b
 [<c01649e8>] ext3_new_blocks+0x1d1/0x4c3
 [<c015269b>] __bread+0x6/0x67
 [<c01672ba>] ext3_get_blocks_handle+0x34b/0x790
 [<c0129794>] __rmqueue+0x14/0x196
 [<c0167890>] ext3_get_block+0x83/0xb6
 [<c01518d5>] __block_prepare_write+0xe1/0x2a4
 [<c0151b2a>] block_write_begin+0x71/0xcc
 [<c016780d>] ext3_get_block+0x0/0xb6
 [<c0168a28>] ext3_write_begin+0xc1/0x161
 [<c016780d>] ext3_get_block+0x0/0xb6
 [<c012721b>] generic_file_buffered_write+0xec/0x55e
 [<c0126489>] file_remove_suid+0x18/0x47
 [<c0127c79>] __generic_file_aio_write_nolock+0x401/0x452
 [<c0102c03>] common_interrupt+0x23/0x30
 [<c01c85ca>] sock_aio_read+0xb8/0xc2
 [<c0127d03>] generic_file_aio_write+0x39/0x8d
 [<c01656f9>] ext3_file_write+0x19/0x84
 [<c0138c02>] do_sync_write+0xbd/0x104
 [<c012b2b1>] wb_timer_fn+0xc/0x27
 [<c0113f5c>] run_timer_softirq+0xf3/0x133
 [<c011a959>] autoremove_wake_function+0x0/0x2b
 [<c01aa496>] p54p_interrupt+0x1a6/0x1de
 [<c0138b45>] do_sync_write+0x0/0x104
 [<c01392dc>] vfs_write+0x7f/0xec
 [<c013965f>] sys_write+0x3c/0x63
 [<c01029e2>] syscall_call+0x7/0xb
 =======================
Code: 00 00 00 01 50 50 8b 80 94 00 00 00 3b 83 90 00 00 00 73 0b 8b 4c 24 04 8
EIP: [<c01ccf4c>] skb_put+0x4/0x2e SS:ESP 0068:c0883a68
Kernel panic - not syncing: Fatal exception in interrupt


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.