I'm still following this thread but the problem went away for me about a
year ago after I switched from Sidux to standard Debian (Sid).
What I did notice, when it was still happening, is that it always
occurred after I started X from a terminal with startx. Since Ubuntu
boots directly into Gnome I
I can confirm this still happens on 8.10 with 2.6.27-8-generic
--
Uhhuh. NMI received for unknown reason a0 on CPU 0
https://bugs.launchpad.net/bugs/116752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I also have a T60 running 24h/7d. From my experience, there seems to be
problems with various kernels at least up to 2.6.26 and Thinkpads and
the problems are not specific to Ubuntu. I do use fglrx (no beryl) and
crashes appear with a quiet blank screen. I nearly always get the NMI
crash after some
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I have recently been getting a similar message, except that it's b1 not
a0, when recovering from suspend to disk on a Thinkpad Z61M. This is on
Debian Sid (Sidux). It does not occur with Ubuntu 6.10 and I think,
though I'm not sure, that it does not happen if I don't have X running.
I don't think
Hi all,
I have an Acer Aspire 1802WSMI, 2Go RAM, ATI X600 Mobility, Wifi
(NDISWrapper), Pentium 4 HT 3.0GHz, Ubuntu Feisty.
I had the same problem; Although freezed (as described in previous
posts) sometimes the computer was still remotely (ssh...) accessible
sometimes not.
Though it did not ent
I got the same three lines today when my computer was idle. I had never
seen that before. This Thinkpad T60 has had ubuntu installed on it since
day 1, first with 6.10, now 7.04. I always ran XGL (I have an ATI card,
bleh) and beryl or compiz. The only thing that changed lately is that I
have had a
I forgot to mention that, like many people here, I also have the default
Atheros drivers from the Ubuntu repositories.
--
Uhhuh. NMI received for unknown reason a0 on CPU 0
https://bugs.launchpad.net/bugs/116752
You received this bug notification because you are a member of Ubuntu
Bugs, which is
PS: Of course, directly before the overruns was:
[221515.80] Uhhuh. NMI received for unknown reason b0 on CPU 0.
[221515.80] You have some hardware problem, likely on the PCI bus.
[221515.80] Dazed and confused, but trying to continue
--
Uhhuh. NMI received for unknown reason a0 on C
When I had the madwifi SVN drivers installed, some time after suspend (2
minutes? 3 days?) it would kill my wireless connection with:
[224591.06] wifi0: rx FIFO overrun; resetting
[224593.612000] wifi0: rx FIFO overrun; resetting
[224595.728000] wifi0: rx FIFO overrun; resetting
[224598.384000
Err, it says a different reason for the NMI:
PCI: Setting latency timer of device :00:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[:00:01.0:pcie00]
Allocate Port Service[:00:01.0:pcie03]
Uhhuh. NMI received for unknown reason b1 on CPU 0.
You have
Me too. Lenovo Thinkpad T43p. Tried with vanilla v2.6.22, v2.6.23-rc3. With
beryl+emerald.
It _looks_ like it is related to heavy graphics operations.
Xorg.0.log, messages, and the configs for both kernels attached.
** Attachment added: "X freezing on Thinkpad T43p"
http://launchpadlibrarian.
I had this happen for the only time this morning. Unlikely my
temperatures were that bad, I only have a puny Intel 945GM card in my
Thinkpad T60.
I'm also running madwifi svn since the ath_hal module which ships with
Feisty does not work with my AR5418 card. It does seem like the wireless
is relat
Um, I meant 80 deg.C. Sorry about that.
--
Uhhuh. NMI received for unknown reason a0 on CPU 0
https://bugs.launchpad.net/bugs/116752
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
This happened to me when I left my ThinkPad Z60m on the couch, raising
the GPU temperature to 80 deg.F. or so. This error was accompanied by
screen corruption. I'm keeping the machine off the couch and haven't
seen it since.
--
Uhhuh. NMI received for unknown reason a0 on CPU 0
https://bugs.launc
Answer 5537 seems to be relevant:
https://answers.launchpad.net/ubuntu/+question/5537
--
Uhhuh. NMI received for unknown reason a0 on CPU 0
https://bugs.launchpad.net/bugs/116752
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I have the same problem on my Thinkpad x60s. It's annoying, and happens
more than once a week. It may or may not be tied to the machine
freaking out about wireless & its ath0 card; both happen regularly and
seem to have a vague time connection.
SJ
--
Uhhuh. NMI received for unknown reason a0 o
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.20
--
Uhhuh. NMI received for unknown reason a0 on CPU 0
https://bugs.launchpad.net/bugs/116752
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
18 matches
Mail list logo
