Re: POSSIBLE SMP KERNEL BUG ?

From: Adam (adam@eax.com)
Date: Mon Apr 03 2000 - 23:21:38 EST


Well, I run 2.3.50 on Abit BP6 with two Celerons and it had been fairly
stable for me. .. So I doubt it is "smp bug" as title imples.

Some datapoints.
        - It looks for me kind of like overheading cpu. Thus
                - make sure you are not overclocking anything
                - make sure you got decent fans and working fan on each cpu.
                - consider using silcon pasta.
                - check temperature of each cpu in bios, should be 40'C or
                  less (over 50 everything usually goes to hell)
        - if you want to use ATA/66 you need support for it.
          Kernels 2.3.x have it. I think 2.3.50 is a good example here.
          Some 2.2.x kerneles *might* have it, but I'm not sure which
          The one shipped with redhat 6.1 for sure does not have it.
        - for us to help you best you need to run the ops thru 'ksymops'
          script. it is in /usr/src/linux/kernel/scripts/ksymops
        - for easier catching of panic msg you might want to consider
          using serial console to catch all output (see
          linux/Documentation/serial-console.txt)
        - you might want to checkout following web sites:
                linux-abit@listserv.geek.net/">http://www.mail-archive.com/linux-abit@listserv.geek.net/
                http://www.gentus.com/
                http://www.bp6.com/
        
> I'm in the process of trying to setup a rackmount server to host my new
> linux website on. I'm having (pardon my language) a sh*tload of problems.
> Namely, anytime I try and use a SMP enabled kernel I get a kernel panic. I
> can't figure out the problem. I've tried 2.2.14, 2.3.99-pre3,
> 2.2.12-20smp(rpm), getting the same error with different numbers. I don't
> know if this is a hardware problem or a software problem(Kernel bug maybe?).
> Nobody has been able to help me at all, and I've been re-compiling,
> re-installing, and re-configuring for roughly 20 hours over about 3 or 4
> days. Nothing seems to work. I _had_ it working with 2.2.14 for about 5
> minutes (I saw both cpu's in /proc/cpuinfo), but when I rebooted again I got
> the same kernel panic error.
>
> 95% of the hardware on this system is brand
> new with the exception of the video card which is an old one I had in a
> drawer and I used it because I don't want to ship off one of my good vid
> cards with the server. (I doubt it would be causing the problem.
>
> I've been using Linux for almost 2 years but I am still learning,
> and this is my first attempt at a SMP system. Maybe you guys(and gals)
> can help, or send me in the right direction.
>
> Thank you for taking the time to read this e-mail, hopefully you might have
> a better grasp at the problem than I do.
>
> Sincerely,
>
> J. Buset
>
>
>
> The System:
>
> Abit BP6 Motherboard (new, w/ factory bios)
> -all power managment in bios turned off, as was mentioned in the
> SMP-HOWTO
> 2 Celeron 500mhz ppga CPUs (new)
> Maxtor DiamondMax Plus 40 - 30gb hard disk (new)
> Trident 1mb video card
> 128MB of PC100 Ram (new)
> 3COM 3c905b NIC (new)
> Rackmount 2U ATX chassis
>
>
> Here is a copy of the error I recieved with a Stock RedHat 6.1 "Server
> Install" booting with 2.2.12-20smp RPM kernel right after install. I hope I
> didn't make any copying errors, I had to type it on a different computer:
>
>
> Welcome to RedHat Linux
> Press 'I' to enter interactive startup
> Mounting proc filesystem [ OK ]
> Oops: 0002
> CPU: 1
> EIP: 0010:[<c0107a6d>]
> EFLAGS: 00010246
> eax: 00000000 ebx: c40ea000 ecx: c40ea000 edx: c0212b00
> esi: c40ea000 edi: c0264d00 ebp: 00000000 esp: c40ebfb8
> ds: 0018 es: 0018 ss: 0018
> Process swapper (pid: 0, process nr:1, stackpage=c40eb000)
> Stack: 00000000 c023e00c 00000000 00001100 00000000 c023dff4 c0239f70
> 00000001
> 00000001 00000000 c0110018 c0230018 00000078 c0107cd6 00000010
> 00000206
> ffffffff 00000001
> Call Trace: [<c0110010>] [<c0107cd6>]
> Code: 00 75 01 f4 83 7b 14 00 74 dd e8 f8 ad 00 00 e8 23 54 01 00
> Kernel Panic: Attempted to kill the idle task!
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:11 EST