Activity log for bug #218357

Date Who What changed Old value New value Message
2008-04-16 19:49:26 Simone Tolotti bug added bug
2008-04-27 18:10:49 Nikolay Belikov bug added attachment 'lspci' (lspci output)
2008-08-02 19:05:42 Jean-Baptiste Lallement None: status New Incomplete
2008-08-02 19:05:42 Jean-Baptiste Lallement None: bugtargetdisplayname Ubuntu linux (Ubuntu)
2008-08-02 19:05:42 Jean-Baptiste Lallement None: bugtargetname ubuntu linux (Ubuntu)
2008-08-02 19:05:42 Jean-Baptiste Lallement None: statusexplanation Thanks for your report. The iTCO_wdt error is due to module iTCO_wdt . This drivers should not be loaded automatically, but only if a watchdog daemon is installed. To get rid of this error at boot time add the line "blacklist iTCO_wdt" to /etc/modprobe.d/blacklist-watchdog I don't think this is causing the hanging issue. Can you try to blacklist this module and report here if it fixes the hanging issue or not. Thanks.
2008-08-02 19:05:42 Jean-Baptiste Lallement None: title Bug #218357 in Ubuntu: "[hardy] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware" Bug #218357 in linux (Ubuntu): "[hardy] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware"
2008-08-17 10:46:31 Jean-Baptiste Lallement linux: status Incomplete Invalid
2008-08-17 10:46:31 Jean-Baptiste Lallement linux: statusexplanation Thanks for your report. The iTCO_wdt error is due to module iTCO_wdt . This drivers should not be loaded automatically, but only if a watchdog daemon is installed. To get rid of this error at boot time add the line "blacklist iTCO_wdt" to /etc/modprobe.d/blacklist-watchdog I don't think this is causing the hanging issue. Can you try to blacklist this module and report here if it fixes the hanging issue or not. Thanks. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
2008-10-15 18:11:42 Carl Leitner bug added attachment 'term.log' (term.log)