All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Carter <knghtbrd@debian.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.4ac7 oops, locks in init on boot
Date: Fri, 11 May 2001 13:02:03 -0700	[thread overview]
Message-ID: <20010511130202.A8660@debian.org> (raw)
In-Reply-To: <20010511140019.A1248@debian-home.lcisp.com> <E14yIBC-0001XM-00@the-village.bc.nu>
In-Reply-To: <E14yIBC-0001XM-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, May 11, 2001 at 08:02:22PM +0100

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

On Fri, May 11, 2001 at 08:02:22PM +0100, Alan Cox wrote:
> > If anyone has any further suggestions/patches to run 2.4.x with K7
> > chosen optimizations, I'm open to testing.
> 
> 'Buy an AMD chipset box..'
> 
> Seriously at this point I am out of ideas. The prefetch to far effect 
> explained the old athlon locks (step 1) people reported on all chipsets. It
> didnt really seem to explain the problem with a few via chipset boards but I
> was hopeful. 

I'm considering it, but for AGP weirdness reasons.  Have the USB bugs been
worked out?  I am highly dependant on USB.

-- 
Joseph Carter <knghtbrd@debian.org>                Free software developer

<Palisade> how are we going to pronounce '00 or '01 or '02 and so on?
<Deek> Say goodbye to the nineties, say hello to the naughties. :)


[-- Attachment #2: Type: application/pgp-signature, Size: 273 bytes --]

  reply	other threads:[~2001-05-11 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 19:00 PROBLEM: 2.4.4ac7 oops, locks in init on boot Gordon Sadler
2001-05-11 19:02 ` Alan Cox
2001-05-11 20:02   ` Joseph Carter [this message]
2001-05-11 20:03     ` Alan Cox
2001-05-11 21:46       ` Joseph Carter
2001-05-12  1:57   ` Tom Diehl
2001-05-12 11:03     ` Alan Cox

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=20010511130202.A8660@debian.org \
    --to=knghtbrd@debian.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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 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.