Re: eject(1) locks machine on = 4.4

2009-05-14 Thread Jasper Valentijn
2009/5/10 Nick Guenther kou...@gmail.com:
 I had a similar problem where trying to write anything with my CD
 drive, and sometimes even just reading it, would lock. I saw something
 go by on here that hinted it was because the drive was a fancy
 blu-ray/duallayer/hddvd-capable drive but that's as far as I cared to
 dig.

There's this patch krw's cooked up. It fixes the problem for him and
me, it might also work for you.

Index: udf_subr.c
===
RCS file: /cvs/src/sys/isofs/udf/udf_subr.c,v
retrieving revision 1.18
diff -u -p -r1.18 udf_subr.c
--- udf_subr.c  23 Jul 2008 16:24:43 -  1.18
+++ udf_subr.c  14 May 2009 01:40:41 -
@@ -110,7 +110,7 @@ udf_disklabelspoof(dev_t dev, void (*str
 */
bp-b_blkno = sector * btodb(bsize);
bp-b_bcount = bsize;
-   bp-b_flags |= (B_READ | B_RAW);
+   bp-b_flags = B_BUSY | B_READ | B_RAW;
bp-b_resid = bp-b_blkno / lp-d_secpercyl;

(*strat)(bp);
@@ -130,7 +130,7 @@ udf_disklabelspoof(dev_t dev, void (*str
for (sector = mvds_start; sector  mvds_end; sector++) {
bp-b_blkno = sector * btodb(bsize);
bp-b_bcount = bsize;
-   bp-b_flags |= (B_READ | B_RAW);
+   bp-b_flags = B_BUSY | B_READ | B_RAW;
bp-b_resid = bp-b_blkno / lp-d_secpercyl;

(*strat)(bp);


--
We spend the first twelve months of our children's lives teaching
them to walk and talk and the next twelve telling them to sit down and
shut up.



eject(1) locks machine on = 4.4

2009-05-09 Thread Jasper Valentijn
Hey misc@,

I'm able to open/close the trays of cd0, cd1 and cd3 through eject(1).

When I use eject(1) on cd2 at scsibus1 targ 0 lun 0: _NEC, DV-5800D,
F9S6 ATAPI 5/cdrom removable, the machine locks up hard. Doesn't
respond to pings, sshs or ctrl-alt-dels.  I've tried this with acpi on
and off. Same results. :(

When trying this with a ramdisk kernel, I've tried 4.3-release,
4.4-release and stable, 4.5-release, stable and current, the prompt
doesn't return on all tests except the 4.3 one. The box doesn't lock
up as hard as when using a regular kernel. cd0, cd1 and cd3 do open
and close after making the devices with MAKEDEV when booted with
bsd.rd.

If I should provide more info let me know.

tia,

Jasper

OpenBSD 4.5-current (RAMDISK_CD) #133: Fri May  8 00:26:19 MDT 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: AMD Athlon(tm) XP 3200+ (AuthenticAMD 686-class, 512KB L2
cache) 2.21 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F
XSR,SSE
real mem  = 1073246208 (1023MB)
avail mem = 1031086080 (983MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/04/04, BIOS32 rev. 0 @
0xfb470, SMBIOS rev. 2.2 @ 0xf (48 entries)
bios0: vendor Phoenix Technologies, LTD version ASUS A7N8X-X ACPI
BIOS Rev 1011 date 08/04/2004
bios0: ASUSTeK Computer INC. A7N8X-X
apm0 at bios0: Power Management spec V1.2
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdeb0/208 (11 entries)
pcibios0: PCI Exclusive IRQs: 3 4 5 10 11
pcibios0: no compatible PCI ICU found
pcibios0: Warning, unable to fix up PCI interrupt routing
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xf800 0xd/0x1800 0xd2000/0x6600
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 NVIDIA nForce2 PCI rev 0xc1
NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 1 not configured
NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 2 not configured
NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 3 not configured
NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 4 not configured
NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 5 not configured
pcib0 at pci0 dev 1 function 0 NVIDIA nForce2 ISA rev 0xa4
NVIDIA nForce2 SMBus rev 0xa2 at pci0 dev 1 function 1 not configured
ohci0 at pci0 dev 2 function 0 NVIDIA nForce2 USB rev 0xa4: irq 11,
version 1.0, legacy support
ohci1 at pci0 dev 2 function 1 NVIDIA nForce2 USB rev 0xa4: irq 4,
version 1.0, legacy support
ehci0 at pci0 dev 2 function 2 NVIDIA nForce2 USB rev 0xa4: irq 3
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1
nfe0 at pci0 dev 4 function 0 NVIDIA nForce2 LAN rev 0xa1: irq 10,
address 00:0e:a6:72:92:77
rlphy0 at nfe0 phy 1: RTL8201L 10/100 PHY, rev. 1
NVIDIA nForce2 AC97 rev 0xa1 at pci0 dev 6 function 0 not configured
ppb0 at pci0 dev 8 function 0 NVIDIA nForce2 PCI-PCI rev 0xa3
pci1 at ppb0 bus 1
ahc0 at pci1 dev 7 function 0 Adaptec AHA-29160 U160 rev 0x02: irq 11
scsibus0 at ahc0: 16 targets, initiator 7
sd0 at scsibus0 targ 0 lun 0: SEAGATE, ST39204LC, 0703 SCSI3 0/direct fixed
sd0: 8683MB, 512 bytes/sec, 17783240 sec total
cd0 at scsibus0 targ 1 lun 0: PLEXTOR, CD-ROM PX-40TS, 1.05 SCSI2
5/cdrom removable
cd1 at scsibus0 targ 4 lun 0: PLEXTOR, CD-R PX-W124TS, 1.07 SCSI2
5/cdrom removable
pciide0 at pci0 dev 9 function 0 NVIDIA nForce2 IDE rev 0xa2: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0: Maxtor 6G160P0
wd0: 64-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 6
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd2 at scsibus1 targ 0 lun 0: _NEC, DV-5800D, F9S6 ATAPI 5/cdrom removable
atapiscsi1 at pciide0 channel 1 drive 1
scsibus2 at atapiscsi1: 2 targets
cd3 at scsibus2 targ 0 lun 0: TSSTcorp, CDDVDW SH-S202J, SB00 ATAPI
5/cdrom removable
cd2(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd3(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 4
ppb1 at pci0 dev 30 function 0 NVIDIA nForce2 AGP rev 0xc1
pci2 at ppb1 bus 2
vga1 at pci2 dev 0 function 0 ATI Radeon X1650 Pro rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
ATI Radeon X1650 Pro Sec rev 0x00 at pci2 dev 0 function 1 not configured
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 NVIDIA OHCI root hub rev 1.00/1.00 addr 1
usb2 at ohci1: USB revision 1.0
uhub2 at usb2 NVIDIA OHCI root hub rev 1.00/1.00 addr 1
biomask fbfd netmask fffd ttymask 
rd0: fixed, 3800 blocks
uhub3 at uhub1 port 1 vendor 

Re: eject(1) locks machine on = 4.4

2009-05-09 Thread Jasper Valentijn
2009/5/9 Jasper Valentijn jasper.valent...@gmail.com:
 Hey misc@,

 I'm able to open/close the trays of cd0, cd1 and cd3 through eject(1).

 When I use eject(1) on cd2 at scsibus1 targ 0 lun 0: _NEC, DV-5800D,
 F9S6 ATAPI 5/cdrom removable, the machine locks up hard. Doesn't
 respond to pings, sshs or ctrl-alt-dels.  I've tried this with acpi on
 and off. Same results. :(

 When trying this with a ramdisk kernel, I've tried 4.3-release,
 4.4-release and stable, 4.5-release, stable and current, the prompt
 doesn't return on all tests except the 4.3 one. The box doesn't lock
 up as hard as when using a regular kernel. cd0, cd1 and cd3 do open
 and close after making the devices with MAKEDEV when booted with
 bsd.rd.

 If I should provide more info let me know.

I've just tested if the kind of media matters. It does.

With a dvd in the drive the machine locks up, with a cd or nothing in
it, it doesn't.

--
We spend the first twelve months of our children's lives teaching
them to walk and talk and the next twelve telling them to sit down and
shut up.



Re: eject(1) locks machine on = 4.4

2009-05-09 Thread Jasper Valentijn
2009/5/9 Jasper Valentijn jasper.valent...@gmail.com:
 2009/5/9 Jasper Valentijn jasper.valent...@gmail.com:
 Hey misc@,

 I'm able to open/close the trays of cd0, cd1 and cd3 through eject(1).

 When I use eject(1) on cd2 at scsibus1 targ 0 lun 0: _NEC, DV-5800D,
 F9S6 ATAPI 5/cdrom removable, the machine locks up hard. Doesn't
 respond to pings, sshs or ctrl-alt-dels.  I've tried this with acpi on
 and off. Same results. :(

 When trying this with a ramdisk kernel, I've tried 4.3-release,
 4.4-release and stable, 4.5-release, stable and current, the prompt
 doesn't return on all tests except the 4.3 one. The box doesn't lock
 up as hard as when using a regular kernel. cd0, cd1 and cd3 do open
 and close after making the devices with MAKEDEV when booted with
 bsd.rd.

 If I should provide more info let me know.

 I've just tested if the kind of media matters. It does.

 With a dvd in the drive the machine locks up, with a cd or nothing in
 it, it doesn't.

The dvds I've done my first tests with are windows game dvds. I've
also tested dvd-movies then there's no problem.

Same on macppc.

--
We spend the first twelve months of our children's lives teaching
them to walk and talk and the next twelve telling them to sit down and
shut up.



Re: eject(1) locks machine on = 4.4

2009-05-09 Thread Nick Guenther
I had a similar problem where trying to write anything with my CD
drive, and sometimes even just reading it, would lock. I saw something
go by on here that hinted it was because the drive was a fancy
blu-ray/duallayer/hddvd-capable drive but that's as far as I cared to
dig.

On 09/05/2009, Jasper Valentijn jasper.valent...@gmail.com wrote:
 2009/5/9 Jasper Valentijn jasper.valent...@gmail.com:
 2009/5/9 Jasper Valentijn jasper.valent...@gmail.com:
 Hey misc@,

 I'm able to open/close the trays of cd0, cd1 and cd3 through eject(1).

 When I use eject(1) on cd2 at scsibus1 targ 0 lun 0: _NEC, DV-5800D,
 F9S6 ATAPI 5/cdrom removable, the machine locks up hard. Doesn't
 respond to pings, sshs or ctrl-alt-dels.  I've tried this with acpi on
 and off. Same results. :(

 When trying this with a ramdisk kernel, I've tried 4.3-release,
 4.4-release and stable, 4.5-release, stable and current, the prompt
 doesn't return on all tests except the 4.3 one. The box doesn't lock
 up as hard as when using a regular kernel. cd0, cd1 and cd3 do open
 and close after making the devices with MAKEDEV when booted with
 bsd.rd.

 If I should provide more info let me know.

 I've just tested if the kind of media matters. It does.

 With a dvd in the drive the machine locks up, with a cd or nothing in
 it, it doesn't.

 The dvds I've done my first tests with are windows game dvds. I've
 also tested dvd-movies then there's no problem.

 Same on macppc.

 --
  We spend the first twelve months of our children's lives teaching
 them to walk and talk and the next twelve telling them to sit down and
 shut up.