Re: HPPA hang with PCI SERR or PARITY enabling

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

 



On Mon, 10 Aug 2009 10:01:32 +0200
Thibaut VARENE <T-Bone@xxxxxxxxxxxxxxxx> wrote:

> On Mon, Aug 10, 2009 at 3:22 AM, Randolph Chung<randolph@xxxxxxxxx>
> wrote:
> >>
> >>> [    7.988000] Freeing unused kernel memory: <0>------------[ cut
> >>> here ]------------
> >>> [    8.096000] Badness at
> >>> /build/buildd/linux-2.6-2.6.30/debian/build/source_hppa_none/kernel/smp.c:369
> >>> [    8.104000] [    8.104000]
> >>>  YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI [    8.108000] PSW:
> >>> 00001000000001100000000000001110 Not tainted [    8.116000]
> >>> r00-03  000000000806000e 0000000040686fa0 0000000040182c6c
> >>> 000000004058d020 [    8.120000] r04-07  0000000040668fa0
> >>> 000000004065e7c0 00000000404f7db0 000000r08-11  0000000040686fa0
> >>> 000000004065e7c0 0000000000000000 00000000406797a0
> >>> [    8.644000] r12-15  0000000000000001 0000000000000001
> >>> 0000000000000000 0000000000000001
> >>> [    8.776000] r16-19  00000000f00003b0 0000000040686fa0
> >>> 000000012f87cb40 00000000406d6000
> >>> [    8.784000] r20-23  0000000000000000 00000000406d6000
> >>> ffffffffffffffff 0000000000000001
> >>> [    8.788000] r24-27  0000000000000000 000000004065e7c0
> >>> 00000000404f7db0 0000000040668fa0
> >>> [    8.796000] r28-31  0000000000000000 000000012f880490
> >>> 000000012f880580 0000000000000000
> >>> [    8sr00-03  0000000000000000 0000000000000000 0000000000000000
> >>> 0000000000000000
> >>> [    9.208000] sr04-07  0000000000000000 0000000000000000
> >>> 0000000000000000 0000000000000000
> >>> [    9.340000] [    9.340000] IASQ: 0000000000000000
> >>> 0000000000000000 IAOQ: 00000000401829b4 00000000401829b8
> >>> [    9.348000]  IIR: 03ffe01f    ISR: 0000000010240000  IOR:
> >>> 0000000179de7d0c
> >>> [    9.356000]  CPU:        0   CR30: 000000012f880000 CR31:
> >>> 0000000000008020
> >>> [    9.360000]  ORIG_R28: 000000000800000e
> >>> [    9.364000]  mp_call_function_many+0x7c/0x2f8
> >>> [    9.768000]  IAOQ[1]: smp_call_function_many+0x80/0x2f8
> >>> [    9.796000]  RP(r2): smp_call_function+0x3c/0x50
> >>> [    9.800000] Backtrace:
> >>> [    9.804000] Backtrace:
> >>> [    9.804000]  [<0000000040115fe8>] printk+0x40/0x50
> >>> [    9.804000]  [<0000000040152760>] print_tainted+0xc0/0xe0
> >>> [    9.804000]  [<0000000040104084>] intr_check_sig+0x0/0x38
> >>> [    9.804000]  [<0000000040104074>] intr_return+0x0/0x4
> >>> [    9.804000]  [<0000000040182c6c>] smp_call_function+0x3c/0x50
> >>> [    9.804000]  [<0000000040159d08>] on_each_cpu+0x28/0x68
> >>> [    9.804000]  [<000000004011b92c>] free_initmem+0x94/0x340
> >
> > Is there another error message further on? 

No. Nothing. After that point the system give no further messages.
Someone noted it looks like a deadlock.

> For the sake of reliability I've put a (temporary) static copy of the

Thank you for that.

> FWIW, the above dump is not the final message, from what can be seen
> of the other dumps. As a matter of fact, it happens way before the
> actual crash, which is triggered by loading drivers (SYM, afaict).
> Output is garbled by GSP, and it seems to me that the dump with
> pdcchassis=0 is truncated. Could the author post a full dump of the
> boot log with pdcchassis=0 please? (and maybe use pastebin? ;-)

http://www.pateam.org/archive/tmp/serrparitylogs.html#kernel_2.6.30-1-parisc64-smp
is a full dump of the boot log.

I've blacklisted the tulip kernel module but this doesn't change the
behavior. I'll try a custom kernel without all these driver.

cheers,
bernd

-- 
Bernd Gietzelt <berndg@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux