public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix von Leitner <felix-kernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: VIA Firewire still broken in 2.6.5 (also broken in 2.6.4, worked in 2.6.3)
Date: Thu, 15 Apr 2004 20:32:31 +0200	[thread overview]
Message-ID: <20040415183230.GA16458@codeblau.de> (raw)

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?

Felix

             reply	other threads:[~2004-04-15 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 18:32 Felix von Leitner [this message]
2004-04-15 20:24 ` VIA Firewire still broken in 2.6.5 (also broken in 2.6.4, worked in 2.6.3) Alexandre Oliva

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=20040415183230.GA16458@codeblau.de \
    --to=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