Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Jeremy Lea
Hi,

On Wed, Jul 21, 1999 at 03:15:26PM -0700, Julian Elischer wrote:
> try a -current but only reverting pci/ide_pci.c

It'll have to wait for 18 hours or so...  I'm moving the machine from
-CURRENT to 3.2-RELEASE then -STABLE, so once my CDs are written and I
can get da0 out then I'll play with the disk again...  I only wanted a
new network driver.

Maybe revert -STABLE anyway if there's signs of smoke?

> you can use the CVS web interface to fetch various versions...

Never run current without a CVS repository is probably better advice.

Regards,
 -Jeremy

-- 
  |   "I could be anything I wanted to, but one things true
--+--  Never gonna be as big as Jesus, never gonna hold the world in my hand
  |Never gonna be as big as Jesus, never gonna build a promised land
  |But that's, that's all right, OK with me..." -Audio Adrenaline


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Julian Elischer

try a -current but only reverting pci/ide_pci.c

you can use the CVS web interface to fetch various versions...

julian


On Thu, 22 Jul 1999, Jeremy Lea wrote:

> Hi,
> 
> On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote:
> > > I was in the UDMA code yesterday
> > > (but mostly in the CYRIX code... (changes elsewhere should have been
> > > mostly cosmetic).
> > > 
> > > 
> > > can you get the exact error message?
> > > 
> > > julian
> > 
> > I got it..., I happened to be working on something else at the time
> > and I let it sit unattended for awhile.. it ate my disk partition rather
> > badly.
> > 
> > Here is the error I see:
> > wd0: DMA failure, DMA status 5
> > 
> > Thank goodness I tested this -STABLE on my desk machine before I was going 
> > to
> > place it on the home directory server for the department...
> 
> Same error here, from 18h old -CURRENT.  Asus TX97 MB and Quantum
> Fireball SE (4.3GB).  Thankfully my disk seems ok (I didn't write
> anything to that disk with the bad kernel).
> 
> My last kernel was from 5 July, so I can't narrow the gap any.  I tried
> a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I
> did a quick rebuild, so that might be pilot error.)
> 
> Regards,
>  -Jeremy
> 
> -- 
>   |   "I could be anything I wanted to, but one things true
> --+--  Never gonna be as big as Jesus, never gonna hold the world in my hand
>   |Never gonna be as big as Jesus, never gonna build a promised land
>   |But that's, that's all right, OK with me..." -Audio Adrenaline
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Julian Elischer

this looks like a hardware failure..


On Wed, 21 Jul 1999, David E. Cross wrote:

> > I was in the UDMA code yesterday
> > (but mostly in the CYRIX code... (changes elsewhere should have been
> > mostly cosmetic).
> > 
> > 
> > can you get the exact error message?
> > 
> > julian
> 
> I got it..., I happened to be working on something else at the time
> and I let it sit unattended for awhile.. it ate my disk partition rather
> badly.
> 
> Here is the error I see:
> wd0: DMA failure, DMA status 5
> 
> Thank goodness I tested this -STABLE on my desk machine before I was going to
> place it on the home directory server for the department...
> 
> --
> David Cross   | email: cro...@cs.rpi.edu 
> Systems Administrator/Research Programmer | Web: 
> http://www.cs.rpi.edu/~crossd 
> Rensselaer Polytechnic Institute, | Ph: 518.276.2860
> Department of Computer Science| Fax: 518.276.4033
> I speak only for myself.  | WinNT:Linux::Linux:FreeBSD
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Jeremy Lea

Hi,

On Wed, Jul 21, 1999 at 03:15:26PM -0700, Julian Elischer wrote:
> try a -current but only reverting pci/ide_pci.c

It'll have to wait for 18 hours or so...  I'm moving the machine from
-CURRENT to 3.2-RELEASE then -STABLE, so once my CDs are written and I
can get da0 out then I'll play with the disk again...  I only wanted a
new network driver.

Maybe revert -STABLE anyway if there's signs of smoke?

> you can use the CVS web interface to fetch various versions...

Never run current without a CVS repository is probably better advice.

Regards,
 -Jeremy

-- 
  |   "I could be anything I wanted to, but one things true
--+--  Never gonna be as big as Jesus, never gonna hold the world in my hand
  |Never gonna be as big as Jesus, never gonna build a promised land
  |But that's, that's all right, OK with me..." -Audio Adrenaline


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Jeremy Lea
Hi,

On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote:
> > I was in the UDMA code yesterday
> > (but mostly in the CYRIX code... (changes elsewhere should have been
> > mostly cosmetic).
> > 
> > 
> > can you get the exact error message?
> > 
> > julian
> 
> I got it..., I happened to be working on something else at the time
> and I let it sit unattended for awhile.. it ate my disk partition rather
> badly.
> 
> Here is the error I see:
> wd0: DMA failure, DMA status 5
> 
> Thank goodness I tested this -STABLE on my desk machine before I was going to
> place it on the home directory server for the department...

Same error here, from 18h old -CURRENT.  Asus TX97 MB and Quantum
Fireball SE (4.3GB).  Thankfully my disk seems ok (I didn't write
anything to that disk with the bad kernel).

My last kernel was from 5 July, so I can't narrow the gap any.  I tried
a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I
did a quick rebuild, so that might be pilot error.)

Regards,
 -Jeremy

-- 
  |   "I could be anything I wanted to, but one things true
--+--  Never gonna be as big as Jesus, never gonna hold the world in my hand
  |Never gonna be as big as Jesus, never gonna build a promised land
  |But that's, that's all right, OK with me..." -Audio Adrenaline


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Julian Elischer


try a -current but only reverting pci/ide_pci.c

you can use the CVS web interface to fetch various versions...

julian


On Thu, 22 Jul 1999, Jeremy Lea wrote:

> Hi,
> 
> On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote:
> > > I was in the UDMA code yesterday
> > > (but mostly in the CYRIX code... (changes elsewhere should have been
> > > mostly cosmetic).
> > > 
> > > 
> > > can you get the exact error message?
> > > 
> > > julian
> > 
> > I got it..., I happened to be working on something else at the time
> > and I let it sit unattended for awhile.. it ate my disk partition rather
> > badly.
> > 
> > Here is the error I see:
> > wd0: DMA failure, DMA status 5
> > 
> > Thank goodness I tested this -STABLE on my desk machine before I was going to
> > place it on the home directory server for the department...
> 
> Same error here, from 18h old -CURRENT.  Asus TX97 MB and Quantum
> Fireball SE (4.3GB).  Thankfully my disk seems ok (I didn't write
> anything to that disk with the bad kernel).
> 
> My last kernel was from 5 July, so I can't narrow the gap any.  I tried
> a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I
> did a quick rebuild, so that might be pilot error.)
> 
> Regards,
>  -Jeremy
> 
> -- 
>   |   "I could be anything I wanted to, but one things true
> --+--  Never gonna be as big as Jesus, never gonna hold the world in my hand
>   |Never gonna be as big as Jesus, never gonna build a promised land
>   |But that's, that's all right, OK with me..." -Audio Adrenaline
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread David E. Cross
> I was in the UDMA code yesterday
> (but mostly in the CYRIX code... (changes elsewhere should have been
> mostly cosmetic).
> 
> 
> can you get the exact error message?
> 
> julian

I got it..., I happened to be working on something else at the time
and I let it sit unattended for awhile.. it ate my disk partition rather
badly.

Here is the error I see:
wd0: DMA failure, DMA status 5

Thank goodness I tested this -STABLE on my desk machine before I was going to
place it on the home directory server for the department...

--
David Cross   | email: cro...@cs.rpi.edu 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Julian Elischer


this looks like a hardware failure..


On Wed, 21 Jul 1999, David E. Cross wrote:

> > I was in the UDMA code yesterday
> > (but mostly in the CYRIX code... (changes elsewhere should have been
> > mostly cosmetic).
> > 
> > 
> > can you get the exact error message?
> > 
> > julian
> 
> I got it..., I happened to be working on something else at the time
> and I let it sit unattended for awhile.. it ate my disk partition rather
> badly.
> 
> Here is the error I see:
> wd0: DMA failure, DMA status 5
> 
> Thank goodness I tested this -STABLE on my desk machine before I was going to
> place it on the home directory server for the department...
> 
> --
> David Cross   | email: [EMAIL PROTECTED] 
> Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
> Rensselaer Polytechnic Institute, | Ph: 518.276.2860
> Department of Computer Science| Fax: 518.276.4033
> I speak only for myself.  | WinNT:Linux::Linux:FreeBSD
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread Jeremy Lea

Hi,

On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote:
> > I was in the UDMA code yesterday
> > (but mostly in the CYRIX code... (changes elsewhere should have been
> > mostly cosmetic).
> > 
> > 
> > can you get the exact error message?
> > 
> > julian
> 
> I got it..., I happened to be working on something else at the time
> and I let it sit unattended for awhile.. it ate my disk partition rather
> badly.
> 
> Here is the error I see:
> wd0: DMA failure, DMA status 5
> 
> Thank goodness I tested this -STABLE on my desk machine before I was going to
> place it on the home directory server for the department...

Same error here, from 18h old -CURRENT.  Asus TX97 MB and Quantum
Fireball SE (4.3GB).  Thankfully my disk seems ok (I didn't write
anything to that disk with the bad kernel).

My last kernel was from 5 July, so I can't narrow the gap any.  I tried
a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I
did a quick rebuild, so that might be pilot error.)

Regards,
 -Jeremy

-- 
  |   "I could be anything I wanted to, but one things true
--+--  Never gonna be as big as Jesus, never gonna hold the world in my hand
  |Never gonna be as big as Jesus, never gonna build a promised land
  |But that's, that's all right, OK with me..." -Audio Adrenaline


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!

1999-07-21 Thread David E. Cross

> I was in the UDMA code yesterday
> (but mostly in the CYRIX code... (changes elsewhere should have been
> mostly cosmetic).
> 
> 
> can you get the exact error message?
> 
> julian

I got it..., I happened to be working on something else at the time
and I let it sit unattended for awhile.. it ate my disk partition rather
badly.

Here is the error I see:
wd0: DMA failure, DMA status 5

Thank goodness I tested this -STABLE on my desk machine before I was going to
place it on the home directory server for the department...

--
David Cross   | email: [EMAIL PROTECTED] 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message