From: "J.A. Magallon" <jamagallon@able.es>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
"Barry K. Nathan" <barryn@pobox.com>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
rwhron@earthlink.net
Subject: Re: [PATCHSET] Linux 2.4.18-rc3-jam1
Date: Sat, 23 Feb 2002 10:40:37 +0100 [thread overview]
Message-ID: <20020223104037.A5624@werewolf.able.es> (raw)
In-Reply-To: <20020223023332.A1689@werewolf.able.es> <20020223082301.34EDF89C87@cx518206-b.irvn1.occa.home.com>
In-Reply-To: <20020223082301.34EDF89C87@cx518206-b.irvn1.occa.home.com>; from barryn@pobox.com on sáb, feb 23, 2002 at 09:23:01 +0100
On 20020223 Barry K. Nathan wrote:
>J.A. Magallon wrote:
>> My box also hangs acessing the floppy. Strange thing is that it also
>> hangs without irqrate-A1. Will send an oops.
>
>It could be one of the patches that comes before irqrate-A1 in the 00-90
>numbering sequence that your patches use; I've definitely reproduced this
>without any of the patches numbered higher than the irqrate-A1 patch.(In
>my case, if I applied all of those patches except the irqrate one, I
>didn't get the freeze. If I applied all the patches up to the irqrate one
>after, then I got the freeze.)
>
Looking at the out of sysrq-p:
Pid: 0, comm: swapper
EIP: 0010:[schedule+129/928] CPU: 0 EFLAGS: 00000286 Tainted: P
EIP: 0010:[<c0117651>] CPU: 0 EFLAGS: 00000286 Tainted: P
lf32-i386 -a i386
EAX: 000000ff EBX: c02bac80 ECX: 00000000 EDX: c027c000
ESI: 00000000 EDI: c027c000 EBP: c027dfc0 DS: 0018 ES: 0018
CR0: 8005003b CR2: 4004f6b0 CR3: 1d9fc000 CR4: 000002d0
Call Trace: [rest_init+0/64] [default_idle+0/64] [default_idle+0/64] [rest_init+0/64] [cpu_idle+41/48]
Call Trace: [<c0105000>] [<c0105200>] [<c0105200>] [<c0105000>] [<c0105289>]
Warning (Oops_read): Code line not seen, dumping what data is available
>>EIP; c0117650 <schedule+80/3a0> <=====
Trace; c0105000 <_stext+0/0>
Trace; c0105200 <default_idle+0/40>
Trace; c0105200 <default_idle+0/40>
Trace; c0105000 <_stext+0/0>
Trace; c0105288 <cpu_idle+28/30>
I vote for the sched-O1. The mount never gets rescheduled ????
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-rc4-jam1 #1 SMP Sat Feb 23 01:39:06 CET 2002 i686
next prev parent reply other threads:[~2002-02-23 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 0:50 [PATCHSET] Linux 2.4.18-rc3-jam1 J.A. Magallon
2002-02-22 7:38 ` Barry K. Nathan
2002-02-23 1:33 ` J.A. Magallon
2002-02-23 8:23 ` Barry K. Nathan
2002-02-23 9:40 ` J.A. Magallon [this message]
2002-02-23 23:39 ` Barry K. Nathan
2002-02-24 2:24 ` Barry K. Nathan
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 4:21 rwhron
2002-02-22 5:35 ` Andrew Morton
2002-02-24 15:00 rwhron
2002-02-24 23:14 ` J.A. Magallon
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=20020223104037.A5624@werewolf.able.es \
--to=jamagallon@able.es \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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