From: Ulrich Drepper <drepper@redhat.com>
To: linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>
Subject: oops with current bk kernel on x86-64
Date: Fri, 02 May 2003 00:07:37 -0700 [thread overview]
Message-ID: <3EB21939.70002@redhat.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 452 bytes --]
Some harmless code (while compiling glibc) caused two oopses with the
current bk kernel (as of 2003-05-01T21:00:00-07). syslogd log the
attached lines but the remote session I was using is pretty dead. This
is on a Solo machine.
--
--------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
[-- Attachment #1.2: a --]
[-- Type: text/plain, Size: 4102 bytes --]
May 1 23:55:30 hammer kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
May 1 23:55:30 hammer kernel: printing rip:
May 1 23:55:30 hammer kernel: ffffffff8021efe4
May 1 23:55:30 hammer kernel: PML4 eb8f067 PGD 27ad067 PMD 0
May 1 23:55:30 hammer kernel: Oops: 0000 [1]
May 1 23:55:30 hammer kernel: CPU 0
May 1 23:55:30 hammer kernel: Pid: 18070, comm: ld-linux-x86-64 Not tainted
May 1 23:55:30 hammer kernel: RIP: 0010:[<ffffffff8021efe4>] <ffffffff8021efe4>{copy_user_generic+1}
May 1 23:55:30 hammer kernel: RSP: 0018:000001000a475b88 EFLAGS: 00010246
May 1 23:55:30 hammer kernel: RAX: 0000000000000058 RBX: 0000000000000fa8 RCX: 0000000000000000
May 1 23:55:30 hammer kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000100027f4058
May 1 23:55:30 hammer kernel: RBP: 000001001ec83860 R08: 000000ff000000fe R09: 000000f7000000f6
May 1 23:55:30 hammer kernel: R10: 000000f9000000f8 R11: 000000f3000000f2 R12: 0000000000000000
May 1 23:55:30 hammer kernel: R13: 00000100027f4058 R14: 0000000000000000 R15: 0000000000000074
May 1 23:55:30 hammer kernel: FS: 0000002a95791300(0000) GS:ffffffff803e7440(0000) knlGS:0000000000000000
May 1 23:55:30 hammer kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 1 23:55:30 hammer kernel: CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006a0
May 1 23:55:30 hammer kernel:
May 1 23:55:30 hammer kernel: Call Trace:<ffffffff80194a2a>{ext3_prepare_write+106} <ffffffff8014b843>{__filemap_copy_from_user_iovec+67}
May 1 23:55:30 hammer kernel: <ffffffff8014bf2a>{generic_file_aio_write_nolock+1722}
May 1 23:55:30 hammer kernel: <ffffffff8019eea6>{journal_dirty_metadata+438} <ffffffff8014c2ae>{generic_file_write_nolock+94}
May 1 23:55:30 hammer kernel: <ffffffff8019eea6>{journal_dirty_metadata+438} <ffffffff801967b1>{ext3_do_update_inode+657}
May 1 23:55:30 hammer kernel: <ffffffff8019f32f>{journal_stop+511} <ffffffff8019a88d>{__ext3_journal_stop+45}
May 1 23:55:30 hammer kernel: <ffffffff8014c49a>{generic_file_writev+58} <ffffffff80164278>{do_readv_writev+392}
May 1 23:55:30 hammer kernel: <ffffffff80163d00>{do_sync_write+0} <ffffffff80164986>{get_empty_filp+118}
May 1 23:55:30 hammer kernel: <ffffffff801632e3>{dentry_open+227} <ffffffff801631f1>{filp_open+65}
May 1 23:55:30 hammer kernel: <ffffffff80164474>{sys_writev+68} <ffffffff801116a4>{system_call+124}
May 1 23:55:30 hammer kernel:
May 1 23:55:30 hammer kernel: Process ld-linux-x86-64 (pid: 18070, stackpage=10019826c50)
May 1 23:55:30 hammer kernel: Stack: 0000000000000fa8 ffffffff8014b843 00000000000005a8 000001001ec83850
May 1 23:55:30 hammer kernel: 00000100010c7c40 00000100046a2300 0000000000000000 ffffffff8014bf2a
May 1 23:55:30 hammer kernel: 000001000a475bd8 0000007fbffff630
May 1 23:55:30 hammer kernel: Call Trace:<ffffffff8014b843>{__filemap_copy_from_user_iovec+67}
May 1 23:55:30 hammer kernel: <ffffffff8014bf2a>{generic_file_aio_write_nolock+1722}
May 1 23:55:30 hammer kernel: <ffffffff8019eea6>{journal_dirty_metadata+438} <ffffffff8014c2ae>{generic_file_write_nolock+94}
May 1 23:55:30 hammer kernel: <ffffffff8019eea6>{journal_dirty_metadata+438} <ffffffff801967b1>{ext3_do_update_inode+657}
May 1 23:55:30 hammer kernel: <ffffffff8019f32f>{journal_stop+511} <ffffffff8019a88d>{__ext3_journal_stop+45}
May 1 23:55:30 hammer kernel: <ffffffff8014c49a>{generic_file_writev+58} <ffffffff80164278>{do_readv_writev+392}
May 1 23:55:30 hammer kernel: <ffffffff80163d00>{do_sync_write+0} <ffffffff80164986>{get_empty_filp+118}
May 1 23:55:30 hammer kernel: <ffffffff801632e3>{dentry_open+227} <ffffffff801631f1>{filp_open+65}
May 1 23:55:30 hammer kernel: <ffffffff80164474>{sys_writev+68} <ffffffff801116a4>{system_call+124}
May 1 23:55:30 hammer kernel:
May 1 23:55:30 hammer kernel:
May 1 23:55:30 hammer kernel: Code: 0f 18 1e 31 c0 89 f9 83 e1 07 0f 85 9b 00 00 00 48 89 d1 bb
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-05-02 6:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EB21939.70002@redhat.com \
--to=drepper@redhat.com \
--cc=ak@muc.de \
--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 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.