Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-12-01 Thread Shawn Heisey
On 11/20/2010 11:55 AM, Ben Hutchings wrote: Try 'mii-tool -vv eth0'? New output. Just in case, I tried it with a third and fourth v, no difference. This is with it hard-set to 100 full, I can do it with it set to auto when I get home. frodo:~# mii-tool -vv eth0 Using SIOCGMIIPHY=0x8947

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-11-20 Thread Shawn Heisey
On 9/11/2010 8:15 PM, Ben Hutchings wrote: Please try this while running kernel version 2.6.32: 1. Enable additional error logging by running: ethtool -s eth0 msglvl 0x3f 2. Enable autoneg again 3. Disconnect and reconnect the cable 4. Check for any new error messages in the kernel log Also

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-11-20 Thread Shawn Heisey
On 11/20/2010 10:20 AM, Shawn Heisey wrote: Unknown RealTek chip (mask: 0x2800) I found what looks like a bug report and resolution for this same chip and problem in FreeBSD. http://www.pubbs.net/200904/netbsd/15177-50rc3-messed-up-rtl8111dl-onboard-nic.html I know there are licensing

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-11-20 Thread Ben Hutchings
On Sat, 2010-11-20 at 10:20 -0700, Shawn Heisey wrote: [...] ethtool -d eth0: Unknown RealTek chip (mask: 0x2800) So this is an RTL8168d, for which the upstream driver does load a firmware blob. It's possible that that blob fixes this bug (it's never been made clear just what it does).

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-09-11 Thread Shawn Heisey
On 9/10/2010 4:57 PM, Ben Hutchings wrote: Please test a newer version. There was a bug fix to r8169 in version 2.6.32-16 which might address this. I was already on the -20 version. Then I tried the -21 recently added to the backports archive, with no change. After a little

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-09-11 Thread Ben Hutchings
On Sat, 2010-09-11 at 01:03 -0600, Shawn Heisey wrote: On 9/10/2010 4:57 PM, Ben Hutchings wrote: Please test a newer version. There was a bug fix to r8169 in version 2.6.32-16 which might address this. I've already got 2.6.32-20, significantly newer than the -16 you're mentioning.

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-09-11 Thread Ben Hutchings
Forwarded Message From: Shawn Heisey elyog...@elyograg.org To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#596390: Log messages from 2.6.30 and 2.6.32 Date: Sat, 11 Sep 2010 01:03:40 -0600 On 9/10/2010 4:57 PM, Ben Hutchings wrote: Please test a newer version

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-09-11 Thread Ben Hutchings
On Sat, 2010-09-11 at 16:02 -0600, Shawn Heisey wrote: On 9/11/2010 10:46 AM, Ben Hutchings wrote: On Sat, 2010-09-11 at 01:03 -0600, Shawn Heisey wrote: On 9/10/2010 4:57 PM, Ben Hutchings wrote: Please test a newer version. There was a bug fix to r8169 in version 2.6.32-16

Bug#596390: Log messages from 2.6.30 and 2.6.32

2010-09-10 Thread Ben Hutchings
On Fri, 2010-09-10 at 16:31 -0600, Shawn Heisey wrote: Here's the full kernel log from both versions, taken a couple of minutes apart. I've had this trouble for quite some time, ever since 2.6.32 made it into lenny-backports. I'd like to get on the new kernel version and eliminate the