From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Rainer Mager <rmager@vgkk.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is this kernel related (signal 11)?
Date: Mon, 22 Jan 2001 08:53:13 +0100 (MET) [thread overview]
Message-ID: <200101220753.IAA12360@cave.bitwizard.nl> (raw)
In-Reply-To: <NEBBJBCAFMMNIHGDLFKGOEJOCNAA.rmager@vgkk.com> from Rainer Mager at "Jan 22, 2001 02:17:53 pm"
Rainer Mager wrote:
> that it is likely a hardware or kernel problem. So, my question is,
> how can I pin point the problem? Is this likely to be a kernel
> issue?
No, not hardware. No not kernel.
Harware problems are normally not reproducable. Can you attach a
debugger to your X server, and catch it when things go bad? (And
give the Xfree86 people a backtrace)
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-22 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 22:27 [patch] smbfs cache rewrite for 2.4.1-pre Urban Widmark
2001-01-22 5:17 ` Is this kernel related (signal 11)? Rainer Mager
2001-01-22 7:34 ` David Woodhouse
2001-01-22 8:03 ` Rainer Mager
2001-01-23 2:47 ` David Ford
2001-01-23 8:37 ` Rainer Mager
2001-01-24 0:56 ` Rainer Mager
2001-01-25 0:45 ` Rainer Mager
2001-01-22 7:53 ` Rogier Wolff [this message]
2001-01-22 21:47 ` Russell King
2001-01-23 0:15 ` Paul Jakma
2001-01-22 14:27 ` Barry K. Nathan
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=200101220753.IAA12360@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rmager@vgkk.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.