Jeff Doolittle
2007-Oct-21 09:00 UTC
Promise PDC20378 - SETFEATURES SET TRANSFER MODE taskqueue timeout
Everyone,
I just recently updated my primary server to the latest FreeBSD RELENG_6
release last weekend and have started receiving the following errors
every day requiring me to power off the computer (the console is hung
and Ctrl-Alt-Del don't work):
===========================================================Oct 18 23:15:02
saturn kernel: ad6: WARNING - SETFEATURES SET TRANSFER
MODE taskqueue timeout - completing request
directly
Oct 18 23:15:02 saturn kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE
taskqueue timeout - completing request dire
ctly
Oct 18 23:15:02 saturn kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE
taskqueue timeout - completing request dire
ctly
Oct 18 23:15:02 saturn kernel: ad6: WARNING - SET_MULTI taskqueue
timeout - completing request directly
Oct 18 23:15:02 saturn kernel: ad6: TIMEOUT - WRITE_DMA retrying (1
retry left) LBA=1129375
Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES SET TRANSFER
MODE taskqueue timeout - completing request
directly
Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES SET TRANSFER
MODE taskqueue timeout - completing request
directly
Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE
taskqueue timeout - completing request dire
ctly
Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE
taskqueue timeout - completing request dire
ctly
Oct 18 23:15:02 saturn kernel: ad4: WARNING - SET_MULTI taskqueue
timeout - completing request directly
Oct 18 23:15:02 saturn kernel: ad4: TIMEOUT - WRITE_DMA retrying (1
retry left) LBA=1129375
===========================================================
For some strange reason the above error last night didn't cause the
typical hang, but this evening it happend again @ ~9:30pm (17:30) with a
hard failure resulting in a power-cycle to get the server running again.
I originally thought one of the drives was going bad so I replaced the
existing 200gb Maxstor PATA with two 500gb WD SATA. Therefore, that
rules out cables and drives and returns me to the motherboard (Promise
Controller) or FreeBSD.
The following is the output from a "pciconf -lv"
===========================================================agp0@pci0:0:0:
class=0x060000 card=0x80f61043 chip=0x25788086 rev=0x02
hdr=0x00
vendor = 'Intel Corporation'
device = '82875P/E7210 DRAM Controller / Host-Hub Interface'
class = bridge
subclass = HOST-PCI
pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x25798086 rev=0x02
hdr=0x01
vendor = 'Intel Corporation'
device = '82875P PCI-to-AGP Bridge'
class = bridge
subclass = PCI-PCI
uhci0@pci0:29:0: class=0x0c0300 card=0x80a61043 chip=0x24d28086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller'
class = serial bus
subclass = USB
uhci1@pci0:29:1: class=0x0c0300 card=0x80a61043 chip=0x24d48086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller'
class = serial bus
subclass = USB
uhci2@pci0:29:2: class=0x0c0300 card=0x80a61043 chip=0x24d78086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller'
class = serial bus
subclass = USB
uhci3@pci0:29:3: class=0x0c0300 card=0x80a61043 chip=0x24de8086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller'
class = serial bus
subclass = USB
ehci0@pci0:29:7: class=0x0c0320 card=0x80a61043 chip=0x24dd8086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) USB 2.0 EHCI Controller'
class = serial bus
subclass = USB
pcib2@pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086
rev=0xc2 hdr=0x01
vendor = 'Intel Corporation'
device = '82801BA/CA/DB/DBL/EB/ER/FB (ICH2/3/4/4/5/5/6), 6300ESB
Hub Interface to PCI Bridge'
class = bridge
subclass = PCI-PCI
isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x24d08086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) LPC Interface Bridge'
class = bridge
subclass = PCI-ISA
atapci3@pci0:31:1: class=0x01018a card=0x80a61043 chip=0x24db8086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) EIDE Controller'
class = mass storage
subclass = ATA
none0@pci0:31:3: class=0x0c0500 card=0x80a61043 chip=0x24d38086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) SMBus Controller'
class = serial bus
subclass = SMBus
none1@pci0:31:5: class=0x040100 card=0x80f31043 chip=0x24d58086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller'
class = multimedia
subclass = audio
none2@pci1:0:0: class=0x030000 card=0x001e10de chip=0x002d10de rev=0x15
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'NV5 TNT2 Model 64 / TNT2 Model 64 Pro'
class = display
subclass = VGA
atapci0@pci2:4:0: class=0x010400 card=0x80f51043 chip=0x3373105a
rev=0x02 hdr=0x00
vendor = 'Promise Technology Inc'
device = 'PDC20378 FastTrak 378/SATA 378 RAID Controller'
class = mass storage
subclass = RAID
twa0@pci2:9:0: class=0x010400 card=0x100213c1 chip=0x100213c1 rev=0x00
hdr=0x00
vendor = '3ware Inc.'
device = '9000 series SATA/PATA Storage Controller'
class = mass storage
subclass = RAID
em0@pci2:11:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x04
hdr=0x00
vendor = 'Intel Corporation'
device = '82545GM Gigabit Ethernet Controller'
class = network
subclass = ethernet
atapci1@pci2:12:0: class=0x010400 card=0x00011103 chip=0x00081103
rev=0x07 hdr=0x00
vendor = 'HighPoint Technologies Inc'
device = 'HPT374 Rocket 154x/1640, RocketRAID 154x/1640 RAID
EIDE Controller'
class = mass storage
subclass = RAID
atapci2@pci2:12:1: class=0x010400 card=0x00011103 chip=0x00081103
rev=0x07 hdr=0x00
vendor = 'HighPoint Technologies Inc'
device = 'HPT374 Rocket 154x/1640, RocketRAID 154x/1640 RAID
EIDE Controller'
class = mass storage
subclass = RAID
===========================================================
As a side note, I cleared the /usr/src tree last night and cvsup'd the
RELENG_6 tag again to make sure I had a clean source environment yet the
problem still persists.
Any idea before I open a trouble ticket? (or maybe just move the array
to the RocketRAID controller).
Thanks
- Jeff
Miroslav Lachman
2007-Oct-21 18:24 UTC
Promise PDC20378 - SETFEATURES SET TRANSFER MODE taskqueue timeout
Jeff Doolittle wrote:> Everyone, > > I just recently updated my primary server to the latest FreeBSD RELENG_6 > release last weekend and have started receiving the following errors > every day requiring me to power off the computer (the console is hung > and Ctrl-Alt-Del don't work): > > ===========================================================> Oct 18 23:15:02 saturn kernel: ad6: WARNING - SETFEATURES SET TRANSFER > MODE taskqueue timeout - completing request > directly > Oct 18 23:15:02 saturn kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE > taskqueue timeout - completing request dire > ctly > Oct 18 23:15:02 saturn kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE > taskqueue timeout - completing request dire > ctly > Oct 18 23:15:02 saturn kernel: ad6: WARNING - SET_MULTI taskqueue > timeout - completing request directly > Oct 18 23:15:02 saturn kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 > retry left) LBA=1129375 > Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES SET TRANSFER > MODE taskqueue timeout - completing request > directly > Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES SET TRANSFER > MODE taskqueue timeout - completing request > directly > Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE > taskqueue timeout - completing request dire > ctly > Oct 18 23:15:02 saturn kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE > taskqueue timeout - completing request dire > ctly > Oct 18 23:15:02 saturn kernel: ad4: WARNING - SET_MULTI taskqueue > timeout - completing request directly > Oct 18 23:15:02 saturn kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 > retry left) LBA=1129375 > ===========================================================[...]I had same problem many times and only mainboard replacement solves the problem. Last time I saw these errors (1 week ago) it was in dying Asus RS-120 which was running 6.2-RELEASE for about 6 month. So the problem is not related to 6.2-RELEASE, but to hardware. Miroslav Lachman