Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Bernd Gietzelt <berndg@fsim-ev.de>
To: linux-parisc@vger.kernel.org
Subject: Re: HPPA hang with PCI SERR or PARITY enabling
Date: Thu, 6 Aug 2009 14:15:42 +0200	[thread overview]
Message-ID: <20090806141542.bf48febf.berndg@fsim-ev.de> (raw)
In-Reply-To: <Pine.SOC.4.64.0908052241550.4076@math.ut.ee>

On Wed, 5 Aug 2009 22:42:34 +0300 (EEST)
Meelis Roos <mroos@linux.ee> wrote:

> > It would be helpful to know if 2.6.30.x kernels (from unstable)
> > show the same problem.
> 
> Will test.

I've done some test with actual and older kernels from debian because
my system shows the same behavior.

2.6.18-5-parisc64-smp 	Kernel panic at statfs
2.6.18-6-parisc64-smp 	Kernel panic at statfs
2.6.26-2-parisc64-smp 	SERR & PARITY
2.6.30-1-parisc64-smp 	Kernel panic
at /build/buildd/linux-2.6-2.6.30/debian/build/source_hppa_none/kernel/smp.c:369
2.6.30-1-parisc64 	SERR & PARITY 

The complete logs can be found here:
http://89.144.17.178/~bernd/lasatonline.de/dokuwiki/doku.php?id=programmieren:administration:computer:ulrike


Some idea what's behind this failure message?

<snap>
Begin: Running /scripts/init-bottom ... done.
run-init: statfsKernel panic - not syncing: Attempted to kill init!
 /: Function not 
</snap>


If some additional test/logs needed: I'm compliant to deliever them.


-- 
Bernd Gietzelt <berndg@fsim-ev.de>

  reply	other threads:[~2009-08-06 12:15 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 [this message]
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
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=20090806141542.bf48febf.berndg@fsim-ev.de \
    --to=berndg@fsim-ev.de \
    --cc=linux-parisc@vger.kernel.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