Re: bad kernel 2.0.34 bug ?

1998-06-25 Thread Harald Weidner
Hello, > > As a matter of fact it just happened with our IDE drives after upgrading >to 2.0.34, since we had read this, we downgraded to 2.0.33 and it works with >no erros now. I >don't intent to say that this is an important bug, but maybe it should be >looked at. I had this error messag

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread Dale Scheetz
On Wed, 24 Jun 1998, Javier Fdz-Sanguino Pen~a wrote: > > As a matter of fact it just happened with our IDE drives after upgrading > to 2.0.34, since we had read this, we downgraded to 2.0.33 and it works with > no erros now. I > don't intent to say that this is an important bug, but maybe

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread G John Lapeyre
On Wed, 24 Jun 1998, Andreas Jellinghaus wrote: > i have 40 identical computers here, and one of them has the same problems. > i guess some trouble with the mainboard, but i'm not sure and could not > investigate till today. all other machines work fine (with hard disk, > 2 have network card probl

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread G John Lapeyre
Well , its already off. Thanks for the tip. I downgraded to 2.0.33, and things are much more stable , so far, but I've seen a couple of errors. I guess we'll have to wait a while longer and see if other people report the same thing. On 24 Jun 1998, Gregory S. Stark wrote: > Are you run

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread Andreas Jellinghaus
>it as well. > A typical error message is (this occurs on 2 of three drives): > >Jun 23 20:35:40 homey kernel: hdb: read_intr: status=0x59 { DriveReady >SeekComplete DataRequest Error } >Jun 23 20:35:40 homey kernel: hdb: read_intr: error=0x40 { >UncorrectableError }, LBAsect=6766956, sec

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread Gregory S. Stark
> > > On Wed, Jun 24, 1998 at 12:24:52AM -0700, G John Lapeyre wrote: > > > > A typical error message is (this occurs on 2 of three drives): > > > > > > > > Jun 23 20:35:40 homey kernel: hdb: read_intr: status=0x59 { DriveReady > > > > SeekComplete DataRequest Error } > > > > Jun 23 20:

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread Javier Fdz-Sanguino Pen~a
As a matter of fact it just happened with our IDE drives after upgrading to 2.0.34, since we had read this, we downgraded to 2.0.33 and it works with no erros now. I don't intent to say that this is an important bug, but maybe it should be looked at. Regards Javi On W

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread G John Lapeyre
OK, I was wrong , its happening now with 2.0.33 too. However, its happening to all three ide drives. I'd better figure it out fast On Wed, 24 Jun 1998, Christian Meder wrote: > On Wed, Jun 24, 1998 at 12:24:52AM -0700, G John Lapeyre wrote: > > A typical error message is (thi

Re: bad kernel 2.0.34 bug ?

1998-06-24 Thread Christian Meder
On Wed, Jun 24, 1998 at 12:24:52AM -0700, G John Lapeyre wrote: > A typical error message is (this occurs on 2 of three drives): > > Jun 23 20:35:40 homey kernel: hdb: read_intr: status=0x59 { DriveReady > SeekComplete DataRequest Error } > Jun 23 20:35:40 homey kernel: hdb: read_intr: err

bad kernel 2.0.34 bug ?

1998-06-24 Thread G John Lapeyre
My file systems are getting trashed. I get errors and eventually the system hung (couldn't shutdown). I switched back to 2.0.33 and everything is fine. I'm not sure if overheating has something to do with it as well. A typical error message is (this occurs on 2 of three drive