2010-11-18 14:49:15

by Michael Monnerie

[permalink] [raw]
Subject: Regression 2.6.36 - driver rtl8169 crashes kernel, triggered by user app

I did not get any answer, so here again:

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. :-)

--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

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

****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/


Attachments:
signature.asc (198.00 B)
This is a digitally signed message part.

2010-11-20 00:45:32

by Francois Romieu

[permalink] [raw]
Subject: Re: Regression 2.6.36 - driver rtl8169 crashes kernel, triggered by user app

Michael Monnerie <[email protected]> :
> I did not get any answer, so here again:

I already answered one week ago, you were Cc:ed and I had my
answer delivered through vger. Please check your spambox.

Can you test again after reverting 801e147cde02f04b5c2f42764cd43a89fc7400a2 ?

--
Ueimor