Date: Tue, 15 Jun 2004 12:05:41 -0400
From: Ben Collins <bcollins@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: ieee1394 still utterly broken in 2.6.7-rc3
Message-ID: <20040615160541.GB9456@phunnypharm.org>
References: <20040615155354.GA7988@fefe.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040615155354.GA7988@fefe.de>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1343
Lines: 37

On Tue, Jun 15, 2004 at 05:53:54PM +0200, Felix von Leitner wrote:
> Is it too much to ask to at least revert back to the ieee1394 code from
> 2.6.3 before shipping the final 2.6.7?
> 
> Firewire was dysfunctional sind 2.6.3, and still has not been fixed,
> despite several updates to the code.
> 
> Please, 2.6 is supposed to be a stable kernel, for people to use in
> production environments.
> 
> Here's what happens with every kernel since 2.6.4:
> 
>   kernel boots
>   finds firewire hard disk
>   creates device
>   boot sequence tries to mount disk
>   computer hangs
>   I pull the cable
>   computer continues booting, just without firewire disk
> 
> It's an Athlon mainboard with VIA chipset.

Is firewire built-in to the kernel? I haven't seen any of these problems
_at all_, but I use modules. I have a 250gig firewire disk that is used
for nightly backups for 5 systems via rsync and ssh, and it never shows
any problems.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/