[Prism54-devel] [Bug 82] New: Kernel oops under continuous medium high load
bugzilla-daemon@mcgrof.com
bugzilla-daemon@mcgrof.com
Sun, 2 May 2004 06:17:55 +0000 (UTC)
http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=82
Summary: Kernel oops under continuous medium high load
Product: prim54
Version: 1.0.2.2
Platform: ia32
OS/Version: Linux 2.6
Status: NEW
Severity: major
Priority: P2
Component: Device Driver
AssignedTo: prism54-devel@prism54.org
ReportedBy: janl@langfeldt.net
Hi,
System:
- 2.8GHz P4, HT disabled, 1G memory
- 2.6.5 kernel with stock prism54 driver
- SMC2802W EU prism54 PCI card, bought last fall. Running in a ad-hoc B net.
The other cards are Orinocos and a Airport card.
My machine can be reliably be brought down within 24 hours. What I have to do
is to take part in some bittorrents and otherwise go about my business. I have
1Mbps incomming so the load is not all that high. The first few hours
everything is fine. Then I start seeing packet loss. This packet-loss is
reduced when I move the laptop closer to the machine. It helps to bring the
machine down if I try to use rsync to load some files of this machine onto my
laptop. Rsync seems to stress systems quite thorougly.
This is iwconfig for the card:
root@roke /home/janl # iwconfig eth1
eth1 IEEE 802.11b/g ESSID:"LangfeldtWLLan"
Mode:Ad-Hoc Channel:1 Cell: 86:FF:3D:F4:2C:E8
Bit Rate:11Mb/s Tx-Power=31 dBm Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Link Quality:207/0 Signal level:-67 dBm Noise level:-239 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
I've had several crashes, but this is the first time I've been able to catch the
oops (turned off the screen saver on the console and used digi-cam to take a
picture). Ksymoops says:
Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
EFLAGS: 00010292 (2.6.5-UP-nfb)
eax: 0000002e ebx: f77ba800 ecx: c02edcd0 edx: 00000296
esi: c02bd515 edi: f77baa20 epb: 00000002 esp: c035df20
Warning (Oops_set_regs): garbage 'epb: 00000002 esp: c035df20' at end of
register line ignored
ds: 007b es: 007b ss: 0068
Stack: c02d8920 f89a967f 00000a14 00000511 f77ba800 00000511 c1c66480 f89a9684
f89b0538 00000000 f7740000 f77ba800 f77ba800 00000002 f77baa20 c035dfac
f89ad57f c035df60 00000000 f786fb20 04000001 00000000 c01080da 0000000c
Call Trace:
[<f89a967f>] islpci_eth_receive+0x2b6/0x2cd [prism54]
[<f89a9684>] islpci_eth_receive+0x2bb/0x2cd [prism54]
[<f89ad57f>] islpci_interrupt+0x17f/0x226 [prism52]
[<c01080da>] handle_IRQ_event+0x2f/0x55
[<c01083db>] do_IRQ+0x86/0x122
[<c0106c48>] common_interrupt+0x18/0x20
[<c0104a6d>] default_idle+0x23/0x26
[<c0104acb>] cpu_idle+0x2c/0x35
[<c035e674>] start_kernel+0x14b/0x165
[<c035e3fb>] unknown_bootoption+0x0/0x10b
Code: 0f 0b 58 00 b2 71 2d c0 8b 5c 24 14 8b 74 24 18 83 c4 1c c3
Using defaults from ksymoops -t elf32-i386 -a i386
>>ebx; f77ba800 <pg0+373ad800/3fbf1000>
>>ecx; c02edcd0 <fmt.1+720e/33592>
>>esi; c02bd515 <ip_mc_join_group+2a/1b2>
>>edi; f77baa20 <pg0+373ada20/3fbf1000>
Trace; f89a967f <pg0+3859c67f/3fbf1000>
Trace; f89a9684 <pg0+3859c684/3fbf1000>
Trace; f89ad57f <pg0+385a057f/3fbf1000>
Trace; c01080da <do_bounds+5f/8d>
Trace; c01083db <do_alignment_check+45/aa>
Trace; c0106c48 <resume_userspace+14/18>
Trace; c0104a6d <gunzip+4e7/4fa>
Trace; c0104acb <poll_idle+5/33>
Trace; c035e674 <pci_bus_type+34/100>
Trace; c035e3fb <pci_class_numbers+bb/c0>
Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 0f 0b ud2a
Code; 00000002 Before first symbol
2: 58 pop %eax
Code; 00000003 Before first symbol
3: 00 b2 71 2d c0 8b add %dh,0x8bc02d71(%edx)
Code; 00000009 Before first symbol
9: 5c pop %esp
Code; 0000000a Before first symbol
a: 24 14 and $0x14,%al
Code; 0000000c Before first symbol
c: 8b 74 24 18 mov 0x18(%esp,1),%esi
Code; 00000010 Before first symbol
10: 83 c4 1c add $0x1c,%esp
Code; 00000013 Before first symbol
13: c3 ret
<0>Kernel panic: Fatal exception in interrupt
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.