[Kernel-packages] [Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command
I can't answer what is happening here. But can you obtain more information using SysRq-t and SysRq-m as described at https://akari.osdn.jp/capturing-kernel-messages.html#Tips5 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762450 Title: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command Status in linux package in Ubuntu: Confirmed Bug description: I've upgraded to 18.04. Since then, it's impossible to use thumb- drives. If I try, on the first write operation, that operation hangs. Trying to issue a 'sync' command that hangs too. After a while (some minutes or so?) I see the following in kernel log / dmesg (see later). It's not even possible to cleanly shut the computer down, as it also hangs then. kernel is: 4.15.0-15-generic Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -S /boot/vmlinuz-4.15.0-15-generic linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic $ dpkg -l linux-image-4.15.0-15-generic ii linux-image-4.15.0-15-generic4.15.0-15.16 amd64 Linux kernel image for version 4.15.0 on 64 bit x86 SMP dmesg: [ 110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd [ 111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00 [ 111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 111.083441] usb 6-1: Product: DataTraveler 2.0 [ 111.083444] usb 6-1: Manufacturer: Kingston [ 111.083447] usb 6-1: SerialNumber: 5B7402949950 [ 111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected [ 111.157882] scsi host6: usb-storage 6-1:1.0 [ 111.158826] usbcore: registered new interface driver usb-storage [ 111.174387] usbcore: registered new interface driver uas [ 112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS [ 112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 GB/1.92 GiB) [ 112.443462] sd 6:0:0:0: [sdb] Write Protect is off [ 112.443464] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 112.443586] sd 6:0:0:0: [sdb] No Caching mode page found [ 112.443591] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 112.447045] sd 6:0:0:0: [sdb] Attached SCSI removable disk this was ok, the problem is from here: [ 363.231738] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 363.231745] Tainted: G OE4.15.0-15-generic #16-Ubuntu [ 363.231747] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.231750] fdisk D0 1798 1728 0x [ 363.231754] Call Trace: [ 363.231764] __schedule+0x297/0x8b0 [ 363.231768] ? fdatawait_one_bdev+0x20/0x20 [ 363.231771] schedule+0x2c/0x80 [ 363.231775] io_schedule+0x16/0x40 [ 363.231779] wait_on_page_bit_common+0xd8/0x160 [ 363.231782] ? page_cache_tree_insert+0xe0/0xe0 [ 363.231785] __filemap_fdatawait_range+0xfa/0x160 [ 363.231788] ? __filemap_fdatawrite_range+0xc1/0x100 [ 363.231791] ? __filemap_fdatawrite_range+0xcd/0x100 [ 363.231794] ? __sync_filesystem+0x60/0x60 [ 363.231797] filemap_fdatawait_keep_errors+0x1e/0x40 [ 363.231799] fdatawait_one_bdev+0x16/0x20 [ 363.231802] iterate_bdevs+0xb7/0x160 [ 363.231805] sys_sync+0x7e/0xb0 [ 363.231809] do_syscall_64+0x73/0x130 [ 363.231813] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 363.231816] RIP: 0033:0x7f2fcff17287 [ 363.231817] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX: 00a2 [ 363.231820] RAX: ffda RBX: 56096b767400 RCX: 7f2fcff17287 [ 363.231821] RDX: RSI: 56096b766018 RDI: 56096b767400 [ 363.231823] RBP: 7fffbbea82d8 R08: 000a R09: 7472617020656854 [ 363.231824] R10: 0008 R11: 0202 R12: 56096a25b198 [ 363.231825] R13: R14: 56096a25b198 R15: [ 484.045928] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 484.045934] Tainted: G OE4.15.0-15-generic #16-Ubuntu [ 484.045936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.045939] fdisk D0 1798 1728 0x [ 484.045942] Call Trace: [ 484.045950] __schedule+0x297/0x8b0 [ 484.045954] ? fdatawait_one_bdev+0x20/0x20 [ 484.045956] schedule+0x2c/0x80 [ 484.045959] io_schedule+0x16/0x40 [ 484.045962] wait_on_page_bit_common+0xd8/0x160 [ 484.045965] ? page_cache_tree_insert+0xe0/0xe0 [ 484.045967] __filemap_fdatawait_range+0xfa/0x160 [ 484.045970] ? __filemap_fdatawrite_range+0xc1/0x100 [
[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system
Since 18.04 seems to give up LSM stacking patchset, safest choice (if
acceptable) would be to completely revert LSM stacking patchset for
17.10 as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
In Progress
Bug description:
== SRU Justification ==
The following commit introduced a regression identified in bug 1734327:
ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of
the remaining blobs")
The regression causes a kernel panic to occur after multiple TCP connection
creations/closures to the localhost. The bug was found using STAF RPC calls,
but is easily reproducible with SSH.
A revert of commit ac8f82a0b6d9 is needed to resolve this bug. However,
commit 4ae2508f0bed
also needs to be reverted because it depend on commit ac8f82a0b6d9.
== Fix ==
Revert 4ae2508f0bed ("UBUNTU: SAUCE: LSM stacking: add stacking support to
apparmor network hooks")
Revert ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure
management of the remaining blobs")
== Test Case ==
A test kernel was built with these two commits reverted and tested by the
original bug reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Description ==
Summary:
Kernel panic occurs after multiple TCP connection creations/closures to the
localhost.
The bug was found using STAF RPC calls, but is easily reproducible with SSH.
The bug doesn't appear on an identical virtual machine booting from the disk.
The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
The bug is reproducible using an older 4.13.0-16-generic kernel
Reproducible on multiple hardware types.
Unable to create a kernel memory dump due to makedumpfile errors.
apport-bug save attached.
NFSRoot boot options:
vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw
Software:
OS: Ubuntu 17.10
Kernel: 4.13.0-17-generic x86_64
Reproduction steps:
1. Boot a system from a nfsroot
2. Configure password-less localhost ssh access
3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
4. Wait for system to crash
Trace:
4,1151,52372730,-;general protection fault: [#1] SMP
4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops
ahci ptp drm libahci pps_core wmi
4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted
4.13.0-17-generic #20-Ubuntu
4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0
12/17/2015
4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
4,1159,52373521,-;RAX: RBX: 241c89490001 RCX:
0004
4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI:
62fac000
4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09:
943bb839
4,1162,52373656,-;R10: 00904c789100 R11: R12:
9d09267ef000
4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15:
9d09267ef000
4,1164,52373746,-;FS: 7f3a53313700() GS:9d092ecc()
knlGS:
4,1165,52373797,-;CS: 0010 DS: ES: CR0: 80050033
4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4:
003406e0
4,1167,52373878,-;DR0: DR1: DR2:
4,1168,52373923,-;DR3: DR6: fffe0ff0 DR7:
0400
4,1169,52373968,-;Call Trace:
4,1170,52373987,-;
4,1171,52374009,-; security_sk_free+0x3e/0x50
4,1172,52374042,-; __sk_destruct+0x108/0x190
4,1173,52374070,-;
[Kernel-packages] [Bug 1752621] Re: BUG: unable to handle kernel paging request at ffffded5330000a0
Thanks for reporting. This is a duplicate of bug 1734327 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752621 Title: BUG: unable to handle kernel paging request at ded533a0 Status in linux package in Ubuntu: Confirmed Bug description: [ 155.111268] BUG: unable to handle kernel paging request at ded533a0 [ 155.111335] IP: kfree+0x53/0x160 [ 155.111357] PGD 0 [ 155.111358] P4D 0 [ 155.111401] Oops: [#1] SMP PTI [ 155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii [ 155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic #40-Ubuntu [ 155.111853] Hardware name: Gigabyte Technology Co., Ltd. H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012 [ 155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000 [ 155.111942] RIP: 0010:kfree+0x53/0x160 [ 155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282 [ 155.111998] RAX: RBX: 00102aa3 RCX: 0003 [ 155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 716c4000 [ 155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: bafc6a19 [ 155.112121] R10: ded53380 R11: R12: 8e974abe7800 [ 155.112162] R13: baba74d4 R14: R15: 8e9714f4d3c0 [ 155.112204] FS: () GS:8e975fa0() knlGS: [ 155.112250] CS: 0010 DS: ES: CR0: 80050033 [ 155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 000606f0 [ 155.112326] Call Trace: [ 155.112349] security_sk_free+0x44/0x60 [ 155.112377] __sk_destruct+0x10b/0x190 [ 155.112403] sk_destruct+0x20/0x30 [ 155.112427] __sk_free+0x82/0xa0 [ 155.112451] sk_free+0x19/0x20 [ 155.112472] tcp_close+0x238/0x3f0 [ 155.112498] inet_release+0x42/0x70 [ 155.112522] sock_release+0x25/0x80 [ 155.112546] sock_close+0x12/0x20 [ 155.114960] __fput+0xea/0x230 [ 155.117332] fput+0xe/0x10 [ 155.119604] task_work_run+0x7c/0xa0 [ 155.121861] do_exit+0x2d2/0xae0 [ 155.124100] ? entry_SYSCALL_64_after_hwframe+0xd4/0x139 [ 155.126330] ? entry_SYSCALL_64_after_hwframe+0xc6/0x139 [ 155.128524] ? entry_SYSCALL_64_after_hwframe+0xbf/0x139 [ 155.130674] ? entry_SYSCALL_64_after_hwframe+0xb8/0x139 [ 155.132757] ? entry_SYSCALL_64_after_hwframe+0xb1/0x139 [ 155.134769] do_group_exit+0x43/0xb0 [ 155.136307] SyS_exit_group+0x14/0x20 [ 155.138219] entry_SYSCALL_64_fastpath+0x24/0xab [ 155.140110] RIP: 0033:0x7fe7b4851fd8 [ 155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 00e7 [ 155.143882] RAX: ffda RBX: 563529f04030 RCX: 7fe7b4851fd8 [ 155.145590] RDX: RSI: 003c RDI: [ 155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: fef8 [ 155.148956] R10: 7fe7acf95148 R11: 0246 R12: 7fe7acf94d90 [ 155.150230] R13: 0036 R14: R15: 7ffe7f1d1c10 [ 155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [ 155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8 [ 155.154283] CR2: ded533a0 [ 155.167949] ---[ end trace 28ca6dd18121abd3 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1058 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 1 20:51:56 2018 HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5 InstallationDate: Installed on 2018-02-23 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: enp3s0no wireless extensions. lono wireless
[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system
No plan to land upstream yet. Casey's upstream proposal
(
http://kernsec.org/pipermail/linux-security-module-archive/2017-December/004728.html
) is stalling.
Please carry my patch as UBUNTU: SAUCE: patch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
In Progress
Bug description:
== SRU Justification ==
The following commit introduced a regression identified in bug 1734327:
ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of
the remaining blobs")
The regression causes a kernel panic to occur after multiple TCP connection
creations/closures to the localhost. The bug was found using STAF RPC calls,
but is easily reproducible with SSH.
A revert of commit ac8f82a0b6d9 is needed to resolve this bug. However,
commit 4ae2508f0bed
also needs to be reverted because it depend on commit ac8f82a0b6d9.
== Fix ==
Revert 4ae2508f0bed ("UBUNTU: SAUCE: LSM stacking: add stacking support to
apparmor network hooks")
Revert ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure
management of the remaining blobs")
== Test Case ==
A test kernel was built with these two commits reverted and tested by the
original bug reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Description ==
Summary:
Kernel panic occurs after multiple TCP connection creations/closures to the
localhost.
The bug was found using STAF RPC calls, but is easily reproducible with SSH.
The bug doesn't appear on an identical virtual machine booting from the disk.
The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
The bug is reproducible using an older 4.13.0-16-generic kernel
Reproducible on multiple hardware types.
Unable to create a kernel memory dump due to makedumpfile errors.
apport-bug save attached.
NFSRoot boot options:
vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw
Software:
OS: Ubuntu 17.10
Kernel: 4.13.0-17-generic x86_64
Reproduction steps:
1. Boot a system from a nfsroot
2. Configure password-less localhost ssh access
3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
4. Wait for system to crash
Trace:
4,1151,52372730,-;general protection fault: [#1] SMP
4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops
ahci ptp drm libahci pps_core wmi
4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted
4.13.0-17-generic #20-Ubuntu
4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0
12/17/2015
4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
4,1159,52373521,-;RAX: RBX: 241c89490001 RCX:
0004
4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI:
62fac000
4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09:
943bb839
4,1162,52373656,-;R10: 00904c789100 R11: R12:
9d09267ef000
4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15:
9d09267ef000
4,1164,52373746,-;FS: 7f3a53313700() GS:9d092ecc()
knlGS:
4,1165,52373797,-;CS: 0010 DS: ES: CR0: 80050033
4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4:
003406e0
4,1167,52373878,-;DR0: DR1: DR2:
4,1168,52373923,-;DR3: DR6: fffe0ff0 DR7:
0400
4,1169,52373968,-;Call Trace:
4,1170,52373987,-;
4,1171,52374009,-; security_sk_free+0x3e/0x50
4,1172,52374042,-;
[Kernel-packages] [Bug 1749221] Re: kernel crash / BUG: unable to handle kernel paging request at fffffe3ed8000020
Since you are using apparmor=0 parameter,
this will be a duplicate of bug 1734327.
Try removing apparmor=0 parameter for now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1749221
Title:
kernel crash / BUG: unable to handle kernel paging request at
fe3ed820
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Confirmed
Bug description:
Booted under maas in rescue mode system console has the attached failure.
First bit is
[ 440.196466] BUG: unable to handle kernel paging request at
fe3ed820
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic (not installed)
ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Feb 13 15:32 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
Date: Tue Feb 13 15:34:40 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=username/amd64/generic/xenial/daily/boot-kernel
nomodeset
root=squash:http://10.247.16.6:5248/images/username/amd64/generic/xenial/daily/squashfs
ro ip=hostname:BOOTIF ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.247.16.6:5240/MAAS/metadata/latest/by-id/sbgyxn/?op=get_preseed
apparmor=0 log_host=10.247.16.6 log_port=514 --- console=ttyS1
BOOTIF=01-ec:b1:d7:7f:2a:6c
RelatedPackageVersions:
linux-restricted-modules-4.13.0-32-generic N/A
linux-backports-modules-4.13.0-32-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2015
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrP89:bd03/05/2015:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant DL360 Gen9
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749221/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744071] Re: linux 3.13.0-140.189 - kernel panic after trying to launch any 32-bit application
You can monitor https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744199 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744071 Title: linux 3.13.0-140.189 - kernel panic after trying to launch any 32-bit application Status in linux package in Ubuntu: Confirmed Bug description: I have installed linux-image-3.13.0-140-lowlatency from -proposed. This kernel panics immediately when I try to start any 32-bit program. The previous version (linux-image-3.13.0-139-lowlatency) works fine. --- Architecture: amd64 DistroRelease: Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744199] Re: ubuntu_32_on_64 test crash Trusty 3.13.0-140 amd64 system
F.Y.I. Here is the kernel panic message.
You can google for "PANIC: double fault, error_code: 0x0".
[ 193.361839] PANIC: double fault, error_code: 0x0
[ 193.363960] Kernel panic - not syncing: Machine halted.
[ 193.366020] CPU: 1 PID: 1822 Comm: a.out Not tainted 3.13.0-140-generic
#189-Ubuntu
[ 193.368882] Hardware name: VMware, Inc. VMware Virtual Platform/440BX
Desktop Reference Platform, BIOS 6.00 07/02/2015
[ 193.371892] 88013a627e90 8172e82c
81a44fd6
[ 193.374275] 88013a627f08 8172764f
88010008
[ 193.376712] 88013a627f18 88013a627eb8 304a
0046
[ 193.379181] Call Trace:
[ 193.379957] <#DF> [] dump_stack+0x64/0x82
[ 193.381810] [] panic+0xc8/0x1e1
[ 193.383271] [] df_debug+0x31/0x40
[ 193.384737] [] do_double_fault+0x80/0x100
[ 193.386361] [] double_fault+0x28/0x30
[ 193.387891] [] ? ia32_sysenter_target+0x4f/0x195
[ 193.389691] <>
[ 193.390626] Kernel Offset: 0x0 from 0x8100 (relocation range:
0x8000-0x9fff)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1744199
Title:
ubuntu_32_on_64 test crash Trusty 3.13.0-140 amd64 system
Status in linux package in Ubuntu:
Confirmed
Bug description:
THIS IS A POTENTIAL REGRESSION
Steps:
1. Deploy a Trusty amd64 node (node pepe in this case)
2. sudo apt-get install git python-minimal -y
3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-b master-next
4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
5. rm -fr autotest/client/tests
6. ln -sf ~/autotest-client-tests autotest/client/tests
7. Monitor the syslog with tail -f /var/log/syslog
8. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_32_on_64/control.ubuntu
Result:
* The system will hang without any output in syslog. I can't see any error
message from ipmi output as well.
This test can pass with 3.13.0-139
Output:
ubuntu@pepe:~$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E
autotest/client/autotest-local --verbose
autotest/client/tests/ubuntu_32_on_64/control.ubuntu
03:53:08 INFO | Writing results to
/home/ubuntu/autotest/client/results/default
03:53:08 DEBUG| Initializing the state engine
03:53:08 DEBUG| Persistent state client.steps now set to []
03:53:08 DEBUG| Persistent option harness now set to None
03:53:08 DEBUG| Persistent option harness_args now set to None
03:53:08 DEBUG| Selected harness: standalone
03:53:08 INFO | START timestamp=1516333988localtime=Jan
19 03:53:08
03:53:08 DEBUG| Persistent state client._record_indent now set to 1
03:53:08 INFO | START ubuntu_32_on_64 ubuntu_32_on_64
timestamp=1516333988localtime=Jan 19 03:53:08
03:53:08 DEBUG| Persistent state client._record_indent now set to 2
03:53:08 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_32_on_64', 'ubuntu_32_on_64')
03:53:08 WARNI| Could not find GDB installed. Crash handling will operate
with limited functionality
03:53:08 DEBUG| Running 'apt-get install --yes --force-yes build-essential
gcc-multilib'
03:53:08 DEBUG| [stdout] Reading package lists...
03:53:08 DEBUG| [stdout] Building dependency tree...
03:53:08 DEBUG| [stdout] Reading state information...
03:53:09 DEBUG| [stdout] build-essential is already the newest version.
03:53:09 DEBUG| [stdout] gcc-multilib is already the newest version.
03:53:09 DEBUG| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not
upgraded.
03:53:09 DEBUG| Running 'which gcc'
03:53:09 DEBUG| [stdout] /usr/bin/gcc
03:53:09 DEBUG| Running
'/home/ubuntu/autotest/client/tmp/ubuntu_32_on_64/src/forkexec date'
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-140-generic 3.13.0-140.189
ProcVersionSignature: User Name 3.13.0-140.189-generic 3.13.11-ckt39
Uname: Linux 3.13.0-140-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 19 03:43 seq
crw-rw 1 root audio 116, 33 Jan 19 03:43 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Fri Jan 19 03:44:08 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
The problematic patches are not yet in mainline/upstream kernels, and hence the fix patch is not yet in mainline/upstream kernels. Please ask Joseph Salisbury when the action for Artful kernel will be taken. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
OK. Your report will be duplicate of 1731031, 1734327, 1734686. Explanation of the bug is http://kernsec.org/pipermail/linux-security-module-archive/2017-November/004532.html and the fix for the bug is http://kernsec.org/pipermail/linux-security-module-archive/2017-December/004638.html . According to http://kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/log/security , neither the problematic patches are reverted nor the fix patch is applied. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Forgot to mention. Try removing apparmor=0 parameter for now. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734686 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
The dump looks like below bug. Was the bug already fixed in 4.13.0-25.29 ? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731031 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734327 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739928] Re: Kernel segfault playing EVERSPACE
As far as I can see, nothing is wrong, except you put too much memory pressure on your machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739928 Title: Kernel segfault playing EVERSPACE Status in linux package in Ubuntu: Confirmed Bug description: Here is the stacktrace: https://paste.ubuntu.com/26240799 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vadi 7458 F pulseaudio /dev/snd/controlC0: vadi 7458 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Dec 24 03:47:54 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-23 (2101 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3 ProcFB: 0 VESA VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: Z68AP-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68AP-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739928] Re: Kernel segfault playing EVERSPACE
Well, not 6 seconds. It is 21 seconds. I overlooked that timestamp in syslog and uptime are not in sync. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739928 Title: Kernel segfault playing EVERSPACE Status in linux package in Ubuntu: Confirmed Bug description: Here is the stacktrace: https://paste.ubuntu.com/26240799 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vadi 7458 F pulseaudio /dev/snd/controlC0: vadi 7458 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Dec 24 03:47:54 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-23 (2101 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3 ProcFB: 0 VESA VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: Z68AP-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68AP-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739928] Re: Kernel segfault playing EVERSPACE
It seems to me that this is not a kernel problem. I guess that there was a NULL pointer dereference in RSG-Linux-Shipping when the system started entering severe memory pressure. Then, due to severe memory pressure, many memory allocation requests started stalling. But there is no kernel oops messages, which means that the kernel should not be in inconsistent state. -- Dec 23 20:08:25 gooseberry kernel: [83579.182919] vboxdrv: VBoxEhciR0.r0 Dec 23 20:37:43 gooseberry kernel: [85336.572498] RSG-Linux-Shipp[4986]: segfault at 0 ip (null) sp 7fffe2493778 error 14 in RSG-Linux-Shipping[40+638c000] Dec 23 20:38:58 gooseberry kernel: [85389.847138] rtkit-daemon: page allocation stalls for 10224ms, order:0, mode:0x14200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null) Dec 23 20:39:02 gooseberry kernel: [85392.351015] nacl_helper: page allocation stalls for 10660ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:03 gooseberry kernel: [85394.373753] CIPCServer::Thr: page allocation stalls for 13060ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:04 gooseberry kernel: [85394.418114] redshift: page allocation stalls for 10768ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:04 gooseberry kernel: [85394.626684] java: page allocation stalls for 13336ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:05 gooseberry kernel: [85394.710998] java: page allocation stalls for 14172ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:05 gooseberry kernel: [85395.064425] gmain: page allocation stalls for 12828ms, order:0, mode:0x1420848(GFP_NOFS|__GFP_NOFAIL|__GFP_HARDWALL|__GFP_MOVABLE), nodemask=(null) Dec 23 20:39:06 gooseberry kernel: [85396.166591] java: page allocation stalls for 12360ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:07 gooseberry kernel: [85396.182852] dropbox: page allocation stalls for 14584ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85396.444863] java: page allocation stalls for 15116ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85397.998896] SlateLoading1: page allocation stalls for 11004ms, order:0, mode:0x1400840(GFP_NOFS|__GFP_NOFAIL), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85399.180885] Chrome_FileThre: page allocation stalls for 12120ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85399.937947] java: page allocation stalls for 20236ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85402.716378] CHTTPClientThre: page allocation stalls for 21712ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85403.440140] keybase: page allocation stalls for 21264ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85404.113506] chrome: page allocation stalls for 13840ms, order:0, mode:0x14200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85404.148676] dropbox: page allocation stalls for 20224ms, order:0, mode:0x14200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85404.415977] dropbox: page allocation stalls for 20492ms, order:0, mode:0x14200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85404.788766] dropbox: page allocation stalls for 23188ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85406.296349] keybase: page allocation stalls for 24120ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85406.912627] Watchdog: page allocation stalls for 10744ms, order:0, mode:0x14200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85408.143462] java: page allocation stalls for 27644ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85408.314888] java: page allocation stalls for 24508ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85408.915217] java: page allocation stalls for 29212ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85409.229332] java: page allocation stalls for 28728ms, order:0, mode:0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null) Dec 23 20:39:08 gooseberry kernel: [85409.759119] chrome: page allocation stalls for 16468ms, order:0,
[Kernel-packages] [Bug 1734686] Re: BUG: unable to handle kernel paging request at ffffdf3cd60001a0
Thank you for reporting this problem. Ubuntu 17.10 kernel has "LSM: Stacking for major security modules" patches enabled and this problem will be a bug in the patches. That's why mainline 4.13.11 kernel works fine. I reported this problem at http://kernsec.org/pipermail/linux-security-module-archive/2017-November/004532.html and waiting for a fix. Meanwhile, you can use mainline kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734686 Title: BUG: unable to handle kernel paging request at df3cd60001a0 Status in linux package in Ubuntu: Confirmed Bug description: I can consistently reproduce this with the Ubuntu 17.10 kernel. It never happens with a mainline 4.13.11 kernel built from source. To reproduce: 1. clone https://github.com/nodejs/node (currently at commit 4ca4db0d4c) 2. ./configure && make -j8 3. ./out/Release/cctest cctest is sometimes killed, sometimes locks up the computer. When the computer is still usable, the following message is logged: [36488.886799] BUG: unable to handle kernel paging request at df3cd60001a0 [36488.886824] IP: kfree+0x53/0x190 [36488.886831] PGD 0 [36488.886831] P4D 0 [36488.886844] Oops: [#2] PREEMPT SMP [36488.886851] Modules linked in: xt_tcpudp iptable_filter cfg80211 binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_realtek snd_hda_codec_generic intel_cstate r8712u(C) intel_rapl_perf snd_seq_midi snd_seq_midi_event input_leds snd_hda_intel snd_rawmidi snd_hda_codec snd_hda_core snd_seq snd_hwdep snd_pcm snd_seq_device snd_timer snd ie31200_edac soundcore mei_me shpchp mei lpc_ich mac_hid cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt uas ahci fb_sys_fops usbhid usb_storage r8169 drm libahci hid mii video [36488.886940] CPU: 6 PID: 21882 Comm: cctest Tainted: G D C 4.13.0-17-lowlatency #20-Ubuntu [36488.886947] Hardware name: MEDION H77H2-EM/H77H2-EM, BIOS EM0411-M8 04/11/2012 [36488.886951] task: 8ebd7c18a640 task.stack: a003ce10c000 [36488.886957] RIP: 0010:kfree+0x53/0x190 [36488.886961] RSP: 0018:a003ce10fd30 EFLAGS: 00010282 [36488.886965] RAX: RBX: 6fa8 RCX: 0002 [36488.886970] RDX: 314521002bc0 RSI: 00010080 RDI: 7145 [36488.888247] RBP: a003ce10fd48 R08: 0001f640 R09: a27c7979 [36488.890131] R10: df3cd6000180 R11: 0100 R12: 8ebe84406900 [36488.892024] R13: a23aa5ee R14: R15: 8ebe8c611820 [36488.901718] FS: 7f7666764b80() GS:8ebe9ed8() knlGS: [36488.906872] CS: 0010 DS: ES: CR0: 80050033 [36488.908816] CR2: df3cd60001a0 CR3: 0002fc3c5000 CR4: 001406e0 [36488.910711] Call Trace: [36488.912512] security_sk_free+0x3e/0x50 [36488.914232] __sk_destruct+0x108/0x190 [36488.915872] sk_destruct+0x20/0x30 [36488.917483] __sk_free+0x82/0xa0 [36488.919064] sk_free+0x19/0x20 [36488.920626] tcp_close+0x230/0x3f0 [36488.922183] inet_release+0x3c/0x60 [36488.923714] inet6_release+0x30/0x40 [36488.925242] sock_release+0x1f/0x80 [36488.926785] sock_close+0x12/0x20 [36488.932837] __fput+0xe1/0x220 [36488.937778] fput+0xe/0x10 [36488.942441] task_work_run+0x76/0x90 [36488.943956] exit_to_usermode_loop+0xc4/0xd0 [36488.945467] syscall_return_slowpath+0x59/0x60 [36488.946973] entry_SYSCALL_64_fastpath+0xa7/0xa9 [36488.948468] RIP: 0033:0x7f7666376df0 [36488.949967] RSP: 002b:7ffe98391250 EFLAGS: 0293 ORIG_RAX: 0003 [36488.951522] RAX: RBX: 000c RCX: 7f7666376df0 [36488.953073] RDX: RSI: 0002 RDI: 000c [36488.954639] RBP: 000c R08: 55a301618920 R09: 000a [36488.956208] R10: 7ffe9839126c R11: 0293 R12: 0011 [36488.957774] R13: 0020 R14: 0001 R15: 7ffe983916ec [36488.959354] Code: 00 80 49 01 da 0f 82 47 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d ef 98 c1 00 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 cd 98 c1 00 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [36488.961040] RIP: kfree+0x53/0x190 RSP: a003ce10fd30 [36488.962714] CR2: df3cd60001a0 [36488.964377] ---[ end trace 46732cc399d66b31 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-lowlatency 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8 Uname: Linux
[Kernel-packages] [Bug 1720263] Re: BUG: unable to handle kernel paging request at ffffffffffffffe1
Just a comment from a security module developer. What happens if you pass security=none to kernel command line options (i.e. disable AppArmor security module), for I think it might help isolating the problem because you are hitting oops at security_vm_enough_memory_mm() and security_file_free(). Also, can you afford try compiling the kernel with KASAN enabled (i.e. CONFIG_KASAN=y), for it might be some memory corruption error (including possibility of use-after-free bug) ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720263 Title: BUG: unable to handle kernel paging request at ffe1 Status in linux package in Ubuntu: Incomplete Bug description: I'm constantly getting random kernel oopses and the machine hangs completely. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Fri Sep 29 02:51:30 2017 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: security_vm_enough_memory_mm+0x38/0x60 RSP: ad63cb35fd90 Failure: oops InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=0f587df5-406f-4a5b-b415-224eac397e66 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at ffe1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1303657] Re: Cannot boot trusty kernel on qemu-system-arm
Recent distros can silently hang due to insufficient RAM while decompressing kernel image. Did you give enough RAM? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1303657 Title: Cannot boot trusty kernel on qemu-system-arm Status in “linux” package in Ubuntu: Confirmed Bug description: Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no longer boots: === U-Boot 2013.10 (Nov 23 2013 - 04:30:10) DRAM: 1 GiB WARNING: Caches not enabled Flash: 256 MiB MMC: MMC: 0 In:serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 reading boot.scr 352 bytes read in 28 ms (11.7 KiB/s) ## Executing script at 6000 reading vmlinuz 5474584 bytes read in 958 ms (5.4 MiB/s) reading initrd.img 17883834 bytes read in 3013 ms (5.7 MiB/s) reading board.dtb 11863 bytes read in 6 ms (1.9 MiB/s) Kernel image @ 0x60008000 [ 0x00 - 0x538918 ] ## Flattened Device Tree blob at 62008000 Booting using the fdt blob at 0x62008000 Using Device Tree in place at 62008000, end 6200de56 Starting kernel ... === At this point, the host CPU just spins. The previous kernel from saucy (3.11.0-19-generic) boots correctly into the trusty environment. The VM is being launched as so: export QEMU_AUDIO_DRV=none exec qemu-system-arm -display none -M vexpress-a9 -kernel /srv/arm-dev/u-boot -m 1024 \ -serial stdio -net nic,model=lan9118,macaddr=52:54:00:68:90:14 \ -net tap,ifname=arm-dev,script=no,downscript=no -sd /dev/mapper/host-arm_dev \ -pflash /srv/arm-dev/pflash1.img -pflash /srv/arm-dev/pflash2.img -smp 1 The flash images are unused; the scr points to the SD: fatload mmc 0:1 0x60008000 vmlinuz fatload mmc 0:1 0x61008000 initrd.img fatload mmc 0:1 0x62008000 board.dtb setenv bootargs console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp setenv fdt_high 0x setenv initrd_high 0x bootz 0x60008000 0x61008000:0x100 0x62008000 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu1 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDmesg: [ 113.007517] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 7 01:23:13 2014 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyAMA0,38400 root=/dev/mmcblk0p2 nosmp RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.127 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Hello, Marco. The problem handled by this entry is about mptsas_probe() hitting scsi4: error handler thread failed to spawn, error = -12 mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem BUG: unable to handle kernel NULL pointer dereference at 0060 due to kthread_create() returning immediately upon SIGKILL. But the problem you are reporting is about mptsas_remove(). It seems to me that what you are reporting is an irrelevant one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
(a) Linux kernel guys think that a hardcoded timeout is a systemd bug. https://lkml.org/lkml/2014/3/23/42 (b) The systemd guys think that kernel module loading takes more than 30 seconds is a kernel module's bug. But Linux kernel guys won't be able to fix it immediately. Also, solution by updating firmware won't be acceptable because there will be users who can't update firmware for some reason. http://lists.freedesktop.org/archives/systemd- devel/2014-March/018007.html The systemd guys suggest that adding OPTIONS+=event_timeout=120 to udev rules might help, but I don't think it will help. https://lkml.org/lkml/2014/3/22/207 (c) The LVM guys added OPTIONS+=event_timeout=180 before commit 786235ee was merged into Linux kernel. http://www.redhat.com/archives/lvm- devel/2013-September/msg00036.html (d) I tried to rebuild systemd package with longer timeout but I was unable to build it without build failures. Therefore, I opened a bug report in order to ask for systemd package with longer timeout, but no response so far. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1297248 Well, it is unlikely that this situation is solved within 7 days. I think that applying the patch in comment #48 as a [trusty] UBUNTU: SAUCE: patch is the safest choice for 14.04 LTS kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
PierreF wrote: Applied patch on tag v3.14-rc6 (fa389e2), run kernel 4 four times, all worked. Thank you! Now we proved that systemd-udevd's 30 seconds timeout is the trigger of this problem. It would be best if we can fix systemd side. Joseph, is there any possibility that systemd-udevd's timeout is extended to e.g. 120 seconds (or rootdelay= + alpha seconds if explicitly given)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Pierre, would you give me a hand? I proposed the final patch but
I'm unable to prove that SIGKILL sent by systemd-udevd's 30 seconds
timeout is the trigger of this problem, for I don't have a real
machine which takes very long time upon initialization.
According to https://lkml.org/lkml/2014/3/18/396 , I assume that the
probe did not hang but Oleg assumes that the probe did hang and the
SIGKILL wakes up from the hung.
To test whether the probe did actually hang, I think we can ignore
the SIGKILL sent by systemd-udevd process, by applying the patch
shown below on a kernel without the final patch and booting with
rootdelay=45 . If the machine boots fine, we can assert that the
SIGKILL is not needed for waking up from the hung.
-- patch start --
diff --git a/kernel/signal.c b/kernel/signal.c
index 52f881d..49359cb 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -1051,6 +1051,7 @@ static int __send_signal(int sig, struct siginfo *info,
struct task_struct *t,
int override_rlimit;
int ret = 0, result;
+ WARN_ON(sig == SIGKILL);
assert_spin_locked(t-sighand-siglock);
result = TRACE_SIGNAL_IGNORED;
@@ -2915,6 +2916,10 @@ SYSCALL_DEFINE2(kill, pid_t, pid, int, sig)
info.si_code = SI_USER;
info.si_pid = task_tgid_vnr(current);
info.si_uid = from_kuid_munged(current_user_ns(), current_uid());
+ if (sig == SIGKILL !strcmp(current-comm, systemd-udevd)) {
+ printk(KERN_WARNING Ignored SIGKILL by systemd-udevd\n);
+ return -ESRCH;
+ }
return kill_something_info(sig, info, pid);
}
-- patch end --
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Trusty:
Confirmed
Bug description:
We have recently upgraded an Dell R300 server to Trusty (was running
fine in precise), and after upgrade it fail to boot.
It is an issue with the SAS controller during the initilisation. It
fail to detect the disk, we have the following error in console log:
[ 36.539955] scsi4: error handler thread failed to spawn, error = -12
[ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with
SCSI subsystem
After this error, initramfs drop to a shell complaining that rootfs is
not found. No disk is seen at all (cat /proc/partition only show sr0 -
cdrom drive).
We have this issue with two different server (both R300, both Dell SAS
6/iR controller and same hardware).
We don't have this issue with another Dell server (R310, Dell PERC
H200).
We also tester with old kernel (generic, 3.2.0-58.88), it is working.
Those server need a greater rootdelay (probably #579572), so we have
rootdelay=45. If we remove rootdelay=45, then disk are correctly
recognized ! (but few second too late, initramfs dropped to a shell.
Pressing control-D resume normal boot)
So the issue is that with the (mandatory) rootdelay greater that 30
(default value I think), the disk are not detected due to the error
shown above. This is a regression since those server worked in precise
(and work with precise old kernel).
System information
* Dell R300 with Dell SAS 6/iR controller
* Ubuntu Trusty Tahr (14.04)
* Running arch: x86_64
* Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25)
* Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic
root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0
console=ttyS1,57600 quiet
* uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4
10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Attached files:
* console output when error occure.
* dmesg when system boot (no rootdelay, need to press control-d during
initramfs boot)
* lspci -vnn
Tell me if you need more informations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I reproduced a similar result using test patch shown below.
-- test patch start --
diff --git a/drivers/message/fusion/mptspi.c b/drivers/message/fusion/mptspi.c
index 5653e50..eaaa5e2 100644
--- a/drivers/message/fusion/mptspi.c
+++ b/drivers/message/fusion/mptspi.c
@@ -1412,6 +1412,9 @@ mptspi_probe(struct pci_dev *pdev, const struct
pci_device_id *id)
return 0;
}
+ printk(KERN_WARNING Sleep injection start\n);
+ ssleep(40);
+ printk(KERN_WARNING Sleep injection end\n);
sh = scsi_host_alloc(mptspi_driver_template, sizeof(MPT_SCSI_HOST));
if (!sh) {
diff --git a/kernel/signal.c b/kernel/signal.c
index 52f881d..52ec166 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -1051,6 +1051,7 @@ static int __send_signal(int sig, struct siginfo *info,
struct task_struct *t,
int override_rlimit;
int ret = 0, result;
+ WARN_ON(sig == SIGKILL);
assert_spin_locked(t-sighand-siglock);
result = TRACE_SIGNAL_IGNORED;
-- test patch end --
-- dmesg start --
[2.665872] Fusion MPT base driver 3.04.20
[2.666876] Copyright (c) 1999-2008 LSI Corporation
[2.676334] Fusion MPT SPI Host driver 3.04.20
[2.679817] mptbase: ioc0: Initiating bringup
[2.692059] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[2.693733] e1000: Copyright (c) 1999-2006 Intel Corporation.
[2.761570] ioc0: LSI53C1030 B0: Capabilities={Initiator}
[2.919766] Sleep injection start
[3.062094] e1000 :02:00.0 eth0: (PCI:66MHz:32-bit) 00:0c:29:d7:20:d6
[3.064980] e1000 :02:00.0 eth0: Intel(R) PRO/1000 Network Connection
[ 35.716117] [ cut here ]
[ 35.718364] WARNING: CPU: 2 PID: 174 at kernel/signal.c:1054
__send_signal+0x476/0x4b0()
[ 35.722092] Modules linked in: e1000 mptspi(+) mptscsih mptbase floppy
[ 35.725666] CPU: 2 PID: 174 Comm: systemd-udevd Not tainted 3.14.0-rc5+ #267
[ 35.729478] Hardware name: VMware, Inc. VMware Virtual Platform/440BX
Desktop Reference Platform, BIOS 6.00 09/20/2012
[ 35.734379] 0009 8800377c5d50 816f9669
[ 35.738226] 8800377c5d88 8106970d 88007a47
0009
[ 35.742039] 8800377c5ec0 0001 0003
8800377c5d98
[ 35.745852] Call Trace:
[ 35.747083] [816f9669] dump_stack+0x45/0x56
[ 35.749482] [8106970d] warn_slowpath_common+0x7d/0xa0
[ 35.752228] [810697ea] warn_slowpath_null+0x1a/0x20
[ 35.754904] [8107ac66] __send_signal+0x476/0x4b0
[ 35.757467] [8107acde] send_signal+0x3e/0x80
[ 35.759889] [8107b753] do_send_sig_info+0x43/0x80
[ 35.762490] [8107bc16] group_send_sig_info+0x46/0x50
[ 35.764040] [8107bd24] kill_pid_info+0x34/0x50
[ 35.765244] [8107bdee] SYSC_kill+0x8e/0x1a0
[ 35.766360] [810a18db] ? account_user_time+0x8b/0xa0
[ 35.767654] [810a1ef4] ? vtime_account_user+0x54/0x60
[ 35.768946] [81022635] ? syscall_trace_enter+0x145/0x250
[ 35.770298] [8107d9be] SyS_kill+0xe/0x10
[ 35.771373] [8170aabf] tracesys+0xe1/0xe6
[ 35.772455] ---[ end trace aeaeb4f8a60584a0 ]---
[ 42.921677] Sleep injection end
[ 42.923315] scsi2: error handler thread failed to spawn, error = -12
[ 42.926270] mptspi: ioc0: WARNING - Unable to register controller with SCSI
subsystem
[ 42.929990] BUG: unable to handle kernel NULL pointer dereference at
0060
[ 42.933846] IP: [816fff62] mutex_lock+0x12/0x2f
[ 42.936484] PGD 7a453067 PUD 7a454067 PMD 0
[ 42.939242] Oops: 0002 [#1] SMP
[ 42.940874] Modules linked in: e1000 mptspi(+) mptscsih mptbase floppy
[ 42.944277] CPU: 0 PID: 181 Comm: systemd-udevd Tainted: GW
3.14.0-rc5+ #267
[ 42.947652] Hardware name: VMware, Inc. VMware Virtual Platform/440BX
Desktop Reference Platform, BIOS 6.00 09/20/2012
[ 42.952471] task: 88007a47 ti: 88007a478000 task.ti:
88007a478000
[ 42.954281] RIP: 0010:[816fff62] [816fff62]
mutex_lock+0x12/0x2f
[ 42.955924] RSP: 0018:88007a479b20 EFLAGS: 00010246
[ 42.957009] RAX: RBX: 0060 RCX: 1a42
[ 42.958398] RDX: 4090 RSI: 40924090 RDI: 0060
[ 42.959853] RBP: 88007a479b28 R08: 0082 R09: 050c
[ 42.961323] R10: 8185b080 R11: 2049534353206874 R12: 0060
[ 42.962752] R13: 88007be19000 R14: R15: 0001
[ 42.964164] FS: 7f79226bd880() GS:88007fa0()
knlGS:
[ 42.965755] CS: 0010 DS: ES: CR0: 80050033
[ 42.966899] CR2: 0060 CR3: 7a452000 CR4: 000407f0
[ 42.968333] Stack:
[ 42.969259] 88007a479b50
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Thank you. I missed that we are not allowed to call wait_for_completion() again if wait_for_completion_timeout() succeeded, for do_wait_for_common() does x-done-- which cancels x-done++ done by complete(). I must update this patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I changed this patch to call wait_for_completion() again only if wait_for_completion_timeout() returned 0, for wait_for_completion_timeout() will return non-0 if completed. ** Patch added: kthread: defer leaving kthread_create() upon SIGKILL. (v2) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026630/+files/kthread-defer-leaving%28v2%29.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Great! I updated this patch to be more OOM killer friendly. I will propose this patch for 3.14-final. ** Patch added: Final patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026689/+files/kthread-Do-not-leave-kthread_create-immediately.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
OK. I read this thread. I'm sure that somebody is sending SIGKILL to the systemd-udevd process who is doing finit_module() system call, after waiting for 30 seconds. However, since the probe function takes more than 30 seconds, the probe function already received SIGKILL by the moment scsi_host_alloc() calls kthread_run(). Therefore, reverting this commit will allow systemd-udevd process to ignore SIGKILL until leaving finit_module() system call, making kthread_run() to start successfully. I think you can find the process who is sending SIGKILL after waiting for 30 seconds, by inserting WARN_ON(). ** Patch added: (Untested) patch to warn SIGKILL https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4025040/+files/check-sigkill.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Would you try this patch? ** Patch added: kthread: defer leaving kthread_create() upon SIGKILL. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026192/+files/kthread-defer-leaving.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
That return statement is called only when wait_for_completion_killable() returned an error. That is, the caller received SIGKILL while waiting for kthreadd to create a kernel thread. That matches your bisection result because commit 786235ee changed to return to the caller when the caller received SIGKILL in order to allow the OOM killer to kill the process waiting for kthreadd to create a kernel thread. The changelog which I expected for that commit is shown below. -- [PATCH] kthread: Make kthread_create() killable. Any user process callers of wait_for_completion() except global init process might be chosen by the OOM killer while waiting for completion() call by some other process which does memory allocation. When such users are chosen by the OOM killer when they are waiting for completion() in TASK_UNINTERRUPTIBLE, the system will be kept stressed due to memory starvation because the OOM killer cannot kill such users. kthread_create() is one of such users and this patch fixes the problem for kthreadd by making kthread_create() killable. Signed-off-by: Tetsuo Handa penguin-ker...@i-love.sakura.ne.jp Cc: Oleg Nesterov o...@redhat.com Acked-by: David Rientjes rient...@google.com Signed-off-by: Andrew Morton a...@linux-foundation.org -- I think there are two problems listed below. (a) Somebody is sending SIGKILL to the caller of kthread_create(). Somebody is systemd waited for timeout? The caller is PID: 9847 Comm: systemd-udevd ? (b) Error handling of the caller of kthread_create() is wrong. mptsas_probe() calls mptsas_remove() when scsi_host_alloc() returned NULL due to receiving SIGKILL. But mptsas_remove() assumes that ioc-sh = sh; was already called with sh != NULL which means scsi_host_alloc() did not return NULL. scsi_host_alloc() can return NULL when kzalloc() returned NULL. In other words, the caller of scsi_host_alloc() must be prepared for scsi_host_alloc() returning NULL even if the caller did not receive SIGKILL while waiting for kthreadd to create a kernel thread. Therefore, I don't think reverting commit 786235ee is appropriate because the problem will again happen when kzalloc() in scsi_host_alloc() fails. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https
