forwarded 652056 http://thread.gmane.org/gmane.linux.network/217197/focus=217203
quit
AymanHotmail wrote:
> It did reproduced the kernel panic, and repeating the same steps
> again with the patch did solve the problem (actually I'm writing
> this email running the patched one, something I couldn'
On 01/26/2012 02:12 PM, Jonathan Nieder wrote:
Debian kernel maintainers:
Please consider applying b189e810619a ("8139cp: fix missing
napi_gro_flush") to sid. In addition to fixing this oops, it would
help the submitter to test the fix, which would mean a quick journey
to the upstream linux-3.
AymanHotmail wrote:
> I'm sorry, I tried but it was overwhelming for me, I downloaded the
> source and lost it between steps 4.2.4 and 4.2.5.
> I'm still novice generally on linux, so I can't test the patch,
> except if there is already build kernel with the patch.
> Again thanks for your help and
On 01/26/2012 10:41 AM, Jonathan Nieder wrote:
tags 652056 + patch moreinfo
quit
AymanHotmail wrote:
Is it also a kernel BUG at [...]/net/core/dev.c:3719, like the
original one, and is the backtrace the same?
Well according to Image_02, it give a kernel BUG at
[...]/net/core/dev.c:3831 , and
tags 652056 + patch moreinfo
quit
AymanHotmail wrote:
>> Is it also a kernel BUG at [...]/net/core/dev.c:3719, like the
>> original one, and is the backtrace the same?
>
> Well according to Image_02, it give a kernel BUG at
> [...]/net/core/dev.c:3831 , and the backtrace is the same.
Thanks much
found 652056 linux-2.6/3.1.6-1
found 652056 linux-2.6/3.1.8-2
found 652056 linux-2.6/3.2.1-2
quit
Hi,
AymanGmail wrote:
> [Subject: 3.1.8-2 & 3.2.1-2 kernels still have the same issue]
Thanks for testing. Please keep in mind that this appears as an email
in a crowded inbox, so the subject line
6 matches
Mail list logo
