[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1247647
Title:
Kernel oops during btrfs access
Status in “linux” pack
Thanks for testing. The bug may have been introduced in 3.9 or maybe
one of the 3.10 rc kernels. Can you test the following kernels:
v3.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy/
v3.10-rc1: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.10-rc1-saucy/
v3.10-rc5: http:
Strange, i get the same problem with both kernels.
Nov 5 08:12:31 ubuntunas kernel: [ 18.506379] [ cut here
]
Nov 5 08:12:31 ubuntunas kernel: [ 18.507390] Kernel BUG at a014f0d2
[verbose debug info unavailable]
Nov 5 08:12:31 ubuntunas kernel: [ 18.50875
To start a bisect, we first need to identify the last good kernel
version and first bad kernel version. Can you test the following two
kernels:
v3.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/
v3.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/
They can
I will try. Didn't do kernel tweaks for a long time.
Mit freundlichen Grüßen
Gregor Suhr
On Mon, Nov 4, 2013 at 9:20 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> We can perform a kernel bisect to try and identify the commit that
> introduced this regression. Would you be a
We can perform a kernel bisect to try and identify the commit that
introduced this regression. Would you be able to install some test
kernels on this machine?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Hi this problem started after the update 13.10 and 3.11.0-11.17-generic see
report Bug #1235798.
The last working kernel was 3.11.0.7.9
Tell me if an can provide further debug info...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when this regression was introduced.
If this is a regre
9 matches
Mail list logo
