Summary: | 2006.1 64Bit Live CD kernel 2.6.17-gentoo-r7 bug | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | chad heuschober <chad_ryan1> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED CANTFIX | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
System specs
Dump from error1 |
Description
chad heuschober
2007-02-03 21:54:48 UTC
Created attachment 109047 [details]
System specs
Created attachment 109048 [details]
Dump from error1
I wanted to add an update. Until recently 'nix has been my only possible testing platform. And both memtest86 and cpuburn have worked without error -- (cpu burn run in knoppix5.1.1 -- kernel 2.6.19) Today I found time enough to pull an old pata drive out (circa 1997) and put XP on it with hopes of comparing stability woes (and whether or not this really /is/ a hardware problem). Unfortunately this isn't ideal for comparative testing because it is a different drive on a different bus (IDE) on a different arch (32-bit) but I am desperate for leads and will later try 32bit gentoo on the same drive. The results? Installation proceeded without a problem. Upgrade to Service Pack 2 driver an d cd burning software also without failure. Bios on my mb was 3 subversions behind and the board lacks a floppy header so a windows installation is necessary for a BIOS upgrade. This failed on an error that it couldn't 'map main memory'. I tried superpi -- the first few small iterations were fine but when I started with a medium sized iteration I received a failure. This failure then seemed to affect subsequent iterations of superpi regardless of calculation size. Runs that completed successfully before now failed. That said this /seems/ more like a hardware issue and something I shouldn't trouble you with but the replaced hardware list says otherwise as does the stability of cpuburn in knoppix over a 48 hour period. Any help is appreciated. Sorry, I don't have any ideas. As you have observed, this doesn't really make any sense but does smell like a hardware problem. If you do decide this is a Linux kernel issue, then the next step would be to figure out how you can boot the latest development kernel (currently 2.6.20) on this system, then post a complete report of the first few oops's to the Linux kernel mailing list. Someone should be able to assess whether they are bogus (i.e. hardware is screwed) or not. |