[sparc] "General Fault" light lit at bootup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-source-2.6.15 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
| linux-source-2.6.17 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: linux-image-
This problem exists in edgy and dapper, as well as other Linux distributions like Aurora 1.0, 2.0 and CentOS 4.2. The host is a Sun Enterprise 250 (E250).
When Linux is booting, it attempts to probe the RTC. Only there is no RTC on an E250. I don't know if this is exactly the thing that the kernel is doing when the LED lights up, but it's the only thing that is spat out to the console at that time so it's my first hunch. I am sure that this host does not illuminate the General Fault light under non-Linux OS's such as Solaris 10 and OpenBSD 4.0 (tested both).
I have anecdotal confirmation that others with Enterprise-class server hardware get the same light upon bootup.
Normal behavior is for this light to blink some during IPL and then shut off unless there is a serious issue that requires operator attention. Thus it's a bit counterintuitive to have Linux turning this light on when nothing is wrong with the system.
| Cristian Aravena Romero (caravena) wrote | #1 |
| Cristian Aravena Romero (caravena) wrote | #2 |
| Changed in linux-source-2.6.17: | |
| status: | Unconfirmed → Needs Info |
| Changed in linux-source-2.6.15: | |
| status: | Unconfirmed → Needs Info |
| Changed in linux-source-2.6.15: | |
| assignee: | nobody → caravena |
| Changed in linux-source-2.6.17: | |
| assignee: | nobody → caravena |
| Fabio Massimo Di Nitto (fabbione) wrote | #3 |
| Changed in linux-source-2.6.17: | |
| status: | Needs Info → Confirmed |
| Changed in linux-source-2.6.15: | |
| status: | Needs Info → Confirmed |
| assignee: | caravena → fabbione |
| Changed in linux-source-2.6.17: | |
| assignee: | caravena → fabbione |
| woosht (woosht) wrote | #4 |
| Changed in linux-source-2.6.15: | |
| assignee: | fabbione → phillip-lougher |
| Changed in linux-source-2.6.17: | |
| assignee: | fabbione → phillip-lougher |
| Changed in linux-source-2.6.17: | |
| status: | Confirmed → Won't Fix |
| Changed in linux-source-2.6.15: | |
| status: | Confirmed → Won't Fix |
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.
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 "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available here: <http://