From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: quintela@mandrakesoft.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: pcmcia oops problem?
Date: Thu, 14 Mar 2002 09:56:17 -0500 [thread overview]
Message-ID: <3C90BA11.40106@mandrakesoft.com> (raw)
Can you describe the pcmcia oops problem in detail?
What output do you get from a serial console?
what do you mean, oops got infinite trace? were there (a) many oops or
(b) one oops with long trace
what do you mean, double fix of /dev/XXXXX name?
is pcmcia-cs creating and removing /dev entries too?
Jeff
next reply other threads:[~2002-03-14 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:56 Jeff Garzik [this message]
2002-03-14 16:16 ` pcmcia oops problem? Juan Quintela
2002-03-14 18:01 ` Richard Gooch
2002-03-14 18:40 ` Juan Quintela
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=3C90BA11.40106@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quintela@mandrakesoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.