Re: Showstopper ATA bug in 6.1-PRE?
* Søren Schmidt [EMAIL PROTECTED] [2006-02-09 15:38]: [...] OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. The patch also fixes my problem with the promise controller. So go on to get it commited. Thanks, jens ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE? (Still happening)
On Feb 10, 2006, at 9:03 AM, Wilko Bulte wrote: On Thu, Feb 09, 2006 at 11:08:24PM +0100, Wilko Bulte wrote.. On Thu, Feb 09, 2006 at 09:24:23PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:45:53PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the - stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. Is this relative to HEAD or RELENG_6? I cannot / will not go to HEAD with this machine (my main production box.. :-) Doesn't matter, ATA is the same on both... OK, I was not sure if they were 100% identical. The patch at first impression seems to have eliminated the problem. Good seems I'm on the right track at least. Interestingly enough ad10 remained ad10 with the patch applied? Yeah, thats intentional, I though we better not break POLA here.. I agree :-) I'll put some load on to see what happens. Let me know how that turns out, I'll clean things up a bit and get it committed to -current, then get permission to MFC when we are sure it fixes the problem... I ran a 44GB disk-to-disk dump without incidents (source on the RAID1, target on the JBOD). No problems whatsoever. Looks like things behave much better now. Tonight the machine will run a daily full dump to DLT tape, I'll know how that turns out tomorrow. Backup ran without problems. -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- [EMAIL PROTECTED] Soren, I am still getting this error. I cvsup'd to RELENG_6 today (Feb. 15, 2006 at 6:00 PM CET) and I got the following files from HEAD: ata-all.c (1.264) ata-all.h (1.113) ata-chipset.c (1.158) ata-pci.c (1.115) I have then rebuilt the kernel and world and I tested the system. I have a Promise TX2300 with two 250 GB Maxtor in RAID1 with gmirror, plus two 9 GB SCSI drives in RAID1 with gmirror where I put the OS and applications and a 160 GB UATA Seagate (attached to the motherboard UATA) where I backup sensitive data. The system was able to rebuild the mirror (I always got the error with RELENG_6_0), but then I made a backup tar from the two Maxtor's mirror to the Seagate and I got the following error after having copied approx 16 GB: Feb 15 20:56:31 zoe kernel: GEOM_MIRROR: Device data1: provider ad4 disconnected. Feb 15 20:56:31 zoe kernel: GEOM_MIRROR: Device data1: provider ad4 detected. Feb 15 20:56:31 zoe kernel: GEOM_MIRROR: Device data1: rebuilding provider ad4. ... Feb 15 22:33:15 zoe kernel: GEOM_MIRROR: Device data1: rebuilding provider ad4 finished. Feb 15 22:33:15 zoe kernel: GEOM_MIRROR: Device data1: provider ad4 activated. ... Feb 15 23:04:12 zoe kernel: ad4: req=0xc2422578 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Feb 15 23:04:28 zoe last message repeated 4 times Feb 15 23:04:32 zoe kernel: ad4: req=0xc2422578 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Feb 15 23:05:04 zoe last message
Re: Showstopper ATA bug in 6.1-PRE?
On Thu, Feb 09, 2006 at 11:08:24PM +0100, Wilko Bulte wrote.. On Thu, Feb 09, 2006 at 09:24:23PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:45:53PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. Is this relative to HEAD or RELENG_6? I cannot / will not go to HEAD with this machine (my main production box.. :-) Doesn't matter, ATA is the same on both... OK, I was not sure if they were 100% identical. The patch at first impression seems to have eliminated the problem. Good seems I'm on the right track at least. Interestingly enough ad10 remained ad10 with the patch applied? Yeah, thats intentional, I though we better not break POLA here.. I agree :-) I'll put some load on to see what happens. Let me know how that turns out, I'll clean things up a bit and get it committed to -current, then get permission to MFC when we are sure it fixes the problem... I ran a 44GB disk-to-disk dump without incidents (source on the RAID1, target on the JBOD). No problems whatsoever. Looks like things behave much better now. Tonight the machine will run a daily full dump to DLT tape, I'll know how that turns out tomorrow. Backup ran without problems. -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
Hi, * Søren Schmidt [EMAIL PROTECTED] [2006-02-08 22:44]: Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... I have seen nearly the same problem after upgrading to -stable at the weekend. I digged through the commits and went back to 2006.01.25.00.00.00 of -stable as there were many ata and gmirror commits that time. That helped to get the mirror back alive. I am willing to test patches as I'm prepared now. Feb 5 12:21:00 beast kernel: ad6: req=0xc4e487d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Feb 5 12:21:04 beast kernel: ad6: req=0xc4e487d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! This is my controller: atapci1: Promise PDC40518 SATA150 controller port 0xdc00-0xdc7f,0xe000-0xe0ff mem 0xdf521000-0xdf521fff,0xdf50-0xdf51 irq 16 at device 12.0 on pci0 ata2: ATA channel 0 on atapci1 ata3: ATA channel 1 on atapci1 ata4: ATA channel 2 on atapci1 ata5: ATA channel 3 on atapci1 jens ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
Hi Soren,
I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE
of roughly end of december.
And I hit some stuff that really worries me:
- the freshly built kernel keels over with (hand transcribed):
ata3: reiniting channel SATA connect ...
SATA connected
sata_connect_devices 0x1 ATA_MASTER
ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout
!! DANGER Will RObinson !!
(... is where I cannot read my own handwriting, it scrolled quite fast on
the screen..)
Boot device is a SATA RAID1 on a Promise 2300.
Hmm, that should not happen. Could you try to backstep just ATA to
before the MFC, that is 24/1/06 and let me know if that helps please ?
First impression is that the problem is gone. None of the previously
reported errors are seen. I am running a level 0 dump from disk to disk
to see if the box remains stable. Given that this is my primary machine
I sure hope it will be :-)
Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on
6.1-PRE
Hmm that is because there is only 2 ports on your promise which is now
correctly identified, before it was errounsly found as 3 ports.
Ah, OK. I would suggest a note to the Release Note writers would be a good
thing, devices changing location after an upgrade in the -stable branch
is unnerving ;-)
Well, the good thing is that I can reproduce the error here, the bad
thing is that it slipped through testing on -current...
Oh, well, I'll look into it ASAP...
Thank you Soren!
OK, had a few this afternoon, could you try this patch and let me know
if it helps, at least it makes the problem go away on my testbed..
-Søren
Index: ata-chipset.c
===
RCS file: /nfs/export/ncvs/src/sys/dev/ata/ata-chipset.c,v
retrieving revision 1.156
diff -u -r1.156 ata-chipset.c
--- ata-chipset.c 6 Feb 2006 19:17:48 - 1.156
+++ ata-chipset.c 9 Feb 2006 13:20:06 -
@@ -2861,10 +2861,10 @@
{ ATA_PDC20377, 0, PRMIO, PRCMBO, ATA_SA150, PDC20377 },
{ ATA_PDC20378, 0, PRMIO, PRCMBO, ATA_SA150, PDC20378 },
{ ATA_PDC20379, 0, PRMIO, PRCMBO, ATA_SA150, PDC20379 },
- { ATA_PDC20571, 0, PRMIO, PRSATA2, ATA_SA150, PDC20571 },
+ { ATA_PDC20571, 0, PRMIO, PRCMBO2, ATA_SA150, PDC20571 },
{ ATA_PDC20575, 0, PRMIO, PRCMBO2, ATA_SA150, PDC20575 },
{ ATA_PDC20579, 0, PRMIO, PRCMBO2, ATA_SA150, PDC20579 },
- { ATA_PDC20771, 0, PRMIO, PRSATA2, ATA_SA300, PDC20771 },
+ { ATA_PDC20771, 0, PRMIO, PRCMBO2, ATA_SA300, PDC20771 },
{ ATA_PDC40775, 0, PRMIO, PRCMBO2, ATA_SA300, PDC40775 },
{ ATA_PDC20617, 0, PRMIO, PRPATA, ATA_UDMA6, PDC20617 },
{ ATA_PDC20618, 0, PRMIO, PRPATA, ATA_UDMA6, PDC20618 },
@@ -2925,6 +2925,7 @@
ata_promise_chipinit(device_t dev)
{
struct ata_pci_controller *ctlr = device_get_softc(dev);
+int fake_reg, stat_reg;
if (ata_setup_interrupt(dev))
return ENXIO;
@@ -2962,8 +2963,7 @@
ctlr-r_rid2, RF_ACTIVE)))
goto failnfree;
- switch (ctlr-chip-cfg2) {
- case PRSX4X: {
+ if (ctlr-chip-cfg2 == PRSX4X) {
struct ata_promise_sx4 *hpkt;
u_int32_t dimm = ATA_INL(ctlr-r_res2, 0x000c0080);
@@ -2998,58 +2998,55 @@
ctlr-setmode = ata_promise_setmode;
ctlr-channels = 4;
return 0;
- }
- case PRPATA:
- case PRCMBO:
- case PRSATA:
- /*
-* older mio type controllers need an interrupt intercept
-* function to compensate for the reset on read type interrupt
-* status register they have.
-*/
- if (bus_teardown_intr(dev, ctlr-r_irq, ctlr-handle) ||
+ }
+
+ /* mio type controllers need an interrupt intercept */
+ if (bus_teardown_intr(dev, ctlr-r_irq, ctlr-handle) ||
bus_setup_intr(dev, ctlr-r_irq, ATA_INTR_FLAGS,
ata_promise_mio_intr, ctlr, ctlr-handle)) {
device_printf(dev, unable to setup interrupt\n);
goto failnfree;
- }
- /* prime fake interrupt register */
- ATA_OUTL(ctlr-r_res2, 0x060, 0x);
- break;
}
-
- ctlr-allocate = ata_promise_mio_allocate;
- ctlr-reset = ata_promise_mio_reset;
- ctlr-dmainit = ata_promise_mio_dmainit;
- ctlr-setmode = ata_promise_mio_setmode;
-
switch (ctlr-chip-cfg2) {
case PRPATA:
ctlr-channels = ((ATA_INL(ctlr-r_res2, 0x48) 0x01) 0) +
((ATA_INL(ctlr-r_res2, 0x48) 0x02) 0) + 2;
- return 0;
-
+ goto sata150;
case PRCMBO:
-
Re: Showstopper ATA bug in 6.1-PRE?
On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. Is this relative to HEAD or RELENG_6? I cannot / will not go to HEAD with this machine (my main production box.. :-) Wilko ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. Is this relative to HEAD or RELENG_6? I cannot / will not go to HEAD with this machine (my main production box.. :-) Doesn't matter, ATA is the same on both... -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
On Thu, Feb 09, 2006 at 03:45:53PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. Is this relative to HEAD or RELENG_6? I cannot / will not go to HEAD with this machine (my main production box.. :-) Doesn't matter, ATA is the same on both... OK, I was not sure if they were 100% identical. The patch at first impression seems to have eliminated the problem. Interestingly enough ad10 remained ad10 with the patch applied? I'll put some load on to see what happens. -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:45:53PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. Is this relative to HEAD or RELENG_6? I cannot / will not go to HEAD with this machine (my main production box.. :-) Doesn't matter, ATA is the same on both... OK, I was not sure if they were 100% identical. The patch at first impression seems to have eliminated the problem. Good seems I'm on the right track at least. Interestingly enough ad10 remained ad10 with the patch applied? Yeah, thats intentional, I though we better not break POLA here.. I'll put some load on to see what happens. Let me know how that turns out, I'll clean things up a bit and get it committed to -current, then get permission to MFC when we are sure it fixes the problem... -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
On Thu, Feb 09, 2006 at 09:24:23PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:45:53PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! OK, had a few this afternoon, could you try this patch and let me know if it helps, at least it makes the problem go away on my testbed.. Is this relative to HEAD or RELENG_6? I cannot / will not go to HEAD with this machine (my main production box.. :-) Doesn't matter, ATA is the same on both... OK, I was not sure if they were 100% identical. The patch at first impression seems to have eliminated the problem. Good seems I'm on the right track at least. Interestingly enough ad10 remained ad10 with the patch applied? Yeah, thats intentional, I though we better not break POLA here.. I agree :-) I'll put some load on to see what happens. Let me know how that turns out, I'll clean things up a bit and get it committed to -current, then get permission to MFC when we are sure it fixes the problem... I ran a 44GB disk-to-disk dump without incidents (source on the RAID1, target on the JBOD). No problems whatsoever. Looks like things behave much better now. Tonight the machine will run a daily full dump to DLT tape, I'll know how that turns out tomorrow. thanks, Wilko -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Showstopper ATA bug in 6.1-PRE?
Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Verbose dmesg.boot from the 6.0-STABLE kernel and atacontrol list are attached. thanks, -- Wilko Bulte [EMAIL PROTECTED] ATA channel 0: Master: acd0 NEC DVD RW ND-2510A/2.15 ATA/ATAPI revision 0 Slave: no device present ATA channel 1: Master: acd1 CD-532E/1.0A ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 Maxtor 7Y250M0/YAR51KW0 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 Maxtor 7Y250M0/YAR51KW0 Serial ATA v1.0 Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: ad10 Maxtor 6B160M0/BANC1BY0 Serial ATA v1.0 Slave: no device present ATA channel 6: Master: no device present Slave: no device present found- vendor=0x8086, dev=0x244e, revid=0xc2 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) found- vendor=0x8086, dev=0x24d0, revid=0x02 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x8086, dev=0x24db, revid=0x02 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type 4, range 32, base fc00, size 4, enabled map[24]: type 1, range 32, base , size 10, memory disabled found- vendor=0x8086, dev=0x24d1, revid=0x02 bus=0, slot=31, func=2 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type 4, range 32, base bc00, size 3, enabled map[14]: type 4, range 32, base b880, size 2, enabled map[18]: type 4, range 32, base b800, size 3, enabled map[1c]: type 4, range 32, base b480, size 2, enabled map[20]: type 4, range 32, base b400, size 4, enabled pcib0: matched entry for 0.31.INTA pcib0: slot 31 INTA hardwired to IRQ 18 found- vendor=0x8086, dev=0x24d3, revid=0x02 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[20]: type 4, range 32, base 0400, size 5, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 17 found- vendor=0x8086, dev=0x24d5, revid=0x02 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base c000, size 8, enabled map[14]: type 4, range 32, base c400, size 6, enabled map[18]: type 1, range 32, base f6fff800, size 9, enabled map[1c]: type 1, range 32, base f6fff400, size 8, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 17 agp0: Intel 82865 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 agp0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xf800 agp0: allocating GATT for aperture of size 64M pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode0xf000-0xfff pcib1: memory decode 0xf700-0xf7ef pcib1: prefetched decode 0xf400-0xf5ff pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 - AE_NOT_FOUND pci1: ACPI PCI bus on pcib1 pci1: physical bus=1 found- vendor=0x102b, dev=0x0525, revid=0x82 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=4 (dwords) lattimer=0x40 (1920 ns), mingnt=0x10 (4000 ns), maxlat=0x20
Re: Showstopper ATA bug in 6.1-PRE?
Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Showstopper ATA bug in 6.1-PRE?
On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote.. Wilko Bulte wrote: Hi Soren, I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE of roughly end of december. And I hit some stuff that really worries me: - the freshly built kernel keels over with (hand transcribed): ata3: reiniting channel SATA connect ... SATA connected sata_connect_devices 0x1 ATA_MASTER ad6: req=0xC35ba0c8 SETFEATURES SETTRANSFERMODE semaphore timeout !! DANGER Will RObinson !! (... is where I cannot read my own handwriting, it scrolled quite fast on the screen..) Boot device is a SATA RAID1 on a Promise 2300. Hmm, that should not happen. Could you try to backstep just ATA to before the MFC, that is 24/1/06 and let me know if that helps please ? First impression is that the problem is gone. None of the previously reported errors are seen. I am running a level 0 dump from disk to disk to see if the box remains stable. Given that this is my primary machine I sure hope it will be :-) Another snag is that my ad10 disk on 6.0-STABLE suddenly became ad12 on 6.1-PRE Hmm that is because there is only 2 ports on your promise which is now correctly identified, before it was errounsly found as 3 ports. Ah, OK. I would suggest a note to the Release Note writers would be a good thing, devices changing location after an upgrade in the -stable branch is unnerving ;-) Well, the good thing is that I can reproduce the error here, the bad thing is that it slipped through testing on -current... Oh, well, I'll look into it ASAP... Thank you Soren! -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
