generic_make_request: Trying to write to read-only block-device loop1 (partno 0)

Bug #1789636 reported by Cristian Aravena Romero
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Hello,

dmesg:
[ 79.648411] ------------[ cut here ]------------
[ 79.648415] generic_make_request: Trying to write to read-only block-device loop1 (partno 0)
[ 79.648437] WARNING: CPU: 0 PID: 305 at block/blk-core.c:2180 generic_make_request_checks+0x4c9/0x610
[ 79.648439] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter devlink ip6_tables iptable_filter cmac bnep samsung_laptop intel_rapl x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp kvm_intel snd_hda_intel uvcvideo btusb kvm btrtl snd_hda_codec irqbypass videobuf2_vmalloc btbcm videobuf2_memops crct10dif_pclmul btintel videobuf2_v4l2 crc32_pclmul videobuf2_common bluetooth ghash_clmulni_intel arc4 cryptd videodev snd_hda_core intel_cstate ecdh_generic media intel_rapl_perf
[ 79.648517] iwldvm snd_hwdep snd_pcm mac80211 input_leds snd_seq_midi joydev snd_seq_midi_event iwlwifi snd_rawmidi serio_raw snd_seq snd_seq_device cfg80211 snd_timer snd mei_me mei soundcore shpchp mac_hid sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace parport_pc ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_generic usbhid hid i915 gpio_ich i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci r8169 drm libahci lpc_ich mii video wmi
[ 79.648588] CPU: 0 PID: 305 Comm: ureadahead Tainted: G OE 4.17.0-9-generic #10-Ubuntu
[ 79.648589] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013
[ 79.648594] RIP: 0010:generic_make_request_checks+0x4c9/0x610
[ 79.648595] RSP: 0018:ffff97eb41ee7d20 EFLAGS: 00010282
[ 79.648598] RAX: 0000000000000000 RBX: ffff89938561b2a0 RCX: 0000000000000006
[ 79.648600] RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff89939f2164b0
[ 79.648602] RBP: ffff97eb41ee7d80 R08: 0000000000000001 R09: 0000000000000364
[ 79.648604] R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000000
[ 79.648607] R13: 0000000000000000 R14: 0000000000000001 R15: ffff8993621bb900
[ 79.648610] FS: 00007f4d8c4747c0(0000) GS:ffff89939f200000(0000) knlGS:0000000000000000
[ 79.648613] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 79.648615] CR2: 00007f4d8c4b9bb0 CR3: 000000030fa8e006 CR4: 00000000000606f0
[ 79.648618] Call Trace:
[ 79.648627] generic_make_request+0x5b/0x410
[ 79.648632] ? mempool_alloc_slab+0x15/0x20
[ 79.648635] ? mempool_alloc+0x71/0x190
[ 79.648640] submit_bio+0x49/0x140
[ 79.648646] submit_bio_wait+0x59/0x90
[ 79.648650] blkdev_issue_flush+0x85/0xb0
[ 79.648657] blkdev_fsync+0x35/0x50
[ 79.648661] vfs_fsync_range+0x48/0x80
[ 79.648665] ? __x64_sys_prctl+0x3c6/0x500
[ 79.648667] do_fsync+0x3d/0x70
[ 79.648670] __x64_sys_fsync+0x14/0x20
[ 79.648675] do_syscall_64+0x5a/0x110
[ 79.648682] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 79.648685] RIP: 0033:0x7f4d8ba56ae1
[ 79.648687] RSP: 002b:00007ffc2d5c0398 EFLAGS: 00000246 ORIG_RAX: 000000000000004a
[ 79.648692] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f4d8ba56ae1
[ 79.648694] RDX: 0000000000000008 RSI: 0000000000000000 RDI: 0000000000000003
[ 79.648696] RBP: 0000000000000003 R08: 0000000000000200 R09: 0000000000000000
[ 79.648699] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[ 79.648700] R13: 000055e74d044600 R14: 00007f4d8c4d0680 R15: 000055e74d02e1e0
[ 79.648702] Code: 8b ad 54 03 00 00 48 8d 75 b0 4c 89 ff c6 05 d1 cc 19 01 01 e8 99 6c 01 00 48 c7 c7 c8 9c 52 a7 44 89 ea 48 89 c6 e8 09 68 c1 ff <0f> 0b 4d 8b 6f 08 e9 c8 fb ff ff 49 8b 76 08 48 85 f6 0f 84 e8
[ 79.648765] ---[ end trace 40ed335baa94347c ]---

Best regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.17.0-9-generic 4.17.0-9.10
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: caravena 3331 F...m pulseaudio
 /dev/snd/controlC0: caravena 3331 F.... pulseaudio
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Wed Aug 29 08:39:22 2018
InstallationDate: Installed on 2017-10-13 (319 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.17.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.17.0-9-generic N/A
 linux-backports-modules-4.17.0-9-generic N/A
 linux-firmware 1.174
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.19 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.19-rc1/

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Cristian Aravena Romero (caravena) wrote :
tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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.