mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter <pk@q-leap.com>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: pk@q-leap.com, linux-kernel@vger.kernel.org
Subject: Re: oops with e1000, ifenslave (bonding)
Date: Tue, 15 Apr 2003 12:47:59 +0200	[thread overview]
Message-ID: <16027.58207.975001.863568@q-leap.com> (raw)
In-Reply-To: <200304151220.36148.m.c.p@wolk-project.de>

Hello,

thanks for your quick response.  Using your patch on the version
5.0.43 driver gives me:

patching file e1000_main.c
Hunk #1 succeeded at 1035 (offset 72 lines).
Hunk #2 succeeded at 1103 (offset 72 lines).

don't know if your patch can be used on this source?

Anyways, after doing "ifenslave -d bond0 eth1 eth2" I get:

wait_on_irq, CPU 0:
irq:  0 [ 0 0 ]
bh:   1 [ 0 1 ]
Stack dumps:
CPU 1:00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
       00000000 00000002 01000000 c1c18740 c1c18740 00000000 c1c18640 f7e9d2a0
       c1c185c0 00000000 f5dc5520 00000000 00000000 00000000 00000003 00000000
Call Trace:    [<c015b6ec>] [<c015b788>] [<c015b808>] [<c015b990>] [<c015ba08>]
  [<c015ba64>] [<c015bd2c>] [<c015bd60>] [<c015bd94>] [<c015bdc8>] [<c015bdfc>]
  [<c015be38>] [<c015be74>] [<c015bf20>] [<c015bf54>] [<c015beec>]

CPU 0:f0cc7e64 c02beffd 00000000 00000000 00000000 c0109ffd c02bf012 f5de3ea0
       00000001 bffff9a8 c01e59f1 bffff9a8 bffff9a8 f0ccbec0 000001ff 0b043b40
       00000000 c01e5e01 f5de3ea0 bffff9a8 f0ee0000 bffff9a8 f0ccbec0 f0ee0000
Call Trace:    [<c0109ffd>] [<c01e59f1>] [<c01e5e01>] [<c0116855>] [<c01d73e3>]
  [<c0132ac8>] [<c0132ae9>] [<c0147a3a>] [<c0147d5f>] [<c0147d9a>] [<c01d4389>]
  [<c0147007>] [<c01089f7>]


wait_on_irq, CPU 0:
irq:  0 [ 0 0 ]
bh:   1 [ 0 1 ]
Stack dumps:
CPU 1:00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
       00000000 00000002 01000000 c1c18740 c1c18740 00000000 c1c18640 f7e9d2a0
       c1c185c0 00000000 f5dc5520 00000000 00000000 00000000 00000003 00000000
Call Trace:    [<c015b6ec>] [<c015b788>] [<c015b808>] [<c015b990>] [<c015ba08>]
  [<c015ba64>] [<c015bd2c>] [<c015bd60>] [<c015bd94>] [<c015bdc8>] [<c015bdfc>]
  [<c015be38>] [<c015be74>] [<c015bf20>] [<c015bf54>] [<c015beec>]

CPU 0:f0cc7e64 c02beffd 00000000 00000000 00000000 c0109ffd c02bf012 f5de3ea0
       00000001 bffff9a8 c01e59f1 bffff9a8 bffff9a8 f0ccbec0 000001ff 0b043b40
       00000000 c01e5e01 f5de3ea0 bffff9a8 f0ee0000 bffff9a8 f0ccbec0 f0ee0000
Call Trace:    [<c0109ffd>] [<c01e59f1>] [<c01e5e01>] [<c0116855>] [<c01d73e3>]
  [<c0132ac8>] [<c0132ae9>] [<c0147a3a>] [<c0147d5f>] [<c0147d9a>] [<c01d4389>]
  [<c0147007>] [<c01089f7>]


running ksymoops on this:


Warning (Oops_read): Code line not seen, dumping what data is available


Trace; c015b6ec <loadavg_read_proc+0/9c>
Trace; c015b788 <uptime_read_proc+0/80>
Trace; c015b808 <meminfo_read_proc+0/188>
Trace; c015b990 <version_read_proc+0/50>
Trace; c015ba08 <modules_read_proc+0/34>
Trace; c015ba64 <kstat_read_proc+0/2c8>
Trace; c015bd2c <devices_read_proc+0/34>
Trace; c015bd60 <interrupts_read_proc+0/34>
Trace; c015bd94 <filesystems_read_proc+0/34>
Trace; c015bdc8 <dma_read_proc+0/34>
Trace; c015bdfc <ioports_read_proc+0/3c>
Trace; c015be38 <cmdline_read_proc+0/3c>
Trace; c015be74 <locks_read_proc+0/78>
Trace; c015bf20 <swaps_read_proc+0/34>
Trace; c015bf54 <memory_read_proc+0/3c>
Trace; c015beec <execdomains_read_proc+0/34>
Trace; c0109ffd <__global_cli+bd/124>
Trace; c01e59f1 <get_modem_info+21/140>
Trace; c01e5e01 <rs_ioctl+8d/42c>
Trace; c0116855 <schedule+49d/560>
Trace; c01d73e3 <normal_poll+103/11f>
Trace; c0132ac8 <__free_pages+1c/20>
Trace; c0132ae9 <free_pages+1d/20>
Trace; c0147a3a <poll_freewait+3a/44>
Trace; c0147d5f <do_select+1eb/204>
Trace; c0147d9a <select_bits_free+a/10>
Trace; c01d4389 <tty_ioctl+371/3a8>
Trace; c0147007 <sys_ioctl+1bb/1f6>
Trace; c01089f7 <system_call+33/38>
Trace; c015b6ec <loadavg_read_proc+0/9c>
Trace; c015b788 <uptime_read_proc+0/80>
Trace; c015b808 <meminfo_read_proc+0/188>
Trace; c015b990 <version_read_proc+0/50>
Trace; c015ba08 <modules_read_proc+0/34>
Trace; c015ba64 <kstat_read_proc+0/2c8>
Trace; c015bd2c <devices_read_proc+0/34>
Trace; c015bd60 <interrupts_read_proc+0/34>
Trace; c015bd94 <filesystems_read_proc+0/34>
Trace; c015bdc8 <dma_read_proc+0/34>
Trace; c015bdfc <ioports_read_proc+0/3c>
Trace; c015be38 <cmdline_read_proc+0/3c>
Trace; c015be74 <locks_read_proc+0/78>
Trace; c015bf20 <swaps_read_proc+0/34>
Trace; c015bf54 <memory_read_proc+0/3c>
Trace; c015beec <execdomains_read_proc+0/34>
Trace; c0109ffd <__global_cli+bd/124>
Trace; c01e59f1 <get_modem_info+21/140>
Trace; c01e5e01 <rs_ioctl+8d/42c>
Trace; c0116855 <schedule+49d/560>
Trace; c01d73e3 <normal_poll+103/11f>
Trace; c0132ac8 <__free_pages+1c/20>
Trace; c0132ae9 <free_pages+1d/20>
Trace; c0147a3a <poll_freewait+3a/44>
Trace; c0147d5f <do_select+1eb/204>
Trace; c0147d9a <select_bits_free+a/10>
Trace; c01d4389 <tty_ioctl+371/3a8>
Trace; c0147007 <sys_ioctl+1bb/1f6>
Trace; c01089f7 <system_call+33/38>


2 warnings issued.  Results may not be reliable.



-- 
Peter Kruse <pk@q-leap.com>
Q-Leap Networks GmbH
+497071-703171


      reply	other threads:[~2003-04-15 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 10:10 Peter
2003-04-15 10:20 ` Marc-Christian Petersen
2003-04-15 10:47   ` Peter [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=16027.58207.975001.863568@q-leap.com \
    --to=pk@q-leap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    /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

all inboxes | Powered by JetHome®