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.
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
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
** 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
** 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.
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
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
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
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
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
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.
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
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
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
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.
**
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
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
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:
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
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
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
[
21 matches
Mail list logo
