From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jonathan Isom <jeisom@gmail.com>
Cc: linux1394-user@lists.sourceforge.net, linux-scsi@vger.kernel.org
Subject: Re: 2.6.39 and Powerfile c200
Date: Mon, 30 May 2011 23:24:29 +0200 [thread overview]
Message-ID: <20110530232429.3ef05054@stein> (raw)
In-Reply-To: <BANLkTin=kaUtYMi7QeEAJmSLvLm7rmADkQ@mail.gmail.com>
On May 30 Jonathan Isom wrote:
> > On Sat, May 28, 2011 at 1:26 PM, Stefan Richter
> >> Was the 2.6.39 kernel update the only change that you did on your system,
> >> or were there userland updates too? If yes, maybe you have a program now
> >> that sends weird commands that crash the Powerfile's firmware.
[...]
>
> Well I messed around with it on the mac. It works fine with it. Could
> this be a firewire board failure or is it more indicative of a software bug?
FireWire board failures usually cause some more pronounced I/O errors than
mere SCSI request time-outs; so while it is a possible cause, it is a
rather unlikely one.
> You mentioned updates to software. What packages would you suggest
> I look besides udev?
If there is hal(d) on your system, shut this service down and retry.
Another thought: Which FireWire controller do you have according to
lspci -nn?
--
Stefan Richter
-=====-==-== -=-= ====-
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-30 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikkCOML4aNv_wSrk9VRSofjVwtVAw@mail.gmail.com>
2011-05-28 18:26 ` 2.6.39 and Powerfile c200 Stefan Richter
2011-05-28 20:32 ` Jonathan Isom
2011-05-30 21:08 ` Jonathan Isom
2011-05-30 21:24 ` Stefan Richter [this message]
2011-05-30 21:26 ` Jonathan Isom
2011-05-30 21:38 ` Stefan Richter
2011-05-31 16:48 ` Jonathan Isom
2011-05-31 19:26 ` Stefan Richter
2011-06-01 14:58 ` Jonathan Isom
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=20110530232429.3ef05054@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=jeisom@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-user@lists.sourceforge.net \
/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