This bug was fixed in the package linux - 3.13.0-16.36
---
linux (3.13.0-16.36) trusty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1287903
[ Andy Whitcroft ]
* Revert [Config] lowlatency -- turn CONFIG_IRQ_FORCED_THREADING_DEFAULT
off temporarily
I built a Trusty test kernel that has a cherry pick of commit
a1227f3c1030e96ebc51d677d2f636268845c5fb. This test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1275116/
Can you test this kernel and confirm it resolves this bug? I built an
i386 and amd_64 version of the
The following commit has landed in upstream v3.14-rc5:
commit a1227f3c1030e96ebc51d677d2f636268845c5fb
Author: Stanislaw Gruszka sgrus...@redhat.com
Date: Wed Feb 19 10:29:01 2014 +0100
usb: ehci: fix deadlock when threadirqs option is used
It has also been cc'd to stable, so it will make
** Also affects: linux (Ubuntu Trusty)
Importance: High
Status: Confirmed
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It would be good to know if when using the threadirqs parameter is a
regression. If that is the case, we can bisect to identify the commit
that introduced this.
Can you test the following kernels with the threadirqs parameter enabled
and post back if any do not exhibit the bug:
v3.2 final:
3 bootups with the 'GRUB_CMDLINE_LINUX_DEFAULT=' option
http://i.imgur.com/csOYLTT.jpg
thats always the moment when nothing happens anymore and i have to hard-reset
the computer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: csOYLTT.jpg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274987/+attachment/3977238/+files/csOYLTT.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Were you able to test the 3.13.2 kernel, which was posted in comment #9?
It would be good to know if the bug still exists with that kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
already done it in comment #10 (its the mainline part). i can boot up.
but what i had noticed, the computer freezes a little later while i
work, or browse the web.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Sandra, thanks for the update.
Can you follow the details in comment #3 of this bug and see if there is
additional debug info you can provide?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also, the upstream 3.13.2 kernel is now available. Can you test this
kernel to see if it still exhibits the bug? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.2-trusty/
--
You received this bug notification because you are a member of Kernel
Packages, which is
3.13.0-8-lowlatency with bootuption nothreadirqs works (i can boot it
up)
mainline lowlatency kernel (with ubuntu standard bootoptions) works too
(but shows many many apparmor errors)
removing the standard boot options on 3.13.0-8-lowlatency (#3) dont work
--
You received this bug notification
We would like to gather as much info as possible when the boot failure
happens. Comment #3 has a link on how to gather additional debug
information. We would like you to remove quiet splash and add debug
boot options. Then boot without the nothreadirqs option, to reproduce
the problem.
As
Is there some more generic way to get informations? because there are
lots of parameters and i think i need to set them all, but i dont have
the time to do this
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We are looking for any messages printed to the screen when the boot fails. To
see further debug info, you could edit the /etc/default/grub file and change
this line:
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
to this:
GRUB_CMDLINE_LINUX_DEFAULT=
Then run the following from a terminal:
sudo
Arrg :/ seems like yahoos imap dont work correctly. i didnt get any
notification, sorry
your Kernel works.
all other lowletency kernels of the 3.13 series dont boot up on the
optiplex, and EEEPC 1005h. not a single time. they just stop after a few
secounds on boot.
--
You received this bug
Can you follow the Boot options instructions on the following wiki to
enable additional output on boot:
https://wiki.ubuntu.com/DebuggingKernelBoot
As mentioned on the wiki, it would be great if you can attach a log file
which may have captured any messages you see. If you are unable to
capture
And just to confirm, like you mentioned in the description, the linux-
image-3.13.0-6-generic kernel does boot fine?
Also, I see the apport data indicates: Package: linux-
image-3.13.0-6-lowlatency 3.13.0-6.23. Does the kernel boot sometimes?
If not, does it boot on the OptiPlex 760 and not
In additional to answering the previous questions, could you also try to
boot with the following kernel boot option: nothreadirqs
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I built an amd64 lowlatency test kernel with PREEMPT disabled. This
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1275116/
Can you test this kernel and see if it also exhibits this bug? Please
note, this is a diagnostic kernel and not a fix.
Thanks in advance!
--
You
20 matches
Mail list logo
