Dell 210L randomly DOES NOT shutdown when issued a shutdown command.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
We have about 150 Dell 210L workstations running Ubuntu 6.10 at the school where I work.
Randomly (I can't find a significant variable), when shutting down, they will get to the point where Ubuntu is done closing down but instead of the power light turning off, it stays on and I can hear a fan either kick on or speed up significantly inside the box. Moreover, the only way to shut them down at this point is to hold in the power button until is does a complete power down (which ruins the possibility of remotely turning the workstation on).
I'd say this happens anywhere from 3%-10% of the time, regardless of how the computer is shut down (from the command-line, by pressing the power button, by sending it a remote shutdown command via iTALC).
When we send a shutdown command through iTALC to an entire classroom (30 workstation), there are always somewhere between one and three workstations that go into this strange seizure, but they are never the same workstations, and there does not seem to be a pattern to this behavior.
This is not an issue in the classrooms outfitted with Dell 170Ls.
Changed in linux-source-2.6.20: | |
assignee: | brian-murray → ubuntu-kernel-team |
status: | Needs Info → Confirmed |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/