From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70: pcmcia oops (a real one! honest!)
Date: Wed, 28 May 2003 14:38:23 +1000 [thread overview]
Message-ID: <20030528043823.GA485@zip.com.au> (raw)
In-Reply-To: <20030528042610.GD6501@zip.com.au>
On Wed, May 28, 2003 at 02:26:10PM +1000, CaT wrote:
> removed my xircom pcmcia realport card and put in another. End result was
> total loss of ps2 keyboard functionality (everything else, inc the ps2 mouse
> still works). I then removed the xircom card. The following was in dmesg:
A bit more info:
lspci segfaults
cat /proc/pci segfaults
cat /proc/bus/pci/devices segfaults
cat /proc/bus/pci/02/00.* segfaults BUT that is only because it is 00.0
that is causing it. This represents the ethernet side of the card and 00.1
is fine.
also, processes hung on me. bash hung on exit and took screen with it. mutt
hung on exit also and took screen with it aswell.
on reboot init reported some hung processes and all up it all went
spaz on me with two of my partitions not being able to be unmounted
(prolly cos of the hung processes) and the e100 driver dieing in
e100_notify_reboot (or somesuch name). the laptop refused to reboot and
I had to powercycle.
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
next prev parent reply other threads:[~2003-05-28 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 4:26 2.5.70: pcmcia oops (a real one! honest!) CaT
2003-05-28 4:38 ` CaT [this message]
2003-05-29 8:02 ` Russell King
2003-05-29 21:21 ` Greg KH
2003-05-31 15:41 ` CaT
2003-06-02 21:05 ` Greg KH
2003-06-03 19:28 ` Greg KH
2003-06-05 4:24 ` CaT
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=20030528043823.GA485@zip.com.au \
--to=cat@zip.com.au \
--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