mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Felix von Leitner <felix-kernel@fefe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA Firewire still broken in 2.6.5 (also broken in 2.6.4, worked in 2.6.3)
Date: 15 Apr 2004 17:24:09 -0300	[thread overview]
Message-ID: <or3c75dm6u.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20040415183230.GA16458@codeblau.de>

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}

      reply	other threads:[~2004-04-15 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 18:32 Felix von Leitner
2004-04-15 20:24 ` Alexandre Oliva [this message]

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=or3c75dm6u.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=felix-kernel@fefe.de \
    --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

all inboxes | Powered by JetHome®