apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802614/+files/UdevDb.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/1655437
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802611/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802612/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802608/+files/CurrentDmesg.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
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802607/+files/CRDA.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/1655437
Ti
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802615/+files/WifiSyslog.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/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802610/+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/1655437
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802613/+files/ProcModules.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/b
apport information
** Tags added: apport-collected xenial
** Description changed:
During ENIC driver development on our end, there was a mistake and the
driver was built on the 4.4.0-22-generic kernel but we intended it to be
on the inbox kernel with 16.04 which is 4.4.0-21-generic. So whe
I ran apport-collect after booting up with the 4.4.0-21-generic kernel.
I was not able to boot into the OS with the 4.4.0-22-generic kernel to
run the command.
When boot fails and it drops to shell, it doesn't appear to be accepting
keyboard input. I found some old issues with USB drivers not bein
Thanks Joseph, it's working fine. We can close this out, I don't see a
point in pushing to get this specific kernel issue with 4.4.0-22
resolved by Canonical. I'll work with my manager to get the bug closed
out on our end internally.
Should I set this to won't fix or invalid?
--
You received thi
Public bug reported:
Opening this on behalf of one of my colleagues at Cisco, we're seeing an
issue on our new S-series S3260 server that's causing the kernel to
crash.
If we have an NVMe device inserted into one of two drive slots, we will
see kernel crash only with Ubuntu. With an NVMe drive in
I've asked the engineer to try the latest v4.10-rc6 kernel. This is
their first test with 16.04.1, so unknown if it works with previous
kernel version. I've asked them to check older versions to see if it
exists.
I'll update the tag and comment when I hear back from them. Thanks for
the recommenda
The mainline kernel seems to have resolved the issue so far. We're
running some IO just to make sure it's stable. I will update the tag
once we have confirmation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Tags added: kernel-fixed-upstream
--
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/1661131
Title:
kernel crash when NVMe drive inserted in one slot
Status in linux package in Ubuntu:
We tried with the 4.4.47 kernel but when booting it gives up waiting on
the root device. We are troubleshooting to try and get it to boot.
--
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/166
Hi Joseph,
To confirm, in order to correctly install the v4.4.47 kernel, we need to
do the git clone and apply the patches before installing the kernel .deb
packages correct? My colleague was only copying the .deb packages which
may be causing us to see the root device timeout. I was able to
succe
I was able to git clone the v4.4.47 kernel over to the machine having
issues. When trying to apply the patches after 0001, it's unable to
locate the file to patch for some. I am seeing this same error on
another machine I've previously successfully upgraded to the 4.4.47
kernel with the same files.
v4.4.47 kernel has the fix and is working with the NVMe drive in the
"bad" slot.
--
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/1661131
Title:
kernel crash when NVMe drive inserted in on
Kamal - to avoid confusion, the log files were uploaded based on the
4.2.0-35-generic kernel without the patches (re: Luis' request).
I'm getting to the updated 4.2.0-35-generic now (re: Kamal's request).
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609421/+files/Lsusb.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/1556562
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609419/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609426/+files/WifiSyslog.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/bug
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609422/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609425/+files/UdevDb.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/1556562
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609423/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609417/+files/CRDA.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/1556562
Ti
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609420/+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/1556562
apport information
** Tags added: apport-collected wily
** Description changed:
I'm working on an Lubuntu 15 machine. It was chosen because it supports
VIA C7-D processor and the VIA PM400 chipset without crashing (also see
). Lubuntu 15 uses the 4.2 kernel:
$ lsb_release -a
No
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609418/+files/CurrentDmesg.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
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1556562/+attachment/4609424/+files/ProcModules.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/b
Kamal - the updated kernel files cleared the issue. Thank you so much.
Dmesg shows only the following, which I believe is expected when
creating a socket with "AF_ALG" domain:
[ 806.458783] NET: Registered protocol family 38
--
You received this bug notification because you are a member of
I wanted to provide some feedback, if interested. Using Kamal's test
kernel and asynchronus test vectors from Taruk's GitHub
(https://github.com/tstruk/afalg_async_test)...
The SKCIPHER asynchronous test program passed.
However, the the AEAD asynchronous test program failed with:
$ cd aead
$
It looks like this is why the AEAD test is failing (if I am parsing
things correctly): http://patchwork.kernel.org/patch/8182971/. The
current kernel sources are missing struct aead_async_rsgl, struct
aead_async_req, et al.
Also, from comment 18: s/Taruk's GitHub/Tadeusz GitHub/g. I'm not sure
how
Public bug reported:
I installed the Xenial daily testing image dated 2-13-2016
(ttp://cdimage.ubuntu.com/lubuntu/daily-live/20160213/xenial-
desktop-i386.iso).
I'm booting the kernel with the following:
ipv6.disable=1 biosdevname=0 longhaul.enable=0 audit=0 quiet splash
However, eth0 is be
apport information
** Tags added: apport-collected xenial
** Description changed:
I installed the Xenial daily testing image dated 2-13-2016
(ttp://cdimage.ubuntu.com/lubuntu/daily-live/20160213/xenial-
desktop-i386.iso).
I'm booting the kernel with the following:
ipv6.disabl
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571545/+files/Lsusb.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/1545441
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571544/+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/1545441
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571546/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571551/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571543/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571549/+files/ProcModules.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/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571548/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571541/+files/CRDA.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/1545441
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571550/+files/UdevDb.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/1545441
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571542/+files/CurrentDmesg.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
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1545441/+attachment/4571547/+files/ProcEnviron.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/b
This issue is still present in Ubuntu Server, 14.03.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/839393
Title:
Network problem with the r8169 driver and RTL8111/8168B
Status in
>From Comment #48
(https://bugs.launchpad.net/linux/+bug/1488719/comments/48):
> If you don't want to downgrade your kernel: become root ('sudo su'),
> then open '/etc/default/grub' for edition (e.g. 'gedit /etc/default/grub'),
> then add the 'nomodeset' option to "GRUB_CMDLINE_LINUX_DEFAULT="
> (
>From Comment #124
(https://bugs.launchpad.net/linux/+bug/1488719/comments/124):
> ... I did this now for a lot of times (because setting the display
settings up again sucks)
I had luck with the following. It removed all of the dmesg's except one:
$ uname -a
Linux qotom 3.19.0-49-generic .
> Can you confirm that the Wily kernel (4.2.0-36.41)
> currently in -proposed fixes this bug? Thanks!
All looks good when installing the three packages from wily-proposed:
linux-headers-4.2.0-36-generic linux-image-4.2.0-36-generic
linux-image-extra-4.2.0-36-generic. The kernel did not deference
Hi Colin,
We ran into this at Cisco during 16.04 certification, Samantha asked me
to collect the data you requested to see if we can be of any help.
kernel versions:
Ubuntu 16.04: 4.4.0-21-generic
RHEL 7.2: 3.10.0-327.el7.x86_64
I've attached dmi_cisco.rar which will have a screenshot with dmide
Hi Adam, after enabling -proposed and installing the
dmidecode_3.0-2ubuntu0.1 package, it resolved the dmidecode issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1578022
Title:
I'm seeing this on i686 WIly and linux-image-4.2.0-35-generic:
[4.030019] clocksource: Switched to clocksource tsc
[4.034058] systemd[1]: Failed to insert module 'kdbus': Function not
implemented
[4.049880] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT
+SELINUX +IMA +A
Change to GDB.
It sure would be nice if someone took the time to fix Launchpad and its
broke package search. When looking up GDB, "Too many matches. Please try
to narrow your search" is a useless error message. It would be better to
give someone the damn result.
** Package changed: linux (Ubuntu)
Public bug reported:
I'm attempting to debug a C++ program in a debug configuration under
GDB. GDB seems to be having some trouble due to Python:
Catchpoint 1 (exception thrown), 0x77b348b0 in __cxa_throw ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) where
#0 0x77b348
Ubuntu 14.04 on Acer Aspire One D260
I got this bug when attempting to watch a video with totem.
Had previously encountered a vlc related bug (bug #1288206), attempted
to watch instead with totem and after a few seconds of playback, this
bug occured.
--
You received this bug notification becaus
http://ubuntuforums.org/archive/index.php/t-1387211.html
--
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/1213239
Title:
[Lenovo ThinkPad Twist] Bluetooth subsystem dies after suspend
Sta
Public bug reported:
Reference:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213239
This solution fixed the issue:
http://ubuntuforums.org/archive/index.php/t-1387211.html
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.25
ProcVersionSignatu
I filed the bug under
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280911
--
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/1213239
Title:
[Lenovo ThinkPad Twist] Bluetooth subsys
** Changed in: linux (Ubuntu)
Status: Expired => 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/1320022
Title:
[Dell Latitude E6540] ALPS touchpad keeps having state re
Øyvind, I experienced that when I upgraded to BIOS A10 from A08.
Fortunately, I was able to downgrade from A10 back to A08. I suspect
that either A10 has an issue or it just pokes even harder at this bug
than A08 did. (A10 cites "Keyboard input improvement" as one of its
fixes, which is probably
Public bug reported:
I just upgraded to Ubuntu Vivid. My Toshiba Satellite laptop has a
flicker with kernel 3.19. It had a screen flicker that began with 3.18
and was supposed to be cured with kernel 3.19 but evidently persists
with kernel 3.19
** Affects: linux (Ubuntu)
Importance: Undecide
Hi Joseph,
> Were you able to confirm this also happens with the Trusty daily image?
I've got some cycles and I can test it.
So I'm clear: there are only desktop builds; and not server builds,
which the bug report was written against. Do you still want the
testing to proceed?
If so, I will be us
Public bug reported:
I successively upgraded from 12.04 LTS to 12.10 to 13.04 to 13.10 on my
Asus EEE PC 1015PED, and upon booting, I saw "wifi disabled via hardware
switch" in the network-manager toolbar menu. rfkill list returned
4: brcmwl-0: Wireless LAN
Soft blocked: no
Hard b
Hello Christopher - yes, it was enabled before and not after. However,
as I've already completed the upgrade, I'm not confident that I can
provide helpful information on whether the 13.10 upgrade (or 13.04 or
12.10) cause this to happen again. While it's frustrating not to be able
to test the chang
> If verification is not done by 5 working days from today,
> this fix will be dropped from the source code, and this bug
> will be closed.
Forgive my ignorance, but how do I test the fix. Adding a repo does not
seem to apply since I fetch prebuilt ISO's from Ubuntu. That is,
"selective upgrading
This sync issue with the E7440 touchpad can cause spurious clicks too.
One thing that I found helps is to add psmouse.resetafter=1 to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (and then run update-
grub and reboot).
This will cause the driver to reset when it loses sync, causing the
touchpa
Allan, do the older kernels that don't seem to exhibit the bug recognize
the touchpad as a touchpad? For instance, with the older kernels that
don't seem to exhibit the bug, does the 'xinput' command list a generic
mouse instead of what's normally listed as your touchpad?
--
You received this bu
There's no actual regression though because, although the generic mouse
driver doesn't have the sync issue, using it is even worse since it
doesn't expose any touchpad-specific functionality.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I've been having this issue also. After a conversation in #ubuntu on
IRC, someone pointed out a script for /etc/pm/sleep.d
The script as shown below seems to have fixed this issue, although it is
(at least to me) a workaround.
Thanks
___
#!/bin/bash
#Code from http://
Further noteThe script seems to work for others also, not just
thinkpad.
--
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/1213239
Title:
[Lenovo ThinkPad Twist] Bluetooth subsystem die
Hi Joseph,
> http://cdimage.ubuntu.com/ubuntu-server/daily/current/
I can confirm the issue is still present with:
trusty-server-i386.iso
09-Nov-2013 06:52 668M
Server install image for PC (Intel x86) computers
Oddly, the first two screens (CD-Language and Install) do accept input
w
e:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1859 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 30 10:21:54 2015
HibernationDevice: RESUME=UUID=ec60eb80-b974-4fee-9d01-2ac7b77309fe
InstallationDate: Installed on 2014-09-19 (314 days ago)
InstallationMedia: Ubun
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1859 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 30 10:21:54 2015
PID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1859 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 30 10:21:54 2015
HibernationDevice: RESUME=UUID=ec60eb80-b974-4fee-9d01-2ac7b77309fe
InstallationDate: Installed on 2014-09-19 (314 days ago)
InstallationMedia: Ubuntu 1
Also see https://fosspost.org/fix-bluetooth-rtl8761b-problem-on-linux-
ubuntu-22-04/. From the article:
This happens because the rtl8761bu firmware is being requested, but the system
should have loaded the rtl8761b firmware, not the rtl8761bu one. The latter may
not even exist on your system.
This issue is still present in Ubuntu 20.04.3 LTS running the
5.4.0-81-generic kernel.
[0.725170] xhci_hcd :02:00.0: xHCI Host Controller
[0.725172] xhci_hcd :02:00.0: new USB bus registered, assigned bus
number 4
[0.725174] xhci_hcd :02:00.0: Host supports USB 3.1 Enhance
Hi Adam,
I believe there are different flickering bugs affecting different
processors at this time. Does the `intel_iommu=igfx_off` workaround
work for you? That would go toward understanding whether you are
affected by #2062951.
--
You received this bug notification because you are a member o
Despite some of the nondeterminism behind this bug, I believe I have
bisected this bug to the following commit in the Ubuntu kernel tree:
14ebfcacaeb07b02235f2ea881fd6e34e3de0d6f .
More info is available on this commit here:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unsta
> Thank you for doing your research into the issue but I am confused by
> your results.
>
> Are you claiming that removing mentioned Ubuntu specific commit resolves
> the issue?
Specifically it's the first commit where I experience the bug, so I
would assume that reverting it will resolve the iss
> model name : Intel(R) Core(TM) Ultra 7 155H
Hi Sean, this processor does not appear to have a Gen9 GPU. You are
likely experiencing another bug. You may consider opening a new bug
report.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
> And in this bug, we are trying to fix the flicker issue that can be worked
> around by intel_iommu=igfx_off
> I'll need your VGA PCI ID if intel_iommu=igfx_off works for you.
>lspci -nnk | grep -A3 VGA
$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation U
Please re-open this hardware bug. Thanks.
--
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/1220146
Title:
Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
Status in HWE
may i know will there be a permanent solution for this? thanks.
--
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/1846702
Title:
MEDIATEK Corp. MT7630e 802.11bgn does not work
Status in li
i get below when installing in 19.10
sudo apt-get install --install-recommends linux-generic-hwe-18.04
xserver-xorg-hwe-18.04
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-generic-hwe-18.04
E: Couldn't find any pa
I have the same issue with a Dell XPS 17 9700 when using 5.13.0-21.
5.13.0-20 works with a full power cycle.
--
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/1950515
Title:
WiFi Killer AX
The 'unavailability' of the wifi interface is apparently a path-
dependent bug in network manager or a related component. I was not able
to fix it in place, but a scratch reinstall of Kinetic fixed it. So it
can't be the kernel.
** Package changed: linux (Ubuntu) => network-manager (Ubuntu)
--
Y
Add an Acer Aspire 5 Laptop
(https://www.amazon.com/gp/product/B07RF1XD36) to the list of problem
platforms.
The machine was just upgraded to Linux Mint 20.2. Mint 20.1 was OK.
Linux Mint 20 is based on Ubuntu 20.04 LTS.
-
$ dmesg | grep -i error
[0.755376] RAS: Correctable Errors collec
*** This bug is a duplicate of bug 1938978 ***
https://bugs.launchpad.net/bugs/1938978
** This bug is no longer a duplicate of bug 1939254
nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
** This bug has been marked a duplicate of bug 1938978
nvidia-340 kern
Output of acpidump.
** Attachment added: "Output of acpidump."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809206/+attachment/5455179/+files/acpidump.txt.zip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
I'm still seeing this issue on Focal. The rub is, this is a new machine
- a Dell 8930 with fully updated firmware
(https://www.amazon.com/gp/product/B078N85NCR).
Here's part of dmesg:
...
[ 1217.951042] ACPI: Waking up from system sleep state S3
[ 1219.092307] ACPI BIOS Error (bug): AE_AML_BUFFER
This issue is still present today, on 5.4.0-153.170
Seems like the resolution is stalled. What can be done to get a fix out?
--
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/1950706
Title:
I'm also seeing failure to boot with -18 (-15 works) and I do not have
nvidia graphics, I have i915.
--
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/1991703
Title:
Failure to boot
This seems to be the relevant utterance of the kernel that fails to
boot:
i915 :00:02.0: vgaarb: deactivate vga console
BUG: kernel NULL pointer dereference, address: 002e
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 0 P4D 0
Oops: 0002
I don't know how to bring this to the attention of the relevant people,
but this is clearly a show-stopper. It renders most intel systems
unbootable. It's really unfortunate that a diff of this size was slipped
in moments before the kernel freeze. In my opinion having the system in
a non-working st
Public bug reported:
Since 5.19.0-16, which is also the kernel that broke booting on
11/12-gen Intel graphics, my Intel wifi is no longer working. This
continues with the present release candidate kernel package -21. The
wifi status reports simply that it is "unavailable" and no means to make
it "
Possibly this is a NM bug. I have no idea.
--
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/1993571
Title:
After 5.19.0-15, intel wifi 6 no longer available
Status in linux package in Ubu
4. Or per comment 73 your CPU/GPU is affected by this issue but is not
yet covered by the patch in 6.8.0-48? I'm hoping AceLan can chime in
concerning what hardware is covered by the patch and what is still
planned.
--
You received this bug notification because you are a member of Kernel
Package
The proposed kernel does not fix the issue for me, but maybe this is
expected? AceLan, does the workaround include Kaby Lake R CPUs yet?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/b
101 - 200 of 257 matches
Mail list logo
