public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Danny ter Haar <dth@dth.net>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Date: Sun, 29 Jul 2007 03:23:24 +0200	[thread overview]
Message-ID: <20070729012324.GA29723@dth.net> (raw)
In-Reply-To: <200707290142.53689.bzolnier@gmail.com>

Quoting Bartlomiej Zolnierkiewicz (bzolnier@gmail.com):
> Please retry with the latest -git kernel and if the problem is still
> there install git, get kernel tree and run git-bisect.

I ran over "make menuconfig" and did a few changes.

http://www.dth.net/kernel/config-2.6.23-rc1-git5

It boots, but freezes solid before doing any "work" as a firewall.
I was able to catch boot messages with netconsole

http://www.dth.net/kernel/via_output_2.6.23-rc1-git5

It didn't respond after the last line.
magig sysrq etc, all nada.

Will start to get acquainted with git ;-)

Danny
-- 

  parent reply	other threads:[~2007-07-29  1:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 19:38 ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not dth
2007-07-28 23:42 ` Bartlomiej Zolnierkiewicz
2007-07-29  0:30   ` Danny ter Haar
2007-07-29  1:23   ` Danny ter Haar [this message]
2007-07-29  2:48     ` Gabriel C
2007-07-29  3:30       ` Danny ter Haar
2007-07-29  3:54         ` Gabriel C
2007-07-30  2:54           ` Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not: Danny ter Haar
2007-07-30 17:30             ` Len Brown
2007-07-31  1:10               ` Danny ter Haar
2007-07-31  4:00               ` Danny ter Haar
2007-07-31 14:30               ` Danny ter Haar
2007-08-01  0:44               ` Danny ter Haar
2007-08-01 20:03               ` Update: ACPI problems: 2.6.22-git17 working, 2.6.23-rc1* is not: (was ide not working) Danny ter Haar

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=20070729012324.GA29723@dth.net \
    --to=dth@dth.net \
    --cc=bzolnier@gmail.com \
    --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