on 09/26/2012 08:41 AM Thanasis wrote the following:
> on 09/25/2012 11:53 PM Francois Romieu wrote the following:
>> Thanasis :
>> [...]
>>> Ping failed in the following step:
>>>
>>> HEAD is now at 3c6ad46 r8169: move rtl_set_rx_mode before its
>>> rtl_hw_start callers.
>>
>> *spleen*
>>
>>
on 09/26/2012 08:41 AM Thanasis wrote the following:
on 09/25/2012 11:53 PM Francois Romieu wrote the following:
Thanasis thana...@asyr.hopto.org :
[...]
Ping failed in the following step:
HEAD is now at 3c6ad46 r8169: move rtl_set_rx_mode before its
rtl_hw_start callers.
*spleen*
It's
on 09/25/2012 11:53 PM Francois Romieu wrote the following:
> Thanasis :
> [...]
>> Ping failed in the following step:
>>
>> HEAD is now at 3c6ad46 r8169: move rtl_set_rx_mode before its
>> rtl_hw_start callers.
>
> *spleen*
>
> It's a genuine code move without any real change. Imho it's more a
Thanasis :
[...]
> Ping failed in the following step:
>
> HEAD is now at 3c6ad46 r8169: move rtl_set_rx_mode before its
> rtl_hw_start callers.
*spleen*
It's a genuine code move without any real change. Imho it's more a
matter of sleeping a few seconds for the link to settle after the
device
on 09/25/2012 12:54 PM Francois Romieu wrote the following:
> Thanasis :
> [...]
>> I don't know what's wrong, but I am getting those errors.
>> Are you sure about the git tree?
>
> Yes. Replace 'git rev-list --all' with 'git rev-list --branches'.
>
> It should show something like:
> $ git
Thanasis :
[...]
> I don't know what's wrong, but I am getting those errors.
> Are you sure about the git tree?
Yes. Replace 'git rev-list --all' with 'git rev-list --branches'.
It should show something like:
$ git rev-list --branches
a65a9b5d9c4569228909e36bb6e20d33fe208950
on 09/25/2012 02:12 AM Francois Romieu wrote the following:
> Thanasis :
>> Attached the whole log so far.
>> (the process looks stuck anyway for more than 30 min at the same point)
>
> You don't need to wait that long.
>
> I have updated git://violet.fr.zoreil.com/romieu/r8169 with a
>
on 09/25/2012 02:12 AM Francois Romieu wrote the following:
Thanasis thana...@asyr.hopto.org :
Attached the whole log so far.
(the process looks stuck anyway for more than 30 min at the same point)
You don't need to wait that long.
I have updated git://violet.fr.zoreil.com/romieu/r8169
Thanasis thana...@asyr.hopto.org :
[...]
I don't know what's wrong, but I am getting those errors.
Are you sure about the git tree?
Yes. Replace 'git rev-list --all' with 'git rev-list --branches'.
It should show something like:
$ git rev-list --branches
on 09/25/2012 12:54 PM Francois Romieu wrote the following:
Thanasis thana...@asyr.hopto.org :
[...]
I don't know what's wrong, but I am getting those errors.
Are you sure about the git tree?
Yes. Replace 'git rev-list --all' with 'git rev-list --branches'.
It should show something like:
Thanasis thana...@asyr.hopto.org :
[...]
Ping failed in the following step:
HEAD is now at 3c6ad46 r8169: move rtl_set_rx_mode before its
rtl_hw_start callers.
*spleen*
It's a genuine code move without any real change. Imho it's more a
matter of sleeping a few seconds for the link to settle
on 09/25/2012 11:53 PM Francois Romieu wrote the following:
Thanasis thana...@asyr.hopto.org :
[...]
Ping failed in the following step:
HEAD is now at 3c6ad46 r8169: move rtl_set_rx_mode before its
rtl_hw_start callers.
*spleen*
It's a genuine code move without any real change. Imho
Thanasis :
> Attached the whole log so far.
> (the process looks stuck anyway for more than 30 min at the same point)
You don't need to wait that long.
I have updated git://violet.fr.zoreil.com/romieu/r8169 with a
'3.2.r8169.backport' branch.
You can remove your existing r8169 git tree, clone
Thanasis thana...@asyr.hopto.org :
Attached the whole log so far.
(the process looks stuck anyway for more than 30 min at the same point)
You don't need to wait that long.
I have updated git://violet.fr.zoreil.com/romieu/r8169 with a
'3.2.r8169.backport' branch.
You can remove your existing
on 09/22/2012 01:53 AM Francois Romieu wrote the following:
>>> Could you perform a test with ... 3.2-something kernel and its
>>> r8169 driver ?
As I said in my previous mail, I tried the r8169 of 3.2.30 and it works.
FWIW, while compiling the 3.2.30 kernel I saw this warning:
on 09/22/2012 01:53 AM Francois Romieu wrote the following:
>
> You did experience a failure with a 3.5.4 kernel. Can you try a 3.2.x
I downloaded the stable 3.2.30 and compiled.
It worked. The r8169 driver of the latest (22 Sep 2012) stable 3.2.30
source tree for the NIC in subject works.
on 09/22/2012 01:53 AM Francois Romieu wrote the following:
> You did experience a failure with a 3.5.4 kernel. Can you try a 3.2.x if
> your vendor provides one ?
>
The vendor does not provide a 3.x kernel. But I will compile one.
Do you want me to run the r8169 make tests, if the r8169 of the
on 09/22/2012 01:53 AM Francois Romieu wrote the following:
You did experience a failure with a 3.5.4 kernel. Can you try a 3.2.x if
your vendor provides one ?
The vendor does not provide a 3.x kernel. But I will compile one.
Do you want me to run the r8169 make tests, if the r8169 of the
on 09/22/2012 01:53 AM Francois Romieu wrote the following:
You did experience a failure with a 3.5.4 kernel. Can you try a 3.2.x
I downloaded the stable 3.2.30 and compiled.
It worked. The r8169 driver of the latest (22 Sep 2012) stable 3.2.30
source tree for the NIC in subject works.
--
on 09/22/2012 01:53 AM Francois Romieu wrote the following:
Could you perform a test with ... 3.2-something kernel and its
r8169 driver ?
As I said in my previous mail, I tried the r8169 of 3.2.30 and it works.
FWIW, while compiling the 3.2.30 kernel I saw this warning:
Thanasis :
> on 09/21/2012 11:29 PM Francois Romieu wrote the following:
[...]
> What message? What do you mean "the usual netdev watchdog message"?
No, this one (see your 3.5.4 kernel log):
[ 23.712058] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x121/0x1a3(
)
[ 23.712062]
on 09/21/2012 11:29 PM Francois Romieu wrote the following:
> Thanasis :
>> 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
Thanasis :
> So far, ping has failed *only* at this iteration of the make loop:
Ok.
Without the usual netdev watchdog message I presume ?
[...]
> 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
Attached the whole log so far.
(the process looks stuck anyway for more than 30 min at the same point)
lets-go-shopping.log.bz2
Description: application/bzip
So far, ping has failed *only* at this iteration of the make loop:
HEAD is now at b087148 r8169: support control of advertising.
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]
Thanasis :
[...]
> Hmm, think I got it ... Here is what I put there:
>
> ifconfig eth0 192.168.0.19 up ; ping -c 3 192.168.0.1
If it fails with the r8169 driver included in the 3.5 tree, that's what
you can use, yes (you may add a second ping with -q -f -l and more
packets to wrap the descriptor
on 09/21/2012 07:30 PM Thanasis wrote the following:
> on 09/21/2012 06:28 PM Francois Romieu wrote the following:
>>
> I don't get what you mean by the above step.
> Could you be more explicit please?
Hmm, think I got it ... Here is what I put there:
ifconfig eth0 192.168.0.19 up ; ping -c 3
on 09/21/2012 06:28 PM Francois Romieu wrote the following:
> Thanasis :
>> on 09/21/2012 02:20 AM Francois Romieu wrote the following:
> [...]
>>> Thanasis, can you narrow down a bit the failing revision ?
>>
>> Sure, let me know how to do it please.
>
> A rough kernel estimate had been enough.
on 09/21/2012 06:28 PM Francois Romieu wrote the following:
>
I don't get what you mean by the above step.
Could you be more explicit please?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Thanasis :
> on 09/21/2012 02:20 AM Francois Romieu wrote the following:
[...]
> > Thanasis, can you narrow down a bit the failing revision ?
>
> Sure, let me know how to do it please.
A rough kernel estimate had been enough. Nevermind.
You will find a hopefully not too quick 2.6.38 backport
Thanasis thana...@asyr.hopto.org :
on 09/21/2012 02:20 AM Francois Romieu wrote the following:
[...]
Thanasis, can you narrow down a bit the failing revision ?
Sure, let me know how to do it please.
A rough kernel estimate had been enough. Nevermind.
You will find a hopefully not too quick
on 09/21/2012 06:28 PM Francois Romieu wrote the following:
insert your ip addr add ... / link up and test sequence here
I don't get what you mean by the above step.
Could you be more explicit please?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
on 09/21/2012 06:28 PM Francois Romieu wrote the following:
Thanasis thana...@asyr.hopto.org :
on 09/21/2012 02:20 AM Francois Romieu wrote the following:
[...]
Thanasis, can you narrow down a bit the failing revision ?
Sure, let me know how to do it please.
A rough kernel estimate had
on 09/21/2012 07:30 PM Thanasis wrote the following:
on 09/21/2012 06:28 PM Francois Romieu wrote the following:
insert your ip addr add ... / link up and test sequence here
I don't get what you mean by the above step.
Could you be more explicit please?
Hmm, think I got it ... Here is what I
Thanasis thana...@asyr.hopto.org :
[...]
Hmm, think I got it ... Here is what I put there:
ifconfig eth0 192.168.0.19 up ; ping -c 3 192.168.0.1
If it fails with the r8169 driver included in the 3.5 tree, that's what
you can use, yes (you may add a second ping with -q -f -l and more
packets to
So far, ping has failed *only* at this iteration of the make loop:
HEAD is now at b087148 r8169: support control of advertising.
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]
Attached the whole log so far.
(the process looks stuck anyway for more than 30 min at the same point)
lets-go-shopping.log.bz2
Description: application/bzip
Thanasis thana...@asyr.hopto.org :
So far, ping has failed *only* at this iteration of the make loop:
Ok.
Without the usual netdev watchdog message I presume ?
[...]
Now, after 74 iterations, it looks as if the loop is stuck at the following:
HEAD is now at 1ce4b16 r8169: spinlock redux.
on 09/21/2012 11:29 PM Francois Romieu wrote the following:
Thanasis thana...@asyr.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
Thanasis thana...@asyr.hopto.org :
on 09/21/2012 11:29 PM Francois Romieu wrote the following:
[...]
What message? What do you mean the usual netdev watchdog message?
No, this one (see your 3.5.4 kernel log):
[ 23.712058] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x121/0x1a3(
)
[
on 09/21/2012 02:20 AM Francois Romieu wrote the following:
>
> Thanasis, can you narrow down a bit the failing revision ?
Sure, let me know how to do it please.
FWIW , attached full lspci -k output.
00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller
Hub (rev 03)
Bjorn Helgaas :
[...]
> Thanks. I don't see anything wrong from the PCI core point of view.
> But searching for "r8169 transmit queue timed out" found lots of
> similar reports.
It's a rather common symptom when things go wrong :o/
> +cc 8169 driver folks
(thanks)
Thanasis, can you narrow
On Thu, Sep 20, 2012 at 12:10 PM, Thanasis wrote:
> on 09/20/2012 08:47 PM Bjorn Helgaas wrote the following:
>> On Thu, Sep 20, 2012 at 11:28 AM, Thanasis wrote:
>>> I have an Acer Aspire One notebook, and it has a NIC as shown below:
>>>
>>> # lspci |grep -i Realtek
>>> 02:00.0 Ethernet
on 09/20/2012 08:47 PM Bjorn Helgaas wrote the following:
> On Thu, Sep 20, 2012 at 11:28 AM, Thanasis wrote:
>> I have an Acer Aspire One notebook, and it has a NIC as shown below:
>>
>> # lspci |grep -i Realtek
>> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL8101E/RTL8102E
On Thu, Sep 20, 2012 at 11:28 AM, Thanasis wrote:
> I have an Acer Aspire One notebook, and it has a NIC as shown below:
>
> # lspci |grep -i Realtek
> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
>
> The driver
On Thu, Sep 20, 2012 at 11:28 AM, Thanasis thana...@asyr.hopto.org wrote:
I have an Acer Aspire One notebook, and it has a NIC as shown below:
# lspci |grep -i Realtek
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
on 09/20/2012 08:47 PM Bjorn Helgaas wrote the following:
On Thu, Sep 20, 2012 at 11:28 AM, Thanasis thana...@asyr.hopto.org wrote:
I have an Acer Aspire One notebook, and it has a NIC as shown below:
# lspci |grep -i Realtek
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
On Thu, Sep 20, 2012 at 12:10 PM, Thanasis thana...@asyr.hopto.org wrote:
on 09/20/2012 08:47 PM Bjorn Helgaas wrote the following:
On Thu, Sep 20, 2012 at 11:28 AM, Thanasis thana...@asyr.hopto.org wrote:
I have an Acer Aspire One notebook, and it has a NIC as shown below:
# lspci |grep -i
Bjorn Helgaas bhelg...@google.com :
[...]
Thanks. I don't see anything wrong from the PCI core point of view.
But searching for r8169 transmit queue timed out found lots of
similar reports.
It's a rather common symptom when things go wrong :o/
+cc 8169 driver folks
(thanks)
Thanasis, can
on 09/21/2012 02:20 AM Francois Romieu wrote the following:
Thanasis, can you narrow down a bit the failing revision ?
Sure, let me know how to do it please.
FWIW , attached full lspci -k output.
00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller
Hub (rev 03)
50 matches
Mail list logo
