From: Thibaut VARENE <T-Bone@parisc-linux.org>
To: Randolph Chung <randolph@tausq.org>
Cc: Bernd Gietzelt <berndg@fsim-ev.de>,
Grant Grundler <grundler@parisc-linux.org>,
linux-parisc@vger.kernel.org
Subject: Re: HPPA hang with PCI SERR or PARITY enabling
Date: Mon, 10 Aug 2009 10:09:36 +0200 [thread overview]
Message-ID: <7d01f9f00908100109y6265c3efs31a6a2c46679ae90@mail.gmail.com> (raw)
In-Reply-To: <7d01f9f00908100101w3d73e91fmce80eb79e85bdc61@mail.gmail.com>
On Mon, Aug 10, 2009 at 10:01 AM, Thibaut VARENE<T-Bone@parisc-linux.or=
g> wrote:
> On Mon, Aug 10, 2009 at 3:22 AM, Randolph Chung<randolph@tausq.org> w=
rote:
>>>
>>>> [ =C2=A0 =C2=A07.988000] Freeing unused kernel memory: <0>--------=
----[ cut here
>>>> ]------------
>>>> [ =C2=A0 =C2=A08.096000] Badness at
>>>> /build/buildd/linux-2.6-2.6.30/debian/build/source_hppa_none/kerne=
l/smp.c:369
>>>> [ =C2=A0 =C2=A08.104000] [ =C2=A0 =C2=A08.104000] =C2=A0 =C2=A0 =C2=
=A0YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
>>>> [ =C2=A0 =C2=A08.108000] PSW: 00001000000001100000000000001110 Not=
tainted
>>>> [ =C2=A0 =C2=A08.116000] r00-03 =C2=A0000000000806000e 00000000406=
86fa0 0000000040182c6c
>>>> 000000004058d020
>>>> [ =C2=A0 =C2=A08.120000] r04-07 =C2=A00000000040668fa0 00000000406=
5e7c0 00000000404f7db0
>>>> 000000r08-11 =C2=A00000000040686fa0 000000004065e7c0 0000000000000=
000
>>>> 00000000406797a0
>>>> [ =C2=A0 =C2=A08.644000] r12-15 =C2=A00000000000000001 00000000000=
00001 0000000000000000
>>>> 0000000000000001
>>>> [ =C2=A0 =C2=A08.776000] r16-19 =C2=A000000000f00003b0 00000000406=
86fa0 000000012f87cb40
>>>> 00000000406d6000
>>>> [ =C2=A0 =C2=A08.784000] r20-23 =C2=A00000000000000000 00000000406=
d6000 ffffffffffffffff
>>>> 0000000000000001
>>>> [ =C2=A0 =C2=A08.788000] r24-27 =C2=A00000000000000000 00000000406=
5e7c0 00000000404f7db0
>>>> 0000000040668fa0
>>>> [ =C2=A0 =C2=A08.796000] r28-31 =C2=A00000000000000000 000000012f8=
80490 000000012f880580
>>>> 0000000000000000
>>>> [ =C2=A0 =C2=A08sr00-03 =C2=A00000000000000000 0000000000000000 00=
00000000000000
>>>> 0000000000000000
>>>> [ =C2=A0 =C2=A09.208000] sr04-07 =C2=A00000000000000000 0000000000=
000000
>>>> 0000000000000000 0000000000000000
>>>> [ =C2=A0 =C2=A09.340000] [ =C2=A0 =C2=A09.340000] IASQ: 0000000000=
000000 0000000000000000
>>>> IAOQ: 00000000401829b4 00000000401829b8
>>>> [ =C2=A0 =C2=A09.348000] =C2=A0IIR: 03ffe01f =C2=A0 =C2=A0ISR: 000=
0000010240000 =C2=A0IOR:
>>>> 0000000179de7d0c
>>>> [ =C2=A0 =C2=A09.356000] =C2=A0CPU: =C2=A0 =C2=A0 =C2=A0 =C2=A00 =C2=
=A0 CR30: 000000012f880000 CR31:
>>>> 0000000000008020
>>>> [ =C2=A0 =C2=A09.360000] =C2=A0ORIG_R28: 000000000800000e
>>>> [ =C2=A0 =C2=A09.364000] =C2=A0mp_call_function_many+0x7c/0x2f8
>>>> [ =C2=A0 =C2=A09.768000] =C2=A0IAOQ[1]: smp_call_function_many+0x8=
0/0x2f8
>>>> [ =C2=A0 =C2=A09.796000] =C2=A0RP(r2): smp_call_function+0x3c/0x50
>>>> [ =C2=A0 =C2=A09.800000] Backtrace:
>>>> [ =C2=A0 =C2=A09.804000] Backtrace:
>>>> [ =C2=A0 =C2=A09.804000] =C2=A0[<0000000040115fe8>] printk+0x40/0x=
50
>>>> [ =C2=A0 =C2=A09.804000] =C2=A0[<0000000040152760>] print_tainted+=
0xc0/0xe0
>>>> [ =C2=A0 =C2=A09.804000] =C2=A0[<0000000040104084>] intr_check_sig=
+0x0/0x38
>>>> [ =C2=A0 =C2=A09.804000] =C2=A0[<0000000040104074>] intr_return+0x=
0/0x4
>>>> [ =C2=A0 =C2=A09.804000] =C2=A0[<0000000040182c6c>] smp_call_funct=
ion+0x3c/0x50
>>>> [ =C2=A0 =C2=A09.804000] =C2=A0[<0000000040159d08>] on_each_cpu+0x=
28/0x68
>>>> [ =C2=A0 =C2=A09.804000] =C2=A0[<000000004011b92c>] free_initmem+0=
x94/0x340
>>>>
>
>> As others have pointed out this smp dump appears to be "harmless" an=
d may
>> not be the real culprit of the problems you are seeing.
>>
>> Is there another error message further on? Your URL doesn't work for=
me
>> either.
>
> For the sake of reliability I've put a (temporary) static copy of the=
page here:
> http://www.pateam.org/archive/tmp/serrparitylogs.html
> It still links to the original URL for CSS and stuff, but at least th=
e
> logs are there.
>
> 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=3D0 is truncated. Could the author post a full dump of the
> boot log with pdcchassis=3D0 please? (and maybe use pastebin? ;-)
Bummer, I've been reading the logs a bit too quickly. It seems we have
two different problems here:
2.6.30-1-64smp doesn't boot (apparently doesn't load init, hangs after
the badness in smp.c message)
2.6.30-1-64up crashes while loading PCI drivers
A log of the up kernel with pdcchassis=3D0 would thus be helpful.
HTH
--=20
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-10 8:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 10:24 HPPA hang with PCI SERR or PARITY enabling Meelis Roos
2009-06-15 13:45 ` John David Anglin
2009-07-30 17:58 ` Meelis Roos
2009-07-31 1:25 ` Randolph Chung
2009-07-31 1:45 ` John David Anglin
2009-07-31 6:28 ` Meelis Roos
2009-07-31 9:35 ` Thibaut VARENE
2009-07-31 14:46 ` John David Anglin
2009-07-31 14:50 ` John David Anglin
2009-07-31 23:16 ` Meelis Roos
2009-08-01 20:59 ` John David Anglin
2009-08-05 17:45 ` Grant Grundler
2009-08-05 19:42 ` Meelis Roos
2009-08-06 12:15 ` Bernd Gietzelt
2009-08-07 16:22 ` Grant Grundler
2009-08-08 9:31 ` Bernd Gietzelt
2009-08-09 5:27 ` Grant Grundler
2009-08-10 1:22 ` Randolph Chung
2009-08-10 8:01 ` Thibaut VARENE
2009-08-10 8:09 ` Thibaut VARENE [this message]
2009-08-10 11:08 ` Bernd Gietzelt
2009-08-10 11:18 ` Thibaut VARENE
2009-08-10 11:57 ` Bernd Gietzelt
2009-08-10 23:20 ` Grant Grundler
2009-08-11 9:27 ` Thibaut VARENE
2009-08-10 8:26 ` Bernd Gietzelt
2009-08-07 16:36 ` Grant Grundler
2009-08-29 20:19 ` Meelis Roos
2009-06-15 14:06 ` John David Anglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d01f9f00908100109y6265c3efs31a6a2c46679ae90@mail.gmail.com \
--to=t-bone@parisc-linux.org \
--cc=berndg@fsim-ev.de \
--cc=grundler@parisc-linux.org \
--cc=linux-parisc@vger.kernel.org \
--cc=randolph@tausq.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox