[Kernel-packages] [Bug 2016371] [NEW] kernel NULL pointer dereference in apparmor_parser
Public bug reported: Since about a month or so, I get many oopses from apparmor, such as this one: [ 14.620816] BUG: kernel NULL pointer dereference, address: 0130 [ 14.620822] #PF: supervisor read access in kernel mode [ 14.620825] #PF: error_code(0x) - not-present page [ 14.620829] PGD 0 P4D 0 [ 14.620834] Oops: [#1] PREEMPT SMP PTI [ 14.620838] CPU: 0 PID: 1105 Comm: apparmor_parser Not tainted 5.19.0-38-generic #39~22.04.1-Ubuntu [ 14.620842] Hardware name: LENOVO 20FES3TE00/20FES3TE00, BIOS N1GETA2W (1.81 ) 06/12/2020 [ 14.620845] RIP: 0010:aa_unpack+0x127/0x540 [ 14.620853] Code: 00 48 85 c0 0f 84 29 04 00 00 48 8d 75 a0 48 8d 7d b0 4c 8b 7d c0 e8 e8 ea ff ff 48 89 c3 48 3d 00 f0 ff ff 0f 87 00 02 00 00 <4c> 8b b0 30 01 00 00 4d 85 f6 0f 84 38 01 00 00 49 8b 86 c8 00 00 [ 14.620857] RSP: 0018:b07141cc3ce0 EFLAGS: 00010207 [ 14.620861] RAX: RBX: RCX: [ 14.620864] RDX: RSI: RDI: [ 14.620867] RBP: b07141cc3d48 R08: R09: [ 14.620869] R10: R11: R12: b07141cc3da8 [ 14.620872] R13: b07141cc3da0 R14: 9755c5518000 R15: 9755c5500010 [ 14.620875] FS: 7f53ef091740() GS:9756f960() knlGS: [ 14.620879] CS: 0010 DS: ES: CR0: 80050033 [ 14.620882] CR2: 0130 CR3: 000106b64006 CR4: 003706f0 [ 14.620886] DR0: DR1: DR2: [ 14.620888] DR3: DR6: fffe0ff0 DR7: 0400 [ 14.620891] Call Trace: [ 14.620893] [ 14.620899] aa_replace_profiles+0x97/0x1010 [ 14.620906] ? _copy_from_user+0x55/0x90 [ 14.620913] policy_update+0xdb/0x180 [ 14.620918] profile_replace+0xbb/0x150 [ 14.620923] vfs_write+0xb5/0x2a0 [ 14.620929] ksys_write+0x67/0xf0 [ 14.620933] __x64_sys_write+0x19/0x30 [ 14.620937] do_syscall_64+0x59/0x90 [ 14.620941] ? irqentry_exit_to_user_mode+0x9/0x20 [ 14.620946] ? irqentry_exit+0x43/0x50 [ 14.620949] ? exc_page_fault+0x92/0x1b0 [ 14.620954] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 14.620960] RIP: 0033:0x7f53eef14a37 [ 14.620964] Code: 10 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 14.620968] RSP: 002b:7fffa3676028 EFLAGS: 0246 ORIG_RAX: 0001 [ 14.620972] RAX: ffda RBX: 5628aad3df60 RCX: 7f53eef14a37 [ 14.620975] RDX: 00018000 RSI: 5628aad6e810 RDI: 0006 [ 14.620978] RBP: 00018000 R08: R09: 5628aad6e810 [ 14.620980] R10: R11: 0246 R12: 5628aad6e810 [ 14.620983] R13: 00018000 R14: 5628a9b26c5b R15: 0006 [ 14.620989] [ 14.620991] Modules linked in: snd_soc_avs snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_hda_codec_hdmi snd_soc_acpi snd_ctl_led snd_soc_core snd_hda_codec_conexant snd_compress snd_hda_codec_generic ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl_msr snd_intel_dspcfg intel_rapl_common snd_intel_sdw_acpi intel_tcc_cooling x86_pkg_temp_thermal snd_hda_codec intel_powerclamp snd_hda_core btusb thinkpad_acpi btrtl binfmt_misc kvm_intel snd_hwdep nvram btbcm snd_pcm ledtrig_audio uvcvideo btintel kvm iwlmvm snd_seq_midi videobuf2_vmalloc btmtk mei_pxp mei_hdcp snd_seq_midi_event videobuf2_memops rapl mac80211 snd_rawmidi videobuf2_v4l2 input_leds intel_cstate bluetooth snd_seq videobuf2_common libarc4 joydev serio_raw hid_sensor_accel_3d hid_sensor_custom_intel_hinge hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_als nls_iso8859_1 wmi_bmof think_lmi firmware_attributes_class snd_seq_device videodev ecdh_generic [ 14.621071] hid_sensor_trigger iwlwifi snd_timer industrialio_triggered_buffer ecc mc kfifo_buf snd cfg80211 mei_me hid_sensor_iio_common intel_pch_thermal intel_xhci_usb_role_switch mei industrialio soundcore platform_profile mac_hid sch_fq_codel coretemp msr parport_pc ppdev ramoops pstore_blk lp reed_solomon efi_pstore parport pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_crypt wacom usbhid hid_sensor_custom hid_sensor_hub hid_generic intel_ishtp_hid hid i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core crct10dif_pclmul drm_kms_helper crc32_pclmul syscopyarea ghash_clmulni_intel sysfillrect sysimgblt aesni_intel fb_sys_fops nvme rtsx_pci_sdmmc i2c_i801 crypto_simd intel_ish_ipc xhci_pci cryptd drm psmouse e1000e nvme_core i2c_smbus rtsx_pci intel_ishtp xhci_pci_renesas wmi video [ 14.621163] CR2: 0130 [ 14.621166] ---[ end trace ]--- [
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
Yes, there are solutions to this that don't expose the whole kernel to
root.
* This project's kernel module could use DKMS. This could make use of the MOK
workflow already present in Ubuntu.
* This project's kernel module could be included in the upstream kernel.
The last option would be more secure, but more difficult to achieve.
I don't think this can be solved in Ubuntu, so let's continue this
discussion in the first upstream issue you linked. (Although I'd
probably need to take a look at the source code and I don't know any
C#.)
--
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/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
So, um, is there a simple way to get this fix into the other affected
distributions or do I have to open an issue in each one?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: LENOVO 20E8S00600
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-68-generic
root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet
splash kaslr i915.alpha_support=1 vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-68-generic N/A
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
I can confirm that this bug is fixed in bionic:
# echo "x" > /proc/sysrq-trigger
Nov 14 20:38:58 panzersperre kernel: sysrq: SysRq :
Nov 14 20:38:58 panzersperre kernel: This sysrq operation is disabled from
userspace.
I don't have a disco or eoan to test.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: LENOVO 20E8S00600
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-68-generic
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
I'm no expert in either kernel or C programming and I didn't test this
patch, but it looks good to me.
Also, the resulting code is quite similar to the one Fedora is currently using
- they accidentally fixed this bug in
https://src.fedoraproject.org/rpms/kernel/c/5df4c5562f191b434edf57e8c92b176baad37cba.
(Debian also seems to be affected:
https://salsa.debian.org/kernel-team/linux/blob/4dcfa860/debian/patches/features/all/lockdown/0002-Add-a-SysRq-option-to-lift-kernel-lockdown.patch)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
This is relatively hard to reproduce. It happens sometimes directly after boot and login, sometimes after more than a week uptime. I've simply selected an older kernel at boot (4.8.0-46-generic; the newest one I had installed from Yakkety) and I didn't experience a crash, yet. -- 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/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
I'm experiencing the same issue for a while now. I think it occurred after I upgraded form Yakkety to Zesty. I'm currently on 4.10.0-21-generic. I think the issue is more likely to happen when I run CPU and / or RAM intensive applications. If this happens, all my screens are stuck. ** Attachment added: "a snippet from dmesg; problem occurs at 15:15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+attachment/4892288/+files/grafikcrash-2017-06-08.log -- 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/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe
[Kernel-packages] [Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
Since I've upgraded to yakkety, this issue seems to be gone. But the weird thing is: I'm not even able to reproduce it with a live version of xenial with the exact same software I ran when I first encountered the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Triaged Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
This doesn't work for me. (But I've got a 7265D and not a 7260.) -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Triaged Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1540406] Re: warning: file-aligned section .text extends beyond end of file
Just got this warning when installing linux-signed- image-4.4.0-51.72-generic: warning: file-aligned section .text extends beyond end of file warning: checksum areas are greater than image size. Invalid section table? And the new kernel won't boot. The old one still works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1540406 Title: warning: file-aligned section .text extends beyond end of file Status in linux-signed package in Ubuntu: Confirmed Bug description: When running a dist-upgrade, I received the following warning: Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ... warning: file-aligned section .text extends beyond end of file warning: checksum areas are greater than image size. Invalid section table? Note: I've tried booting the kernel with dmesg enabled, it seems to boot just fine. See https://launchpadlibrarian.net/235948033/CurrentDmesg.txt for when I booted it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-signed-image-4.4.0-2-generic 4.4.0-2.16 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 1 15:58:45 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (65 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1540406/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
So, this seems to be the same bug as https://bugzilla.kernel.org/show_bug.cgi?id=114501. ** Bug watch added: Linux Kernel Bug Tracker #114501 http://bugzilla.kernel.org/show_bug.cgi?id=114501 -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Triaged Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
This is the thread on the mailing list: https://marc.info/?t=14681417051=1=2 -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Triaged Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
Yes, this problem still occurs with 4.7-rc6. -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Incomplete Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
I didn't manage to bisect the commits because every version failed to build. Then I started from 4.1.0-1 and reverted commits with "iwlwifi" in the title. http://kernel.ubuntu.com/git/ubuntu/ubuntu- wily.git/commit/?id=8d193ca26cc28019e760b77830295a0c349d90dc seems to be the culprit. (Resuming from standby works without and not with it.) -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Incomplete Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
I can't build the second commit to test. The build fails with the following: II: Checking modules for generic... reading new modules...read 4341 modules. reading old modules... MISS: bcm_sf2 MISS: dsa_core MISS: hid-huion MISS: intel_mid_dma MISS: mv88e6060 MISS: mv88e6xxx_drv MISS: phy-generic MISS: snd-soc-atmel-pcm MISS: snd-soc-sst-bytcr-dpcm-rt5640 MISS: snd-soc-wm8804 MISS: tc3589x-keypad MISS: tpm_i2c_stm_st33 NEW : spi-cadence NEW : comedi_8254 NEW : nhc_hop NEW : btbcm NEW : nhc_routing NEW : snd-soc-sst-bytcr-rt5640 NEW : vfio_virqfd NEW : nhc_dest NEW : nhc_udp NEW : snd-soc-sst-ipc NEW : btintel NEW : nhc_mobility NEW : usb_f_printer NEW : nhc_fragment NEW : snd-hda-core NEW : nhc_ipv6 read 4337 modules : new(16) missing(12) EE: Missing modules (start begging for mercy) I'm at d0a3997. -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Incomplete Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
So, I'm done with versions bisecting. The issue has been introduced somewhere between 4.0.0-4 and 4.1.0-1. I'll commit bisect later. -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Incomplete Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
** Description changed: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). - A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the + A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: niklas 2175 F pulseaudio - /dev/snd/controlC0: niklas 2175 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: niklas 2175 F pulseaudio + /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. - - lxcbr0no wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. + + lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-22-generic N/A - linux-backports-modules-4.4.0-22-generic N/A - linux-firmware1.157 + linux-restricted-modules-4.4.0-22-generic N/A + linux-backports-modules-4.4.0-22-generic N/A + linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO ** 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Confirmed Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
** Attachment added: "iwlwifi.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+attachment/4685023/+files/iwlwifi.log -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Incomplete Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
I've tested it with rc2 and rc3. It does still happen. -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Incomplete Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
This error occurs in 4.4.0-21-generic as well, but not in 3.19.0-59-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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Confirmed Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+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 1588637] [NEW] iwlwifi: Microcode SW error detected. Restarting 0x2000000
Public bug reported: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Attachment added: "a snippet from the systemd journal" https://bugs.launchpad.net/bugs/1588637/+attachment/4675656/+files/iwlwifi-error.log -- 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/1588637 Title: iwlwifi: Microcode SW error detected. Restarting 0x200 Status in linux package in Ubuntu: Confirmed Bug description: My wifi won't work after I wake my laptop up from standby. This problem looks quite the same as #1099487 or #944271. But I experienced this bug on Xenial with 4.4.0-22-generic (amd64). A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi" doesn't solve the problem. (A reboot does.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: niklas 2175 F pulseaudio /dev/snd/controlC0: niklas 2175 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 08:23:06 2016 InstallationDate: Installed on 2015-12-11 (174 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: LENOVO 20E8S00600 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JHET20WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20E8S00600 dmi.product.version: ThinkPad 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588637/+subscriptions -- Mailing list:
