public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <oliver@hartkopp.net>
To: Steven King <sfking@fdwdc.com>,
	johnstul@us.ibm.com, Michael Guntsche <mike@it-loops.com>,
	Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: bzImage build 'fix' for x86 broke 2.6.33-rc1 boot - was: Re: Also on x86 - was: 2.6.33-rc1: hrtimers and tickless broken on m68knommu.
Date: Sun, 20 Dec 2009 09:22:26 +0100	[thread overview]
Message-ID: <4B2DDEC2.9080708@hartkopp.net> (raw)
In-Reply-To: <4B2D45F8.7090008@hartkopp.net>

Sorry for always answering myself. But to get this issue closed for the readers.

This problem tracked down by Michael Guntsche was also my problem:

http://lkml.org/lkml/2009/12/19/124

By reverting ("kbuild: fix bzImage build for x86")

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4a2ff67c88211026afcbdbc190c13f705dae1b59

i was able to boot my first 2.6.33-rc1 ...

I'm running a Debian stable/testing here.

Tnx Michael!

Best regards,
Oliver



Oliver Hartkopp wrote:
> Oliver Hartkopp wrote:
>> Hi,
>>
>> i'm currently checking in LKML why my Dell 830 Laptop is not booting at all
>> with 2.6.33-rc1 - and i found your thread:
>>
>> http://lkml.org/lkml/2009/12/18/494
>>
>> I also use a setup with tickless & hrtimers enabled - but on a x86.
>>
>> Same behaviour as on your m68knommu box: Just nothing to see ...
> 
> I tried to dig a little deeper:
> 
> After disabling
> 
> - TICKLESS
> - HRTIMER
> - HPET
> - SMP
> 
> step by step I did not get any improvement on my Laptop :-(
> 
> So it's probably not a timer issue on my box.
> 
> The latest net-2.6 of Dave Miller is still running well ...
> 
> Regards,
> Oliver
> 
> 


      reply	other threads:[~2009-12-20  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 19:21 Also on x86 - was: 2.6.33-rc1: hrtimers and tickless broken on m68knommu Oliver Hartkopp
2009-12-19 21:30 ` Oliver Hartkopp
2009-12-20  8:22   ` Oliver Hartkopp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2DDEC2.9080708@hartkopp.net \
    --to=oliver@hartkopp.net \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@it-loops.com \
    --cc=sam@ravnborg.org \
    --cc=sfking@fdwdc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox