Bug 15476 - kernel hangs/freeze till key press event acpi=noirq helps
Summary: kernel hangs/freeze till key press event acpi=noirq helps
Status: CLOSED DUPLICATE of bug 15289
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-08 08:42 UTC by daniel schroeder
Modified: 2010-03-17 16:55 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.32.8
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
my kernel config (56.48 KB, text/plain)
2010-03-08 08:43 UTC, daniel schroeder
Details

Description daniel schroeder 2010-03-08 08:42:38 UTC
beginning with 2.6.32.8 and therefor 2.6.33 and 2.6.33-git14 (pre 2.6.34) shows this annoying regression. 2.6.32.7 works fine.
Attached is the .7 .config any help is appreciated. No time/knowledge to do a git bisect between 32.7 and 32.8.
Comment 1 daniel schroeder 2010-03-08 08:43:53 UTC
Created attachment 25405 [details]
my kernel config
Comment 2 daniel schroeder 2010-03-08 08:46:38 UTC
some specs:
AMD 770 chipset, Athlon II X4 605e, AMD64 arch, rv710 radeonhd4550, using KMS
Comment 3 daniel schroeder 2010-03-08 08:50:19 UTC
more detailed problem description: kernel boots into initramfs, ask for cryptsetup password, boots further and at an arbitrary position kernel freeze/io freeze/everything freeze if i then press any key the kernel continues to boot for one or two seconds and again i have to press a key and so on...
Comment 4 daniel schroeder 2010-03-09 06:16:44 UTC
hmmm...overlooked the other one...duplicate of 
#15289
Comment 5 daniel schroeder 2010-03-09 06:17:40 UTC

*** This bug has been marked as a duplicate of bug 15289 ***
Comment 6 herrmann.der.user 2010-03-16 08:06:02 UTC
Do you also have a Gigabyte mainboard?
What's the model number and which BIOS version do you have installed?
Comment 7 daniel schroeder 2010-03-16 19:29:46 UTC
Yepp, Gigabyte MA770T-UD3P Revision 1.0 with Bios version F5 (2009/11/18)

Note You need to log in before you can comment on or make changes to this bug.