From: John David Anglin <dave.anglin@bell.net>
To: Mikulas Patocka <mpatocka@redhat.com>, Helge Deller <deller@gmx.de>
Cc: Simone Mannori <simone.mannori@gmail.com>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: Kernel Panic on 4 cores hp c8000
Date: Tue, 5 Apr 2016 16:50:28 -0400 [thread overview]
Message-ID: <57042514.7000503@bell.net> (raw)
In-Reply-To: <alpine.LRH.2.02.1604051615410.32758@file01.intranet.prod.int.rdu2.redhat.com>
On 2016-04-05 4:18 PM, Mikulas Patocka wrote:
>
> On Tue, 5 Apr 2016, Helge Deller wrote:
>
>> On 05.04.2016 20:54, Mikulas Patocka wrote:
>>> On Thu, 31 Mar 2016, Simone Mannori wrote:
>>>>> I think Debian 5 will not even install on the C8000..
>>>> Correct: the boot DVD hang after a while.
>>> I installed Debian 5 on the C8000 (using tftp netboot, not DVD) some times
>>> ago.
>>>
>>> It required PCI serial card (because the Debian 5 kernel doesn't recognize
>>> the built-in serial ports) and PCI network card (the Debian 5 kernel can't
>>> handle the built-in E1000 network card due to non-standard checksum in the
>>> EEPROM).
>> ... and the debian 5 kernel was most likely *very* unstable on that machine ? :-)
>>
>> Helge
> Yes, it was very unstable. It took long time for the parisc port to
> stabilize.
I would say it took a change in the way the port is maintained. Helge
and I communicate
closely. I look at the buildd logs on a regular basis and try to push
fixes for gcc problems
aggressively. This causes some instability but I don't see any other
choice. We have also
pushed stuff to glibc. More needs to be done there but the Debian patch
set is reduced.
>
> Recently, I've got some gcc crashes when running kernel compilation in
> parallel with the LVM2 testsuite, so there may still be some stability
> bugs.
>
The LVM2 builds on Debian have been generally successful:
https://buildd.debian.org/status/logs.php?pkg=lvm2&arch=hppa
However, it looks as if testsuite isn't being run.
If you find something that is reproducible, please send along.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2016-04-05 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 17:00 Kernel Panic on 4 cores hp c8000 Simone Mannori
2016-03-31 17:19 ` Helge Deller
2016-03-31 17:44 ` Simone Mannori
2016-03-31 18:01 ` Helge Deller
2016-03-31 18:27 ` Simone Mannori
2016-04-01 6:41 ` Simone Mannori
2016-04-05 18:54 ` Mikulas Patocka
2016-04-05 18:57 ` Helge Deller
2016-04-05 20:18 ` Mikulas Patocka
2016-04-05 20:50 ` John David Anglin [this message]
2016-03-31 17:52 ` Simone Mannori
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=57042514.7000503@bell.net \
--to=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=simone.mannori@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.