Removing modular bay drive causes system freeze

[Matthew Buck]

I'm running a Dell Inspiron 600m laptop that comes with a modular bay for
swapping out the dvd-rom and the secondary battery. When I boot up with the
dvd-rom drive in the modular bay and then try to swap it out, my system
completely freezes. I've noticed that my drive gets detected as /dev/hdc.

When I boot up with the second battery and try to swap it out to the dvd-rom
drive, it doesn't get detected. starting / stopping hotplug doesn't seem to fix
this.

[Matt Zimmerman (mdz)]

It generally isn't possible to swap these devices while the system is booted,
though I don't know about your particular laptop. Does it work under another OS?

[Matthew Buck (mabuck)]

(In reply to comment #1)
> It generally isn't possible to swap these devices while the system is booted,
> though I don't know about your particular laptop. Does it work under another OS?

The only other OS I've tried it on is windows, and it worked fine. These things
seem to be made for hot-swapability, or at least for that particular OS.

It's driver seems to be built into the kernel, rather than loaded from hotplug
or discovery. I don't know of any way to change it, since it probably uses the
IDE driver.

[Thomas Hood (jdthood)]

*** Bug 18196 has been marked as a duplicate of this bug. ***

[Thomas (tms)]

(In reply to comment #1)
> It generally isn't possible to swap these devices while the system is booted,
> though I don't know about your particular laptop. Does it work under another OS?

Besides from Windows XP, this also works under Gentoo by default. it doesnt detect the CD-rom if you insert it after booting, but atleast
it doesnt freeze if you remove the CD-rom afterwards. (Using coldplug and hotplug)

[Matthew Garrett (mjg59)]

Removable IDE is an utter nightmare. I'll see if there's any way we can fudge
around it, but I wouldn't be optimistic.

[Ben Collins (ben-collins)]

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

[Ben Collins (ben-collins)]

Closing, inactive.

[André Rüdiger (andreruediger-deactivatedaccount)]

I can confirm this on my Thinkpad T42p with up to date Edgy. The system freezes immediately after I have removed the cd drive off the ultrabay. Additional informations are available at http://thinkwiki.org/wiki/How_to_hotswap_UltraBay_devices .

Should I file a new bug instead?

Thanks!

[Noel J. Bergman (noeljb)]

This appears to have been fixed for Gutsy, and is broken again for Hardy. I have tested both.

With Gutsy, I can easily swap my CD/DVD multi-burner and my PATA 2nd HD adapter. Going further, if I configure the scripts for ACPI as described by http://thinkwiki.org/wiki/How_to_hotswap_UltraBay_devices#Scripts_for_hotswapping and configure HAL as described by http://thinkwiki.org/wiki/How_to_hotswap_UltraBay_devices#HAL_support, everything works a treat.

If I remove the drive with Hardy, the system locks up solid. Not just a UI freeze. Nothing responds, not even over the LAN or Bluetooth. A power cycle is reequired.

Another bit of data: with Gutsy and my ThinkPad T61p 6457-7WU, the hotswap bay shows up as 1:0:0:0; with Hardy, it shows up as 3:0:0:0.

I am marking my bug #182058 as a duplicate of this bug.

[Leann Ogasawara (leannogasawara)]

Hi Noel,

Thanks for the update. Per the kernel team's bug policy, can you please attach the following information when running Hardy. Please be sure to attach each file as a separate attachment.

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Also, after you notice the issue and have to power cycle, could you maybe examine /var/log/kern.log.0. Maybe it will have captured a useful error message prior to locking up. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Noel J. Bergman (noeljb)]

Hi Leann,

Thank you for explaining what you need. Ben Collins wrote: "We would like to fix all bugs, but need users to test and help with debugging." Well, this bug is important to me, and I'm here to help as much as I can. Just let me know how I can help. :-) Need me to run an interim test build? Just give me the instructions. Whatever you need.

I have attached the files as requested. I did not see anything in the kernel log that appeared to be "a useful error message prior to locking up." I can reproduce the lockup at will, and have check each of the reboots to see if there was anything logged prior to it. Nothing that I can see in any log. I apologize, because I had noticed the lack of logging earlier, but had not mentioned it in my bug report.

[Noel J. Bergman (noeljb)]

Would it help you if I provided the same attachments from the same T61p running Gutsy. where this works?

[Noel J. Bergman (noeljb)]

> Another bit of data: with Gutsy and my ThinkPad T61p 6457-7WU, the hotswap bay shows up as 1:0:0:0; with Hardy, it shows up as 3:0:0:0

And with the latest changes to Hardy, it is showing up as 4:0:0:0. Is this shifting of the host ID related to the bug?

[Noel J. Bergman (noeljb)]

I just rebooted under Gutsy and updated it.

Hotswapping still works with Gutsy, but it seems that I was wrong about the host ID being consistent. The host ID is shifting with Gutsy too. I'll modify the udev rules and scripts from http://thinkwiki.org/wiki/How_to_hotswap_UltraBay_devices#Scripts_for_hotswapping by passing the DEVPATH on the event, and adjusting the scripts to use it as necessary.

[Leann Ogasawara (leannogasawara)]

Hi Noel,

It might be good if you test with the latest published kernel - 2.6.24-5.9 (https://launchpad.net/ubuntu/+source/linux) It was most recently sync'd wih the 2.6.24 release of the upstream mainline kernel. Thanks!

[Noel J. Bergman (noeljb)]

Leann,

Done. It didn't work. I will attach the logs you've previously requested.

BUT ... I also have an additional data point for you this time. Although nothing showed up in the logs, I happened to be using console 1 instead of the gnome session when I pulled the drive, and there was output to the console:

  ata4: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xa frozen
  ata4: ACPI event

After rebooting, I did a grep for frozen in /var/log, and found nothing.

[Noel J. Bergman (noeljb)]

I booted to my BIOS and doublechecked the configuration. The hot-bay is configured for AHCI, not "Compatibility". Again, this is the same configuration that works with Gutsy.

[Noel J. Bergman (noeljb)]

Rebooted and tried Compatibility mode instead of AHCI. No difference, except that it was ata2 instead of ata4 when the error appeared on the console.

[Noel J. Bergman (noeljb)]

Just confirming that this regression is still present in the latest kernel for Hardy alpha:

  $ uname -a
  Linux noel-hardy 2.6.24-7-generic #1 SMP Thu Feb 7 00:56:31 UTC 2008 x86_64 GNU/Linux

  $ cat /proc/version_signature
  Ubuntu 2.6.24-7.12-generic

Gutsy works, Hardy alpha is still broken. I will continue to test each new kernel as soon as it is available for testing.

[Noel J. Bergman (noeljb)]

FWIW, I just tried this with the latest Fedora 9 code, which installed a 2.6.25 kernel. It also freezes solid when the drive is pulled from the bay. So it is not fixed upstream.

You might want to check with Matthew Garrett, since I believe that he's the one who made this work for Gutsy.

As for the importance of this defect, if I knew how (and could), I'd personally move it to critical. I won't be upgrading to Hardy, which fixes so many other things, if this regression isn't fixed.

[Amit Kucheria (amitk)]

Bay hotplug patch from Gutsy was integrated upstream, so we already carry it. Can you confirm if you see ACPI events on ejecting the bay? It probably shows up in /var/log/acpid

[Noel J. Bergman (noeljb)]

Amit,

*NOTHING* appears in the acpid log for any of the following:

  - unlock the bay lever
  - pull the DVD drive
  - insert the DVD drive
  - lock the bay lever

This is true for both Gutsy and Hardy.

With Gutsy, I see the following from lshal -m:

  22:30:46.957: pci_8086_2850_scsi_host_scsi_device_lun0_scsi_generic removed
  22:30:46.988: pci_8086_2850_scsi_host_scsi_device_lun0 removed
  22:30:46.988: pci_8086_2850_scsi_host removed
  22:30:47.002: storage_model_DVD_RAM_UJ_852 removed
  22:30:54.717: pci_8086_2850_scsi_host added
  22:30:54.717: pci_8086_2850_scsi_host_scsi_device_lun0 added
  22:30:54.717: pci_8086_2850_scsi_host_scsi_device_lun0_scsi_generic added
  22:30:56.789: storage_model_DVD_RAM_UJ_852 added

and from udevmonitor:

  #udevmonitor --kernel --udev
  udevmonitor will print the received events for:
  UDEV the event which udev sends out after rule processing
  UEVENT the kernel uevent

  --- unlock lever ---
  UEVENT[1204083328.721202] change /devices/pci0000:00/0000:00:1f.1/host2/target2:0:0/2:0:0:0 (scsi)
  UDEV [1204083328.722937] change /devices/pci0000:00/0000:00:1f.1/host2/target2:0:0/2:0:0:0 (scsi)
  UEVENT[1204083329.309553] remove /class/scsi_generic/sg1 (scsi_generic)
  UEVENT[1204083329.309592] remove /class/scsi_device/2:0:0:0 (scsi_device)
  UEVENT[1204083329.309610] remove /block/sr0 (block)
  UEVENT[1204083329.310684] remove /devices/pci0000:00/0000:00:1f.1/host2/target2:0:0/2:0:0:0 (scsi)
  UDEV [1204083329.313203] remove /class/scsi_generic/sg1 (scsi_generic)
  UDEV [1204083329.316554] remove /class/scsi_device/2:0:0:0 (scsi_device)
  UDEV [1204083329.335449] remove /block/sr0 (block)
  UDEV [1204083329.396879] remove /devices/pci0000:00/0000:00:1f.1/host2/target2:0:0/2:0:0:0 (scsi)

  -- lock lever --
  UEVENT[1204083412.454330] add /devices/pci0000:00/0000:00:1f.1/host2/target2:0:0/2:0:0:0 (scsi)
  UEVENT[1204083412.475358] add /block/sr0 (block)
  UEVENT[1204083412.475397] add /class/scsi_device/2:0:0:0 (scsi_device)
  UEVENT[1204083412.475415] add /class/scsi_generic/sg1 (scsi_generic)
  UDEV [1204083412.549064] add /devices/pci0000:00/0000:00:1f.1/host2/target2:0:0/2:0:0:0 (scsi)
  UDEV [1204083412.563941] add /class/scsi_device/2:0:0:0 (scsi_device)
  UDEV [1204083412.564876] add /class/scsi_generic/sg1 (scsi_generic)
  UDEV [1204083414.630600] add /block/sr0 (block)

Now to check Hardy ...

[Noel J. Bergman (noeljb)]

... and here we go:

  # lshal -m

  Start monitoring devicelist:
  -------------------------------------------------

  --- NOTHING ---

and from udevmonitor:

  # udevmonitor --kernel --udev
  udevmonitor will print the received events for:
  UDEV the event which udev sends out after rule processing
  UEVENT the kernel uevent

  --- unlock lever ---
  UEVENT[1204083856.581788] change /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0 (scsi)
  UDEV [1204083856.583007] change /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0 (scsi)

  --- lock lever ---
  UEVENT[1204083962.010976] change /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0 (scsi)
  UDEV [1204083962.011887] change /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0 (scsi)

As you can see, Gutsy and Hardy exhibit different behavior.

[Noel J. Bergman (noeljb)]

And just to confirm:

  # uname -a
  Linux noel-hardy 2.6.24-10-generic #1 SMP Fri Feb 22 18:26:06 UTC 2008 x86_64 GNU/Linux

and when I pull the drive, I still get the kernel freeze, with the only output being to the console, as documented previously.

[Noel J. Bergman (noeljb)]

I just tried booting both Gutsy and Hardy without anything in the drive bay, and then inserting.

With Hardy, NOTHING happens. I can insert, remove, insert, remove, who cares. NOTHING happens. It does not recognize that I have put a drive into the bay.

With Gutsy:

  # lshal -m

  Start monitoring devicelist:
  -------------------------------------------------
  23:24:42.657: pci_8086_2850_scsi_host added
  23:24:42.659: pci_8086_2850_scsi_host_scsi_device_lun0 added
  23:24:42.665: pci_8086_2850_scsi_host_scsi_device_lun0_scsi_generic added
  23:24:44.821: storage_model_DVD_RAM_UJ_852 added

  # udevmonitor --kernel --udev
  udevmonitor will print the received events for:
  UDEV the event which udev sends out after rule processing
  UEVENT the kernel uevent

  -- lock lever --
  UEVENT[1204086282.467824] add /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0 (scsi)
  UEVENT[1204086282.467877] add /class/scsi_device/0:0:0:0 (scsi_device)
  UEVENT[1204086282.467895] add /class/scsi_generic/sg2 (scsi_generic)
  UEVENT[1204086282.554669] add /module/cdrom (module)
  UDEV [1204086282.556280] add /module/cdrom (module)
  UEVENT[1204086282.569548] add /module/sr_mod (module)
  UEVENT[1204086282.569830] add /bus/scsi/drivers/sr (drivers)
  UDEV [1204086282.571589] add /bus/scsi/drivers/sr (drivers)
  UDEV [1204086282.572402] add /module/sr_mod (module)
  UEVENT[1204086282.589792] add /block/sr0 (block)
  UDEV [1204086282.658476] add /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0 (scsi)
  UDEV [1204086282.663156] add /class/scsi_device/0:0:0:0 (scsi_device)
  UDEV [1204086282.664926] add /class/scsi_generic/sg2 (scsi_generic)
  UDEV [1204086284.720635] add /block/sr0 (block)

Hope this data is heplful.

[Noel J. Bergman (noeljb)]

Since the only message that appears anywhere with respect to the hotswap bay is:

    ata4: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xa frozen
    ata4: ACPI event

on the console (not the logs), I thought that the following might have some value. I had attached an eSATA drive on a SiiG eSATA ExpressCard. When I powered off the drive (it was not mounted), the following appeared in kern.log:

  Mar 15 11:27:35 noel-hardy kernel: [ 94.930433] ata2: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0xa frozen
  Mar 15 11:27:35 noel-hardy kernel: [ 94.930445] ata2: irq_stat 0x01140010, PHY RDY changed
  Mar 15 11:27:35 noel-hardy kernel: [ 94.930450] ata2: SError: { 10B8B }
  Mar 15 11:27:35 noel-hardy kernel: [ 94.930468] ata2: hard resetting link
  Mar 15 11:27:37 noel-hardy kernel: [ 95.148572] ata2: SATA link down (SStatus 0 SControl 0)
  Mar 15 11:27:37 noel-hardy kernel: [ 95.148591] ata2: failed to recover some devices, retrying in 5 secs
  Mar 15 11:27:42 noel-hardy kernel: [ 95.514751] ata2: hard resetting link
  Mar 15 11:27:44 noel-hardy kernel: [ 95.758041] ata2: SATA link down (SStatus 0 SControl 0)
  Mar 15 11:27:44 noel-hardy kernel: [ 95.758060] ata2: failed to recover some devices, retrying in 5 secs
  Mar 15 11:27:49 noel-hardy kernel: [ 96.099245] ata2: hard resetting link
  Mar 15 11:27:51 noel-hardy kernel: [ 96.320802] ata2: SATA link down (SStatus 0 SControl 0)
  Mar 15 11:27:51 noel-hardy kernel: [ 96.320821] ata2.00: disabled
  Mar 15 11:27:52 noel-hardy kernel: [ 96.436877] ata2: EH complete
  Mar 15 11:27:52 noel-hardy kernel: [ 96.436889] ata2.00: detaching (SCSI 1:0:0:0)
  Mar 15 11:27:52 noel-hardy kernel: [ 96.437129] sd 1:0:0:0: [sda] Synchronizing SCSI cache
  Mar 15 11:27:52 noel-hardy kernel: [ 96.437159] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
  Mar 15 11:27:52 noel-hardy kernel: [ 96.437163] sd 1:0:0:0: [sda] Stopping disk
  Mar 15 11:27:52 noel-hardy kernel: [ 96.437168] sd 1:0:0:0: [sda] START_STOP FAILED
  Mar 15 11:27:52 noel-hardy kernel: [ 96.437169] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK

and when powering the drive back on:

  Mar 15 11:36:23 noel-hardy kernel: [ 169.535591] ata2: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xa frozen
  Mar 15 11:36:23 noel-hardy kernel: [ 169.535602] ata2: irq_stat 0x00b40090, PHY RDY changed
  Mar 15 11:36:23 noel-hardy kernel: [ 169.535621] ata2: hard resetting link
  Mar 15 11:36:33 noel-hardy kernel: [ 170.463754] ata2: softreset failed (timeout)
  Mar 15 11:36:33 noel-hardy kernel: [ 170.463767] ata2: hard resetting link
  Mar 15 11:36:41 noel-hardy kernel: [ 171.101536] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
  Mar 15 11:36:41 noel-hardy kernel: [ 171.102423] ata2.00: ATA-7: Hitachi HDS721010KLA330, GKAOA70M, max UDMA/133
  Mar 15 11:36:41 noel-hardy kernel: [ 171.102433] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
  Mar 15 11:36:41 noel-hardy kernel: [ 171.103044] ata2.00: configured for UDMA/100
  Mar 15 11:36:41 noel-hardy kernel: [ 171.103057] ata2: EH complete
  Mar 15 11:36:41 noel-har...

[Noel J. Bergman (noeljb)]

According to the schedule (https://wiki.ubuntu.com/HardyReleaseSchedule), Hardy kernel freeze is in just over a week. Is there anything I can do to help in terms of testing so that this regression from Gutsy is fixed in Hardy?

[Federico Belvisi (armalite)]

I have the same regression on a Fujitsu-Siemens Lifebook C1110. On gutsy, bay was working as intended. In hardy, system hard freeze when ejecting the bay dvd-rom.

Still present on 2.6.24-12.

[Aaron Toponce (atoponce-deactivatedaccount)]

Still present on my ThinkPad T61. Hotswapping CD/DVDROM causes hard lock, requiring cold reboot. 2.6.24-16-generic is my kernel.

[Slawa Kewlin (lordleto)]

I am experiencing the same behavior on a T41p with Hardy and the stock kernel 2.6.24-16-generic
.
Hotswapping of my harddisk with cdrw drive worked perfectly well with Gutsy (kernel 2.6.22-14-generic). After the upgrade to Hardy the system freezes when I try eject the drive. Interestingly when I boot the Gutsy kernel (which I kept as failsafe) on my new Hardy install the hotswapping works perfectly as before.
So I think there was some change between 2.6.22 and 2.6.24 which caused this regression.
I will gladly give more information about my system if needed. Hopefully someone has an idea what exactly causes this problem.

[jnewton (nevion)]

Using 2.6.24-17-rt and its happening on my t61p still... complete and instantaneous hardlock every time.

[lophiomys (lophiomys)]

Confirmed with Kubuntu 8.04 Hardy Heron, all updates
on a Thinkpad T42p 2373
Hotswapping Ultrabay devices (PATA HDD and DVD-RAM) was working perfectly under Gutsy
and is now totally locking and freezing the computer. Only resetting with the power button helps.
This is SHOWSTOPPER for Hardy!!!! very annoying indeet.
I vonlunteer to help out testing a fix.

uname -a
Linux T42p 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

[Noel J. Bergman (noeljb)]

As per Leann's request in Bug 129125, I've installed the first of the 2.6.25 kernels. The good news is that it does *not* freeze. I have not yet tested for functionality of devices inserted into the hot-swap bay.

[Johannes R. (ringe-efreun)]

Confirmed. I'm using a Toshiba Satellite Pro 6100 with Ubuntu 8.04.
It worked in 7.10 Gutsy and I think in 7.04 Feisty too. But I'm not sure about that.

$ uname -r
2.6.24-15-generic

[MWRSA (mwrsa)]

Sadly I have to confirm that, too.
http://ibm-acpi.sourceforge.net/README
says this:
<quote>
UltraBay eject -- /proc/acpi/ibm/bay
------------------------------------

Inserting or ejecting an UltraBay device requires some actions to be
taken by the operating system to safely make or break the electrical
connections with the device.

This feature generates the following ACPI events:

 ibm/bay MSTR 00000003 00000000 -- eject request
 ibm/bay MSTR 00000001 00000000 -- eject lever inserted

NOTE: These events will only be generated if the UltraBay was present
when the laptop was originally booted [...]
</quote>

My thought: Why does this NOT happen even WITH the device inserted? Any ideas? I lack knowledge concerning this, but that's what came into my mind. Maybe just some trigger not set when compiling the kernel, or acpi, or sth.?

Btw, my system: Thinkpad T41p, Hardy, Kernel 2.6.24-19-generic, was -16- before with same effects; latest updates always installed.

[Kedar (kdrlx0-deactivatedaccount)]

Confirmed with Linux ubuntu 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux on Thinkpad R61.
I will get a 2.6.22 kernel and see what the results are.

[Johannes R. (ringe-efreun)]

Confirmed with my new Lenovo R61i too.
2.6.24-19-generic

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[James Ward (jamesward)]

On 2.6.27-1-generic my computer no longer freezes when I remove a drive from the modular bay!

There was an interesting dmesg:
[71146.238059] ata5.00: disabled
[71146.238090] ata5.00: detaching (SCSI 4:0:0:0)
[71146.238090] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[71146.238090] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[71146.238090] sd 4:0:0:0: [sdb] Stopping disk
[71146.238090] sd 4:0:0:0: [sdb] START_STOP FAILED
[71146.238090] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK

I then inserted a DVD Drive and it seemed to work fine. Removing the DVD caused gvfs-hal-volume-monitor to crash. I then reinserted my hard drive and it seemed to work.

So I'd say that for now this bug is closed for Intrepid.

[Leann Ogasawara (leannogasawara)]

Hi James,

Thanks so much for the quick testing and the feedback. I'm going to tentatively wait to mark this bug "Fix Released" until it's officially confirmed we'll be sticking with the 2.6.27 kernel. I'll tag this bug 'fixed-2.6.27' so we know to flip the status when the decision is made.

If others could test as well just to confirm that would be great. Thanks.

[Johannes R. (ringe-efreun)]

Hey,

removing my DVD-Rom on my Thinkpad R60i works in Intrepid Ibex Alpha 5 now.

Linux merlin 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux

Great work! Thanks.

Johannes R.

[Leann Ogasawara (leannogasawara)]

Setting this to "Fix Released" based on the decision to stick with the 2.6.27 kernel for Intrepid - https://lists.ubuntu.com/archives/kernel-team/2008-September/003107.html .

[Jojo (kuzniarpawel)]

works like charm on T61p

[ 1052.036096] ata1.00: disabled
[ 1052.036161] ata1.00: detaching (SCSI 0:0:0:0)
[ 1073.684055] ata1: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen
[ 1073.684069] ata1: ACPI event
[ 1073.684153] ata1: soft resetting link
[ 1073.848722] ata1.00: ATAPI: MATSHITADVD-RAM UJ-862, RB01, max UDMA/33
[ 1073.864614] ata1.00: configured for UDMA/33
[ 1073.864636] ata1: EH complete
[ 1073.869330] scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-862 RB01 PQ: 0 ANSI: 5
[ 1073.906415] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 1073.906624] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 1073.906820] sr 0:0:0:0: Attached scsi generic sg0 type 5

[Jojo (kuzniarpawel)]

should add on Intrepid Alpha 6 2.6.27-generic kernel

[roffik (roffik)]

Confirmed to work normally under Intrepid on Thinkpad T40. Tested with Ultrabay: combo drive.

Linux 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux

[Leann Ogasawara (leannogasawara)]

Thanks for the updates everyone. Unfortunately it's not likely this will be fixed as a Stable Release Update to Dapper so I'm closing the linux-source-2.6.15 task. Thanks.