From: Lee Revell <rlrevell@joe-job.com>
To: gene.heskett@verizononline.net
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Firewire problems, apparently since 2.6.13-rc1
Date: Sun, 02 Apr 2006 15:00:49 -0400 [thread overview]
Message-ID: <1144004450.11043.1.camel@mindpipe> (raw)
In-Reply-To: <200604021418.16263.gene.heskett@verizon.net>
On Sun, 2006-04-02 at 13:18 -0500, Gene Heskett wrote:
> Greetings;
>
> How much trouble will I have if I take the current 2.6.16.1 kernel src
> tree, nuke the ieee1394 directory of it, and bring the ieee1394
> directory in from the 2.6.12 tarball?
>
This has no chance of working.
> At 2.6.12, all the firewire stuff I needed to import from my camera,
> edit it, and make vcd's or dvd's out of it worked _flawlessly_. Now,
> at 2.6.16.1, and apparently since 2.6.13-rc1, kino is broken and must
> be killed by the system when it hangs. I figured it would get sorted,
> but apparently not.
>
That's always a bad assumption. Bugs should be reported early and
often.
> I can recover from backups all the stuff I've overwritten in the last 2
> days trying to make it work. That should make it all work again IF the
> ieee1394 stuff was reverted to the 2.6.12 version. Is this feasable at
> all?
>
No - it would be a much better use of your time to put together an
actionable bug report. The above is too vague... can you get an strace
or GDB backtrace of the hung process, dmesg, etc
Lee
next prev parent reply other threads:[~2006-04-02 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 18:18 Firewire problems, apparently since 2.6.13-rc1 Gene Heskett
2006-04-02 19:00 ` Lee Revell [this message]
2006-04-02 20:25 ` Gene Heskett
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=1144004450.11043.1.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=gene.heskett@verizononline.net \
--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