From: Samuel Flory <sflory@rackable.com>
To: Jason Zebchuk <jason@consensys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SE7500CW2 motherboard
Date: 20 Aug 2002 13:00:50 -0700 [thread overview]
Message-ID: <1029873651.3947.97.camel@flory.corp.rackablelabs.com> (raw)
In-Reply-To: <033f01c247d4$1abd5610$4902a8c0@consensys.com>
Try updating to the latest intel bios. I had a lot of issues with the
keyboard not working, and at least once I swear using it crashed the
system.
PS- I really recommend using the intel SE7500WV2 instead of the CW2.
It's a bit more in cost, but well worth it if you can afford it.
On Mon, 2002-08-19 at 15:59, Jason Zebchuk wrote:
> Hi,
>
> I'm having problems with the kernel debugger on a number of machines
> with Intel SE7500CW2 motherboards.
>
> When attempting to enter the debugger, either by pressing "PAUSE" or at
> a breakpoint, one of four things will happen:
>
> 1. It works as expected.
>
> 2. It reboots.
>
> 3. It hangs. ie. input seems to have no effect, no signs of activity,
> forced to power down.
>
> 4. It prints:
>
> PCI System Error on Bus/Device/Function 00B0h
> PCI Parity Error on Bus/Device/Function 00B0h
>
> and then continues to function as expected.
>
>
> In addition, it also occasionally hangs or reboots after entering the
> debugger successfully and using it for a short while.
>
>
> I'm using a 2.4.18 kernel, and the problems are only happening on Intel
> SE7500CW2 motherboards (ie. I don't have problems on say an Intel SDS2).
>
> Has anyone seen any similar problems? Has anyone had problems using
> this motherboard? Does anyone have any suggestions?
>
> Thanks,
>
> Jason Zebchuk
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2002-08-20 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 22:59 Jason Zebchuk
2002-08-20 20:00 ` Samuel Flory [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=1029873651.3947.97.camel@flory.corp.rackablelabs.com \
--to=sflory@rackable.com \
--cc=jason@consensys.com \
--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
all inboxes | Powered by JetHome®