<br><br><div><span class="gmail_quote">On 7/6/07, <b class="gmail_sendername">Thorsten Leemhuis</b> <<a href="mailto:fedora@leemhuis.info">fedora@leemhuis.info</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 05.07.2007 16:50, dragoran wrote:<br>> On 7/5/07, *dragoran* <<a href="mailto:drago01@gmail.com">drago01@gmail.com</a> <mailto:<a href="mailto:drago01@gmail.com">drago01@gmail.com</a>>> wrote:<br>> On 7/5/07, *dragoran* <
<a href="mailto:drago01@gmail.com">drago01@gmail.com</a><br>> <mailto:<a href="mailto:drago01@gmail.com">drago01@gmail.com</a>>> wrote:<br>> On 7/5/07, *Build System* < <a href="mailto:buildsys@redhat.com">
buildsys@redhat.com</a><br>> <mailto:<a href="mailto:buildsys@redhat.com">buildsys@redhat.com</a>>> wrote:<br>> kernel-2.6.22-0.9.rc7.git3.fc8<br>> ------------------------------
<br>> * Wed Jul 04 2007 Dave Jones <<a href="mailto:davej@redhat.com">davej@redhat.com</a><br>> <mailto:<a href="mailto:davej@redhat.com">davej@redhat.com</a>>><br>> -
2.6.22-rc7-git3<br>><br>> * Wed Jul 04 2007 Dave Jones < <a href="mailto:davej@redhat.com">davej@redhat.com</a><br>> <mailto:<a href="mailto:davej@redhat.com">davej@redhat.com</a>>>
<br>> - x86-64 tickless support.<br>> I tested this one on my laptop (still uses f7) and it hangs at<br>> boot. after "Booting the kernel" no more errors, no panic it<br>> just don't continue to boot.
<br>> Its a Zepto 6615WD with a Core 2 Duo T7400, ICH7 chipset running<br>> on x86_64<br>> added CC, any idea how to get a message from the kernel to see whats<br>> going on?<br>> it boots when I pass "nohpet" to it.
<br>> dmesg is attached.<br><br>Same problem here as well -- same workaround works :-)<br><br>Dell D630 (Santa Rosa with GM965).<br><a href="http://leemhuis.info/files/fedorarpms/MISC.fdr/dmesg-d630">http://leemhuis.info/files/fedorarpms/MISC.fdr/dmesg-d630
</a><br><br>dragoran, did you file a bug somewhere? I could not find one.</blockquote><div><br>no, just wrote this mail.<br>fell free to open a bug and cc me, but dave already knows about it and the next kernel should have a workaround (remove the force hpet patch) until the upstream developer gets back from vocation.
<br></div><br></div><br>