Re: ICH5 ATA DMA timeouts
Interesting. The ICH5 is part of the processor chipset, and it could be "anywhere" on the system board, so finding/identifying it (so as to point a fan at it, or figure out a way to add a heatsink) may be less than straightforward -- but it's worth keeping in mind as something to look into if problems arise. Any idea where one finds cheap (but reliable) PCI SATA cards these days? It would have to be PCI -- this box does not have PCI-E slots. Florian Ermisch wrote: > I had some onboard (S)ATA controllers becoming unreliable in the > past. Two of them due to chipsets overheating under load which > were fixable with additional cooling. In the third one we just > added a cheap SATA card and spread the redundant disks between > onboard and add-on controller to make a temporary failure a minor > issue. > > Regards, Florian > > Am 6. Dezember 2015 22:21:35 MEZ, schrieb Steven Hartland > : > > Check cables and devices are in good condition. These things are > > usually a connectivity issue or device failing > > > > On 06/12/2015 03:06, Perry Hutchison wrote: > > > Does anyone know the condition of the ICH5 ATA support in FreeBSD > > > 10? > > > > > > In preparing to repurpose an elderly Dell Dimension 4600 from > > > Windows to FreeBSD, and needing to decide what to do about > > > drives, I found several mentions in the archives* of ICH5 ATA > > > DMA timeouts -- mostly affecting the SATA ports, but the > > > prevalence of SATA reports may just indicate which ports were > > > getting the most use: a couple of the reports involved the > > > PATA ports. > > > > > > While there have been commits to the ATA code since then, I didn't > > > find any definitive statement that the DMA timeouts had been fixed. > > > Did I miss something, or would I be better off using a separate SATA > > > or PATA PCI card instead of the ICH5's built-in ports? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ICH5 ATA DMA timeouts
Er, there's nothing to check, yet. I'm trying to *avoid* trouble by finding out in advance about any dodgy hardware support. In several of the cited threads, it was pretty clear that the hardware was not faulty, since the identical hardware had run properly on 4.x but started generating DMA timeouts on 5.x; also diagnostics were run (=> drives OK), cables replaced, etc. In at least one case the failure was reproduced on a different box than where it had originally been observed. It was suspected that there might have been some kind of interaction between geom and the ATA code, e.g. a timing problem, since many of the failures involved software mirroring (vinum or gmirror). Steven Hartland wrote: > Check cables and devices are in good condition. These things are > usually a connectivity issue or device failing > > On 06/12/2015 03:06, Perry Hutchison wrote: > > Does anyone know the condition of the ICH5 ATA support in FreeBSD 10? > > > > In preparing to repurpose an elderly Dell Dimension 4600 from Windows > > to FreeBSD, and needing to decide what to do about drives, I found > > several mentions in the archives* of ICH5 ATA DMA timeouts -- mostly > > affecting the SATA ports, but the prevalence of SATA reports may > > just indicate which ports were getting the most use: a couple of > > the reports involved the PATA ports. > > > > While there have been commits to the ATA code since then, I didn't > > find any definitive statement that the DMA timeouts had been fixed. > > Did I miss something, or would I be better off using a separate SATA > > or PATA PCI card instead of the ICH5's built-in ports? > > > > Relevant parts of dmesg (with no hard drives attached): > > > > FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 19:31:38 UTC 2015 > > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.06-MHz 686-class CPU) > >Origin="GenuineIntel" Id=0xf34 Family=0xf Model=0x3 Stepping=4 > > > > Features=0xbfebfbff > >Features2=0x441d > >TSC: P-state invariant > > uhci0: port 0xff80-0xff9f irq > > 16 at device 29.0 on pci0 > > usbus0 on uhci0 > > uhci1: port 0xff60-0xff7f irq > > 19 at device 29.1 on pci0 > > usbus1 on uhci1 > > uhci2: port 0xff40-0xff5f irq > > 18 at device 29.2 on pci0 > > usbus2 on uhci2 > > uhci3: port 0xff20-0xff3f irq > > 16 at device 29.3 on pci0 > > usbus3 on uhci3 > > ehci0: mem > > 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 > > usbus4: EHCI version 1.0 > > usbus4 on ehci0 > > atapci0: port > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xfeb7fc00-0xfeb7 > > irq 18 at device 31.1 on pci0 > > ata0: at channel 0 on atapci0 > > ata1: at channel 1 on atapci0 > > atapci1: port > > 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf irq > > 18 at device 31.2 on pci0 > > ata2: at channel 0 on atapci1 > > ata3: at channel 1 on atapci1 > > pci0: at device 31.3 (no driver attached) > > pcm0: port 0xee00-0xeeff,0xedc0-0xedff mem > > 0xfeb7fa00-0xfeb7fbff,0xfeb7f900-0xfeb7f9ff irq 17 at device 31.5 on pci0 > > pcm0: primary codec not ready! > > pcm0: > > ata0: reset tp1 mask=00 ostat0=ff ostat1=ff > > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > > ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb > > ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb > > ata1: reset tp2 stat0=00 stat1=00 devices=0x3 > > ata2: SATA reset: ports status=0x00 > > ata2: p0: SATA connect timeout status=0004 > > ata3: SATA reset: ports status=0x00 > > ata3: p0: SATA connect timeout status=0004 > > pass0 at ata1 bus 0 scbus1 target 0 lun 0 > > pass0: Removable CD-ROM SCSI device > > pass0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > pass1 at ata1 bus 0 scbus1 target 1 lun 0 > > pass1: Removable CD-ROM SCSI device > > pass1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > cd0 at ata1 bus 0 scbus1 target 0 lun 0 > > cd0: Removable CD-ROM SCSI device > > cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > cd0: Attempt to query device size failed: NOT READY, Medium not present > > cd1 at ata1 bus 0 scbus1 target 1 lun 0 > > cd1: Removable CD-ROM SCSI device > > cd1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > cd1: Attempt to query device size failed: NOT READY, Medium not present - > > tray closed > > GEOM: new disk cd0 > > GEOM: new disk cd1 > > > > * Archive mentions, i
ICH5 ATA DMA timeouts
Good day everyone ! First of all I would advise you to change all of your hard drives interface cables with new ones. >Понедельник, 7 декабря 2015, 12:00 UTC от freebsd-stable-requ...@freebsd.org: > >Send freebsd-stable mailing list submissions to >freebsd-stable@freebsd.org > >To subscribe or unsubscribe via the World Wide Web, visit >https://lists.freebsd.org/mailman/listinfo/freebsd-stable >or, via email, send a message with subject or body 'help' to >freebsd-stable-requ...@freebsd.org > >You can reach the person managing the list at >freebsd-stable-ow...@freebsd.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of freebsd-stable digest..." > > >Today's Topics: > > 1. urtwn regression(?) from 10.2 to current r291431 > (Anton Shterenlikht) > 2. Re: urtwn regression(?) from 10.2 to current r291431 > (Hans Petter Selasky) > 3. Re: urtwn regression(?) from 10.2 to current r291431 > (Anton Shterenlikht) > 4. Re: urtwn regression(?) from 10.2 to current r291431 > (Michael Mitchell) > 5. Re: urtwn regression(?) from 10.2 to current r291431 > (Adrian Chadd) > 6. ICH5 ATA DMA timeouts (Perry Hutchison) > 7. Re: application coredump behavior differences between FreeBSD > 7.0andFreeBSD 10.1 (Konstantin Belousov) > 8. Re: ICH5 ATA DMA timeouts (Steven Hartland) > 9. Re: ICH5 ATA DMA timeouts (Florian Ermisch) > 10. jiberish output in mail from cron (Johan Hendriks) > > >-- > >Message: 1 >Date: Sun, 06 Dec 2015 06:14:52 -0800 (PST) >From: Anton Shterenlikht < me...@bris.ac.uk > >To: freebsd-curr...@freebsd.org, freebsd-stable@freebsd.org >Subject: urtwn regression(?) from 10.2 to current r291431 >Message-ID: < 201512061414.tb6eepty041...@mech-as222.men.bris.ac.uk > > >I posted this about a week ago: > >http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html > >The problem is that urtwn stopped >working in current r291431. > >I did more testing with the same revision, >and sometimes it would work, but extremely >slowly, and sometimes seemingly associate >but get an address of 0.0.0.0. > >I now installed 10.2-RELEASE-p8 and >the urtwn works fine, no issues at all. > >Does this look like a bug at some recent >current revision? Should I file a PR? > >I's just I recall there have been major >chages to wlan, so perphaps I'm forgetting >to change the config in recent current? > >Please advise > >Anton > > >-- > >Message: 2 >Date: Sun, 6 Dec 2015 15:33:18 +0100 >From: Hans Petter Selasky < h...@selasky.org > >To: me...@bris.ac.uk, freebsd-curr...@freebsd.org, >freebsd-stable@freebsd.org, Adrian Chadd < adr...@freebsd.org > >Subject: Re: urtwn regression(?) from 10.2 to current r291431 >Message-ID: < 5664472e.3090...@selasky.org > >Content-Type: text/plain; charset=windows-1252; format=flowed > >On 12/06/15 15:14, Anton Shterenlikht wrote: >> I posted this about a week ago: >> >> http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html >> >> The problem is that urtwn stopped >> working in current r291431. >> >> I did more testing with the same revision, >> and sometimes it would work, but extremely >> slowly, and sometimes seemingly associate >> but get an address of 0.0.0.0. >> >> I now installed 10.2-RELEASE-p8 and >> the urtwn works fine, no issues at all. >> >> Does this look like a bug at some recent >> current revision? Should I file a PR? >> >> I's just I recall there have been major >> chages to wlan, so perphaps I'm forgetting >> to change the config in recent current? >> >> Please advise >> >> Anton > >Hi, > >There is work ongoing in the WLAN drivers. Did you try the latest -current? > >--HPS > > > >-- > >Message: 3 >Date: Sun, 06 Dec 2015 06:44:26 -0800 (PST) >From: Anton Shterenlikht < me...@bris.ac.uk > >To: adr...@freebsd.org, freebsd-curr...@freebsd.org, >freebsd-stable@freebsd.org, h...@selasky.org, me...@bris.ac.uk >Subject: Re: urtwn regression(?) from 10.2 to current r291431 >Message-ID: < 201512061444.tb6eipmm041...@mech-as222.men.bris.ac.uk > > >>From h...@selasky.org Sun Dec 6 14:41:27 2015 >> >>On 12/06/15 15:14, Anton Shterenlikht wrote: >>> I posted this about a week ago: >>> >>> >>> http://lists.freebsd.org/pipermail/freebsd-current/2015-Nov
Re: ICH5 ATA DMA timeouts
I had some onboard (S)ATA controllers becoming unreliable in the past. Two of them due to chipsets overheating under load which were fixable with additional cooling. In the third one we just added a cheap SATA card and spread the redundant disks between onboard and add-on controller to make a temporary failure a minor issue. Regards, Florian Am 6. Dezember 2015 22:21:35 MEZ, schrieb Steven Hartland : > Check cables and devices are in good condition. These things are > usually > a connectivity issue or device failing > > On 06/12/2015 03:06, Perry Hutchison wrote: > > Does anyone know the condition of the ICH5 ATA support in FreeBSD > 10? > > > > In preparing to repurpose an elderly Dell Dimension 4600 from > Windows > > to FreeBSD, and needing to decide what to do about drives, I found > > several mentions in the archives* of ICH5 ATA DMA timeouts -- mostly > > affecting the SATA ports, but the prevalence of SATA reports may > > just indicate which ports were getting the most use: a couple of > > the reports involved the PATA ports. > > > > While there have been commits to the ATA code since then, I didn't > > find any definitive statement that the DMA timeouts had been fixed. > > Did I miss something, or would I be better off using a separate SATA > > or PATA PCI card instead of the ICH5's built-in ports? > > > > Relevant parts of dmesg (with no hard drives attached): > > > > FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 19:31:38 UTC 2015 > > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.06-MHz 686-class CPU) > >Origin="GenuineIntel" Id=0xf34 Family=0xf Model=0x3 > Stepping=4 > > > Features=0xbfebfbff > >Features2=0x441d > >TSC: P-state invariant > > uhci0: port > 0xff80-0xff9f irq 16 at device 29.0 on pci0 > > usbus0 on uhci0 > > uhci1: port > 0xff60-0xff7f irq 19 at device 29.1 on pci0 > > usbus1 on uhci1 > > uhci2: port > 0xff40-0xff5f irq 18 at device 29.2 on pci0 > > usbus2 on uhci2 > > uhci3: port > 0xff20-0xff3f irq 16 at device 29.3 on pci0 > > usbus3 on uhci3 > > ehci0: mem > 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 > > usbus4: EHCI version 1.0 > > usbus4 on ehci0 > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem > 0xfeb7fc00-0xfeb7 irq 18 at device 31.1 on pci0 > > ata0: at channel 0 on atapci0 > > ata1: at channel 1 on atapci0 > > atapci1: port > 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf > irq 18 at device 31.2 on pci0 > > ata2: at channel 0 on atapci1 > > ata3: at channel 1 on atapci1 > > pci0: at device 31.3 (no driver attached) > > pcm0: port 0xee00-0xeeff,0xedc0-0xedff mem > 0xfeb7fa00-0xfeb7fbff,0xfeb7f900-0xfeb7f9ff irq 17 at device 31.5 on > pci0 > > pcm0: primary codec not ready! > > pcm0: > > ata0: reset tp1 mask=00 ostat0=ff ostat1=ff > > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > > ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb > > ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb > > ata1: reset tp2 stat0=00 stat1=00 devices=0x3 > > ata2: SATA reset: ports status=0x00 > > ata2: p0: SATA connect timeout status=0004 > > ata3: SATA reset: ports status=0x00 > > ata3: p0: SATA connect timeout status=0004 > > pass0 at ata1 bus 0 scbus1 target 0 lun 0 > > pass0: Removable CD-ROM SCSI device > > pass0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > pass1 at ata1 bus 0 scbus1 target 1 lun 0 > > pass1: Removable CD-ROM SCSI device > > pass1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > cd0 at ata1 bus 0 scbus1 target 0 lun 0 > > cd0: Removable CD-ROM SCSI device > > cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > cd0: Attempt to query device size failed: NOT READY, Medium not > present > > cd1 at ata1 bus 0 scbus1 target 1 lun 0 > > cd1: Removable CD-ROM SCSI device > > cd1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > > cd1: Attempt to query device size failed: NOT READY, Medium not > present - tray closed > > GEOM: new disk cd0 > > GEOM: new disk cd1 > > > > * Archive mentions, in http://lists.freebsd.org/pipermail/... > > > >freebsd-hardware/2004-September/thread.html#1924 > >freebsd-current/2005-February/thread.html#46719 > >freebsd-current/2005-February/thread.html#46737 > >freebsd-stable/2005-March/thread.html#13265 > >freebsd-stable/2007-May/thread.html#35061 > >
Re: ICH5 ATA DMA timeouts
Check cables and devices are in good condition. These things are usually a connectivity issue or device failing On 06/12/2015 03:06, Perry Hutchison wrote: Does anyone know the condition of the ICH5 ATA support in FreeBSD 10? In preparing to repurpose an elderly Dell Dimension 4600 from Windows to FreeBSD, and needing to decide what to do about drives, I found several mentions in the archives* of ICH5 ATA DMA timeouts -- mostly affecting the SATA ports, but the prevalence of SATA reports may just indicate which ports were getting the most use: a couple of the reports involved the PATA ports. While there have been commits to the ATA code since then, I didn't find any definitive statement that the DMA timeouts had been fixed. Did I miss something, or would I be better off using a separate SATA or PATA PCI card instead of the ICH5's built-in ports? Relevant parts of dmesg (with no hard drives attached): FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 19:31:38 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.06-MHz 686-class CPU) Origin="GenuineIntel" Id=0xf34 Family=0xf Model=0x3 Stepping=4 Features=0xbfebfbff Features2=0x441d TSC: P-state invariant uhci0: port 0xff80-0xff9f irq 16 at device 29.0 on pci0 usbus0 on uhci0 uhci1: port 0xff60-0xff7f irq 19 at device 29.1 on pci0 usbus1 on uhci1 uhci2: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 usbus2 on uhci2 uhci3: port 0xff20-0xff3f irq 16 at device 29.3 on pci0 usbus3 on uhci3 ehci0: mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 usbus4: EHCI version 1.0 usbus4 on ehci0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xfeb7fc00-0xfeb7 irq 18 at device 31.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf irq 18 at device 31.2 on pci0 ata2: at channel 0 on atapci1 ata3: at channel 1 on atapci1 pci0: at device 31.3 (no driver attached) pcm0: port 0xee00-0xeeff,0xedc0-0xedff mem 0xfeb7fa00-0xfeb7fbff,0xfeb7f900-0xfeb7f9ff irq 17 at device 31.5 on pci0 pcm0: primary codec not ready! pcm0: ata0: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0x3 ata2: SATA reset: ports status=0x00 ata2: p0: SATA connect timeout status=0004 ata3: SATA reset: ports status=0x00 ata3: p0: SATA connect timeout status=0004 pass0 at ata1 bus 0 scbus1 target 0 lun 0 pass0: Removable CD-ROM SCSI device pass0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) pass1 at ata1 bus 0 scbus1 target 1 lun 0 pass1: Removable CD-ROM SCSI device pass1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata1 bus 0 scbus1 target 1 lun 0 cd1: Removable CD-ROM SCSI device cd1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed GEOM: new disk cd0 GEOM: new disk cd1 * Archive mentions, in http://lists.freebsd.org/pipermail/... freebsd-hardware/2004-September/thread.html#1924 freebsd-current/2005-February/thread.html#46719 freebsd-current/2005-February/thread.html#46737 freebsd-stable/2005-March/thread.html#13265 freebsd-stable/2007-May/thread.html#35061 freebsd-stable/2007-July/thread.html#36308 freebsd-bugs/2012-November/thread.html#50729 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ICH5 ATA DMA timeouts
Does anyone know the condition of the ICH5 ATA support in FreeBSD 10? In preparing to repurpose an elderly Dell Dimension 4600 from Windows to FreeBSD, and needing to decide what to do about drives, I found several mentions in the archives* of ICH5 ATA DMA timeouts -- mostly affecting the SATA ports, but the prevalence of SATA reports may just indicate which ports were getting the most use: a couple of the reports involved the PATA ports. While there have been commits to the ATA code since then, I didn't find any definitive statement that the DMA timeouts had been fixed. Did I miss something, or would I be better off using a separate SATA or PATA PCI card instead of the ICH5's built-in ports? Relevant parts of dmesg (with no hard drives attached): FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 19:31:38 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.06-MHz 686-class CPU) Origin="GenuineIntel" Id=0xf34 Family=0xf Model=0x3 Stepping=4 Features=0xbfebfbff Features2=0x441d TSC: P-state invariant uhci0: port 0xff80-0xff9f irq 16 at device 29.0 on pci0 usbus0 on uhci0 uhci1: port 0xff60-0xff7f irq 19 at device 29.1 on pci0 usbus1 on uhci1 uhci2: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 usbus2 on uhci2 uhci3: port 0xff20-0xff3f irq 16 at device 29.3 on pci0 usbus3 on uhci3 ehci0: mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 usbus4: EHCI version 1.0 usbus4 on ehci0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xfeb7fc00-0xfeb7 irq 18 at device 31.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf irq 18 at device 31.2 on pci0 ata2: at channel 0 on atapci1 ata3: at channel 1 on atapci1 pci0: at device 31.3 (no driver attached) pcm0: port 0xee00-0xeeff,0xedc0-0xedff mem 0xfeb7fa00-0xfeb7fbff,0xfeb7f900-0xfeb7f9ff irq 17 at device 31.5 on pci0 pcm0: primary codec not ready! pcm0: ata0: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0x3 ata2: SATA reset: ports status=0x00 ata2: p0: SATA connect timeout status=0004 ata3: SATA reset: ports status=0x00 ata3: p0: SATA connect timeout status=0004 pass0 at ata1 bus 0 scbus1 target 0 lun 0 pass0: Removable CD-ROM SCSI device pass0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) pass1 at ata1 bus 0 scbus1 target 1 lun 0 pass1: Removable CD-ROM SCSI device pass1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata1 bus 0 scbus1 target 1 lun 0 cd1: Removable CD-ROM SCSI device cd1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed GEOM: new disk cd0 GEOM: new disk cd1 * Archive mentions, in http://lists.freebsd.org/pipermail/... freebsd-hardware/2004-September/thread.html#1924 freebsd-current/2005-February/thread.html#46719 freebsd-current/2005-February/thread.html#46737 freebsd-stable/2005-March/thread.html#13265 freebsd-stable/2007-May/thread.html#35061 freebsd-stable/2007-July/thread.html#36308 freebsd-bugs/2012-November/thread.html#50729 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
