Linux PARISC architecture development
 help / color / mirror / Atom feed
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: Sun, 29 May 2005 10:32:16 +0000	[thread overview]
Message-ID: <42999A30.6070602@tiscali.be> (raw)
In-Reply-To: <200505290141.j4T1ffhI006449@hiauly1.hia.nrc.ca>



John David Anglin wrote:
> I can panic my c3750 very consistently running the binutils testsuite
> (cvs source as of 20050526).
mmm the experimental debian bintuils-2.16 seems to works fine for me (kernel 2.6.8.1-pa11 32bit on a b180).

> I've tried many of the default kernels
> to see if I could isolate when the problem was introduced.  The last
> kernel that seems unaffected is 2.6.8.1-pa11.  The problem is present
> in 2.6.12-rc5-pa0 and 2.6.11-pa4.
> 
I observe the same differences of behaviour.

Btw, that looks like the pb I encountered many times when I tried CONFIG_DEBUG_SLAB=y?

As I tried to explain in detail (<http://lists.parisc-linux.org/pipermail/parisc-linux/2005-May/026493.html>) there is a big pb with 
this option. Unfortunately, I am not a C programer and so lake of deep knowledges to suggest a proper fix :-(

If it's your case too, can you try without this option.
(or give a try to this patch attempt: <http://lists.parisc-linux.org/pipermail/parisc-linux/2005-May/026474.html>.
it's not perfect but it helps me anyway :-) ).


> The sad part is that panic is also broken and no error messages are
> produced when the fault occurs.  Before adding panic=180 to the command
> line, pressing TOC just yielded a register dump for panic itself.  That's
> not too useful.  In my testing, the last working panic dump was with
> 2.6.9-pa1 which faulted with a HPMC during boot.
> 

The same for me, it seems that the pb appears during 2.6.9 developement;
as far as I can test, it seems that the pb appears between 2.6.9-rc2-pa2 and pa5;
For my part I already tried to revert only this pa5 (just to be sure) 
<http://lists.parisc-linux.org/pipermail/parisc-linux-cvs/2004-September/034576.html>
but it doesn't help :-)

So still have to revert few thing (but it would be hard like fixup stuff) to try to isolate the pb?

Ah still a question: is it the same pb for 32bit and 64bit twin kernel?

Thanks,
	Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2005-05-29 10:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-29  1:41 [parisc-linux] c3k panics 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 [this message]
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
     [not found] <429A0B7C.3020003@tiscali.be>
2005-05-29 20:49 ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2005-05-31  5:41 Joel Soete
2005-05-31  6:26 ` Randolph Chung
2005-06-01 13:11   ` Joel Soete
2005-06-01 13:55     ` John David Anglin
2005-06-01 15:05 Joel Soete

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=42999A30.6070602@tiscali.be \
    --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