From: Tomas Szepe <szepe@pinerecords.com>
To: Derek Atkins <warlord@MIT.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linus BK tree crashes with PANIC: INIT: segmentation violation
Date: Sat, 11 Jan 2003 00:07:18 +0100 [thread overview]
Message-ID: <20030110230718.GO10062@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301101424590.1193-100000@penguin.transmeta.com>
> [torvalds@transmeta.com]
>
> I was hoping for a exact changset, your post didn't seem to be 100% sure.
>
> Anyway, the one you pinpointed ("Make x86 platform choice strings more
> easily selectable" top-of-tree is working), is followed by a patch by
> Christop Hellwig ("Missed one 'try_inc_mod_count'") which almost certainly
> isn't the cause of your trouble. So I'd like you to go forward a bit.
>
> For example, if you know that your (2) happens before 2.5.54, then you can
> do
>
> bk clone -ql -rv2.5.54 linux-BK test-tree
> bk changes
> .. look for the one you already know is ok: it's called
> "1.911.13.50" in the full 2.5.54 tree ..
Or you can just do everything "by hand" using these two together:
http://linux.bkbits.net:8080/linux-2.5
ftp://ftp.nl.linux.org/pub/linux/bk2patch/v2.5
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-01-10 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sjm7kdc63ul.fsf@kikki.mit.edu>
2003-01-10 22:52 ` Linus BK tree crashes with PANIC: INIT: segmentation violation Linus Torvalds
2003-01-10 23:07 ` Tomas Szepe [this message]
2003-01-11 5:06 ` Derek Atkins
2003-01-11 5:33 ` Linus Torvalds
2003-01-11 22:19 ` Derek Atkins
2003-01-12 1:49 ` Derek Atkins
2003-01-12 4:02 ` Linus Torvalds
2003-01-12 4:27 ` Derek Atkins
2003-01-10 17:01 Derek Atkins
2003-01-10 21:20 ` Tomas Szepe
2003-01-10 22:11 ` Linus Torvalds
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=20030110230718.GO10062@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=warlord@MIT.EDU \
/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