netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, gionnico@email.it
Subject: Re: [Bugme-new] [Bug 12432] New: [2.6.28 regression] sis900 fast ethernet breakage
Date: Sun, 11 Jan 2009 11:39:56 -0800	[thread overview]
Message-ID: <20090111113956.b5c75e83.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12432-10286@http.bugzilla.kernel.org/>


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

On Sun, 11 Jan 2009 11:00:58 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=12432
> 
>            Summary: [2.6.28 regression] sis900 fast ethernet breakage
>            Product: Networking
>            Version: 2.5
>      KernelVersion: 2.6.28
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: acme@ghostprotocols.net
>         ReportedBy: gionnico@email.it
> 
> 
> Latest working kernel version: 2.6.27
> Earliest failing kernel version: 2.6.28
> Distribution: gentoo
> Hardware Environment: i686, sis900 ethernet
> Problem Description: i can't reach the machine anymore, since i've installed
> 2.6.28 vanilla. it worked in 2.6.27 with the same configuration.
> 
> Steps to reproduce:
> You need a sis900 ethernet and even if you set an ip, the machine doesn't
> respond anymore to the net.
> I tried assigning a dynamic ip with dhcpcd eth0 and i'll post the dmesg.

It's a regression and I'm not seeing any likely-looking changes to that
driver in 2.6.28.


           reply	other threads:[~2009-01-11 19:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-12432-10286@http.bugzilla.kernel.org/>]

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=20090111113956.b5c75e83.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=gionnico@email.it \
    --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 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).