All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Anders <dizzey@ing.umu.se>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] k-class smp_call_function	at	arch/parisc/kernel/smp.c:340
Date: Mon, 28 Mar 2005 15:03:11 +0000	[thread overview]
Message-ID: <42481CAF.5010905@tiscali.be> (raw)
In-Reply-To: <20050328133837.GA14623@ing.umu.se>



Anders wrote:
> On Mon, Mar 28, 2005 at 01:04:27PM +0000, Joel Soete wrote:
> 
>>
...
> 
> Well yes the system hung after those messages the FLT parts are from the 
> firmware during the reboot, so i only included them to show it was 
> rebooting.  i will be back with a test from a up kernel soon.

mmm another question: are you using a initrd.img?
fwiw I encounter the same message as you reported:
...
SCSI subsystem initialized
unwind_init: start = 0x103bad60, end = 0x103ddd50, entries = 8959
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
...
while testing latest kyle debian-kernel? (tbh, I don't remember to have encountered it before?)

Can you check if in your kernel config CONFIG_SCSI_ZALON=y
and btw remove devfs support?

Thanks,
	Joel

PS: iirc Willy also boot a k model may be ask him his config file (I don't remember if he custumized or used the default one?)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-03-28 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 12:27 [parisc-linux] k-class smp_call_function at arch/parisc/kernel/smp.c:340 Anders
2005-03-28 13:04 ` Joel Soete
2005-03-28 13:38   ` Anders
2005-03-28 15:03     ` Joel Soete [this message]
2005-03-28 15:20       ` Anders
2005-03-28 15:16   ` Anders

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=42481CAF.5010905@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=dizzey@ing.umu.se \
    --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 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.