I did run a memtest and after 1 pass I received 0 errors. Should I run it longer than one pass?
Jon On 12/13/06, Adam Talbot <[EMAIL PROTECTED]> wrote: > Point filo to boot off of memtest. I would look at memory. Just an > idea, and its an easy test. > -Adam > > > Jon Dufresne wrote: > > Thanks, Uwe. > > > > I used the 82801dbm as a starting ground. I've already had to change a > > few things such as device IDs. > > > > I know something somewhere isn't right because I get a kernel panic > > anytime I modprobe a kernel module that relates to a device in the > > southbridge. Since I'm responding I'll post the kernel panic in case > > someone has an idea. This example is trying to bring up the sound > > device. If I remove all module loading during init, I can get to a > > single user prompt. > > > > Anyway thanks for the tip. > > > > Unable to handle kernel paging request at virtual address 019b2005 > > printing eip: > > *pde = 00000000 > > Oops: 0000 [#1] > > Modules linked in: snd_intel8x0 snd_ac97_codec snd_pcm_oss > > snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart > > snd_rawmidi snd_seq_device snd soundcore floppy ext3 jbd > > CPU: 0 > > EIP: 0060:[<c0129fe0>] Not tainted VLI > > EFLAGS: 00010202 (2.6.9-42.EL) > > EIP is at __request_resource+0x24/0x41 > > eax: 019b2001 ebx: c1ab0460 ecx: c036849c edx: c0004014 > > esi: f02021ff edi: f0202000 ebp: f0202000 esp: c1a1de80 > > ds: 007b es: 007b ss: 0068 > > Process modprobe (pid: 1186, threadinfo=c1a1d000 task=c1a2c170) > > Stack: c1ab0460 c036849c c1ab047c c012a27c dff4c800 00000200 000001ff > > 00000002 > > dff4c800 c1a7dc24 c01f02a0 c1a7dc24 00000002 c1a7dc24 dff4c800 > > f885d270 > > c01f033c c1a7dc00 dfce2400 dff4c800 f8858c73 00000001 c1a7dc00 > > c1a7dc00 > > Call Trace: > > [<c012a27c>] __request_region+0x52/0x74 > > [<c01f02a0>] pci_request_region+0x82/0xf2 > > [<c01f033c>] pci_request_regions+0x14/0x37 > > [<f8858c73>] snd_intel8x0_create+0x104/0x403 [snd_intel8x0] > > [<f885903c>] snd_intel8x0_probe+0xca/0x21a [snd_intel8x0] > > [<c01f1b09>] pci_device_probe_static+0x2a/0x3d > > [<c01f1b37>] __pci_device_probe+0x1b/0x2c > > [<c01f1b63>] pci_device_probe+0x1b/0x2d > > [<c0252157>] bus_match+0x27/0x45 > > [<c0252220>] driver_attach+0x37/0x66 > > [<c02525d5>] bus_add_driver+0x77/0x97 > > [<c02529f0>] driver_register+0x51/0x58 > > [<c01f1d21>] pci_register_driver+0x85/0xa1 > > [<f881400a>] alsa_card_intel8x0_init+0xa/0x39 [snd_intel8x0] > > [<c01410b6>] sys_init_module+0xe9/0x1d0 > > [<c0318d93>] syscall_call+0x7/0xb > > Code: 84 36 c0 5b 89 d0 c3 57 89 c1 56 53 8b 7a 04 89 d3 8b 72 08 39 > > fe 72 2c 3b 79 04 72 27 3b 71 08 77 22 8d 51 18 8b 02 85 c0 74 05 <39> > > 70 04 76 0c 89 43 14 31 c0 89 1a 89 4b 10 eb 08 39 78 08 > > <0>Fatal exception: panic in 5 seconds > > Kernel panic - not syncing: Fatal exception > > > > > > Thanks for the tip. > > > > On 12/13/06, Uwe Hermann <[EMAIL PROTECTED]> wrote: > > > >> Hi Jon, > >> > >> you noted that you work on the Intel 82801DB: > >> http://linuxbios.org/index.php?title=Supported_Chipsets_and_Devices&curid=1002&diff=3747&oldid=3739&rcid=1296 > >> > >> Please have a look at the 82801DBM code before, that's at the very least > >> very similar, maybe it even already supports the 82801DB, too(?) > >> > >> > >> Uwe. > >> -- > >> http://www.hermann-uwe.de | http://www.holsham-traders.de > >> http://www.crazy-hacks.org | http://www.unmaintained-free-software.org > >> > >> > >> -----BEGIN PGP SIGNATURE----- > >> Version: GnuPG v1.4.6 (GNU/Linux) > >> > >> iD8DBQFFgD4CXdVoV3jWIbQRAk0KAJ9J8VboHY4II7umgiNPmS1TIVDynQCfT+sh > >> IcESivY9FsYMzj1HaUQdhP4= > >> =JSxz > >> -----END PGP SIGNATURE----- > >> > >> > >> > >> > > > > > > > -- > linuxbios mailing list > [email protected] > http://www.openbios.org/mailman/listinfo/linuxbios > -- linuxbios mailing list [email protected] http://www.openbios.org/mailman/listinfo/linuxbios
