From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Derrik Pates <dpates@dsdk12.net>,
Stefan Piger <piger@rvs.uni-hannover.de>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Again with the firewire
Date: Thu, 22 Nov 2001 19:21:11 +0100 [thread overview]
Message-ID: <20011122182111.9961@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111220058320.14868-100000@andromeda.dsdk12.net>
>
>I actually just had the same thing happen, only the entire console froze,
>X and all. I don't know if the kernel was still working or not, I didn't
>have another machine connected at the time. However, this is actually an
>improvement for me - the ohci1394 module doesn't lock the PMU up and cause
>the system to suddenly shutdown (this is a FireWire iBook). If I boot the
>system with the FireWire device - a QPS CD-RW drive - plugged in, all is
>fine.
In Stefan's case, it appears to be the transmit DMA of the chip stalling
for some unknown reason. I suggest moving that discussion to the
linux1394-devel list as I really don't know what may be going on.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-22 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 7:15 Again with the firewire Stefan Piger
2001-11-22 8:28 ` Derrik Pates
2001-11-22 11:00 ` benh
2001-11-22 15:18 ` Derrik Pates
2001-11-22 18:21 ` Benjamin Herrenschmidt [this message]
2001-11-24 2:08 ` Derrik Pates
2001-11-24 12:21 ` Benjamin Herrenschmidt
2001-11-24 23:32 ` Derrik Pates
2001-11-22 10:59 ` benh
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 16:09 mocm
2001-11-21 18:27 ` benh
2001-11-22 6:31 ` Derrik Pates
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=20011122182111.9961@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=dpates@dsdk12.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=piger@rvs.uni-hannover.de \
/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.