Most recent kernel where this bug did not occur: 2.6.14-rc4 Distribution: Debian Unstable Hardware Environment: Compaq Armada 110 without any USB or PCMCIA devices attached; 1. lspci: 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05) 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP] 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) 0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) 0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10) 0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) 0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 20) 0000:00:09.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 09) 0000:00:09.1 Serial controller: Agere Systems LT WinModem 0000:00:0a.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01) 0000:01:00.0 VGA compatible controller: Trident Microsystems CyberBlade i1 (rev 6a) http://zeus.polsl.gliwice.pl/~jfk/kernel/lspci-v http://zeus.polsl.gliwice.pl/~jfk/kernel/lspci-v-v http://zeus.polsl.gliwice.pl/~jfk/kernel/lspci-v-v-v 2. dmesg http://zeus.polsl.gliwice.pl/~jfk/kernel/dmesg Software Environment: 1. config: http://zeus.polsl.gliwice.pl/~jfk/kernel/config-2.6.14-rc4-laptop no changes in config for 2.6.14-rc5, except for some: "+# CONFIG_AIRO is not set" 2. hibernation "script" http://zeus.polsl.gliwice.pl/~jfk/kernel/hib 3. ver-linux (as in 2.6.14-rc4) --------------------------------------------------- Linux miriel 2.6.14-rc4-laptop #5 PREEMPT Fri Nov 11 21:36:41 CET 2005 i686 GNU/Linux Gnu C 4.0.3 Gnu make 3.80 binutils 2.16.91 util-linux 2.12p mount 2.12p module-init-tools 3.2-pre9 e2fsprogs 1.38 reiserfsprogs line reiser4progs line pcmcia-cs 3.2.8 PPP 2.4.3 Linux C Library 2.3.5 Dynamic linker (ldd) 2.3.5 Procps 3.2.6 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.2.1 Modules Loaded uhci_hcd floppy sd_mod scsi_mod ipx p8022 psnap llc thermal fan button processor ac battery ipt_multiport ipt_state ipt_pkttype ipt_LOG ipt_limit ipt_REJECT iptable_nat ip_nat iptable_filter ip_tables ip_conntrack_ftp ip_conntrack nfnetlink pcmcia firmware_class crc32 8250_pnp yenta_socket rsrc_nonstatic pcmcia_core 8250_pci 8250 serial_core e100 snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_via82xx gameport snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore via686a i2c_isa i2c_core parport_pc parport nls_iso8859_2 nls_cp852 vfat fat loop rtc psmouse mousedev pegasus mii Problem Description: System freezes while resuming from suspend-to-disk; nothing in logs, nothing on the vga console Steps to reproduce: Start the system, work for a minute or two (what I did was to run X, run browser and exit), suspend (no problem here), resume (freezes after "Stopping tasks: =============..." appears on the screen again). Actually I was able to sucessfully resume with 2.6.14-rc5, but only once (start->login->sync, sync->hibernate) Related: : "Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1" thread on lkml
Do you think this is a regression?
See lkml, there is dmitry torokov's patch that solves problem in ps/2 support...
I've just checked the Dymitri's patch (http://www.ussg.iu.edu/hypermail/linux/kernel/0511.2/1060.html) ontop of 2.6.14.2 and it looks the same - ie. 'nothing' after "Stopping task======" I've not yet tried increasing timeout value (which has helped in a few cases). Could it be valuable?
and as for regression - for me it is kind of - swsup has been working here for over a year from one version of kernel to another (thanks btw) :)
Maybe it is not easy, but, do you still remember from which version, S4 stop working for you.
I've got a new laptop for a while now, but recently got an occasion to borrow an old one and test the regression with 2.6.15. I believe the bug it's no longer there - everything works OK from within X and console...