aboutsummaryrefslogtreecommitdiff
path: root/scripts/mkuboot.sh
diff options
context:
space:
mode:
authorZoltan Devai <zdevai@gmail.com>2008-11-12 23:05:40 -0500
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2008-11-19 16:54:59 -0500
commit59bdb43769f2c3995badcd930d799451f5a39f76 (patch)
tree5cb629bf256532f9653b1bf0094a6c0cf3f0ff5a /scripts/mkuboot.sh
parent2ec6f246c33a0b830a6ad3171161e9d880e2251e (diff)
Input: pcspkr - fix PIT lockup on some chipsets
There've been reports [1] about the sysem bell causing a hard lockup. My machine was affected as well: any speaker output hung the machine completely, nothing in the logs, no magic sysrq, etc., looked like a hardware problem. Had a closer look on the issue, and it turned out that the pcspkr module is responsible. The cause is the bad setup of Timer 2 in the i8253 controller, which probably hangs the whole PIT controller. Intel datasheets [2] state that the timer registers are in an undefined state after reset and they need to be programmed before enabling the timer. (And enabling without programming the frequency first doesn't make sense anyway). I don't know which chipsets are affected (if not all), it also depends on the BIOS whether it initializes the timer (e.g. to beep when you start the machine). The following patch solved the issue on my ICH6 notebook, couldn't test it with any others, but should be safe to apply. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/146151 https://bugs.launchpad.net/ubuntu/+bug/270790 http://ubuntuforums.org/showthread.php?t=227693 http://bugs.gentoo.org/show_bug.cgi?id=222583 https://bugzilla.redhat.com/show_bug.cgi?id=454225 [2] http://www.intel.com/assets/pdf/datasheet/252516.pdf http://www.intel.com/assets/pdf/datasheet/301473.pdf http://www.intel.com/design/chipsets/datashts/29065503.pdf Signed-off-by: Zoltan Devai <zdevai@gmail.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Diffstat (limited to 'scripts/mkuboot.sh')
0 files changed, 0 insertions, 0 deletions