Re: UDMA broken in -CURRENT/-STABLE?
I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 [...] I've seen the exact same problem on -stable builds since the 20th (I don't know how much further back it went than that). I'm not in front of my computer right now, but the errors were all DMA errors (status ready as I recall). I have a PIIX4 controller. I played around with it a bit and found that simply turning of the DMA hint in the flags cleared the problems (my flags went from f0fff0ff to d0ffd0ff I believe). Actually, once I accidentilly left the flags with DMA enabled on only 1 drive and only received DMA errons on that single drive. I don't know if this is related, but my atapi CD (Acer 40x) still reports DMA (apparently not affected by the wdc flags), but won't play audio CDs from most CD apps (apparently the ones which use the CDIOCPLAYWMF ioctl to play audio). This has been going on for longer, but I don't know if it was maybe a precursor to the UDMA bug? Kelly ~[EMAIL PROTECTED]~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE?
I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 r...@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 [...] I've seen the exact same problem on -stable builds since the 20th (I don't know how much further back it went than that). I'm not in front of my computer right now, but the errors were all DMA errors (status ready as I recall). I have a PIIX4 controller. I played around with it a bit and found that simply turning of the DMA hint in the flags cleared the problems (my flags went from f0fff0ff to d0ffd0ff I believe). Actually, once I accidentilly left the flags with DMA enabled on only 1 drive and only received DMA errons on that single drive. I don't know if this is related, but my atapi CD (Acer 40x) still reports DMA (apparently not affected by the wdc flags), but won't play audio CDs from most CD apps (apparently the ones which use the CDIOCPLAYWMF ioctl to play audio). This has been going on for longer, but I don't know if it was maybe a precursor to the UDMA bug? Kelly ~kby...@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
UDMA broken in -CURRENT/-STABLE?
I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 [...] -- 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
Re: UDMA broken in -CURRENT/-STABLE?
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 On Wed, 21 Jul 1999, David E. Cross wrote: I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 [...] -- 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*!!!!!
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 5active 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
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
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
UDMA broken in -CURRENT/-STABLE?
I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 r...@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 [...] -- 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?
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 On Wed, 21 Jul 1999, David E. Cross wrote: I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 r...@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 [...] -- 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*!!!!!
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 5active 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*!!!!!
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 5active 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*!!!!!
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 5active 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*!!!!!
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 5active 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*!!!!!
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
