I don't know if this is the same bug. The first excerpt from kern.log
didn't lock up the box but 2-3 minutes later X crashed with the bt
below:
Jul 1 21:30:38 tanghus kernel: [ 181.155905] virtuoso-t[2154] general
protection ip:8429e5c sp:b78831c0 error:0 in virtuoso-t[8048000+88d000]
Jul 1 21
** Tags added: kernel-uncat
** Tags removed: kernel-bug needs-upstream-testing
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I don't think this has been there before?:
Jun 20 17:18:13 tanghus kernel: [23632.437395] [ cut here
]
Jun 20 17:18:13 tanghus kernel: [23632.437458] kernel BUG at
/home/kernel-ppa/mainline/build/mm/slub.c:2846!
Jun 20 17:18:13 tanghus kernel: [23632.437526] invalid opcod
OK, great.
Just out of curiosity I have a few questions from which you can probably see
how totally blank I am about this ;-):
- I'm guessing this Oops's is handled upstream?
- Are they hardware specific (GPU)? Or driver; or both :-)
- Is soprano.so (partly?) responsible for this? The I'd guess i
Thank you, that should be all the information the developers should
need.
It seems three things are associated with the freezes:
1) The null pointer dereference kernel oops mentioned in the description, along
with most kern.log's.
2) The segfault in soprano.so (mentioned in Comment #31)
3) The GP
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
New crash on June 15th at ~07:29. I was listening to a radio stream in
Amarok with the monitor turned off. Had to do a power off. Nothing in
the logs at that time but I'll attach kern.log anywas as there are
several errors in it.
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net
New crash on June 12th at 16:15:41. I was listening to a radio stream
with Amarok and the monitor was suspended. I moved the mouse to wake it
up and a few seconds after it did X crashed and I was left with a
console unable to do anything. The funny is was that the stream kept
playing until I REISUB
Crash at June 12th 13:25.
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net/50182399/kern.log.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net/50103452/kern.log.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
New crash June 11th at 02:05:44. Attached kern.log and Xorg.0.log.old.
** Attachment added: "Xorg.0.log.old.txt"
http://launchpadlibrarian.net/50103449/Xorg.0.log.old.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification bec
New crash on June 10 at 22:46:48 with 2.6.34-020634-generic.
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net/50094123/kern.log.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member
New total crash on June 10th at 12:01:48. Only kern.log had anything
useful as I had to power off.
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net/50065279/kern.log.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug
New crash. The only thing I was able to get was from kern.log:
Jun 9 01:53:29 tanghus kernel: [ 552.593095] nepomukservices[2030]: segfault
at 7 ip b6221ca8 sp bffd7a30 error 4 in libsoprano.so
.4.3.0[b61dc000+ef000]
Jun 9 01:53:49 tanghus kernel: [ 572.402565] nepomukservices[2349]: segfault
** Attachment added: "dmesg.0.txt"
http://launchpadlibrarian.net/49981064/dmesg.0.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/49981047/dmesg.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Attachment added: "kern.log.1.txt"
http://launchpadlibrarian.net/49981042/kern.log.1.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net/49981038/kern.log.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
BTW: This was with 2.6.34 bc I couldn't even boot with 2.6.35rc1.
** Attachment added: "Xorg.0.log.txt"
http://launchpadlibrarian.net/49981034/Xorg.0.log.txt
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are
New crash at June 9th at 01:38. Only log I could get something from was
Xorg.0.old but it had bt.
X crashed and I was left at the terminal tried to get the state of
/sys/kernel/debug/dri/0/i915_error_state but the box totally froze before I had
a chance.
I'll attach the logs but I think only Xor
Please try the 2.6.35-rc1 kernel [1]. See if you can capture anything in
'/sys/kernel/debug/dri/0/i915_error_state' after a crash. If so, please
attach that file, along with the output of 'dmesg', /var/log/dmesg,
/var/log/dmesg.0 /var/log/kern.log, /var/log/Xorg.0.log, and
/var/log/Xorg.0.log.old.
Switch back to 2.6.32-22-generic because mainline crashed even more
often. Just had another crash but it only took down X. It is reported in
kern.log at 22:24:59.
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net/49841064/kern.log.txt
--
[865g] X locks up solid with HD thrashi
New crash. Could REISUB out of it but still nothing in kern.log, Xorg.0.log* or
anywhere I can think of. Any place else I should look?
I do get several errors like the one below in kern.log but they don't seem to
cause the crash:
Jun 5 07:50:52 tanghus kernel: [25896.712240] [drm:i915_handle_er
A short follow-up: I've been using the mainline kernel for 3 days now
and I've had 3 kernel crashes. No response on Caps-lock or Num-lock.
REISUB has no effect. No messages in kern.log at all.
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bu
Glad to be able to help :-)
I can see from your changes - and also realized it myself - that it's a kernel
bug rather than an X bug. I also checked Xorg.0.log.old but it had last been
touched at 18:03 so I figured it would be of any use. I'll attach it here
anyways.
For your other questions:
1
** Tags added: kernel-bug kernel-oops needs-upstream-testing
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Excellent, thank you. Mentioning the exact timestamp was very helpful.
Xorg.0.log won't have debugging information because it's the current log
for your rebooted session. To get the log of the previous session where
the freeze occurred, check Xorg.0.log.old. Check the timestamp in the
log (first e
** Description changed:
- System freezes apparently at random. kern.log at the time of a freeze:
+ System freezes apparently at random. kern.log at the time of a freeze is
+ below.
+
+ Compiz is disabled. MemTest ran for 6+ hours without an error.
===kern.log.txt (Comment #17)===
May 31 23
** Description changed:
- Binary package hint: xserver-xorg-video-intel
+ System freezes apparently at random. kern.log at the time of a freeze:
- X locks up randomly with the HD running full speed. Nothing to do but a hard
reset.
- Can't really provide any logs as they are reset on reboot.
+
Just had another crash at 23:56:49. Xorg.0.log shows nothing but I'll attach
kern.log.
Don't know if it was a coincidence or the trigger but I was trying out the new
fancy opendesktop.org integration in Amaroks About dialog.
** Attachment added: "kern.log.txt"
http://launchpadlibrarian.net/49
Ran memtest for +6 hrs and it passed with flying collars (spelling?) although
running VERY warm.
I've checked Xorg.0.log every time but it rarely shows anything.
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are
Also check your Xorg.0.log.old immediately after a crash for any
warnings or errors, and especially backtraces.
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Just had two crashes. One at 12:12 (noon. Dunno if it's am or pm?) from
which I had to do power-off to reboot and one at ~12:32 where I could
ALT-SysRq-s and ALT-SysRq-b to sync'n'reboot. Couldn't find anything in
any logs but I'll attach kern.log.
** Attachment added: "kern.log.txt"
http://lau
Also please run a MemTest (in the Grub menu, hold down Shift while
booting to get there). Let it run overnight; RAM tends to only show
symptoms of breakage once it's warmed up or under prolonged stress.
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You receiv
** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Will do. Thanks for helping.
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
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.ubun
There are at least three different kernel oopses, and most of them refer
to different processes.
Could you please keep track of the date/time of your next three crashes
and then upload the kern.log? This should give a definitive answer as to
which error messages are actually related to the crash.
It must have been around 14:00 (GMT+1) on the 27th. I'm not sure about
the time but the date is correct.
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you. That was very helpful. Can you also tell me the date and time
you disabled Compiz? It'd be nice to know where exactly in kern.log you
made that switch, since errors are everywhere, dating back to the 25th.
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585
So now I ran without Desktop Effects for ~24hrs and got a crash that didn't
lock up the PC. Xorg.0.log didn't show anything interesting but kern.log had
some good info which I'll attach.
Next step I'll try the mainline kernel as suggested. Should I just download the
*.deb files or could I add a
** Tags added: kubuntu
--
[865g] X locks up solid with HD thrashing
https://bugs.launchpad.net/bugs/585734
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.ubuntu.com
Do you have more than one dmesg in /var/log? I have dmesg and dmesg.0,
the latter of which is an old dmesg specifically for situations like
this. Old kern.log's and syslog's might also have interesting errors.
You could probably also SSH into your frozen computer, but I'm really no
expert at this.
Hi Stenten. Sorry I wasn't aware I didn't upload it as text but I guess it's
enough to give it a .txt extension?
I would have liked to attach dmesg output but as mentioned I wasn't able to
issue any commands until after reboot.
Just had another solid lockup where ALT-SysReq didn't even help.
--
43 matches
Mail list logo
