From: Ken Brownfield <brownfld@irridia.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 Kernel - ASUS CUV4X-DLS Question
Date: Thu, 3 May 2001 15:52:23 -0700 [thread overview]
Message-ID: <200105032252.RAA12232@asooo.flowerfire.com> (raw)
In-Reply-To: <E14vRVN-0006Ke-00@the-village.bc.nu>
I have some info at "http://web.irridia.com/linux/" from an LPr having
issues, including the dmidecode output and a mostly complete boot-time
dmesg dump from an LPr and LP1000r. The LPr was running 2.4.2-pre4 and
the LP1000r is running 2.4.5-pre1, both without "noapic". Please let me
know if you need more info.
BTW, I have an isolated bank of redundant machines, one of which I can
load down with heavy live load so I can test patches pretty easily.
I'll do anything, including setting fire to a machine, if it'll help. :-)
--
Ken.
On Thursday, May 3, 2001, at 03:23 PM, Alan Cox wrote:
>> But the distributions use _the_ kernel. Even if -ac is fixed, it's not
>> really something I would be willing to put in production. Until I
>> found
>
> Actually by unit count Linus is currently losing to me on 2.4 shipping.
> Thats one reason I really want to get the stuff I have back into the
> main
> tree.
>
>> the noapic work-around, we were basically going to have to move off of
>> Linux. I could very well be an isolated case, but the APIC issues I'm
>> seeing scare me, and not just for my sake.
>
> Can you give me the detailed boot up messages from one of your HP boxes
> and
> some more info. Also can you run dmidecode.c from
> ftp://ftp.linux.org.uk/pub/linux/alan
>
> on them and send me the DMI strings. You will need to run it as root but
> it can be run on a live system (at least I dont know of any bugs in it
> and
> it only reads from raw BIOS memory not writes).
>
> Alan
next prev parent reply other threads:[~2001-05-03 22:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 17:51 2.4.4 Kernel - ASUS CUV4X-DLS Question David A. Neal
2001-05-03 18:03 ` Alan Cox
2001-05-03 19:51 ` Ken Brownfield
2001-05-03 20:36 ` Alan Cox
2001-05-03 21:24 ` Hugh Dickins
2001-05-03 21:56 ` Alan Cox
2001-05-03 22:07 ` Ken Brownfield
2001-05-03 22:23 ` Alan Cox
2001-05-03 22:52 ` Ken Brownfield [this message]
2001-05-09 1:57 ` J. S. Connell
2001-05-09 8:47 ` Alan Cox
[not found] <Pine.LNX.4.10.10105031614270.4386-100000@coffee.psychology.mcmaster.ca>
2001-05-03 21:50 ` Ken Brownfield
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=200105032252.RAA12232@asooo.flowerfire.com \
--to=brownfld@irridia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox