[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Badness at arch/parisc/kernel/smp.c:323



On Thu, May 14, 2009 at 3:42 PM, Bernd Gietzelt <berndg@fsim-ev.de> wrote:
> Hello,
>
> i am a newbie with debian-hppa. I installed debian-hppa on 3 servers without problems but the last one do some strange things.
>
> Can someone give me a hint where I should start?
>
> [17179578.028000] Badness at arch/parisc/kernel/smp.c:323
[...]
> [17179579.708000]  IAOQ[0]: smp_call_function+0x5c/0x348
> [17179579.724000]  IAOQ[1]: smp_call_function+0x60/0x348
> [17179579.728000]  RP(r2): smp_call_function+0x4c/0x348
> [17179579.732000] Backtrace:
> [17179579.736000]  [<00000000401545c0>] on_each_cpu+0x28/0x68
> [17179579.972000]  [<0000000040119fc0>] flush_data_cache+0x28/0x38
> [17179579.992000]  [<0000000040119278>] free_initmem+0x68/0x2d0
> [17179579.996000]  [<00000000401187e0>] init_post+0x18/0x1a8
> [17179580.000000]  [<00000000405dca1c>] kernel_init+0x444/0x478
> [17179580.252000]

This is harmless.

> a few lines later:
>
> [17179584.524000] tulip 0000:18:00.0: enabling device (0000 -> 0003)
> [17179584.524000] tulip 0000:18:00.0: enabling SERR and PARITY (0003 -> 0143)
>
> ************* SYSTEM ALERT **************
> DATE: 05/14/2009 TIME: 11:42:31
> ALERT LEVEL: 7 = reserved
>
> REASON FOR ALERT
> SOURCE: 0 = unknown, no source stated
> SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: FF
> PROBLEM DETAIL: 0 = no problem detail
>
> LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
>       ON       FLASH         OFF       ON         ON
> LED State: There was a system interruption that did not take the system down.
> Check Chassis and Console Logs for error messages.
>
> then follow a console and boot device reset. Then nothing more happens... nothing...

I've seen that too. Do you have any add-on PCI network card in that
box? It seems that the current debian kernel has bugs with some
network drivers. Loading tg3 or tulip drivers with such network cards
in the PCI slots will trigger a High Priority Machine Check (what you
saw here). If you don't want to bother too much, I'd suggest
installing etch and then upgrading to lenny, sticking to the etch
kernel until you can build your own kernel.

HTH

-- 
Thibaut VARENE
http://www.parisc-linux.org/~varenet/


Reply to: