From: Dave Jones <davej@codemonkey.org.uk>
To: jgarzik@pobox.com, linux.nics@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: e100 doing bad things in 2.5.44.
Date: Fri, 25 Oct 2002 19:53:16 +0100 [thread overview]
Message-ID: <20021025185316.GA10278@suse.de> (raw)
Oct 25 18:38:12 tetrachloride kernel: Debug: sleeping function called from illegal context at mm/slab.c:1384
Oct 25 18:38:12 tetrachloride kernel: Call Trace:
Oct 25 18:38:12 tetrachloride kernel: [<c011dd94>] __might_sleep+0x54/0x58
Oct 25 18:38:12 tetrachloride kernel: [<c01403ae>] kmalloc+0x5a/0x314
Oct 25 18:38:12 tetrachloride kernel: [<c017e2da>] proc_create+0x76/0xcc
Oct 25 18:38:12 tetrachloride kernel: [<c017e3fb>] proc_mkdir+0x17/0x40
Oct 25 18:38:12 tetrachloride kernel: [<c010a4c3>] register_irq_proc+0x6b/0xb0
Oct 25 18:38:12 tetrachloride kernel: [<c010a2ba>] setup_irq+0x166/0x174
Oct 25 18:38:12 tetrachloride kernel: [<c02b9424>] e100intr+0x0/0x308
Oct 25 18:38:12 tetrachloride kernel: [<c0109b48>] request_irq+0x88/0xa4
Oct 25 18:38:12 tetrachloride kernel: [<c02b84fa>] e100_open+0x106/0x188
Oct 25 18:38:12 tetrachloride kernel: [<c02b9424>] e100intr+0x0/0x308
Oct 25 18:38:12 tetrachloride kernel: [<c03a5080>] dev_open+0x50/0xb0
Oct 25 18:38:12 tetrachloride kernel: [<c03a65e1>] dev_change_flags+0x51/0x104
Oct 25 18:38:12 tetrachloride kernel: [<c03decc5>] devinet_ioctl+0x331/0x6d8
Oct 25 18:38:12 tetrachloride kernel: [<c03e1bc7>] inet_ioctl+0xab/0xf0
Oct 25 18:38:12 tetrachloride kernel: [<c039e6a1>] sock_ioctl+0xfd/0x160
Oct 25 18:38:12 tetrachloride kernel: [<c0162cfb>] sys_ioctl+0x27f/0x2f5
Oct 25 18:38:12 tetrachloride kernel: [<c0108029>] error_code+0x2d/0x38
Oct 25 18:38:12 tetrachloride kernel: [<c01075c7>] syscall_call+0x7/0xb
Another weirdo.. Check out the Speed..
Oct 25 18:38:12 tetrachloride kernel: Intel(R) PRO/100 Network Driver - version 2.1.24-k1
Oct 25 18:38:12 tetrachloride kernel: Copyright (c) 2002 Intel Corporation
Oct 25 18:38:12 tetrachloride kernel:
Oct 25 18:38:12 tetrachloride kernel: e100: selftest OK.
Oct 25 18:38:12 tetrachloride kernel: e100: eth0: Intel(R) PRO/100 VE Network Connection
Oct 25 18:38:12 tetrachloride kernel: Mem:0xfeafc000 IRQ:20 Speed:0 Mbps Dx:N/A
Oct 25 18:38:12 tetrachloride kernel: Hardware receive checksums enabled
--
| Dave Jones. http://www.codemonkey.org.uk
next reply other threads:[~2002-10-25 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 18:53 Dave Jones [this message]
2002-10-26 21:17 ` e100 doing bad things in 2.5.44 Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-10-27 4:30 Feldman, Scott
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=20021025185316.GA10278@suse.de \
--to=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
/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.