[Kernel-packages] [Bug 2061040] [NEW] I2C HID device sometimes fails to initialize causing touchpad to not work
Public bug reported: Hi, Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad doesn't work on boot. I see this: | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | ... | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced collection at end of report description | [Thu Apr 11 13:57:26 2024] hid-generic: probe of 0018:2C2F:0028.0001 failed with error -22 Per the Arch Linux wiki page[1], removing and reloading the `i2c_hid_acpi` seems to fix it: | [Thu Apr 11 13:58:02 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input15 | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input16 | [Thu Apr 11 13:58:02 2024] hid-multitouch 0018:2C2F:0028.0002: input,hidraw0: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00 | [Thu Apr 11 13:58:03 2024] psmouse serio1: trackpoint: Synaptics TrackPoint firmware: 0x08, buttons: 3/3 | [Thu Apr 11 13:58:03 2024] input: TPPS/2 Synaptics TrackPoint as /devices/platform/i8042/serio1/input/input18 >From that Arch Linux wiki page, it seems to be a bug upstream[2] with the commit fixing this: | https://github.com/torvalds/linux/commit/af93a167eda90192563bce64c4bb989836afac1f Or | https://lore.kernel.org/linux- input/20240331182440.14477-1...@kl.wtf/T/#u Can we get fix this backported? | [hloeung@dharkan tmp]$ apt-cache policy linux-image-generic-hwe-24.04 | linux-image-generic-hwe-24.04: | Installed: 6.8.0-22.22 | Candidate: 6.8.0-22.22 | Version table: | *** 6.8.0-22.22 500 | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 Packages | 100 /var/lib/dpkg/status | [hloeung@dharkan tmp]$ uname -a | Linux dharkan.local 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux | [hloeung@dharkan tmp]$ Thanks, Haw [1]: https://wiki.archlinux.org/title/Lenovo_ThinkPad_Z16_Gen_2 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2271136 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Tags: noble ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Tags added: noble ** Description changed: Hi, Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad doesn't work on boot. I see this: | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack reset within 1000 ms | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item tag 0x0 | ... | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced collection at end of report description | [Thu Apr 11 13:57:26 2024] hid-generic: probe of
[Kernel-packages] [Bug 2044428] Re: fanctl should exit 0 if interface is already configured
*** This bug is a duplicate of bug 1744296 *** https://bugs.launchpad.net/bugs/1744296 ** This bug has been marked a duplicate of bug 1744296 After ifdown on underlay interface ifup fails with 'already configured' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/2044428 Title: fanctl should exit 0 if interface is already configured Status in ubuntu-fan package in Ubuntu: Invalid Bug description: Hi, This is output from a `juju run` of `ifdown ens5; ifup ens5`: | - MachineId: "4" | ReturnCode: 1 | Stderr: | | Killed old client process | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Corrupt lease file - possible data loss! | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPRELEASE on ens5 to 172.31.0.1 port 67 (xid=0x3575bf41) | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | sudo: unable to resolve host ip-172-31-8-162: Connection refused | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPDISCOVER on ens5 to 255.255.255.255 port 67 interval 3 (xid=0x811b3e7f) | DHCPREQUEST of 172.31.8.162 on ens5 to 255.255.255.255 port 67 (xid=0x7f3e1b81) | DHCPOFFER of 172.31.8.162 from 172.31.0.1 | DHCPACK of 172.31.8.162 from 172.31.0.1 | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | bound to 172.31.8.162 -- renewal in 1536 seconds. | /usr/sbin/fanctl: fan-252: already configured | run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 | Stdout: | | auto ens5 | iface ens5 inet6 dhcp | /usr/sbin/fanctl: /etc/network/fan:40 172.31.0.0/16 252.0.0.0/8 -- failed err=1 | Failed to bring up ens5. Unfortunately, it causes ifup to fail because fan interface already exists. ubuntu@ip-172-31-43-199:/etc/network$ apt-cache policy ubuntu-fan ubuntu-fan: Installed: 0.12.8~16.04.3 Candidate: 0.12.8~16.04.3 Version table: *** 0.12.8~16.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.9.0 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/2044428/+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 2044428] Re: fanctl should exit 0 if interface is already configured
It looks like this was reported in LP:1744296 and is supposed to have been fixed for Bionic. ** Changed in: ubuntu-fan (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/2044428 Title: fanctl should exit 0 if interface is already configured Status in ubuntu-fan package in Ubuntu: Invalid Bug description: Hi, This is output from a `juju run` of `ifdown ens5; ifup ens5`: | - MachineId: "4" | ReturnCode: 1 | Stderr: | | Killed old client process | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Corrupt lease file - possible data loss! | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPRELEASE on ens5 to 172.31.0.1 port 67 (xid=0x3575bf41) | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | sudo: unable to resolve host ip-172-31-8-162: Connection refused | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPDISCOVER on ens5 to 255.255.255.255 port 67 interval 3 (xid=0x811b3e7f) | DHCPREQUEST of 172.31.8.162 on ens5 to 255.255.255.255 port 67 (xid=0x7f3e1b81) | DHCPOFFER of 172.31.8.162 from 172.31.0.1 | DHCPACK of 172.31.8.162 from 172.31.0.1 | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | bound to 172.31.8.162 -- renewal in 1536 seconds. | /usr/sbin/fanctl: fan-252: already configured | run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 | Stdout: | | auto ens5 | iface ens5 inet6 dhcp | /usr/sbin/fanctl: /etc/network/fan:40 172.31.0.0/16 252.0.0.0/8 -- failed err=1 | Failed to bring up ens5. Unfortunately, it causes ifup to fail because fan interface already exists. ubuntu@ip-172-31-43-199:/etc/network$ apt-cache policy ubuntu-fan ubuntu-fan: Installed: 0.12.8~16.04.3 Candidate: 0.12.8~16.04.3 Version table: *** 0.12.8~16.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.9.0 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/2044428/+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 2044428] [NEW] fanctl should exit 0 if interface is already configured
Public bug reported: Hi, This is output from a `juju run` of `ifdown ens5; ifup ens5`: | - MachineId: "4" | ReturnCode: 1 | Stderr: | | Killed old client process | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Corrupt lease file - possible data loss! | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPRELEASE on ens5 to 172.31.0.1 port 67 (xid=0x3575bf41) | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | sudo: unable to resolve host ip-172-31-8-162: Connection refused | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPDISCOVER on ens5 to 255.255.255.255 port 67 interval 3 (xid=0x811b3e7f) | DHCPREQUEST of 172.31.8.162 on ens5 to 255.255.255.255 port 67 (xid=0x7f3e1b81) | DHCPOFFER of 172.31.8.162 from 172.31.0.1 | DHCPACK of 172.31.8.162 from 172.31.0.1 | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | bound to 172.31.8.162 -- renewal in 1536 seconds. | /usr/sbin/fanctl: fan-252: already configured | run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 | Stdout: | | auto ens5 | iface ens5 inet6 dhcp | /usr/sbin/fanctl: /etc/network/fan:40 172.31.0.0/16 252.0.0.0/8 -- failed err=1 | Failed to bring up ens5. Unfortunately, it causes ifup to fail because fan interface already exists. ubuntu@ip-172-31-43-199:/etc/network$ apt-cache policy ubuntu-fan ubuntu-fan: Installed: 0.12.8~16.04.3 Candidate: 0.12.8~16.04.3 Version table: *** 0.12.8~16.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.9.0 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/2044428 Title: fanctl should exit 0 if interface is already configured Status in ubuntu-fan package in Ubuntu: Invalid Bug description: Hi, This is output from a `juju run` of `ifdown ens5; ifup ens5`: | - MachineId: "4" | ReturnCode: 1 | Stderr: | | Killed old client process | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Corrupt lease file - possible data loss! | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPRELEASE on ens5 to 172.31.0.1 port 67 (xid=0x3575bf41) | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | sudo: unable to resolve host ip-172-31-8-162: Connection refused | Internet Systems Consortium DHCP Client 4.3.3 | Copyright 2004-2015 Internet Systems Consortium. | All rights reserved. | For info, please visit https://www.isc.org/software/dhcp/ | | Listening on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on LPF/ens5/0a:c8:aa:2d:4d:2c | Sending on Socket/fallback | DHCPDISCOVER on ens5 to 255.255.255.255 port 67 interval 3 (xid=0x811b3e7f) | DHCPREQUEST of 172.31.8.162 on ens5 to 255.255.255.255 port 67 (xid=0x7f3e1b81) | DHCPOFFER of 172.31.8.162 from 172.31.0.1 | DHCPACK of 172.31.8.162 from 172.31.0.1 | run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3 | run-parts: /etc/resolvconf/update.d/libc exited with return code 1 | bound to 172.31.8.162 -- renewal in 1536 seconds. | /usr/sbin/fanctl: fan-252: already configured | run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 | Stdout: | | auto ens5 | iface ens5 inet6 dhcp | /usr/sbin/fanctl: /etc/network/fan:40 172.31.0.0/16 252.0.0.0/8 -- failed err=1 | Failed to bring up ens5. Unfortunately, it causes ifup to fail because fan interface already exists. ubuntu@ip-172-31-43-199:/etc/network$ apt-cache policy ubuntu-fan ubuntu-fan: Installed: 0.12.8~16.04.3 Candidate:
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
It seems the latest in -proposed has fixed it for us. | [hloeung@banjo ~]$ uname -a | Linux banjo 5.4.0-123-generic #139~18.04.1-Ubuntu SMP Wed Jul 13 21:12:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | [hloeung@banjo ~]$ uptime | 01:06:47 up 44 min, 2 users, load average: 11.01, 11.21, 9.54 Where previously, it would kernel panic not too long after booting up. | [hloeung@banjo ~]$ apt-cache policy linux-image-5.4.0-123-generic | linux-image-5.4.0-123-generic: | Installed: 5.4.0-123.139~18.04.1 | Candidate: 5.4.0-123.139~18.04.1 | Version table: | *** 5.4.0-123.139~18.04.1 500 | 500 http://archive.ubuntu.com//ubuntu bionic-proposed/main amd64 Packages | 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ?
[Kernel-packages] [Bug 1981658] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603030/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr
[Kernel-packages] [Bug 1981658] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603028/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser
[Kernel-packages] [Bug 1981658] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603033/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: linux-hwe-5.4 (Ubuntu) Status: New => Confirmed ** Changed in: linux-hwe-5.4 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024]
[Kernel-packages] [Bug 1981658] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603029/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr
[Kernel-packages] [Bug 1981658] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603031/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser
[Kernel-packages] [Bug 1981658] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603032/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_cm iw_cm
[Kernel-packages] [Bug 1981658] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603027/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_cm iw_cm
[Kernel-packages] [Bug 1981658] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603025/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser
[Kernel-packages] [Bug 1981658] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1981658/+attachment/5603026/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_cm iw_cm
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
apport information ** Tags added: apport-collected bionic ** Description changed: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear mlx5_ib raid1 ses enclosure ib_uverbs ib_core mgag200 drm_vram_helper ttm drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect mlx5_core crc32_pclmul sysimgblt smartpqi fb_sys_fops uas ghash_clmulni_intel aesni_intel crypto_simd igb pci_hyperv_intf cryptd glue_helper usb_storage dca tls drm
[Kernel-packages] [Bug 1981658] [NEW] BUG: kernel NULL pointer dereference, address: 0000000000000008
Public bug reported: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear mlx5_ib raid1 ses enclosure ib_uverbs ib_core mgag200 drm_vram_helper ttm drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect mlx5_core crc32_pclmul sysimgblt smartpqi fb_sys_fops uas ghash_clmulni_intel aesni_intel crypto_simd igb pci_hyperv_intf cryptd glue_helper usb_storage dca tls drm i2c_algo_bit scsi_transport_sas mlxfw nvme i2c_piix4 nvme_core wmi | [ 351.180156] CR2: 0008 | [ 351.183629] ---[ end trace 23210cdf0c6d5851 ]--- | [ 351.322276] RIP:
[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
@mruffell, that's for Bionic, but for Focal is that still 5.4.0-56-generic? Or is there a new respun kernel to include these patches? -- 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/1898786 Title: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1898786 [Impact] Systems that utilise bcache can experience extremely high IO wait times when under constant IO pressure. The IO wait times seem to stay at a consistent 1 second, and never drop as long as the bcache shrinker is enabled. If you disable the shrinker, then IO wait drops significantly to normal levels. We did some perf analysis, and it seems we spend a huge amount of time in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". Looking at the recent commits in Bionic, we found the following commit merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through upstream stable: commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b Author: Coly Li Date: Wed Nov 13 16:03:24 2019 +0800 Subject: bcache: at least try to shrink 1 node in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b It mentions in the description that: > If sc->nr_to_scan is smaller than c->btree_pages, after the above > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring > and releasing mutex c->bucket_lock. This seems to be what is going on here, but the above commit only addresses when nr is 0. From what I can see, the problems we are experiencing are when nr is 1 or 2, and again, we just waste time in bch_mca_scan() waiting on c->bucket_lock, only to release c->bucket_lock since the shrinker loop never executes since there is no work to do. [Fix] The following commits fix the problem, and all landed in 5.6-rc1: commit 125d98edd11464c8e0ec9eaaba7d682d0f832686 Author: Coly Li Date: Fri Jan 24 01:01:40 2020 +0800 Subject: bcache: remove member accessed from struct btree Link: https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686 commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 Author: Coly Li Date: Fri Jan 24 01:01:41 2020 +0800 Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 commit e3de04469a49ee09c89e80bf821508df458ccee6 Author: Coly Li Date: Fri Jan 24 01:01:42 2020 +0800 Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6 The first commit is a dependency of the other two. The first commit removes a "recently accessed" marker, used to indicate if a particular cache has been used recently, and if it has been, not consider it for cache eviction. The commit mentions that under heavy IO, all caches will end up being recently accessed, and nothing will ever be shrunk. The second commit changes a previous design decision of skipping the first 3 caches to shrink, since it is a common case to call bch_mca_scan() with nr being 1, or 2, just like 0 was common in the very first commit I mentioned. This time, if we land on 1 or 2, the loop exits and nothing happens, and we waste time waiting on locks, just like the very first commit I mentioned. The fix is to try shrink caches from the tail of the list, and not the beginning. The third commit fixes a minor issue where we don't want to re-arrange the linked list c->btree_cache, which is what the second commit ended up doing, and instead, just shrink the cache at the end of the linked list, and not change the order. One minor backport / context adjustment was required in the first commit for Bionic, and the rest are all clean cherry picks to Bionic and Focal. [Testcase] This is kind of hard to test, since the problem shows up in production environments that are under constant IO pressure, with many different items entering and leaving the cache. The Launchpad git server is currently suffering this issue, and has been sitting at a constant IO wait of 1 second / slightly over 1 second which was causing slow response times, which was leading to build failures when git clones ended up timing out. We installed a test kernel, which is available in the following PPA: https://launchpad.net/~mruffell/+archive/ubuntu/sf294907-test Once the test
[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1900438 Title: Bcache bypasse writeback on caching device with fragmentation Status in linux package in Ubuntu: Confirmed Bug description: Hello, An upstream bug has been opened on the matter for quite some time now [0]. I can reproduce easily on our production compute node instance, which are trusty host with xenial hwe kernels (4.15.0-101-generic). However due to heavy backport and such, doing real tracing is a bit hard there. I was able to reproduce the behavior on a hwe-bionic kernel as well. Since most of our critical deployments use bcache, I think this is a kinda nasty bug to have. Reproducing the issue is relatively easy with the script provided in the bug [1]. The script used to capture the stats is this one [2]. [0]: https://bugzilla.kernel.org/show_bug.cgi?id=206767 [1]: https://pastebin.ubuntu.com/p/YnnvvSRhXK/ [2]: https://pastebin.ubuntu.com/p/XfVpzg32sN/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900438/+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 1898786] Re: Issue with bcache bch_mca_scan causing huge IO wait
** Description changed: Hello, In short, we faced an issue with a huge IO wait on a bionic Ubuntu 4.15.0-118.119-generic kernel. - This is the full list of process and the kernel function they were stuck in [2]. + This is the full list of process and the kernel function they were stuck in [0]. - The main issue can probably be summarized by this perf reports + The main issue can probably be summarized by this perf reports * first identify that the cpu are stuck in idle because of something[1] * second, see what kernel function seems to stuck the process kswapd0 and kswapd1 [2]. We could see that this seems to be the mutex_lock in the bch_mca_scan function [3]. After running the command: - | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- + | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- 583c48d0c2b8/internal/btree_shrinker_disabled" The server started to respond normally and the IO wait dropped significantly [0]: https://pastebin.canonical.com/p/wYYKwHdRXk/ [1]: https://pastebin.canonical.com/p/n2Tw57QyBC/ [2]: https://pastebin.canonical.com/p/3QqFTfdHhX/ [3]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674 $ cat /proc/version_signature Ubuntu 4.15.0-118.119-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: User Name 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Sep 29 10:04 seq - crw-rw 1 root audio 116, 33 Sep 29 10:04 timer + total 0 + crw-rw 1 root audio 116, 1 Sep 29 10:04 seq + crw-rw 1 root audio 116, 33 Sep 29 10:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Oct 6 20:36:18 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL380 G7 PciMultimedia: - + ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=c6ad1629-a506-4043-a339-6d57f0708d12 ro console=ttyS1,115200 nosplash RelatedPackageVersions: - linux-restricted-modules-4.15.0-118-generic N/A - linux-backports-modules-4.15.0-118-generic N/A - linux-firmware 1.173.18 + linux-restricted-modules-4.15.0-118-generic N/A + linux-backports-modules-4.15.0-118-generic N/A + linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-09-27 (375 days ago) dmi.bios.date: 05/05/2011 dmi.bios.vendor: HP dmi.bios.version: P67 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP67:bd05/05/2011:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL380 G7 dmi.sys.vendor: HP -- 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/1898786 Title: Issue with bcache bch_mca_scan causing huge IO wait Status in linux package in Ubuntu: Confirmed Bug description: Hello, In short, we faced an issue with a huge IO wait on a bionic Ubuntu 4.15.0-118.119-generic kernel. This is the full list of process and the kernel function they were stuck in [0]. The main issue can probably be summarized by this perf reports * first identify that the cpu are stuck in idle because of something[1] * second, see what kernel function seems to stuck the process kswapd0 and kswapd1 [2]. We could see that this seems to be the mutex_lock in the bch_mca_scan function [3]. After running the command: | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- 583c48d0c2b8/internal/btree_shrinker_disabled" The server started to respond normally and the IO wait dropped significantly [0]: https://pastebin.canonical.com/p/wYYKwHdRXk/ [1]: https://pastebin.canonical.com/p/n2Tw57QyBC/ [2]: https://pastebin.canonical.com/p/3QqFTfdHhX/ [3]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674 $ cat /proc/version_signature Ubuntu 4.15.0-118.119-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: User Name 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 AlsaDevices:
[Kernel-packages] [Bug 1863087] Re: i915 GPU HANG: ecode 9:1:0x00000000, hang on rcs0
*** This bug is a duplicate of bug 1861395 *** https://bugs.launchpad.net/bugs/1861395 ** This bug is no longer a duplicate of bug 1862865 i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 ** This bug has been marked a duplicate of bug 1861395 system hang: i915 Resetting rcs0 for hang on rcs0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863087 Title: i915 GPU HANG: ecode 9:1:0x, hang on rcs0 Status in linux-signed-5.4 package in Ubuntu: Confirmed Bug description: During normal desktop use I noticed the whole desktop freeze and it would not respond (even mouse was frozen and virtual consoles were inaccessible) - so I rebooted using Alt-SysRq-RIESUB and the following was in the logs: Feb 13 16:15:19 slate kernel: i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0 Feb 13 16:15:19 slate kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Feb 13 16:15:19 slate kernel: Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Feb 13 16:15:19 slate kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue. Feb 13 16:15:19 slate kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it. Feb 13 16:15:19 slate kernel: GPU crash dump saved to /sys/class/drm/card0/error Feb 13 16:15:19 slate kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Feb 13 16:15:19 slate kernel: i915 :00:02.0: Resetting chip for hang on rcs0 Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): EDID vendor "DEL", prod id 53409 Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Using hsync ranges from config file Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Using vrefresh ranges from config file Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Printing DDC gathered Modelines: Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1920x1080"x0.0 174.50 1920 1968 2000 2080 1080 1083 1088 1119 +hsync -vsync (83.9 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
5.4.0-18.22 looks good too, been up for 2 days, 10:52. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed -- 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/1861395 Title: system hang: i915 Resetting rcs0 for hang on rcs0 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Invalid Status in linux source package in Focal: Confirmed Bug description: System hangs, unknown cause, When this happens, the mouse pointer still moves, but I can't do anything else with the keys or clicking in the UI. Only recover I have found is a hard power-off Last bit of kern.log below: Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required to analyze GPU hangs, so please always attach it. Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to /sys/class/drm/card0/error Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting chip for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks suppressed Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000] Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 7d 8f 00 Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting rcs0 for hang on rcs0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 12:51:24 2020 InstallationDate: Installed on 2018-06-18 (591 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb 115653 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-06-18 (604 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics
[Kernel-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
*** This bug is a duplicate of bug 1861395 *** https://bugs.launchpad.net/bugs/1861395 Duplicate of LP:1861395 Per LP:1861395 both 5.4.0-17 (from the Kernel Team's Unstable PPA) and 5.4.0-18 (from -proposed) seems to fixes it for me. ** This bug has been marked a duplicate of bug 1861395 system hang: i915 Resetting rcs0 for hang on rcs0 -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Will try 5.4.0-18.22 in -proposed this weekend. -- 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/1861395 Title: system hang: i915 Resetting rcs0 for hang on rcs0 Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Invalid Status in linux source package in Focal: Incomplete Bug description: System hangs, unknown cause, When this happens, the mouse pointer still moves, but I can't do anything else with the keys or clicking in the UI. Only recover I have found is a hard power-off Last bit of kern.log below: Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required to analyze GPU hangs, so please always attach it. Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to /sys/class/drm/card0/error Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting chip for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks suppressed Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000] Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 7d 8f 00 Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting rcs0 for hang on rcs0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 12:51:24 2020 InstallationDate: Installed on 2018-06-18 (591 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb 115653 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-06-18 (604 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Been running 5.4.0-17.21, also from the canonical-kernel-team/unstable PPA, for 5 days now and have yet to see any i915 resets or hangs. -- 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/1861395 Title: system hang: i915 Resetting rcs0 for hang on rcs0 Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Invalid Status in linux source package in Focal: Incomplete Bug description: System hangs, unknown cause, When this happens, the mouse pointer still moves, but I can't do anything else with the keys or clicking in the UI. Only recover I have found is a hard power-off Last bit of kern.log below: Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required to analyze GPU hangs, so please always attach it. Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to /sys/class/drm/card0/error Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting chip for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks suppressed Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000] Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 7d 8f 00 Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting rcs0 for hang on rcs0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 12:51:24 2020 InstallationDate: Installed on 2018-06-18 (591 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb 115653 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-06-18 (604 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp.
[Kernel-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
Also, I even tried disabling the power saving feature (i915.enable_psr=0) but it still seems to lock up or hang. -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:15 dharkan
[Kernel-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0 | [Fri Feb 14 18:55:37 2020] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. | [Fri Feb 14 18:55:37 2020] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel | [Fri Feb 14 18:55:37 2020] drm/i915 developers can then reassign to the right component if it's not a kernel issue. | [Fri Feb 14 18:55:37 2020] The GPU crash dump is required to analyze GPU hangs, so please always attach it. | [Fri Feb 14 18:55:37 2020] GPU crash dump saved to /sys/class/drm/card0/error | [Fri Feb 14 18:55:37 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | [Fri Feb 14 18:55:45 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0 So included saved crash dump from /sys/class/drm/card0/error. ** Attachment added: "/sys/class/drm/card0/error" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1862865/+attachment/5328143/+files/drm-error.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584]
[Kernel-packages] [Bug 1862865] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328141/+files/UdevDb.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 |
[Kernel-packages] [Bug 1862865] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328138/+files/ProcInterrupts.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for
[Kernel-packages] [Bug 1862865] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328142/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu Focal) Status: Incomplete => New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915
[Kernel-packages] [Bug 1862865] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328140/+files/PulseList.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0
[Kernel-packages] [Bug 1862865] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328139/+files/ProcModules.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on
[Kernel-packages] [Bug 1862865] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328137/+files/ProcEnviron.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on
[Kernel-packages] [Bug 1862865] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328136/+files/ProcCpuinfoMinimal.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Kernel-packages] [Bug 1862865] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328134/+files/PciMultimedia.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang
[Kernel-packages] [Bug 1862865] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328135/+files/ProcCpuinfo.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on
[Kernel-packages] [Bug 1862865] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328130/+files/CurrentDmesg.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang
[Kernel-packages] [Bug 1862865] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328131/+files/IwConfig.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0
[Kernel-packages] [Bug 1862865] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328133/+files/Lsusb-v.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 |
[Kernel-packages] [Bug 1862865] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328132/+files/Lspci.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb
[Kernel-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
apport information ** Tags added: apport-collected focal ** Description changed: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:17 dharkan kernel: [71072.575930] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:19 dharkan kernel: [71074.591922] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:21 dharkan kernel: [71076.575911] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:23 dharkan kernel: [71078.591901] i915 :00:02.0: Resetting
[Kernel-packages] [Bug 1862865] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328127/+files/CRDA.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2
[Kernel-packages] [Bug 1862865] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328128/+files/Card0.Codecs.codec.0.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Kernel-packages] [Bug 1862865] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1862865/+attachment/5328129/+files/Card0.Codecs.codec.2.txt -- 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/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Kernel-packages] [Bug 1793753] Re: kernel panic - null pointer dereference on ipset operations
Maybe it's fixed in this commit which landed in Linux 4.6-rc2: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=596cf3fe5854fe2b1703b0466ed6bf9cfb83c91e -- 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/1793753 Title: kernel panic - null pointer dereference on ipset operations Status in linux package in Ubuntu: Confirmed Bug description: Hi, We've experienced crashes on machines running iptables using ipsets. We could get a trace from the console on one of them (attached file kernel-trace.txt). On these machines, some ipset commands are automatically run to update the sets, and/or to dump them (ipset restore, swap, delete ... / ipset save). We strongly suspect the panic is happening due to a race when ipset updates happen at the same time as a dump. These machines are running xenial. Before the crash, they were on 4.4.0-116-generic #140-Ubuntu, but then rebooted into 4.4.0-135-generic #161-Ubuntu. I have an ipset save running in loops on one of these machines to try and reproduce quicker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793753/+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 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
NOTE: That these are systems using the pcc-cpufreq and acpi-cpufreq drivers. -- 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/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00%
[Kernel-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
@dsmythies, sorry, missed your question. We're actually seeing performance issues/load on a couple of our Ubuntu Archive servers (archive.ubuntu.com). They're high traffic servers with 10GbE NICs with just apache2 serving .deb packages from disk. We've recently upgraded a few to 4.11.0-14-generic from linux-image-generic-hwe-16.04-edge (for TCP BBR). ** Attachment added: "cpu usage 2017-08-23 02-11-45" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/+attachment/4969405/+files/cpu%20usage%202017-08-23%2002-11-45.png -- 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/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect |
[Kernel-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
** Attachment added: "load 15m 2017-08-23 02-10-53" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/+attachment/4969406/+files/load%2015m%202017-08-23%2002-10-53.png -- 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/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00%
[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers
Sounds like it might be LP:1709536 -- 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/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Status in lxd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+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 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory
Looking good so far with 4.4.0-63-generic. -- 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/1662378 Title: many OOMs on busy xenial IMAP server with lots of available memory Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: We recently noticed that a busy xenial IMAP server with about 22 days uptime has been logging a lot of OOM messages. The machine has 24G of memory. Below please find some typical memory info. I noted that there was about 11G of memory allocated to slab, and since all of the oom-killer invoked messages report order=2 or order=3 (see below for gfp_flags) I thought that maybe fragmentation was a factor. After doing echo 2 > /proc/sys/vm/drop_caches to release reclaimable slab memory, no OOMs were logged for around 30 minutes, but then they started up again, although perhaps not as frequently as before, and the amount of memory in slab was back up around its former size. To the best of my knowledge we do not have any custom VM- related sysctl tweaks on this machine. Attached please find version.log and lspci-vnvn.log. And here's a link to a kern.log from a little before time of boot onwards, containing all of the oom-killer messages: https://people.canonical.com/~pjdc/grenadilla-sanitized-kern.log.xz == Breakdown of Failed Allocations === pjdc@grenadilla:~$ grep -o 'gfp_mask=.*, order=.' kern.log-version-with-oom-killer-invoked | sort | uniq -c | sort -n 1990 gfp_mask=0x26000c0, order=2 4043 gfp_mask=0x240c0c0, order=3 pjdc@grenadilla:~$ _ == Representative (Probably) Memory Info == pjdc@grenadilla:~$ free -m totalusedfree shared buff/cache available Mem: 240971762 213 266 22121 21087 Swap: 17492 101 17391 pjdc@grenadilla:~$ cat /proc/meminfo MemTotal: 24676320 kB MemFree: 219440 kB MemAvailable: 21593416 kB Buffers: 6186648 kB Cached: 4255608 kB SwapCached: 3732 kB Active: 7593140 kB Inactive:4404824 kB Active(anon):1319736 kB Inactive(anon): 508544 kB Active(file):6273404 kB Inactive(file): 3896280 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 17912436 kB SwapFree: 17808972 kB Dirty: 524 kB Writeback: 0 kB AnonPages: 1553244 kB Mapped: 219868 kB Shmem:272576 kB Slab: 12209796 kB SReclaimable: 11572836 kB SUnreclaim: 636960 kB KernelStack: 14464 kB PageTables:54864 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:30250596 kB Committed_AS:2640808 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 18432 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB DirectMap4k: 2371708 kB DirectMap2M:22784000 kB pjdc@grenadilla:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+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 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
pitti, can we please have a config option to disable "ondemand"? As originally reported, one some workloads, it seems setting to powersave/ondemand causes high load with CPUs checking to see if they need to enter powersave state. While the original report included perf report for the acpi-cpufreq driver, it was also seen with intel_pstate (and was why we decided to try switch to acpi-cpufreq). -- 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/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01%
[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage
OOI, does this fix this? | for i in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do sudo sh -c "echo performance > $i"; done If so, was the scaling governor set to "ondemand" by any chance? -- 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/1518457 Title: kswapd0 100% CPU usage Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 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: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+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 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server)
Bug #1188647 enables Intel PSTATE by default. -- 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server) Status in linux package in Ubuntu: Invalid Status in sysvinit package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in sysvinit source package in Xenial: New Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00% __tick_nohz_idle_enter | 0.00% irq_entries_start | 0.00% sched_clock_idle_wakeup_event | 0.00%
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server)
In that same Google+ post, Arjan van de Ven wrote: """ Now, about ondemand and cpufreq. The ondemand algorithm was designed roughly 10 years ago, for CPUs from that era. If you look at what ondemand really ends up doing, is managing the frequency during idle periods, and 10 years ago, that mattered for power. Today (well, last 5 years), the frequency in idle is zero, and even the voltage is now zero (NHM and later) so what frequency the OS picks during the idle period is completely irrelevant. This, and other things, make ondemand not a good algorithm for current Intel processors. ... The new code in the 3.9 kernel, under, CONFIG_X86_INTEL_PSTATE, is a fresh approach to all of this. """ -- 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server) Status in linux package in Ubuntu: Invalid Status in sysvinit package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in sysvinit source package in Xenial: New Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02%
[Kernel-packages] [Bug 1584124] Re: revisit /etc/init.d/ondemand
Bug #1579278 to consider switching to "performamce" may be of relevance here. -- 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/1584124 Title: revisit /etc/init.d/ondemand Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: We've been carrying /etc/init.d/ondemand for many years. We should revisit if booting with a kernel that defaults to "ondemand" right away is still actually slower than "performance". In the short term, systemd should grow a "Type=idle" unit that switches to ondemand, to replace the static "1 minute" sleep. This will also get rid of the last init.d script in "initscripts" that we actually use, and pave the way for dropping the initscripts package. In the long term, we could drop it completely if "ondemand" DTRT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584124/+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 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server)
Ah thanks. So maybe /etc/init.d/ondemand should have something to override or disable it (say DISABLE=1 in /etc/default/ondemand)? Looking at it currently, it seems to prefer governors in this order - interactive, ondemand, powersave. Even an option in /etc/default/ondemand to specify the preferred would be nice (e.g. PREFERRED_GOVERNOR=performance). ** Also affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server) Status in linux package in Ubuntu: Invalid Status in sysvinit package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in sysvinit source package in Xenial: New Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01%
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server)
** Summary changed: - Consider changing default CPU frequency scaling governor back to "performance" + Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server) -- 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00% __tick_nohz_idle_enter | 0.00% irq_entries_start | 0.00%
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed -- 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00% __tick_nohz_idle_enter | 0.00% irq_entries_start | 0.00% sched_clock_idle_wakeup_event | 0.00% reschedule_interrupt
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
| - 26.02% 0.08% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 25.94% cpu_startup_entry | - 23.65% call_cpuidle | - 23.63% cpuidle_enter | - 17.31% cpuidle_enter_state | 17.04% intel_idle | 0.04% poll_idle |+ 0.03% ktime_get | 0.02% leave_mm |+ 0.02% ret_from_intr |+ 0.00% apic_timer_interrupt | 0.00% sched_idle_set_state | 0.00% read_tsc | + 4.41% ret_from_intr | + 1.79% apic_timer_interrupt | 0.04% native_irq_return_iret | 0.02% ktime_get | 0.01% irq_entries_start | + 0.01% reschedule_interrupt | 0.01% common_interrupt | 0.01% intel_idle | 0.00% sched_idle_set_state | 0.00% do_IRQ | 0.00% restore_regs_and_iret | 0.00% native_iret | 0.00% restore_c_regs_and_iret | + 0.00% call_function_single_interrupt | + 0.00% call_function_interrupt | + 0.00% ret_from_intr |0.00% cpuidle_enter_state -- 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | +
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
As Theodore Ts'o has pointed out[1]: """ ... with modern Intel processors, the ondemand CPU governor is actually counterproductive because waking up to decide whether the CPU is idle keeps it from entering the deepest sleep states, and so (somewhat counterintuitively) the performance governor will actually result in the best battery life. """ [1]https://plus.google.com/+TheodoreTso/posts/2vEekAsG2QT ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit
[Kernel-packages] [Bug 1579278] [NEW] Consider changing default CPU frequency scaling governor back to "performance"
Public bug reported: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00% __tick_nohz_idle_enter | 0.00% irq_entries_start | 0.00% sched_clock_idle_wakeup_event | 0.00% reschedule_interrupt | + 0.00% apic_timer_interrupt |+ 0.20% start_secondary |+ 0.00% x86_64_start_kernel | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | - 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter |- 52.92% cpuidle_enter | + 31.81% cpuidle_enter_state | + 20.01% ret_from_intr | + 0.51% apic_timer_interrupt | 0.28% native_irq_return_iret | + 0.09% reschedule_interrupt | 0.05% irq_entries_start | 0.05% do_IRQ | 0.05%
[Kernel-packages] [Bug 1532523] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547309/+files/PciMultimedia.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547311/+files/ProcEnviron.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547312/+files/ProcInterrupts.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547317/+files/WifiSyslog.txt ** Summary changed: - Error parsing PCC subspaces from PCCT on ThinkPad-X1-Carbon-Type-20A7-20A8 + Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7, 20A8) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7, 20A8) + Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547310/+files/ProcCpuinfo.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] [NEW] Error parsing PCC subspaces from PCCT on ThinkPad-X1-Carbon-Type-20A7-20A8
Public bug reported: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and-netbooks/ThinkPad-X -Series-laptops/ThinkPad-X1-Carbon-Type-20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad-X1-Carbon-Type- 20A7-20A8 Status in linux package in Ubuntu: Incomplete Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] Card1.Codecs.codec.0.txt
apport information ** Attachment added: "Card1.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547304/+files/Card1.Codecs.codec.0.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547305/+files/CurrentDmesg.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547302/+files/CRDA.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547307/+files/JournalErrors.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] Re: Error parsing PCC subspaces from PCCT on ThinkPad-X1-Carbon-Type-20A7-20A8
apport information ** Tags added: apport-collected xenial ** Description changed: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and-netbooks/ThinkPad-X -Series-laptops/ThinkPad-X1-Carbon-Type-20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.19.3-0ubuntu2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: hloeung1241 F pulseaudio + /dev/snd/controlC1: hloeung1241 F pulseaudio + Card0.Amixer.info: Error: [Errno 2] No such file or directory + Card0.Amixer.values: Error: [Errno 2] No such file or directory + Card1.Amixer.info: Error: [Errno 2] No such file or directory + Card1.Amixer.values: Error: [Errno 2] No such file or directory + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2014-04-24 (625 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: LENOVO 20A7CT01WW + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 + ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 + RelatedPackageVersions: + linux-restricted-modules-4.3.0-5-generic N/A + linux-backports-modules-4.3.0-5-generic N/A + linux-firmware 1.155 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.3.0-5-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users + _MarkForUpload: True + dmi.bios.date: 11/04/2015 + dmi.bios.vendor: LENOVO + dmi.bios.version: GRET46WW (1.23 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20A7CT01WW + dmi.board.vendor: LENOVO + dmi.board.version: 0B98420 STD + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 20A7CT01WW + dmi.product.version: ThinkPad X1 Carbon 2nd + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547301/+files/AlsaDevices.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1532523] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547308/+files/Lspci.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547315/+files/UdevDb.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547313/+files/ProcModules.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547316/+files/UdevLog.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547314/+files/PulseList.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547303/+files/Card0.Codecs.codec.0.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1532523/+attachment/4547306/+files/IwConfig.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1532523] Re: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7)
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+attachment/4547317/+files/WifiSyslog.txt -- 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/1532523 Title: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7) Status in linux package in Ubuntu: Confirmed Bug description: May be the same issue or duplicate as LP:1528684. I've just updated the BIOS to the latest (1.23) as per http://support.lenovo.com/au/en/products/Laptops-and- netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type- 20A7-20A8/downloads/DS039783 and am still seeing this error: | [hloeung@ragnar tmp]$ dmesg | grep -i error | [0.157751] Error parsing PCC subspaces from PCCT Both bootup info and dmidecode output shows latest: | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date | GRET46WW (1.23 ) | 11/04/2015 Running Xenial Alpha 1: | [hloeung@ragnar tmp]$ cat /etc/*release | DISTRIB_ID=Ubuntu | DISTRIB_RELEASE=16.04 | DISTRIB_CODENAME=xenial | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" | [hloeung@ragnar tmp]$ uname -a | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.3.0-5-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hloeung1241 F pulseaudio /dev/snd/controlC1: hloeung1241 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-04-24 (625 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: LENOVO 20A7CT01WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.3.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GRET46WW (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98420 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CT01WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
Disabling KSM doesn't seem to have helped. Ryan's (http://launchpad.net/~fo0bar) been working on getting hwe-w installed on these compute nodes to see if a more recent kernel will help. -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: Confirmed Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct
[Kernel-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
7 day log rotate: | hloeung@floette:~$ zgrep -h SEGV /var/log/syslog* | Oct 28 14:46:34 floette kernel: [1351174.845829] init: rsyslog main process (2652) killed by SEGV signal | hloeung@bagon:~$ zgrep -h SEGV /var/log/syslog* | Nov 2 22:17:03 bagon kernel: [2401829.665556] init: neutron-plugin-openvswitch-agent main process (124418) killed by SEGV signal | Nov 3 00:20:46 bagon kernel: [2409252.286349] init: nova-compute main process (125673) killed by SEGV signal | Oct 26 11:51:25 bagon kernel: [1759496.565022] init: nova-compute main process (94922) killed by SEGV signal | Oct 26 11:56:08 bagon kernel: [1759778.693294] init: neutron-plugin-openvswitch-agent main process (18574) killed by SEGV signal | Oct 26 11:56:23 bagon kernel: [1759794.417232] init: neutron-plugin-openvswitch-agent main process (95171) killed by SEGV signal | hloeung@gligar:~$ zgrep -h SEGV /var/log/syslog* | Oct 30 18:32:56 gligar kernel: [745109.275184] init: neutron-plugin-openvswitch-agent main process (4705) killed by SEGV signal | Oct 30 18:32:56 gligar kernel: [745109.776233] init: neutron-plugin-openvswitch-agent main process (88517) killed by SEGV signal | Oct 30 18:32:57 gligar kernel: [745110.335622] init: neutron-plugin-openvswitch-agent main process (88527) killed by SEGV signal | hloeung@patrat:~$ zgrep -h SEGV /var/log/syslog* | Oct 27 08:18:29 patrat kernel: [508926.329315] init: neutron-plugin-openvswitch-agent main process (51113) killed by SEGV signal I've disabled KSM as suggested. I'll try get wgrant or cjwatson to trigger a full rebuild and get some load on these compute nodes. -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr
[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Kernel OOPS on one of the mcdivitts: | [544599.231964] block nbd0: Attempted send on closed socket | [544599.231968] block nbd0: Attempted send on closed socket | [544599.231972] block nbd0: Attempted send on closed socket | [544599.231975] block nbd0: Attempted send on closed socket | [544627.046717] INFO: rcu_sched self-detected stall on CPU { 3} (t=15040176 jiffies g=8751031 c=8751030 q=246988591) | [544627.046719] Task dump for CPU 3: | [544627.046723] qemu-nbdR running task0 32375 1 0x000a | [544627.046724] Call trace: | [544627.046733] [] dump_backtrace+0x0/0x170 | [544627.046737] [] show_stack+0x20/0x2c | [544627.046740] [] sched_show_task+0xa0/0xf8 | [544627.046742] [] dump_cpu_task+0x44/0x54 | [544627.046745] [] rcu_dump_cpu_stacks+0x98/0xec | [544627.046747] [] rcu_check_callbacks+0x410/0x740 | [544627.046751] [] update_process_times+0x40/0x74 | [544627.046754] [] tick_sched_handle.isra.15+0x38/0x7c | [544627.046756] [] tick_sched_timer+0x48/0x84 | [544627.046758] [] __run_hrtimer+0x90/0x1d0 | [544627.046760] [] hrtimer_interrupt+0xec/0x28c | [544627.046764] [] arch_timer_handler_phys+0x38/0x48 | [544627.046766] [] handle_percpu_devid_irq+0x90/0x12c | [544627.046769] [] generic_handle_irq+0x38/0x54 | [544627.046770] [] __handle_domain_irq+0x64/0xc0 | [544627.046772] [] gic_handle_irq+0x38/0x88 | [544627.046773] Exception stack(0xffc634947610 to 0xffc634947730) | [544627.046776] 7600: 00c1a000 ffc0 00c1f000 ffc0 | [544627.046778] 7620: 34947750 ffc6 000ffe0c ffc0 0900 01c0 | [544627.046780] 7640: 0005 004a1870 ffc0 004a1870 ffc0 004a433c ffc0 | [544627.046782] 7660: 00ff 00b5c658 ffc0 6465736f 636f7320 00ba157e | [544627.046784] 7680: 00ba1449 0006 20666366 | [544627.046786] 76a0: 34393433 30353737 ec9de100 0038d0cb 0023ceec ffc0 004bc7f8 | [544627.046788] 76c0: aff5f5d0 007f 00c1a000 ffc0 00c1f000 ffc0 0140 | [544627.046790] 76e0: 00c1adc0 ffc0 00b7c198 ffc0 0001 00c1f1c0 ffc0 | [544627.046792] 7700: 0003 fff47938 ffcf 34947750 ffc6 | [544627.046793] 7720: 000ffe08 ffc0 34947750 ffc6 | [544627.046795] [] el1_irq+0x64/0xc0 | [544627.046798] [] vprintk_emit+0x33c/0x59c | [544627.046801] [] dev_vprintk_emit+0xc8/0x204 | [544627.046802] [] dev_printk_emit+0x74/0x84 | [544627.046804] [] __dev_printk+0x54/0x9c | [544627.046805] [] dev_err+0x70/0x80 | [544627.046814] [] __nbd_ioctl+0x810/0x944 [nbd] | [544627.046817] [] nbd_ioctl+0x7c/0x228 [nbd] | [544627.046821] [] blkdev_ioctl+0x1f4/0x770 | [544627.046825] [] block_ioctl+0x50/0x64 | [544627.046829] [] do_vfs_ioctl+0x330/0x5d4 | [544627.046831] [] SyS_ioctl+0x8c/0xa4 -- 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/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) Status in linux package in Ubuntu: Incomplete Status in linux-meta-lts-vivid package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: Hi, We're seeing this often on our HP Moonshot ARM64 nova-compute nodes where qemu-nbd processes would lock up. At the same time, there's also a bunch of kernel spew as follows: | [605282.018238] block nbd3: Attempted send on closed socket | [605282.018242] block nbd3: Attempted send on closed socket | [605282.018245] block nbd3: Attempted send on closed socket | [605282.018249] block nbd3: Attempted send on closed socket swirlix01: | hloeung@swirlix01:~$ uname -a | Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux | hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd | 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10 /var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk | hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print $1 }')/stack | [] __switch_to+0x74/0x8c | [] futex_wait_queue_me+0xf4/0x184 | [] futex_wait+0x154/0x24c | [] do_futex+0x1a0/0x9ec | [] SyS_futex+0x98/0x1cc | [] el0_svc_naked+0x20/0x28 | [] 0x swirlix08: | hloeung@swirlix08:~$ uname -a | Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux | hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd | 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6 /var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk | hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print $1 }')/stack | [] __switch_to+0x74/0x8c | [] futex_wait_queue_me+0xf4/0x184 | []
[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
apport information ** Also affects: linux-meta-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected trusty uec-images ** Description changed: Hi, We're seeing this often on our HP Moonshot ARM64 nova-compute nodes where qemu-nbd processes would lock up. At the same time, there's also a bunch of kernel spew as follows: | [605282.018238] block nbd3: Attempted send on closed socket | [605282.018242] block nbd3: Attempted send on closed socket | [605282.018245] block nbd3: Attempted send on closed socket | [605282.018249] block nbd3: Attempted send on closed socket swirlix01: | hloeung@swirlix01:~$ uname -a | Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux | hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd | 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10 /var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk | hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print $1 }')/stack | [] __switch_to+0x74/0x8c | [] futex_wait_queue_me+0xf4/0x184 | [] futex_wait+0x154/0x24c | [] do_futex+0x1a0/0x9ec | [] SyS_futex+0x98/0x1cc | [] el0_svc_naked+0x20/0x28 | [] 0x swirlix08: | hloeung@swirlix08:~$ uname -a | Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux | hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd | 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6 /var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk | hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print $1 }')/stack | [] __switch_to+0x74/0x8c | [] futex_wait_queue_me+0xf4/0x184 | [] futex_wait+0x154/0x24c | [] do_futex+0x1a0/0x9ec | [] SyS_futex+0x98/0x1cc | [] el0_svc_naked+0x20/0x28 | [] 0x swirlix11: | hloeung@swirlix11:~$ uname -a | Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux | hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd | 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3 /var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk | hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print $1 }'/stack | hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print $1 }')/stack | [] __switch_to+0x74/0x8c | [] futex_wait_queue_me+0xf4/0x184 | [] futex_wait+0x154/0x24c | [] do_futex+0x1a0/0x9ec | [] SyS_futex+0x98/0x1cc | [] el0_svc_naked+0x20/0x28 | [] 0x | hloeung@swirlix11:~$ sudo strace -f -p 18149 | Process 18149 attached with 3 threads | [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8 | [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL | ... (hangs here) ... We're using the QEMU package backported from Vivid as per LP:1457639 | hloeung@swirlix11:~$ apt-cache policy qemu-utils | qemu-utils: | Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 | Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 | Version table: | *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0 | 500 http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/ trusty/main arm64 Packages - I'm also not sure if this is related to LP:1505564, which is for - amd64/x86_64. + I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 25 17:42 seq + crw-rw 1 root audio 116, 33 Oct 25 17:42 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.18 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 + Package: qemu (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: console=ttyS0,9600n8r ro + ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty uec-images trusty uec-images + Uname: Linux 3.19.0-31-generic aarch64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm + _MarkForUpload: True ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510810/+files/BootDmesg.txt -- You
[Kernel-packages] [Bug 1508767] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510844/+files/UdevDb.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510839/+files/ProcInterrupts.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11
[Kernel-packages] [Bug 1508767] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510838/+files/ProcCpuinfo.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] ProcLocks.txt
apport information ** Attachment added: "ProcLocks.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510840/+files/ProcLocks.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510837/+files/Lspci.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510836/+files/IwConfig.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] ProcMisc.txt
apport information ** Attachment added: "ProcMisc.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510841/+files/ProcMisc.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] nvram.gz
apport information ** Attachment added: "nvram.gz" https://bugs.launchpad.net/bugs/1508767/+attachment/4510847/+files/nvram.gz -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8
[Kernel-packages] [Bug 1508767] ProcPpc64.tar.gz
apport information ** Attachment added: "ProcPpc64.tar.gz" https://bugs.launchpad.net/bugs/1508767/+attachment/4510843/+files/ProcPpc64.tar.gz -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] DeviceTree.tar.gz
apport information ** Attachment added: "DeviceTree.tar.gz" https://bugs.launchpad.net/bugs/1508767/+attachment/4510835/+files/DeviceTree.tar.gz -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11
[Kernel-packages] [Bug 1508767] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510834/+files/CurrentDmesg.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510833/+files/CRDA.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8
[Kernel-packages] [Bug 1508767] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510842/+files/ProcModules.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510845/+files/UdevLog.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510846/+files/WifiSyslog.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
apport information ** Tags added: apport-collected ** Description changed: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8 nip 101abf40 lr 100d9cac code 30001 | Oct 14 22:21:46 floette kernel: [168902.724121] neutron-openvsw[153852]: unhandled signal 11 at 882b78783fa8 nip 100b5c8c lr 1014c734 code 30001 | hloeung@patrat:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 15 00:48:13 patrat kernel: [553143.677075] rsync[89656]: unhandled signal 11 at 3fffe6a5
[Kernel-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
** Also affects: linux-meta-lts-vivid (Ubuntu) Importance: Undecided Status: New -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8 nip 101abf40 lr