*** This bug is a duplicate of bug 1743812 ***
https://bugs.launchpad.net/bugs/1743812
user@server2:~$ tail /sys/devices/system/cpu/vulnerabilities/*
==> /sys/devices/system/cpu/vulnerabilities/meltdown <==
Mitigation: PTI
==> /sys/devices/system/cpu/vulnerabilities/spectre_v1 <==
Mitigation:
: This occured during a previous suspend and prevented it from
resuming properly.
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lee1866 F pulseaudio
Date: Sun Oct 6 13:59:56 2013
ExecutablePath: /usr/share
So far, so good. And I added the tag to the bug as requested. At least, I
hope I added it right.
Thanks.
~Lee
sent using Debian Linux
http://www.debian.org/
On Mon, Oct 7, 2013 at 11:48 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Wo
Public bug reported:
Just doing a package update through synaptic and this one failed.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
Uname: Linux 5.10.17-051017-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5Chec
Public bug reported:
aster: Ubuntu desktop 20.04.6
Device: Advantech ARK-3534
Kernel: 5.15.0-67-generic x86_6
Steps to repro:
1. Execute Checkbox
2. View the Suspend Test
Failure symptom:
Attachments
suspend/1_xrandr_screens_after_suspend.tar.gz_auto
Failure rate:
100%
Note:
When using PCE-
** Changed in: linux-intel-iotg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2043079
Title:
[PCE-5033] suspend/1_xrandr_screens_after_
I tested this today using 5.0.0-8-generic and between reboots I am still
getting different MAC addresses on Z13.
--
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/1646805
Title:
MAC address
Public bug reported:
Clean install from just-downloaded (24 July 2019) xubuntu 18.04.2 LTS.
Shuttle XH110V. 32GB, 4T. UEFI.
Since it does not boot I can't give you anything from the crashed
system.
I attach a picture of the screen at the crash.
BTW, this started when the Software Updater inst
I should have mentioned that I had the install fetch updates while
installing. I'll try again without that.
--
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/1838050
Title:
Kernel panic at
If I try booting 4.18.0-15 it still crashes, but differently. Note that
4.18.0-15 is what's running on the live CD.
Attached is picture of screen booting from 4.18.0-15.
Next I'll try a reinstall without fetching updates.
** Attachment added: "y19m07d26_iphone-x_9602.jpg"
https://bugs.launc
Since I can't get any logs or anything, I've changed status to
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/1838050
Title:
Kernel panic at 4.8 sec into boot
Status in linux
I found a BIOS update, to 2.06, and flashed it.
Problem has gone away, at least for the new installation.
Sigh.
I marked the bug report invalid.
Thanks for your patience.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
Hi Kai-Heng,
First of all, I'm sorry for the late response..
and.. I may need to tell you that I'm just a user, not a developer.
It is hard to install new kernel for testing to me.
Also, I have no skill for GRUB bootloader.
I beg your pardon.
Thank you
--
You received this bug notification
** No longer affects: maas/2.7
--
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/1881821
Title:
MAAS does not properly detect max interface speed for interfaces which
use multiple phyisca
ity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee4054 F pulseaudio
/dev/snd/controlC1: lee4054 F pulseaudio
/dev/snd/controlC0: lee4054 F pu
You can see from that output that link speed is being reported as 2
while interface speed is reported as 1. MAAS does not allow the link
speed to exceed the interface speed which causes the failure. Given that
both LXD and ethtool show the same data this seems to be a kernel bug.
** Change
MAAS 2.7 introduced network testing. As part of network testing we added
the following features which require accurate interface and link speed
information.
1. The interface and uplink speeds are now shown in the API and over the UI.
2. MAAS now warns when an interface is connected to an uplink wh
Hi everyone,
I did upgrade kernel packages to 5.3.0-40 today and boot up with it.
Unfortunately, however, still nothing...
Thank you
--
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/186025
** Tags added: focal
--
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/1752251
Title:
Missing mcelog userspace package in bionic - or maybe linux kernel
config should disable mcelog_legac
I also had this problem. Touchpad stopped working after installation of Kernal
4.15.0-72, working fine after reverting to Kernal 4.15.0-70.
Kernal intstalled using linux mint update manager, and removed again with
update manager.
Although I occasionally use the terminal, I am an ex Windows user
** Tags added: eoan
--
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/1752251
Title:
Missing mcelog userspace package in bionic - or maybe linux kernel
config should disable mcelog_legacy
Hi everyone,
I did upgrade kernel packages to 5.3.0-28 yesterday and boot up with it.
Unfortunately, however, still nothing...
So, I switched back the kernel to 5.0.0-37.
In my thoughts, this is caused by entire 5.3.0 kernel...
Thank you
--
You received this bug notification because you are
Public bug reported:
I have a Lenovo X1 Carbon Extreme Gen 2. When I first installed Focal on
it battery status was working however its now stuck at 59% even though
its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
** Aff
h its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contr
n
though its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contr
h its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee
/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu15
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC2: lee4054 F pulseaudio
+ /dev/snd/controlC1: lee
though its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contr
n charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee
h its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee
h its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee
/dev/snd/controlC2: lee4054 F pulseaudio
/dev/snd/controlC1: lee4054 F pulseaudio
/dev/snd/controlC0: lee4054 F pulseaudio
/dev/snd/pcmC0D0p: lee4054 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
Instal
though its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contr
/controlC2: lee4054 F pulseaudio
/dev/snd/controlC1: lee4054 F pulseaudio
/dev/snd/controlC0: lee4054 F pulseaudio
/dev/snd/pcmC0D0p: lee4054 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: In
h its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee
h its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee
though its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/contr
h its been charging for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee
tus
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee4054 F pulseaudio
/dev/snd/controlC1: lee405
for days.
$ cat /sys/class/power_supply/BAT0/status
Unknown
$ cat /sys/class/power_supply/BAT0/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee4054 F pu
/capacity
59
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: lee4054 F pulseaudio
/dev/snd/controlC1: lee4054 F pulseaudio
/dev/snd/controlC0: lee4054
Public bug reported:
Hi, Ubuntu
First of all,
Ubuntu Version: 18.04.3 LTS
Kernel Version: linux-image-5.0.0-37-generic
H/W Info:
Processor - AMD Phenom II X3 720
Chipset - NVIDIA GeForce 8200
Package Repository: JAIST (JP)
Summary: A problem with Linux kernel linux-image-5.3.0-26-generic
T
Hi, Ubuntu
I did try to run the command as you told, but failed.
Because the command tried to open up a new browser window but didn't
work and got stuck.
I want to provide the logs to reproduce the symptom but, can't for that
reason.
Thank you
** Changed in: linux (Ubuntu)
Status: Inc
Public bug reported:
Each time that I use kodi, it allows me to sign in and get to the intro
screen,etc. It will start to play the video and then hang. I reboot and it
does the same thing. Ubuntu 16.04
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-64-generic
Public bug reported:
The MAAS CI has a PPC64 machine which is failing to boot into the
ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic
from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: I
Unable to run apport-collect as the error occurs while PXE booting the
kernel. A panic happens while loading the initrd and a shell is not
available.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Pack
This microcode forced update bricked my Samsung APU until I could flash
the bios back using DOS to a clear flag state. This should be down-
graded until better ucode tools are available. It fails on AMD-K1-1500
APU and AMD-A12 with Radeon ATI GPUs. I was forced to downgrade to
x32-bit machine just
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792929/+attachment/5189821/+files/dmesg
--
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/1792929
Public bug reported:
Reported as per https://wiki.ubuntu.com/DebuggingTouchpadDetection.
No touchpad listed in /proc/bus/input/devices after upgrading from
xubuntu 17.10 to xubuntu 18.04. No issues with touchpad prior to this.
** Affects: linux (Ubuntu)
Importance: Undecided
Status
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792929/+attachment/5189822/+files/Xorg.0.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/17929
I've tested the latest upstream kernels at http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.19-rc4 and have the same problem.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a m
In response to the previous question - this occurred after upgrading
xubuntu 17.10 to 18.04, previously the touchpad worked perfectly (and
therefore must've have been detected). I am afraid I do not know which
kernel version I was previously on.
--
You received this bug notification because you a
@kaihengfeng I am having a similar problem with a Lenovo ideapad 330.
Could I get access to the custom kernel you posted before? Those links
are dead.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Tags added: cosmic
--
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/1752251
Title:
Missing mcelog userspace package in bionic - or maybe linux kernel
config should disable mcelog_lega
** Tags added: disco
--
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/1752251
Title:
Missing mcelog userspace package in bionic - or maybe linux kernel
config should disable mcelog_legac
Public bug reported:
The latest nvidia update causes X.org to crash as soon as I try to login
with gdm. I can login to Wayland for a few minutes but it then crashes
as well. While going through dmesg I saw the following. It appears that
the crash is happening because I disabled UEFI secure boot. O
Good afternoon Paolo. It's been a while. I hope you and the team are
well.
How much extra enablement for the Snapdragon 835does 'snapdragon-edge'
contain?
My fear is that a lot of the most recent functionally patches have
either only just gone upstream, or are currently residing in -next. In
o
Public bug reported:
[ cut here ]
WARNING: CPU: 0 PID: 1012 at
/build/linux-pWDSBu/linux-3.13.0/include/drm/ttm/ttm_bo_driver.h:878
qxl_surface_id_alloc+0x37e/0x410 [qxl]()
Modules linked in: snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc
snd_seq_midi snd_s
** 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/1812889
Title:
WARNING: CPU: 0 PID: 1012 at /build/linux-
pWDSBu/lin
** Tags added: groovy
--
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/1752251
Title:
Missing mcelog userspace package in bionic - or maybe linux kernel
config should disable mcelog_lega
** Changed in: maas
Status: Fix Committed => Fix Released
--
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/1881821
Title:
MAAS does not properly detect max interface speed for inter
Last week we split the image stream hosted at images.maas.io into
candidate and stable. daily now redirects to stable. There have been no
changes to the images, only the label has been changed. lp:maas-images
only downloads the SquashFS from http://cloud-images.ubuntu.com/ and
pulls the kernel out
I have similar problems in 950XBE.
I tried
$sudo hda-verb /dev/snd/hwC0D0 0x1a SET_PIN_WIDGET_CONTROL 0xc5
but there's still no sound from the headphone.
Are the pins different for Samsung Notebook 9 Always?
!!DMI Information
!!---
Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
Pro
After changing alsa-base.config according to #6, headphones are working in
950XBE.
Attaching alsa-info with model=mono-speakers and headphones connected.
** Attachment added: "alsa-info in 950XBE"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404324/+files/alsa-in
That's correct.
For support, please go to: https://github.com/aarch64-laptops/build
--
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/1845347
Title:
Lenovo Yoga C630 not supported in Ubunt
Followed up on bug 1683105 . I've worked out the exact thing that needs
to be done.
--
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/1313169
Title:
Ubuntu Trusty Tahr cannot boot on RAID5
Public bug reported:
This is related to bug 1313169, I have had a sudden bout of clarity on
the cause of the issue.
I propose this modification to the dmraid installation script as it is a
small but necessary enhancement.
When dmraid is installed, it adds all the necessary hooks to initramfs-
to
Public bug reported:
[ cut here ]
WARNING: CPU: 0 PID: 0 at
/build/linux-1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92
mach_get_cmos_time+0x186/0x1a0()
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-64-generic #85-Ubuntu
0086 394369744a47151
Public bug reported:
[ cut here ]
WARNING: CPU: 0 PID: 1 at /build/linux-1hW8mg/linux-4.4.0/mm/page_alloc.c:3152
__alloc_pages_slowpath.constprop.88+0x9ed/0xad0()
Modules linked in: autofs4 raid10 raid456 async_raid6_recov async_memcpy
async_pq async_xor async_tx xor raid
Unable to run apport-collect.
** 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/1683510
Title:
WARNING: CPU: 0 PID: 0 a
Unable to run apport-collect.
** 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/1683509
Title:
WARNING: CPU: 0 PID: 1 a
Public bug reported:
The lirc package does not respond predictably to the 'sudo dpkg-
reconfigure lirc' command. When the command is run, the following
messages are displayed:
Warning: Stopping lircd.service, but it can still be activated by:
lircd.socket
Listing '/usr/lib/x86_64-linux-gnu/pyth
Public bug reported:
Please add bnxt_en_bpo to nic-modules to Ubuntu kernel 4.4.
bnxt_en_pbo has been available since SAUCE commits with 4.4.0-94.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: xenial
--
You received this bug notification because you are
The artful 4.13 kernel needs this upstream 4.13.14 patch.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.13.y&id=939f509d274541e32b1350ddc7f9d16d16617538
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
** 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/1734757
Title:
Add installer support for new Broadcom network drivers.
ubuntu 16.04,4.13.0-31-generic is now running on my ThinkPad x230.
I was writing my diary when the battery ran out. The indicator
told me (as usual) that my laptop is going to hibernate. When I plug
in the AC adapter and turned it on, I met this black screen and freeze
on resume.
At the same t
This bug has reappeared in 4.13.0-11.
** Changed in: linux (Ubuntu Artful)
Status: Fix Released => 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/1714112
Title:
EDAC sb
Public bug reported:
Please add bnxt_en to nic-modules to Ubuntu kernels 4.4 and later.
bnxt_en has been available since upstream Linux 4.4 commit
c0c050c58d840994ba842ad1c338a98e7c12b764 ("bnxt_en: New Broadcom
ethernet driver.").
** Affects: linux (Ubuntu)
Importance: Undecided
S
** 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/1720466
Title:
Add installer support for Broadcom BCM573xx network dri
Public bug reported:
Bionic kernel panics in the MAAS ephemeral environment. This does not
always happen during commissioning or testing but does happen every time
when trying to enter rescue mode. The test system is a KVM machine using
all VirtIO drivers running on a Bionic host system. Both syst
The kernel panic happens before I can access the system. The long log I
am able to pull is the console log which is attached.
** Tags removed: artful
** Tags added: bionic
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are
4.15-rc7 works with MAAS. I've commissioned, tested, and entered rescue
mode without hitting any kernel panics.
--
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/1742324
Title:
Bionic kerne
** Changed in: maas
Status: Triaged => Won't Fix
--
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/1742324
Title:
Bionic kernel panics in the MAAS ephemeral environment
Status in MA
Public bug reported:
CPU offlining can trigger hangs with HP ProLiant DL360p Gen8 on Ubuntu
17.10.
The hangs also occur with latest mainline kernel Linux 4.15-rc8.
I bisected the upstream mainline kernel. This is a regression introduced
by Linux 4.13-rc1 commit c5cb83bb337c25caae995d992d1cdf9b31
** 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/1744163
Title:
CPU offlining can trigger hangs with HP ProLiant DL360p
kernel: [ 242.381420] INFO: task kworker/u129:0:6 blocked for more than 120
seconds.
kernel: [ 242.417101] Not tainted 4.15.0-041500rc8-generic #201801142030
kernel: [ 242.447495] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
kernel: [ 242.482715] kworker/u12
Public bug reported:
Rehash of bug 1313169 / bug 1683105
My patch was ignored. As a result I am left with two unbootable boxes
after upgrade.
** Affects: dmraid (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Rehash of bug 1313169.
My patch was ignored.
Public bug reported:
[ cut here ]
WARNING: CPU: 13 PID: 0 at
/build/linux-0XAgc4/linux-4.4.0/net/ipv4/tcp_output.c:1145
tcp_fragment+0x34d/0x370()
Modules linked in: ip6table_filter ipip tunnel4 ip_tunnel cpuid 8021q garp mrp
stp llc ip6_tables binfmt_misc xt_comment nf_
Cannot run apport-collect.
** 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/1698241
Title:
WARNING: CPU: 13 PID: 0 at
This warning does not occur on the Ubuntu 4.8 kernel.
It might be fixed by upstream Linux 4.5 commit
d88270eef4b56bd7973841dd1fed387ccfa83709 "tcp: fix tcp_mark_head_lost to
check skb len before fragmenting".
https://github.com/torvalds/linux/commit/d88270eef4b56bd7973841dd1fed387ccfa83709
** Ta
Public bug reported:
I use the command "setxkbmap -layout us -option ctrl:swapcaps" to set
capslock as control.
Whenever I plug in any USB device or my docking station this gets
'reset' and I have to run the command again.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-
Public bug reported:
I recently upgraded to artful (xenial -> zesty -> artful).
Now when I plug in my docking station I see this[1] in syslog and no
network device appear.
The docking station is a ThinkPad OneLink+ Dock, my laptop a ThinkPad X1
Carbon 4th gen.
[1] http://pastebin.ubuntu.com/253
I installed the requested kernel[0] and the issue still renames. Tagging
as requested.
[0] $ uname -a
Linux Prodigal 4.13.0-041300rc6-generic #201708201831 SMP Sun Aug 20 22:32:57
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
I installed the requested kernel[0] and the issue still remains[1].
Tagging as requested.
[0] $ uname -a
Linux Prodigal 4.13.0-041300rc6-generic #201708201831 SMP Sun Aug 20 22:32:57
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[1] http://pastebin.ubuntu.com/25366599/
** Changed in: linux (Ubuntu)
@kaihengfeng, which kernel would that be? In grub I only see (taken from "dpkg
--list | grep linux-image | grep ii"):
- linux-image-4.12.0-11-generic
- linux-image-4.13.0-041300rc6-generic
I take it I would have to install a previous kernel to check this one
out?
--
You received this bug n
Public bug reported:
These kernel error messages appear with artful kernel 4.12.0-11-generic.
EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Failed to register device with error -22.
EDAC_GHES is enable in 4.12.0-11-generic, but according to
https:/
** 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/1714112
Title:
EDAC sbridge: Failed to register device with error -22.
** Tags added: xenial zesty
--
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/1708604
Title:
Backport recent bbr bugfixes to 4.10 kernel
Status in linux package in Ubuntu:
Opinion
Bug d
Please backport these tcp_bbr patches to ubuntu-zesty 4.10 kernel. These
patches have already landed in linux-stable kernels in 4.9.42 and
4.12.6.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
** Changed in: linux (Ubuntu)
Status: Opinion => 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/1708604
Title:
Backport recent bbr bugfixes to 4.10 kernel
Status in lin
1 - 100 of 1336 matches
Mail list logo
