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, seraph@xs4all.nl
Subject: Re: [Bugme-new] [Bug 10273] New: Sun GEM (PCI) - network device doesn't work
Date: Mon, 17 Mar 2008 14:36:24 -0700	[thread overview]
Message-ID: <20080317143624.da313311.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10273-10286@http.bugzilla.kernel.org/>

On Mon, 17 Mar 2008 14:25:50 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=10273
> 
>            Summary: Sun GEM (PCI) - network device doesn't work
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.23
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: jgarzik@pobox.com
>         ReportedBy: seraph@xs4all.nl
> 
> 
> Latest working kernel version: 2.6.22.9
> Earliest failing kernel version: 2.6.23

A regression in 2.6.23.

> Distribution: Gentoo
> Hardware Environment: Sparc64 (Sun Blade 100)
> Software Environment:
> Problem Description: 
> 
> I have two nearly identical Sun Blade 100 systems. Up to and including kernel
> version 2.6.22.9, both were working fine. However, with the 2.6.23- and 2.6.24-
> series I cannot get the Sun GEM network device on one of the two Blades to
> work. The other one strangely does not have this problem at all.
> 
> The network device detects fine and the sungem module loads without problems.
> Mii-diag reports that a 100FDX connection exists and there is link beat.
> However, packets are neither being sent nor received, all counters in ifconfig
> remain at zero.
> 
> Attempts to use the network eventually result in the following message in
> dmesg:
> 
> eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:03:ba:08:61:7c
> eth0: Found Generic MII PHY
> eth0: Link is up at 100 Mbps, full-duplex.
> eth0: Link is up at 100 Mbps, full-duplex.
> eth0: Pause is disabled
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out, resetting
> eth0: TX_STATE[003ffc05:00000001:0000001f]
> eth0: RX_STATE[0100c805:00000001:00000021]
> eth0: Link is up at 100 Mbps, full-duplex.
> eth0: Pause is disabled
> 
> 
> The difference between the non-working system and the working one are as
> follows:
> - The non-working system has more memory (1G opposed to 512M)
> - A dual SCSI controller is present in this system. Connected to it are two
> external 72G disks and an Exabyte Mammoth tapedrive.
> 01:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14)
> 01:02.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14)
> - The following kernel modules are loaded on this system and not on the working
> one: sym53c8xx, sd_mod, st, nfsd, md_mod and raid1 plus of course their
> respective dependencies.
> 
> The problem is exactly the same with both Gentoo-patched kernels and vanilla
> kernels, that's why I am reporting it here.
> 
> 
> Steps to reproduce:
> 
> Just boot an affected kernel and try to use eth0 in any way.
> 


       reply	other threads:[~2008-03-17 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10273-10286@http.bugzilla.kernel.org/>
2008-03-17 21:36 ` Andrew Morton [this message]
2008-04-02 18:26   ` Fwd: [SPARC64] INO problem Re: [Bug 10273] New: Sun GEM (PCI) - network device doesn't work Jarek Poplawski
2008-04-10 10:30     ` David Miller
2008-04-25  7:26     ` David Miller
2008-04-25 19:59       ` Jos van der Ende
2008-04-25 20:35         ` David Miller

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=20080317143624.da313311.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=seraph@xs4all.nl \
    /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).