linux-kernel - Re: Soft lockup in sungem on Netra AC200 when switching interface up

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID:  <slrngop4qe.rks.alex@woodchuck.wormnet.eu>
Date:	Fri, 6 Feb 2009 19:45:18 +0000
From:	Alexander Clouter <alex@...riz.org.uk>
To:	linux-kernel@...r.kernel.org
Subject:  Re: Soft lockup in sungem on Netra AC200 when switching interface up

* Ilkka Virta <itvirta@....fi> [Fri, 6 Feb 2009 13:29:02 +0200]:
> What ho, chaps
>
> The sungem network driver seems to be broken with the integrated
> Ethernet ports of a Sun Netra T1 AC200. On that machine, switching the
> interface up when link is up leads to a soft lockup. However,
> switching the interface up with no link, and only then connecting the
> cable works; as does the same driver on seemingly same hardware on a
> Sun Blade 1000.
>
Et tu Brute?

> lspci doesn't show any real differences between the gems on the Netra
> and on the Blade, both are these: 
> 0000:00:05.1 Ethernet controller [0200]: Sun Microsystems Computer
>              Corp. RIO 10/100 Ethernet [eri] [108e:1101] (rev 01)
>
> Earlier reports of the same problem indicate that the driver was
> broken by commit bea3348eef27e6044b6161fd04c3152215f96411 in around
> 2.6.24, but the problem still exists in 2.6.28.
>
> http://kerneltrap.org/mailarchive/linux-kernel/2008/8/7/2856094
> http://bugzilla.kernel.org/show_bug.cgi?id=10309
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508151
>
> Now, I didn't find any ready-made cure for this, so I poked around the
> driver a bit to see what happens. What follows is very much only
> guesswork, since I don't really know anything about Linux network
> drivers.
>
I live with the following:
----
# The primary network interface (right hand side port)
auto eth0
iface eth0 inet static
  address 77.75.105.223
  netmask 255.255.255.0
  gateway 77.75.105.1

  pre-up ethtool -s eth0 autoneg off
  pre-up ethtool -s eth1 autoneg off
  pre-up ethtool -s eth0 autoneg on
----

Seems to make it work...the autonegoation caused it to sulk if the cable 
was in for us.  The above worked, and has since I started using it.  We 
are running 2.6.24 but I'm pretty sure the problem was there back on 
2.6.18.  I have a spare Netra in my attic for testing but last time I 
reported this no one seemed to care so I lived with my 'workaround'.

As a side note, do you find the cpufreq scaling locks up your machine 
instantly without even an oops?

Cheers

-- 
Alexander Clouter
.sigmonster says: Hold the MAYO & pass the COSMIC AWARENESS ...

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/