public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Bugla" <uwe.bugla@gmx.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: johnstul@us.ibm.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
	Valdis.Kletnieks@vt.edu
Subject: Re: Re: i686 hang on boot in userspace
Date: Mon, 17 Jul 2006 15:38:09 +0200	[thread overview]
Message-ID: <20060717133809.150390@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0607171242440.6761@scrub.home>


-------- Original-Nachricht --------
Datum: Mon, 17 Jul 2006 12:52:28 +0200 (CEST)
Von: Roman Zippel <zippel@linux-m68k.org>
An: Uwe Bugla <uwe.bugla@gmx.de>
Betreff: Re: i686 hang on boot in userspace

> Hi,
> 
> On Fri, 14 Jul 2006, Uwe Bugla wrote:
> 
> > Hi everybody,
> > first of all thanks to the explanatory hints how a magic Sysrq key works
> – I've learned a lot.
> > 
> > I first pressed ALT + PrintScreen + P, then ALT + PrintScreen + T.
> > To avoid wordwrapping or other unwanted effects please see the resulting
> kern.log as outline attachment.
> > 
> > Could someone please explain to me what's behind that cryptic code?
> 
> It shows what the kernel is currently is doing and where it's spending the
> time.
> First, your kernel buffer log buffer seems a little small, so not 
> everything is captured. Could you increase the number in the "Kernel log 
> buffer size" option (it's in the "Kernel debugging" part of the "Kernel 
> hacking" menu).
> Second, could you press ALT+PrintScreen+P a few more times (maybe around 
> 10 at least) while the kernel hangs? This would should where the cpu is 
> spending its time and whether it's at a single place or at different 
> places.
> Thanks.
> 
> bye, Roman

Hi Roman, Hi everybody else,
my boot problem is solved within kernel 2.6.18-rc1-mm2!!!

A thousands of thanks for all your efforts!

I have compared 18-rc1-mm1 and 18-rc1-mm2.
mm2 contains a patch for timer.c owning almost twice as many hunks than mm1.
In so far I was sure it was a timer.c issue.

Regards

Uwe

-- 


Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

  parent reply	other threads:[~2006-07-17 13:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060714150418.120680@gmx.net>
2006-07-14 19:43 ` i686 hang on boot in userspace john stultz
2006-07-17 10:52 ` Roman Zippel
2006-07-17 11:09   ` Roman Zippel
2006-07-17 13:38   ` Uwe Bugla [this message]
2006-07-17 14:17     ` Roman Zippel
2006-07-17 14:59       ` gmu 2k6
2006-07-17 15:21         ` Roman Zippel
2006-07-17 15:58           ` gmu 2k6
2006-07-17 16:02             ` gmu 2k6
2006-07-17 17:03               ` Roman Zippel
2006-07-17 18:15                 ` gmu 2k6
2006-07-17 18:17                   ` gmu 2k6
2006-07-18  9:38                   ` gmu 2k6
2006-07-19 10:26                     ` gmu 2k6
2006-07-24 15:34                       ` gmu 2k6
2006-07-25  7:32                         ` Jens Axboe
2006-07-25  8:00                           ` gmu 2k6
2006-07-25  7:41                             ` Jens Axboe
     [not found]                               ` <f96157c40607250120s2554cbc6qbd7c42972b70f6de@mail.gmail.com>
     [not found]                                 ` <20060725080002.GD4044@suse.de>
2006-07-25  8:28                                   ` gmu 2k6
2006-07-25  8:08                                     ` Jens Axboe
2006-07-25  9:17                                       ` gmu 2k6
2006-07-25  8:57                                         ` Jens Axboe
2006-07-25 10:09                                           ` gmu 2k6
2006-07-25  9:46                                             ` Jens Axboe
2006-07-25 10:19                                               ` gmu 2k6
2006-07-25 10:41                                                 ` Jens Axboe
2006-07-25  9:20                                         ` gmu 2k6
2006-07-25  8:57                                           ` Jens Axboe
2006-07-25  9:35                                           ` gmu 2k6
2006-07-25  9:24                                             ` Jens Axboe
2006-07-25 11:29                                             ` Jens Axboe
2006-07-25 12:47                                               ` gmu 2k6
2006-07-25 12:52                                                 ` Jens Axboe
2006-07-25 12:58                                                   ` Jens Axboe
2006-07-25 14:27                                                     ` gmu 2k6
2006-07-25 14:29                                                       ` gmu 2k6
2006-07-25 15:18                                                       ` Jens Axboe
2006-07-25 13:13                                                   ` gmu 2k6
2006-07-25 14:50                                                   ` gmu 2k6
2006-07-25 15:19                                                     ` Jens Axboe
2006-07-25 18:58                                                     ` gmu 2k6
2006-07-25 19:21                                                       ` Jens Axboe
2006-07-25 19:28                                                         ` gmu 2k6
2006-07-25  9:51                                       ` gmu 2k6
2006-07-25  9:42                                         ` Jens Axboe
2006-07-17 16:11             ` gmu 2k6

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=20060717133809.150390@gmx.net \
    --to=uwe.bugla@gmx.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.org \
    /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