Hi Steve, Julian, Łukasz, everyone,
Sorry that I didn't test the package on time – my life circumstances
have significantly changed since I reported this bug, nowadays I don't
have enough free time to do as much testing as I did back in the day.
I've been using the workaround ever since then, retu
Sorry, I didn't actually test Focal and Groovy.
Xenial will be supported for about a year, so I think it worth to fix it
there as well; however it's relative what worth to fix and what not, as
most users probably left Xenial behind already or applied a workaround
if they were ever affected by this
Public bug reported:
Unclear whether to report it against kexec-tools or systemd.
After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the
following error message:
Cannot find the ESP partition mount point.
What's interesting is that strace shows that systemctl tries to find the
Public bug reported:
My computer running Ubuntu Yakkety with 32 bit 4.8.0-41-generic kernel
often locks up. Error messages like this appear in syslog:
Mar 10 09:49:22 ReThinkCentre kernel: [47896.075600] NMI watchdog: BUG:
soft lockup - CPU#0 stuck for 23s! [kswapd0:38]
In later mainline kernels
Thanks for the workaround! It seems adding raid1 is enough.
--
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/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Stat
Public bug reported:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
https://www.redhat.com/archives/linux-lvm/2014-Nov
** 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/1396213
Title:
LVM VG is not activated during system boot
Status in “
I can't run apport-collect because Lynx doesn't send HTTP referrer to
Launchpad, and I don't wish to go through the ordeal of finding out how
to change this behaviour.
Furthermore, I'm not sure what logs would be collected. I can provide
logs you need manually, if you ask for them.
--
You receiv
I've generated the report and I'm trying to use what the linked tutorial
suggests:
$ ubuntu-bug -c 1396213.apport -u 1396213
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
ubuntu-bug: error: -u/--update-bug option cannot be used together with
options for a new
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268367/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268372/+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: "Card1.Codecs.codec97.0.ac97.0.0.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268365/+files/Card1.Codecs.codec97.0.ac97.0.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268375/+files/UdevLog.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/1396
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268376/+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/1396213/+attachment/4268369/+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/1396213
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268374/+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/1396213
apport information
** Tags added: apport-collected
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268371/+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: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268370/+files/PciMultimedia.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: "Card1.Codecs.codec97.0.ac97.0.0.regs.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268366/+files/Card1.Codecs.codec97.0.ac97.0.0.regs.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268368/+files/IwConfig.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/13
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268373/+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: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268364/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4268363/+files/BootDmesg.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/
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
https://www.redhat.com/archives/linux
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.18-rc6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1396213
Title:
LVM VG is not activated during system boot
S
I experience the same symptoms with the mainline kernel.
Note, if the problem is really with initrd scripts, then probably the
kernel version doesn't matter much. On the other hand, as I see, lvm2
initrd scripts haven't changed since Trusty, which would suggest it's a
kernel bug, after all. Hard t
lease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: megabrut
apport information
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
https://www.redha
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269735/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269738/+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/1396213/+attachment/4269739/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269741/+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/1396213
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269742/+files/UdevLog.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/1396
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269737/+files/PciMultimedia.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/1396213/+attachment/4269743/+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: "Card1.Codecs.codec97.0.ac97.0.0.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269733/+files/Card1.Codecs.codec97.0.ac97.0.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269740/+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: "Card1.Codecs.codec97.0.ac97.0.0.regs.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269734/+files/Card1.Codecs.codec97.0.ac97.0.0.regs.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269732/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269736/+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/1396213
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1396213/+attachment/4269731/+files/BootDmesg.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/
ersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
- USER PID ACCESS COMMAND
- /dev/snd/controlC0: megabrutal 2497 F pulseaudio
- /dev/snd/seq:timidity 1420 F timidity
+ USER PID ACCESS COMMAND
+ /dev/snd/controlC0: megabrutal 2497 F...
Yeah, I was in hurry and didn't have the time to give you the reason why
I did this.
I sent the latest apport from a kernel with which I don't experience the
issue. The difference is that I see these messages:
[5.527952] bio: create slab at 1
[ 151.415509] bio: create slab at 2
[ 161.7178
sion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: megabrutal 2497 F pulseaudio
/dev/snd/seq:timidity 1420 F timidity
Date: Thu Nov 27 07:40:07 2014
HibernationDevice: RESUME=UUID=3d113c6f-7cf
Signature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: megabrutal 2497 F pulseaudio
/dev/snd/seq:timidity 1420 F.
6.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: megabrutal 2497 F pulseaudio
/dev/snd/seq:ti
Reported upstream to BTRFS developers:
https://bugzilla.kernel.org/show_bug.cgi?id=89121
** Bug watch added: Linux Kernel Bug Tracker #89121
http://bugzilla.kernel.org/show_bug.cgi?id=89121
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I've had a backup of my old Trusty system, and I've built an initrd for
3.16.0-23-generic in that environment. With that initrd, the kernel
booted properly. Note, still it takes several minutes for the VG to
activate, but it eventually comes up if the kernel waits enough with
"rootdelay=300".
Now,
I've tested with 3.18.0-031800rc5-generic amd64. I experience the same.
** Tags added: kernel-bug-exists-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/1391429
Title:
grub-prob
I've built a system to reproduce the bug. You can download the image and
run it with KVM or other virtualization technology. Instructions are
straightforward – if you start the VM, you'll know what to do, and
you'll see what I was talking about.
http://undead.megabrutal.com/kvm-reproduce-1391429.i
Public bug reported:
I'm experiencing with Vivid Vervet on a virtual machine and tried a new
LVM feature, lvmcache. I made a cache for the root file system, rebuilt
the initrd and rebooted the VM.
At boot time, the system failed to activate the root LV. After some
investigation, I found out, it's
This is an lvm2 bug and I wanted to report it to lvm2, not Linux. I
remember that I exactly typed lvm2, I don't know why it was still
reported to linux. Could someone help me to sort it out?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
mType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS C
3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: megabrutal 2497 F pulseaudio
/dev/snd/seq:timidity 1420 F...
Now I have some more info about this. What actually makes the VG
activation so long is that I have a snapshot. Activating the snapshot
takes very long, and bringing up the entire VG takes about 5 minutes.
This wouldn't be such a big problem, as I could just patiently wait for
the activation (with r
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
With the knowledge that the hang is caused by snapshots, some googling has
brought up some duplicates:
https://bugs.launchpad.net/lvm2/+bug/360237
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645
It seems the issue was hanging around since 2009 or earlier.
In Trusty (or probably even e
Got an interesting reply from the Red Hat LVM mailing list:
https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html
Haven't tested the suggestion yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Turns out, the suggested --setactivationskip option is not present in
Utopic, as Utopic comes with an LVM version which dates back to 2012
(2.02.98(2) (2012-10-15)), while the feature was implemented in 2013.
Vivid will come with a newer LVM: 2.02.111(2) (2014-09-01).
Activation skip could be a n
@Astara:
> Now, I've noticed when I am booting, it *does* take a bit of time to mount
> bring up and mount all of the lvs, but you can the root mount is NOT
> in an VG/LV -- It's on a "regular device" (numbers on left are w/kernel time
> printing turned on -- so they are in seconds after boot):
>
>
ug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
6.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: megabrutal 2497 F pulseaudio
/dev/snd/seq:timidity 1420 F timidity
Date: Thu Nov 27 07:40:07 2014
HibernationDevice: RES
ture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: megabrutal 2497 F pulseaudio
/dev/snd/seq:timidity 1420 F timidity
Date: Thu Nov 27 07:40:07 2014
HibernationDevice: RESUME=UUID=3d113c6f-7cf8-477f-81e1-857aa62102c2
InstallationDat
Public bug reported:
After upgrading to Wily, raid1 LVs don't activate during the initrd
phase. Since the root LV is also RAID1-mirrored, the system doesn't
boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fin
I can't collect logs on non-booting system.
** 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/1509717
Title:
Wily LVM-R
** Tags added: regression-release wily
--
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/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status in initramfs-tools
Reproducible: upgraded another Ubuntu installation in VM and got the same
result.
Since the bug prevents booting, I suggest to increase priority to High.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
68 matches
Mail list logo
