Miles Lane wrote:
...
> Things went pretty well, until I ran
> "pccardctl eject" and then popped out the Firewire card.
...
> BUG: unable to handle kernel NULL pointer dereference at virtual
> address 00000000
...
> EIP is at dv1394_remove_host+0x17/0xad [dv1394]
...
> Call Trace:
> [<f91788c2>] __unregister_host+0x17/0x79 [ieee1394]
> [<f9178945>] highlevel_remove_host+0x21/0x42 [ieee1394]
> [<f9177e65>] hpsb_remove_host+0x37/0x56 [ieee1394]
> [<f912c9f2>] ohci1394_pci_remove+0x41/0x1cd [ohci1394]
> [<c10c5d24>] pci_device_remove+0x16/0x28
> [<c111dcbd>] __device_release_driver+0x5a/0x72
> [<c111de8f>] device_release_driver+0x1b/0x29
> [<c111d705>] bus_remove_device+0x78/0x8a
> [<c111c8a7>] device_del+0xe9/0x11a
> [<c111c8e0>] device_unregister+0x8/0x10
> [<c10c3ee5>] pci_remove_bus_device+0x39/0xcf
> [<c10c3f95>] pci_remove_behind_bridge+0x1a/0x2d
> [<f910d5ae>] socket_shutdown+0x89/0xdd [pcmcia_core]
> [<f910d675>] pcmcia_eject_card+0x56/0x65 [pcmcia_core]
...
Looks like the last word on
http://bugzilla.kernel.org/show_bug.cgi?id=2228 isn't spoken. Maybe the
bug can be fixed in dv1394 itself, or maybe we need to rework the
ieee1394 core's *_remove_host sequence.
Checking the 1394 driver stack's conduct during card hot-ejection is in
my long-term to-do list. Hopefully someone else can look at it sooner.
But I suggest you open a new bugzilla bug so we don't lose track.
I suppose the temporary workaround is to unload dv1394 before card ejection.
Thanks for this and the previous reports,
--
Stefan Richter
-=====-=-==- =--= -=---
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
