Date: Mon, 17 Dec 2007 13:46:50 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: =?KOI8-R?Q?=ED=C9=C8=C1=C9=CC_=EB=C9=D0=C1?= <msnkipa@mail.ru> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.0beta4 panic on ftp transfer Message-ID: <47666FBA.1040606@quip.cz> In-Reply-To: <E1J42UD-0008Zn-00.msnkipa-mail-ru@f127.mail.ru>
index | next in thread | previous in thread | raw e-mail
νΙΘΑΙΜ λΙΠΑ wrote: > SO I have 7.0beta4 on my server. My HDD have such configuration: > > ad4: 476940MB <SAMSUNG HD501LJ CR100-10> at ata2-master SATA300 > ad6: 476940MB <SAMSUNG HD501LJ CR100-11> at ata3-master SATA300 > ad10: 152627MB <WDC WD1600AAJS-22PSA0 05.06H05> at ata5-master SATA150 > ad12: 152627MB <WDC WD1600AAJS-22PSA0 05.06H05> at ata6-master SATA150 > ar0: 476928MB <JMicron Technology Corp RAID1> status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (mirror) using ad6 at ata3-master > ar1: 152627MB <VIA Tech V-RAID RAID1> status: READY > ar1: disk0 READY (master) using ad10 at ata5-master > ar1: disk1 READY (mirror) using ad12 at ata6-master > SMP: AP CPU #1 Launched! > > > During ftp transfer (among 10GB to server) I have kernel panic and reboon wiht > such log messages: [...] > Dec 17 01:49:17 SERVER kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE > taskqueue timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE > taskqueue timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue > timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue > timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad4: WARNING - SET_MULTI taskqueue timeout - > completing request directly > Dec 17 01:49:17 SERVER kernel: ad4: TIMEOUT - WRITE_DMA retrying (0 retries left) > LBA=211491863 > Dec 17 01:49:17 SERVER kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE > taskqueue timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad6: WARNING - SETFEATURES SET TRANSFER MODE > taskqueue timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue > timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue > timeout - completing request directly > Dec 17 01:49:17 SERVER kernel: ad6: WARNING - SET_MULTI taskqueue timeout - > completing request directly > Dec 17 01:49:17 SERVER kernel: ad6: FAILURE - WRITE_DMA timed out LBA=211491607 > Dec 17 01:49:17 SERVER kernel: ad4: WARNING - WRITE_DMA taskqueue timeout - > completing request directly > Dec 17 01:49:17 SERVER kernel: ad6: WARNING - WRITE_DMA taskqueue timeout - > completing request directly > Dec 17 01:49:17 SERVER kernel: > Dec 17 01:49:17 SERVER kernel: > Dec 17 01:49:17 SERVER kernel: Fatal trap 12: page fault while in kernel mode > Dec 17 01:49:17 SERVER kernel: cpuid = 0; apic id = 00 > Dec 17 01:49:17 SERVER kernel: fault virtual address = 0x18 > Dec 17 01:49:17 SERVER kernel: fault code = supervisor read data, > page not present > Dec 17 01:49:17 SERVER kernel: instruction pointer = 0x8:0xffffffff80221bec > Dec 17 01:49:17 SERVER kernel: stack pointer = 0x10:0xffffffffab692af0 > Dec 17 01:49:17 SERVER kernel: frame pointer = 0x10:0xffffff0029b72bd0 > Dec 17 01:49:17 SERVER kernel: code segment = base 0x0, limit 0xfffff, > type 0x1b > Dec 17 01:49:17 SERVER kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 > Dec 17 01:49:17 SERVER kernel: processor eflags = interrupt enabled, resume, IOPL > = 0 > Dec 17 01:49:17 SERVER kernel: current process = 17 (swi6: task queue) > Dec 17 01:49:17 SERVER kernel: trap number = 12 > Dec 17 01:49:17 SERVER kernel: panic: page fault > Dec 17 01:49:17 SERVER kernel: cpuid = 0 > Dec 17 01:49:17 SERVER kernel: Uptime: 3d5h9m56s > > ad4 and ad6 is my mirror RAID on which I try to write! > Anyone can explain to what does it mean??? > Mihail From my experience - it is caused by poor onboard HTT/RAID controller, failing HDD or SATA cables. Try another pair of cables, check HDD with smartmontools (from ports tree), or try to switch from ataraid to gmirror. Miroslav Lachmanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47666FBA.1040606>