Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

[bradley mclain]

i thought that it was my network driver, but i
recompiled 2.4.2 without sound support and apm
--suspend has begun to work again.

the sound card is a yamaha YMF-744B.  i hadn't been
compiling with sound support (i dont care about sound
on my laptop), but when i got 2.4.2 i decided to try,
and now i'm pretty sure that was the problem.

is there anything else i should do, or information i
could provide that would confirm this analysis or help
to find a fix?

--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Can you see if 2.4.1ac20 was ok
> 


__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

[bradley mclain]

i thought that it was my network driver (xircom), but
i recompiled 2.4.2 without sound support and apm
--suspend has begun to work again.

the sound card is a yamaha YMF-744B.  i hadn't been
compiling with sound support (i dont care about sound
on my laptop), but when i got 2.4.2 i decided to try,
and now i'm pretty sure that was the problem.

is there anything else i should do, or information i
could provide that would confirm this analysis or help
to find a fix?

--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Can you see if 2.4.1ac20 was ok
> 


__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

[Alan Cox]

> the sound card is a yamaha YMF-744B.  i hadn't been
> compiling with sound support (i dont care about sound
> on my laptop), but when i got 2.4.2 i decided to try,
> and now i'm pretty sure that was the problem.

The Yamaha sound driver doesnt handle the case where the bios fails to restore
the chip status and expects a windows driver to do its dirty work. That
requires on resume that the device is completely reloaded.

A workaround is to make it a module, unload it before suspend and reload it
after resume but thats pretty umm uggly.

Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

[John Fremlin]

 Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> > the sound card is a yamaha YMF-744B.  i hadn't been
> > compiling with sound support (i dont care about sound
> > on my laptop), but when i got 2.4.2 i decided to try,
> > and now i'm pretty sure that was the problem.
> 
> The Yamaha sound driver doesnt handle the case where the bios fails
> to restore the chip status and expects a windows driver to do its
> dirty work. That requires on resume that the device is completely
> reloaded.
> 
> A workaround is to make it a module, unload it before suspend and
> reload it after resume but thats pretty umm uggly.

Why not use kernel/pm.c:pm_register? Then you can either refuse
suspend or have a proper workaround.

-- 

	http://www.penguinpowered.com/~vii

Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

[Alan Cox]

> Why not use kernel/pm.c:pm_register? Then you can either refuse
> suspend or have a proper workaround.

Feel free to provide code. I suspect you can do something like
refuse to suspend if the device is open at all and reload the firmware, reinit
it on resume if it was idle.

I dont have the hardware

Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

[John Fremlin]

 Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> > Why not use kernel/pm.c:pm_register? Then you can either refuse
> > suspend or have a proper workaround.
> 
> Feel free to provide code. 

You have me there - I should have realised who I was writing to ;-)

[...]

> I dont have the hardware

I neither.

-- 

	http://www.penguinpowered.com/~vii

APM suspend system lockup under 2.4.2 and 2.4.2ac1

[bradley mclain]

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

apm --suspend causes my system to hang under 2.4.2 and
2.4.2ac1.  it was working fine under 2.4.1ac19. 
looking at syslog it appears that the driver for my
xircom pcmcia card may be involved -- it was the last
entry on two of three occasions.  the latest lockup
(under 2.4.1ac1) left no trace in syslog.

upon issuing the command the screen shuts down, but
the rest of the machine (drive, etc.) fails to, and i
cannot get control back.

machine:  toshiba tecra 8100

lspci output and two syslog entries are in the
attached file.

1st syslog shows last entry and first of reboot under
2.4.2 and 2nd shows last entry and first of reboot
under 2.4.2ac1.

if anything else is needed, please let me know.

bradley mclain



__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/

[-- Attachment #2: extract --]
[-- Type: application/octet-stream, Size: 1275 bytes --]

Feb 22 17:20:00 localhost CROND[1326]: (root) CMD (   /sbin/rmmod -as) 
Feb 22 17:23:49 localhost cardmgr[380]: executing: './network suspend eth0'
Feb 22 17:45:51 localhost syslogd 1.3-3: restart.

Feb 22 18:13:59 localhost rc: Starting linuxconf succeeded
Feb 22 18:22:11 localhost syslogd 1.3-3: restart.

00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
00:05.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:05.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:05.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:05.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03)
00:07.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
00:09.0 IRDA controller: Toshiba America Info Systems FIR Port Type-DO
00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 20)
00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 20)
00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02)
01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/MX-/IX (rev 11)

Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1

[John Fremlin]

Unfortunately, the APM maintainer, Stephen Rothwell, seems to have
gone into hibernation (pun) and is not responding to emails.

bradley mclain <bradley_kernel@yahoo.com> writes:

> apm --suspend causes my system to hang under 2.4.2 and 2.4.2ac1.  it
> was working fine under 2.4.1ac19. looking at syslog it appears that
> the driver for my xircom pcmcia card may be involved -- it was the
> last entry on two of three occasions.  the latest lockup (under
> 2.4.1ac1) left no trace in syslog.

Are all kernel messages dumped to syslog? See syslog.conf(5).

> upon issuing the command the screen shuts down, but the rest of the
> machine (drive, etc.) fails to, and i cannot get control back.

If the screen shutdown, all the PM enabled drivers OK'd the suspend
and the APM state was changed.

Perhaps the particular driver you used bungled things somehow. You
could try again with the driver/card unloaded, which would help narrow
the cause of the problem down.

[...]

-- 

	http://www.penguinpowered.com/~vii