Thanks Colin!
2016-02-16 19:20 GMT+01:00 Colin Ian King <1532...@bugs.launchpad.net>:
> I suggest a workaround for the moment, using aufs as the overlay to see
> if this helps.
>
> Modify the chroot config and set the union-type to aufs:
>
> union-type=aufs
>
> you may see an error like:
>
>
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=101951
Importance: Unknown
Status: Unknown
--
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/1532145
Title:
Same bug that I already had with another laptop, it seems to be related
to overlay and btrfs:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496438
Happens also on coreos:
https://github.com/coreos/rkt/issues/1498
Kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=101951
** Bug
output of lsblk:
http://paste.ubuntu.com/14468218/
--
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/1532145
Title:
Kernel Panic wrt btrfs while sbuild/schroot
Status in linux package in
I tried with the upstream v4.4-wily kernel.
kick@kick-gs60:~/work/merges/freeipmi$ uname -a
Linux kick-gs60 4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
I couldn't re-use my previous schroot (couldn't mount with overlayfs).
I've created
Public bug reported:
I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop.
I'm running btrfs on top of a bcached dmraid setup(intel software
raid0).
I can't use sbuild, cause it crashes.
I tried to use a schroot env, and when updating it I got it to crash
also.
All the keyboard/mouse/X11
Public bug reported:
The 7th of september I lost my Xorg display on wily. I was always in failsafe
mode.
I still could get openbox to run, which was still loading i915, but didn't
consume any 3D/advanced instruction I thinK.
I didn't got too much time to go beyond.
As I got also a btrfs
252:70 798M 0 crypt /home/kick/Secrets
Kernel traces:
[ 224.670454] BUG: unable to handle kernel NULL pointer dereference at
0334
[ 224.672387] IP: [] btrfs_sync_file+0xc1/0x360 [btrfs]
[ 224.674261] PGD 8451a067 PUD 84527067 PMD 0
[ 224.676056] Oops: 0002 [#1] PREEMPT
Yes you can get rid of bcache0, but you can't re-use the device for
anything unless you reboot ( re bcache or just plain fdisk/parted ).
In fact whether you unmount before stopping the bcache or not doesn't change
the behaviour. I did that this way in the description, to show the process.
You
Strange, I can reproduce each time, I'm using the iso:
ubuntu-14.10-beta2-desktop-amd64.iso from http://releases.ubuntu.com/utopic/
I'm on utopic, with vrit-manager.
Regards.
Le 08/10/2014 13:17, Stefan Bader a écrit :
+1 on the fail to reproduce. Followed the steps and everything worked
Yes you can get rid of bcache0, but you can't re-use the device for
anything unless you reboot ( re bcache or just plain fdisk/parted ).
Le 08/10/2014 13:15, Stefan Bader a écrit :
There does not seem to be clear documentation on this. Just a note that from
your description I was not
In fact whether you unmount before stopping the bcache or not doesn't
change the behaviour. I did that this way in the description, to show
the process. You just stop the caching device with the echo 1 ...
But, the backing is still in use, but you have no control over it.
Le 08/10/2014 13:15,
Thanks,
I didn't wrote to /sys/block/bcache0/bcache/stop, I missed this as I was
only looking in /dev/bcache* and in /sys/fs/bcache; which explains why I
was left with an used device.
I agree that the interface is not very user-fiendly, we may need to
improve the bcache-tools command to simplify
Public bug reported:
Hi,
I found a bug that crashes the machine if you create a bcache where the
caching device size is bigger than backing device.
This case may happen if you create a bcache with a plan to add a bigger
disk/partition/raid later to it.
To reproduce it follow this steps:
start
** Description changed:
If you create a bcache device, you can't reuse all your disk/partitions
without a reboot.
You can reproduce the case this way:
start a vm with 2 disks (caching must be bigger or equal to the backing
cf bug :1377130) and an iso of utopic desktop amd64
** Description changed:
Hi,
I found a bug that crashes the machine if you create a bcache where the
caching device size is bigger than backing device.
This case may happen if you create a bcache with a plan to add a bigger
disk/partition/raid later to it.
To reproduce it
Public bug reported:
If you create a bcache device, you can't reuse all your disk/partitions
without a reboot.
You can reproduce the case this way:
start a vm with 2 disks (caching must be bigger or equal to the backing
cf bug :1377130) and an iso of utopic desktop amd64
create the bcache
** Also affects: bcache-tools (Ubuntu)
Importance: Undecided
Status: New
--
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/1377130
Title:
Crash at creation of bcache if caching
** Package changed: linux-ports-meta (Ubuntu) = linux (Ubuntu)
--
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/1376661
Title:
Strange behaviour of ahci driver (intel 82801 Mobile SATA
: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
DistroRelease
: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: kick 3322 F pulseaudio
+ /dev/snd/controlC2: kick 3322 F pulseaudio
+ /dev/snd/controlC1: kick 3322 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.10
+ HibernationDevice
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop
: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
DistroRelease
: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
DistroRelease
: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
DistroRelease
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F pulseaudio
/dev/snd/controlC2: kick 3322 F pulseaudio
/dev/snd/controlC1: kick 3322 F pulseaudio
CurrentDesktop: Unity
DistroRelease
The virtual machine hangs some seconds after mount command of bcache
device.
--
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/1359146
Title:
Kernel crash when mounting bcache on a vm with
I've tested with upstream kernel, and I've got also an hang of the virtual
machine.
kernel tested is :
linux-image-3.17.0-031700rc1
--
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/1359146
At boot ime after crash I got:
http://paste.ubuntu.com/8106758/
trace begins at line 466
--
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/1359146
Title:
Kernel crash when mounting bcache
Public bug reported:
bcache used in a virtual machine:
If you create a bcache device with caching device and backing device on
virtio disks, it will let you do your work until you mount it where it
crashes the virtual machine (virtual machine is utopic, host is trusty).
For example:
if your
** Description changed:
bcache used in a virtual machine:
If you create a bcache device with caching device and backing device on
virtio disks, it will let you do your work until you mount it where it
crashes the virtual machine (virtual machine is utopic, host is trusty).
For
I'll try upstream kernel, and I will try previous release. Only utopic
kernel releases, or also trusty ones?
Le 20/08/2014 18:07, Joseph Salisbury a écrit :
Also, was there a prior release that did not exhibit this bug?
--
You received this bug notification because you are a member of Kernel
41 matches
Mail list logo
