All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: 7eggert@gmx.de, akpm@osdl.org, linux-kernel@vger.kernel.org,
	mingo@elte.hu
Subject: Re: [patch] floppy: suspend/resume fix
Date: Sun, 12 Nov 2006 23:58:06 +0000	[thread overview]
Message-ID: <20061112235806.GC31624@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200611122240.kACMeS7l005120@harpo.it.uu.se>

On Sun, Nov 12, 2006 at 11:40:28PM +0100, Mikael Pettersson wrote:
> The bug occurs regardless of whether I leave the floppy disc in the drive
> during suspend or not. 2.6.19-rc5 (vanilla and with Ingo's suspend/resume
> hooks) fails the following use case as well:
> 
> 1. boot
> 2. insert floppy disc
> 3. tar tvf /dev/fd0 (works)
> 4. manually eject floppy disc
> 5. suspend, later resume 
> 6. insert floppy disc
> 7. tar tvf /dev/fd0 (fails with I/O errors)
> 8. tar tvf /dev/fd0 (works)
> 
> Like Ingo said, something happens to the HW during suspend and we
> need to figure out how to reinitialise the HW and the driver so that
> things work immediately after resume.

Now this is interesting - I know there's been a long standing bug with
kernels on my Thinkpad which behave in a similar way to your description
above.  Basically whenever I change the disk in the drive I tend to need
_two_ goes to do anything with it - the first mostly always fails with
IO errors.

I've not bothered to report it because it runs a _very_ old 2.6 kernel
and upgrading the machine to something modern would be extremely painful
(read - would need new hard drive, and probably more RAM than the laptop
can take.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-11-12 23:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12 22:40 [patch] floppy: suspend/resume fix Mikael Pettersson
2006-11-12 23:58 ` Russell King [this message]
2006-11-15 18:53   ` Ingo Molnar
     [not found] <7grMO-2YO-55@gated-at.bofh.it>
     [not found] ` <7gs69-46A-37@gated-at.bofh.it>
     [not found]   ` <7gtvd-7xg-23@gated-at.bofh.it>
2006-11-12 21:44     ` Bodo Eggert
2006-11-14 11:05       ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-11-12 20:47 Mikael Pettersson
2006-11-12 21:29 ` Russell King
2006-11-12 22:03   ` Ingo Molnar
2006-11-12 23:54     ` Russell King
2006-11-14 11:09       ` Pavel Machek
2006-11-14 16:34         ` Lee Revell
2006-11-15 20:24           ` Pavel Machek
2006-11-15 20:34             ` Lee Revell
2006-11-15 20:49             ` Alan
2006-11-15 20:49               ` Pavel Machek
2006-11-15 21:03                 ` Rafael J. Wysocki
2006-11-15 21:14                 ` Arjan van de Ven
2006-11-16 12:38                 ` Russell King
2006-11-15 18:46         ` Ingo Molnar
2006-11-12 17:53 Mikael Pettersson
2006-11-12 18:09 ` Ingo Molnar
2006-11-12 19:30   ` Andrew Morton
2006-11-12 20:35     ` Arjan van de Ven
2006-11-12 19:40   ` Russell King
2006-11-11 20:48 [BUG] floppy: broken after resume due to 2.6.18-rc1 lockdep changes Mikael Pettersson
2006-11-12 15:47 ` [patch] floppy: suspend/resume fix Ingo Molnar

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=20061112235806.GC31624@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=7eggert@gmx.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.