Messages in this thread | | | Date | Tue, 30 Mar 2004 03:11:31 -0800 | From | Andrew Morton <> | Subject | Re: ohci1394 issues ( 2.6.5-rc2 and beyond ) |
| |
Michael Baehr <tehdely_lkml@metawire.org> wrote: > > I'm running a linux 2.6.5-rc2-mm5 kernel atm... motherboard is an Abit > NF7-s with an onboard firewire controller (I assume Nforce2 chipset). > > I get this loveliness everytime I modprobe ohci1394: > > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5] > MMIO=[e0084000-e00847ff] Max > Packet=[2048] > Badness in get_phy_reg at drivers/ieee1394/ohci1394.c:238 > Call Trace: > [<f8bb710e>] get_phy_reg+0x10e/0x120 [ohci1394] > [<f8bb7f3c>] ohci_devctl+0x5c/0x5d0 [ohci1394] > [<c03f23c0>] common_interrupt+0x18/0x20 > [<c0113d54>] delay_tsc+0x14/0x20 > [<f8bba058>] ohci_irq_handler+0x588/0x830 [ohci1394] > [<c012643f>] do_timer+0xdf/0xf0 > [<c010a8ca>] handle_IRQ_event+0x3a/0x70 > [<c010ac85>] do_IRQ+0xd5/0x1b0
That's due to a debug patch in -mm which catches out code which calls mdelay() from hard IRQ context. It's considered to be unsociable.
But there's nothing very wrong here.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |