[ltp] T30 failes to resume from suspend

[Reinhard Foerster]

On Mon, 23 Dec 2002 15:57:30 +0100, Rune Froysa wrote:

> I'm having problems making my T30 (type 2366 - 92g) resume properly
> from suspend.  The system wakes up, but when trying to access the hd,
> the message "hda: lost interrupt" is printed and the process in
> question hangs.

I can't reproduce it on T30 2366 97G. Suspend and hibernation are fine.

The only malfunction here is that I cant resume from standby (Fn+F3) 
while running X. The display backlight comes back, X doesnt. I have 
to change to an other vt, Fn+F3 two times, change back to X.

>  The powerswitch is needed to resume system
> operation.  Sometimes I also get "ide_dmaproc: chipset supported
> ide_dma_lostirq func only: 13", or "resume warning: bios doesn't
> restore PCI state properly\nresume warning: if resume failed, try
> booting with resume=force" (resume=force doesn't help).
> 
> About 1 of 5 resumes succeedes without problems.  On boot, the message
> "IBM machine detected. Enabling interrupts during APM calls." is
> printed (redhat 8.0, linux-2.4.18-18.8.0).  I've tried compiling
> linux-2.4.20 with:
> 
>   CONFIG_APM_ALLOW_INTS=y
>   # CONFIG_IDEPCI_SHARE_IRQ is not set
>   CONFIG_IDEDISK_MULTI_MODE=y

I use vanilla 2.4.21pre2. .config an XF86Config available at
http://rudi.urz.tu-dresden.de/~rf11/t30/

> as well as updating /etc/sysconfig/apmd with:
> 
>   HDPARM_AT_SUSPEND="-q -X0 -q -c0 -q -d0 -q -u0 -q -S10"
>   HDPARM_AT_RESUME="-q -X66 -q -c1 -q -d1 -q -u1 -q -S30"

battery and suspend:
        /sbin/hdparm -S3 -d1 -c1 -u1  /dev/hda >/dev/null
        /sbin/hdparm     -d1 -c1 -u1  /dev/hdc &>/dev/null
AC:
        /sbin/hdparm -S0 -d1 -c1 -u1  /dev/hda >/dev/null
        /sbin/hdparm     -d1 -c1 -u1  /dev/hdc &>/dev/null

Maybe you have another hard disk. Mine is a HITACHI_DK23EA-60B.

> Loaded modules are:
> 
>   Module                  Size  Used by    Not tainted
>   speedstep               5820   0 (unused)

I havent patched for speedstep.

> Are there any known solutions to this problem?

No, sorry. Is Fn+F3 working for you while running X?

   Reinhard