From: Bryan Batten <BryanBatten@sbcglobal.net>
To: linux-kernel@vger.kernel.org
Cc: "Carl-Daniel Hailfinger@sbcglobal.net"
<c-d.hailfinger.kernel.2004@gmx.net>
Subject: kmalloc oops
Date: Sun, 18 Mar 2007 10:41:55 -0700 [thread overview]
Message-ID: <45FD79E3.5050004@sbcglobal.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Hi,
I'm working on a driver which currently is a real memory hog. As a
result, it seems to stress other system components, one of which seems
to be the forcedeth ethernet driver.
The attached file has the oops trace that was recently generated. I
thought you might be interested in taking a look.
--
Bryan
----------------------------------------------------------------------
"You're tensing up, Arthur! The trick is to leap *before* you look!"
The Tick, ca. 1995
----------------------------------------------------------------------
[-- Attachment #2: forcedeth.oops --]
[-- Type: text/plain, Size: 1439 bytes --]
ksymoops 2.4.9 on i686 2.4.34. Options used
-V (default)
-k /var/log/ksymoops/20070317111830.ksyms (specified)
-l /var/log/ksymoops/20070317111830.modules (specified)
-o /lib/modules/2.4.34/ (default)
-m /boot/System.map-2.4.34 (default)
Adhoc c01380d0 <__wait_on_buffer+50/80>
Adhoc c0138362 <wait_for_buffers+82/90>
Adhoc c0138393 <wait_for_locked_buffers+23/40>
Adhoc c0138415 <sync_buffers+65/70>
Adhoc c0138565 <fsync_dev+55/60>
Adhoc c01a8eb9 <go_sync+169/170>
Adhoc c01a8f82 <do_emergency_sync+c2/d0>
Adhoc c01178d3 <panic+113/130>
Adhoc c011acf0 <do_exit+240/260>
Adhoc c0114090 <do_page_fault+0/577>
Adhoc c01075b2 <die+72/80>
Adhoc c01143a5 <do_page_fault+315/577>
Adhoc c022eae0 <nf_hook_slow+b0/170>
Adhoc c02375fc <ip_local_deliver+1ac/1e0>
Adhoc c0237a00 <ip_local_deliver_finish+0/180>
Adhoc c0237d29 <ip_rcv_finish+1a9/200>
Adhoc c0237b80 <ip_rcv_finish+0/200>
Adhoc c0114090 <do_page_fault+0/577>
Adhoc c0107004 <error_code+34/3c>
Adhoc c012eb14 <kmalloc+b4/120>
Adhoc c0226149 <netif_rx+79/170>
Adhoc c0222011 <alloc_skb+b1/1c0>
Adhoc e088c7df <[forcedeth]nv_alloc_rx+ef/130>
Adhoc e088dffb <[forcedeth]nv_nic_irq+5b/140>
Adhoc c010862d <handle_IRQ_event+3d/70>
Adhoc c01087db <do_IRQ+6b/b0>
Adhoc c01052e0 <default_idle+0/30>
Adhoc c010aa18 <call_do_IRQ+5/d>
Adhoc c01052e0 <default_idle+0/30>
Adhoc c0105306 <default_idle+26/30>
Adhoc c0105382 <cpu_idle+42/60>
Adhoc c0105000 <_stext+0/0>
reply other threads:[~2007-03-18 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45FD79E3.5050004@sbcglobal.net \
--to=bryanbatten@sbcglobal.net \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--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 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.