| 2006-10-21 03:32:51 |
Martin Visser |
bug |
|
|
added bug |
| 2006-10-21 03:34:35 |
Martin Visser |
description |
In edgy with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work.
4. Powerdown/restart with Power button does not recover problem
Workaround:
1. Once the problem occurs, the only way I can boot my computer is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
This laptop is new, and does not exhibit the problem when shutting down from running Windows XP. |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work.
4. Powerdown/restart with Power button does not recover problem
Workaround:
1. Once the problem occurs, the only way I can boot my computer is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
This laptop is new, and does not exhibit the problem when shutting down from running Windows XP. |
|
| 2006-10-21 03:48:50 |
Martin Visser |
description |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work.
4. Powerdown/restart with Power button does not recover problem
Workaround:
1. Once the problem occurs, the only way I can boot my computer is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
This laptop is new, and does not exhibit the problem when shutting down from running Windows XP. |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
3. The computer will appear to shutdown and power off normally.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work.
4. Powerdown/restart with Power button does not recover problem
Workaround:
1. Once the problem occurs, the only way I can boot my computer is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
This laptop is new, and does not exhibit the problem when shutting down from running Windows XP. |
|
| 2006-10-21 04:04:28 |
Martin Visser |
description |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
3. The computer will appear to shutdown and power off normally.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work.
4. Powerdown/restart with Power button does not recover problem
Workaround:
1. Once the problem occurs, the only way I can boot my computer is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
This laptop is new, and does not exhibit the problem when shutting down from running Windows XP. |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
3. The computer will appear to shutdown and power off normally.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. If you don't have a BIOS password configured then it will reach the Grub menu, but it does take about twice as long as normal.
4. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work before the OS has had a chance to start.
4. Powerdown/restart with Power button does not recover problem.
Workaround:
1. Once the problem occurs, the only way I can boot my computer and pass keystrokes to BIOS is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
Security Implications:
1. As I can now not have the computer prompt me for a BIOS password (without the incovenience of having to remove the battery before powering up) it means than my computer is less protected than I would otherwise like.
This laptop is new, and does not exhibit the problem when shutting down from running Windows XP. |
|
| 2006-10-21 04:04:28 |
Martin Visser |
title |
Clean shutdown prevents BIOS from restarting |
Clean shutdown prevents BIOS from accepting keystrokes |
|
| 2006-10-21 04:06:00 |
Martin Visser |
description |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
3. The computer will appear to shutdown and power off normally.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. If you don't have a BIOS password configured then it will reach the Grub menu, but it does take about twice as long as normal.
4. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work before the OS has had a chance to start.
4. Powerdown/restart with Power button does not recover problem.
Workaround:
1. Once the problem occurs, the only way I can boot my computer and pass keystrokes to BIOS is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
Security Implications:
1. As I can now not have the computer prompt me for a BIOS password (without the incovenience of having to remove the battery before powering up) it means than my computer is less protected than I would otherwise like.
This laptop is new, and does not exhibit the problem when shutting down from running Windows XP. |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
3. The computer will appear to shutdown and power off normally.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. If you don't have a BIOS password configured then it will reach the Grub menu, but it does take about twice as long as normal.
4. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work before the OS has had a chance to start.
4. Powerdown/restart with Power button does not recover problem.
Workaround:
1. Once the problem occurs, the only way I can boot my computer and pass keystrokes to BIOS is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
Security Implications:
1. As I can now not have the computer prompt me for a BIOS password (without the incovenience of having to remove the battery before powering up) it means than my computer is less protected than I would otherwise like.
Other notes:
1. This laptop is new, and does not exhibit the problem when shutting down from running Windows XP.
2. Before trying Edgy, I briefly installed Dapper (with updates). This also exhibited the same issue as Edgy. |
|
| 2006-10-24 20:14:50 |
AndyB |
description |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
3. The computer will appear to shutdown and power off normally.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. If you don't have a BIOS password configured then it will reach the Grub menu, but it does take about twice as long as normal.
4. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work before the OS has had a chance to start.
4. Powerdown/restart with Power button does not recover problem.
Workaround:
1. Once the problem occurs, the only way I can boot my computer and pass keystrokes to BIOS is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
Security Implications:
1. As I can now not have the computer prompt me for a BIOS password (without the incovenience of having to remove the battery before powering up) it means than my computer is less protected than I would otherwise like.
Other notes:
1. This laptop is new, and does not exhibit the problem when shutting down from running Windows XP.
2. Before trying Edgy, I briefly installed Dapper (with updates). This also exhibited the same issue as Edgy. |
Running Edgy Eft (6.10) with all updates as at Oct 21 2006. Kernel is 2.6.17-10.33.
System is HP Compaq nc6320 notebook. nx6325 is affected too.
To reproduce the problem:
1. Boot Ubuntu either in normal mode or single user mode.
2. Perform a standard clean shutdown.
3. The computer will appear to shutdown and power off normally.
Symptoms:
1. When you next power up the computer the BIOS seems to take approximately twice as long as normal to reach the stage where BIOS password is entered.
2. If you try to enter the password, the BIOS seems as if the it doesn't accept input from the keyboard. Also note that the preceeding F9 (for alternate boot device) or F10 (for setup) are also ignored.
3. If you don't have a BIOS password configured then it will reach the Grub menu, but it does take about twice as long as normal.
4. Also note however that Fn-F9 and Fn-F10 which provide hardware control of screen brightness does still work before the OS has had a chance to start.
4. Powerdown/restart with Power button does not recover problem.
Workaround:
1. Once the problem occurs, the only way I can boot my computer and pass keystrokes to BIOS is to remove plugpack power and to remove the LiIon battery for a few seconds. Restoring power then allows me to boot the computer normally.
Testing for Possible cause:
1. If rather than performing a clean Gnome shutdown or "shutdown - h now", I simply hold the power button down I can restart the computer normally. This would indicate that the shutdown process is leaving something in a state which prevents the BIOS from allowing the computer to restart.
2. When the computer tries to start BIOS after the clean shutdown it takes twice as long as normal. I am wondering whether some soft "firmware" is left in a state that prevents BIOS from properly initialising the hardware.
Security Implications:
1. As I can now not have the computer prompt me for a BIOS password (without the incovenience of having to remove the battery before powering up) it means than my computer is less protected than I would otherwise like.
Other notes:
1. This laptop is new, and does not exhibit the problem when shutting down from running Windows XP.
2. Before trying Edgy, I briefly installed Dapper (with updates). This also exhibited the same issue as Edgy. |
|
| 2006-11-28 21:07:55 |
Luc Stroobant |
None: status |
Unconfirmed |
Confirmed |
|
| 2006-11-28 21:07:55 |
Luc Stroobant |
None: statusexplanation |
|
|
|
| 2006-12-06 17:20:18 |
Luc Stroobant |
None: status |
Confirmed |
Fix Committed |
|
| 2006-12-06 20:08:15 |
Luc Stroobant |
None: status |
Fix Committed |
Confirmed |
|
| 2006-12-06 20:08:15 |
Luc Stroobant |
None: statusexplanation |
|
fixed by editing init-scripts -> sysvinit package. |
|
| 2006-12-07 10:34:08 |
Scott James Remnant (Canonical) |
sysvinit: statusexplanation |
fixed by editing init-scripts -> sysvinit package. |
This would be better off fixed in the kernel by finding out why psmouse being loaded breaks your machine so ... |
|
| 2006-12-16 17:01:32 |
Ben Collins |
linux-source-2.6.19: status |
Confirmed |
Needs Info |
|
| 2006-12-16 17:01:32 |
Ben Collins |
linux-source-2.6.19: statusexplanation |
This would be better off fixed in the kernel by finding out why psmouse being loaded breaks your machine so ... |
Please retest against 2.6.20-2 when it is available in the feisty archive. |
|
| 2007-01-02 19:57:55 |
Ben Collins |
linux-source-2.6.20: status |
Needs Info |
Rejected |
|
| 2007-01-02 19:57:55 |
Ben Collins |
linux-source-2.6.20: statusexplanation |
Please retest against 2.6.20-2 when it is available in the feisty archive. |
I'm still inclined to think this is a hardware problem. When the OS sends a shutdown signal the machine, and the machine acts on it (in this case, it actually shuts down), then I think everything after that is left to the hardware to handle.
The kernel shouldn't have to cleanup devices to get the hardware to shutdown properly. |
|
