Re: r8169 doesn't work after boot until `transmit queue 0 timed out`

On Fri, Apr 27, 2018 at 8:22 PM, ojab // wrote: > Oh hai! > > I've created bugzilla ticket about this, but I'm not sure if anyone > reads it, so duplicating here. > > I have new motherboard (ASUS A320-K) with 10ec:8168 realtek network > card installed and it doesn't work (i. e.

r8169 doesn't work after boot until `transmit queue 0 timed out`

Oh hai! I've created bugzilla ticket about this, but I'm not sure if anyone reads it, so duplicating here. I have new motherboard (ASUS A320-K) with 10ec:8168 realtek network card installed and it doesn't work (i. e. `tcpdump` shows outgoing packets but no packets are actually transmitted and

Re: r8169 doesn't work

Francois Romieu [EMAIL PROTECTED] writes: [...] Oh, thanks. I'll try. Excellent. That patchset works fine for me. (i386 + smp, i386 + up, x86_64 + smp) I hope to include those patches to 2.6.21. Thanks. -- OGAWA Hirofumi [EMAIL PROTECTED] - To unsubscribe from this list: send the line

Re: r8169 doesn't work

OGAWA Hirofumi [EMAIL PROTECTED] : [...] That patchset works fine for me. (i386 + smp, i386 + up, x86_64 + smp) Cool. I hope to include those patches to 2.6.21. The patchkit is scheduled for the next merge window. It fixes things for some users but: 1. it missed the merge window of 2.6.21 2.

r8169 doesn't work

Hi, I have a r8169 problem, it seems RX doesn't work. To work r8169 for me I'm needing to revert the following three commits now, but I don't know why. 9cb427b6ff0b3e235c518acf5c1fcbbfc95f0ae2 12d86f682e8acad8555718dc7b0082590f2365d0 cc9f022d97d08e4e36d38661857991fe91447d68 Any

Re: r8169 doesn't work

OGAWA Hirofumi [EMAIL PROTECTED] : [...] I have a r8169 problem, it seems RX doesn't work. To work r8169 for me I'm needing to revert the following three commits now, but I don't know why. 9cb427b6ff0b3e235c518acf5c1fcbbfc95f0ae2 12d86f682e8acad8555718dc7b0082590f2365d0

Re: r8169 doesn't work

Francois Romieu [EMAIL PROTECTED] writes: OGAWA Hirofumi [EMAIL PROTECTED] : [...] I have a r8169 problem, it seems RX doesn't work. To work r8169 for me I'm needing to revert the following three commits now, but I don't know why. 9cb427b6ff0b3e235c518acf5c1fcbbfc95f0ae2

Re: r8169 doesn't work

OGAWA Hirofumi [EMAIL PROTECTED] : [...] IIRC, First broken one was 9cb427b6ff0b3e235c518acf5c1fcbbfc95f0ae2. To make sure, I'll confirm tomorrow. If your kernel includes 9cb427b6ff0b3e235c518acf5c1fcbbfc95f0ae2 but misses 81f4e6c190a0fa016fd7eecaf76a5f95d121afc2, you can consider it a known