From: "Nelson A. de Oliveira" <naoliv@gmail.com>
To: "Michael Buesch" <mb@bu3sch.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
"Gary Zambrano" <zambrano@broadcom.com>
Subject: Re: [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY"
Date: Fri, 18 Apr 2008 14:12:34 -0300 [thread overview]
Message-ID: <9bfa9ae0804181012l451687d8o7e6ce1f5213ff716@mail.gmail.com> (raw)
In-Reply-To: <200804181732.48546.mb@bu3sch.de>
Hi!
On Fri, Apr 18, 2008 at 12:32 PM, Michael Buesch <mb@bu3sch.de> wrote:
> Ehm, please enable CONFIG_KALLSYMS.
Right. Sorry.
Here it is:
Pid: 4, comm: ksoftirqd/0 Tainted: GF 2.6.25-naoliv #4
[<f899df84>] b44_halt+0x68/0x7f [b44]
[<f899f432>] b44_poll+0x36a/0x405 [b44]
[<b02393ad>] net_rx_action+0x63/0x131
[<b011ee60>] __do_softirq+0x5a/0xa5
[<b01061e2>] do_softirq+0x52/0x84
[<b011f159>] ksoftirqd+0x78/0x110
[<b011f0e1>] ksoftirqd+0x0/0x110
[<b01298d4>] kthread+0x38/0x60
[<b012989c>] kthread+0x0/0x60
[<b010474b>] kernel_thread_helper+0x7/0x10
Anything else that I can do to help, please?
Thank you!
Best regards,
Nelson
next prev parent reply other threads:[~2008-04-18 17:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10473-10286@http.bugzilla.kernel.org/>
2008-04-18 0:12 ` [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY" Andrew Morton
2008-04-18 14:06 ` Michael Buesch
2008-04-18 15:23 ` Nelson A. de Oliveira
2008-04-18 15:32 ` Michael Buesch
2008-04-18 17:12 ` Nelson A. de Oliveira [this message]
2008-04-18 17:19 ` Michael Buesch
2008-04-18 17:43 ` Nelson A. de Oliveira
2008-04-18 17:59 ` Michael Buesch
2008-04-18 18:09 ` Nelson A. de Oliveira
2008-04-18 18:18 ` Michael Buesch
2008-04-18 19:02 ` Nelson A. de Oliveira
2008-04-18 19:19 ` Michael Buesch
2008-04-18 20:38 ` Nelson A. de Oliveira
2008-04-21 18:14 ` Nelson A. de Oliveira
2008-04-21 18:21 ` Michael Buesch
2008-04-22 3:01 ` Nelson A. de Oliveira
2008-04-22 13:34 ` Michael Buesch
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=9bfa9ae0804181012l451687d8o7e6ce1f5213ff716@mail.gmail.com \
--to=naoliv@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=zambrano@broadcom.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;
as well as URLs for NNTP newsgroup(s).