Re: new machine: what's wrong?
Many thanks to those replied. Just found where the problem was: plugging another P133 Mem calms everything down. Yeah, It's a memory problem. thanks again, jack
Re: new machine: what's wrong?
Thanks for the reply! However, I've already tried that with no luck. The installation (boot from cd) of Debian and Redhat 7.0 failed with same kind of error message. BTW, my old machine is not so old indeed, PII 400. On Mon, Oct 23, 2000 at 10:39:21PM -0500, Andrei Ivanov wrote: Thats most likely because you are booting a system that was build on your old box...different hardware, totally. I've had something like that happen to me when I booted a kernel from old system into new one (different architectures, 486-Pentium). System booted, but behaved very badly. Same story with Windows. I'd try to do a clean install somewhere on a partition you dont need. Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354
Re: new machine: what's wrong?
On Mon, Oct 23, 2000 at 11:41:10PM -0400, Jack wrote: Frustrated with my new machine. It's a self-assembled machine and it's the first one I've made. (PIII, PC133, 128M mem) Tried to boot from the my old hard-disk, which has Win98, Win2k, Debian installed on it. Win98 could be booted into DOS mode just fine. Win98 itself (even safe mode) and Win2k crashed when boot. Debian failed either. Here's error message I got from linux: -- Calibrating delay loop ... 1468.01 BogoMIPS Memory 127064K/131008K available (1016k Kernel code, 416K reserved, 1680k data, 60k init, OK bigmem) Dentry hash table entries: 262144(order 9, 2048k) Buffer cache hash table entries: 131072(order 7, 512k) Page cache hash table entries: 32768(order 5, 128k) Unable to handle kernel paging request at virtual address 87fe15a8 current-tss.cr3 = 00101000, %cr3 = 00101000 *pde = Oops: CPU: 0 EIP: 0010[c011edb0] EFLAGS: 00010283 eax: ebx:87fe1560 ecxc024cc84 edx c01d57c0 esi:c01d20d7 edi:c01d57c1 ebpc7f317a0 esp: c0229f90 ds 0018 es 0018 ss:0018 Process swapper(pid:0, processs nr:0, stackpage: c0229000) stack: .. .. (numbers) Call Trace: [6106000] [c01d57c0] [c0106000] [c0100175] Code: 8b 73 48 8b 7c 24 38 fc ac ae 75 08 84 c0 75 88 31 c0 eb 04 Kernel panic: Attempted to kill the idle task! In swapper task - not syncing -- [...] ps. the memory works fine on my old machine, although the old motherboard only supports pc100. But your memory does support PC133? Maybe it just claims to support it. Don't laugh - the german Computer magazine c't tested a bunch of RAMs to check if the SPD was programmed correctly. On http://www.heise.de/ct/ftp/ctspd.shtml they got a nice tool to check your's. Of course it's in german but if you want to I would be able to translate the important stuff. This is not a commom memory test, but a test to see if the SPD is programmed according to the Specs. You could try to borrow some other memory (PC133!) and see if it does make any change. You could also try to boot a Floppy-Linuy like http://sunsite.dk/mulinux/ http://www.toms.net/rb/ and see if they boot with your hardware. If all that doesn't help then I guess you have to check every single piece of hardware and replace it for testing. HTH, Phil
Re: new machine: what's wrong?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 23, 2000 at 11:41:10PM -0400, Jack wrote: Buffer cache hash table entries: 131072(order 7, 512k) Page cache hash table entries: 32768(order 5, 128k) Unable to handle kernel paging request at virtual address 87fe15a8 current-tss.cr3 = 00101000, %cr3 = 00101000 *pde = Oops: CPU: 0 EIP: 0010[c011edb0] EFLAGS: 00010283 eax: ebx:87fe1560 ecxc024cc84 edx c01d57c0 esi:c01d20d7 edi:c01d57c1 ebpc7f317a0 esp: c0229f90 ds 0018 es 0018 ss:0018 Process swapper(pid:0, processs nr:0, stackpage: c0229000) stack: .. .. (numbers) Call Trace: [6106000] [c01d57c0] [c0106000] [c0100175] Code: 8b 73 48 8b 7c 24 38 fc ac ae 75 08 84 c0 75 88 31 c0 eb 04 Kernel panic: Attempted to kill the idle task! In swapper task - not syncing Looks like a memory problem. Try getting the memtest86 package. It is packaged in Debian, but it's not actually a Linux app. You copy it to a floppy and boot with the floppy. Memtest hammers hard on the ram for a while, doing a series of checks designed to cause problems with the RAM to become apparent. I've also seen problems like this with bad motherboards. If possible, try swapping out different hardware components (i.e. try a different video board, etc). Good luck. noah - -- ___ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE59g2hYrVLjBFATsMRAuLnAJ9Xhn6G14/zqJ+zyFI3+QmPIScMPgCfZL2q jybuyChz+DYhFMRQ5ZyCovU= =jcAi -END PGP SIGNATURE-
new machine: what's wrong?
Hi, Frustrated with my new machine. It's a self-assembled machine and it's the first one I've made. (PIII, PC133, 128M mem) Tried to boot from the my old hard-disk, which has Win98, Win2k, Debian installed on it. Win98 could be booted into DOS mode just fine. Win98 itself (even safe mode) and Win2k crashed when boot. Debian failed either. Here's error message I got from linux: -- Calibrating delay loop ... 1468.01 BogoMIPS Memory 127064K/131008K available (1016k Kernel code, 416K reserved, 1680k data, 60k init, OK bigmem) Dentry hash table entries: 262144(order 9, 2048k) Buffer cache hash table entries: 131072(order 7, 512k) Page cache hash table entries: 32768(order 5, 128k) Unable to handle kernel paging request at virtual address 87fe15a8 current-tss.cr3 = 00101000, %cr3 = 00101000 *pde = Oops: CPU: 0 EIP: 0010[c011edb0] EFLAGS: 00010283 eax: ebx:87fe1560 ecxc024cc84 edx c01d57c0 esi:c01d20d7 edi:c01d57c1 ebpc7f317a0 esp: c0229f90 ds 0018 es 0018 ss:0018 Process swapper(pid:0, processs nr:0, stackpage: c0229000) stack: .. .. (numbers) Call Trace: [6106000] [c01d57c0] [c0106000] [c0100175] Code: 8b 73 48 8b 7c 24 38 fc ac ae 75 08 84 c0 75 88 31 c0 eb 04 Kernel panic: Attempted to kill the idle task! In swapper task - not syncing -- Please help with no-clues: does it look like a CPU failure, Mem failure, bad configured CMOS, wrong jumpers on Motherboard? Any comments will be very much appreciated! could provide all model names of hardware if someone is interested in this case. thanks for reading. Jack ps. the memory works fine on my old machine, although the old motherboard only supports pc100.
Re: new machine: what's wrong?
Thats most likely because you are booting a system that was build on your old box...different hardware, totally. I've had something like that happen to me when I booted a kernel from old system into new one (different architectures, 486-Pentium). System booted, but behaved very badly. Same story with Windows. I'd try to do a clean install somewhere on a partition you dont need. Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354 --
