linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jim Deas" <jdeas0648@jadsystems.com>
To: <linux-kernel@vger.kernel.org>
Date: Tue, 24 Feb 2004 05:58:10 -0800	[thread overview]
raw)

Can someone point me in the right direction. 
I am getting a oops on a driver I am porting from 2.4 to 2.6.2 kernel. 
I have expanded the file_operations structures and have a driver that loads and inits the hardware but when I call the open function I get an oops. The best I can track it is 

EIP 0060:[c0188954] 
chrdev_open +0x104 

What is the best debug tool to put this oops information in clear sight? It appears to never get to my modules open routine so I am at a debugging crossroad. What is the option on a kernel compile to get the compile listing so I can see what is at 0x104 in this block of code?



             reply	other threads:[~2004-02-24 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 13:58 Jim Deas [this message]
2004-02-24 14:44 ` your mail Richard B. Johnson

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=200402240558.AA3585540272@jadsystems.com \
    --to=jdeas0648@jadsystems.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;
as well as URLs for NNTP newsgroup(s).