linux-kernel - Re: RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

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: <505CD982.2000409@asyr.hopto.org>
Date:	Sat, 22 Sep 2012 00:17:54 +0300
From:	Thanasis <thanasis@...r.hopto.org>
To:	Francois Romieu <romieu@...zoreil.com>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Hayes Wang <hayeswang@...ltek.com>
Subject: Re: RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

on 09/21/2012 11:29 PM Francois Romieu wrote the following:
> Thanasis <thanasis@...r.hopto.org> :
>> So far, ping has failed *only* at this iteration of the make loop:
> 
> Ok.
> 
> Without the usual netdev watchdog message I presume ?

What message? What do you mean "the usual netdev watchdog message"?
I used a usb stick to transfer the log to another machine, if that's
what you mean.

> 
> [...]
>> Now, after 74 iterations, it looks as if the loop is stuck at the following:
>>
>> HEAD is now at 1ce4b16 r8169: spinlock redux.
>> make -C /lib/modules/2.6.38-r8/build
>> M=/mnt/usb-disk/atom/usr/src/test-r8169/r8169 modules
>> make[1]: Entering directory `/usr/src/linux-2.6.38-r8'
>>   CC [M]  /mnt/usb-disk/atom/usr/src/test-r8169/r8169/r8169.o
>>   Building modules, stage 2.
>>   MODPOST 1 modules
>>   CC      /mnt/usb-disk/atom/usr/src/test-r8169/r8169/r8169.mod.o
>>   LD [M]  /mnt/usb-disk/atom/usr/src/test-r8169/r8169/r8169.ko
>> make[1]: Leaving directory `/usr/src/linux-2.6.38-r8'
>>
>>
>> Should I wait for it to end?
> 
> No. I surely f*cked up something.
> 
>> Do you want me to post the whole log so far?
> 
> Please. It should gzip well. The complete dmesg with timestamps would be
> welcome too.

Attached dmesg.gz
> 
> Could you perform a test with your vendor's 3.2-something kernel and its
> r8169 driver ?
> 
The vendor's kernel was a 2.6 series.

Download attachment "dmesg.gz" of type "application/x-gzip" (12605 bytes)