OOPS on startup

Jody Goldberg <[email protected]>
Newsgroups gmane.linux.drivers.atmel-wlan
Message-ID <[email protected]>
I've been trying the snapshots regularly for a while now under
2.4.20.  Things have gotten marginally better recently, only the
keyboard locks up now.  Strangely the atmel driver did actually
mostly work a few months ago until I tried the berlios driver.  Now
both are unhappy.

Today I tried a nice fresh 2.4.21 + 0.11beta3 (July 12 snapshot)
with no appreciable change.

Any insight on the attached oops ?
It corresponds to manually loading the rfmd drivers via modprobe and
plugging a netgear 101b into the usb slot of a sony vaio sr7 laptop.
The config is pretty vanilla, I've tried various combinations of
debug enabled/disabled with varying levels of lockup.
oops.txt (text/plain, 3.3 KB)
ksymoops 2.4.8 on i686 2.4.21.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.21/ (default)
     -m /boot/System.map-2.4.21 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Jul 12 15:07:14 laptop kernel: Unable to handle kernel paging request at virtual address 0060002b
Jul 12 15:07:14 laptop kernel: cc84615c
Jul 12 15:07:14 laptop kernel: *pde = 00000000
Jul 12 15:07:14 laptop kernel: Oops: 0000
Jul 12 15:07:14 laptop kernel: CPU:    0
Jul 12 15:07:14 laptop kernel: EIP:    0010:[<cc84615c>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Jul 12 15:07:14 laptop kernel: EFLAGS: 00013206
Jul 12 15:07:14 laptop kernel: eax: 0060000f   ebx: 00000000   ecx: c123be9c   edx: cba59d40
Jul 12 15:07:14 laptop kernel: esi: 000001f4   edi: c123a000   ebp: c123be84   esp: c123be5c
Jul 12 15:07:14 laptop kernel: ds: 0018   es: 0018   ss: 0018
Jul 12 15:07:14 laptop kernel: Process keventd (pid: 2, stackpage=c123b000)
Jul 12 15:07:14 laptop kernel: Stack: 000001f4 cc84625a cba59d40 00000001 00000000 00000000 c123a000 00000000 
Jul 12 15:07:14 laptop kernel:        00000000 00000023 c123be9c c123be9c 00000000 00000000 00000000 c123a000 
Jul 12 15:07:14 laptop kernel:        c123be84 c123be84 00000000 c87455c0 00000005 c9dd2a00 cc8463c3 cba59d40 
Jul 12 15:07:14 laptop kernel: Call Trace:    [<cc84625a>] [<cc8463c3>] [<cc84646b>] [<cc853bc0>] [<cc847281>]
Jul 12 15:07:14 laptop kernel:   [<cc84a4b5>] [<cc88b75c>] [schedule+524/848] [__run_task_queue+90/112] [context_thread+307/448] [context_thread+0/448]
Jul 12 15:07:14 laptop kernel: Code: 8b 40 1c 85 c0 75 14 8d b6 00 00 00 00 8d bc 27 00 00 00 00 


>>EIP; cc84615c <[usbcore]usb_submit_urb+1c/40>   <=====

>>ecx; c123be9c <_end+f154d8/c51669c>
>>edx; cba59d40 <_end+b73337c/c51669c>
>>edi; c123a000 <_end+f1363c/c51669c>
>>ebp; c123be84 <_end+f154c0/c51669c>
>>esp; c123be5c <_end+f15498/c51669c>

Trace; cc84625a <[usbcore]usb_start_wait_urb+7a/180>
Trace; cc8463c3 <[usbcore]usb_internal_control_msg+63/70>
Trace; cc84646b <[usbcore]usb_control_msg+9b/b0>
Trace; cc853bc0 <[usbcore]hub_event_lock+0/0>
Trace; cc847281 <[usbcore]usb_set_address+61/70>
Trace; cc84a4b5 <[usbcore]usb_reset_device+b5/350>
Trace; cc88b75c <[usbdfu]kevent+b0/148>

Code;  cc84615c <[usbcore]usb_submit_urb+1c/40>
00000000 <_EIP>:
Code;  cc84615c <[usbcore]usb_submit_urb+1c/40>   <=====
   0:   8b 40 1c                  mov    0x1c(%eax),%eax   <=====
Code;  cc84615f <[usbcore]usb_submit_urb+1f/40>
   3:   85 c0                     test   %eax,%eax
Code;  cc846161 <[usbcore]usb_submit_urb+21/40>
   5:   75 14                     jne    1b <_EIP+0x1b>
Code;  cc846163 <[usbcore]usb_submit_urb+23/40>
   7:   8d b6 00 00 00 00         lea    0x0(%esi),%esi
Code;  cc846169 <[usbcore]usb_submit_urb+29/40>
   d:   8d bc 27 00 00 00 00      lea    0x0(%edi,1),%edi


1 warning issued.  Results may not be reliable.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.