From: "Joel Soete" <soete.joel@tiscali.be>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] c3k panics
Date: Wed, 1 Jun 2005 17:05:32 +0200 [thread overview]
Message-ID: <4282FEEC00007DED@mail-2-bnl.tiscali.it> (raw)
>
> I believe that there's likely more than one bug. After working around
> the memory management bug, I tried a number of gcc builds. Two crashes=
> occurred as previously reported. I also had a third crash. In this
> one, the TOC IIA Offset value pointed into "userspace". These all
> occurred with only a few hours of running time.
>
Sorry but I don't remember if I already mentioned some more results about=
test getting rid of cffc():
I reach to boot successfully this kernel which didn't panicing any more;
anyway after enough untar, rm the corresponding ext3 fs was switched to r=
ead-only
mode (corruption)?
> I then switched from vmlinux-2.6.11-pa4-c3000_defconfig to
> vmlinux-2.6.8.1-pa11-c3000_defconfig. This kernel seems ok. It's
> survived one binutils and three full gcc builds. However, there are
> seven fails in the libstdc++ testsuite that don't occur with 2.6.11.
> On the otherhand, I'm seeing a few Java processes not terminate with
> 2.6.11-pa4. This problem doesn't seem to be present in 2.6.8.1-pa11
> and Grant's 64-bit version of 2.6.11-pa4 on gsyprf11.
>
imho and according to my numerous test (that took me more time on b180) 2=
.6.8.1-pa11
(+some Kyle backport) seems to be rock solid, and iirc early 2.6.10 alrea=
dy
presented the pb (2.6.9 seems also?)
> I'm going to try a few more kernels to see if it's possible to isolate
> the change that introduced the problem.
>
Thanks (that's too much time I am working in blind on this pb, I very nee=
d
a breack)
Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next reply other threads:[~2005-06-01 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 15:05 Joel Soete [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-31 5:41 [parisc-linux] c3k panics Joel Soete
2005-05-31 6:26 ` Randolph Chung
2005-06-01 13:11 ` Joel Soete
2005-06-01 13:55 ` John David Anglin
[not found] <429A0B7C.3020003@tiscali.be>
2005-05-29 20:49 ` John David Anglin
2005-05-29 1:41 John David Anglin
2005-05-29 1:50 ` John David Anglin
2005-05-29 22:08 ` Carlos O'Donell
2005-05-29 23:39 ` John David Anglin
2005-05-29 10:32 ` Joel Soete
2005-05-29 17:15 ` Joel Soete
2005-05-30 1:13 ` Randolph Chung
2005-06-01 14:04 ` Joel Soete
2005-05-29 17:45 ` 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=4282FEEC00007DED@mail-2-bnl.tiscali.it \
--to=soete.joel@tiscali.be \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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