From: Aldy Hernandez <aldyh@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: partial oops on 2.6.6-bk9 (netconsole + tulip dmfe ethernet)
Date: Mon, 24 May 2004 08:24:31 -0400 [thread overview]
Message-ID: <20040524122431.GA3732@redhat.com> (raw)
Hi folks.
I'm trying to track down a kernel lockup on my box. What looked like
a FC2 issue, seems like an actual kernel problem. My box is dying
after 2 days of uptime.
I've enabled nmi_watchdog and netconsole to track the problem. What I
get looks like a partial Oops, or something quite unusable:
Unable to handle kernel paging request at virtual address 8cffffe8
printing eip:
c017bff0
*pde = 00000000
Oops: 0000 [#1]
SMP
No stack trace. No register dump. Nothing.
I have compiled the kernel with debugging, and the offended code is
here:
(gdb) l *0xc017bff0
0xc017bff0 is in sys_poll (fs/select.c:517).
512 err = -EFAULT;
513 while(walk != NULL) {
514 struct pollfd *fds = walk->entries;
515 int j;
516
517 for (j=0; j < walk->len; j++, ufds++) {
518 if(__put_user(fds[j].revents, &ufds->revents))
519 goto out_fds;
520 }
521 walk = walk->next;
My box is a P4 with a Tulip/Davicom (dmfe.o) network card. I have
noticed that the CONFIG_NET_POLL_CONTROLLER code was recently added to
the dmfe.c driver, so I'm wondering if this particular Oops is due to
the driver, and not the actual problem I'm chasing down.
My kernel parameters are:
kernel /bzImage ro root=LABEL=/ rhgb quiet vdso=0 netconsole=6665@172.31.1.50/eth0,6666@172.31.1.137/00:30:65:02:c4:c3 nmi_watchdog=1
I'm not very kernel savvy, so any pointers would be greatly
appreciated. Perhaps I should try configuring a serial console?
How can I be of use in helping to track down this problem? BTW, 2.4.x
worked fine with my box.
Cheers.
Aldy
reply other threads:[~2004-05-24 12:24 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=20040524122431.GA3732@redhat.com \
--to=aldyh@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox