> Supermicro S2DGE motherboard
> 2 - 400 mhz PII Xeons w/ 512k cache
> 256 megs PC-100 ram
> Gulliemot Maxi Xentor Gamer 32 (agp, TNT2 Ultra chipset w/ 32 megs ram)
> 13 gig Maxtor IDE hard disk
> Ricoh 4x4x24 IDE CD-RW
> Creative Labs 6x IDE DVD player
> 10 megabit combo card (linux recognizes it as a NE2000 PCI card)
> Sound Blaster live value
>
> I am running Mandrake 6.1 with full (ie everything) installation. I am
> using this computer to run Jaguar, a ab initio computational chemistry
> program. First of all, is Mandrake 6.1 a good distribution of linux for
> me to use ( I also have RH6.0) and do I have to modify it in any way to
> make it more stable with the two processors (i.e. recompile the kernel,
> upgrade etc.).
> I received the following error message on the console when I was running
> several Jaguar jobs at once, after which the computer froze:
I use mandrake myself, I noticed that they compile there kernel with gcc
2.95 and pentium compiler optimisations. This is know to cause problems so
to be clear is this with a Mandrake kernel or a home grown kernel? Can you
try recompiling the kernel with gcc 2.7.2
> [navindra@onyx test]$ Scheduling in interrupt
> Unable to handle kernel NULL pointer derefernce at virtual address
> 00000000
> current -> tss.cr3 = 0dfba000, %cr3 = 0dfba000
> *pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[<80114329>]
> EFLAGS: 00010092
> eax: 00000018 ebx: 8df92000 ecx: 0000004a edx: 00000002
> esi: 8df9200 edi: 802626a0 ebp: 8df93fbc esp: 8df93f8c
> ds: 0018 es: 0018 ss: 0018
> Process rwr (pid: 4168, process nr: 29, stackpage = 8df93000)
> Stack: 00000000 8df93fbc 8df92000 0a115d10 00000015
> 8df93fc4 00000000 8df93fc4
> 0a27de38 8010ccd2 00000000 80249c00
> 00000003 80109bc5 00000078 00000001
> 00000001 0a115d10 00000015 00000003
> 00001b4a 8010002b 0000002b ffffffff
> Call Trace: [<8010ccd2>] [<80109bc5>] [<8010002b7>]
> Code: c7 05 00 00 00 00 00 00 00 00
> 8d 65 d8 56 5e 5f 89 ec 5d c3
> Aiee, killing interupt handler
Can you take a look at /usr/src/linux/Documentation/oops-tracing.txt and
do a trace on the oops as discribed in there.
> I have had numerous lockups and reboots while running several jaguar
> jobs at once, but this is the 1st time i have had a message appear on
> the console. The lockups/reboots occur randomly, somtimes within a
> matter of minutes, and at other times, it takes hours. I have not had
> any problems with running a non-smp kernel. I have also experienced a
> lockup when compiling a kernel with "make= make -j " in the Makefile.
>
> I would really appreciate it if someone could help me understand what is
> wrong in my computer.
Can you check the temperature in there (either with lm_sensors or the old
fastioned way), random reboots are often CPU problems either overheating
or manufacturing flaws. If you can swap out memory, cpu, disk, etc and see
if you still get crashes.
--
Tim Fletcher .~.
/V\ L I N U X
[EMAIL PROTECTED] // \ >Don't fear the penguin<
[EMAIL PROTECTED] /( )\
^^-^^
Who needs a life when there's linux?
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
