linux-kernel - Re: 2.6.24-mm1 bugs

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: <47B5D6EB.5010203@intel.com>
Date:	Fri, 15 Feb 2008 10:16:11 -0800
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Miklos Szeredi <miklos@...redi.hu>
CC:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: 2.6.24-mm1 bugs

Miklos Szeredi wrote:
>> OK. can you download, install and run `ethregs -i eth0` (from
>> e1000.sf.net) and send me the output? I'll compare with a known
>> working t60 I have here and see if anything shows up.
> 
> OK, attached.
> 
>> Also, post me the dmesg from after the adapter fails to load
>> properly.
> 
> Hmm, nothing in dmesg.  Looking at syslog, I'm not even sure it's a
> driver issue, it could also be dhclient or NetworkManager bug.  The
> strange thing is that this only happens on -mm.
> 
> These are the relevant syslog messages for an unsuccessful attempt:
> 
> ==========================================================================
> Feb 15 12:27:32 tucsk kernel: [   35.169183] 0000:02:00.0: eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
> Feb 15 12:27:32 tucsk kernel: [   35.169190] 0000:02:00.0: eth0: 10/100 speed: disabling TSO
> Feb 15 12:27:40 tucsk dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
> Feb 15 12:27:40 tucsk dhclient: DHCPOFFER from 192.168.0.1
> Feb 15 12:27:45 tucsk dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
> Feb 15 12:27:45 tucsk dhclient: DHCPACK from 192.168.0.1
> Feb 15 12:27:46 tucsk dhclient: bound to 192.168.0.9 -- renewal in 1539 seconds.
> Feb 15 12:28:20 tucsk dhclient: caught deadly SIGTERM
> Feb 15 12:28:20 tucsk dhclient: could not restore resolv.conf: No such file or directory
> Feb 15 12:28:20 tucsk dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
> Feb 15 12:28:20 tucsk dhclient: send_packet: Network is unreachable
> Feb 15 12:28:20 tucsk dhclient: send_packet: please consult README file regarding broadcast address.
> ==========================================================================
> 
> And then for the successful one:
> 
> ==========================================================================
> Feb 15 12:29:17 tucsk dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
> Feb 15 12:29:17 tucsk dhclient: DHCPOFFER from 192.168.0.1
> Feb 15 12:29:22 tucsk dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
> Feb 15 12:29:22 tucsk dhclient: DHCPACK from 192.168.0.1
> Feb 15 12:29:22 tucsk dhclient: bound to 192.168.0.9 -- renewal in 1543 seconds.
> ==========================================================================
> 
> Thanks,
> Miklos
> 
> 
> 
> 02:00.0 (8086:109a)
> Unknown device 8086:109a
> 	Name           Value
> 	~~~~           ~~~~~
> 	CTRL           18140248

the register dump looks OK as far as I can see. Since initialization works OK and
the adapter seems to be setup OK reading from the register dump, I'm not sure at
all what is going on.

can you try manually ifup-ing the device and running tcpdump? do you see packets
coming in?

just for kicks, have you tried a different cable? or is the adapter consistently
working properly using a different kernel/driver?

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