From: "Frode Tennebø" <frodet@nvg.org>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Kernel Oops
Date: Wed, 1 Aug 2001 23:24:05 +0200 [thread overview]
Message-ID: <01080123240507.01440@leia> (raw)
I have tested SGI's linux-2.4-xfs in it's 2.4.7 incarnation. Compilled
with gcc-2.96-81 on a Dell Latitude CPt400 with an Adaptec 1460A PCMCIA
SCSI adapter.
I can do whatever I want until I mount an LVM volume. After some time
or immediately it will panic with a dump like this:
Aug 1 18:57:26 localhost kernel: Unable to handle kernel paging
request at virtual address c489c4f0
Aug 1 18:57:26 localhost kernel: printing eip:
Aug 1 18:57:26 localhost kernel: c489c4f0
Aug 1 18:57:26 localhost kernel: *pde = 03bd1067
Aug 1 18:57:26 localhost kernel: *pte = 00000000
Aug 1 18:57:26 localhost kernel: Oops: 0000
Aug 1 18:57:26 localhost kernel: CPU: 0
Aug 1 18:57:26 localhost kernel: EIP:
0010:[fat:__insmod_fat_S.bss_L2264+450160/60315488]
Aug 1 18:57:26 localhost kernel: EIP: 0010:[<c489c4f0>]
Aug 1 18:57:26 localhost kernel: EFLAGS: 00010086
Aug 1 18:57:26 localhost kernel: eax: c0331c20 ebx: 00000202 ecx:
00000801 edx: c489c4f0
Aug 1 18:57:26 localhost kernel: esi: c250f620 edi: 00000002 ebp:
00073000 esp: c1913c98
Aug 1 18:57:26 localhost kernel: ds: 0018 es: 0018 ss: 0018
Aug 1 18:57:26 localhost kernel: Process mount (pid: 19930,
stackpage=c1913000)
Aug 1 18:57:26 localhost kernel: Stack: c01e6d2a 00000801 00000001
c01e7ada 00000801 c10e6c84 00000000 c02c5cb4
Aug 1 18:57:26 localhost kernel: c02c5e20 c250f620 00000001
00000000 00000000 c01e7b94 00000000 c250f620
Aug 1 18:57:26 localhost kernel: c250f620 c250f620 00000000
c01e7df7 00000000 c250f620 c0133ae3 c1912000
Aug 1 18:57:27 localhost kernel: Call Trace: [blk_get_queue+42/48]
[generic_make_request+186/288] [submit_bh+84/112] [ll_rw_block+583/672]
[getblk+211/256] [block_read+722/1184] [do_ide_request+15/32]
Aug 1 18:57:27 localhost kernel: Call Trace: [<c01e6d2a>] [<c01e7ada>]
[<c01e7b94>] [<c01e7df7>] [<c0133ae3>] [<c0138aa2>] [<c01f498f>]
Aug 1 18:57:27 localhost kernel: [__alloc_pages+116/624]
[do_anonymous_page+58/272] [do_no_page+48/192]
[filemap_nopage+185/1264] [filemap_nopage+185/1264] [do_no_page+77/192]
[handle_mm_fault+97/208] [__alloc_pages+116/624]
Aug 1 18:57:27 localhost kernel: [<c012bb84>] [<c012189a>]
[<c01219a0>] [<c0124c49>] [<c0124c49>] [<c01219bd>] [<c0121a91>]
[<c012bb84>]
Aug 1 18:57:27 localhost kernel: [do_anonymous_page+58/272]
[cached_lookup+16/80] [path_walk+1788/2016] [file_read_actor+115/240]
[cached_lookup+16/80] [blkdev_open+71/128] [dentry_open+195/320]
[sys_read+150/208]
Aug 1 18:57:27 localhost kernel: [<c012189a>] [<c013bf60>]
[<c013c86c>] [<c0124643>] [<c013bf60>] [<c01392a7>] [<c01316a3>]
[<c0131cc6>]
Aug 1 18:57:27 localhost kernel: [sys_llseek+201/224]
[system_call+51/56]
Aug 1 18:57:27 localhost kernel: [<c0131c19>] [<c0106ecb>]
Aug 1 18:57:27 localhost kernel:
Aug 1 18:57:27 localhost kernel: Code: Bad EIP value.
This also happens with 2.4.8-pre3-xfs. I'm not sure if this is a LVM
issue, a general kernel issue or an SGi/XFS issue, but I thought I'd
bring it up here before I talked to the XFS guys as this is directly
related to LVM (#define LVM_RELEASE_NAME "0.9.1_beta6" - perhaps a
known problem?)
Regards,
-Frode
--
^ Frode Tennebø | email: frodet@nvg.org | Frode@IRC ^
| with Standard.Disclaimer; use Standard.Disclaimer; |
next reply other threads:[~2001-08-01 21:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 21:24 Frode Tennebø [this message]
2001-08-02 21:42 ` [linux-lvm] Re: Kernel Oops Frode Tennebø
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 6:49 [linux-lvm] Kernel oops Tracy R Reed
2003-09-16 13:19 ` Tracy R Reed
1999-11-29 17:19 [linux-lvm] kernel oops Rusty Wickell
1999-11-30 0:00 ` Heinz Mauelshagen
1999-11-23 16:47 Rusty Wickell
1999-11-19 21:35 Rusty Wickell
1999-11-19 22:58 ` Matthias G. Eckermann
1999-11-20 14:22 ` Sune Kirkeby
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=01080123240507.01440@leia \
--to=frodet@nvg.org \
--cc=linux-lvm@sistina.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.