From: Tom McNeal <tmcneal@mvista.com>
To: bridge@lists.osdl.org
Subject: [Bridge] stresstest.sh
Date: Fri, 16 Sep 2005 14:43:42 -0700 [thread overview]
Message-ID: <432B3C8E.1070503@mvista.com> (raw)
Hi -
When running the stress tests, after a few hours, a panic occurs
due to a kernel page fault for address 0x0 while executing one
of the brctl commands. We don't know which one, yet. Has anyone
run across this?
do_cpu invoked from kernel context! in traps.c:do_cpu, line 787:
...snip...
Process brctl (pid: 23999, stackpage=813d8000)
...snip...
note: brctl[23999] exited with preempt_count 2
Unable to handle kernel paging request at virtual address 00000000,
epc ==
801131e8, ra == 8011c5d8
Oops in fault.c:do_page_fault, line 213:
...etc....
This is basically in the 2.4.17 kernel, with some of the security
fixes.
Tom
--
Tom McNeal
MontaVista Software
408-992-4459
next reply other threads:[~2005-09-16 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 21:43 Tom McNeal [this message]
2005-09-16 22:18 ` [Bridge] stresstest.sh Stephen Hemminger
2005-09-19 15:49 ` Tom McNeal
2005-09-19 16:34 ` Stephen Hemminger
2005-09-21 16:37 ` Tom McNeal
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=432B3C8E.1070503@mvista.com \
--to=tmcneal@mvista.com \
--cc=bridge@lists.osdl.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