From: Derek Atkins <warlord@MIT.EDU>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Larry McVoy <lm@bitmover.com>
Subject: Re: Linus BK tree crashes with PANIC: INIT: segmentation violation
Date: 11 Jan 2003 20:49:39 -0500 [thread overview]
Message-ID: <sjm1y3j3znw.fsf@kikki.mit.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0301101424590.1193-100000@penguin.transmeta.com>
Linus,
Linus Torvalds <torvalds@transmeta.com> writes:
> > 1) PANIC: INIT: ...
> > 2) String of Oopses
> > 3) Working Tree.
> >
> > The changeover from 2-3 is approximately December 30 (see my previous
> > post).
>
> I was hoping for a exact changset, your post didn't seem to be 100% sure.
The 'String of oopses' was a red herring. It was fixed sometime in early
January. The PANIC: INIT: problem, however, is real, and was introduced
by the following ChangeSet on January 7:
D 1.972 03/01/07 10:08:55-08:00 torvalds@home.transmeta.com 15824 15815 2/0/1
P ChangeSet
C Move x86 signal handler return stub to the vsyscall page,
C and stop honoring the SA_RESTORER information.
C
C This will prepare us for alternate signal handler returns.
If I build a kernel WITH this changeset it fails; if I build a kernel
at 1.971 (bjorn_helgaas's i810/i830 AGP patches) the kernel works just
fine.
So, something in your changes to kernel/sysenter.c or kernel/signal.c
causes INIT to PANIC and fail.
So, what would you like me to test, now?
-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
next prev parent reply other threads:[~2003-01-12 1:40 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 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 [this message]
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=sjm1y3j3znw.fsf@kikki.mit.edu \
--to=warlord@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®