Re: mm kernel oops with r8169 & named, PREEMPT

On Wed, 13 Oct 2004 22:54:33 +0200, Francois Romieu wrote:

[snip]
Possible :o)

OTOH, I do not want to miss an error report.

Well the options I tried disabling (ACPI, PREEMPT) didn't stop the oops.

[snip]
I am not a reiserfs addict but you can imho go for the complete serie
of reiserfs patches once you have sucked the first one (3Mo, yuck).

If you have issues with the ordering of the patches, just grep the
patches in the 'series' file.

Ok thanks, I have work to do right now so I'll have to try this out tonight.

I wasn't able to get the kernel to compile with just the reiser4
patches from the broken-out dir on the ftp.  The patching itself
seemed to go well though.  I tried to apply the patches in the order
they were listed in "series" but some had to go out of order anyway,
such as reiser4-only.patch had to go first.

However I was able to verify it's not a problem with the r8169 driver.
 I copied over the r8169 driver to a fresh linux-2.6.8.1-mm4 and was
able to compile and run fine with the latest r8169 driver from the
linux-2.6.9-rc4-mm1 release.  I also tested it in reverse, bringing
over r8169.c to a fresh linux-2.6.9-rc4-mm1 and it still gave me the
oops.

I'm not sure where this leaves me now.  Perhaps I should repost my
oops and my proc info in the lkml with a different subject to draw the
attention of others, since I now know this subject to be entirely
missleading.

Danny [off-list ref] :
[...]

I'm not sure where this leaves me now.  Perhaps I should repost my
oops and my proc info in the lkml with a different subject to draw the
attention of others, since I now know this subject to be entirely
missleading.

May be try this one first:

http://www.uwsg.indiana.edu/hypermail/linux/kernel/0410.1/1920.html

--
Ueimor

On Fri, 15 Oct 2004 18:18:18 +0200, Francois Romieu wrote:

May be try this one first:

http://www.uwsg.indiana.edu/hypermail/linux/kernel/0410.1/1920.html

Thanks, that appears to have fixed it.  I'm not getting an oops any
more.  I wish I hadn't assumed so much in my subject line, perhaps
someone would have found the solution before John Flinchbaugh even
reported his problem.

Also posting the oops directly instead of linking to it probably
allows people passing by to look at the oops, increasing the total
number of eyes.

I have a quick question though, if I'm using the kernel with all the
debug features turned on, should I still run it through ksymoops?

Danny [off-list ref] :
[profile path bug hits hard]

Also posting the oops directly instead of linking to it probably
allows people passing by to look at the oops, increasing the total
number of eyes.

Yes.

Oops posting is still on-topic in l-k.

I have a quick question though, if I'm using the kernel with all the
debug features turned on, should I still run it through ksymoops?

Your file named "oops-raw" contained the relevant information.

--
Ueimor

Thanks for your help.  Live and learn. :)