It resolved itself. Sorry to bother you.
I listed all installed Linux kernel packages (dpkg -l | grep
"linux\-[a-z]*\-") and kept only the 6.2.0-26 versions. Then I removed
unused packages (sudo apt autoremove) and afterwards reinstalled
6.2.0-32 (sudo apt install linux-image-6.2.0-32-generic
Public bug reported:
After the update from kernel 6.2.0-26 to 6.2.0-32 under Ubuntu 22.04
LTS, there are no more sound cards found. I can reliably reproduce this
by switching in the grub boot menu between the kernel versions.
I used sound over HDMI of the NVIDIA Corporation GP108 [GeForce GT
Bootin with boot option break=premount:
(initramfs) modprobe zfs
[ 45.484502] spl: loading out-of-tree module taints kernel.
[ 45.503302] icp: module license 'CDDL' taints kernel.
[ 45.509218] Disabling lock debugging due to kernel taint
[ 45.709339] ZFS: Loaded module v2.1.2-1ubuntu3, ZFS
P.S.: I renamed the zpools from rpool_unencrypted to rpool and from
bpool_unencrypted to bpool. Just to find out if this is the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Next test:
Same with boot options break=premount, but then only bpool imported:
(initramfs) modprobe zfs
(initramfs) zpool import -N bpool
(initramfs) zpool status
pool: bpool
state: ONLINE
scan: scrub repaired 0B in 00:00:55 with 0 errors on Mon Sep 12 19:50:53 2022
config:
NAME
Oops I did it again...
Hi folks,
after moving my zpool to another hardware because of a broken system I got
almost the same error with jammy. So it might not be fixed and I still have a
problem.
[ 48.494682] ZFS: Loaded module v2.1.2-1ubuntu3, ZFS pool version 5000, ZFS
filesystem version 5
There are 2 usable configurations in 12d1:15c1, cfg#2 which is cdc_ether
and cfg#3 which is cdc_mbim , usb_modeswitch will select the linux
preferred mbim configuration if mbim drivers are present in the kernel.
This is by design and not a bug.
A user who prefers cdc_ether can disable the the
Updating to jammy fixed this problem...
-> Close
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956101
Title:
BUG: kernel NULL pointer dereference, address: 06c8
Public bug reported:
I am trying to get rid of the bug#1906476, so I installed a new Ubuntu/Impish
on another Disk with an unencrypted rpool followed the tutorial at
https://openzfs.github.io/openzfs-docs/Getting%20Started/Ubuntu/Ubuntu%2020.04%20Root%20on%20ZFS.html
After installation I copied
Public bug reported:
For the Lenovo L15 (with Ubuntu 20.04 and Kernel 5.10.0-1038.40) the F1,
F4 and NumLock LEDs remain lit after shutdown.
Boot of the machine via the power button is not possible until the battery is
drained and the machine is plugged via power chord. Alternatively, a hard
The security fixed Kernel
# cat /proc/version_signature
Ubuntu 5.4.0-80.90-generic 5.4.124
from focal-security also fixes the problem.
Greetings,
Lars
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Hello Kleber,
thank you very much for your fast reply!
I can confirm that Kernel:
# cat /proc/version_signature
Ubuntu 5.4.0-79.88-generic 5.4.124
fixes my Problem.
We can close this bug.
Greetings,
Lars
--
You received this bug notification because you are a member of Kernel
Packages
5.4.0-77.86-generic 5.4.119
Is anyone else having this problem?
Thanks in advance,
Lars
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : ker
-image-5.4.0-77-generic 5.4.0-77.86 amd64Signed kernel image
generic
# cat /proc/version_signature
Ubuntu 5.4.0-77.86-generic 5.4.119
Is anyone else having this problem?
Thanks in advance,
Lars
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags
Public bug reported:
Hi.
(sorry if this is in the wrong place, but a nice person at
#ubuntu@LiberaChat told me to try here)
The current hwe-netboot kernel for bionic is still suffering from the
bug described in #1893956, which basically lacks the support for Intel
X710 NICs. Causing netboot to
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable.
I'm also affected by this bug. I just did a fresh install of Xubuntu
20.04.1 and see the issue.
In my case it's "usb usb2-port1: Cannot enable. Maybe the USB cable is
bad?".
There are no USB devices connected at all, so I get the bug with only
the motherboard root hub present. I can make the log
Public bug reported:
WIreless connectivity has been very flaky in focal ever since release.
Thought I'd start investigating a bit. This is all I found, but it
clearly signisfies an error. Please let med know, if I can provide more
information.
Description:Ubuntu 20.04 LTS
Release:
I'd like to add that this bug also occurs exactly as described (full
system freeze when heavy traffic begins) on Pop!_OS 19.10 with kernel
5.3 and the 9260ac.
Pop!_OS 19.10 x86_64
Dell Precision 5530
5.3.0-19-generic
lspci -nnv output:
3b:00.0 Network controller [0280]: Intel Corporation
usb_modeswitch did once upon a time check that a driver bound to the
dongles interface(s) and if not then it did a modeprobe of the option
serial driver. If it still didn't get option to bind then it added the
dongles usb id to option's new_id and if the driver bound then it asked
the user to
This is not an issue for Linux USB developers, it is a matter of
usb_modeswitch's default switch message under linux and Canonical's
implementation of usb_modeswitch.
As a start before I continue, which is the usb_modeswitch version?
--
You received this bug notification because you are a
Confirming fix, login working again on bionic. Thanks for your work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813873
Title:
Userspace break as a result of missing patch backport
Confirming the login loop bug for 18.04.2 with 4.15.0-45-generic
And also confirming the fix in proposed with 4.15.0-46-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/1813873
Yes, I think this bug is a duplicate.
--
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/1814084
Title:
The screen went black - had to restart. Have happened several times
today..
Status
Public bug reported:
The screen went black - had to restart. Have happened several times
today..
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-44-generic 4.15.0-44.47
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
Uname: Linux 4.15.0-44-generic x86_64
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
This bug affects me as well: Lenovo X1 Carbon 6th generation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm not hit by the kernel bug - I haven't tried installing kernel
4.15.0.44 yet. But some of my colleagues has - and opened bug [bug
1813663|https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663] in
return. We have a lot of rather new Lenovo laptops here...
My running config is still:
Do you need more information from me?
Still marked as 'incomplete', I see.
--
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/1811860
Title:
Display ports on Lenovo docking
The dock connects through Thunderbolt - and yes, it was connected when I
ran lspci.
It is this dock: https://www.lenovo.com/us/en/accessories-and-monitors
/top-tech/Ultra-Dock-135-W-US/p/40AJ0135US
It's hard to get exact specifications for this dock, though.
--
You received this bug
lspci output attached.
Thanks in advance. :-)
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1811860/+attachment/5230229/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Forgot to mention: Downgrading linux-firmware from 1.173.3 to 1.173.2
made a single port work again.
Still cannot use two ports.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Public bug reported:
Lenovo Carbon X1 running on Lenovo Thinkpad Ultra Dock
I have only been able to attach a single monitor to the docking station
before the upgrade of linux-firmware. After todays upgrade from 1.173.2
to 1.173.3, none of the outputs work anymore.
The Ultra Dock has two DP, an
encryption right now.
Greetings,
Lars
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802481
Title:
cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported
during boot
order during boot.
The zpool has to be imported at the time when cryptsetup starts. Is there any
reason it is other way round?
Greetings,
Lars
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https
mfs-shell (initramfs).
When I do zpool list there is no zpool importet.
After
zpool import -N rpool
^D
the cryptsetup succeeds.
Greetings,
Lars
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cryptsetup-initramfs 2:2.0.4-2ubuntu2
ProcVersionSignature: Ubuntu 4.1
Hello,
I tried to install the new Kernel. But get the same Problem.
root@h2744217:~# sudo dpkg -i *.deb
Vormals nicht ausgewähltes Paket linux-headers-4.18.0-041800rc7-generic wird
gewählt.
(Lese Datenbank ... 113720 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169382/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169381/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784244
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169384/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169387/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169386/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected bionic
** Description changed:
Hello,
today I would Update the Kernel on my Server. But I got this warning at the
Kernel Installation.
Is that an Bug?
[Code]
sudo update-initramfs -u update-initramfs: Generating
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169380/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169388/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169385/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1784244/+attachment/5169383/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Hello,
today I would Update the Kernel on my Server. But I got this warning at the
Kernel Installation.
Is that an Bug?
[Code]
sudo update-initramfs -u update-initramfs: Generating
/boot/initrd.img-4.15.0-29-generic
cryptsetup: WARNING: failed to detect canonical device
A package dependency issue should not require log-files.
** 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/1777166
** Description changed:
- For Ubuntu 18.04 recently new dependencies have been added from linux-
- image-generic to intel-microcode and amd64-microcode.
+ For Ubuntu 18.04 recently (since kernel 4.15.0.23) new dependencies have
+ been added from linux-image-generic to intel-microcode and
+
Public bug reported:
For Ubuntu 18.04 recently new dependencies have been added from linux-
image-generic to intel-microcode and amd64-microcode.
Problem with that is that at least intel-microcode is not compatible with all
hardware:
For my good old Acer Travelmate 292 (Pentium M Machine), the
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920
We can also confirm, that kernel image 4.15.0-15.16 boots on one of our
affected machines.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64
and
linux-image-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_amd64
both are working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
System works with
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/linux-
image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
Too funny. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
linux-image-4.4.0-116-generic_4.4.0-116.140~lp1745349Commitb0c3e8bd0405Reverted_amd64
seems to work here, 3 reboots in a row on one machine without hard locks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
No success, hard locks with b0c3e8bd040
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
Status in linux package
47a07600efe does not work here, hard lock on two pcs.
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
Status in
Yay!
Three boots in a row worked with
linux-image-4.4.0-110-generic_4.4.0-110.133~lp1745349Commit7de295e2a47849_amd64
Was only able to test on one machine though, all my users are logged in.
More testing tomorrow.
--
You received this bug notification because you are a member of Kernel
No luck, unfortunately.
linux-image-4.4.0-110-generic_4.4.0-110.133~lp1745349Commitd3d0f0a209ee_amd64
shows the same hard lock.
--
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/1745349
Sorry, no improvement on ASUS H110M-C Board with
linux-image-4.4.0-116-generic_4.4.0-116.140~lp1745349Commitff2699cReverted_amd64
Still 4 out of 5 boots result in hard lock.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi there,
we tried this new kernel - our test machine still locked up during the
boot process while starting services.
--
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/1746418
Title:
Am 22.02.2018 um 09:05 schrieb ake sandgren:
> The 4.4.0-116-generic still hangs my laptop during boot the same way
> -112 did. And noibpb still solves the problem.
Confirming for Asus H110M-C boards, still the hardlocks.
--
You received this bug notification because you are a member of Kernel
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5046867/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Any more info that you need? The bug is still tagged as "incomplete"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
Hard lockup during boot with
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5042847/+files/WifiSyslog.txt
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5046863/+files/WifiSyslog.txt
**
Am 25.01.2018 um 21:45 schrieb Joseph Salisbury:
> Can you see if either of the following two kernels also exhibit the bug:
>
> 4.4.0-110: https://launchpad.net/~canonical-kernel-security-
> team/+archive/ubuntu/ppa/+build/14231477
>
> 4.4.0-111: https://launchpad.net/~canonical-kernel-security-
Public bug reported:
Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
instead they show
NMI watchdog: Watchdog detected hard lockup on cpu 0
NMI watchdog: Watchdog detected hard lockup on cpu 1
NMI watchdog: Watchdog detected hard lockup on cpu 3
NMI watchdog: Watchdog
147 ***
> https://bugs.launchpad.net/bugs/1734147
>
> ** This bug has been marked a duplicate of bug 1734147
> corrupted BIOS due to Intel SPI bug in kernel
>
--
Cheers
Lars
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
You
Public bug reported:
I have an ACER V5-571G-53314G75Makk, SSID:23302770966
Installed Ubuntu 17.10.1 yesterday and can longer boot into USB or
CDROM. Cannot access BIOS(Phoenix) via F2.
Ubuntu boots fine and works.
I have followed the steps above in #1734147, installing both kernel
versions and
I have an ACER V5-571G-53314G75Makk, SSID:23302770966
Installed Ubuntu 17.10.1 yesterday and can longer boot into USB or
CDROM. Cannot access BIOS(Phoenix) via F2.
Ubuntu boots fine and works.
I have followed the steps above, installing both kernel versions and the
BIOS has NOT recovered. I
Asked for the 16.10 drivers from Intel and they are on it's way.
https://01.org/comment/2783
Hopefully this will fix some of the issues we are facing with this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lars 2010 F pulseaudio
/dev/snd/controlC0: lars 2010 F pulseaudio
CurrentDesktop: Unity
Date: Sun Jul 10
4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lars 2010 F pulseaudio
/dev/snd/controlC0: lars 2010 F pulseaudio
CurrentDesktop: Unity
-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lars 2010 F pulseaudio
Still have the issue on 4.8.0-25-generic with Asus Z170 motherboard and
dualscreen HDMI.
--
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/1553503
Title:
multi monitors - black flashes or
4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lars 2010 F pulseaudio
/dev/snd/controlC0: lars 2010 F pulseaudio
CurrentDesktop: Unity
Date: Sun Jul 10 19:41:18
Hi, Interesting post. I do think this is the reason for many posts on
Blue-tooth issues regarding the Pro 5. I hope that you'll find the fix and that
it will then as well solve my bug post;
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608115
Br,
Lars
--
You received this bug
4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lars 2010 F pulseaudio
/dev/snd/controlC0: lars 2010 F pulseaudio
CurrentDesktop: Unity
Date: Sun Jul 10 19:41:18
Public bug reported:
Still the bluetooth aren't stable in the pro 5. Music interrupted when
playing on bluetooth speakers and the phone loses connection to keyboard
and mouse.
The same speaker, keyboard and mouse works well on the Bq units M10 and
e4.5
** Affects: bluez (Ubuntu)
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lars 2010 F pulseaudio
/dev/snd/controlC0: lars 2010 F pulseaudio
CurrentDesktop: Unity
Date: Sun Jul 10 19:41:18 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a45b9984-4de8-49e3-ba57
Done: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1600624
--
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/1575321
Title:
brcmfmac: Direct firmware load failed
Status in linux
16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lars 2010 F
I do have a wired icon regardless of connection type. However, it is
only the wired connection that actually works; disconnecting the cable
does not change the icon, but does remove connectivity altogether (so
there's a "wired-connection" icon even though networking is not
working).
It sounds
Additionally, the file mentioned in the error (brcmfmac43602-pcie.txt)
does not exist anywhere in the system.
--
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/1575321
Title:
brcmfmac:
I'm also seeing this issue. Trying with kernel 4.6.0 does not solve the
issue for me:
$ dmesg | grep brcm
[ 23.745801] usbcore: registered new interface driver brcmfmac
[ 23.865470] brcmfmac :03:00.0: Direct firmware load for
brcm/brcmfmac43602-pcie.txt failed with error -2
[
Tested proposed kernel 4.4.0-22.38 for xenial, does not solve the
virtualbox-bug. Virtualbox package is 5.0.18-dfsg-2build1, kernel module
won't load with error message "modprobe: ERROR: could not insert
'vboxdrv': Required key not available".
--
You received this bug notification because you
Public bug reported:
My system locks up several times a week. There is nothing that I know
of that can trigger it, it happens whether I use one monitor or two.
The symptom is that the applications windows become unresponsive, then
eventually also the mouse pointer, then eventually even the
Tested with v4.6-rc1-wily
(4.6.0-040600rc1_4.6.0-040600rc1.201603261930_amd64), bug is resolved
there.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
System fails to enter suspend mode on ubuntu 16.04 LTS (beta2) - did
work on ubuntu 14.04 LTS.
Events:
* closing the laptop lid, or
* calling `sudo pm-hibernate` via terminal
Effect:
* Screen goes black
* System stays on, but no commands are acknowledged (mouse, keyboard,
4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
I have the same issue and it comes every 2-5 minutes
Jan 23 11:56:59 zhakal kernel: [ 212.683811] WARNING: CPU: 6 PID: 1446 at
/build/linux-NgsOGa/linux-4.2.0/drivers/gpu/drm/i915/intel_pm.c:3404
Public bug reported:
After cleaning boot partition
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-50-generic 3.16.0-50.67~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
Uname: Linux 3.16.0-50-generic x86_64
ApportVersion:
One way to reproduce the bug: In LibreOffice, mark text across several
text types (e.g. "standard" and "Headline"). In Kubuntu only LibreOffice
freezes,in Ubuntu the entire desktop freezes.
Rafaels solution worked for me as well, afrer i reboot.
--
You received this bug notification because you
I now have tested both drivers nvidia sets the cpu freq to 3,4 GHz and
uses much more power. Intel has micro freezes in dmesg this shows up
perf interrupt took too long (2514 2500), lowering
kernel.perf_event_max_sample_rate to 5
i dont know if someone knows a trick so that i can use my
-21-generic x86_64
- ApportVersion: 2.17.2-0ubuntu1.1
- Architecture: amd64
- AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: lars 1994 F pulseaudio
- /dev/snd/controlC0: lars 1994 F pulseaudio
- CurrentDesktop: KDE
- Date: Mon Jul 6 16:18:50 2015
ok found a solution :D
it seems that i have done something wrong when i removed bumblebee.
Working Configuration is Nvidia-Prime with driver Nvidia-346.
then i switched the Prime Configuration profile trough nvidia-settings
to intel - reboot.
Now it works
(but i like to test it a few hours to
** Description changed:
Laptop Lenovo Y50-70
(Kubuntu)
Description:Ubuntu 15.04
Release:15.04
Linux L 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Xorg freezes (i think so because kill Xorg helps).
There are 2
** Description changed:
Laptop Lenovo Y50-70
(Kubuntu)
Description:Ubuntu 15.04
Release:15.04
Linux L 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Xorg freezes (i think so because kill Xorg helps).
There are 2
** Description changed:
Laptop Lenovo Y50-70
(Kubuntu)
Description:Ubuntu 15.04
Release:15.04
Linux L 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Xorg freezes.
- There are 2 GPU's in the laptop . No matter
Public bug reported:
Computer freezes at random. Nothing special being done. Can be opening a
browser, a libreoffice document.
Has happened more and more since 14.04 version.
This is the output from the kern.log
Jun 1 19:17:17 zhakal kernel: [96835.300207] BUG: unable to handle kernel NULL
** Tags added: kernel-unable-to-test-upstream
** 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/1460743
Title:
BUG:
cdrom dip lpadmin plugdev sambashare sudo
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lars 4065 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID
1 - 100 of 264 matches
Mail list logo
