From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Miles Lane <miles.lane@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6.17-rc6-mm1 -- BUG: warning at drivers/ieee1394/ohci1394.c:235/get_phy_reg()
Date: Sat, 10 Jun 2006 09:28:49 +0200 [thread overview]
Message-ID: <448A74B1.5000606@s5r6.in-berlin.de> (raw)
In-Reply-To: <a44ae5cd0606092234k70f92bfajb359a9e0c09db3b9@mail.gmail.com>
Miles Lane wrote at lkml:
> BUG: warning at drivers/ieee1394/ohci1394.c:235/get_phy_reg()
> [<c0103999>] show_trace_log_lvl+0x53/0xff
> [<c0103ff1>] show_trace+0x16/0x19
> [<c0104037>] dump_stack+0x1a/0x1f
> [<f9295ade>] get_phy_reg+0x77/0xe4 [ohci1394]
> [<f9295e66>] ohci_devctl+0x49/0x56c [ohci1394]
> [<f9298e82>] ohci_irq_handler+0x329/0x720 [ohci1394]
> [<c01435cd>] handle_IRQ_event+0x18/0x4d
> [<c01443fb>] handle_fasteoi_irq+0x57/0x95
> [<c01050bf>] do_IRQ+0xa1/0xc6
> [<c0103475>] common_interrupt+0x25/0x2c
> BUG: warning at drivers/ieee1394/ohci1394.c:264/set_phy_reg()
> [<c0103999>] show_trace_log_lvl+0x53/0xff
> [<c0103ff1>] show_trace+0x16/0x19
> [<c0104037>] dump_stack+0x1a/0x1f
> [<f9295a14>] set_phy_reg+0x84/0xd7 [ohci1394]
> [<f9295e79>] ohci_devctl+0x5c/0x56c [ohci1394]
> [<f9298e82>] ohci_irq_handler+0x329/0x720 [ohci1394]
> [<c01435cd>] handle_IRQ_event+0x18/0x4d
> [<c01443fb>] handle_fasteoi_irq+0x57/0x95
> [<c01050bf>] do_IRQ+0xa1/0xc6
> [<c0103475>] common_interrupt+0x25/0x2c
Above trace seems to appear due to a hack to get certain FireWire
controllers going: Apple UniNorth, NVidia nForce2. Miles, do you have
one of those?
A similar trace occurs as ohci_irq_handler -> hpsb_selfid_complete
-> highlevel_host_reset -> csr.c::host_reset -> {ohci_}hw_csr_reg ->
mdelay. This host_rest's purpose is to mark iso channel 31 as default
broadcast channel. This functionality can probably be moved into a
workqueue job or into nodemgr's kthread. This is currently being tracked
as http://bugzilla.kernel.org/show_bug.cgi?id=6070 but I am afraid
nobody is actively working on it yet.
--
Stefan Richter
-=====-=-==- -==- -=-=-
http://arcgraph.de/sr/
prev parent reply other threads:[~2006-06-10 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 5:34 Miles Lane
2006-06-10 7:28 ` Stefan Richter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=448A74B1.5000606@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=miles.lane@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®