All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org, Michael Buesch <mb@bu3sch.de>
Cc: bugme-daemon@bugzilla.kernel.org, naoliv@gmail.com
Subject: Re: [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY"
Date: Thu, 17 Apr 2008 17:12:15 -0700	[thread overview]
Message-ID: <20080417171215.f7fbba3b.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10473-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Thu, 17 Apr 2008 17:08:27 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=10473
> 
>            Summary: Infinite loop "b44: eth0: powering down PHY"
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.25
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Network
>         AssignedTo: jgarzik@pobox.com
>         ReportedBy: naoliv@gmail.com
> 
> 
> Latest working kernel version: 2.6.24.4 (from Debian)
> Earliest failing kernel version: 2.6.25 (vanilla)
> Distribution: Debian
> Problem Description:
> 
> 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.

       reply	other threads:[~2008-04-18  0:13 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 ` Andrew Morton [this message]
2008-04-18 14:06   ` [Bugme-new] [Bug 10473] New: Infinite loop "b44: eth0: powering down PHY" 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
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=20080417171215.f7fbba3b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=naoliv@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.