From: Alex Riesen <alexander.riesen@synopsys.COM>
To: Milton Miller <miltonm@bga.com>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
linux-kernel@vger.kernel.org, mikpe@csd.uu.se
Subject: Re: 2.5.69+bk: oops in apmd after waking up from suspend mode
Date: Tue, 20 May 2003 19:17:59 +0200 [thread overview]
Message-ID: <20030520171759.GR32559@Synopsys.COM> (raw)
In-Reply-To: <20030520170054.GQ32559@Synopsys.COM>
Alex Riesen, Tue, May 20, 2003 19:00:54 +0200:
> Milton Miller, Tue, May 20, 2003 18:34:09 +0200:
> > Shouldn't this just use active_mm? Can somebody test?
>
> It helped.
>
> > by the way, I saw this with a 486 kernel compiled by
> > gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)
> >
> > on a Toshiba 2105 (aka 2100 +- sw) 486DX2/50, although I am not
> > at that computer presenlty to test.
> >
>
> Also the stability problems I mentioned before gone.
>
the last sentence is not true:
Unable to handle kernel paging request at virtual address 8bd6c008
printing eip:
c0180010
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c0180010>] Not tainted
EFLAGS: 00010216
EIP is at ext3_get_inode_loc+0xc0/0x180
eax: c5eb6000 ebx: 00066080 ecx: 0000000c edx: 00000066
esi: c5ebbe00 edi: 00000100 ebp: c5c89e20 esp: c5c89e08
ds: 007b es: 007b ss: 0068
Process find (pid: 22, threadinfo=c5c88000 task=c5e7e080)
Stack: 00000cc1 00000008 c5c89e30 c49bb984 c5ebbe00 c49bb900 c5c89e58 c018018d
c49bb984 c5c89e3c c5c89e54 c0162920 c5ebbe00 c10fe4f4 000209c2 c10fe4f4
000209c2 c49bb984 c5ebbe00 c56ad0a0 c5c89e74 c018215e c49bb984 c20861c8
Call Trace:
[<c018018d>] ext3_read_inode+0x2d/0x3c0
[<c0162920>] iget_locked+0x90/0xc0
[<c018215e>] ext3_lookup+0x12e/0x140
[<c01570cc>] real_lookup+0xac/0xd0
[<c015739e>] do_lookup+0x6e/0x80
[<c015783a>] link_path_walk+0x48a/0x900
[<c01b74be>] write_chan+0x16e/0x220
[<c0156cd8>] getname+0x78/0xc0
[<c01580e2>] __user_walk+0x32/0x50
[<c01533f7>] vfs_lstat+0x17/0x50
[<c01539d4>] sys_lstat64+0x14/0x30
[<c014aba2>] vfs_write+0xb2/0xf0
[<c014ac5e>] sys_write+0x2e/0x50
[<c0109187>] syscall_call+0x7/0xb
Code: 8b 4c 00 08 01 ca 89 55 f0 8b 46 0c 50 52 8b 86 8c 00 00 00
It is harder to trigger, but possible.
I booted with init=/bin/bash. Than I started this
find / -type f -fprint /dev/stderr -print | xargs cat > /dev/null
and began going in suspend mode and back.
At some point it broke with oops above.
-alex
next prev parent reply other threads:[~2003-05-20 17:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 12:16 2.5.69+bk: oops in apmd after waking up from suspend mode mikpe
2003-05-19 12:31 ` Alex Riesen
2003-05-19 14:41 ` Alex Riesen
2003-05-19 15:13 ` Alex Riesen
2003-05-20 10:39 ` Carl-Daniel Hailfinger
2003-05-20 10:48 ` Alex Riesen
2003-05-20 16:34 ` Milton Miller
2003-05-20 17:00 ` Alex Riesen
2003-05-20 17:17 ` Alex Riesen [this message]
2003-05-20 20:10 ` Nigel Cunningham
2003-05-20 22:01 ` Zwane Mwaikambo
2003-05-22 17:01 ` bill davidsen
2003-05-19 21:57 ` Zwane Mwaikambo
2003-05-19 21:57 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 9:48 Alex Riesen
2003-05-14 13:04 ` mikpe
2003-05-14 13:46 ` Alex Riesen
2003-05-14 14:03 ` mikpe
2003-05-14 14:11 ` Alex Riesen
2003-05-14 14:37 ` mikpe
2003-05-14 14:45 ` Alex Riesen
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=20030520171759.GR32559@Synopsys.COM \
--to=alexander.riesen@synopsys.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=miltonm@bga.com \
--cc=zwane@linuxpower.ca \
/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.