Re: [rft] s2ram wakeup moves to .c, could fix few machines

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Pavel Machek <pavel@...>
Cc: Rafael J. Wysocki <rjw@...>, kernel list <linux-kernel@...>, Linux-pm mailing list <linux-pm@...>, H. Peter Anvin <hpa@...>
Date: Friday, February 8, 2008 - 5:41 pm

On Friday, 8 February 2008 23:13:46 Pavel Machek wrote:

Seriously, why not...
For decades BIOSes have used sound beeps to tell the user about a early problem
that happened have before video is initialized.

Maybe not a long messages using morse code, but at least
you can have several messages to tell the user about different problems in the boot code

like

two short beeps for an oops
1 short beep for normal resume (so the user will know that the video is to blame)

and so on.

I don't know morse code, but I probably would have learn it.
Once I had very nasty problem with resume, a hang, but only sometimes,
and I had to play with rtc to debug it, and still I couldn't figure out
what was wrong.

Fortunately, this problem disappeared (was somehow fixed).
For reference take a look at http://lkml.org/lkml/2007/3/17/155

I remember that I did about 1500 reboots to try to fix this.
(According to hard disk's 'smart' statistics)



Suggestion: the speaker usually is quite loud, thus it can be annoying to use
for morse code or so.
Why not to use keyboard leds for this purpose?
(USB keyboard probably isn't an option, but user can always pull an old PC keyboard
out of closet, and use it)


Best regards,
	Maxim Levitsky

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[rft] s2ram wakeup moves to .c, could fix few machines, Pavel Machek, (Tue Feb 5, 3:06 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Wed Feb 6, 7:37 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Tue Feb 5, 9:27 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Wed Feb 6, 7:48 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Thu Feb 7, 6:12 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Fri Feb 8, 6:01 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Fri Feb 8, 8:18 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Sat Feb 9, 9:48 am)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Thu Feb 7, 7:06 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Fri Feb 8, 12:23 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Thu Feb 7, 7:36 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Thu Feb 7, 6:57 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Thu Feb 7, 7:09 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Thu Feb 7, 6:40 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Maxim Levitsky, (Fri Feb 8, 5:41 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Thu Feb 7, 6:53 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Tue Feb 5, 9:42 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Bill Davidsen, (Wed Feb 13, 10:54 pm)
Re: [rft] s2ram wakeup moves to .c, could fix few machines, Rafael J. Wysocki, (Tue Feb 5, 9:56 pm)