From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Ben Collins <bcollins@debian.org>
Cc: dale_d@telusplanet.net, linux-kernel@vger.kernel.org
Subject: Re: ieee1394 subsystem causes segfaults
Date: Fri, 19 Dec 2003 09:03:08 -0800 [thread overview]
Message-ID: <20031219090308.6966e068.rddunlap@osdl.org> (raw)
In-Reply-To: <20031217141057.GC551@phunnypharm.org>
On Wed, 17 Dec 2003 09:10:57 -0500 Ben Collins <bcollins@debian.org> wrote:
| > 5. no oops message
|
| Not sure how things can segv without some sort of kernel message. Are
| you sure it didn't print anything at all?
What messages are there then? You should post the kernel log
showing the problem(s). (Yes, I looked at the original posting.)
I have seen kernel bugs cause user space segfaults, so maybe
it's an app that is having the segfault.
--
~Randy
MOTD: Always include version info.
prev parent reply other threads:[~2003-12-19 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 14:10 Dale K Dicks
2003-12-17 14:10 ` Ben Collins
2003-12-19 17:03 ` Randy.Dunlap [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=20031219090308.6966e068.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=bcollins@debian.org \
--cc=dale_d@telusplanet.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 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®