@jean-Pierre: Thank you very much, manually overwriting the .bin file
with the one form the commit you mentioned fixed it. Lets hope the fixed
is packaged for 18.04 soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ub
Greetings,
Have you ever tried that stuff before? It's something gorgeous, just take a
look http://comprehensive.rebelselector.com/c4c5
ulischroeder
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-common in Ubuntu.
https://bu
Version 0.9.1 fixes this bug for armhf and aarch6. I'm using Docker on
both platforms and I'm happy to see that the network startup won't get
confused any more by ubuntu-fan (like version 0.9.0 did). This is what I
can confirm.
What I cannot conform is if 0.9.1 has any impact for people who rely o
> @Uli, It's an automated dependency.
I know.
The question is: Should I modify /etc/network/fan if I'm using private
IP addresses outside of 10.254/16, 172.16/12, 192.168/16, e.g. 10/24 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is
I've have docker.io installed, but I didn't modify /etc/default/ubuntu-
fan nor /etc/network/fan.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes iss
Version 0.9.1 fixes the bug for armhf and aarch64 in the way that I
won't get an error message any more. I don't use a fan configuration so
cannot tell anything about possible side effects for (active) fan users.
--
You received this bug notification because you are a member of Kernel
Packages, w
I faced the same issue with an embedded LEX 2I260D-H26 on Ubuntu 16.04
both in kernels 4.6. I faced an issue where (when not blacklisting the
gma500_gfx driver via /etc/modprobe.d/blacklist.conf), the HDMI screen
would stay black, unless the HDMI cable was NOT plugged in during boot
in which case I
I meant included in linux-firmware, not just linux-lts-utopic. I am on
15.10 with the same issue, and the patch works, but it means downgrading
the linux-firmware package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in U
The patched package is somewhat outdated now. Wish this were finally
included in the official linux-firmware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1475639
Title:
No ad
Hello Joseph,
before issuing an upstream bug report I tried the first stable release
of 3.18 [0] and I wasn't able to reproduce the bug so far. So you may
suspend or keep this bug report on hold. I'd really like to know if
there is some incidence (i.e. a specific commit) for this bug being
fixed b
I there anything I can do next?
--
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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Status in linux package in Ubuntu:
Conf
If I totally disable any sound output or even the whole sound subsystem,
do you think this will decrease the likelihood of this bug to appear?
--
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
I tried the 3.18-rc4 kernel, the bug is also there:
Nov 16 07:16:39 box kernel: [34280.152007] NMI watchdog: BUG: soft lockup -
CPU#1 stuck for 22s! [clamscan:2868]
Nov 16 07:16:39 box kernel: [34280.152007] Modules linked in: xt_multiport
iptable_filter ip_tables x_tables gpio_ich snd_hda_codec
eeab517b68beb9e044e869bee18e3bdfa60e5aca exhibits the bug (quite early
this time, only 100s after starting the checks)
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403
94daf85e3c4db3b804205277eec7c4eae6efe9db is clean
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
23b4faa9a36257e75dade0f2945bc3e487e6f4
a3183c60e3e9be7abd830ebed904491625e07d2e: clean
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
23b4faa9a36257e75dade0f2945bc3e487e6f463
5e1109adde6acd0f3424886da09402ac22ed244b: clean
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
23b4faa9a36257e75dade0f2945bc3e487e6f463
8a5dc585d50015af9c079ae2d182dc4c1cd22914: bug
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
23b4faa9a36257e75dade0f2945bc3e487e6f463:
Is there anything I should test next?
--
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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Status in “linux” package in Ubuntu
86467ff2ddca94c0d8d10b92b5916e68c0cad8a9: clean
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
23b4faa9a36257e75dade0f2945bc3e487e6f46
23b4faa9a36257e75dade0f2945bc3e487e6f463: clean
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
23b4faa9a36257e75dade0f2945bc3e487e6f463
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
a6bc732b5a96b5403c2637e85c350b95ec6591f3: clean
c2d33069915d1f9b3b1dcc2199af11d4e072b037
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
2026d24ef2ea8caad5e87662a58075e930ccab63: clean
c2d33069915d1f9b3b1dcc2199af11d4e072b037: bug
5cbb3d216e2041700231bcfc383ee5f8b7fc8b74:
c2d33069915d1f9b3b1dcc2199af11d4e072b037: exhibits this bug
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
c2d33069915d1f9b3b1dcc2199af11d4e072b037: bug
5cbb3d216e2041700231bcfc383ee5f8b7fc8b74: bug
3.13.0-031300rc1-generic: bug
3.
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: seems to be clean, did the
check twice.
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
f095ca6b31cfd20e6e7e0338ed8548d8a4374287: clean
5cbb3d216e2041700231bcfc383ee5f8b7fc8b74: bug
3.13.0-031300rc1-generic: bug
3.13 final: bug
--
You r
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: seems to be clean, did the
check twice.
3.12 final: clean
f9efbce6334844c7f8b9b9459f6d7a6fbc2928e0: clean
5cbb3d216e2041700231bcfc383ee5f8b7fc8b74: bug
3.13.0-031300rc1-generic: bug
3.13 final: bug
--
You received this bug notification because you are a
5cbb3d216e2041700231bcfc383ee5f8b7fc8b74: bug
[ 908.144025] BUG: soft lockup - CPU#0 stuck for 22s! [md3_raid1:173]
[ 908.144025] Modules linked in: xt_multiport iptable_filter ip_tables
x_tables gpio_ich snd_hda_codec_realtek coretemp snd_hda_intel serio_raw
snd_hda_codec pl2303 usbserial snd
3.12 final: clean
3.12.14: clean
3.12.21: clean
3.12.25: clean
3.12.27: clean
3.12.28: clean
3.13.0-031300rc1-generic: bug
3.13.0-031300rc2-generic: bug
3.13.0-031300rc3-generic: bug
3.13.0-031300rc5-generic: bug
3.13.0-031300rc6-generic: bug
3.13 final: bug
Is there any kernel version before 3.13
3.12 final: clean
3.12.14: clean
3.12.21: clean
3.12.25: clean
3.12.27: clean
...
3.13.0-031300rc1-generic: bug
3.13.0-031300rc2-generic: bug
3.13.0-031300rc3-generic: bug
3.13.0-031300rc5-generic: bug
3.13.0-031300rc6-generic: bug
3.13 final: bug
--
You received this bug notification because you
3.12 final: clean
3.12.14: clean
3.12.21: clean
3.12.25: clean
...
3.13.0-031300rc1-generic: bug
3.13.0-031300rc2-generic: bug
3.13.0-031300rc3-generic: bug
3.13.0-031300rc5-generic: bug
3.13.0-031300rc6-generic: bug
3.13 final: bug
--
You received this bug notification because you are a member o
3.12 final: clean
3.12.14: clean
3.12.21: clean
...
3.13.0-031300rc1-generic: bug
3.13.0-031300rc2-generic: bug
3.13.0-031300rc3-generic: bug
3.13.0-031300rc5-generic: bug
3.13.0-031300rc6-generic: bug
3.13 final: bug
--
You received this bug notification because you are a member of Kernel
Packag
3.12 final: clean
3.12.14: clean
...
3.13.0-031300rc1-generic: bug
3.13.0-031300rc2-generic: bug
3.13.0-031300rc3-generic: bug
3.13.0-031300rc5-generic: bug
3.13.0-031300rc6-generic: bug
3.13 final: bug
--
You received this bug notification because you are a member of Kernel
Packages, which is su
For the records:
3.12 final: clean
...
3.13.0-031300rc1-generic: bug
3.13.0-031300rc2-generic: bug
3.13.0-031300rc3-generic: bug
3.13.0-031300rc5-generic: bug
3.13.0-031300rc6-generic: bug
3.13 final: bug
--
You received this bug notification because you are a member of Kernel
Packages, which is
3.13.0-031300rc1-generic: exhibits this bug
I'll try v3.12.14-trusty next
--
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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
3.13.0-031300rc2-generic: exhibits this 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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Status in “linux” package in
Hello Joseph,
the last kernel, you have prepared for testing contains this bug.
I've just noticed that 3.13.0-031300rc3-generic kernel contains the bug
the bug as well, so the bisect went in the wrong direction. Sorry for
this. I'll have a deeper look inside, hoping to understand why the bug
didn
OK, I didn't install the linux-image-extra package, it wasn't necessary
with the other kernels I've tested before. With this package installed,
the kernel boots properly, but
c6c1f325: exhibits this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I'd like to test the kernel, but this particular build doesn't come up
with support for networking nor usb keyboard. I've attached the
dmesg.gz.
** Attachment added: "dmesg.3.13.0-36.63~lp1356558v1.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356558/+attachment/4200926/+files/dmes
The v3.13-rc3 build instead is running well.
** Attachment added: "dmesg.3.13.0-031300rc3.201312061335.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356558/+attachment/4200927/+files/dmesg.3.13.0-031300rc3.201312061335.gz
--
You received this bug notification because you are a me
Hi Joseph,
unfortunately the kernel you are offering for testing is for the amd64
platform, but I need it for the i386 platform.
Regards
Uli
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
c6c1f325adc8a8e0cd06c6ad0ca232a6880a1783: exhibits this bug:
Sep 8 22:18:29 box kernel: [ 1940.144024] BUG: soft lockup - CPU#0 stuck for
22s! [md3_raid1:172]
Sep 8 22:18:29 box kernel: [ 1940.144024] Modules linked in: xt_multiport
iptable_filter ip_tables x_tables gpio_ich snd_hda_codec_real
308d17ef9530f236466a31a7855fc3d5176292d4: exhibits this bug
Sorry for the confusion.
--
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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s!
308d17ef9530f236466a31a7855fc3d5176292d4: doesn't exhibit this 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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Status
v3.13-rc5: exhibits this 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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Status in “linux” package in Ubuntu:
Confi
v3.13-rc3: doesn't exhibit this bug
v3.13-rc6: exhibits this bug
I'll try v3.13-rc4 and v3.13-rc5 next, but http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.13-rc4-trusty/ seems to be incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
is there any kernel I should try next?
--
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/1356558
Title:
BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Status in “linux” package in Ubunt
3.12 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/
doesn't seem to have this regression
--
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/1356558
Title:
BUG: soft locku
Update
regression yes (but significantly later : v3.13 Final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/
regression yes: v3.13.5:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.5-trusty/
not tested: v3.13.11.4:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.4-trust
regression no: v3.13 Final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/
regression yes: v3.13.5:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.5-trusty/
not tested: v3.13.11.4:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.4-trusty/
--
You received this bug noti
Public bug reported:
Hi,
this bug appeared in Ubuntu 14.04, Ubuntu 12.04 didn't show this behavior.
I've found a possible predecessor in bug #212684.
Switching to a recent mainline kernel didn't fix this issue.
Starting
$ /usr/share/mdadm/checkarray /dev/md3
will repeat this behavior.
/dev/
@ Larry & Sirius
That is great to hear! I'll try and dig out the old card to test this over the
weekend.
@nobody
You dont have to use a USB Card. You can trick Lenovos whitelisting by using
the WWAN slot instead of the WLAN slot. But it sounds like thanks to Larry
Fingers work this wount be nec
@ Christopher
Am I understanding you correctly? Do you seriously want each user affected by
this bug to file a duplicate bug report?
Should Koen file one for each of his 228 cards, or just one bug report per user
and devise?
--
You received this bug notification because you are a member of Ke
@ Christopher
If you read the comments above you will find that this bug is most definetly
not fixed!
I also changed the wireless the card from my laptop, which is the only proper
workaround. If you want I can install the old card to confirm it is still not
working properly, but the word of al
53 matches
Mail list logo
