I also have this problem using Asus P5N-E SLI motherboard. Hope it gets
sorted, subscribed this post.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791089
Title:
crash after rebooting or shutting
Mobo: P5N-D,
GFX: ATI Radeon HD 5670
Mem: 6GB
Kernel: ubuntu 3.0.0-13-generic-pae #22-Ubuntu SMP (Ubuntu 11.10 32)
As per this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089/comments/43
I blacklisted nv_tco and found the following:
No POST crashing on warm or cold start.
Far /far/
** Tags added: kernel-fixed-upstream-v3.2-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791089
Title:
crash after rebooting or shutting down from Ubuntu 11.04 11.10
To manage notifications
Mainline kernel 3.2-rc2 seems to fix this. It takes some time to pass the BIOS
bootlogo but I don't get any reboots for now.
Ubuntu 11.10 (64), Asus P5N-D, NVIDIA GTX 580.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
will do, because the solution I did with the fedora fix did give some
special behaviours.
When rebooting, no problem. When shutting down and afterwards booting windows
(dual boot) or even 11.10, my machine reboots while booting and I am having the
same press F1, there was a POST failure 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 . If possible, please test
the latest release candidate kernel (Not a kernel in the daily
directory). Once
** Summary changed:
- crash after rebooting or shutting down from Ubuntu 11.04
+ crash after rebooting or shutting down from Ubuntu 11.04 11.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791089
I give the hint in
http://forums.fedoraforum.org/showthread.php?p=1502068#post1502068 a
try... will see if I am still able to boot ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791089
Title:
worked!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791089
Title:
crash after rebooting or shutting down from Ubuntu 11.04 11.10
To manage notifications about this bug go to:
Made the above entry in the blacklist-watchdog on ubuntu 11.10 beta and:
kernel crash when rebooting.
Had to reinstall the kernel, because the system won't come up after
implementing the blacklist entry with initramfs... This is getting a serious
bug.
Still have to check if the same happens
The 'same' on ASUS motherboard with nForce 790i SLI chipset. This
command prevented sudden reboot after restarting or shutting down from
Ubuntu 11.04 as John previously described. Agreed that this is not a
solution of course, should to be a bug fix that resolve the problem in
core which cause it.
I have the same problem with an asus P5N32-E sli in kubuntu 11.04 and to
kubuntu 11.10. Yesterday i have upgrade to 11.10 and the problem still exist
with the new kernel 3.0.9
There is a same bug report here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/794702
--
You received this
Blacklisting the nv_tco module is not a good long-term solution.
A recent upstream commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=6b01d30eef64456ad9e261d2173266a3244da8e1
looks like it could be a fix for this issue.
Could somebody affected by this problem
Glad to hear this is working for everyone else! Personally I can't
think of a time that my system has locked hard and this watchdog would
have actually come in handy, most times I'd have hit the reset button
myself before waiting one minute for it to kick in. I guess it would be
useful for a
Superb John,
nv_tco added to blacklist reboot problem resolved. I do agree however
that this module would be better enabled - does need fixing first tho, I
imagine there is some risk not having this module enabled but a bigger
risk is hardware damage from these constant false boots IMHO.
Cheers
Wow, thanks John!!! I had lost all hope, but you are spot on I think.
I haven't tested thoroughly, but I have done a restart without a
spontaneous reboot!
gksudo gedit /etc/modprobe.d/blacklist.conf
add
blacklist nv_tco
I suppose these patches are related to this:
Any ideas how to reassign this bug to nv_tco?
When I search for it it doesn't find it, but it does find watchdog... Is that
the package that contains that module?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, is there a BIOS setting for the watchdog? I don't remember seeing
one.
In my case (Archlinux) this module comes with the kernel:
---
pacman -Qo ./modules/3.0-ARCH/kernel/drivers/watchdog/nv_tco.ko.gz
./modules/3.0-ARCH/kernel/drivers/watchdog/nv_tco.ko.gz is owned by linux
3.0.1-1
---
I
OK, I read everything over there and may post my question there too in
case it gets missed here.
One, does blacklisting this module cause any system changes, other
issues, missing *anything*, etc. I need to be aware of as I would hate
to solve (work around) one problem only to add some other
@John
Oh, is there a BIOS setting for the watchdog?
I'm not saying there is a BIOS option. I think the upon boot/restart, the BIOS
is supposed to disable the tco watchdog/timer.
@Arkangyl
I'm no expert on this but if you search about nvidia (or intel) TCO timers, you
will find this:
timeout
@Alex
Okay, yes I agree that the watchdog/timer should be reset on reboot;
it seems silly that it would remain enabled after the BIOS initializes.
A config option would be fine for clean reboots, but it persists even
after a hardware reset once it's been set up, so I think the best option
I've found the cause of this.
I looked at my loaded modules for anything nvidia-specific and the first
hit was nv_tco.
Looked at the source for this module (http://lxr.free-
electrons.com/source/drivers/watchdog/nv_tco.c) and it seems to handle
some hardware watchdog timer for Nvidia chipsets
I have the same problem with the same board, but I run ArchLinux. Since
it seems to also affect Ubuntu and Fedora
(http://forums.fedoraforum.org/showthread.php?p=1502068#post1502068), I
suspect a kernel or module issue.
I've thought I've had a funny hardware issue for months and tried
different
PS, my kernel is 2.6.39-ARCH and it's 64 bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791089
Title:
crash after rebooting or shutting down from Ubuntu 11.04
To manage notifications about
Minor update that might help track this down (I hope).
After shutting down (N/A to a reboot / restart), if you completely
remove power to your PSU via an on-off switch on it, etc., the computer
will not bios crash / double post on the next computer boot. I do not
know why of course, but it must
** Summary changed:
- unexpected reboot after rebooting or shutting down from Ubuntu 11.04
+ crash after rebooting or shutting down from Ubuntu 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
26 matches
Mail list logo
