mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Satchell <spamfilter@fluent2.pyramid.net>
To: linux-kernel@vger.kernel.org
Subject: Toshiba PCToPIC97 PC Card freeze in 2.4.18
Date: Sun, 16 Jun 2002 21:51:19 -0700	[thread overview]
Message-ID: <5.1.0.14.0.20020616212259.00a8b110@fluent2.pyramid.net> (raw)
In-Reply-To: <1024271844.1476.26.camel@sinai>

All:

I'm at my wit's end.  I have a Toshiba Satellite 2545XCDT which has a PC 
Card adapter.  I have been happily running this laptop with a 2.2.16 kernel 
without problem.  Today, when trying to upgrade to a 20GB hard disk and a 
2.4.18 kernel, the box would freeze when trying to start the PCMCIA 
service.  Here is the message that I get on the screen:

PCI:  No IRQ known for interrupt pin A of device 00:13:0.  Please try using 
pci=biosirq
PCI:  No IRQ known for interrupt pin B of device 00:13.0.  Please try using 
pci=biosirq
Yenta IRQ list 06b8 PCI irq 0
Socket status: 30000007

and the system is completely frozen at that point -- even CTRL-ALT-DEL 
doesn't work.  (The soft power switch does, which tells me that NMI 
interrupts get through, but nothing else.)  As you might guess, SysRq 
didn't work, either.  Only powering off would allow me to restart the system.

When I recompile the kernel to not make PCMCIA a module, there is NO 
message, just the system freeze.

Nothing interesting shows up in syslog.

Probing the /proc filesystem, I find that under 2.2.16 there is a character 
device 254 labeled PCMCIA; in the 2.4.18 kernel I see no device 254 or any 
device with the label PCMCIA.  Granted, in the case of 2.2.16 the various 
modules successfully loaded, so they may have advertised device 254, 
whereas on the 2.4.18 kernel the failure kept the device from being advertised.

Dumping /proc/pci, I see device 19 (0x13) listed but completely different 
capabilities advertised.  Under 2.2.16, I see "Slow devsel.  Fast 
back-to-back capable.  Master Capable.  No bursts.  Min Gnt=128.Max 
lat=4."  The same device under 2.4.18 reports "Non-prefetchable 32 bit 
memory at 0x100000000 [0x100000fff]."  Other PCI devices have reports that 
differ in format but not significantly in the amount of and values in content.

I even went so far as to download the latest version 
(pcmcia-cs-3.1.34.tar.gz) of the PCMCIA stuff from SourceForge, compiled it 
all, and ended up with exactly the same results.  So I'm beginning to 
believe that it's not the PCMCIA/PCCard software.

I checked the kernel archives for any mention of this problem, and the 
closest I could find was a complaint regarding an IBM ThinkPad.  Ditto 
checking the bug list for the project on SourceForge.  Nothing on Toshiba

I put the old hard drive back into the laptop so I can get some work done, 
but I still have all the stuff on the new drive.

The distributions involved are Red Hat 7.0 and Red Hat 7.3.

Where to "try using pci=biosirq"?  I tried adding it to the boot sequence, 
with no result.

I'm stumped.  Any suggestions where to start looking?


Stephen Satchell


  parent reply	other threads:[~2002-06-17  4:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 19:21 [PATCH] 2.4-ac: sparc64 support for O(1) scheduler Robert Love
2002-06-14  4:25 ` David S. Miller
2002-06-14 17:32   ` Robert Love
2002-06-15 13:22     ` David S. Miller
2002-06-20 19:42       ` Alan Cox
2002-06-16 15:19     ` Ingo Molnar
2002-06-16 17:00       ` [patch] 2.4.19-pre10-ac2: O(1) scheduler merge, -A3 Ingo Molnar
2002-06-16 23:57         ` Robert Love
2002-06-17  0:13           ` J.A. Magallon
2002-06-17  4:28             ` Ingo Molnar
2002-06-17  0:15           ` Robert Love
2002-06-17  3:49             ` Ingo Molnar
2002-06-17  3:57               ` Robert Love
2002-06-17  4:07                 ` Ingo Molnar
2002-06-17  4:02               ` Robert Love
2002-06-17  4:26                 ` Ingo Molnar
2002-06-17  4:49                 ` [patch] 2.5.22 current scheduler bits #1 Ingo Molnar
2002-06-17  3:24           ` [patch] 2.4.19-pre10-ac2: O(1) scheduler merge, -A3 Ingo Molnar
2002-06-17  3:35             ` Robert Love
2002-06-17  4:01               ` Ingo Molnar
2002-06-17  7:50             ` Zwane Mwaikambo
2002-06-17  8:32               ` Ingo Molnar
2002-06-17  8:23                 ` Zwane Mwaikambo
2002-06-17  9:00                   ` Ingo Molnar
2002-06-17  9:34                     ` Zwane Mwaikambo
2002-06-18  7:16                     ` William Lee Irwin III
2002-06-19  1:05                       ` Matthew Dobson
2002-06-20 20:22                         ` Andrew Theurer
2002-06-24  0:16                       ` Martin J. Bligh
2002-06-17 16:26             ` Rusty Russell
2002-06-17  4:51           ` Stephen Satchell [this message]
2002-06-16 23:45       ` [PATCH] 2.4-ac: sparc64 support for O(1) scheduler Robert Love
2002-06-17  5:28         ` David S. Miller
2002-06-17 21:18           ` Robert Love
2002-06-14 22:00   ` Thomas Duffy
2002-06-15 13:35     ` David S. Miller

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=5.1.0.14.0.20020616212259.00a8b110@fluent2.pyramid.net \
    --to=spamfilter@fluent2.pyramid.net \
    --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®