[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155731
I built the next test kernel, up to the following commit:
fe6288e7e4d32cd184d264267bebdabc9a9c99c2
The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1155731
Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based
Crash/oops on first resume while reconeccting the keyboard with your
3.8.0-11.20 ...
Thanks,
J
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155731
Title:
Recurring kernel panic with khidp after
That is good news. So it sounds like this bug was introduced in the
3.8.0-11.20 kernel. I'll looks at the changelog. If nothing sticks
out, I'll kick off a bisect between 3.8.0-10.19 and 3.8.0-11.20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: ticket-spin-lock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155731
Title:
Recurring kernel panic with khidp after resume from S3 on a MacBook3,1
with a connected bluetooth
I started a kernel bisect between3.8.0-10.19 and 3.8.0-11.20 . The
kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
59188446b40179e6865606229c3726d11e905799
The test kernel can be downloaded from:
Preliminary results with v3.8.9-10.19:
Resume without kernel panic, but no reconnection to bluetooth keyboard.
Internal keyboard / external display etc. all work.
Attached kern.log has some info as well, which differs from previous logs.
** Attachment added: kern.log-3.8.0-10.19
So it sounds like 3.8.0-11.20 has this bug as well.
Can you next test the v3.8.9-10.19 build? We are trying to identify
last good kernel and the first bad kernel.
https://launchpad.net/ubuntu/+source/linux/3.8.0-10.19/+build/4343790
--
You received this bug notification because you are a
Can you test the 3.8.0-11.20 to see if it exhibits this bug? It can be
downloaded from:
https://launchpad.net/ubuntu/+source/linux/3.8.0-11.20/+build/4346872
You would need to install the linux-image and linux-image-extra
packages.
--
You received this bug notification because you are a
Just did a run with the aforementioned kernel 3.8.0-11.20 (though I am on i386,
but it was the same release).
The resulting Oops (ca. 1-2s after resume) is attached.
This time I came to X on my internal LVDS (the external monitor stuck in text
mode displaying the oops), and could still type
To start the bisect, we need to know the last good kernel and the first
bad kernel. Is the 3.8.0-12.21 kernel the first kernel to exhibit this
bug? Does this not happen with 3.8.0-11.20?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is a fresh install of 13.04, which had this problem from the very
beginning. If I remember correctly (and I'm quite positive that I do), this
worked correctly in 12.10.
There probably is some way for you to oversee the bluetooth/device related
patches and the releases with significant
Ubuntu kernel still crashing the system with todays update to 3.8.4
base.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155731
Title:
Recurring kernel panic with khidp after resume from S3 on a
Yes, can confirm that
3.8.3-030803-generic
gives no crash and enables the bluetooth keyboard over multiple suspend cycles
and that
linux-image-3.8.0-13-generic
(which came in as an update today) crashes on resume as well as previous ubuntu
kernels.
Thanks for looking into this!
--
You
Can you confirm this does not happen with the latest upstream 3.8 stable kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.3-raring/
If the bug does not exist in 3.8.3, then we can bisect and see which
Ubuntu SAUCE patch may have introduced this.
** Changed in: linux (Ubuntu)
Still happening with 3.8.0-13-generic ...
** Attachment added: from suspend/S3 over resume to panic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1155731/+attachment/3579640/+files/bluetooth-keyboard-panic-3.8.0-13
--
You received this bug notification because you are a member of
** Summary changed:
- Recurring kernel panic with khidp after resume from S3 on a MacBook3,1 with a
connected bluetooth keyboard kernel-fixed-upstream
+ Recurring kernel panic with khidp after resume from S3 on a MacBook3,1 with a
connected bluetooth keyboard
--
You received this bug
This is the log of the last panic from one system start to the final
panic with suspend/resume in between.
** Attachment added: Cut form kern.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1155731/+attachment/3576053/+files/kern-panic.log
--
You received this bug notification
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.9 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
Right after resume:
Mar 15 18:23:32 DeepWhite kernel: [ 219.591269] sysfs: cannot create duplicate
filename '/class/bluetooth/hci0:46'
This (hci0:46) is the bluetooth keyboard device on the MacBook.
Maybe this would need to get removed/disconnected etc. right before suspend, so
that no
Works with mainline kernel 3.9rc2, treid 5 suspends/resumes in a row
without a problem. As a positive side effect, the bluetooth keyboard
works after resume as well, which it doesn't with the ubuntu kernel.
** Summary changed:
- Recurring kernel panic with khidp after resume from S3 on a
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155731
Title:
Recurring kernel panic with khidp after resume from S3 on a MacBook3,1
with a connected bluetooth
Ok, tried again with mainline kernel 3.8.0.-030800, which works flawlessly as
well (as 3.9rc2). So the kernel panic seems to stem from the
differences/patches in between mainline and ubuntu-raring kernel 3.8.0.
Again, the official kernel gives a reliable panic every time I come back from
23 matches
Mail list logo
