netdev - Re: [Bugme-new] [Bug 10273] New: Sun GEM (PCI)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080317143624.da313311.akpm@linux-foundation.org>
Date:	Mon, 17 Mar 2008 14:36:24 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	netdev@...r.kernel.org
Cc:	bugme-daemon@...zilla.kernel.org, seraph@...all.nl
Subject: Re: [Bugme-new] [Bug 10273] New: Sun GEM (PCI) - network device
 doesn't work

On Mon, 17 Mar 2008 14:25:50 -0700 (PDT)
bugme-daemon@...zilla.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@...ox.com
>         ReportedBy: seraph@...all.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.
> 

--
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