All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel freeze when writing e1000 driver
Date: Tue, 26 Feb 2013 12:01:21 -0500	[thread overview]
Message-ID: <3872.1361898081@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 26 Feb 2013 11:19:18 -0500." <CANSQQCKRf_m309juTFHpjQ6yeBSbf_hzP_D5m2XyQhUpc=qJrw@mail.gmail.com>

On Tue, 26 Feb 2013 11:19:18 -0500, Phani Vadrevu said:
> I am writing a network driver for the e1000 card. While doing the
> receive part, I saw that the kernel freezes whenever it reaches the
> netif_rx(skb) call. I was able to reproduce the same error when using
> a bare bones driver where I hard codde the skb data.

There's a known-working driver in the kernel source tree for this
device already.  Start by looking at what data it's placed in the
skb when it calls that routine, and how it differs from what you filled in.

For bonus points - lose the 'unsigned char t[]' array and replace
it with a bunch of explicit 'skb->foo = bar' statements.  In particular,
that assures that you haven't missed a 0x15 27 bytes into the array,
or failed to allow alignment padding bytes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130226/d590311a/attachment.bin 

      parent reply	other threads:[~2013-02-26 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 16:19 Kernel freeze when writing e1000 driver Phani Vadrevu
2013-02-26 16:49 ` Jonathan Neuschäfer
2013-02-26 17:01 ` Valdis.Kletnieks at vt.edu [this message]

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=3872.1361898081@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.