print_req_error: critical target error, dev sr0, sector 2097136

Bug #1740289 reported by Cristian Aravena Romero
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Hello,

dmesg:
[ 1816.482664] print_req_error: critical target error, dev sr0, sector 2097136

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-17-generic 4.13.0-17.20
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: caravena 1655 F...m pulseaudio
 /dev/snd/controlC0: caravena 1655 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 27 15:28:36 2017
InstallationDate: Installed on 2017-10-13 (75 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-17-generic N/A
 linux-backports-modules-4.13.0-17-generic N/A
 linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
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.15 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.15-rc6/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

I saw the exact same messages when running bionic installed through latest cdimage builds of ubuntu. It's visible on boot almost every time (although once I noticed it was not present in the boot logs and dmesg, so it might not be reproducible 100% of the time).

I tried the latest mainline kernel, in this case: 4.15.0-041500rc8 and the issue seems to still be present (output still there). Confirmed I'm running the 4.15 kernel.
Please note my testing environment is a standard kvm instance.

Tagging.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Also, I just wonder why I'm actually seeing this error printed during boot even when the 'quiet splash' options are in the cmdline. I would expect everything to be silenced-out completely in such case.

Revision history for this message
ubuntu38 (ubuntu38) wrote :

I know this is about Ubuntu but I have exact same issue using an Arch Linux x86_64 installation with kernel 4.15.6 on another computer if that can help to rule out anything.

Revision history for this message
A. Denton (aquina) wrote :

It's not exactly the same, but I see the following during reboot, when testing Xubuntu 18.04 daily ISO (2018-04-21), on VirtualBox 4.3 installed on a trusty system.

[ 118.XXXXXX] print_req_error: I/O error, dev sr0, sector 1178984
[ 118.XXXXXX] print_req_error: I/O error, dev loop0, sector 1177462

References:
http://cdimage.ubuntu.com/xubuntu/daily-live/current/
https://www.google.com/search?q=launchpad+print_req_error%3A+I%2FO+error%2C+dev+sr0

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1740289

tags: added: iso-testing
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.