public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: Nico Schottelius <nico-kernel@schottelius.org>,
	Christian Kujau <evil@g-house.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Daniel Aubry <kernel-obri@chaostreff.ch>
Subject: Re: Some problems with 2.6.13.4
Date: Sun, 16 Oct 2005 13:19:54 +0200	[thread overview]
Message-ID: <20051016111954.GU12774@schottelius.org> (raw)
In-Reply-To: <20051015200245.GM12774@schottelius.org>

[-- Attachment #1: Type: text/plain, Size: 2520 bytes --]

After some heavy compile hours, here are the results:

- 2.6.13.1 and 2.6.13.2 behave the same way with the same config.

For reference I now published the configs [0]. 2.6.12.5 was the config
source, all others where generated using make oldconfig.

Perhaps there's a somehow heavy configuration mistake in it?

Btw, Daniel Aubry fixed his keyboard problem with disabling usb keyboard support
in the bios (is this really the right way?).

Nico

[0]: http://creme.schottelius.org/~nico/temp/kb-configs/

Nico Schottelius [Sat, Oct 15, 2005 at 10:02:45PM +0200]:
> I was a little bit wrong:
> 
> 2.6.13.3 and 2.6.13.4 freeze both on the ibm tp 600, but first
> after "Freeing unused kernel memory: 96k"
> 
> There is no output from init (neither "cinit-0.2: Booting from ..."
> nor "INIT:" (sys-v-init)), so this is not an init problem.
> 
> Could we somehow debug this differently or do I have to install
> 2.6.13.2 and 2.6.13.1, too? It would take simply hours until it is
> finished here.
> 
> Nico
> 
> Nico Schottelius [Sat, Oct 15, 2005 at 05:40:48PM +0200]:
> > Christian Kujau [Sat, Oct 15, 2005 at 05:05:21PM +0200]:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: RIPEMD160
> > > 
> > > Nico Schottelius schrieb:
> > > > The kernel configurations are used from the versions before, with running
> > > > make oldconfig before.
> > > 
> > > so, these machines were running fine with 2.6.13.3 or .2 and stopped
> > > working with 2.6.13.4? if yes, then perhaps you can narrow it down to one
> > > of the changes in patch-2.6.13.3-4.gz or patch-2.6.13.2-3.gz
> > > 
> > > (from http://www.kernel.org/pub/linux/kernel/v2.6/incr/)
> > 
> > Sorry, I sent the message before inserting this info:
> > 
> > - ibm tp runs with 2.6.12.5
> > - dell latitude runs with 2.6.10
> > 
> > I personally have access to the ibm tp and I'll test 2.6.13.3 in some hours
> > (which it nees to compile it).
> > 
> > I'll report more info than. Perhaps Daniel Aubry can test on his dell, too.
> > 
> > Nico
> > 
> > -- 
> > Latest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)
> > Open Source nutures open minds and free, creative developers.
> 
> 
> 
> -- 
> Latest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)
> Open Source nutures open minds and free, creative developers.



-- 
Latest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)
Open Source nutures open minds and free, creative developers.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

      parent reply	other threads:[~2005-10-16 11:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 12:21 Some problems with 2.6.13.4 Nico Schottelius
2005-10-15 15:05 ` Christian Kujau
2005-10-15 15:40   ` Nico Schottelius
2005-10-15 20:02     ` Nico Schottelius
2005-10-15 20:22       ` Jesper Juhl
2005-10-15 20:38         ` Nico Schottelius
2005-10-15 21:03           ` Paolo Ornati
2005-10-24 16:27           ` Kalin KOZHUHAROV
2005-10-16 11:19       ` Nico Schottelius [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=20051016111954.GU12774@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --cc=evil@g-house.de \
    --cc=kernel-obri@chaostreff.ch \
    --cc=linux-kernel@vger.kernel.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