From: Juan Quintela <quintela@mandrakesoft.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: pcmcia oops problem?
Date: 14 Mar 2002 19:40:54 +0100 [thread overview]
Message-ID: <m23cz3ro09.fsf@trasno.mitica> (raw)
In-Reply-To: <3C90BA11.40106@mandrakesoft.com> <m2henjruos.fsf@trasno.mitica> <200203141801.g2EI1sK00638@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200203141801.g2EI1sK00638@vindaloo.ras.ucalgary.ca>
>>>>> "richard" == Richard Gooch <rgooch@ras.ucalgary.ca> writes:
richard> Juan Quintela writes:
>> >>>>> "jeff" == Jeff Garzik <jgarzik@mandrakesoft.com> writes:
>>
jeff> Can you describe the pcmcia oops problem in detail?
jeff> What output do you get from a serial console?
>>
>> Ok, trying to get better message now.
richard> Can you:
richard> - capture the Oops and decode with ksymoops
stack overflow, when we got the Oops, we have already overwrote half
the memory, i.e. the stack trace makes no sense at all :(
richard> - make sure you always Cc: me on devfs-related problems (I nearly
richard> missed this one).
Not sure what is this one, and I am beggining to think that the
problem is some subtle thing in andrea_vm.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
prev parent reply other threads:[~2002-03-14 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:56 pcmcia oops problem? Jeff Garzik
2002-03-14 16:16 ` Juan Quintela
2002-03-14 18:01 ` Richard Gooch
2002-03-14 18:40 ` Juan Quintela [this message]
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=m23cz3ro09.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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.