According to Doug:
Heh... well I've already enabled flags 0xb0ff, which has improved things
Speaking of flags for ATA disks, I'm using 0xa0ff for my laptop drive and
wonders if there a better setting...?
found- vendor=0x8086, dev=0x7111, revid=0x01
class=01-01-80, hdrtype=0x00,
Mike Smith wrote:
Well that's not good, since I have almost convinced my boss to replace
the crappy IDE drives on our shiny new Intel N440BX mb's with scsi
drives since the controller is built in. :-/ Does this look like a
soluble problem, or is it just going to be a case of
I would be more than willing to do run some hardware tests in our lab
enviroment here, but our main problem is that we can't acurately
reproduce the problem. The reboots seem to happen maybe 3-4 times a
week from a pool of about 7 machines. I'm not sure if someone could
write a piece of code
David Greenman wrote:
So if this problem is NOT related to specific hardware, how can we get
the driver fixed?
Talk to the maintainer (David). We've offered him cores and kernels
before. Alternatively, you'll need to experiment with your setup to
determine what characterises the
David Greenman wrote:
So if this problem is NOT related to specific hardware, how can we get
the driver fixed?
Talk to the maintainer (David). We've offered him cores and kernels
before. Alternatively, you'll need to experiment with your setup to
determine what characterises the
Well that's not good, since I have almost convinced my boss to replace
the crappy IDE drives on our shiny new Intel N440BX mb's with scsi
drives since the controller is built in. :-/ Does this look like a
soluble problem, or is it just going to be a case of "don't do that?"
Anything I
So if this problem is NOT related to specific hardware, how can we get
the driver fixed?
Talk to the maintainer (David). We've offered him cores and kernels
before. Alternatively, you'll need to experiment with your setup to
determine what characterises the failures and help David
So if this problem is NOT related to specific hardware, how can we get
the driver fixed?
Stevan Arychuk
AvantGo Inc.
[EMAIL PROTECTED]
Mike Smith wrote:
Thanks for your response David.
Do you think the problem is isolated to just the onboard devices? Would
a PCI NIC help or is it the
So if this problem is NOT related to specific hardware, how can we get
the driver fixed?
Talk to the maintainer (David). We've offered him cores and kernels
before. Alternatively, you'll need to experiment with your setup to
determine what characterises the failures and help David out with
So if this problem is NOT related to specific hardware, how can we get
the driver fixed?
Talk to the maintainer (David). We've offered him cores and kernels
before. Alternatively, you'll need to experiment with your setup to
determine what characterises the failures and help David out with
So if this problem is NOT related to specific hardware, how can we get
the driver fixed?
Talk to the maintainer (David). We've offered him cores and kernels
before. Alternatively, you'll need to experiment with your setup to
determine what characterises the failures and help David
Mike Smith [EMAIL PROTECTED] wrote, in response to [EMAIL PROTECTED]:
We're running 3.3-REL on dual processor PII-450's, with a N440BX
motherboard, using the onboard EtherExpress Pro (fxp) NIC and 512MB
RAM.
These machines are running custom software that excercises the disk,
CPU
and
Thanks for your response David.
Do you think the problem is isolated to just the onboard devices? Would
a PCI NIC help or is it the entire N440BX board?
Regards,
Stevan Arychuk
AvantGo Inc.
[EMAIL PROTECTED]
David Greenman wrote:
We're running 3.3-REL on dual processor PII-450's, with a
Thanks for your response David.
Do you think the problem is isolated to just the onboard devices? Would
a PCI NIC help or is it the entire N440BX board?
We've seen these symptoms on non-Intel boards. (eg. ASUS P2L, P2B).
--
\\ Give a man a fish, and you feed him for a day. \\ Mike
We're running 3.3-REL on dual processor PII-450's, with a N440BX
motherboard, using the onboard EtherExpress Pro (fxp) NIC and 512MB RAM.
These machines are running custom software that excercises the disk, CPU
and network quite heavily. The SMP machines seem to have both "fxp0:
device timeout"
Greetings,
We're running 3.3-REL on dual processor PII-450's, with a N440BX
motherboard, using the onboard EtherExpress Pro (fxp) NIC and 512MB RAM.
These machines are running custom software that excercises the disk, CPU
and network quite heavily. The SMP machines seem to have both
We run about 50 machines with a similar setup (asus p2bd mb) all of which
run quite well. We have NMBCLUSERS=30720 though...
- Todd
On Thu, 7 Oct 1999, Stevan Arychuk wrote:
Greetings,
We're running 3.3-REL on dual processor PII-450's, with a N440BX
motherboard, using the onboard
17 matches
Mail list logo
