Bug#506654: linux-image-2.6.29: 2.6.29 still re-detects firewire disk after s3 suspend.
On Wed, Jun 03, 2009 at 11:26:46PM +0300, Hakan BAYINDIR wrote:
> Package: linux-image-2.6.29-2-686-bigmem
> Version: 2.6.29-5
> Severity: normal
> File: linux-image-2.6.29
>
> Hi
>
> After the inclusion of the new firewire stack again, the bug that resulting in re-detection of the firewire disk as a newly plugged device has not gone away.
>
> To re-hash the situation:
>
> - I suspend my system using suspend to RAM in new KDE4's leave menu.
> - System suspends normally.
> - Some time passes (as expected)
> - I wake my system and system comes back as expected.
> - System detects my firewire disk as a new device, gives it a different /dev/ entry, drops the old mountpoint so it appears dead. Making any operations on old mountpoint generate kernel messages about a dead I/O device.
> - To fix the situation, I umount the dead point, remove the disk and re-plug it and mount everything back (sometimes I need to run an fsck to verify the huge 1TB disk)
>
> This is not convenient, dangerous (I may lose data), most importantly was not happening before. I'm running an Intel P35 platform and my FireWire controller is VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller. I'm running with suspend to disk as a workaround.
>
> Since nobody replied and/or provided additional information I needed to bump it. I'm a linux system administrator / programmer so I can provide any additional information you want.
>
> Cheers.
please report upstream in bugzilla.kernel.org,
but first did you try 2.6.30-rc{7,8}, see trunk apt lines
-> http://wiki.debian.org/DebianKernel
if it is still reproducible with latest please let us know about
upstream bug nr. include there the faulty dmesg and lspci -vvv
> ** Tainted: P (1)
not directly related, but voids support.
kind regards
maks
Reply to: