Suspend problems with SuSE 10.1-GM on T60p

I have been using the HSF softmodem driver (7.47.00.01full) with the
various early release versions of SuSE 10.1 (beta9, RC1, RC2, RC3) and
it has worked well. However, since moving to the official 10.1-GM
release, I now find that having the hsf modules loaded prevents suspend
to disk working. It hangs here in the message log:

May 17 09:04:01 koetsu [powersave-do_screen_saver][9331]: DIAG: Process script for event global.suspend2disk ID
May 17 09:04:01 koetsu [powersave-do_screen_saver][9331]: INFO: Event: GLOBAL_SUSPEND2DISK occured.
May 17 09:04:01 koetsu [powersave-do_screen_saver][9331]: INFO: Parameters: Event - global.suspend2disk; Current Active Scheme:  - ACPI event line:
May 17 09:04:01 koetsu [powersave-do_screen_saver][9331]: INFO: process script: screen_saver
May 17 09:04:02 koetsu kernel: cnxthsf_OsEventWaitTime: f7176e40 returning OSEVENT_WAIT_TIMEOUT
May 17 09:04:02 koetsu kernel: cnxthsf_OsEventWaitTime: f7176e40 returning OSEVENT_WAIT_TIMEOUT
May 17 09:04:02 koetsu [powersave-do_screen_saver][9331]: DIAG: script_return() invoked: event_id: 0, request: Script screen_saver, text:

With a snd_ module being accessed on the console screen that shows how
suspend is progressing. The machine is a Thinkpad T60p running a
2.6.16.13-4-smp kernel. I have tried the explicit version of HSF for
this kernel and building it myself but both act in the same way. I have
had the spurious OSEVENT_WAIT_TIMEOUT errors at unpredictable times with
the earlier kernel versions but it didn't prevent suspend to disk.
Suspend to RAM continues to work OK.

Which bits of /tmp/hsfdiag.txt would be useful to you?





Cosmo