suspend-to-disk using a SAS drive

suspend-to-disk using a SAS drive

[Nevine AbouGhazaleh]

I am trying to suspend-to-disk using the Suspend2 modules. I am using an SSD drive connected through a SAS bus interface. The SSD acts as a boot disk.
All read and write transactions to the drive works well during normal operation.  
when I hibernate (suspend-to-disk).

I get the following errors:
------------------
mptbase: ioc0: ERROR – Invalid IOC facts reply, msgLength=0 offset=6
pnp: Failed to activate device 00:09.
pnp: Failed to activate device 00:0a.
------------

Immediately after these messages, Linux hangs as soon as it starts writing the image to the drive. showing the following output.
------------------
Writing Kernel and process data ...
20%...
------------------


When using KDB to trace the problem after the kernel hung.

<ps> shows a running process: Ks2io

when doing Back Trace for Ks2io wheen the kernel hangs, I get the following trace
--------------------
_spin_unlock_irq+0xb
thread_return+0x64
_raw_spin_lock+ox90
__mutex_up_process+0x10
wake_up_process+0x10
suspend_bio_write_page
mutex_lock+0x2a
flush_workqueue+0x51
kblockd_flush+0x10
do_bio_wait+0x1b
suspend_bio_write_page
suepend_bio_write_page+0x41
suspend_compress_write_page+0x137
worker_rw_loop
worker_rw_loop+0x133
worker_rw_loop
kthread+0xf5
schedule_tail_0x45
child_rip+0x45
worker_thread
kthread
child_rip 
--------------------

It seems that the problem is when suspend2 tries to write to the SSD drive.
I am not sure whether the problem is with the suspend2 module or the mpt driver? 
I am using kernel 2.6.21.1 x86_64 with fedora core 5 x86_64. MPT driver 3.04
Any insights/recommendations will be greatly appreciated.  

Re: suspend-to-disk using a SAS drive

[Pavel Machek]

On Sun 2007-08-05 18:36:03, Nevine AbouGhazaleh wrote:
> I am trying to suspend-to-disk using the Suspend2 modules. I am using an 
> SSD drive connected through a SAS bus interface. The SSD acts as a boot 
> disk.
> All read and write transactions to the drive works well during normal 
> operation.  when I hibernate (suspend-to-disk).
>
> I get the following errors:
> ------------------
> mptbase: ioc0: ERROR ? Invalid IOC facts reply, msgLength=0 offset=6
> pnp: Failed to activate device 00:09.
> pnp: Failed to activate device 00:0a.
> ------------
>
> Immediately after these messages, Linux hangs as soon as it starts writing 
> the image to the drive. showing the following output.
> ------------------
> Writing Kernel and process data ...
> 20%...
> ------------------
>
>
> When using KDB to trace the problem after the kernel hung.
>
> <ps> shows a running process: Ks2io
>
> when doing Back Trace for Ks2io wheen the kernel hangs, I get the following 
> trace
> --------------------
> _spin_unlock_irq+0xb
> thread_return+0x64
> _raw_spin_lock+ox90
> __mutex_up_process+0x10
> wake_up_process+0x10
> suspend_bio_write_page
> mutex_lock+0x2a
> flush_workqueue+0x51
> kblockd_flush+0x10
> do_bio_wait+0x1b
> suspend_bio_write_page
> suepend_bio_write_page+0x41
> suspend_compress_write_page+0x137
> worker_rw_loop
> worker_rw_loop+0x133
> worker_rw_loop
> kthread+0xf5
> schedule_tail_0x45
> child_rip+0x45
> worker_thread
> kthread
> child_rip --------------------
>
> It seems that the problem is when suspend2 tries to write to the SSD drive.
> I am not sure whether the problem is with the suspend2 module or the mpt 
> driver? I am using kernel 2.6.21.1 x86_64 with fedora core 5 x86_64. MPT 
> driver 3.04
> Any insights/recommendations will be greatly appreciated.  

Try latest kernel without suspend2 patch... ... if it hangs at 20% you
may have a chance that driver already has some suspend/resume support.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html