cd/dvd tray opens and closes during boot after kernel update [Solved]

[vimes666]

I just updated from kernel 5.4.0-81 to 5.4.0-84 and from that moment the cd/dvd tray opens and closes during a cold boot.
It happens just before the LM logo appears. As my pc is in a location where there is no room for it to open fully, this is pretty annoying.
Anyone else experiencing this problem?
inxi after reverting to 5.4.0-81:

Code: Select all

System:
  Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: MATE 1.24.0 info: mate-panel wm: marco 1.24.0 dm: LightDM 1.30.0 
  Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq 8000 Elite SFF PC 
  v: N/A serial: <filter> Chassis: type: 4 serial: <filter> 
  Mobo: Hewlett-Packard model: 3646h serial: <filter> BIOS: Hewlett-Packard 
  v: 786G7 v01.14 date: 10/14/2015 
CPU:
  Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP 
  arch: Penryn rev: A L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11969 
  Speed: 1995 MHz min/max: 1998/3000 MHz Core speeds (MHz): 1: 1995 2: 1995 
Graphics:
  Device-1: Intel 4 Series Integrated Graphics vendor: Hewlett-Packard 
  driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2e12 
  Display: x11 server: X.Org 1.20.11 driver: modesetting 
  unloaded: fbdev,vesa compositor: marco v: 1.24.0 
  resolution: 1680x1050~60Hz 
  OpenGL: renderer: Mesa DRI Intel Q45/Q43 (ELK) v: 2.1 Mesa 20.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel 82801JD/DO HD Audio vendor: Hewlett-Packard 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3a6e 
  Sound Server: ALSA v: k5.4.0-81-generic 
Network:
  Device-1: Intel 82567LM-3 Gigabit Network vendor: Hewlett-Packard 
  driver: e1000e v: 3.2.6-k port: 1100 bus ID: 00:19.0 chip ID: 8086:10de 
  IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Qualcomm Atheros AR9227 Wireless Network Adapter driver: ath9k 
  v: kernel port: 11e0 bus ID: 10:00.0 chip ID: 168c:002d 
  IF: wlp16s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 456.46 GiB used: 57.98 GiB (12.7%) 
  ID-1: /dev/sda vendor: SanDisk model: SDSSDA240G size: 223.57 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 70RL scheme: MBR 
  ID-2: /dev/sdb vendor: Hitachi model: HDS721025CLA682 size: 232.89 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: A41A scheme: MBR 
Partition:
  ID-1: / size: 212.16 GiB used: 57.98 GiB (27.3%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 7.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/home:ungoogled_chromium.list 
  1: deb http://download.opensuse.org/repositories/home:/ungoogled_chromium/Ubuntu_Focal/ /
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyana main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/recoll-backports-recoll-1_15-on-focal.list 
  1: deb http://ppa.launchpad.net/recoll-backports/recoll-1.15-on/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/recoll-backports/recoll-1.15-on/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/remmina-ppa-team-remmina-next-focal.list 
  1: deb http://ppa.launchpad.net/remmina-ppa-team/remmina-next/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/remmina-ppa-team/remmina-next/ubuntu focal main
Info:
  Processes: 177 Uptime: 14m Memory: 7.65 GiB used: 843.7 MiB (10.8%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: mate-terminal inxi: 3.0.38 

[kyphi]

I get that on wake after suspend occurring after upgrade to kernel 5.4.0-84.
Reversion to kernel 5.4.0-81 avoids that problem.

[mdavies5]

I have tested both scenarios in Mint 20.2 Uma on a Toshiba laptop but could not reproduce the problem. Could it be a desktop or Motherboard problem?

[vimes666]

Yes, it seems to be specific on that computer/release (HP/20 Ulyana). On one of my other pc's (HP/20.1) it does not happen.
I also deactivated the cd drive in the bios (about the only thing I can change there) but the drive keeps opening and closing during boot.

[MikeNavy]

Hi,

Same problem here with ASUS G74SX, kernel 5.4.0-84, Mint 20.2 Mate.

DVD tray self opens during the boot.

DVD tray type: Slimtype BD E DS4E1S (EA2B)

MN

[vimes666]

Just noticed -like Kyphi mentioned before- that when waking from a suspend it just opens.

[jcoles]

I have exactly the same behaviour after updating to kernel 5.11.0-34 from 5.11.0-27.
CD/DVD tray does not open when cold-booting from the previous kernel, confirming that this must be kernel-related.
This is not a show-stopper for me, but it is a little annoying.

HP Compaq Elite 8300 SFF mobo model 3397
Intel Core i7-3770
HP DVD D DH16D6SH
Linux Mint 20.2 Uma MATE

[gittiest personITW]

Yes, I have the issue where the Dvd drive opens after coming out of Suspend since updating the kernel to 4.15.0-156.163.
However, there were a lot of updates that were done at the same time - so it might be one of the others.

Edit,
Timeshifted back to before the updates including Kernel update.
All fine.
Installed all updates except for kernel and problem still gone - so for now will assume it is the kernel update that caused the issue on my system.

[Night Wing]

I also have the DVD tray opening and closing on a cold boot. The tray also opens after waking from sleep mode, but it does not close. I have to manually close the tray. This started happening on the newest kernel update (5.4.0-84).

The above is only happening on two different models of desktop tower computers I own. This does not happen with either of my two laptop computers.

I'm using 64 bit Mint 20.2 (Uma) Xfce.

[ricardogroetaers]

Other users with the same problem:
viewtopic.php?f=90&t=356736

[Night Wing]

Here are my specs from the terminal.

Code: Select all

joe@joe-BN496AV-ABA-HPE-170t:~$ inxi -Sdx
System:
  Host: joe-BN496AV-ABA-HPE-170t Kernel: 5.4.0-84-generic x86_64 bits: 64 
  compiler: gcc v: 9.3.0 Desktop: Xfce 4.16.0 Distro: Linux Mint 20.2 Uma 
  base: Ubuntu 20.04 focal 
Drives:
  Local Storage: total: 1.82 TiB used: 13.83 GiB (0.7%) 
  ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  ID-2: /dev/sdb vendor: Western Digital model: WD1001FAES-75W7A0 
  size: 931.51 GiB 
  Optical-1: /dev/sr0 vendor: hp model: DVD A DH16AAL rev: LHDE 
  dev-links: cdrom,cdrw,dvdrw 
  Features: speed: 40 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
  Optical-2: /dev/sr1 vendor: hp model: DVD D DH16D5S rev: VHD7 
  dev-links: dvd 
  Features: speed: 40 multisession: yes audio: yes dvd: yes rw: none 
  state: running 
joe@joe-BN496AV-ABA-HPE-170t:~$ 

[momo608]

Same here, (tray opens and stays open), I'm also in that linked thread. Yes, annoying. First actual problem with the system worth complaining about since I installed it over two years ago.

So, what's next, do the tech guys read these posts and work on solutions and send us a repair update through the update manager?

I was preparing to do a timeshift to a previous state but since I don't know what I'm doing there I abandoned it. By the looks of it, seems we only have a few days of snapshots before the bad update to go that route.

[Night Wing]

I'm hoping for another kernel update which does not include this annoying bug in it.

[vimes666]

What is bothering me is that I have not seen this problem pop up in ubuntu or any ubuntu based distro other than LM (cinnamon, mate and xfce).

[gittiest personITW]

Timeshifted back to before the updates including Kernel update.
All fine.
Installed all updates except for kernel and problem still gone - so for now will assume it is the kernel update that caused the issue on my system.

[momo608]

Timeshifted back to before the updates including Kernel update.
All fine.
Installed all updates except for kernel and problem still gone - so for now will assume it is the kernel update that caused the issue on my system.

I did the same, was it Linux Kernel 4.15.0-156.163

[deepakdeshp]

Same here, (tray opens and stays open), I'm also in that linked thread. Yes, annoying. First actual problem with the system worth complaining about since I installed it over two years ago.

So, what's next, do the tech guys read these posts and work on solutions and send us a repair update through the update manager?

I was preparing to do a timeshift to a previous state but since I don't know what I'm doing there I abandoned it. By the looks of it, seems we only have a few days of snapshots before the bad update to go that route.

No tech guys don't read the forums. Kernel updates aren't done by the Mint team. They are done by Linus team and the Ubuntu team.
https://bugzilla.kernel.org/

[gittiest personITW]

Timeshifted back to before the updates including Kernel update.
All fine.
Installed all updates except for kernel and problem still gone - so for now will assume it is the kernel update that caused the issue on my system.

I did the same, was it Linux Kernel 4.15.0-156.163

Yes

[ricardogroetaers]

Thanks to the authors by creating this topic and the referenced topic.
Observation:
For those who use the series 4.15 kernel.
The kernel "4.15.0-153" is very good.

[johnswan]

I was having the same problem of one of my optical drives opening on boot up, with Linux Mint 19.1 after a kernel update. I have now blacklisted linux-4.150.156.145 and reverted to 4.15.0-154-generic and the problem has disappeared. I also had to blacklist 4.15.0.158.147

Kernel update, 4.15.0.159.148 received on 28 September does not seem to cause this problem so far.