Skip to contentSkip to conversation

Regression 2.6.36 - driver rtl8169 crashes kernel, triggered by user app

DISCUSSION Michael Monnerie 3 participants 4 messages Nov 27, 2010 – Nov 28, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

This is the 3rd time I send this, and I did not get any answer. I thought *regressions* are a bad thing that would be handled quickly? Maybe this helps: *SHITTY DRIVER NOT WORKING ANYMORE*

Dear list, I've hunted down a bug which does *NOT* occur in kernel 2.6.34.7-0.5-desktop from openSUSE 11.3, but crashes stock kernel 2.6.36 triggered by a user!

It's actually very simple. From my desktop (kernel 2.6.36) I "cd" to an NFS4 share, where a xz compressed image of Win7-64.iso.xz is located.

# cd /q/iso-images

and then I try to uncompress it there (as user, not root!):

# xz -kv Win7-64.iso.xz

With kernel 2.6.34.7-0.5-desktop, this runs with ~41MiB/s without problems.

With kernel 2.6.36, it runs at ~26MiB/s, and while doing so, dmesg shows a lot of noise about r8169 complaining:
http://zmi.at/x/kernel2.6.36-crash86.jpg

Here are 2 pictures of different crashes:
http://zmi.at/x/kernel2.6.36-crash84.jpg
http://zmi.at/x/kernel2.6.36-crash85.jpg

Neither the dmesg-messages nor the crash happens with kernel 2.6.34.7-0.5-desktop as delivered by openSUSE 11.3, but it always fully crashes 2.6.36. I've retried about 10 times, it *never* finished to uncompress the ~3GB image. At around 500-1000MB the kernel was gone.

I'm sure someone knows how to fix it. :-)

Signature · 6 lines
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
#1 lore raw

Michael Monnerie <[email protected]> :

Quoted 1 line

This is the 3rd time I send this, and I did not get any answer.

What about changing your mx blacklisting policy or checking the mailing-list archive (http://marc.info/?t=128950098300003) ?

Quoted 1 line

I thought *regressions* are a bad thing that would be handled quickly?

You are strongly suggested to try current -git kernel. A regression with similar symptoms has already been fixed.

Quoted 1 line

Maybe this helps: *SHITTY DRIVER NOT WORKING ANYMORE*

It does not help, Krusty. Try running for Congress.

Signature · 1 line
Ueimor
#2 lore raw
Quoted 5 lines · Francois Romieu

Michael Monnerie <[email protected]> :

Quoted 1 line

This is the 3rd time I send this, and I did not get any answer.

What about changing your mx blacklisting policy or checking the mailing-list archive (http://marc.info/?t=128950098300003) ?

Maybe some artificial intelligence in the driver? ;-)

Jarek P.

Quoted 10 lines
Quoted 2 lines

I thought *regressions* are a bad thing that would be handled quickly?

You are strongly suggested to try current -git kernel. A regression with similar symptoms has already been fixed.

Quoted 1 line

Maybe this helps: *SHITTY DRIVER NOT WORKING ANYMORE*

It does not help, Krusty. Try running for Congress.

#3 lore raw
In reply to Francois Romieu
Quoted 5 lines · On Samstag, 27. November 2010 Francois Romieu wrote:

Michael Monnerie <[email protected]> :

Quoted 1 line

This is the 3rd time I send this, and I did not get any answer.

What about changing your mx blacklisting policy or checking the mailing-list archive (http://marc.info/?t=128950098300003) ?

We've solved that in PM now.

Quoted 1 line

Is it in v2.6.37-rc2.

Thanks, I'll try and report back then.

Signature · 11 lines
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
// 
// Haus zu verkaufen: http://zmi.at/langegg/