DVD drive works under Win dows 10 but not Ubuntu 17.10

Bug #1758463 reported by G Money
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Drive does not mount when any supported media type is inserted and is unusable. Older drive(NEC DVD+/-RW ND-6650A) with newer motherboard (Z370N-WIFI).

greg@greg-Z370N-WIFI:~$ dmesg |grep -i ata3
[ 0.660472] ata3: SATA max UDMA/133 abar m2048@0xf724b000 port 0xf724b200 irq 129
[ 0.980029] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 0.983555] ata3.00: ATAPI: _NEC DVD+/-RW ND-6650A, 103D, max UDMA/33
[ 0.983556] ata3.00: applying bridge limits
[ 0.990656] ata3.00: configured for UDMA/33
[ 6.112005] ata3.00: qc timeout (cmd 0xa0)
[ 6.116004] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 6.432011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 6.442649] ata3.00: configured for UDMA/33
[ 11.488004] ata3.00: qc timeout (cmd 0xa0)
[ 11.488008] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 11.488009] ata3: limiting SATA link speed to 1.5 Gbps
[ 11.488010] ata3.00: limiting speed to UDMA/33:PIO3
[ 11.804011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 11.814638] ata3.00: configured for UDMA/33
[ 16.864003] ata3.00: qc timeout (cmd 0xa0)
[ 16.864007] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 16.864008] ata3.00: disabled
[ 16.868004] ata3: hard resetting link
[ 17.184011] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 17.184014] ata3: EH complete
greg@greg-Z370N-WIFI:~$

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-37-generic 4.13.0-37.42
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: greg 1651 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 17:17:43 2018
GvfsMonitorError:
 This tool has been deprecated, use 'gio mount' instead.
 See 'gio help mount' for more info.
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=c0e62877-bafa-4694-b2c3-8f4f2e1df82f
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2018-03-17 (6 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Gigabyte Technology Co., Ltd. Z370N WIFI
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=4b0ef4f1-040a-46c5-af19-f012da1ef057 ro quiet splash acpi=off i915.alpha_support=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-37-generic N/A
 linux-backports-modules-4.13.0-37-generic N/A
 linux-firmware 1.169.3
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 17:18:20.743: The udisks-daemon is running (name-owner :1.2).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: Default string
dmi.board.name: Z370N WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd11/09/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z370N WIFI
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
G Money (gmun) wrote :
information type: Public → Private Security
G Money (gmun)
information type: Private Security → Public
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
G Money (gmun) wrote :

Also exists in 16.04LTS and upstream in v4.16-rc7. tag::kernel-bug-exists-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.