[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804181732.48546.mb@bu3sch.de>
Date: Fri, 18 Apr 2008 17:32:48 +0200
From: Michael Buesch <mb@...sch.de>
To: "Nelson A. de Oliveira" <naoliv@...il.com>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
netdev@...r.kernel.org, bugme-daemon@...zilla.kernel.org,
"Gary Zambrano" <zambrano@...adcom.com>
Subject: Re: [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY"
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@...sch.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists