Hehe, sorry, I missed that post... I updated my BIOS but the regression is still there, however... the bios fixed my usb power surge errors that I knew would be fixed eventually.
one more dmesg just in case it helps. I updated from v 5.10 to 5.90 http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_dtlViewDL.jsp?soid=1795538&moid=1310946&rpn=PSAA8U&BV_ [quote] Change History Version 5.90 07-06-2007 o Added: 4GB USB Memory boot support. o Added: Battery critical wake up" at 5% enable/disable function. o Added: When the battery capacity <= 5% in DC mode during BIOS Setup, the Critical Battery Wakeup item will be enabled to wake the computer from standby. o Updated: Intel Microcode for 6F6h, 6F2h, and 10061h CPUs to address errata AH3. o Added: Merom-Lite Celeron CPU support. o Corrected: "TBX error" and "auto password prompt pop-ups" that occur if CMOS data becomes corrupt. o Corrected: The Wireless LAN LED/function does not correlate with the latest kill switch status after waking from Standby (S3), Hibernation (S4), or Soft Off (S5) states. o Added: Kill-Switch On/Off events to correct "Wireless LAN can not maintain the correct state" after waking from S3/S4/S5. Version 5.60 03-15-2007 o Corrected: Audio Line-In function appears without being docked. o Updated: Execute Disable (XD) function. o Updated: Virtualization Technology function o Corrected: Computer hangs when closing the top cover during a restart (DOS or POST) with Yonah Celeron CPUs. (Debug code "69") o Added: NVIF interface for nVidia systems. o Added: ATIF interface for ATI systems. o Corrected: USB errors occurred on XP Main Boards with a Vista BIOS after waking from a Suspend state. o The pre-charge current was changed from 128mA to 256mA to correct rare occurrences of battery recharge failures. o Notes: BIOS version 5.10 (and higher) can be used with Windows XP & Vista. BIOS versions 2.20 (and lower) can not be used with Windows Vista. Once the BIOS is updated to V5.10 (or higher), it will not be possible to downgrade back to V2.20 (or lower). Version 5.50 03-07-2007 o Updated the T2060 CPU (CPU ID=6EC) microcode from version 59h to 5Bh. o Added support for the G781-1 Thermal sensor IC. o Notes: BIOS version 5.10 (and higher) can be used with Windows XP & Vista. BIOS version 2.20 (and lower) can not be used with Windows Vista. Once the BIOS is updated to V5.10 (or higher), it will not be possible to downgrade back to V2.20 (or lower). Version 5.20 01-30-2007 o Corrected: Audio Line In does not function when docked. o Notes: BIOS version 5.10 (and higher) can be used with Windows XP & Vista. BIOS version 2.20 (and lower) can not be used with Windows Vista. Once the BIOS is updated to V5.10 (or higher), it will not be possible to downgrade back to V2.20 (or lower). [/quote] So your suggestion worked. I believe that after rmmod the first time, i rebooted as I had the false impression that this was something that needed a reboot. [code] [EMAIL PROTECTED]:~$ rmmod processor ERROR: Module processor is in use by thermal,acpi_cpufreq [EMAIL PROTECTED]:~$ rmmod thermal ERROR: Removing 'thermal': Operation not permitted [EMAIL PROTECTED]:~$ sudo rmmod thermal [sudo] password for tim: [EMAIL PROTECTED]:~$ sudo rmmod acpi_cpufreq [EMAIL PROTECTED]:~$ sudo rmmod processor [EMAIL PROTECTED]:~$ lsmod Module Size Used by battery 10116 0 ac 5252 0 fan 4868 0 button 8080 0 ipw3945 120224 1 ieee80211 34248 1 ipw3945 e100 36364 0 mii 5632 1 e100 aes 27712 2 ieee80211_crypt_ccmp 7168 2 af_packet 21896 4 binfmt_misc 11400 1 rfcomm 38684 2 l2cap 22788 11 rfcomm bluetooth 52324 4 rfcomm,l2cap nfsd 216304 13 exportfs 5632 1 nfsd lockd 65672 2 nfsd sunrpc 166140 8 nfsd,lockd ppdev 9348 0 ipv6 257700 19 i915 24576 2 drm 81428 3 i915 cpufreq_powersave 1792 0 cpufreq_stats 5508 0 cpufreq_userspace 4116 0 cpufreq_ondemand 8084 0 cpufreq_conservative 6560 0 freq_table 4740 2 cpufreq_stats,cpufreq_ondemand video 17164 0 container 4608 0 sbs 18568 0 dock 9476 0 ext3 129800 1 jbd 53416 1 ext3 mbcache 8324 1 ext3 vfat 12800 0 fat 52636 1 vfat sbp2 23304 0 parport_pc 36132 0 lp 11460 0 parport 35656 3 ppdev,parport_pc,lp snd_hda_intel 262304 1 snd_pcm_oss 43264 0 snd_mixer_oss 16640 1 snd_pcm_oss snd_pcm 77320 2 snd_hda_intel,snd_pcm_oss snd_seq_dummy 3844 0 snd_seq_oss 31872 0 snd_seq_midi 8704 0 snd_rawmidi 24832 1 snd_seq_midi joydev 10432 0 sdhci 17804 0 mmc_core 27668 1 sdhci pcmcia 40236 0 tifm_7xx1 7680 0 tifm_core 10132 1 tifm_7xx1 ieee80211_crypt 6272 2 ieee80211,ieee80211_crypt_ccmp rtc 13208 0 yenta_socket 26636 1 rsrc_nonstatic 13184 1 yenta_socket pcmcia_core 39952 3 pcmcia,yenta_socket,rsrc_nonstatic iTCO_wdt 10656 0 iTCO_vendor_support 3972 1 iTCO_wdt snd_seq_midi_event 7552 2 snd_seq_oss,snd_seq_midi snd_seq 50416 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 22916 2 snd_pcm,snd_seq psmouse 38672 0 serio_raw 7044 0 snd_seq_device 8332 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 52356 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 7520 1 snd snd_page_alloc 9992 2 snd_hda_intel,snd_pcm shpchp 33556 0 pci_hotplug 31288 1 shpchp intel_agp 24596 1 agpgart 33584 3 drm,intel_agp evdev 10240 5 reiserfs 243968 1 sg 36124 0 sr_mod 16548 0 cdrom 36512 1 sr_mod sd_mod 29200 4 ata_piix 16644 3 ehci_hcd 34700 0 ohci1394 35760 0 ieee1394 94904 2 sbp2,ohci1394 ata_generic 7556 0 libata 124400 2 ata_piix,ata_generic scsi_mod 146828 5 sbp2,sg,sr_mod,sd_mod,libata uhci_hcd 25232 0 usbcore 135576 3 ehci_hcd,uhci_hcd raid10 24960 0 raid456 124944 0 xor 16008 1 raid456 raid1 24320 0 raid0 8704 0 multipath 8832 0 linear 6528 0 md_mod 79636 7 raid10,raid456,raid1,raid0,multipath,linear dm_mirror 22400 0 dm_snapshot 17952 0 dm_mod 56768 2 dm_mirror,dm_snapshot fuse 44948 3 apparmor 38812 0 commoncap 7424 1 apparmor [/code] and I can also confirm that using modprobe to re-enable them and suspending causes the yellow Linu screen. -- [gutsy] [regression] suspend-to-ram: resume is blocked on a blinking cursor until some random keystrokes are entered on the keyboard https://bugs.launchpad.net/bugs/137477 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
