mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: markw@osdl.org
To: linux-lvm@sistina.com
Cc: linux-kernel@vger.kernel.org
Subject: linux-2.6.0-test9 oops with lvm2
Date: Tue, 28 Oct 2003 12:00:43 -0800 (PST)	[thread overview]
Message-ID: <200310282000.h9SK0ko25805@mail.osdl.org> (raw)

I've got the following oops with pdflush on 2.6.0-test9.  I have a
52 disk LVM2 (v2.00.07) volume attached through a pair of Adaptec raid
controllers. It appears to oops after I've created an ext2 filesystem on
the volume and attempt to mount it.  I wonder if it might be device
manager related since I see dm_request in the call trace. If there's any
more information I can provide, let me know.

Thanks!

Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:                                                                
c0146797      
*pde = 37c83001
*pte = 00000000
Oops: 0000 [#1]
CPU:    0      
EIP:    0060:[<c0146797>]    Not tainted
EFLAGS: 00010082                        
EIP is at page_address+0x17/0xb0
eax: 00000000   ebx: 00000000   ecx: 00000004   edx: f7f68160
esi: f6a38c00   edi: 00000000   ebp: 00000001   esp: f7d91b54
ds: 007b   es: 007b   ss: 0068                               
Process pdflush (pid: 35, threadinfo=f7d90000 task=f7d95310)
Stack: 00000001 f6df3f00 f6a38c00 00000000 00000001 c0219dbc 00000000 cab3cc20 
       00000020 00000000 00002f30 00000000 00000000 00000008 00000010 f6df3f00 
       f6a38c00 00000010 cab3caa0 00000010 c021a2cf f6a38c00 cab3cc20 f7fc7260 
Call Trace:                                                                    
 [<c0219dbc>] __make_request+0x1fc/0x5a0
 [<c021a2cf>] generic_make_request+0x16f/0x1f0
 [<c02920ad>] __map_bio+0x3d/0x100            
 [<c0292459>] __clone_and_map+0x1d9/0x310
 [<c011e1a0>] autoremove_wake_function+0x0/0x50
 [<c0292618>] __split_bio+0x88/0x100           
 [<c0292753>] dm_request+0xc3/0xe0  
 [<c021a2cf>] generic_make_request+0x16f/0x1f0
 [<c011e1a0>] autoremove_wake_function+0x0/0x50
 [<c021a3a4>] submit_bio+0x54/0xa0             
 [<c017a0de>] mpage_bio_submit+0x2e/0x40
 [<c017ab26>] mpage_writepage+0x246/0x790
 [<c015af83>] __find_get_block+0x73/0x100
 [<c015b107>] __bread+0x27/0x50          
 [<c01947d8>] ext2_get_inode+0xe8/0x140
 [<c017b30c>] mpage_writepages+0x29c/0x2db
 [<c0193920>] ext2_get_block+0x0/0x410    
 [<c0193f3f>] ext2_writepages+0x1f/0x30
 [<c0193920>] ext2_get_block+0x0/0x410 
 [<c013f7ee>] do_writepages+0x1e/0x40 
 [<c0179574>] __sync_single_inode+0xc4/0x220
 [<c017992c>] sync_sb_inodes+0x1ac/0x270    
 [<c0179a59>] writeback_inodes+0x69/0xa0
 [<c013f5f8>] wb_kupdate+0xe8/0x160     
 [<c013fc00>] __pdflush+0xd0/0x1c0 
 [<c013fcf0>] pdflush+0x0/0x20    
 [<c013fcff>] pdflush+0xf/0x20
 [<c013f510>] wb_kupdate+0x0/0x160
 [<c01072a4>] kernel_thread_helper+0x0/0xc
 [<c01072a9>] kernel_thread_helper+0x5/0xc
                                          
Code: 8b 03 a9 00 01 00 00 75 30 8b 0d 6c b3 42 c0 29 cb c1 fb 03 

-- 
Mark Wong - - markw@osdl.org
Open Source Development Lab Inc - A non-profit corporation
12725 SW Millikan Way - Suite 400 - Beaverton, OR 97005
(503) 626-2455 x 32 (office)
(503) 626-2436      (fax)

                 reply	other threads:[~2003-10-28 20:00 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=200310282000.h9SK0ko25805@mail.osdl.org \
    --to=markw@osdl.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®