From: Paul <set@pobox.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
Date: Tue, 21 Aug 2001 21:42:33 -0400 [thread overview]
Message-ID: <20010821214233.F218@squish.home.loc> (raw)
In-Reply-To: <Pine.LNX.4.33.0108191600580.10914-100000@boston.corp.fedex.com> <m166bjokre.fsf@frodo.biederman.org> <20010819214322.D1315@squish.home.loc> <m1snenmfe0.fsf@frodo.biederman.org> <20010820211410.B218@squish.home.loc> <m1g0amlzcm.fsf@frodo.biederman.org>
In-Reply-To: <m1g0amlzcm.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Tue, Aug 21, 2001 at 12:08:09AM -0600
"Eric W. Biederman" <ebiederm@xmission.com>, on Tue Aug 21, 2001 [12:08:09 AM] said:
> Paul <set@pobox.com> writes:
>
> > I need to setup a test machine to persue this farther, as
> > locking and fscking my main box is no fun:) Ill try to get that
> > strace...
>
> O.k. That rules out all kinds of things. What is interesting at first
> glance is that a) Every oops has been in an interrupt handler. and
> b) It is never remotely at the same location.
>
> I'm beginning to suspect there is some kind of hardware problem. But it
> is very weird. I wonder if dos 6.2 somehow tickles a bug in the media GX
> processor. Though my top canidate is probably the lazy state switching
> introduced in 2.4. I know there were some problems with the ldt that were
> fixed, and there might be another case out there. But I'm just guessing
> in the dark.
>
> If you can reproduce this on a second machine that would definentily help.
>
> Eric
Dear Eric;
Oops'd twice on intel pentium 90 box. Same dosemu 1.0.0
binary and config files, 2.4.8-ac7 kernel. Behaviour was same as
my k6 box-- I did not decode oops, as that box didnt have a
serial console, and it didnt seem worth transcribing...
(was unable to oops it running 2.2.18pre21 on p90 box) Here
is the tail end of an strace. (the last bit that made it across
the wire during the telnet session-- I logged with fs mounted
sync, but the end of the log was garbage)
Paul
set@pobox.com
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
write(3,
"8\1\4\0\n\0\0\4\10\0\0\0\250\0\0\0L\1\5\0\2\0\0\4\n\0\0"..., 76)
= 76
write(3,
"L\"\r\0\2\0\0\4\n\0\0\4\0\0\34\0\332\304\304\304\304\304"...,
592) = 592
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = ? ERESTARTNOHAND (To be
restarted)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
write(3,
"L\1\5\0\2\0\0\4\n\0\0\4\0\0|\1\263\304\304\3048\304\5\0"...,
552) = 552
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
next prev parent reply other threads:[~2001-08-22 1:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " Paul
2001-08-19 5:09 ` Jeff Chua
2001-08-19 5:40 ` Paul
2001-08-19 8:04 ` Jeff Chua
2001-08-19 20:30 ` Eric W. Biederman
2001-08-20 1:43 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] " Paul
2001-08-20 6:09 ` Eric W. Biederman
2001-08-21 1:14 ` Paul
2001-08-21 6:08 ` Eric W. Biederman
2001-08-21 16:14 ` Wilfried Weissmann
[not found] ` <3B828898.BD98D4C4@gmx.at>
2001-08-21 16:20 ` Eric W. Biederman
2001-08-21 18:49 ` Wilfried Weissmann
2001-08-21 21:50 ` Wilfried Weissmann
2001-08-22 1:42 ` Paul [this message]
2001-08-22 7:56 ` Eric W. Biederman
2001-08-19 5:10 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " Jeff Chua
2001-08-22 2:45 ` Brian Gerst
[not found] ` <20010821232557.G218@squish.home.loc>
[not found] ` <3B832904.491AFE0E@didntduck.org>
2001-08-22 4:43 ` [OOPS] [resolution] Paul
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=20010821214233.F218@squish.home.loc \
--to=set@pobox.com \
--cc=ebiederm@xmission.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
all inboxes | Powered by JetHome®