From: Grant Miner <mine0057@mrs.umn.edu>
To: Nikita Danilov <Nikita@namesys.com>, reiserfs-list@namesys.com
Subject: Re: Autoconf error
Date: Wed, 30 Jul 2003 13:45:49 -0500 [thread overview]
Message-ID: <3F28125D.8040802@mrs.umn.edu> (raw)
In-Reply-To: <16168.4042.555742.436499@laputa.namesys.com>
> Very interesting. Is there anything in the logs (/var/log/messages), or
> on the console?
>
> Can you compile with Kernel-Hacking/Magic-Sysrq turned on, press
> sysrq-T on lock up and send us its output?
The first time I try that, I get an oops (see below). And init goes
into runlevel 5 for some reason. Second time, cat freezes up.
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c021c724
*pde = 00000000
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[<c021c724>] Not tainted
EFLAGS: 00010202
EIP is at reiser4_setattr+0x64/0xf0
eax: 00000000 ebx: 00000000 ecx: deee5c00 edx: 00000000
esi: de4cc108 edi: d30e9980 ebp: cf6dfd88 esp: cf6dfd80
ds: 007b es: 007b ss: 0068
Process bash (pid: 1569, threadinfo=cf6de000 task=d594f380)
Stack: de4cc108 cf6dfe48 00000000 00000000 00000000 00000000 00000000
00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul 30 11:37:14 uber login(pam_unix)[1030]: session closed for user root
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Call Trace:
[<c016ebe1>] notify_change+0x201/0x260
[<c02387f0>] update_ugid+0x90/0xb0
[<c024a7b4>] vsscanf+0x274/0x4a0
[<c024a9ff>] sscanf+0x1f/0x24
[<c023886d>] get_uid+0x5d/0x70
[<c023c689>] write_pseudo+0x69/0xb0
[<c02063ba>] init_context+0x9a/0xd0
[<c021d1dd>] reiser4_write+0x8d/0x100
[<c021d150>] reiser4_write+0x0/0x100
[<c0152d3c>] vfs_write+0xdc/0x150
[<c0152e62>] sys_write+0x42/0x70
[<c010accb>] syscall_call+0x7/0xb
Code: 83 08 04 89 2c 24 e8 61 9d fe ff 89 d8 8b b4 24 8c 00 00 00
next prev parent reply other threads:[~2003-07-30 18:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 16:54 Autoconf error Grant Miner
2003-07-28 17:10 ` Grant Miner
2003-07-29 5:07 ` Yury Umanets
2003-07-29 6:12 ` Grant Miner
2003-07-29 6:14 ` Yury Umanets
2003-07-29 6:30 ` Grant Miner
2003-07-29 6:30 ` Yury Umanets
2003-07-29 18:43 ` Grant Miner
2003-07-30 5:17 ` Yury Umanets
2003-07-30 18:34 ` Nikita Danilov
2003-07-30 18:40 ` Nikita Danilov
2003-07-30 18:49 ` Nikita Danilov
2003-07-30 23:04 ` link error [was Re: Autoconf error] Grant Miner
2003-07-31 0:18 ` [patch] for configure.in for reiser4progs Grant Miner
2003-07-31 4:59 ` Yury Umanets
2003-07-30 18:45 ` Grant Miner [this message]
2003-07-29 18:56 ` Autoconf error Grant Miner
2003-07-29 5:01 ` Yury Umanets
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=3F28125D.8040802@mrs.umn.edu \
--to=mine0057@mrs.umn.edu \
--cc=Nikita@namesys.com \
--cc=reiserfs-list@namesys.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 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.