linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Diehl <lists@mdiehl.de>
To: Jon Fairbairn <Jon.Fairbairn@cl.cam.ac.uk>
Cc: Russell King <rmk@arm.linux.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: Omnibook PCMCIA slots unusable after suspend.
Date: Tue, 16 Sep 2003 23:13:54 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0309140058440.16165-100000@notebook.home.mdiehl.de> (raw)
In-Reply-To: <7839.1063471929@cl.cam.ac.uk>


Sorry for the delay...

On Sat, 13 Sep 2003, Jon Fairbairn wrote:

> > I had a similar problem with my OB800. It turned out the
> > problem is the BIOS maps the yenta memory window into
> > legacy address range below 1MB.
> 
> This appears to be the correct diagnosis. I applied your
> patch to 2.4.22 and the Omnibook now correctly restarts the
> network after a suspend. Vielen dank!

You're welcome.

> What's the status of a patch like this? It's obviously of
> use to more than one person, and it took me a great deal of
> time to find you and your solution -- I suspect fainter
> hearted folk might just have given up and said "Linux
> doesn't work with this combination of hardware" which would
> have been a shame.

Well, I've sent it to lkml once or twice some years ago. It was apparently 
lost in the noise and I personally didn't care much resending it because 
nobody else reported a similar problem. So I've just included it in my 
local patchset - just the "fixed and forget because nobody else reports 
this problem" case ;-)

> I haven't tried it with 2.6 yet; I don't normally get into
> test kernels, but I might try out of curiosity. I'll post
> the result if anyone indicates that it's a worthwhile thing
> to do.

Right, except for some fuzz the patch should work with both 2.4 and 2.6 - 
at least it does for me. I'm not sure if this is the best possible way to 
work around the issue. But it does the job and I've taken considerable 
care to avoid breaking other boxes.

Of course I personally have no objections wrt. including it in the 
official tree. Russel, what do you think - do you want to apply it? Or 
shall I send it to Greg directly?

> > Yep, this is what happens fo me in the sitation above. And
> > the next time one inserts/ejects any card the box dies in
> > interrupt storm because the irq cannot be acknoledged.
> 
> I think I got that too, at least, reinserting the card caused
> a lockup.  With the patch applied I can eject and reinsert,
> which is fortunate because there seems to be another problem
> where the card switches off when I switch VCs, but it's hard
> to reproduce. (and inconvenient because /usr is on nfs on
> this machine)

No idea - sounds strange to me. No such problem here with any of 
serial_cs, pcnet_cs or orinoco_cs with my ob800 (neither 2.4 nor 2.6).

Martin


  reply	other threads:[~2003-09-16 21:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 21:22 Omnibook PCMCIA slots unusable after suspend Jon Fairbairn
2003-09-10 22:45 ` Russell King
2003-09-11 16:01   ` Jon Fairbairn
2003-09-11 21:18   ` Martin Diehl
2003-09-13 16:52     ` Jon Fairbairn
2003-09-16 21:13       ` Martin Diehl [this message]
2003-09-16 22:56         ` Russell King
2003-09-17 23:07           ` Jon Fairbairn

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.44.0309140058440.16165-100000@notebook.home.mdiehl.de \
    --to=lists@mdiehl.de \
    --cc=Jon.Fairbairn@cl.cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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).