All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Atkins <warlord@MIT.EDU>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linus BK tree crashes with PANIC: INIT: segmentation violation
Date: 11 Jan 2003 23:27:40 -0500	[thread overview]
Message-ID: <sjmlm1r2ds3.fsf@kikki.mit.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0301111953060.1401-100000@home.transmeta.com>

Linus Torvalds <torvalds@transmeta.com> writes:

> Oh, well. Can you verify whether this fixes it for you? And thanks for 
> hunting down the exact changeset.

Thanks.  This patch does indeed fix it for me.  And you're welcome --
I learned a lot about bitkeeper in the process of tracking this down.
FTR, BK *DID* make it a lot easier to visualize the graph so I could
walk backwards and track it down.

> Btw, what version of "init" are you running? It would be interesting to 
> see what it actually does, and obviously none of the machines I have 
> around have that init.. 

Red Hat's SysVinit-2.84-2.

> 		Linus

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available

  reply	other threads:[~2003-01-12  4:18 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
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 [this message]
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=sjmlm1r2ds3.fsf@kikki.mit.edu \
    --to=warlord@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.