The freezes still occure from time to time on my computer, although my kernel
is of 3.5 series.
The reports in kern.log are similar to the one in my post #33 above, though
they often are
truncated at some early position after the words Modules linked in
The system hangs without any response
I confirm that bug come from ATI/AMD drivers.
With generic drivers I can stop PC!
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP),
I think I have the same issue :
[ 77761.6005] WARNING : at /build/buildd/Linux-3.2.0/kernel/watchdog:241
watchdog-overflow-callback +0x9a/0xc0()
[ 77761.6005] Hardware name : System Product Name
[ 77761.6005] Watchdog detected hard LOCK on cpu 2
[ 77761.6005] Module linked in: btrfs
I have experienced apparently the same hang-up today with kernel 3.5.0-22 of
KUbuntu 12.10
I must note it happened previously from time to time, but I assumed this is
some hardware issue
until I looked in the linux logs.
The relevant part of the ``syslog'' file looks like:
Jan 21 17:33:27
Please reopen this bug since it does not seem fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP), warn_slowpath_common+0x7f in
sock_aio_read
To manage
Sorry, I had forgot about this one after it vanished and was only
reminded by a private email from someone suffering something similar.
I went through my collection of panic photos and (as my recollection
also was) there seem to have been none of this 'warn_slowpath_common'
kind since I last
Just to note here also that I've today switched to apw's build of
3.2.0-23 [1] linked to from bug 922906. I had been running the upstream
3.3 for more than 7 weeks without hitting this (#917668). The GPU lockup
I mentioned in #13 also never reoccurred since that one time.
I'll report back, should
Thanks for the update, Jani. Please mark this bug Fix released if you
no longer hit the bug with the new kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard
*** This bug is a duplicate of bug 922906 ***
https://bugs.launchpad.net/bugs/922906
In your latest dmesg output, I see the following:
RIP: 0010:[8103ec22] [8103ec22]
__ticket_spin_lock+0x22/0x30
This appears to be a duplicate of bug 922906
** This bug has been marked a
*** This bug is a duplicate of bug 922906 ***
https://bugs.launchpad.net/bugs/922906
Hi Joseph, are you sure they are related? The other bug appears to be
focused around removal of USB devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It could be that you are hitting both bugs. I will un-mark this as a
duplicate to further investigate.
** This bug is no longer a duplicate of bug 922906
Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
009c; EIP is at __ticket_spin_lock+0x8/0x30
--
You received
While stability is much better on 3.3.0, I did experience this same hard
lock today. The machine had been online for only a few hours. I ran
several days previously without issue though.
DMESG output after the crash is attached.
** Attachment added: kernelcrash-3.3.0.txt
** Changed in: linux (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP), warn_slowpath_common+0x7f in
I just got a hard lock with 3.2.13-030213-generic... I'm back on 3.3
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP), warn_slowpath_common+0x7f in
After 17 hours on 3.2.13-030213-generic I have had no issues. Whatever
the problem was I suspect it is fixed. If I have any further issues
with 3.2.13-030213 I'll report back.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP), warn_slowpath_common+0x7f in
I've been experiencing the same thing on my Lenovo W510. It has an
nVidia card as opposed to the Radeon above, but I've had the same
symptoms and the same type of dmesg errors listed. My dmesg is attached
below.
It got REALLY bad after the last Ubuntu kernel update (3.2.0-20.32) -
like the
@d3mia7, maybe you could try 3.3 too? FWIW, I haven't seen this since
installing 3.3.0-030300rc4-generic a month ago now. If your system's
prone to freeze this way, testing 3.3 could provide further evidence as
to whether the issue's fixed upstream.
--
You received this bug notification because
I tried 3.2.0-20.33 and it was just as bad as 3.2.0-20.32 - couldn't run
for more than an hour or so before I got a lockup.
I then went to 3.3.0-030300-generic (the released one as opposed to the
RC) and I haven't had an issue yet. Been over 2 hours now, though with
some of the earlier 3.2.0's I
Would it be possible to test the latest 3.2 upsteam stable kernel? That
kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.13-precise/
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you
@Joseph - sure thing. I've loaded up 3.2.13-030213-generic and will run
with it for a while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP),
@jsalisbury: Yeah, my Intel hardware's got its own set of problems. :)
I'll get back to doing tests on those later this week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system
Would it be possible for you to test with RC6 disabled?
To disable RC6, do the following:
Hold down Left-Shift key to enter the Grub menu on boot
Hit 'e' to edit the kernel command line
Append i915.i915_enable_rc6=0 as a kernel boot parameter
For example: linux /boot/vmlinuz-3.2.0-17-generic ...
This is a test for the GPU lockup you saw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP), warn_slowpath_common+0x7f in
sock_aio_read
To manage
Actually no need to test the RC6 option. It doesn't look like you have
Intel graphics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP),
I've just had a GPU lockup with 3.3.0-030300rc4-generic. Would this be
yet another issue (i.e. not this bug nor bug #938894)? If so, where (if
anywhere) should I file it? I'm pasting below here what was in syslog
about it.
Feb 26 19:53:38 saegusa kernel: [ 8031.040107] radeon :01:05.0: GPU
I think the bug has been fixed in 3.3-rc4, and the commit is below:
commit bced76aeaca03b45e3b4bdb868cada328e497847
Author: Peter Zijlstra a.p.zijls...@chello.nl
Date: Wed Jan 11 13:11:12 2012 +0100
sched: Fix lockup by limiting load-balance retries on lock-break
Bryce, so could you
@jsalisbury: Alright, thanks. I'm running 3.3.0-030300rc4-generic now.
Let's see how it works out!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP),
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It would be great if you could test with 3.3-rc4-precise. This could
also test if the issue in bug 938894 is resolved upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system
@jsalisbury: On this setup, there were seemingly similar freezes before
Precise (I was using Lucid until then), but being so far apart and
without a reliable recipe for reproducing, I mostly just ignored the
issue. To give a clue as to the rarity, an (again seemingly) similar
freeze happened just
While waiting for this to reoccur, now that I came to think of it: I
have radeon.audio=1 on my kernel parameters due to Bug #864735. Radeon
audio is considered too buggy by developers to be enabled by default, so
my force-enabling it definitely makes it a suspect here.
--
You received this bug
Do you know if this issue happened in previous version of Ubuntu, or is
this a new issue?
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
Alright, I will. Thanks Bryce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze (hard LOCKUP), warn_slowpath_common+0x7f in
sock_aio_read
To manage notifications about
While it may feel like an Xorg freeze, actually from your logs I'm not
seeing anything that indicates X is complicit. Retargeting to the
kernel.
sock_aio_read() sounds like it might be happening in some asynchronous
I/O. However, the dmesg you posted only starts at 19199 sec, so might
be
37 matches
Mail list logo
