From: Thibaut VARENE <T-Bone@parisc-linux.org>
To: Bernd Gietzelt <berndg@fsim-ev.de>
Cc: Randolph Chung <randolph@tausq.org>,
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 13:18:51 +0200 [thread overview]
Message-ID: <7d01f9f00908100418x20ef23d5p2e752e05e8246ce4@mail.gmail.com> (raw)
In-Reply-To: <20090810130827.98dfd895.berndg@fsim-ev.de>
On Mon, Aug 10, 2009 at 1:08 PM, Bernd Gietzelt<berndg@fsim-ev.de> wrote:
> On Mon, 10 Aug 2009 10:09:36 +0200
> Thibaut VARENE <T-Bone@parisc-linux.org> wrote:
>
>> 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=0 would thus be helpful.
>
> http://pastebin.com/m2a494b9b
>
> I couldn't see any difference to the log without pdcchassis=0.
The final output of GSP is probably due to a HPMC. Could you check in
GSP "CL" command (for Console Logs) that there is no more kernel
output after line 218 in your dump?
Thanks
--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
next prev parent reply other threads:[~2009-08-10 11:18 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
2009-08-10 11:08 ` Bernd Gietzelt
2009-08-10 11:18 ` Thibaut VARENE [this message]
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=7d01f9f00908100418x20ef23d5p2e752e05e8246ce4@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