From: "René Rebe" <rene.rebe@gmx.net>
To: "René Rebe" <rene.rebe@gmx.net>
Cc: jsimmons@transvirtual.com, linux-kernel@vger.kernel.org,
ademar@conectiva.com.br, rolf@sir-wum.de,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: sis630 - help needed debugging in the kernel
Date: Sat, 16 Jun 2001 23:27:40 +0200 [thread overview]
Message-ID: <20010616232740.092475e2.rene.rebe@gmx.net> (raw)
In-Reply-To: <20010613232502.34fd0237.rene.rebe@gmx.net>
In-Reply-To: <20010613172320.306d5208.rene.rebe@gmx.net> <Pine.LNX.4.10.10106130952590.16375-100000@transvirtual.com> <20010613232502.34fd0237.rene.rebe@gmx.net>
Hi all!
On Wed, 13 Jun 2001 23:25:02 +0200
René Rebe <rene.rebe@gmx.net> wrote:
> Thanks for the quick reply!
>
> On Wed, 13 Jun 2001 09:54:21 -0700 (PDT)
> James Simmons <jsimmons@transvirtual.com> wrote:
>
> >
> > > I currently try to debug why the sisfb driver crashes my machine. (SIS 630
> > > based laptop - linux-2.4.5-ac13).
> >
> > You can do one of two things. Post both System.map and the complete oops
> > or you can run ksymoops on the oops. I can find the problem then. Thanks.
>
> ksymoops' output is attached.
Is there any result with this trace??
[...]
k33p h4ck1n6 René
--
René Rebe (Registered Linux user: #127875)
http://www.rene.rebe.myokay.net/
-Germany-
Anyone sending unwanted advertising e-mail to this address will be charged
$25 for network traffic and computing time. By extracting my address from
this message or its header, you agree to these terms.
next prev parent reply other threads:[~2001-06-16 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 15:23 René Rebe
2001-06-13 16:54 ` James Simmons
2001-06-16 21:27 ` René Rebe [this message]
2001-06-17 14:03 ` James Simmons
2001-06-18 18:32 ` René Rebe
2001-06-18 19:28 ` Paul Mundt
2001-06-18 21:58 ` James Simmons
2001-06-18 22:02 ` Paul Mundt
2001-06-18 21:01 ` René Rebe
2001-06-13 21:25 ` René Rebe
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=20010616232740.092475e2.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=ademar@conectiva.com.br \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rolf@sir-wum.de \
/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®