From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: kraxel@bytesex.ORG (Gerd Knorr)
Cc: linux-kernel@vger.kernel.org
Subject: Re: yenta_socket hangs sager laptop in kernel 2.4.6
Date: Tue, 21 Aug 2001 02:52:24 +0400 (MSD) [thread overview]
Message-ID: <200108202252.CAA00742@mops.inr.ac.ru> (raw)
In-Reply-To: <slrn9o270m.rg.kraxel@bytesex.org> from "Gerd Knorr" at Aug 20, 1 06:45:06 pm
Hello!
> Same problem here. I've spend some time today to figure what is going
> on. Workaround:
>
> ---------------------------- cut here -----------------------------
> --- 2.4.9/drivers/pcmcia/yenta.c.fix Mon Aug 20 11:02:23 2001
> +++ 2.4.9/drivers/pcmcia/yenta.c Mon Aug 20 14:21:33 2001
> @@ -729,7 +729,7 @@
> if (type & IORESOURCE_IO) {
> align = 1024;
> size = 256;
> - min = PCIBIOS_MIN_IO;
> + min = 0x4000 /* PCIBIOS_MIN_IO */;
> max = 0xffff;
> }
>
> ---------------------------- cut here -----------------------------
I do not know how to thank you... You saved my life. :-)
How did you guess this?
> Looks like a ressource conflict to me. The kernel gives I/O ranges to
> the cardbus socket which it thinks are free but which are *not* free for
> some reason (and probably used for APM stuff). BIOS bug? PCI quirks
> time?
The same hardware is here, Mitac M722. :-) BTW what bios is installed
on your one?
Anyway, Windows with the _same_ bios manages to guess and to reserve
a few of ports tagged as some obscure "motherboard resources":
230-233, 398-399, 4d0-4d1, 1000-103f(!), 1400-140f(!) and 3810-381f.
yenta_socket eats ones marked with !. At least 1400 is really critical,
it is interface to SM mode. So, probably, more correct fix
is something sort of:
--- mitac-quirk.c
#include <linux/config.h>
#include <linux/version.h>
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/ioport.h>
#include <linux/init.h>
static __init int mitac_init(void)
{
/* No guesses */
request_region(0x230, 4, "Mitac");
/* Hmm... look at 0x64 @ 0:7.3, 0x398 is set there, no doubts.
* What is this? */
request_region(0x398, 2, "Mitac");
/* 82440MX: ELCR 1&2, Edge/Level Control Regs */
request_region(0x4D0, 2, "82440MX INT CNTRL");
/* No guesses */
request_region(0x1000, 0x40, "Mitac");
/* SMBus: selected with bits 4:15 at 0x90 @ 0:7.3 */
request_region(0x1400, 0x10, "82440MX SMBus");
/* No guesses. */
request_region(0x3810, 0x10, "Mitac");
return 0;
}
module_init(mitac_init);
/*
* Local variables:
* compile-command: "gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -c mitac.c"
* End:
*/
Alexey
next prev parent reply other threads:[~2001-08-21 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0107121802310.17665-100000@cobalt.deepthought.org>
2001-07-13 0:38 ` Linus Torvalds
2001-07-17 20:15 ` Martin Murray
2001-07-17 21:33 ` Linus Torvalds
2001-07-17 21:35 ` Martin Murray
2001-07-21 13:35 ` kuznet
2001-07-21 15:47 ` Ben Greear
2001-08-20 14:17 ` Gerd Knorr
2001-08-20 22:52 ` Alexey Kuznetsov [this message]
2001-08-21 20:37 ` Gerd Knorr
2001-08-22 17:35 ` yenta_socket hangs sager laptop in kernel 2.4.6-> PNPBIOS life saver Gunther Mayer
2001-07-12 18:36 yenta_socket hangs sager laptop in kernel 2.4.6 Martin Murray
2001-07-12 20:42 ` Linus Torvalds
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=200108202252.CAA00742@mops.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=kraxel@bytesex.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 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®