public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4 experiences
Date: Sun, 31 Aug 2003 14:33:27 +0100	[thread overview]
Message-ID: <20030831143327.B9032@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030831131313.GA1049@wiland.intern>; from berberic@fmi.uni-passau.de on Sun, Aug 31, 2003 at 03:13:13PM +0200

On Sun, Aug 31, 2003 at 03:13:13PM +0200, M G Berberich wrote:
> i tried 2.6.0-test on a laptop (Sony Vaio FX502, AMD Mobile Duron
> 1GHz)
> 
> With a PCMCIA-Modem (ELSA Microlink 56k MC Internet, a V.90 Modem) I
> have only 1/3 throughput with 2.6.0-test4 compared to a 2.4.X kernel
> (which gives the normal throughput for 56k modem).
> 
>      Yenta: CardBus bridge found at 0000:00:0a.0 [104d:80f6]
>      Yenta IRQ list 0008, PCI irq11
>      Socket status: 30000010
>      Yenta: CardBus bridge found at 0000:00:0a.1 [104d:80f6]
>      Yenta IRQ list 0008, PCI irq10
>      Socket status: 30000006
>      cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xd3fff 0xdc000-0xdffff 0xe4000-0xfffff
>      serial_cs: RequestIRQ: Unsupported mode

Make sure you have CONFIG_ISA=y in your kernel configuration.
However, I'm thinking that maybe if CONFIG_ISA is not set, we
shouldn't probe ISA IRQs in yenta_socket...

> pulling the card out I get
> 
>      Trying to free nonexistent resource <000002f8-000002ff>

Proper fix for this is behind a large pile of other interdependent patches.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2003-08-31 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31 13:13 2.6.0-test4 experiences M G Berberich
2003-08-31 13:33 ` Russell King [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=20030831143327.B9032@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox