From: peter konrad <kore@aon.at>
To: linux-kernel@vger.kernel.org
Subject: Problem sis 7001usb-controller & framebuffer, bug?
Date: Sat, 9 Jun 2001 22:22:19 +0200 [thread overview]
Message-ID: <01060922221900.01753@pc3workstation> (raw)
Hello!
I have a notebook with this sis 7001 usb-controller and sis 630
chipset.(shared memory 8mb), motherboard uniwill 340s2.
Kernel 2.2.x 2.4.1 -2.4.5
X-winows 3.x -4x.
Many low-cost notebooks have this chipset.
All works fine, like my usb-webcam, usb-scanner and my usb-zip-drive with
usb-ohci driver and the other required drivers, but only without framebuffer.
I need framebuffer,because there is no support from Xfree86 for my
Tft LCD yet.
When i use the shell,zip-drive works very stable, no errors.
When i use this frambuffer-support & X-Windows all works, but usb-devices
are crashes after short time off running..
When i use the X-server without framebuffer, i can only use 640x480 for
testing with bad display, but all usb devices works without any Errors and
very stable.
I have no Io-or Int. conflicts.
It looks like a timing problem for me, because of this problematic sis 7001,
shared memory and framebuffer.
I tested a lot, but no succes.
All devices working stable on my Destop-machines.
I don´t know, how i resolve this strange problem with using framebuffering
and usb.
Kernel-messages from my zip-drive with framebuffering
kernel: bread in fat_access failed
Jun 9 20:04:42 pc3workstation kernel: I/O error: dev 08:01, sector 120
Jun 9 20:04:42 pc3workstation kernel: bread in fat_access failed
Jun 9 20:04:42 pc3workstation kernel: I/O error: dev 08:01, sector 120
Jun 9 20:04:42 pc3workstation kernel: bread in fat_access failed
Jun 9 20:04:42 pc3workstation kernel: I/O error: dev 08:01, sector 23822
Jun 9 20:04:42 pc3workstation kernel: I/O error: dev 08:01, sector 23822
Jun 9 20:05:06 pc3workstation kernel: I/O error: dev 08:01, sector 1556
Kernel-messages from my mustek-scanner
Unable to handle kernel NULL pointer dereJun 7 13:58:21 pc3workstation
kernel: printing eip:
Jun 7 13:58:21 pc3workstation kernel: c01b8fed
Jun 7 13:58:21 pc3workstation kernel: *pde = 00000000
Jun 7 13:58:21 pc3workstation kernel: Oops: 0000
Jun 7 13:58:21 pc3workstation kernel: CPU: 0
Jun 7 13:58:21 pc3workstation kernel: EIP: 0010:[<c01b8fed>]
Jun 7 13:58:21 pc3workstation kernel: EFLAGS: 00010286
Jun 7 13:58:21 pc3workstation kernel: eax: 0000001c ebx: 000009fa ecx:
cd68Jun 7 13:58:21 pc3workstation kernel: esi: cd687f20 edi: cd687f30
ebp: 0000Jun 7 13:58:21 pc3workstation kernel: ds: 0018 es: 0018 ss: 0018
Jun 7 13:58:21 pc3workstation kernel: Process xsane (pid: 630,
stackpage=cd6870Jun 7 13:58:21 pc3workstation kernel: Stack: c01b9111
ce7993a0 000009fa cefd65cJun 7 13:58:21 pc3workstation kernel:
cd687f20 cd88c000 00000000 cd687f2Jun 7 13:58:21 pc3workstation kernel:
00000000 00000000 cd686000 cd687f2Jun 7 13:58:21 pc3workstation kernel:
Call Trace: [<c01b9111>] [<c01b9356>] [<dJun 7 13:58:21 pc3workstation
kernel:
Thanks
Ing.peter konrad
reply other threads:[~2001-06-09 20:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=01060922221900.01753@pc3workstation \
--to=kore@aon.at \
--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 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.