Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: Matthew Wilcox <willy@debian.org>,
	Derek Engelhaupt <derekengelhaupt@rocketmail.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] long bus walk times on boot up
Date: 20 Nov 2002 22:16:31 -0700	[thread overview]
Message-ID: <1037855791.5976.11.camel@beavis> (raw)
In-Reply-To: <20021120154011.G12656@parcelfarce.linux.theplanet.co.uk>

Derek or anyone else experience this problem,

Feel free to test out this patch.  This impliments Willy's idea and
seems to work find on linux-2.5.  I can not test this against cvs head
on linux-2.4 since my C200 HPMCs in cpu_idle().

I do not have time to track down the linux-2.4 boot issue right now, but
I will commit this patch once I get C200 to boot cvs head and if
feedback from the patch is good.

Thanks,

- Ryan

On Wed, 2002-11-20 at 08:40, Matthew Wilcox wrote:
> On Wed, Nov 20, 2002 at 07:30:41AM -0800, Derek Engelhaupt wrote:
> > 
> > Well, my C180 is gone to a new home and my C360 is well on it's
> > way, but I had a question about the new netinstall ISO's out there.
> > I had been running the 2.4.19-pa19-20020922-netinst.iso on the C180 and
> > it didn't have the bus walk issues that cause the long boot up times.
> > I really would like to avoid having my C360 take 20+ minutes to boot up.
> > Are there any real huge issues with running this older kernal on my C360
> > or are there any immediate plans to fix the issues of having to walk
> > the entire bus?  I'm still a little weary of compiling my own kernal
> > (only done this through SAM on HP-UX), but if I was forced to I could
> > probably figure it out using the HOWTO's.  Is there a kernal parameter
> > I could tweak that could resolve the long bus walk times?  Or am I just
> > totally off base?  :)
> 
> 2.4.19-pa19 should run fine on a C360.  the long bus walk problem
> isn't yet fixed in the 2.4 CVS (but should be fixed in the 2.5 tree).
> this isn't a ploy to persuade more people to use 2.5; it's just ryan
> didn't get around to it yet ;-)
> 
> -- 
> Revolutions do not require corporate support.
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 

      reply	other threads:[~2002-11-21  5:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18 22:01 [parisc-linux] An easy installation on a K360/3 with 2.4.3-pa16-pdc Darren Wathen
2002-11-20 15:30 ` [parisc-linux] long bus walk times on boot up Derek Engelhaupt
2002-11-20 15:40   ` Matthew Wilcox
2002-11-21  5:16     ` Ryan Bradetich [this message]

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=1037855791.5976.11.camel@beavis \
    --to=rbradetich@uswest.net \
    --cc=derekengelhaupt@rocketmail.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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