> I wasn't sure what you meant by ARRE or AWRE in this case either, and I
> couldn't find them in the vinum docs. I don't think the kernel panicked, or
> if it did, it couldn't write any logs. I think the controller just freaked
> out or something. The worst part is the lack of availability o
- Original Message -
From: "Archie Cobbs" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, March 07, 2000 2:57 PM
Subject: Help: interrupt timeout
> My laptop running 3.4-RELEASE decided it doesn't want to
boot.
> It was uncleanly shut down via the power sw
In message <[EMAIL PROTECTED]>, Mike
Tancsa wri
tes:
>
> As a work around to preventing a local DoS in STABLE (PR 17152), it was
> suggested to me by Alfred Perlstein that I "patch [my] kernel to make all
> aio calls return ENOSYS". Does anyone have any suggestions as how to do
> that ? I have
I've had the same problem. Most people have told me that I have to
replace the hard drive.
I never had the problem before 3.4. Maybe that's just a coincidence,
though.
--
Chris Byrnes (CB5820)
Network Engineer, High Stability Internet Services
http://www.highstability.com
On Mon, 6 Mar 2000,
My laptop running 3.4-RELEASE decided it doesn't want to boot.
It was uncleanly shut down via the power switch by someone
who thought they were shutting down a different machine.
Now when it boots, running fsck gives this result:
> chip0: rev 0x01 on pci0.0.0
> chip1: rev 0x02 on pci0.7.0
> id
