Re: device timeout when mounting cd
Hello Stephen, In fact, I did not use CDROM ;) I booted only kernel and basic image from CDROM (so it was readed by BIOS). After OpenBSD booted, I never tried to read from it. But I can try it if you want. I instaled everything from network. Mest regards, Lukas On Po, 2005-10-31 at 09:49 +1300, Stephen Nelson wrote: How did you go fixing your problems with the 336? I have a couple of 336 machines that I want to boot from CD as firewalls but I can't get my 336 to read a CD. When I attempt, the device times out. Can your machine read from a CDROM? I've posted on the OpenBSD-misc mailing list, so probably best to CC to that list. Thanks, Stephen Nelson [demime 1.01d removed an attachment of type application/x-pkcs7-signature which had a name of smime.p7s]
Re: device timeout when mounting cd
If you could try that would be good. Thanks, Stephen Lukas( Macura wrote: Hello Stephen, In fact, I did not use CDROM ;) I booted only kernel and basic image from CDROM (so it was readed by BIOS). After OpenBSD booted, I never tried to read from it. But I can try it if you want. I instaled everything from network. Mest regards, Lukas On Po, 2005-10-31 at 09:49 +1300, Stephen Nelson wrote: How did you go fixing your problems with the 336? I have a couple of 336 machines that I want to boot from CD as firewalls but I can't get my 336 to read a CD. When I attempt, the device times out. Can your machine read from a CDROM? I've posted on the OpenBSD-misc mailing list, so probably best to CC to that list. Thanks, Stephen Nelson
Re: device timeout when mounting cd
Andrew Daugherity wrote: I completely missed that you're running amd64 (I saw Intel Xeon, and thought i386). You might try an i386 kernel (maybe the bsd.rd installer, as you don't want to mix libs between i386 and amd64) to see if the CD-ROM works there. If it works under i386, then it looks like a bug somewhere in the amd64 kernel, and might be worth filing a bug over (or perhaps adding comments to PR4570). I wasn't using the i386 kernel as it hangs when probing PCI devices. I managed to get past this by disabling pcibios, but it has the same problem as the amd64 kernel when it comes to reading the CDROM, so nothing gained other than showing that the problem is not amd64 specific. More data is good. If you can swap the drive, that would be a good test. Also, testing other BSDs can't hurt -- NetBSD, OpenBSD, and FreeBSD share some code, Net and Open more so than Free; although they've diverged quite a bit, sometimes drivers (and bugfixes) are ported between them. Note that saying but it works in NetBSD, fix it! isn't likely to get you much help here, but it's also broken in NetBSD might help track down the bug. I'm not an OpenBSD developer, so if someone who is one chimes in, take their word over mine. :-) I have two machines, both with the same problem, so it's not the drive. I've tried using NetBSD, and the amd64 2.1 kernel works fine. How can I bring this to the attention of a developer? I'm guessing that with the release tomorrow developers are a little busy, but once 3.8 is out what should I do to get this fixed? I have some experience with c, but not enough to fix the problem myself. I would be able to apply patchs etc to help deduce the problem though. Thanks for your help, Stephen
Re: device timeout when mounting cd
On Fri, 28 Oct 2005 17:04:42 +1300, Stephen Nelson wrote: I have found a PR4570 which seems to be a similar problem. Interestingly, this was with an nForce4 chipset, whereas my chipset is Intel. There was a post 'Problem instaling OpenBSD on IBM xSeries 336' a few days back. AFAIR, with a similar chipset and drive. If I am right, you could contact that poster and find out how he does. Uwe
Re: device timeout when mounting cd
I would really appreciate help with this. I would like to use this machine to build a diskless firewall, but without being able to boot from a CD I have problems. I have checked and double-checked settings. I have checked that my chipset (Intel 82801EB) is supported (it is) and I have checked as best I can that I am not making a simple mistake in configuration. I have searched mailing lists for similar problems and drawn a blank. I have tested this hardware with Gentoo Linux and with Windows so I am sure it's not a hardware issue. Besides, I can boot from a cd without a problem, I just can't mount it once the kernel has loaded. Should I file a bug report? Is there any way I can get the device to fall back to a legacy mode that would allow me to get further? I will try OpenBSD-current tomorrow to see if this problem is fixed there, but would still appreciate any help or suggestions. Thanks, Stephen Nelson When I attempt to mount a cd or read the disklabel, I get this error from the kernel: Oct 26 10:08:59 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:08:59 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:08:59 develop /bsd: type: atapi Oct 26 10:08:59 develop /bsd: type: atapi Oct 26 10:08:59 develop /bsd: c_bcount: 0 Oct 26 10:08:59 develop /bsd: c_bcount: 0 Oct 26 10:08:59 develop /bsd: c_skip: 0 Oct 26 10:08:59 develop /bsd: c_skip: 0 Oct 26 10:09:09 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:09 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:09 develop /bsd: type: atapi Oct 26 10:09:09 develop /bsd: type: atapi Oct 26 10:09:09 develop /bsd: c_bcount: 32 Oct 26 10:09:09 develop /bsd: c_bcount: 32 Oct 26 10:09:10 develop /bsd: c_skip: 0 Oct 26 10:09:10 develop /bsd: c_skip: 0 Oct 26 10:09:10 develop /bsd: pciide0:0:0: device timeout, c_bcount=32, c_skip=0, status=0x58DRDY,DSC,DRQ, ireason=0x2 Oct 26 10:09:10 develop /bsd: pciide0:0:0: device timeout, c_bcount=32, c_skip=0, status=0x58DRDY,DSC,DRQ, ireason=0x2 Oct 26 10:09:15 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:15 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:15 develop /bsd: type: atapi Oct 26 10:09:15 develop /bsd: type: atapi Oct 26 10:09:15 develop /bsd: c_bcount: 0 Oct 26 10:09:15 develop /bsd: c_bcount: 0 Oct 26 10:09:15 develop /bsd: c_skip: 0 Oct 26 10:09:15 develop /bsd: c_skip: 0 Oct 26 10:09:19 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:19 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:19 develop /bsd: type: atapi Oct 26 10:09:19 develop /bsd: type: atapi Oct 26 10:09:19 develop /bsd: c_bcount: 0 Oct 26 10:09:19 develop /bsd: c_bcount: 0 Oct 26 10:09:19 develop /bsd: c_skip: 0 Oct 26 10:09:19 develop /bsd: c_skip: 0 This message repeats for about 10 minutes, at which point the kernel gives up and I get a prompt. This happens whenever I try to mount cd0[a,c] or 'disklabel cd0'. I can't find anything relevant in the forums - the closest I got was a message about problems with hardware using the le device. The machine is an IBM xSeries 336 with a Xeon processor. I'm using the generic amd64 kernel. I can boot from cd. Anyone have any idea what the problem could be? dmesg output: (not including error messages as above) OpenBSD 3.7-stable (GENERIC) #1: Thu Oct 20 15:48:27 NZDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1073123328 (1047972K) avail mem = 909221888 (887912K) using 22937 buffers containing 10752 bytes (105000K) of memory mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Xeon(TM) CPU 3.00GHz, 3000.60 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,LONG cpu0: 2MB 64b/line 8-way L2 cache pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel E7710 SMCH rev 0x0c Intel E7710 MCH ERR rev 0x0c at pci0 dev 0 function 1 not configured ppb0 at pci0 dev 2 function 0 Intel E7710 MCH PCIE rev 0x0c pci1 at ppb0 bus 2 ppb1 at pci0 dev 4 function 0 Intel E7710 MCH PCIE rev 0x0c pci2 at ppb1 bus 3 ppb2 at pci2 dev 0 function 0 Intel PCIE-PCIE rev 0x09 pci3 at ppb2 bus 4 mpt0 at pci3 dev 1 function 0 Symbios Logic 53c1030 rev 0x08: irq 11 mpt0: sending FW Upload request to IOC (size: 36, img size: 69956) mpt0: IM support: 4 scsibus0 at mpt0: 16 targets sd0 at scsibus0 targ 0 lun 0: LSILOGIC, 1030 IM, 1000 SCSI2 0/direct fixed sd0: 70006MB, 70006 cyl, 16 head, 128 sec, 512 bytes/sec, 143372288 sec total mpt0: target 0 Asynchronous at 0MHz width 8bit offset 0 QAS 0 DT 0 IU 0 ppb3 at pci2 dev 0 function 2 Intel PCIE-PCIE rev 0x09 pci4 at ppb3 bus 5 ppb4 at pci0 dev 6 function 0 Intel E7710 MCH PCIE rev 0x0c pci5 at ppb4 bus 6 bge0 at pci5 dev 0 function 0 Broadcom BCM5721 rev 0x11, unknown BCM5750 (0x4101): irq 11 address 00:14:5e:30:3e:fc brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb5 at pci0 dev 7 function 0 Intel E7710 MCH PCIE
Re: device timeout when mounting cd
On 10/27/05, Stephen Nelson [EMAIL PROTECTED] wrote: Is there any way I can get the device to fall back to a legacy mode that would allow me to get further? I've seen some CD-ROM drives claim to support UDMA2 but not work properly in UDMA mode. You could try setting the flags to disable DMA on it, see atapiscsi(4). 'boot -c' to enter UKC [see boot_config(8)]; 'change atapiscsi' and set the flags accordingly. This may or may not help, but it's worth a try. Definitely try a recent snapshot also. -Andrew
Re: device timeout when mounting cd
On Wed, 26 Oct 2005 10:23:23 +1300, Stephen Nelson wrote: When I attempt to mount a cd or read the disklabel, I get this error from the kernel: Oct 26 10:08:59 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:08:59 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:08:59 develop /bsd: type: atapi Oct 26 10:08:59 develop /bsd: type: atapi Oct 26 10:08:59 develop /bsd: c_bcount: 0 Oct 26 10:08:59 develop /bsd: c_bcount: 0 Oct 26 10:08:59 develop /bsd: c_skip: 0 Oct 26 10:08:59 develop /bsd: c_skip: 0 How far did you go on your own to debug this ? Did you try to swap the drive ? Did you try to swap the cable ? Do you have another OS on your system to try from there ? Have you tried some flags from 'man wd' to bring down the PIO/DMA ? Uwe
Re: device timeout when mounting cd
Andrew Daugherity wrote: I've seen some CD-ROM drives claim to support UDMA2 but not work properly in UDMA mode. You could try setting the flags to disable DMA on it, see atapiscsi(4). 'boot -c' to enter UKC [see boot_config(8)]; 'change atapiscsi' and set the flags accordingly. This may or may not help, but it's worth a try. Definitely try a recent snapshot also. -Andrew I have tried disabling UDMA, and UDMA and DMA, with no change. I have also tried the latest snapshot from ftp. Any more ideas? I have found a PR4570 which seems to be a similar problem. Interestingly, this was with an nForce4 chipset, whereas my chipset is Intel. Thanks, Stephen
Re: device timeout when mounting cd
How far did you go on your own to debug this ? I'm new to OpenBSD and I don't know how to debug this any further. I'm open to suggestions though and prepared to learn. Did you try to swap the drive ? Did you try to swap the cable ? Do you have another OS on your system to try from there ? I have had this drive working correctly with Gentoo Linux and an identical drive on another machine working with Windows XP. I haven't changed the drive or the hardware as I can boot from cd with openbsd, and the drive works with Linux. This is a new machine and I don't want to have to open the case if I can avoid it as it is sealed. Have you tried some flags from 'man wd' to bring down the PIO/DMA ? I have followed Andrew Daugherity's suggestion of disabling UDMA and DMA from boot_config without success. dmesg reports that my device uses atapiscsi not wd. Thanks for your help, Stephen
Re: device timeout when mounting cd
On 10/27/05, Stephen Nelson [EMAIL PROTECTED] wrote: Any more ideas? I have found a PR4570 which seems to be a similar problem. Interestingly, this was with an nForce4 chipset, whereas my chipset is Intel. I completely missed that you're running amd64 (I saw Intel Xeon, and thought i386). You might try an i386 kernel (maybe the bsd.rd installer, as you don't want to mix libs between i386 and amd64) to see if the CD-ROM works there. If it works under i386, then it looks like a bug somewhere in the amd64 kernel, and might be worth filing a bug over (or perhaps adding comments to PR4570). More data is good. If you can swap the drive, that would be a good test. Also, testing other BSDs can't hurt -- NetBSD, OpenBSD, and FreeBSD share some code, Net and Open more so than Free; although they've diverged quite a bit, sometimes drivers (and bugfixes) are ported between them. Note that saying but it works in NetBSD, fix it! isn't likely to get you much help here, but it's also broken in NetBSD might help track down the bug. I'm not an OpenBSD developer, so if someone who is one chimes in, take their word over mine. :-) Andrew
device timeout when mounting cd
When I attempt to mount a cd or read the disklabel, I get this error from the kernel: Oct 26 10:08:59 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:08:59 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:08:59 develop /bsd: type: atapi Oct 26 10:08:59 develop /bsd: type: atapi Oct 26 10:08:59 develop /bsd: c_bcount: 0 Oct 26 10:08:59 develop /bsd: c_bcount: 0 Oct 26 10:08:59 develop /bsd: c_skip: 0 Oct 26 10:08:59 develop /bsd: c_skip: 0 Oct 26 10:09:09 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:09 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:09 develop /bsd: type: atapi Oct 26 10:09:09 develop /bsd: type: atapi Oct 26 10:09:09 develop /bsd: c_bcount: 32 Oct 26 10:09:09 develop /bsd: c_bcount: 32 Oct 26 10:09:10 develop /bsd: c_skip: 0 Oct 26 10:09:10 develop /bsd: c_skip: 0 Oct 26 10:09:10 develop /bsd: pciide0:0:0: device timeout, c_bcount=32, c_skip=0, status=0x58DRDY,DSC,DRQ, ireason=0x2 Oct 26 10:09:10 develop /bsd: pciide0:0:0: device timeout, c_bcount=32, c_skip=0, status=0x58DRDY,DSC,DRQ, ireason=0x2 Oct 26 10:09:15 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:15 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:15 develop /bsd: type: atapi Oct 26 10:09:15 develop /bsd: type: atapi Oct 26 10:09:15 develop /bsd: c_bcount: 0 Oct 26 10:09:15 develop /bsd: c_bcount: 0 Oct 26 10:09:15 develop /bsd: c_skip: 0 Oct 26 10:09:15 develop /bsd: c_skip: 0 Oct 26 10:09:19 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:19 develop /bsd: cd0(pciide0:0:0): timeout Oct 26 10:09:19 develop /bsd: type: atapi Oct 26 10:09:19 develop /bsd: type: atapi Oct 26 10:09:19 develop /bsd: c_bcount: 0 Oct 26 10:09:19 develop /bsd: c_bcount: 0 Oct 26 10:09:19 develop /bsd: c_skip: 0 Oct 26 10:09:19 develop /bsd: c_skip: 0 This message repeats for about 10 minutes, at which point the kernel gives up and I get a prompt. This happens whenever I try to mount cd0[a,c] or 'disklabel cd0'. I can't find anything relevant in the forums - the closest I got was a message about problems with hardware using the le device. The machine is an IBM xSeries 336 with a Xeon processor. I'm using the generic amd64 kernel. I can boot from cd. Anyone have any idea what the problem could be? dmesg output: (not including error messages as above) OpenBSD 3.7-stable (GENERIC) #1: Thu Oct 20 15:48:27 NZDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1073123328 (1047972K) avail mem = 909221888 (887912K) using 22937 buffers containing 10752 bytes (105000K) of memory mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Xeon(TM) CPU 3.00GHz, 3000.60 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,LONG cpu0: 2MB 64b/line 8-way L2 cache pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel E7710 SMCH rev 0x0c Intel E7710 MCH ERR rev 0x0c at pci0 dev 0 function 1 not configured ppb0 at pci0 dev 2 function 0 Intel E7710 MCH PCIE rev 0x0c pci1 at ppb0 bus 2 ppb1 at pci0 dev 4 function 0 Intel E7710 MCH PCIE rev 0x0c pci2 at ppb1 bus 3 ppb2 at pci2 dev 0 function 0 Intel PCIE-PCIE rev 0x09 pci3 at ppb2 bus 4 mpt0 at pci3 dev 1 function 0 Symbios Logic 53c1030 rev 0x08: irq 11 mpt0: sending FW Upload request to IOC (size: 36, img size: 69956) mpt0: IM support: 4 scsibus0 at mpt0: 16 targets sd0 at scsibus0 targ 0 lun 0: LSILOGIC, 1030 IM, 1000 SCSI2 0/direct fixed sd0: 70006MB, 70006 cyl, 16 head, 128 sec, 512 bytes/sec, 143372288 sec total mpt0: target 0 Asynchronous at 0MHz width 8bit offset 0 QAS 0 DT 0 IU 0 ppb3 at pci2 dev 0 function 2 Intel PCIE-PCIE rev 0x09 pci4 at ppb3 bus 5 ppb4 at pci0 dev 6 function 0 Intel E7710 MCH PCIE rev 0x0c pci5 at ppb4 bus 6 bge0 at pci5 dev 0 function 0 Broadcom BCM5721 rev 0x11, unknown BCM5750 (0x4101): irq 11 address 00:14:5e:30:3e:fc brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb5 at pci0 dev 7 function 0 Intel E7710 MCH PCIE rev 0x0c pci6 at ppb5 bus 7 bge1 at pci6 dev 0 function 0 Broadcom BCM5721 rev 0x11, unknown BCM5750 (0x4101): irq 11 address 00:14:5e:30:3e:fd brgphy1 at bge1 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 vendor Intel, unknown product 0x359b (class system subclass miscellaneous, rev 0x0c) at pci0 dev 8 function 0 not configured uhci0 at pci0 dev 29 function 0 Intel 82801EB/ER USB rev 0x02: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801EB/ER USB rev 0x02: irq 3 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801EB/ER USB rev 0x02: irq 5 ehci0: EHCI version 1.0 ehci0: companion controllers, 2 ports each: uhci0 uhci1 usb2 at ehci0:
