Mounting a system from LG's HL-DT-ST DVD-ROM GDR-H30N makes Xorg to freeze

[Alberto Salvia Novella]

Binary package hint: xorg

Full description:

When any disc is inserted in LG's HL-DT-ST DVD-ROM GDR-H30N, and after about 10 seconds, Xorg freezes, making impossible to command the computer from any input device or from the computer's power button, but the tray.

Additional information:

- If the device is tried to be opened before the freeze, this error message's shown:
Place could not be mounted
DBus error org.gtk.Private.RemoteVolumeMonitor.Failed:
An operation is already pending

- If any sound is being played in that moment, it loops in both mini-jack and HDMI connections.

- It also happens under other GNU Linux distributions and under any Ubuntu version since 7, and also using NVIDIA GeForce 8500 GT instead of ATI Radeon HD5750 as graphic processor.

- Doesn't happen with LG's HL-DT-ST DVD-RAM GH22NP20, the computer's second disc reading device.

- If the second reader is in the master position, can be commanded with the keyboard to be opened using "gnome-keyboard-properties"; but no tray opens when the reader affected by the bug is set as master.

- The device works with no problems under:
OpenSolaris
Microsoft Windows from XP to 7

- None of the methods listed under https://wiki.ubuntu.com/X/Troubleshooting/Freeze#Narrow%20Subsystem%20it%20Occurs%20in works using fglrx as display driver.

How can I get a Batch-buffer Dump?

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
CheckboxSubmission: 87995579fa318483ccc4ab7f6ee116a1
CheckboxSystem: 9a8dfd7f83677f101ab201cb214a9227
Date: Wed Apr 21 17:52:01 2010
DkmsStatus:
 fglrx, 8.723.1, 2.6.32-19-generic, x86_64: built
 fglrx, 8.723.1, 2.6.32-21-generic, x86_64: installed
EcryptfsInUse: Yes
GdmLog2:

InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
MachineType: MEDIONPC MS-7358
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-21-generic root=UUID=876c0feb-0a91-424a-9bcc-e0d2ece36f4a ro quiet splash
ProcEnviron:
 LANG=es_ES.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 08/06/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7358
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: Fab D
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.version: OEM
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/06/2007:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
dmi.product.name: MS-7358
dmi.product.version: OEM
dmi.sys.vendor: MEDIONPC
glxinfo: Error: [Errno 2] No existe el fichero ó directorio
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-21-generic

[Felix Kuehling (felix-kuehling)]

Bryce, Alberto clearly stated that he gets the same symptoms when using NVidia graphics. This is clearly not a bug in fglrx.

[Alberto Salvia Novella (es20490446e)]

Please, change the package told to be affected by this bug, cause it isn't the real one as it is said before.

[Konstantin L. Metlov (metlov)]

Lucid installer also freeses at detecting partitions on 43% (if I remember well).

Disabling the DMA for the drive (by passing "libata.dma=1" to kernel at boot time) solves the problem.

Then dmesg says:
[code][ 0.924308] ata1.01: ATAPI: HL-DT-ST DVD-ROM GDR-H30N, 1.00, max UDMA/33
[ 0.940444] ata1.01: configured for PIO4
[ 0.941474] scsi 0:0:1:0: CD-ROM HL-DT-ST DVD-ROM GDR-H30N 1.00 PQ: 0 ANSI: 5
[ 0.945381] sr0: scsi3-mmc drive: 4x/52x cd/rw xa/form2 cdda tray
[ 0.945387] Uniform CD-ROM driver Revision: 3.20
[ 0.945555] sr 0:0:1:0: Attached scsi CD-ROM sr0
[ 0.945637] sr 0:0:1:0: Attached scsi generic sg0 type 5[/code]

and everything just works.

[Alberto Salvia Novella (es20490446e)]

Thank you a lot. So shall I configure boot time or wait the problem to be solved?

[Alberto Salvia Novella (es20490446e)]

This bug is due to the bios lack of updates by the manufacturer, so it shan't be addressed here.