From: "Tom Epperly" <tepperly@llnl.gov>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bad Illegal instruction traps on dual-Xeon (p4) Linux Dell box
Date: Wed, 20 Mar 2002 15:31:50 -0800 [thread overview]
Message-ID: <3C991BE6.70504@llnl.gov> (raw)
In-Reply-To: <E16npXs-0003el-00@the-village.bc.nu>
Alan Cox wrote:
>>I initiated a support call with Dell at around 3:30pm PST on Friday
>>15-Mar-2002, and all the feedback I've received from this so far shows
>>that they are clueless. They are trying to portray this as a Linux
>>problem.
>>
>
>Well to be honest they aren't the only ones who are totally baffled by it.
>Do you have the current microcode updates in your BIOS or via the ucode
>driver ?
>
One box, tux06, has the latest Dell BIOS, A05. I don't know how to
determine if it has the latest microcode updates. Where can one get the
current microcode updates, and how do I install it?
>
>
>Do all the problem boxes have the same stepping of CPU ?
>
According to cat /proc/cpuinfo, two boxes tux06 & tux34 have stepping
10, and tux47 has stepping 2. I have seen the unexplained "Illegal
instruction" messages on tux34 and tux47, but I haven't run the modified
kernel on them. root access is restricted here.
Tom
next prev parent reply other threads:[~2002-03-20 23:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 21:35 Bad Illegal instruction traps on dual-Xeon (p4) Linux Dell box Tom Epperly
2002-03-20 23:26 ` Kurt Garloff
2002-03-21 0:04 ` Alan Cox
2002-03-20 23:31 ` Alan Cox
2002-03-20 23:31 ` Tom Epperly [this message]
2002-03-21 0:03 ` Dave Jones
2002-03-21 0:04 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 23:46 James Washer
2002-03-21 0:30 James Washer
2002-03-21 7:19 ` Zwane Mwaikambo
2002-03-21 14:52 James Washer
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=3C991BE6.70504@llnl.gov \
--to=tepperly@llnl.gov \
--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.