lkml.org 
[lkml]   [2004]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: VIA Firewire still broken in 2.6.5 (also broken in 2.6.4, worked in 2.6.3)
From
Date
On Apr 15, 2004, Felix von Leitner <felix-kernel@fefe.de> wrote:

> In 2.6.4, the kernel would detect my cold plugged Maxtor disk, but then
> freeze and eventually time out trying to mount the file system on it in
> the boot process.

> In 2.6.5, largely the same, but the kernel works when the disk is hot
> plugged in after the boot process. Having it plugged in during the boot
> process still fails, and unplugging and replugging it after the boot
> process still fails.

> After a few write accesses on the file system, however, 2.6.5 panics.

> Is this a known problem? Anyone working on it?

Yup. There seems to have been some progress in this regard in the
linux1394 mailing lists and SVN repository, but it's still a bit
unstable.

Personally, I've been using the 2.6.3 ieee1394 sources in newer kernel
releases, and it's been working very well. Perhaps we should revert
drivers/ieee1394 to the 2.6.3 state until the problems are addressed
in the linux1394 repository, to only then have it merged here.
What we have now was a merge of a non-functional state of the tree,
which servers nobody.

I can easily provide a patch to restore the working state, if people
think this would be a good idea. Just say the word.

--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
-
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/

\
 
 \ /
  Last update: 2005-03-22 14:02    [W:0.025 / U:0.648 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site