From: "Russell McGuire" <rmcguire@videopresence.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: HDLC driver - dev_free_skb_irq causes Segfault
Date: Sat, 9 Feb 2008 18:32:16 -0800 [thread overview]
Message-ID: <00be01c86b8d$27c2fcb0$6405a8c0@absolut> (raw)
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
All,
So I am in the process of debugging my newly established HDLC driver.
More or less modeled after a simplified gianfar / ucc_geth idea.
However, after loading, etc. and using the following commands
-> insmod hdlc-8360.ko
-> sethdlc hdlc0 hdlc-eth
-> ifconfig hdlc0 up 192.168.1.100
All is well, and I am seeing IDL interrupts. Great.
Now I go to ping an address like,
ping 192.168.1.101
I can see that I get the start_xmit function, the IRQ from the QE comes back
and reports the TXBD as successfully sent.
Here is the problem, when I goto free the skb in the tx_handler, I get a
'Unable to Handle Kernel Paging Request for data at address 0x00000000'
Even though for the life of me, I can't see any pointers that are at address
zero.
I have checked the pointer value I am passing in, and indeed it is the exact
same pointer I am receiving from the original
start-xmit call..
Are we supposed to copy the skb? And free it immediately in the start_xmit?
Some special way to store the pointer?
I have tried
txbd->buf = skb->data;
txbd->buf = virt_to_phys(skb->data);
etc.. and various other ways to save that I have seen in the gianfar and
ucc_geth drivers.
My tx_sk_buff** is identical as alloced the same way.
Anyone have any ideas?
-Russ
[-- Attachment #2: Type: text/html, Size: 8796 bytes --]
next reply other threads:[~2008-02-10 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 2:32 Russell McGuire [this message]
2008-02-13 14:11 ` HDLC driver - dev_free_skb_irq causes Segfault Laurent Pinchart
2008-02-15 16:21 ` Jochen Friedrich
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='00be01c86b8d$27c2fcb0$6405a8c0@absolut' \
--to=rmcguire@videopresence.com \
--cc=linuxppc-embedded@ozlabs.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).