[Kernel-packages] [Bug 1305389] [NEW] kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365!
Public bug reported: I was running e4defrag -v /dev/sda1. Also had Firefox open with a few tabs, but hadn't used it within the past 10 mins. System locked solid, I gave it a couple minutes to see if it would clear itself, it did not. Tried REISUB, did nothing. Had to hold power to turn off and reboot. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1937 F pulseaudio Date: Wed Apr 9 22:50:44 2014 Failure: oops HibernationDevice: RESUME=UUID=3b8f071b-7eb6-45cb-a517-913fb9a52ee2 InstallationDate: Installed on 2014-04-05 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Hewlett-Packard HP ProBook 6540b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=3cc87284-3cfc-45bc-9ea5-d432e52b023d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux StagingDrivers: zram Title: kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! UpgradeStatus: Upgraded to trusty on 2014-04-05 (4 days ago) dmi.bios.date: 03/28/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDD Ver. F.21 dmi.board.name: 1722 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 29.37 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDDVer.F.21:bd03/28/2012:svnHewlett-Packard:pnHPProBook6540b:pvr:rvnHewlett-Packard:rn1722:rvrKBCVersion29.37:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6540b dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-kerneloops i386 kernel-oops staging trusty -- 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/1305389 Title: kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! Status in “linux” package in Ubuntu: Confirmed Bug description: I was running e4defrag -v /dev/sda1. Also had Firefox open with a few tabs, but hadn't used it within the past 10 mins. System locked solid, I gave it a couple minutes to see if it would clear itself, it did not. Tried REISUB, did nothing. Had to hold power to turn off and reboot. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1937 F pulseaudio Date: Wed Apr 9 22:50:44 2014 Failure: oops HibernationDevice: RESUME=UUID=3b8f071b-7eb6-45cb-a517-913fb9a52ee2 InstallationDate: Installed on 2014-04-05 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Hewlett-Packard HP ProBook 6540b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=3cc87284-3cfc-45bc-9ea5-d432e52b023d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux StagingDrivers: zram Title: kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! UpgradeStatus: Upgraded to trusty on 2014-04-05 (4 days ago) dmi.bios.date: 03/28/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDD Ver. F.21 dmi.board.name: 1722 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 29.37 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDDVer.F.21:bd03/28/2012:svnHewlett-Packard:pnHPProBook6540b:pvr:rvnHewlett-Packard:rn1722:rvrKBCVersion29.37:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6540b dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305389/+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 1742867] Re: Screen blank, audio choppy, system locked
xorg was chosen by the bug utility, I did not select xorg. Problem appears to be with latest kernel, did not happen prior. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/1742867 Title: Screen blank, audio choppy, system locked Status in linux package in Ubuntu: Confirmed Bug description: While watching a YouTube video, screen went blank. Audio cut out, after a few seconds the audio started playing normally for a few more seconds then kept repeating the last half a second of audio for a few more seconds. Then it stopped and nothing responded. It did this a few times over the course of an hour. Had to power off the PC to get a reboot. Last time it did this I ssh'd from another PC to get dmesg and syslog info as it happened. Attaching those captures. clickwir@mach:~$ uname -a Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux clickwir@mach:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful dmesg [ 10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up link [ 10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [ 10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000 [ 10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000 [ 10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 10.730200] r8169 :02:00.0 eth0: link down [ 10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 16.875586] FS-Cache: Loaded [ 16.896010] FS-Cache: Netfs 'nfs' registered for caching [ 16.914353] NFS: Registering the id_resolver key type [ 16.914364] Key type id_resolver registered [ 16.914364] Key type id_legacy registered [ 17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 17.513074] Ebtables v2.0 registered [ 17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 17.863232] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 17.864899] virbr0: port 1(virbr0-nic) entered blocking state [ 17.864903] virbr0: port 1(virbr0-nic) entered disabled state [ 17.864995] device virbr0-nic entered promiscuous mode [ 17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ 18.038385] virbr0: port 1(virbr0-nic) entered blocking state [ 18.038388] virbr0: port 1(virbr0-nic) entered listening state [ 18.095412] virbr0: port 1(virbr0-nic) entered disabled state [ 89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 92.062606] show_signal_msg: 27 callbacks suppressed [ 92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000] [ 95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed ### abnormal begins here ### [ 1429.496584] sched: RT throttling activated [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 1429.706305] clocksource: 'hpet' wd_now: c4741f2e wd_last: c3bcdb60 mask: [ 1429.706306] clocksource: 'tsc' cs_now: 4acf553cc2d cs_last: 4ac71a54967 mask: [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying [ 1437.469449] nfs: server 10.1.0.4 OK [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 1439.143498] sched_clock: Marking unstable (1439092126811, 50992985)<-(1439477690212, -334199655) [ 1440.403916] clocksource: Switched to clocksource hpet [ 1443.553969] hrtimer: interrupt took 629117003 ns [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 209.684 msecs [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 44.646 msecs [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering kernel.perf_event_max_sample_rate to 500 [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 61.329 msecs [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering kernel.perf_event_max_sample_rate to 250 [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 172.103 msecs [ 1463.284345] perf: interrupt took too long (1344829 > 59
[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked
I tried 4.15 rc8, same result. Went back one rev from my GRUB to 4.13.0-21 and saw the same result. Looking at the dmesg and syslog output, there were a lot of references to the video system. Grabbed another video card, slightly older and put that in. The fan on the one that came out didn't feel like it was spinning as freely as I would assume. Card may have simply been overheating when playing YouTube. New card has almost 1 hour of YouTube playback now with no problems on 4.13.0-25. Odd that this issue happened right with the reboot to the newer kernel, but if that's all it was then job done. If I see any of the same behavior I will post again. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1742867 Title: Screen blank, audio choppy, system locked Status in linux package in Ubuntu: Incomplete Bug description: While watching a YouTube video, screen went blank. Audio cut out, after a few seconds the audio started playing normally for a few more seconds then kept repeating the last half a second of audio for a few more seconds. Then it stopped and nothing responded. It did this a few times over the course of an hour. Had to power off the PC to get a reboot. Last time it did this I ssh'd from another PC to get dmesg and syslog info as it happened. Attaching those captures. clickwir@mach:~$ uname -a Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux clickwir@mach:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful dmesg [ 10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up link [ 10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [ 10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000 [ 10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000 [ 10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 10.730200] r8169 :02:00.0 eth0: link down [ 10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 16.875586] FS-Cache: Loaded [ 16.896010] FS-Cache: Netfs 'nfs' registered for caching [ 16.914353] NFS: Registering the id_resolver key type [ 16.914364] Key type id_resolver registered [ 16.914364] Key type id_legacy registered [ 17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 17.513074] Ebtables v2.0 registered [ 17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 17.863232] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 17.864899] virbr0: port 1(virbr0-nic) entered blocking state [ 17.864903] virbr0: port 1(virbr0-nic) entered disabled state [ 17.864995] device virbr0-nic entered promiscuous mode [ 17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ 18.038385] virbr0: port 1(virbr0-nic) entered blocking state [ 18.038388] virbr0: port 1(virbr0-nic) entered listening state [ 18.095412] virbr0: port 1(virbr0-nic) entered disabled state [ 89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 92.062606] show_signal_msg: 27 callbacks suppressed [ 92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000] [ 95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed ### abnormal begins here ### [ 1429.496584] sched: RT throttling activated [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 1429.706305] clocksource: 'hpet' wd_now: c4741f2e wd_last: c3bcdb60 mask: [ 1429.706306] clocksource: 'tsc' cs_now: 4acf553cc2d cs_last: 4ac71a54967 mask: [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying [ 1437.469449] nfs: server 10.1.0.4 OK [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 1439.143498] sched_clock: Marking unstable (1439092126811, 50992985)<-(1439477690212, -334199655) [ 1440.403916] clocksource: Switched to clocksource hpet [ 1443.553969] hrtimer: interrupt took 629117003 ns [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 209.684 msecs [ 1454.454671] INFO: NMI handler (perf_event_nmi_h
[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked
Installed 4.15 rc8 and same issue. dmesg [ 1265.953008] sched: RT throttling activated [ 1265.953018] clocksource: timekeeping watchdog on CPU4: Marking clocksource 'tsc' as unstable because the skew is too large: [ 1265.953021] clocksource: 'hpet' wd_now: 38b37199 wd_last: 3829ff32 mask: [ 1265.953022] clocksource: 'tsc' cs_now: 4262fdbe767 cs_last: 425d7d7d680 mask: [ 1265.953023] tsc: Marking TSC unstable due to clocksource watchdog [ 1265.953040] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 1265.953041] sched_clock: Marking unstable (1265908240846, 44771742)<-(1266267179035, -314139659) [ 1275.809138] clocksource: Switched to clocksource hpet [ 1299.951513] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 108.138 msecs [ 1299.951516] perf: interrupt took too long (845222 > 2500), lowering kernel.perf_event_max_sample_rate to 250 [ 1300.790347] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 137.277 msecs [ 1300.790351] perf: interrupt took too long (1072756 > 1056527), lowering kernel.perf_event_max_sample_rate to 250 [ 1306.558101] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 208.273 msecs [ 1306.558101] perf: interrupt took too long (1627614 > 1340945), lowering kernel.perf_event_max_sample_rate to 250 [ 1307.396931] hrtimer: interrupt took 629121891 ns [ 1310.123102] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 209.705 msecs [ 1323.540307] radeon :01:00.0: ring 0 stalled for more than 19176msec [ 1323.540312] radeon :01:00.0: GPU lockup (current fence id 0x00022c50 last fence id 0x00022c51 on ring 0) [ 1323.540321] perf: interrupt took too long (2198839 > 2034517), lowering kernel.perf_event_max_sample_rate to 250 [ 1337.804353] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 209.718 msecs [ 1337.804353] perf: interrupt took too long (3803000 > 2748548), lowering kernel.perf_event_max_sample_rate to 250 [ 1340.945936] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 209.758 msecs [ 1342.623577] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 393.159 msecs [ 1352.270069] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u16:2:4609] [ 1352.270071] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter nfsv3 nfs_acl cfg80211 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache zram binfmt_misc nls_iso8859_1 edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi ghash_clmulni_intel pcbc snd_hda_intel input_leds snd_hda_codec snd_hda_core aesni_intel snd_hwdep snd_seq_midi aes_x86_64 snd_seq_midi_event crypto_simd glue_helper cryptd snd_rawmidi snd_ctxfi snd_seq snd_pcm wmi_bmof k10temp eeepc_wmi asus_wmi sparse_keymap video snd_seq_device fam15h_power snd_timer [ 1352.270108] i2c_piix4 snd soundcore shpchp mac_hid bonding parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq hid_generic usbhid hid radeon i2c_algo_bit ttm e1000e drm_kms_helper syscopyarea sysfillrect ptp sysimgblt fb_sys_fops pps_core drm ahci r8169 libahci mii wmi [ 1352.270128] CPU: 2 PID: 4609 Comm: kworker/u16:2 Not tainted 4.15.0-041500rc8-generic #201801142030 [ 1352.270129] Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 EVO, BIOS 1604 10/16/2012 [ 1352.270155] Workqueue: events_power_efficient radeon_fence_check_lockup [radeon] [ 1352.270177] RIP: 0010:evergreen_is_display_hung+0x125/0x1b0 [radeon] [ 1352.270178] RSP: 0018:9b94495ebda0 EFLAGS: 0286 ORIG_RAX: ff11 [ 1352.270180] RAX: RBX: 0008 RCX: 0003 [ 1352.270181] RDX: 0003 RSI: 000112a0 RDI: 0005509f [ 1352.270181] RBP: 9b94495ebdf8 R08: R09: [ 1352.270182] R10: R11: 0055 R12: 8c3596e8 [ 1352.270183] R13: 0001 R14: 003f R15: 0001 [ 1352.270184] FS: () GS:8c35bec8() knlGS: [ 1352.270185] CS: 0010 DS: ES: CR0: 80050033 [ 1352.270186] CR2: 7fb40fd82000 CR3: 00061d2dc000 CR4: 000406e0 [ 1352.270187] Call Trace: [ 1352.270210] evergreen_gpu_check_soft_reset+0xc5/0x120 [radeon] [ 1352.270231] evergreen_gfx_is_lockup+0x17/0x40 [radeon] [ 1352.270246] radeon_fence_check_lockup+0x92/0x170 [radeon] [ 1352.270249] process_one_work+0x1ea/0x410 [ 1352.270250] worker_thread+0x253/0x410 [ 1352.270253] kthread+0x11e/0x140 [ 1352.270254] ?
[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked
Tested on 4.15 rc8 ** 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/1742867 Title: Screen blank, audio choppy, system locked Status in linux package in Ubuntu: Confirmed Bug description: While watching a YouTube video, screen went blank. Audio cut out, after a few seconds the audio started playing normally for a few more seconds then kept repeating the last half a second of audio for a few more seconds. Then it stopped and nothing responded. It did this a few times over the course of an hour. Had to power off the PC to get a reboot. Last time it did this I ssh'd from another PC to get dmesg and syslog info as it happened. Attaching those captures. clickwir@mach:~$ uname -a Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux clickwir@mach:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful dmesg [ 10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up link [ 10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [ 10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000 [ 10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000 [ 10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 10.730200] r8169 :02:00.0 eth0: link down [ 10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 16.875586] FS-Cache: Loaded [ 16.896010] FS-Cache: Netfs 'nfs' registered for caching [ 16.914353] NFS: Registering the id_resolver key type [ 16.914364] Key type id_resolver registered [ 16.914364] Key type id_legacy registered [ 17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 17.513074] Ebtables v2.0 registered [ 17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 17.863232] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 17.864899] virbr0: port 1(virbr0-nic) entered blocking state [ 17.864903] virbr0: port 1(virbr0-nic) entered disabled state [ 17.864995] device virbr0-nic entered promiscuous mode [ 17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ 18.038385] virbr0: port 1(virbr0-nic) entered blocking state [ 18.038388] virbr0: port 1(virbr0-nic) entered listening state [ 18.095412] virbr0: port 1(virbr0-nic) entered disabled state [ 89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 92.062606] show_signal_msg: 27 callbacks suppressed [ 92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000] [ 95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed ### abnormal begins here ### [ 1429.496584] sched: RT throttling activated [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 1429.706305] clocksource: 'hpet' wd_now: c4741f2e wd_last: c3bcdb60 mask: [ 1429.706306] clocksource: 'tsc' cs_now: 4acf553cc2d cs_last: 4ac71a54967 mask: [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying [ 1437.469449] nfs: server 10.1.0.4 OK [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 1439.143498] sched_clock: Marking unstable (1439092126811, 50992985)<-(1439477690212, -334199655) [ 1440.403916] clocksource: Switched to clocksource hpet [ 1443.553969] hrtimer: interrupt took 629117003 ns [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 209.684 msecs [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 44.646 msecs [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering kernel.perf_event_max_sample_rate to 500 [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 61.329 msecs [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering kernel.perf_event_max_sample_rate to 250 [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 172.103 msecs [ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering kernel.perf_event_max_sample_rate to 250 [ 1465.175694] INFO: NMI handler (perf_ev
[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
Linux laptop 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Just upgraded from 17.10 to 18.04, sorry, I somehow didn't realize my laptop was still back on 17.10. Anyway, 17.10 suspend/resume was perfect. But after about 10 resumes on 18.04, the wired NIC does not come back ever. Not even once. Currently running 4.15.0-48-generic and seeing this problem. Removing the 'sky2' module and re-adding it immediately fixes the problem. $ ip a shows 2: ens1: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 But the link light shows a good link and the activity shows activity as expected. This is an HP ProBook 6540b. 45:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8072 PCI-E Gigabit Ethernet Controller (rev 10) I have not tried the GRUB suggestion here: https://askubuntu.com/questions/1029620/ubuntu-18-04-lts-sky2-ethernet- stops-working-after-system-resume-from-suspend GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer" Again, I have not tried this yet. Just putting it here for reference in case it does work. -- 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/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] sky2 ethernet stops working after system resume from suspend. [Fix] Increase the PCI D3 delay can workaround the issue. [Test] User responded that the D3 delay increase can solve the issue. [Regression Potential] Low. It only affects one device. The fix only increase the delay timer, without any functional change. ===Original Bug Report=== After resuming from sleep using the lid-open event, OFTEN (60% replicable, usually after 2nd or later resume) the NIC is not functional, and reloading the sky2 module does not help. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 Possibly relevant: [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives first resume after that, but 1-2 suspend-resume cycles later the issue WILL occur again. Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice:
[Kernel-packages] [Bug 1788321] Re: swapon failed: invalid argument
Just did a fresh install of 20.04 as a Proxmox VM and see this "invalid argument" in the start up messages and syslog. Trying to start it manually also fails. Tried recreating it, also failed. root@changeme:/# fallocate -l 2G /swap.img root@changeme:/# chmod 600 /swap.img root@changeme:/# ls -lah /swap.img -rw--- 1 root root 2.0G Apr 24 04:07 /swap.img root@changeme:/# mkswap /swap.img mkswap: /swap.img: warning: wiping old swap signature. Setting up swapspace version 1, size = 2 GiB (2147479552 bytes) no label, UUID=bd9bdc4f-4c53-4b0b-ad92-687ed5f669e6 root@changeme:/# swapon /swap.img swapon: /swap.img: swapon failed: Invalid argument root@changeme:/# swapon -v /swap.img swapon: /swap.img: found signature [pagesize=4096, signature=swap] swapon: /swap.img: pagesize=4096, swapsize=2147483648, devsize=2147483648 swapon /swap.img swapon: /swap.img: swapon failed: Invalid argument -- 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/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1788321] Re: swapon failed: invalid argument
Fixed my problem. While looking through /var/log/syslog, I noticed this line around the same time swap mount failed. BTRFS warning (device sda3): swapfile must not be copy-on-write Then a few lines later... systemd[1]: swap.img.swap: Failed with result 'exit-code'. systemd[1]: Failed to activate swap /swap.img. systemd[1]: Dependency failed for Swap. systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'. Yes my root is on btrfs and I did not see this error before. So I deleted /swap.img and started over. $ sudo rm -rf /swap.img $ sudo touch /swap.img $ sudo chattr +C /swap.img $ sudo fallocate -l 2G /swap.img $ sudo chmod 600 /swap.img $ sudo mkswap /swap.img $ sudo swapon /swap.img No error and "swapon --show" gives this: NAME TYPE SIZE USED PRIO /swap.img file 2G 0B -2 Just what I was expecting. So problem solved for me, maybe a check can be put in to see if it's on btrfs and apply the 'chattr +C' option. -- 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/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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
