From: Anders Karlsson <anders@trudheim.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Oleg Drokin <green@namesys.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.22-pre3 and reiserfs boot problem
Date: 10 Jul 2003 20:06:15 +0100 [thread overview]
Message-ID: <1057863974.2788.5.camel@tor.trudheim.com> (raw)
In-Reply-To: <3F0D88CB.3090303@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 3549 bytes --]
On Thu, 2003-07-10 at 16:39, Carl-Daniel Hailfinger wrote:
> Was there any disk activity after it became unresponsive? If not, please
> provide a (partially) decoded SysRq-T. I'm only interested in the decoded
> stack trace of the hung process (it should have a "D" after the process name).
Right, I have collected the details that was asked for. Carl-Daniel
suggested a way of tricking the system into doing an fsck without
tampering with the filesystem itself. Please find below the data I
copied out and decoded. If there is anything else I can do, let me know.
If there is any data about my system you require, let me know.
Output from Alt SysRq P:
Pid: 160, comm: fsck.ext3
EIP: 0010:[<c01b0f43>] CPU: 0 EFLAGS: 00000246 Not Tainted
EAX: 00000000 EBX: 00000000 ECX: c0338c00 EDX: 00000007
ESI: c0338c00 EDI: eee68000 EBP: eee69de8 DS: 0018 ES: 0018
CR0: 80050033 CR2: 400dcff0 CR3: 2ee6b000 CR4: 000006d0
Call trace: [<c01b1584>] [<c01b1bfb>] [<c01b1cca>] [<c0141643>]
[<c014178f>] [<c01417a4>] [<c0141887>] [<c01464e1>] [<c0141b61>]
[<c0108f83>]
Output from Alt SysRq T:
fsck.ext3 D current 3808 160 149 (NOTLB)
Call Trace: [<c014178f>] [<c01417a4>] [<c0141887>] [<c01464e1>]
[<c0141b61>] [<c0108f83>]
ksymoops 2.4.8 on i686 2.4.22-pre3-ac1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.22-pre3-ac1/ (default)
-m /boot/System.map-2.4.22-pre3-ac1 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Warning (compare_maps): mismatch on symbol zeroes , ipsec says
f23fdf00, /lib/modules/2.4.22-pre3-ac1/kernel/net/ipsec/ipsec.o says
f23fdde0. Ignoring
/lib/modules/2.4.22-pre3-ac1/kernel/net/ipsec/ipsec.o entry
Pid: 160, comm: fsck.ext3
EIP: 0010:[<c01b0f43>] CPU: 0 EFLAGS: 00000246 Not Tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EAX: 00000000 EBX: 00000000 ECX: c0338c00 EDX: 00000007
ESI: c0338c00 EDI: eee68000 EBP: eee69de8 DS: 0018 ES: 0018
Warning (Oops_set_regs): garbage 'DS: 0018 ES: 0018' at end of register
line ignored
CR0: 80050033 CR2: 400dcff0 CR3: 2ee6b000 CR4: 000006d0
Call trace: [<c01b1584>] [<c01b1bfb>] [<c01b1cca>] [<c0141643>]
[<c014178f>] [<c01417a4>] [<c0141887>] [<c01464e1>] [<c0141b61>]
[<c0108f83>]
Warning (Oops_read): Code line not seen, dumping what data is available
>>EIP; c01b0f43 <__get_request_wait+ae/f6> <=====
>>ECX; c0338c00 <ide_hwifs+c0/2af8>
>>ESI; c0338c00 <ide_hwifs+c0/2af8>
>>EDI; eee68000 <_end+2eb17bf4/304bcc54>
>>EBP; eee69de8 <_end+2eb199dc/304bcc54>
Trace; c01b1584 <__make_request+167/71a>
Trace; c01b1bfb <generic_make_request+c4/13a>
Trace; c01b1cca <submit_bh+59/a0>
Trace; c0141643 <write_locked_buffers+2a/36>
Trace; c014178f <write_some_buffers+140/142>
Trace; c01417a4 <write_unlocked_buffers+13/1d>
Trace; c0141887 <sync_buffers+1a/75>
Trace; c01464e1 <__block_fsync+2f/6c>
Trace; c0141b61 <sys_fsync+93/de>
Trace; c0108f83 <system_call+33/38>
4 warnings issued. Results may not be reliable.
--
Anders Karlsson <anders@trudheim.com>
Trudheim Technology Limited
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2003-07-10 18:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 14:20 2.4.22-pre3 and reiserfs boot problem Carl-Daniel Hailfinger
2003-07-10 14:38 ` Stephan von Krawczynski
2003-07-10 14:44 ` Carl-Daniel Hailfinger
2003-07-10 15:12 ` Stephan von Krawczynski
2003-07-10 15:30 ` Anders Karlsson
2003-07-10 15:39 ` Carl-Daniel Hailfinger
2003-07-10 19:06 ` Anders Karlsson [this message]
[not found] <E19ae9K-000Nas-00.ia6432-inbox-ru@f7.mail.ru>
2003-07-10 17:12 ` Stephan von Krawczynski
2003-07-10 18:01 ` Marcelo Tosatti
2003-07-11 13:15 ` Chris Mason
2003-07-11 13:27 ` Stephan von Krawczynski
2003-07-11 13:48 ` Chris Mason
2003-07-11 13:38 ` Stephan von Krawczynski
2003-07-11 13:51 ` Chris Mason
2003-07-11 15:15 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2003-07-10 15:49 "Peter Lojkin"
2003-07-10 16:06 ` Stephan von Krawczynski
2003-07-10 17:55 ` Marcelo Tosatti
2003-07-10 17:57 ` Marcelo Tosatti
2003-07-06 16:34 Stephan von Krawczynski
2003-07-06 18:13 ` Chris Mason
2003-07-06 21:24 ` Stephan von Krawczynski
2003-07-07 10:06 ` Stephan von Krawczynski
2003-07-09 12:01 ` Stephan von Krawczynski
2003-07-09 13:36 ` Chris Mason
2003-07-09 13:48 ` Oleg Drokin
2003-07-09 13:58 ` Stephan von Krawczynski
2003-07-09 14:11 ` Oleg Drokin
2003-07-09 14:25 ` Stephan von Krawczynski
2003-07-09 17:18 ` Marcelo Tosatti
2003-07-10 11:21 ` Stephan von Krawczynski
2003-07-10 11:54 ` Marcelo Tosatti
2003-07-10 12:20 ` Stephan von Krawczynski
2003-07-10 12:00 ` Stephan von Krawczynski
[not found] ` <20030709154015.GJ150921@niksula.cs.hut.fi>
2003-07-09 16:36 ` Stephan von Krawczynski
2003-07-09 14:01 ` Vincent Touquet
2003-07-09 14:20 ` Stephan von Krawczynski
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=1057863974.2788.5.camel@tor.trudheim.com \
--to=anders@trudheim.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=skraw@ithnet.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