Recently upgraded to 13.10. Replaced Nvidia 560TI with new GTX 760 SC.
Replaced power supply.
x86_64. driver 319.32
Get the message after a few hours running boinc/seti calculations. system
continues running
and calculating, only a reboot restores the monitor from being blank to showing
Here is the start of the messages, this from syslog. The first such
messages
Nov 6 19:20:01 Dseti3 CRON[18475]: (root) CMD (if [ -x
/etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 /dev/null;
elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12
/dev/null;
Still happened although less frequent, recently upgraded to 13.10 with nVidia
331.13 and it started to happen again in the same frequency as from the
beginning.
Will contact Dell now since after some investigation this laptop seems to be
prone to GPU failure and since non of my other PC's, who
I agree with Joris V. they are starting to loose there reason for existence.
Please don't try to be what you despised in the first place!
Sadly I guess closing bug 1 unfortunately does reflect this new strategy...
But on the brighter side of things.
After investigating going to Debian I noticed
This occurs for me pretty much whenever I leave for awhile, come back, and
within first 30 seconds of returning (starting to use my computer again), X
will freeze. Only way to get out of it that I have found is using Alt + SysRq +
REISUB. Checking syslog after it boots again, I always have
John Murray, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug
Control team, and Ubuntu Bug Squad would like you to please file a new report
by executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more
no way... they even have standard messages now.
just create a new report and all will be fine! yeah...
Canonical seems to spread itself thin on various targeted markets, but
are neglecting their core business at the moment.
Haven't I heard that from another software company having gone the
Tested 13.10 beta 1 and this issue still happens quite frequently (325.15
driver), going to try Debian as suggested by Joris V.
I have used Ubuntu primarily since 8.04 but this is getting to much of a burden
and it doesn't seemed to be fixed upstream..
--
You received this bug notification
Hi Christopher,
Why does it need a new bug report when the issue resembles this one
exactly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986831
Title:
system freezes for some seconds: Attempted
M. van Workum, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug
Control team, and Ubuntu Bug Squad would like you to please file a new report
by executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more
Tried running: Linux Machine 3.9.0-030900rc8-generic #201304211835 SMP
Sun Apr 21 22:35:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux with the
nVidia 325.15 driver.
Still causing the issue.
Aug 27 22:33:42 Machine kernel: [ 2530.339582] NVRM: GPU at :01:00:
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.9.0-030900rc8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986831
Title:
system
Michael Mess, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
Unfortunately, working on the laptop detached from the bay didn't fix the
issue, still happening, but less frequent (once every hour).
Tried the newest 325.15 driver to no avail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@M. van Workum: This is getting to a point which makes my computer
unusable.
I know the feeling. Got similar instability problems with Ubuntu ever
since 12.04, rendering the computer unusable.
12.10 and 13.04 did not fix it.
Tried to escalate within Canonical on a few occasions, but all they
This is getting to a point which makes my computer unusable. It seems to happen
more and more.
I started working on 12:00 today and it happened to me over 17 times already!
Tried jtree's solutions which unfortunately doesn't work for me. Anyone?
--
You received this bug notification because
I'm using driver vestion 304.88 that comes with ubuntu 12.04 and
blacklisted all sensor modules.
On an old core 2 Q6600 with a Geforce GTX 480 this bugs dosn't appear more
and an i7-2600 with a Geforce GT 520 this bug appears once or twice a month.
2013/7/29 M. van Workum ubu...@2nv2u.com
This
Just installed the latest beta 325.08, resulting in the same behavior, it
happens to me once or twice every 20 minutes.
Detaching the laptop from the dock solves it though. Very strange...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
lsb_release -rd
Description:Ubuntu 12.04.2 LTS
cat /proc/version_signature
Ubuntu 3.2.0-49.75-generic-pae 3.2.46
32-bit mode
GPU:Nvidia Quadro 4000M, nvidia-current 304.88-0ubuntu0.0.2
In addition to the above mentioned NVRM: Xid ... and NVRM:
os_schedule:... messages, the following extra
@Rocko:
This could be the case, but it never happened to me before 12.10.
I'm using a Quadro FX 3800M and tried drivers 304.*, 310.*, 313.* and 319.* in
12.10 and 13.04 and this error happens quite frequently.
I did notice something that might be of interest. I'm using this laptop (Dell
Happened again, this time nothing but a terminal window and firefox
showing a google search result.
Jul 24 14:44:07 Machine kernel: [ 3585.132265] NVRM: GPU at :01:00:
GPU-9e2ddf6e-47c2-4331-d30f-b7adedcd90fc
Jul 24 14:44:07 Machine kernel: [ 3585.132269] NVRM: Xid (:01:00): 8,
Channel
Still happening regularly:
Jun 24 15:51:30 Machine kernel: [ 424.863708] NVRM: GPU at :01:00:
GPU-9e2ddf6e-47c2-4331-d30f-b7adedcd90fc
Jun 24 15:51:30 Machine kernel: [ 424.863711] NVRM: Xid (:01:00): 8,
Channel 0003
Jun 24 15:51:32 Machine kernel: [ 426.861668] NVRM:
@2nv2u: fwiw, I suspect my Xid errors and crashes were being caused by
poor quality nVidia hardware. I think the frequency of the errors did
drop with later nvidia drivers, but I didn't stop getting them
altogether until I tried a BIOS that reduced the voltage for 3d
operations to the nvidia card
I've got the same issue, completely locking up the computer sometimes, this
seems to be same issue as this one:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1132121
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Locking up again, this time running an OpenGL application, desktop did
not recover, did manage to get to tty1 and after login the music still
plays but returning to tty7 was not possible (black screen and music
stopped, switching back took some time, almost unresponsive), restarted
lightdm and
I am still getting
[31161.506308] NVRM: os_pci_init_handle: invalid context!
[31161.506313] NVRM: os_pci_init_handle: invalid context!
[31161.506324] NVRM: os_map_kernel_space: can't map 0xd000, invalid context!
[31161.506328] NVRM: os_pci_init_handle: invalid context!
[33531.507648] NVRM:
Did nvidia 304.37 fix this issue, as it seems to have done for some
people in bug #973096? Unfortunately it doesn't fix my nvidia card from
crashing when I use it to play 3d games under wine via bumblebee.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Today it hit me again when I was switching user.
I was logged in as one user, then pressed CTRL-ALT-L to lock the screen and
then switch user.
After logging in as second user everything was OK.
Then I switched back to the first user and then back to the second user and the
system was hanging
After installing the current updates, I have enabled tracing and tried to
reproduce the issue.
And the problem still exists.
I was able to reproduce the issue by switching users, this time the X11 system
got completely unusable (hanging) and there also was a Segfault in compiz.
After
When beeing logged in remotely I also vainly tried to regain access to
the console by killing the user processes and the X11 process and later
I found with top that there was a lightdm Zombie process which was using
98% CPU.
--
You received this bug notification because you are a member of
Thanks for the link.
Unfortunately I don't have a way to reproduce this bug, it just comes suddenly,
but in the last time it seems that this issue didn't hit me again, maybe this
has been fixed with one of the last kernel updates, maybe I didn't see it,
because I didn't spend much time in front
These bugs occur typically in an interrupt context. Do you have a way to
reproduce this bug? If so, there is a wiki page[0] that provides some
information on gathering more data specific to these type of bugs. If
possible can you review the wiki page and gather the additional data
listed on that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986831
Title:
system freezes for some seconds: Attempted to yield the CPU while in
atomic or interrupt context
To manage notifications about this bug
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986831
Title:
system freezes for some seconds: Attempted to yield the CPU while in
34 matches
Mail list logo
