Latest working kernel version:184.108.40.206
Earliest failing kernel version: 2.6.25-rc1
Hardware Environment: NB Asus A6JC
2x Genuine Intel(R) CPU T2300 @ 1.66GHz
Software Environment: gcc 4.2.3
Kernel freezes during boot if AC is unplugged. I doesn't freeze every time but very often. It freezes after this two lines:
Apr 2 00:46:15 kedgecomp ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
Apr 2 00:46:15 kedgecomp ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
If I boot with debug parameter then it prints one more line and then freezes.
Apr 2 00:46:15 kedgecomp Switched to high resolution mode on CPU 1
If kernel is compiled without CONFIG_CPU_IDLE then it boots.
I've also tried to revert
or boot with processor.max_cstate=1 as Venkatesh Pallipadi suggested in bug 10093, but it didn't help
Also if it doesn't freeze during boot with unplugged AC then it often
freezes when Gentoo prints "Setting system clock using the hardware clock UTC"
the clock script uses "/sbin/hwclock"
Any suggestions how to fix it?
Created attachment 15556 [details]
Boot log when AC was plugged in
This entry is being used for tracking a regression from 2.6.24. Please don't
close it until the problem is fixed in the mainline.
Still freezes with 2.6.25-rc8-git3
can you get the log using a serial console? Or take a picture when the kernel freezes. :)
Created attachment 15643 [details]
Boot freeze screenshot
I don't have serial console so here's a screenshot.
This is with kernel 2.6.25-rc8-git5.
When running on AC, this system does not export C3.
eg. the dmesg shows
CPU0 (power states: C1[C1] C2[C2])
but when booting on DC, the screenshot shows that C3 is present.
This suggests that processor.max_cstate=2 is a good candidate
for a workaround. Please boot on DC with CONFIG_ACPI_PROCESSOR=y
(not =m) and this cmdline param and see if the hang goes away.
If it does, then CPU_IDLE's C3 code is implicated.
In any event, a hang in the device probe part of kernel boot
usually smells like an interrupt problem...
With CONFIG_CPU_IDLE=n, and CONFIG_ACPI_PROCESSOR=y,
please try processor.bm_history=0
to encourage use of C3 to see if the non CPU_IDLE code can hit this too.
the processor.max_cstate=2 didn't help it still freezes
With CONFIG_CPU_IDLE=n, and CONFIG_ACPI_PROCESSOR=y and processor.bm_history=0 it doesn't freeze when running on DC
After etc. 15 attempts I've managed to boot with 2.6.25-rc8-git5 without any parameters running on DC so I'll attach the boot log.
Created attachment 15713 [details]
2.6.25-rc8-git5 on DC
This is the log when 2.6.25-rc8-git5 didn't freeze on DC
Created attachment 15714 [details]
2.6.25-rc8-git5 on DC with CONFIG_CPU_IDLE=n
Log with CONFIG_CPU_IDLE=n, and CONFIG_ACPI_PROCESSOR=y and processor.bm_history=0 when running on DC
Created attachment 15715 [details]
2.6.25-rc8-git5 on AC
2.6.25-rc8-git5 on DC without any parameters
(In reply to comment #11)
> Created an attachment (id=15715) [details]
> 2.6.25-rc8-git5 on AC
> 2.6.25-rc8-git5 on DC without any parameters
Should be 2.6.25-rc8-git5 on AC without any parameters
Can you attach the .config you are using...
Created attachment 15725 [details]
Created attachment 15728 [details]
cpuidle test patch
Can you please try the attached patch and report back. If it hangs, picture of
last few messages will help.
Also, try using vga=6 boot option, which gives us more number of lines of text
on console (may need config changes with VIDEO_SELECT enabled).
Created attachment 15729 [details]
Boot log with patch
I've noticed that
PCI: Setting latency timer of device ...
ata_piix 0000:00:1f.1: version 2.12
lines are missing when the boot freezes when running on DC
It looks like the hpet=disable parameter has "fixed" the problem as Carlos R. Mafra suggested. (bug 10117)
dmesg logs are here http://kedge.wz.cz/kernel/
I've tried to bisect this and I think I found the commit that broke this.
I think it is:
Author: Rene Herman <firstname.lastname@example.org>
Date: Wed Jan 30 13:30:05 2008 +0100
x86: provide a DMI based port 0x80 I/O delay override.
The source files which are changed by this commit changed a lot so I didn't managed to revert only this patch. But the 4c6b8b4d62fb4cb843c32db71e0a8301039908f3 seems to work.
I've also tried to pass io_delay=0x80 and io_delay=0xed to 2.6.25-rc9 but it didn't help.
Ok I was wrong it still freezes but not very often it took 15 boots to freeze
Kernel also prints 3 more lines.
ata1.00: ATA-6: HTS541080G9AT00, MB4OA60A, max UDMA/100
ata1.00: 156301488 sectors, multi 16: LBA48
ata1.01: ATAPI: HL-DT-ST DVDRAM GMA-4082N, HJ02, max UDMA/33
(b02aae9cf52956dfe1bec73f77f81a3d05d3902b and newer commit shows the 3 lines too)
OK. These two bugs #10117 and #10377 are looking more and more alike. Markng them duplicate...
*** This bug has been marked as a duplicate of bug 10117 ***
This bug is not a duplicate of what was originally tracked in #10117.
Still freezes with 2.6.25 :(
does this still happen when booted with maxcpus=1?
does this still happen when booted with idle=poll?
It doesn't freeze with maxcpus=1 and idle=poll
I've tried 2.6.26-rc1 and 2.6.26-rc2 and both versions freeze "every time", even with AC plugged in.
I've also tried to get some debug info with nmi_watchdog=1 but it doesn't freeze with this parameter. I'm willing to debug this, but I need some help.
> I've tried 2.6.26-rc1 and 2.6.26-rc2 and both versions
>freeze "every time", even with AC plugged in.
does hpet=disable still fix all cases?
yes, hpet=disable does fix it.
btw. 2.6.26-rc3 freezes too
(In reply to comment #27)
> yes, hpet=disable does fix it.
> btw. 2.6.26-rc3 freezes too
you probably mean 2.6.26-rc3 freezes if no using hpet=disable here, right?
Does the problem still exists in the latest kernel?
(In reply to comment #24)
> It doesn't freeze with maxcpus=1 and idle=poll
idle=poll should workaround this issue.
does it freeze with maxcpus=1 only?
(In reply to comment #28)
> (In reply to comment #27)
> > yes, hpet=disable does fix it.
> > btw. 2.6.26-rc3 freezes too
> you probably mean 2.6.26-rc3 freezes if no using hpet=disable here, right?
> Does the problem still exists in the latest kernel?
> (In reply to comment #24)
> > It doesn't freeze with maxcpus=1 and idle=poll
> idle=poll should workaround this issue.
> does it freeze with maxcpus=1 only?
IIRC I've tested maxcpus=1 and idle=poll separately and it didn't freeze
so no it doesn't freeze with maxcpus=1 only.
Btw I can't test it right now because I got new laptop and
removed the system from old one, but if anybody is willing
to debug this with me I can install gentoo on the old laptop
can you please try a latest kerenel? There are a lot of time/c-state related fixes in recent kernel.
no response from the bug reporter.
Roman, please re-open it if the problem still exists in the latest kernel.