Re: Preemptive Kernel oops when disconnecting USBcard

My kernel is plain vanilla 2.4.22 with following patches against it in the
following descending order:
-preemptive-2.4.22 patch from kernel.org
-patch-2.4.23 UPGRADE to kernel 2.4.23
-LVM-1.0.8
-cryptoloop
-loop-jari
-super-freeswan-1.99.8

I enabled the preemptive feature and the APIC for nmi_watchdog=2 for this
kernel.

This is all I have.
I couldn't find the opps_file.txt

I've upgraded to 2.4.24 and will have to wait until I have physical access
to the box to hand copy the oops?

Jan  1 15:15:05 gateway kernel: usb-uhci.c: USB UHCI at I/O 0x1060, IRQ 11
Jan  1 15:15:05 gateway kernel: usb.c: new USB bus registered, assigned
bus numb
er 1
Jan  1 15:15:05 gateway kernel: hub.c: USB hub found
Jan  1 15:15:05 gateway kernel: hub.c: 2 ports detected
Jan  1 15:15:05 gateway kernel: usb-uhci.c: v1.275:USB Universal Host
Controller
 Interface driver
Jan  1 15:15:05 gateway kernel: at76c503.c: Generic Atmel
at76c503/at76c505 rout
ines v0.11beta6
Jan  1 15:15:05 gateway kernel: usbdfu.c: USB Device Firmware Upgrade
(DFU) hand
ler v0.11beta6
Jan  1 15:15:06 gateway kernel: usb.c: registered new driver usbdfu
Jan  1 15:15:06 gateway kernel: at76c503-rfmd.c: Atmel at76c503 (RFMD)
Wireless
LAN Driver v0.11beta6
Jan  1 15:15:06 gateway kernel: usb.c: registered new driver at76c503-rfmd
Jan  1 15:15:06 gateway kernel: hub.c: new USB device 00:07.2-2, assigned
addres
s 2
Jan  1 15:15:06 gateway kernel: usbdfu.c: Downloading firmware for USB
device 2.
..
Jan  1 15:27:44 gateway kernel: klogd 1.4.1, log source = /proc/kmsg started.


> On Sun, 4 Jan 2004, Per J wrote:
>
>> I'm using uhci.o from preemptive kernel 2.4.23 and at76c503a-0.11 rfmd
>> driver for the SMC 2662W v2 USB card.
>>
>> The preemptive kernel oops when I disconnect the USB card by pulling the
>> USB plug first.
>>
>> Also the kernel would oops when trying to load the rfmd driver when the
>> USB card is already plugged during reboot.
>>
>> I never had this problem with a non-preemptive kernel.
>>
>> It started doing this on the preemptive kernel.
>>
>> Help. What to do next?
>
> Try to run the oops output through ksymoops (which may need symbol
> infos from modules - you may need to copy /proc/ksyms after the driver is
> loaded to feed the copy into ksymoops via -k; see the man page) and post
> it.
>
> Is your "preemptive kernel 2.4.23" a plain-vanilla 2.4.23 with some
> preemptive patch applied?
>
> /Jörg