linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@transvirtual.com>
To: "René Rebe" <rene.rebe@gmx.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Ademar de Souza Reis Jr." <ademar@conectiva.com.br>,
	Rolf Schillinger <rolf@sir-wum.de>,
	Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: sis630 - help needed debugging in the kernel
Date: Wed, 13 Jun 2001 09:54:21 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10106130952590.16375-100000@transvirtual.com> (raw)
In-Reply-To: <20010613172320.306d5208.rene.rebe@gmx.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1863 bytes --]


> 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.

> On my serial-console I get:
> [...]
> sisfb: framebuffer at 0xe0000000, mapped to 0xcb800000, size 16384k
> sisfb: MMIO at 0xefce0000, mapped to 0xcc801000, size 128k
> sisfb: encountered LCD # debug output by me
> sisfb: fall back to 1024x768 # debug ouput by me
> sisfb: LCD mode # debug output by me
> sisfb: mode is 800x600x8, linelength=800
> [...]
> Unable to handle kernel paging request at virtual address cc800180
> [oops]
> 
> This happens in the method: register_framebuffer called from sisfb_init.
> 
> I compared the sisfb_init with other framebuffer drivers and can't find what is wrong.
> (I normally don't do kernel hacking...). What does the kernel try to do with the
> _io-memory_, mapped around line 2230 in sis_main.c? - Must the memory reqeuested or
> mapped in an other way?
> 
> Another strange thing is, that the code seems to work for some people ...
> 
> I would be nice if anyone could give me a hint - because the sis-drivers (kernel and X)
> doesn't work for many people ...
> 
> 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.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2001-06-13 16:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 15:23 sis630 - help needed debugging in the kernel René Rebe
2001-06-13 16:54 ` James Simmons [this message]
2001-06-16 21:27   ` René Rebe
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=Pine.LNX.4.10.10106130952590.16375-100000@transvirtual.com \
    --to=jsimmons@transvirtual.com \
    --cc=ademar@conectiva.com.br \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.rebe@gmx.net \
    --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;
as well as URLs for NNTP newsgroup(s).