On Tuesday 25 October 2005 02:58 pm, Lee Revell wrote:
> You need to reproduce this with an untainted kernel AKA without nvidia
> loaded.

My apologies. To retest, I ensured that no modules at all were dynamically 
linked. I also took the liberty of rebuilding the kernel on another system, 
then transferring it over (thankfully I was successful). In the rebuilt 
kernel, I enabled ReiserFS debugging, Magic SysRq, and a serial console (I 
also bought a NULL modem cable).

> You left out the most important part of the Oops, the stack trace.  It
> should have been printed immediately after the registers.

Actually, the Oops didn't contain a stack trace either time I produced the bug 
on my existing 2.6.13! Subsequent attempts to reproduce the problem on that 
production kernel resulted in a freeze.

I've attached the following files:

* boot-dmesg.txt
dmesg right after booting my newly built 2.6.13 debug kernel.
* config-debug.txt
.config from the debug kernel
* cpuinfo.txt
contents of /proc/cpuinfo
* lspci.txt
Output of lspci -vvv, in case anyone finds it relevant.
* emerge.txt
Serial console capture of me running "emerge traceroute" to cause the bug, 
along with some logs of ReiserFS sweating.
* crash.txt
ReiserFS's panic, followed by the full traces produced by the kernel.

Just a few more points about my problem... 

#1 - I've never seen any of the disks in this raid10 (md1 mounted on /) 
produce any CRC errors (though correct me if I'm wrong, I don't see any 
reason the kernel should BUG()/oops/panic because of corrupted filesystems)
#2 - This ReiserFS partition is literally days old.
#3 - When I had strange stability issues before, I had been using 2.6.13 for 
some time successfully. Stability went from perfect to nonexistent.
#4 - I successfully ran a CPU burn in program I don't have source for. I've 
also run memtest86 extensively, replaced the motherboard, power supply and 
GPU. I no longer believe this to be a hardware issue.
#5 - I disabled all swap partitions to eliminate that as a variable.

Thanks a bunch for any ideas. If anyone needs more information from me, I'm 
willing and able to produce whatever is asked for to help debug this.

Thanks,
Chase Venters