snagged kernel-2.6.21-1.3201.fc7 from koji (hoping), but it hangs too, but in a
different spot:

...
ACPI: PCI Interrrupt ...
NET: Regestered protocol family 2
<hang>

Please try booting with kernel parameter

    sysrq_always_enabled

then try hitting alt-sysrq-p (hit "p" while holding down alt and sysrq)
when it locks up.

bummer, nothing visibily happens.  (keyboard seems dead, numlock, capslock don't
seem to function either  ???)

try booting with "maxcpus=0"

Happens on my Latitude D420 as well.

Jeremy's advice of booting with maxcpus=1 fixes the problem (which is a bit of a
bummer for a dual-core machine).

maxcpus=0
gets *much* further, now it seems to be getting stuck on ata stuff(?):

ata1.00: qc timeout (cmd 0x27)
...
ata1.00: failed to set xfermode (err_mask_0x4)
...
ata2.00: qc timeout (cmd 0xef)
...
ata1.00: failed to set xfermode (err_mask_0x4)
...
Loading ata_generic.ko module
...
mount: count not find filesystem '/dev/root'
...
switchroot: moun filed: No such file or directory
Booting has failed.
Kernel panic - not syncing: ...


will now try maxcpus=1

maxcpus=1
works nicely.

also on my d620 kernel 2.6.21-1.3194.fc7 hangs

with maxcpus=0
IOAPIC[0]: Invalid reference to IRQ 0 (5 same messages)
ata1.00: failed to set xfermode (err_mask=0x40) (3 same messages)
ata2.00: failed to set xfermode (err_mask=0x4) (3 same messages)
...
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: count not find filesystem '/dev/root'
setuproot: moving /dev/failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

with maxcpus=1 boots with no problem

One more data point for those keeping score:

My Dell Precision M65 laptop was working fine with
kernel-2.6.21-1.3189.fc7.i686.  Booting kernel-2.6.21-1.3194.fc7.i686 hangs
unless I set maxcpus=1.

-3191 is the last kernel to boot properly, -3194 hangs hard on boot. So it would
be one of those changes:
* Wed May 23 2007 Dave Jones <davej>
- Disable more debug options in the non-debug builds.

* Wed May 23 2007 Dave Jones <davej>
- Disable ub block driver.

* Wed May 23 2007 Dave Jones <davej>
- 2.6.21.2

The bottom one looks the more likely culprit...

*** Bug 241506 has been marked as a duplicate of this bug. ***

So, as per above duplicate, this affects (some) machines with Pentium Dual Core
CPUs too.

That's not too surprising, because the "Pentium" Dual Core is not a real 
Pentium, it's a stripped-down Core Duo, similar to how the Celerons were 
stripped-down Pentiums.

Yeah, the old marketing tricks kicked in there for Intel ;-)

Anyhow, I actually have another Dell Inspiron 6400, with "real" Core Duo this
time and that one doesn't hang (it did once, but not after that). Go figure...

Anyhow, the workaround of maxcpus=1 worked in the Pentium box. The other
suggested workaround, maxcpus=0, didn't. Something about APIC going nuts got
printed on the console.

Just had a second hang on the Core Duo notebook (Dell Inspiron 6400) and then a
successful boot straight after that.

Two new pieces of information:

- once current devel tree is installed (kernel 3194), the system consistently
hangs (i.e. no longer intermittently, like it did from the CD) on my Core Duo
Dell Inspiron 6400 (maxcpus=1 still works around it)

- the new kernel, just built in koji (3208), still hangs (the last message is
apm: no BIOS or something and then it locks up - with numlock on)

3207 locks up my Dell Precision M65 unless I have maxcpus=1, but 3208 boots fine
for me.

3208 worksforme too (dell latitude d620, bios revision a08)

3208 is also working on my latitude d620 Core Duo

Created attachment 155648 [details]
Screen shot of failure on Dell Inspiron 6400 with Core Duo CPU (kernel 3208)

The above screen shot is for kernel 3208.

Created attachment 155657 [details]
Screen shot of failure on Dell Inspiron 6400 with Core Duo CPU (kernel 3209)

Workaround with 3209 on Dell Inspiron 6400: clocksource=acpi_pm, as per:
http://lkml.org/lkml/2007/3/7/554

Created attachment 155660 [details]
Data obtained from Intel's Firmware Developer Kit, release 2

I'm not sure if this is useful to someone, but here it is nonetheless.

F7 Live RC2 CD boots on my other Inspiron 6400 with clocksource=acpi_pm. This is
kernel 3194. So, at least on this hardware, maxcpus=1 is not required.

There were patches to clocksource.[ch] in stable 2.6.21 series, so maybe that's
where the problem is.

Yep, the clocksource=acpi_pm works on my first Inspiron 6400 with 3194 kernel as
well.

(In reply to comment #26)
> Yep, the clocksource=acpi_pm works on my first Inspiron 6400 with 3194 kernel as
> well.

I would like to add that my Dell XPS 1210M with a T2500 CoreDuo chip also
exhibited this exact bug, and adding the "clocksource=acpi_pm" seems to make it
work again with both cores!

Is this the kernel that is on the Fedora 7 Live CD?  Because it will not boot my
dell d820 unless I add the maxcpus=1 to the boot line.

If it is, this really SUCKS for a new release.

Ok, the clocksource=acpi_pm works also.  This looks the the better way to boot
the livecd, rescue cd and the dvd.

*** Bug 241983 has been marked as a duplicate of this bug. ***

ntel Core Duo. Live CD did not boot. maxcpus=1 made it work. Then I installed
the PAE kernel version 3194 from repos since it had NX bit support. Now the
system boots without any trouble.

I have a D620 with a Core 2 Duo and it has the same problem, so it isn't just a
core duo problem. The clocksource parameter allows boot.

So, here is an added wrinkle to this one ... 3194 boots just fine for me on my
D620 *if* I'm docked.  Undocked, I worked around the freeze with "noacpi", but
will try the clocksource option...

Same problem with Dell Inspiron 9400 with a Centrino Duo T2400.  clocksource
allows the system to boot.

Same here, Dell Latitude D820. 
maxcpus=1 works. This machine is not a "real" Core 2 duo, its the old Core duo.

The in-progress kernel at http://people.redhat.com/davej/kernels/Fedora/fc7/ 
fixes this for some folks. It'd be good to know if it doesn't fix it for anyone
tracking this bug.

(In reply to comment #36)
> The in-progress kernel at http://people.redhat.com/davej/kernels/Fedora/fc7/ 
> fixes this for some folks. It'd be good to know if it doesn't fix it for anyone
> tracking this bug.

It did not fix it for my Dell XPS 1210M, CoreDuo T2500, A6 bios rev.

It hangs right after ACPI messages and says "checking if image is initramfs..."
then one last message of "Switched to high resolution mode on CPU 1"

Then dead hang, must power-cycle to reboot.

This kernel as well as the stock FC7 do work with "clocksource=acpi_pm" for me.

If you need more info, please feel free to ask.

Regarding comment #36, did you have a look at that clocksource patch in .2? Does
it look suspect?

kernel-2.6.21-1.3212.fc7.i686 still does not boot for me without the clocksource
line on my Inspiro 9400 (Centrino Duo T2400).

Can you please try with "hpet=disable" on the kernel command line ?

Thanks,
  tglx

Too bad, so sad. "hpet=disable" does not work.

*** Bug 242235 has been marked as a duplicate of this bug. ***

Dell Inspiron 9400, Intel Centrino Duo T5200

clocksource=acpi_pm works for me

Dell Dimension E150n, with Pentium D, same issue. None of the workarounds
presented here work. Stands still at "Ready" prompt. Unbootable.

(In reply to comment #44)
> Dell Dimension E150n, with Pentium D, same issue. None of the workarounds
> presented here work. Stands still at "Ready" prompt. Unbootable.

Sorry, correction, E510n. Pentium D 820 (Smithfield).

Updated via DVD image from FC6 completed, but hung at first boot;
delete and try the Fedora 7 DVD again from scratch, hangs at same point at first
boot...

  applied the "clocksource=acpi_pm" workaround to grub kernel line; clean boot
and made the change permanent to /boot/grub/grug.conf

So, update probably would have been salvagable; do not appear to need the
"maxcpus=1" with both cores fully functional

sf
=-=-=
Dell Inspiron E1705 (9400), Intel Core 2 Duo T7200
Intel 82891G
Mobile Intel 945GM/GU/PM/GMS/940GML/943GML and Intel 945GT
nVidia GeForce Go 7900 GS

*** Bug 242719 has been marked as a duplicate of this bug. ***

I have the same problem with an update of a Dell Latitude D620 with i386 install.
However, another D620 installed (not updated) in x86_64 works fine.
BTW, I also tried to upgrade from an i386 installation to an x86_64, and it
resulted in a mess...

*** Bug 242867 has been marked as a duplicate of this bug. ***

Don't know about others but I used clocksource=acpi_pm on my D620 and everything
is working great.

I had the same issue of my laptop not booting.  I have a Dell Inspiron E1705
Core Duo, and the xen kernel booting without any issues, but until I added
maxcpus=1, the standard kernel would not boot.

*** Bug 242096 has been marked as a duplicate of this bug. ***

clocksource=acpi_pm fixes the problem on my Dell Latitude D820 (Core 2 Duo).

I see a lot of "me too"s here, but nobody with any answers.  Has anyone figured
out what's causing this?

I think there was some discussion on LKML regarding this, related to the next
stable patch to 2.6.21. Hopefully, we'll see a fix soon.

BTW, latest builds of kernel in Koji
(http://koji.fedoraproject.org/koji/buildinfo?buildID=8524) may contain RCs of
the next stable patch. Maybe worth trying and reporting back. I haven't had a
chance yet...

clocksource=acpi_pm also works for me. 

Dell Precision M65, BIOS A08 (Core 2 Duo, T7200)

clocksource=acpi_pm also work for me.

Dell Latitude D420, BIOS A04 (Core 2 Duo, U2500)

clocksource=acpi_pm works for me.  Does this mean that I am not using the
tickless kernel?

Dell Precision M90 BIOS A06 (Core 2 Duo, T7400)

Kernel 3226 boots fine on both of my Inspiron 6400s, with no special options
related to this problem (I only have combined_mode=libata, for the performance
of DVD-RW).

Kernel 2.6.21-1.3226.fc7 works for me too; my Latitude D420 (Core Duo U2500)
didn't work with 3194.

(In reply to comment #46)

Updated today to .3228 from the DVD iso's .3194

Removed the clocksource kernel param from grub.conf, boots without issue.

So, believe the "clocksource=acpi_pm" workaround is no longer needed from .3226
foward as per #60 (Except of course for new install or reinstall from
distribution ISO).

sf

3228 works here.

I can also confirm that 3228 works here too.  It can boot without the
clocksource parameter.

3228 also works for me. on my dell d420

It would be great, when someone with an affected machine could test drive:

http://www.tglx.de/projects/hrtimers/2.6.22-rc4/patch-2.6.22-rc4-hrt10.patch

Thanks,

   tglx

Ok, my Dell Dimension E510 with dual core freezes no matter whether I use
maxcpu=1, maxcpu=0 or clocksource=acpi_pm...
What do I do next? Wait for FC8?

(In reply to comment #66)
> Ok, my Dell Dimension E510 with dual core freezes no matter whether I use
> maxcpu=1, maxcpu=0 or clocksource=acpi_pm...
> What do I do next? Wait for FC8?

that's "maxcpus"

sorry, typo in my mail, not in the boot trials...

Regarding comment #66, this is with the latest kernel, 3228, right?

This is from the default FC7 DVD, F-7-i386-DVD.iso. Forgive my lack of
knowledge, I just don't know how to update from FC6 to FC7 if I can't boot in
the first place. I expect the 3228 kernel to resolve the issue but how do I get
there? Any advice or links to documentation are highly welcome.

If you system is already running FC6, you can use "yum upgrade" to do this.
Install the fedora-release RPM from F7 (you will need to install both
fedora-release-7-3 and fedora-release-notes-7.0.0-1 packages) using RPM. Then
run yum upgrade. This should pick up the updates repository and install the
latest kernel (3228) for you. Anyhow, you should see that in your transaction
before agreeing to go ahead.

A word of caution - don't do this from an X session as your X may die during the
upgrade, which will leave you with a whole lot of duplicate packages. Better
drop to a text console and do it from there.

If you want to test a few more boot options, some of them are listed here:

http://fedoraproject.org/wiki/Fedora7/FAQ#head-1d333d02c2c2e2f3b06d18ce92d41dcbba823d59

For instance, my P3 machine won't run my third NIC correctly without either
acpi=off or acpi=noirq.

Oh, one more thing. You probably want to make sure you BIOS is up to date as well.

Confirmed working with 3228

Dell Precision M65, BIOS A08 (Core 2 Duo, T7200)

Positives:
This Dell XPS 210 has no problems whatsoever, not with the default install
CD or any later kernels, despite being a Core 2 duo machine. Tell me if 
there's anything you want me to test on this hardware.

I have a D520 (Intel Centrino Duo) and I'm having the same issues. I'm currently
using kernel 2.6.21-1.3228.fc7. I'm only able to boot using clocksource=acpi_pm
or maxcpus=1 (my default). If I remove any of the mentioned options, the system
stays put at "Uncompressing Linux... OK, booting the kernel". I waited 5 minutes
and it never passed that point.

I see the same boot-time hang in a Dell latitude D620 (dual core T2400) with 
the default kernel-2.6.21-1.3194.fc7. The hang is catastrophic and power cycle 
reset is the only way out. After using the boot option "acpi=off", the system 
boots fine.

All releases since 3208 (May 29 comment #18) work fine (for me), particularly
recent kernel-2.6.22.1 (-27.fc7, -33.fc7) updates.

afaic, problem is resolved, closing.

(In reply to comment #77)
> All releases since 3208 (May 29 comment #18) work fine (for me), 
particularly
> recent kernel-2.6.22.1 (-27.fc7, -33.fc7) updates.
> 
> afaic, problem is resolved, closing.

I can confirm that kernel 2.6.22.1-33.fc7 boots fine without any special 
options.

(In reply to comment #75)
> I have a D520 (Intel Centrino Duo) and I'm having the same issues. I'm currently
> using kernel 2.6.21-1.3228.fc7. I'm only able to boot using clocksource=acpi_pm
> or maxcpus=1 (my default). If I remove any of the mentioned options, the system
> stays put at "Uncompressing Linux... OK, booting the kernel". I waited 5 minutes
> and it never passed that point.

I can also confirm that these kernels now work without any special boot options:

2.6.22.1-33.fc7
2.6.22.1-41.fc7

I'm having a problem installing F7 from DVD on a Dell Vostro 200 with its
processor described as an "Intel® Pentium® Dual-Core Processor E2140".  The
machine has a SATA drive with an Intel ICH9 chip set.  The installer tries the
ata_piix driver, and hangs for awhile.  Then it enters the selection menus for
installing.  I did some Googling and found out that the proper driver is the
ahci.  However, in doing the menus, it seems to go two items for each key press.
 For example, in going forward or back it always goes two menus instead of one.
 When it gets to a menu listing the drivers, if I up or down arrow, it goes two
selections,  It won't let me select the ahci driver, always skipping over it.

I tried two different keyboards, and get the same result.  I also used the same
DVD on an older machine with different processor and an ATA-100 EIDE hard drive
and had no problems.

Is this the same bug, and is there any workaround for getting F7 installed on
this machine?

I am experiencing the same issue since FC6. I am not running Intel X Dell,
though, I am on an HP Pavillion dv6000, AMD 64X2.

I'm getting consistent boot hangs immediately after HAL starts when the screen
blanks for the X restart. This failure is 100% whenever the network cable is
plugged in and eth0 acquires an identity. If the network cable is unplugged and
eth0 fails, I have about a 40% chance of a successful boot.

The same failure occurs when I log out locally from an X session and the network
connection is active. If I disable the network and unplug the cable, then I have
the same chance to restart X successfully as if it were boot time.

Don't know how they are related, but they definitely are. Extremely irritating.

Have not tried this since an FC7 update, however. I will update and make another
try shortly.

Updated as of 2007.10.24. Exact same problems. Hopefully this gets fixed so I
can use Fedora again someday. This is pretty much a system-killer bug, as no
casual user will ever stick with a distro past getting black-screened 3 times or so.

So why is this issue considered of "medium" importance? Dual-core AMD64 laptops
are in no way rare these days...

(In reply to comment #80)
> I'm having a problem installing F7 from DVD on a Dell Vostro 200 with its
> processor described as an "Intel® Pentium® Dual-Core Processor E2140".  The
> machine has a SATA drive with an Intel ICH9 chip set.  The installer tries the
> ata_piix driver, and hangs for awhile.  Then it enters the selection menus for
> installing.  I did some Googling and found out that the proper driver is the
> ahci.  However, in doing the menus, it seems to go two items for each key press.
>  For example, in going forward or back it always goes two menus instead of one.
>  When it gets to a menu listing the drivers, if I up or down arrow, it goes two
> selections,  It won't let me select the ahci driver, always skipping over it.
> 
> I tried two different keyboards, and get the same result.  I also used the same
> DVD on an older machine with different processor and an ATA-100 EIDE hard drive
> and had no problems.
> 
> Is this the same bug, and is there any workaround for getting F7 installed on
> this machine?


Fedora 7 respins are now available:

http://spins.fedoraunity.org/spins

(In reply to comment #81)
> I am experiencing the same issue since FC6. I am not running Intel X Dell,
> though, I am on an HP Pavillion dv6000, AMD 64X2.
> 
> I'm getting consistent boot hangs immediately after HAL starts when the screen
> blanks for the X restart. This failure is 100% whenever the network cable is
> plugged in and eth0 acquires an identity. If the network cable is unplugged and
> eth0 fails, I have about a 40% chance of a successful boot.

That is a completely different problem. Please open a new bug.