Re: [PATCH 2.4] blacklist a device in usb-storage

From: Pete Zaitcev
Date: Mon Aug 16 2004 - 17:40:32 EST


On Mon, 16 Aug 2004 18:54:25 +0300
"O.Sezer" <sezeroz@xxxxxxxxxxxx> wrote:

> EIP: 0010: [<e0d24da0>] Not tainted

> Call Trace: [<e0a3b9cf>] [<e0a3bde4>] [<e0207ee9>]
> [<e0a3be87>] [<c010a848>] [<c010aa33>]
> [<e0ae4385>] [<c0107150>] [<c0105000>]
> [<c01071f4>]

> >>EIP; e0d24da0 <[sr_mod]sr_registered+22deec/22e1ac> <=====

> Trace; e0a3b9cf <[usb-uhci]process_interrupt+21f/260>
> Trace; e0a3bde4 <[usb-uhci]process_urb+254/260>
> Trace; e0207ee9 <_end+1fe721a5/2064e31c>
> Trace; e0a3be87 <[usb-uhci]uhci_interrupt+97/170>
> Trace; c010a848 <handle_IRQ_event+48/80>
> Trace; c010aa33 <do_IRQ+83/f0>
> Trace; c0107150 <default_idle+0/40>
> Trace; c01071f4 <cpu_idle+34/40>

Hmm. This looks fishy, because sr_registered is not a function.

Does the same happen after "echo /bin/true > /proc/sys/kernel/hotplug"?
Maybe your hotplug setup yanks a module. I heard some crazy distro
did that on unplug.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/