From: Tim Waugh <twaugh@redhat.com>
To: Giacomo Catenazzi <cate@debian.org>
Cc: Mailing List Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.2 OOPS on parport loading [pci_register_driver] // parport slow
Date: Fri, 23 Feb 2001 09:33:58 +0000 [thread overview]
Message-ID: <20010223093358.C1147@redhat.com> (raw)
In-Reply-To: <3A96154F.8A791FF6@debian.org>
In-Reply-To: <3A96154F.8A791FF6@debian.org>; from cate@debian.org on Fri, Feb 23, 2001 at 08:46:23AM +0100
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
On Fri, Feb 23, 2001 at 08:46:23AM +0100, Giacomo Catenazzi wrote:
> After writing the report, I disabled parport resources in BIOS
> and I maked:
>
> cate3:~# modprobe parport_pc
> Unable to handle kernel paging request at virtual address
> c3a5f640
> printing eip:
> .....
> Segmentation fault
> cate3:~#
Please try 2.4.2-ac2, which should have a fix for this.
> In 2.4.x (and also in 2.3.x) the parport is slow!
Please describe what you mean here. Is it consistently slow, or does
it print fine for a bit and then stall?
> cate3:~# cat /proc/interrupts
It is expected behaviour that the interrupt handler isn't registered
until you actually need it. Print something and take a look at
/proc/ioports and you will see it.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-02-23 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 7:46 2.4.2 OOPS on parport loading [pci_register_driver] // parport slow Giacomo Catenazzi
2001-02-23 9:33 ` Tim Waugh [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=20010223093358.C1147@redhat.com \
--to=twaugh@redhat.com \
--cc=cate@debian.org \
--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.