public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pat <patchu1@yahoo.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Invalid operand: kernel BUG at mm/rmap.c:434! and arch/i386/mm/highmem.c:42!)
Date: Mon, 9 Apr 2007 11:06:54 -0700 (PDT)	[thread overview]
Message-ID: <593671.91760.qm@web32503.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704051949280.20591@blonde.wat.veritas.com>

--- Hugh Dickins <hugh@veritas.com> wrote:
> > 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
> 


Sorry for the late reply, I was on vacation with the
family for a few days.

fusedriver is a driver for a customized fpga pci card
used in our systems. I'm not sure how open the
manufacturer will be in sending me the source for the
drivers. I'll contact them though to get their input,
specifically on their use of PageReserved. 

Thanks,
Pat


 
____________________________________________________________________________________
Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

  reply	other threads:[~2007-04-09 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05  0:49 Invalid operand: kernel BUG at mm/rmap.c:434! and arch/i386/mm/highmem.c:42!) Pat
2007-04-05 16:26 ` Hugh Dickins
2007-04-05 18:05   ` Pat
2007-04-05 18:54     ` Hugh Dickins
2007-04-09 18:06       ` Pat [this message]
     [not found] <fa.UqD3AUpVhpmkJHPiQ1o5eUzIrx0@ifi.uio.no>
2007-04-06 15:57 ` Robert Hancock

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=593671.91760.qm@web32503.mail.mud.yahoo.com \
    --to=patchu1@yahoo.com \
    --cc=hugh@veritas.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox