From: Michael Buesch <mb@bu3sch.de>
To: "Nelson A. de Oliveira" <naoliv@gmail.com>
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 17:32:48 +0200 [thread overview]
Message-ID: <200804181732.48546.mb@bu3sch.de> (raw)
In-Reply-To: <9bfa9ae0804180823o1c3213ccj6ac1ab19b0b5cb94@mail.gmail.com>
On Friday 18 April 2008 17:23:06 Nelson A. de Oliveira wrote:
> Hi!
>
> On Fri, Apr 18, 2008 at 11:06 AM, Michael Buesch <mb@bu3sch.de> wrote:
> > > > While booting the new 2.6.25 Kernel, it enters an infinite looping displaying
> > > > "b44: eth0: powering down PHY".
> > > > The system isn't freezed as magick SysRq keys works, but it just stay
> > > > displaying those messages. I am unable to dump any information using SysRq,
> > > > however (as the b44(...) messages are too fast).
> > > >
> > > > I will attach lspci output and my .config
> > > >
> > >
> > > Apparently a regression.
> >
> > Can you add a dump_stack() call to the b44_halt() function and post the resulting logs?
>
> What I get is:
>
> Pid: 4, comm: ksoftirqd/0 Tainted: GF 2.6.25-naoliv1 #2
> [<f8992420>] [<b0231ffd>] [<b02380b9>] [<b011ed60>] [<b01060f2>]
> [<b011f059>] [<b011efe1>] [<b01297c8>] [<b0129790>] [<b010473f>]
Ehm, please enable CONFIG_KALLSYMS.
> BTW, is it a way to "pause" the messages after dump_stack()?
mdelay(1000) will delay one second. But it will kill the system, basically.
--
Greetings Michael.
next prev parent reply other threads:[~2008-04-18 15:33 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 [this message]
2008-04-18 17:12 ` Nelson A. de Oliveira
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=200804181732.48546.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=naoliv@gmail.com \
--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).