I appear to be encountering this bug on 2.6.27-7. Pretty frequently,
certain applications hang, seemingly at random. I've been trying to keep
my eye on them in the System Monitor, and whenever it happens, the
waiting channel reports "futex_wait".
I have been searching a bit for a fix for this erro
Setting this to "Fix Released" based on the decision to stick with the
2.6.27 kernel for Intrepid - https://lists.ubuntu.com/archives/kernel-
team/2008-September/003107.html
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
.27 CPU#1 stuck for 113s! [events/1:10]
http
I cannot experience this anymore with 2.6.27-3.
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
** Tags added: fixed-2.6.27
** Tags removed: linux-2.6.27 regression-2.6.27
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I am marking this bug as fix committed since Intrepid has been rebased
to 2.6.27-rc6 which contains the fixes.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Fix Committed
Target: None => intrepid-alpha-6
--
.27 CPU#1 stuck for 113s! [events/
Your smb5 kernel build boots in a normal amount of time and seems to be
functioning well. I'm attaching the dmesg output.
** Attachment added: "dmesg from 2.6.27-3.3smb5 amd64 (no cpu stuck errors)"
http://launchpadlibrarian.net/17481461/dmesg
--
.27 CPU#1 stuck for 113s! [events/1:10]
https
I just put a amd64 bit version of the smb5 kernel online.
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
** Tags added: regression-2.6.27
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
I'm running the amd64 arch, so that kernel won't work here.
I can boot with "noapictimer", and also with "nohz=off highres=off
apci=debug debug". I'm attaching the dmesg from the latter boot
options. (highres=off did not work by itself, not did nohz=off )
Here are the contents of some other fil
@Marques,
your problem might be related to a bug found in the hpet code. That
should actually work with the kernel at
http://people.ubuntu.com/~smb/bug254668/linux-
image-2.6.27-3-generic_2.6.27-3.3smb2_i386.deb
There were also other problems in related places and I am currently
building a kernel
I already tried posting at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/254668 (ACPI hangs
on boot). I think my problem is the one described here in this bug.
"swapper" is getting hung for me as the original poster describes in his
dmesg log.
I booted with noapictimer and did not get the
Marques - Could you please report your issue in to a separate bug
report, as it is a different problem to the one decribed here.
Thanks
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "(x86_64) 2.6.26-5-generic dmesg (no cpu stuck issues)"
http://launchpadlibrarian.net/17239982/dmesg.2.gz
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I did not have this CPU stuck problem with 2.6.26-5, but I am seeing it
with 2.6.27-1 and 2.6.27-2.
I have tried this kernel on other systems and haven't seen this problem
(an older AMD 2200XP+ or on an 3ghz Intel P4-HT).
I'm attaching the dmesg output from 2.6.27-2 and 2.6.26-5 from my
AMDx2-64
I did not have this CPU stuck problem with 2.6.26-5, but I am seeing it
with 2.6.27-1 and 2.6.27-2.
I have tried this kernel on other systems and haven't seen this problem
(an older AMD 2200XP+ or on an 3ghz Intel P4-HT).
I'm attaching the dmesg output from 2.6.27-2 and 2.6.26-5 from my
AMDx2-64
Is there any NFS mount involved (since the first block seems to occur in
a network function and there has been a change upstream for that)?
Otherwise, does "noacpitimer" change something here?
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug
Hi Carl,
Can you comment if this existed with the 2.6.26 kernel or is this
specifically a regression from 2.6.26 to 2.6.27. You should be able to
test teh 2.6.26 kernel with the Alpha4 Intrepid release -
http://www.ubuntu.com/testing . Thanks.
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/17150298/lspci-vvnn.log
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please could you run the command "sudo lspci -vvnn > lspci-vvnn.log" and
attach the resulting file "lspci-vvnn.log" to this bug report.
Thanks in advance.
** Changed in: linux (Ubuntu)
Assignee: (unassigned)
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/17149123/dmidecode.txt
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/17149122/dmesg.txt
--
.27 CPU#1 stuck for 113s! [events/1:10]
https://bugs.launchpad.net/bugs/262437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
21 matches
Mail list logo
