linux-kernel - Re: Invalid operand: kernel BUG at mm/rmap.c:434! and arch/i386/mm/highmem.c:42!)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <702654.55872.qm@web32508.mail.mud.yahoo.com>
Date:	Thu, 5 Apr 2007 11:05:10 -0700 (PDT)
From:	Pat <patchu1@...oo.com>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Invalid operand: kernel BUG at mm/rmap.c:434! and arch/i386/mm/highmem.c:42!)

--- Hugh Dickins <hugh@...itas.com> wrote:

> > I'm running kernel 2.6.9-22.ELsmp on dual Xeon
> 
> You'd do better to ask Red Hat support than here.

Thanks for the suggestion. I'll give them a shot too.

> Are the initial BUGs usually of that kind -
> rmap.c:434?

Yes. From the ones I've recorded so far, they all
begin with BUGs on rmap.c:434. 

> Do check your RAM (memtest86 overnight), maybe that

I ran memtest86+ (default test) overnight on the
system and it's still going strong, so I hope that
indicates the RAM is okay.

> PG_reserved bit is spurious.  But if rmap.c:434 is
> what's happening to you again and again, I'd wonder
> if a driver has been allocating a high-order page,
> marking the constituent pages as reserved, later
> clearing reserved from the first constituent page,
> then freeing the high-order page while leaving other
> reserved bits behind - I believe that could sneak a
> PageReserved page back into the 2.6.9 allocator.
> 
> If it were a particular application triggering this,
> it'd still be a kernel bug to allow it to happen.

Yes, there is a specific app which seems to be related
to the kernel panic. 

We use a few third party drivers on the system, so my
initial suspicions were on: 3w_9xxx(U) which is the
RAID card driver and fusedriver(U) which is a hardware
PCI card driver. 

The app which is kernel panicing is the only
application which makes use of the fusedriver. I'd
like to confirm my suspicions on the driver. Do you
have any suggestions on how I could trace the kernel
panic to that specific driver?

Thanks again for your input Hugh.

Pat

> > ------------[ cut here ]------------
> > kernel BUG at mm/rmap.c:434!
> > invalid operand: 0000 [#1]
> > SMP 
> > Modules linked in: fusedriver(U) md5 ipv6
> parport_pc
> > lp parport autofs4 i2c_dev i2c_core sunrpc
> > dm_multipath button battery ac uhci_hcd ehci_hcd
> e1000
> > floppy dm_snapshot dm_zero dm_mirror ext3 jbd
> dm_mod
> > 3w_9xxx(U) sd_mod scsi_mod
> > CPU:    5
> > EIP:    0060:[<c01518c6>]    Not tainted VLI
> > EFLAGS: 00010202   (2.6.9-22.ELsmp) 
> > EIP is at page_add_anon_rmap+0xe/0x66
> > eax: 40000964   ebx: c1800040   ecx: 090a100c  
> edx:
> > e5b5a544
> > esi: d1837e8c   edi: fff25508   ebp: c1800040  
> esp:
> > cf12ae40
> > ds: 007b   es: 007b   ss: 0068
> > Process check-enqueued- (pid: 17602,
> > threadinfo=cf12a000 task=f57577b0)
> > Stack: 40002067 80000000 c014d034 fff29000
> 40002025
> > 80000000 00000163 e5b5a544 
> >        f35b9080 00000000 fff25508 fff25508
> 090a100c
> > c014d0e2 cc5a2240 00000001 
> >        090a100c ffffffff ffffffff 00000000
> 00000000
> > 80000000 00000000 00000000 
> > Call Trace:
> >  [<c014d034>] do_anonymous_page+0x19c/0x1db
> >  [<c014d0e2>] do_no_page+0x6f/0x2f9
> >  [<c014d503>] handle_mm_fault+0xbd/0x175
> >  [<c011addb>] do_page_fault+0x1ae/0x5c6
> >  [<c014e58e>] vma_adjust+0x286/0x2d6
> >  [<c014e762>] vma_merge+0xe1/0x165
> >  [<c011d3d5>] finish_task_switch+0x30/0x66
> >  [<c02cf368>] schedule+0x844/0x87a
> >  [<c011ac2d>] do_page_fault+0x0/0x5c6
> >  [<c02d1bab>] error_code+0x2f/0x38
> > Code: 83 7b 10 00 74 0b 89 ca 89 d8 e8 fb fe ff ff
> 01
> > c6 89 d8 e8 ac df fe ff 5b 89 f0 5e c3 56 53 89 c3
> 8b
> > 00 8b 72 44 f6 c4 08 74 08 <0f> 0b b2 01 ce 52 2e
> c0
> > 85 f6 75 08 0f 0b b3 01 ce 52 2e c0 8b 
> 

____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time 
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/