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]

Date:	Thu, 5 Apr 2007 19:54:58 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	Pat <patchu1@...oo.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!)

On Thu, 5 Apr 2007, Pat wrote:
> 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?

Indeed, yes, get its source and look to see what it's doing
with PageReserved - or mail it to me privately and I'll take
a look.  But my Google for fusedriver didn't show anything,
and clearly it has nothing to do with the FUSE filesystems.

Hugh
-
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/