From: Philippe Troin <phil@fifi.org>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.22
Date: 01 Oct 2002 17:22:40 -0700 [thread overview]
Message-ID: <877kh1adv3.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <200210020007.g9207su26324@devserv.devel.redhat.com>
Alan Cox <alan@redhat.com> writes:
> 2.2.2 doesnt support gcc 3
There also is something else broken about it ;-)
It's been crashing repeatedly on one of my boxes with the following
oops:
----------------------------------------------------------------------
Unable to handle kernel paging request at virtual address 000ed0ac
current->tss.cr3 = 031ff000, %cr3 = 031ff000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c018464e>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 000ed0a4 ebx: 00000000 ecx: 00000807 edx: cae8be00
esi: c1c63e24 edi: 00000004 ebp: 00000008 esp: c1c63dcc
ds: 0018 es: 0018 ss: 0018
Process tripwire (pid: 4524, process nr: 108, stackpage=c1c63000)
Stack: 00000000 00000100 c8384620 c8384620 00076855 00000400 c8384620 00000807
00076855 c012e640 00000000 00000004 c1c63e24 cfbcd880 00000374 cfbcd880
00000000 c1c63ea4 00000807 00000004 cae8be00 00000000 cae8be00 c8795d20
Call Trace: [<c012e640>] [<c012e81c>] [<c0122f0e>] [<c0122e4b>] [<c012330c>] [<c01bd025>] [<c01236b3>]
[<c0123600>] [<c0112217>] [<c0111b8a>] [<c012be3e>] [<c010c7ad>] [<c010a7d0>]
Code: 28 8b 14 9e 8b 42 08 c1 e8 09 50 8d 42 10 50 8d 42 0e 50 31
>>EIP; c018464e <ll_rw_block+ce/228> <=====
Trace; c012e640 <brw_page+26c/368>
Trace; c012e81c <generic_readpage+8c/9c>
Trace; c0122f0e <try_to_read_ahead+f2/10c>
Trace; c0122e4b <try_to_read_ahead+2f/10c>
Trace; c012330c <do_generic_file_read+294/588>
Trace; c01bd025 <do_aic7xxx_isr+79/98>
Trace; c01236b3 <generic_file_read+63/7c>
Trace; c0123600 <file_read_actor+0/50>
Trace; c0112217 <do_level_ioapic_IRQ+9b/b0>
Trace; c0111b8a <smp_apic_timer_interrupt+16/20>
Trace; c012be3e <sys_read+c6/f8>
Trace; c010c7ad <apic_timer_interrupt+1d/28>
Trace; c010a7d0 <system_call+34/38>
Code; c018464e <ll_rw_block+ce/228>
00000000 <_EIP>:
Code; c018464e <ll_rw_block+ce/228> <=====
0: 28 8b 14 9e 8b 42 sub %cl,0x428b9e14(%ebx) <=====
Code; c0184654 <ll_rw_block+d4/228>
6: 08 c1 or %al,%cl
Code; c0184656 <ll_rw_block+d6/228>
8: e8 09 50 8d 42 call 428d5016 <_EIP+0x428d5016> 02a59664 Before first symbol
Code; c018465b <ll_rw_block+db/228>
d: 10 50 8d adc %dl,0xffffff8d(%eax)
Code; c018465e <ll_rw_block+de/228>
10: 42 inc %edx
Code; c018465f <ll_rw_block+df/228>
11: 0e push %cs
Code; c0184660 <ll_rw_block+e0/228>
12: 50 push %eax
Code; c0184661 <ll_rw_block+e1/228>
13: 31 00 xor %eax,(%eax)
----------------------------------------------------------------------
See <873crzmb6b.fsf@ceramic.fifi.org> for more details.
2.2.21 has ran with more than 6 months uptime and the same workload.
2.2.22 crashes with the above oops every couple of days.
Phil.
prev parent reply other threads:[~2002-10-02 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 16:35 Linux 2.2.22 Alan Cox
2002-09-17 9:43 ` Luca Montecchiani
2002-10-01 20:47 ` Rasmus Andersen
2002-10-02 0:07 ` Alan Cox
2002-10-02 0:22 ` Philippe Troin [this message]
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=877kh1adv3.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=alan@redhat.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