Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
howto: get swsusp2 (hibernate, suspend to disk) working
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 5, 6, 7 ... 12, 13, 14  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
zmedico
Developer
Developer


Joined: 02 Jan 2004
Posts: 338
Location: California USA

PostPosted: Tue Jul 13, 2004 3:25 am    Post subject: Reply with quote

The include/linux/kdb.h header file should be created by one of the swsusp2 patches. You must have patched it wrong. Lots of people have that problem. There's a thread about that here:
https://forums.gentoo.org/viewtopic.php?p=1290805
_________________
Zac
Back to top
View user's profile Send private message
RoundsToZero
Guru
Guru


Joined: 17 Nov 2003
Posts: 478
Location: New York, NY

PostPosted: Tue Jul 13, 2004 5:40 pm    Post subject: Reply with quote

For me, applying the 10 series patch as well as the 20's and 30's made it work.
Back to top
View user's profile Send private message
dan_a
n00b
n00b


Joined: 21 Jul 2002
Posts: 11
Location: Isle Of Man, British Isles

PostPosted: Tue Jul 13, 2004 11:55 pm    Post subject: Reply with quote

Editing swapwriter.c worked for me.

Code:
vi +14 kernel/power/swapwriter.c

and edit the line that says
Code:
#include <linux/kdb.h>

to say
Code:
// #include <linux/kdb.h>

(I think kdb is the kernel debugger; if you're not a kernel hacker you probably won't use it anyway.)
Back to top
View user's profile Send private message
rlz
n00b
n00b


Joined: 17 Apr 2004
Posts: 31

PostPosted: Wed Jul 14, 2004 3:11 pm    Post subject: Reply with quote

everything seems to work fine for me and it says resuming and loads the file but once its loaded the screen just goes black. has anyone else had these problems or know what causes it ?
Back to top
View user's profile Send private message
pjv
Guru
Guru


Joined: 02 Jul 2003
Posts: 353
Location: Belgium

PostPosted: Wed Jul 14, 2004 7:45 pm    Post subject: Reply with quote

Can I expect problems with ReiserFS?
Does the option GrubMenuFile know that it needs to mount my boot partition (/dev/hda6) first before it can write to /boot/grub/menu.lst?

Thx
Back to top
View user's profile Send private message
tuxlover
Apprentice
Apprentice


Joined: 21 Oct 2003
Posts: 297
Location: weltweit

PostPosted: Fri Jul 16, 2004 11:09 am    Post subject: Reply with quote

No problems at all with reiserfs and swsusp2 here.
Back to top
View user's profile Send private message
Nuuul
n00b
n00b


Joined: 05 Mar 2004
Posts: 11
Location: The Netherlands

PostPosted: Sat Jul 17, 2004 2:07 pm    Post subject: Reply with quote

Tried the new patch 2.0.0.100, but it fails at resuming: hangs at cleaning up 8O

Solved: had to unload the Prism54 module before suspending :roll:
Back to top
View user's profile Send private message
tuxlover
Apprentice
Apprentice


Joined: 21 Oct 2003
Posts: 297
Location: weltweit

PostPosted: Sat Jul 17, 2004 4:47 pm    Post subject: Reply with quote

Anybody tried the new suspend script? It jumped from v0.18 to 0.94 8O Have I been living in a hole? The project also moved from sourceforge to berlios, their new url is http://softwaresuspend.berlios.de/

The configuration file is totally different now... A question I have: (didn't find an answer on the swsusp2 webpage)
How do you do remounting? The option "Remount" doesn't work. (I solved it through "OnResume 20 mount /mnt/c")

I guess I will update the how-to for the new hibernate/suspend script and configuration soon.


Last edited by tuxlover on Sun Jul 18, 2004 1:59 pm; edited 1 time in total
Back to top
View user's profile Send private message
tomthewombat
Apprentice
Apprentice


Joined: 29 Mar 2003
Posts: 244
Location: NY State

PostPosted: Sun Jul 18, 2004 1:55 pm    Post subject: Reply with quote

nVidia and SWSUSP2 Howto:
http://softwaresuspend.berlios.de/wiki/Nvidia

Yes, it really works!!
_________________
http://www.wombatorium.net
Back to top
View user's profile Send private message
tuxlover
Apprentice
Apprentice


Joined: 21 Oct 2003
Posts: 297
Location: weltweit

PostPosted: Sun Jul 18, 2004 3:31 pm    Post subject: Reply with quote

Due to the recent changes to the config files and patch process I made some
Updates to the howto:
Back to top
View user's profile Send private message
Drako'99
n00b
n00b


Joined: 06 Apr 2004
Posts: 50
Location: France

PostPosted: Wed Jul 21, 2004 4:47 pm    Post subject: Reply with quote

I'm currently running with a swsusp 2.0.0.100 patched kernel and I still have little problems caused by the ATI and the fglrx module.

I wanted to know if someone managed to hibernate from a X environment ? :roll:


At this time I stop the xdm service and remove the fglrx module before hibernate and restart the service and load the module at startup.

It's great to be able to do a suspend-to-disk under Linux 8)

PS: hardware -> Dell Inspiron 8600 w/ ATI M10.
EDIT : M11 -> M10


Last edited by Drako'99 on Wed Jul 21, 2004 6:39 pm; edited 1 time in total
Back to top
View user's profile Send private message
tuxlover
Apprentice
Apprentice


Joined: 21 Oct 2003
Posts: 297
Location: weltweit

PostPosted: Wed Jul 21, 2004 6:30 pm    Post subject: Reply with quote

Drako'99 wrote:
I wanted to know if someone managed to hibernate from a X environment ?

There is no problem with X and swsusp. The problem lies in nvidia's and ati's drivers as far as I know.
I'm using the radeon m9 with 3d acceleration from DRI and swsusp is working flawlessly. I just read there that the radeon m10+'s 3d acceleration isn't yet supported, however.
Back to top
View user's profile Send private message
Drako'99
n00b
n00b


Joined: 06 Apr 2004
Posts: 50
Location: France

PostPosted: Wed Jul 21, 2004 6:39 pm    Post subject: Reply with quote

tuxlover wrote:
I just read there that the radeon m10+'s 3d acceleration isn't yet supported, however.

I knew that ATI drivers were problematic, but I wanted to be sure.

However, thank you for your answer :wink:


Other thing, that's not a M11 but a M10...
Back to top
View user's profile Send private message
Kraymer
Guru
Guru


Joined: 27 Aug 2003
Posts: 349
Location: Germany

PostPosted: Fri Jul 23, 2004 5:12 pm    Post subject: Re: howto: get swsusp2 (hibernate, suspend to disk) working Reply with quote

tuxlover wrote:

Code:
%wheel ALL=NOPASSWD: /usr/local/sbin/hibernate

This will allow the members of your wheel group to execute /usr/local/sbin/hibernate:
Code:
sudo /usr/local/sbin/hibernate

Yeah, that was my intention too. Hibernation must be doable by user to make it accessable by hotkeys and such 8)
My problem is.. it doesn't really work.
It's a problem with bootsplash. Unfortunately, the Bootsplash-On-Option didn't work for me, I got text output which is really bad for me as I'm very used to my bootsplash ;) The (working) solution was taken from the swsusp2-FAQ, a manual call to /sbin/splash. The problem is that sudo doesn't transfer root-rights to OnSuspend/OnResume-calls.
Does anyone have a solution for it except suid-root?

Sebastian

edit: moahh.. one moment of stupidity :oops: of course, following did the trick:
Code:
# Hibernation without PWD :-)
%wheel ALL = NOPASSWD: /usr/local/sbin/hibernate
%wheel ALL = NOPASSWD: /sbin/splash
Back to top
View user's profile Send private message
aloha99
n00b
n00b


Joined: 06 Jun 2004
Posts: 20

PostPosted: Sun Jul 25, 2004 6:13 am    Post subject: Reply with quote

I finally did the update, using several patches against gentoo-dev-sources 2.6.7-r11, plus the hibernate script [EDIT] ver. 2.0.0.100 [/EDIT], all works very well, plus acpi-based power button trigger. GREAT JOB, TUXLOVER!

FWIW, on my IBM T30 with ATI Radeon 7500 Mobility (M7), so far *everything* works ... okay, haven't tested everything, but I did say "so far" ;)

Suspends in less than 15 seconds, resumes in 32 seconds from push of button.

BTW, I also referred to this thread: https://forums.gentoo.org/viewtopic.php?p=1290805 which also has helpful info on how to manually patch your kernel in case of errors.

Thanks!


Last edited by aloha99 on Tue Jul 27, 2004 4:43 am; edited 1 time in total
Back to top
View user's profile Send private message
tuxlover
Apprentice
Apprentice


Joined: 21 Oct 2003
Posts: 297
Location: weltweit

PostPosted: Sun Jul 25, 2004 6:29 pm    Post subject: Re: howto: get swsusp2 (hibernate, suspend to disk) working Reply with quote

Once again, another update of the howto: Added section: Tips & Tricks.
smash032 wrote:
Code:
# Hibernation without PWD :-)
%wheel ALL = NOPASSWD: /usr/local/sbin/hibernate
%wheel ALL = NOPASSWD: /sbin/splash

Thanks! I added that. Have you tried acpid to initiate software suspend? Does your bootsplash work then? (acpid runs with root priviliges)
aloha99 wrote:
GREAT JOB, TUXLOVER!
:) Thanks! I added your kernel patching link as well.
Quote:
plus the hibernate script ver. 2.0.0.200-for-2.6.7
I guess this was supposed to read 2.0.0.100...?

By the way... What do you guys think about turning this howto into a wiki? Preferrably at http://softwaresuspend.berlios.de/wiki ?
Back to top
View user's profile Send private message
Kraymer
Guru
Guru


Joined: 27 Aug 2003
Posts: 349
Location: Germany

PostPosted: Sun Jul 25, 2004 6:51 pm    Post subject: Re: howto: get swsusp2 (hibernate, suspend to disk) working Reply with quote

tuxlover wrote:

smash032 wrote:
Code:
# Hibernation without PWD :-)
%wheel ALL = NOPASSWD: /usr/local/sbin/hibernate
%wheel ALL = NOPASSWD: /sbin/splash

Thanks! I added that. Have you tried acpid to initiate software suspend? Does your bootsplash work then? (acpid runs with root priviliges)

No, didn't that yet. I've done a keyboard-shortcut to call hibernate. My power button still triggers a regular shutdown and I think I'll leave it that way. But it doesn't matter, the sudoers-changes do work. There was an error in dmesg from hibernate-script but in fact it works :)
tuxlover wrote:

By the way... What do you guys think about turning this howto into a wiki? Preferrably at http://softwaresuspend.berlios.de/wiki ?

Actually, already thought about that. But I'm kinda busy and unfortunately not familiar with wiki-syntax :( But it's a great idea. Many users (not only gentoo-ists *g) would benefit.. Maybe if time passes by and noone else does it, I could..
Back to top
View user's profile Send private message
dimfox2
n00b
n00b


Joined: 10 Jul 2004
Posts: 24

PostPosted: Tue Jul 27, 2004 1:56 am    Post subject: Reply with quote

Hi, I used swsusp for about two weeks, on my newly installed gentoo. It works fine (can't resume into X though, haven't tried the new trick for nvidia). But I begin to have a problem these two days: it suspends fine, but when resumes the computer becomes very, very slow, probably take 3 seconds to see a reaction, e.g. the letter you typed displayed, or using alt+Fn to switch between consoles. And this is not under X. I don't know if this has anything to do with I close the lid before it totaly shut down when suspending.

Here's the log (sorry for the lengthy post) :oops:
[code:1:276ea9f9a1]
Jul 25 18:59:26 dimtux Software Suspend 2.0.0.96: Initiating a software_suspend cycle.
Jul 25 18:59:53 dimtux Debug: sleeping function called from invalid context at include/asm/semaphore.h:145
Jul 25 18:59:53 dimtux in_atomic():1, irqs_disabled():1
Jul 25 18:59:53 dimtux [<c011b5e4>] __might_sleep+0xb2/0xd3
Jul 25 18:59:53 dimtux [<c0106aa0>] common_interrupt+0x18/0x20
Jul 25 18:59:53 dimtux [<c0219ee7>] tty_write+0xd7/0x300
Jul 25 18:59:53 dimtux [<c021fbc4>] write_chan+0x0/0x21a
Jul 25 18:59:53 dimtux [<c021a110>] redirected_tty_write+0x0/0xe1
Jul 25 18:59:53 dimtux [<c0164feb>] vfs_write+0xb0/0x119
Jul 25 18:59:53 dimtux [<c01650f9>] sys_write+0x42/0x63
Jul 25 18:59:53 dimtux [<c01381e5>] move_cursor_to+0x51/0x75
Jul 25 18:59:53 dimtux [<c0138e9c>] update_status+0x366/0x3fb
Jul 25 18:59:53 dimtux [<c0141771>] save_image_part1+0x26/0x1ba
Jul 25 18:59:53 dimtux [<c0141c68>] do_suspend2_suspend_2+0x8/0x34
Jul 25 18:59:53 dimtux [<c028cbc8>] do_suspend2_lowlevel+0x269/0x8a5
Jul 25 18:59:53 dimtux [<c01416fa>] save_image+0xc0/0x111
Jul 25 18:59:53 dimtux [<c01424f1>] software_suspend_pending+0x249/0x25f
Jul 25 18:59:53 dimtux [<c0196a93>] proc_file_write+0x0/0x42
Jul 25 18:59:53 dimtux [<c01405b6>] proc_software_suspend_pending+0x5/0xa
Jul 25 18:59:53 dimtux [<c0196aca>] proc_file_write+0x37/0x42
Jul 25 18:59:53 dimtux [<c0164feb>] vfs_write+0xb0/0x119
Jul 25 18:59:53 dimtux [<c016459b>] filp_close+0x59/0x86
Jul 25 18:59:53 dimtux [<c01650f9>] sys_write+0x42/0x63
Jul 25 18:59:53 dimtux [<c0106133>] syscall_call+0x7/0xb
Jul 25 18:59:53 dimtux
Jul 25 18:59:53 dimtux PCI: Setting latency timer of device 0000:00:1d.0 to 64
Jul 25 18:59:53 dimtux PCI: Setting latency timer of device 0000:00:1d.1 to 64
Jul 25 18:59:53 dimtux PCI: Setting latency timer of device 0000:00:1d.2 to 64
Jul 25 18:59:53 dimtux PCI: Setting latency timer of device 0000:00:1d.7 to 64
Jul 25 18:59:53 dimtux PCI: Setting latency timer of device 0000:00:1f.5 to 64
Jul 25 18:59:53 dimtux PCI: Setting latency timer of device 0000:00:1f.6 to 64
Jul 25 18:59:53 dimtux Please include the following information in bug reports:
Jul 25 18:59:53 dimtux - SWSUSP core : 2.0.0.96
Jul 25 18:59:53 dimtux - Kernel Version : 2.6.7
Jul 25 18:59:53 dimtux - Version spec. : 2.0.1
Jul 25 18:59:53 dimtux - Compiler vers. : 3.3
Jul 25 18:59:53 dimtux - Modules loaded :
Jul 25 18:59:53 dimtux - Attempt number : 1
Jul 25 18:59:53 dimtux - Pageset sizes : 17624 and 71885 (71885 low).
Jul 25 18:59:53 dimtux - Parameters : 0 0 0 32
Jul 25 18:59:53 dimtux - Calculations : Image size: 89660. Ram to suspend: 1073.
Jul 25 18:59:53 dimtux - Limits : 130928 pages RAM. Initial boot: 127682.
Jul 25 18:59:53 dimtux - Overall expected compression percentage: 0.
Jul 25 18:59:53 dimtux - Swapwriter active.
Jul 25 18:59:53 dimtux Swap available for image: 89509.
Jul 25 18:59:53 dimtux - LZF Compressor enabled.
Jul 25 18:59:53 dimtux Compressed 366628864 bytes into 248587610 (32 percent compression).
Jul 25 18:59:53 dimtux - Preemptive kernel.
Jul 25 18:59:53 dimtux - SMP kernel.
Jul 25 18:59:53 dimtux - Max ranges used: 50571 ranges in 149 pages.
Jul 25 18:59:53 dimtux - I/O speed: Write 22 MB/s, Read 23 MB/s.
Jul 25 20:27:28 dimtux NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-6106 Wed Jun 23 08:14:01 PDT 2004
Jul 25 20:27:28 dimtux SCSI subsystem initialized
Jul 25 20:27:28 dimtux ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device
Jul 25 20:27:28 dimtux scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Jul 25 20:27:28 dimtux Vendor: TEAC Model: DW-224E Rev: F.0A
Jul 25 20:27:28 dimtux Type: CD-ROM ANSI SCSI revision: 02
Jul 25 20:27:28 dimtux scsi.agent[24987]: cdrom at /devices/pci0000:00/0000:00:1f.1/ide1/1.0/host0/0:0:0:0
Jul 25 20:27:29 dimtux sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Jul 25 20:27:29 dimtux Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Jul 25 20:27:29 dimtux usbcore: registered new driver usbfs
Jul 25 20:27:29 dimtux usbcore: registered new driver hub
Jul 25 20:27:29 dimtux USB Universal Host Controller Interface driver v2.2
Jul 25 20:27:29 dimtux uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB (ICH4) USB UHCI #1
Jul 25 20:27:29 dimtux PCI: Setting latency timer of device 0000:00:1d.0 to 64
Jul 25 20:27:29 dimtux uhci_hcd 0000:00:1d.0: irq 10, io base 00001800
Jul 25 20:27:29 dimtux uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
Jul 25 20:27:29 dimtux hub 1-0:1.0: USB hub found
Jul 25 20:27:29 dimtux hub 1-0:1.0: 2 ports detected
Jul 25 20:27:29 dimtux uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB (ICH4) USB UHCI #2
Jul 25 20:27:29 dimtux PCI: Setting latency timer of device 0000:00:1d.1 to 64
Jul 25 20:27:29 dimtux uhci_hcd 0000:00:1d.1: irq 5, io base 00001820
Jul 25 20:27:29 dimtux uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
Jul 25 20:27:29 dimtux hub 2-0:1.0: USB hub found
Jul 25 20:27:29 dimtux hub 2-0:1.0: 2 ports detected
Jul 25 20:27:29 dimtux uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB (ICH4) USB UHCI #3
Jul 25 20:27:30 dimtux PCI: Setting latency timer of device 0000:00:1d.2 to 64
Jul 25 20:27:30 dimtux uhci_hcd 0000:00:1d.2: irq 5, io base 00001840
Jul 25 20:27:30 dimtux uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
Jul 25 20:27:30 dimtux hub 3-0:1.0: USB hub found
Jul 25 20:27:30 dimtux hub 3-0:1.0: 2 ports detected
Jul 25 20:27:30 dimtux ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
Jul 25 20:27:30 dimtux PCI: Setting latency timer of device 0000:00:1d.7 to 64
Jul 25 20:27:30 dimtux ehci_hcd 0000:00:1d.7: irq 5, pci mem e0f6e000
Jul 25 20:27:30 dimtux ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
Jul 25 20:27:30 dimtux PCI: cache line size of 128 is not supported by device 0000:00:1d.7
Jul 25 20:27:30 dimtux ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
Jul 25 20:27:30 dimtux hub 4-0:1.0: USB hub found
Jul 25 20:27:30 dimtux hub 4-0:1.0: 6 ports detected
Jul 25 20:27:31 dimtux PCI: Setting latency timer of device 0000:00:1f.5 to 64
Jul 25 20:27:31 dimtux intel8x0_measure_ac97_clock: measured 49348 usecs
Jul 25 20:27:31 dimtux intel8x0: clocking to 48000
Jul 25 20:27:32 dimtux PCI: Setting latency timer of device 0000:00:1f.6 to 64
Jul 25 20:27:32 dimtux CRON[25634]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 25 20:27:32 dimtux CRON[25632]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 20:27:32 dimtux MC'97 1 converters and GPIO not ready (0xf200)
Jul 25 20:27:33 dimtux ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
Jul 25 20:27:33 dimtux ieee1394.agent[25715]: ... no drivers for IEEE1394 product 0x/0x/0x
Jul 25 20:27:33 dimtux ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[d2004000-d20047ff] Max Packet=[2048]
Jul 25 20:27:33 dimtux Linux Kernel Card Services
Jul 25 20:27:33 dimtux options: [pci] [cardbus] [pm]
Jul 25 20:27:33 dimtux Yenta: CardBus bridge found at 0000:02:04.0 [1179:ff00]
Jul 25 20:27:33 dimtux Yenta: ISA IRQ mask 0x0898, PCI irq 10
Jul 25 20:27:33 dimtux Socket status: 30000006
Jul 25 20:27:33 dimtux Yenta: CardBus bridge found at 0000:02:04.1 [1179:ff00]
Jul 25 20:27:33 dimtux Yenta: ISA IRQ mask 0x0898, PCI irq 10
Jul 25 20:27:33 dimtux Socket status: 30000006
Jul 25 20:27:33 dimtux ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Jul 25 20:27:33 dimtux ohci_hcd: block sizes: ed 64 td 64
Jul 25 20:27:34 dimtux ieee1394.agent[25842]: ... no drivers for IEEE1394 product 0x/0x/0x
Jul 25 20:27:34 dimtux ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f332d003ec7]
Jul 25 20:27:34 dimtux rc-scripts: 'modprobe i82365' failed
Jul 25 20:27:34 dimtux rc-scripts: Trying alternative PCIC driver: yenta_socket
Jul 25 20:27:35 dimtux cardmgr[25895]: watching 2 sockets
Jul 25 20:27:35 dimtux cs: IO port probe 0x0c00-0x0cff: clean.
Jul 25 20:27:35 dimtux cs: IO port probe 0x0800-0x08ff: clean.
Jul 25 20:27:35 dimtux cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x20f 0x378-0x37f 0x4d0-0x4d7
Jul 25 20:27:35 dimtux cs: IO port probe 0x0a00-0x0aff: clean.
Jul 25 20:27:35 dimtux cardmgr[25895]: starting, version is 3.2.5
Jul 25 20:27:35 dimtux eth0: link down
Jul 25 20:27:44 dimtux ifplugd[7159]: Executing '/usr/sbin/ifplugd.action eth0 down'.
Jul 25 20:27:44 dimtux dhcpcd[25910]: recvfrom: Network is down
Jul 25 20:27:44 dimtux dhcpcd[25910]: sendto: Network is down
Jul 25 20:27:44 dimtux rc-scripts: ERROR: wrong args. ( eth0 / eth0 )
Jul 25 20:27:44 dimtux rc-scripts: Usage: net.eth0 { start|stop|restart }
Jul 25 20:27:44 dimtux rc-scripts: net.eth0 without arguments for full help
Jul 25 20:27:44 dimtux ifplugd[7159]: Program executed successfully.
Jul 25 20:27:44 dimtux cdrom: open failed.
Jul 25 20:27:44 dimtux NTFS driver 2.1.14 [Flags: R/O MODULE].
Jul 25 20:27:44 dimtux NTFS volume version 3.1.
Jul 25 20:27:45 dimtux rc-scripts: WARNING: "hotplug" has already been started.
Jul 25 20:27:45 dimtux rc-scripts: WARNING: "pcmcia" has already been started.
Jul 25 20:27:51 dimtux atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
Jul 25 20:27:51 dimtux atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
Jul 25 20:27:54 dimtux (liuwei-26506): starting (version 2.6.0), pid 26506 user 'liuwei'
Jul 25 20:27:54 dimtux (liuwei-26506): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jul 25 20:27:54 dimtux (liuwei-26506): Resolved address "xml:readwrite:/home/liuwei/.gconf" to a writable config source at position 1
Jul 25 20:27:54 dimtux (liuwei-26506): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jul 25 20:30:00 dimtux CRON[26631]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 20:38:32 dimtux su(pam_unix)[26658]: session opened for user root by liuwei(uid=1000)
Jul 25 20:40:00 dimtux CRON[26683]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 20:40:10 dimtux sudo: liuwei : TTY=pts/10 ; PWD=/home/liuwei ; USER=root ; COMMAND=/usr/local/sbin/dialup
Jul 25 20:40:11 dimtux codec_semaphore: semaphore is not ready [0x1][0x701300]
Jul 25 20:40:11 dimtux codec_write 1: semaphore is not ready for register 0x54
Jul 25 20:40:52 dimtux CSLIP: code copyright 1989 Regents of the University of California
Jul 25 20:40:52 dimtux PPP generic driver version 2.4.2
Jul 25 20:40:52 dimtux pppd[26736]: pppd 2.4.1 started by root, uid 0
Jul 25 20:40:52 dimtux pppd[26736]: Using interface ppp0
Jul 25 20:40:52 dimtux pppd[26736]: Connect: ppp0 <--> /dev/pts/11
Jul 25 20:40:53 dimtux PPP Deflate Compression module registered
Jul 25 20:40:53 dimtux pppd[26736]: local IP address 128.104.54.143
Jul 25 20:40:53 dimtux pppd[26736]: remote IP address 128.104.52.2
Jul 25 20:40:53 dimtux pppd[26736]: primary DNS address 144.92.104.20
Jul 25 20:40:53 dimtux pppd[26736]: secondary DNS address 144.92.9.22
Jul 25 20:45:35 dimtux (root-26915): starting (version 2.6.0), pid 26915 user 'root'
Jul 25 20:45:35 dimtux (root-26915): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jul 25 20:45:35 dimtux (root-26915): Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Jul 25 20:45:35 dimtux (root-26915): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jul 25 20:48:06 dimtux su(pam_unix)[26954]: session opened for user root by liuwei(uid=1000)
Jul 25 20:49:05 dimtux (root-26915): GConf server is not in use, shutting down.
Jul 25 20:49:05 dimtux (root-26915): Exiting
Jul 25 20:50:00 dimtux CRON[27029]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 21:00:00 dimtux CRON[27081]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 21:00:00 dimtux CRON[27087]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 25 21:07:37 dimtux codec_semaphore: semaphore is not ready [0x1][0x701304]
Jul 25 21:07:37 dimtux codec_write 1: semaphore is not ready for register 0x54
Jul 25 21:07:37 dimtux pppd[26736]: Terminating on signal 15.
Jul 25 21:07:37 dimtux pppd[26736]: Hangup (SIGHUP)
Jul 25 21:07:37 dimtux pppd[26736]: ioctl(PPPIOCSASYNCMAP): Inappropriate ioctl for device(25)
Jul 25 21:07:37 dimtux pppd[26736]: tcflush failed: Input/output error
Jul 25 21:07:37 dimtux pppd[26736]: Exit.
Jul 25 21:10:00 dimtux CRON[27184]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 21:20:00 dimtux CRON[27201]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 21:30:00 dimtux CRON[27211]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 21:39:42 dimtux (liuwei-26506): Exiting
Jul 25 21:39:42 dimtux su(pam_unix)[26954]: session closed for user root
Jul 25 21:39:42 dimtux su(pam_unix)[26658]: session closed for user root
Jul 25 21:39:47 dimtux atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
Jul 25 21:39:47 dimtux atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
Jul 25 21:39:50 dimtux (liuwei-27306): starting (version 2.6.0), pid 27306 user 'liuwei'
Jul 25 21:39:50 dimtux (liuwei-27306): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jul 25 21:39:50 dimtux (liuwei-27306): Resolved address "xml:readwrite:/home/liuwei/.gconf" to a writable config source at position 1
Jul 25 21:39:50 dimtux (liuwei-27306): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jul 25 21:40:00 dimtux CRON[27418]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 21:43:31 dimtux su(pam_unix)[27539]: session opened for user root by liuwei(uid=1000)
Jul 25 21:50:00 dimtux CRON[27615]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 21:51:07 dimtux (root-27639): starting (version 2.6.0), pid 27639 user 'root'
Jul 25 21:51:07 dimtux (root-27639): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jul 25 21:51:07 dimtux (root-27639): Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Jul 25 21:51:07 dimtux (root-27639): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jul 25 21:51:08 dimtux (root-27641): iid OAFIID:BrokenNoType:20000808 has a NULL type
Jul 25 21:51:08 dimtux (root-27641): invalid character '#' in iid 'OAFIID:This#!!%$iid%^$%_|~!OAFIID_ContainsBadChars'
Jul 25 21:53:32 dimtux su(pam_unix)[27648]: session opened for user root by liuwei(uid=1000)
Jul 25 22:00:00 dimtux CRON[27709]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 22:00:00 dimtux CRON[27712]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jul 25 22:03:28 dimtux (liuwei-27306): Exiting
Jul 25 22:03:28 dimtux su(pam_unix)[27648]: session closed for user root
Jul 25 22:03:28 dimtux su(pam_unix)[27539]: session closed for user root
Jul 25 22:03:33 dimtux atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
Jul 25 22:03:33 dimtux atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
Jul 25 22:03:36 dimtux (liuwei-27800): starting (version 2.6.0), pid 27800 user 'liuwei'
Jul 25 22:03:36 dimtux (liuwei-27800): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jul 25 22:03:36 dimtux (liuwei-27800): Resolved address "xml:readwrite:/home/liuwei/.gconf" to a writable config source at position 1
Jul 25 22:03:36 dimtux (liuwei-27800): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jul 25 22:03:37 dimtux (root-27639): GConf server is not in use, shutting down.
Jul 25 22:03:37 dimtux (root-27639): Exiting
Jul 25 22:05:39 dimtux su(pam_unix)[27926]: session opened for user root by liuwei(uid=1000)
Jul 25 22:06:03 dimtux (root-27933): starting (version 2.6.0), pid 27933 user 'root'
Jul 25 22:06:03 dimtux (root-27933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jul 25 22:06:03 dimtux (root-27933): Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Jul 25 22:06:03 dimtux (root-27933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jul 25 22:06:53 dimtux (root-27641): iid OAFIID:BrokenNoType:20000808 has a NULL type
Jul 25 22:06:53 dimtux (root-27641): invalid character '#' in iid 'OAFIID:This#!!%$iid%^$%_|~!OAFIID_ContainsBadChars'
Jul 25 22:08:25 dimtux su(pam_unix)[27926]: session closed for user root
Jul 25 22:10:00 dimtux CRON[28006]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 22:14:08 dimtux su(pam_unix)[28023]: session opened for user root by liuwei(uid=1000)
Jul 25 22:14:56 dimtux sudo: liuwei : TTY=pts/20 ; PWD=/home/liuwei ; USER=root ; COMMAND=/usr/local/sbin/dialup
Jul 25 22:14:56 dimtux codec_semaphore: semaphore is not ready [0x1][0x701300]
Jul 25 22:14:56 dimtux codec_write 1: semaphore is not ready for register 0x54
Jul 25 22:15:38 dimtux pppd[28076]: pppd 2.4.1 started by root, uid 0
Jul 25 22:15:38 dimtux pppd[28076]: Using interface ppp0
Jul 25 22:15:38 dimtux pppd[28076]: Connect: ppp0 <--> /dev/pts/21
Jul 25 22:15:38 dimtux pppd[28076]: local IP address 128.104.50.168
Jul 25 22:15:38 dimtux pppd[28076]: remote IP address 128.104.48.2
Jul 25 22:15:38 dimtux pppd[28076]: primary DNS address 144.92.104.20
Jul 25 22:15:38 dimtux pppd[28076]: secondary DNS address 144.92.9.22
Jul 25 22:16:45 dimtux codec_semaphore: semaphore is not ready [0x1][0x701300]
Jul 25 22:16:45 dimtux codec_write 1: semaphore is not ready for register 0x54
Jul 25 22:18:03 dimtux pppd[28076]: Terminating on signal 15.
Jul 25 22:18:03 dimtux pppd[28076]: Hangup (SIGHUP)
Jul 25 22:18:03 dimtux pppd[28076]: Modem hangup
Jul 25 22:18:03 dimtux pppd[28076]: Connection terminated.
Jul 25 22:18:03 dimtux pppd[28076]: Connect time 2.5 minutes.
Jul 25 22:18:03 dimtux pppd[28076]: Sent 10283 bytes, received 38166 bytes.
Jul 25 22:18:03 dimtux pppd[28076]: Exit.
Jul 25 22:18:52 dimtux sudo: liuwei : TTY=pts/22 ; PWD=/home/liuwei ; USER=root ; COMMAND=/usr/local/sbin/dialup
Jul 25 22:18:53 dimtux codec_semaphore: semaphore is not ready [0x1][0x701300]
Jul 25 22:18:53 dimtux codec_write 1: semaphore is not ready for register 0x54
Jul 25 22:19:33 dimtux pppd[28246]: pppd 2.4.1 started by root, uid 0
Jul 25 22:19:33 dimtux pppd[28246]: Using interface ppp0
Jul 25 22:19:33 dimtux pppd[28246]: Connect: ppp0 <--> /dev/pts/23
Jul 25 22:19:34 dimtux pppd[28246]: local IP address 128.104.50.172
Jul 25 22:19:34 dimtux pppd[28246]: remote IP address 128.104.48.2
Jul 25 22:19:34 dimtux pppd[28246]: primary DNS address 144.92.104.20
Jul 25 22:19:34 dimtux pppd[28246]: secondary DNS address 144.92.9.22
Jul 25 22:20:00 dimtux CRON[28268]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 22:30:00 dimtux CRON[28318]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 22:40:00 dimtux CRON[28377]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 25 22:42:33 dimtux (root-27933): GConf server is not in use, shutting down.
Jul 25 22:42:33 dimtux (root-27933): Exiting
Jul 25 22:43:29 dimtux pppd[28246]: Hangup (SIGHUP)
Jul 25 22:43:29 dimtux codec_semaphore: semaphore is not ready [0x1][0x701300]
Jul 25 22:43:29 dimtux codec_write 1: semaphore is not ready for register 0x54
Jul 25 22:43:29 dimtux pppd[28246]: Modem hangup
Jul 25 22:43:29 dimtux pppd[28246]: Connection terminated.
Jul 25 22:43:29 dimtux pppd[28246]: Connect time 24.0 minutes.
Jul 25 22:43:29 dimtux pppd[28246]: Sent 391507 bytes, received 1312705 bytes.
Jul 25 22:43:29 dimtux pppd[28246]: Exit.
Jul 25 22:43:29 dimtux su(pam_unix)[28023]: session closed for user root
Jul 25 22:43:35 dimtux (liuwei-27800): Exiting
Jul 25 22:43:45 dimtux su(pam_unix)[28413]: session opened for user root by liuwei(uid=1000)
Jul 25 22:43:49 dimtux su(pam_unix)[28413]: session closed for user root
Jul 25 22:43:56 dimtux rc-scripts: WARNING: you are stopping a boot service.
Jul 25 22:43:57 dimtux ehci_hcd 0000:00:1d.7: remove, state 1
Jul 25 22:43:57 dimtux usb usb4: USB disconnect, address 1
Jul 25 22:43:57 dimtux ehci_hcd 0000:00:1d.7: USB bus 4 deregistered
Jul 25 22:43:57 dimtux uhci_hcd 0000:00:1d.0: remove, state 1
Jul 25 22:43:57 dimtux usb usb1: USB disconnect, address 1
Jul 25 22:43:57 dimtux uhci_hcd 0000:00:1d.0: USB bus 1 deregistered
Jul 25 22:43:57 dimtux uhci_hcd 0000:00:1d.1: remove, state 1
Jul 25 22:43:57 dimtux usb usb2: USB disconnect, address 1
Jul 25 22:43:58 dimtux uhci_hcd 0000:00:1d.1: USB bus 2 deregistered
Jul 25 22:43:58 dimtux uhci_hcd 0000:00:1d.2: remove, state 1
Jul 25 22:43:58 dimtux usb usb3: USB disconnect, address 1
Jul 25 22:43:58 dimtux uhci_hcd 0000:00:1d.2: USB bus 3 deregistered
Jul 25 22:43:58 dimtux usbcore: deregistering driver usbfs
Jul 25 22:43:58 dimtux usbcore: deregistering driver hub
Jul 25 22:43:59 dimtux unloading Kernel Card Services
Jul 25 22:43:59 dimtux ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00023f332d003ec7]
Jul 25 22:44:00 dimtux Software Suspend 2.0.0.96: Initiating a software_suspend cycle.
Jul 25 22:44:32 dimtux Debug: sleeping function called from invalid context at include/asm/semaphore.h:145
Jul 25 22:44:32 dimtux in_atomic():1, irqs_disabled():1
Jul 25 22:44:32 dimtux [<c011b5e4>] __might_sleep+0xb2/0xd3
Jul 25 22:44:32 dimtux [<c0106aa0>] common_interrupt+0x18/0x20
Jul 25 22:44:32 dimtux [<c0219ee7>] tty_write+0xd7/0x300
Jul 25 22:44:32 dimtux [<c021fbc4>] write_chan+0x0/0x21a
Jul 25 22:44:32 dimtux [<c021a110>] redirected_tty_write+0x0/0xe1
Jul 25 22:44:32 dimtux [<c0164feb>] vfs_write+0xb0/0x119
Jul 25 22:44:32 dimtux [<c01650f9>] sys_write+0x42/0x63
Jul 25 22:44:32 dimtux [<c01381e5>] move_cursor_to+0x51/0x75
Jul 25 22:44:32 dimtux [<c0138e9c>] update_status+0x366/0x3fb
Jul 25 22:44:32 dimtux [<c0141771>] save_image_part1+0x26/0x1ba
Jul 25 22:44:32 dimtux [<c0141c68>] do_suspend2_suspend_2+0x8/0x34
Jul 25 22:44:32 dimtux [<c028cbc8>] do_suspend2_lowlevel+0x269/0x8a5
Jul 25 22:44:32 dimtux [<c01416fa>] save_image+0xc0/0x111
Jul 25 22:44:32 dimtux [<c01424f1>] software_suspend_pending+0x249/0x25f
Jul 25 22:44:32 dimtux [<c0196a93>] proc_file_write+0x0/0x42
Jul 25 22:44:32 dimtux [<c01405b6>] proc_software_suspend_pending+0x5/0xa
Jul 25 22:44:32 dimtux [<c0196aca>] proc_file_write+0x37/0x42
Jul 25 22:44:32 dimtux [<c0164feb>] vfs_write+0xb0/0x119
Jul 25 22:44:32 dimtux [<c016459b>] filp_close+0x59/0x86
Jul 25 22:44:32 dimtux [<c01650f9>] sys_write+0x42/0x63
Jul 25 22:44:32 dimtux [<c0106133>] syscall_call+0x7/0xb
Jul 25 22:44:32 dimtux
Jul 25 22:44:32 dimtux PCI: Setting latency timer of device 0000:00:1d.0 to 64
Jul 25 22:44:32 dimtux PCI: Setting latency timer of device 0000:00:1d.1 to 64
Jul 25 22:44:32 dimtux PCI: Setting latency timer of device 0000:00:1d.2 to 64
Jul 25 22:44:32 dimtux PCI: Setting latency timer of device 0000:00:1d.7 to 64
Jul 25 22:44:32 dimtux PCI: Setting latency timer of device 0000:00:1f.5 to 64
Jul 25 22:44:32 dimtux PCI: Setting latency timer of device 0000:00:1f.6 to 64
Jul 25 22:44:32 dimtux Please include the following information in bug reports:
Jul 25 22:44:32 dimtux - SWSUSP core : 2.0.0.96
Jul 25 22:44:32 dimtux - Kernel Version : 2.6.7
Jul 25 22:44:32 dimtux - Version spec. : 2.0.1
Jul 25 22:44:32 dimtux - Compiler vers. : 3.3
Jul 25 22:44:32 dimtux - Modules loaded :
Jul 25 22:44:32 dimtux - Attempt number : 2
Jul 25 22:44:32 dimtux - Pageset sizes : 12195 and 86973 (86973 low).
Jul 25 22:44:32 dimtux - Parameters : 0 0 0 32
Jul 25 22:44:32 dimtux - Calculations : Image size: 99307. Ram to suspend: 1073.
Jul 25 22:44:32 dimtux - Limits : 130928 pages RAM. Initial boot: 127682.
Jul 25 22:44:32 dimtux - Overall expected compression percentage: 0.
Jul 25 22:44:32 dimtux - Swapwriter active.
Jul 25 22:44:32 dimtux Swap available for image: 99172.
Jul 25 22:44:32 dimtux - LZF Compressor enabled.
Jul 25 22:44:32 dimtux Compressed 406192128 bytes into 266053123 (34 percent compression).
Jul 25 22:44:32 dimtux - Preemptive kernel.
Jul 25 22:44:32 dimtux - SMP kernel.
Jul 25 22:44:32 dimtux - Max ranges used: 46522 ranges in 137 pages.
Jul 25 22:44:32 dimtux - I/O speed: Write 24 MB/s, Read 24 MB/s.
Jul 26 19:49:28 dimtux NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-6106 Wed Jun 23 08:14:01 PDT 2004
Jul 26 19:49:28 dimtux syslog-ng[5993]: STATS: dropped 0
Jul 26 19:49:30 dimtux SCSI subsystem initialized
Jul 26 19:49:31 dimtux ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device
Jul 26 19:49:31 dimtux scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Jul 26 19:49:33 dimtux Vendor: TEAC Model: DW-224E Rev: F.0A
Jul 26 19:49:33 dimtux Type: CD-ROM ANSI SCSI revision: 02
Jul 26 19:49:34 dimtux scsi.agent[30148]: cdrom at /devices/pci0000:00/0000:00:1f.1/ide1/1.0/host0/0:0:0:0
Jul 26 19:49:35 dimtux sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Jul 26 19:49:35 dimtux Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Jul 26 19:49:38 dimtux cdrom: open failed.
Jul 26 19:49:42 dimtux NTFS driver 2.1.14 [Flags: R/O MODULE].
Jul 26 19:50:02 dimtux CRON[30266]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jul 26 19:50:06 dimtux NTFS volume version 3.1.
Jul 26 19:50:14 dimtux init: Switching to runlevel: 6
Jul 26 19:50:28 dimtux usbcore: registered new driver usbfs
Jul 26 19:50:28 dimtux usbcore: registered new driver hub
Jul 26 19:50:28 dimtux USB Universal Host Controller Interface driver v2.2
Jul 26 19:50:28 dimtux uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB (ICH4) USB UHCI #1
Jul 26 19:50:30 dimtux PCI: Setting latency timer of device 0000:00:1d.0 to 64
Jul 26 19:50:30 dimtux uhci_hcd 0000:00:1d.0: irq 10, io base 00001800
Jul 26 19:50:31 dimtux uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
Jul 26 19:50:31 dimtux hub 1-0:1.0: USB hub found
Jul 26 19:50:31 dimtux hub 1-0:1.0: 2 ports detected
Jul 26 19:50:32 dimtux uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB (ICH4) USB UHCI #2
Jul 26 19:50:33 dimtux PCI: Setting latency timer of device 0000:00:1d.1 to 64
Jul 26 19:50:33 dimtux uhci_hcd 0000:00:1d.1: irq 5, io base 00001820
Jul 26 19:50:33 dimtux uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
Jul 26 19:50:33 dimtux hub 2-0:1.0: USB hub found
Jul 26 19:50:33 dimtux hub 2-0:1.0: 2 ports detected
Jul 26 19:50:34 dimtux uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB (ICH4) USB UHCI #3
Jul 26 19:50:36 dimtux PCI: Setting latency timer of device 0000:00:1d.2 to 64
Jul 26 19:50:36 dimtux uhci_hcd 0000:00:1d.2: irq 5, io base 00001840
Jul 26 19:50:36 dimtux uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
Jul 26 19:50:36 dimtux hub 3-0:1.0: USB hub found
Jul 26 19:50:36 dimtux hub 3-0:1.0: 2 ports detected
Jul 26 19:50:47 dimtux ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
Jul 26 19:50:47 dimtux PCI: Setting latency timer of device 0000:00:1d.7 to 64
Jul 26 19:50:47 dimtux ehci_hcd 0000:00:1d.7: irq 5, pci mem e0f74000
Jul 26 19:50:47 dimtux ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
Jul 26 19:50:47 dimtux PCI: cache line size of 128 is not supported by device 0000:00:1d.7
Jul 26 19:50:47 dimtux ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
Jul 26 19:50:47 dimtux hub 4-0:1.0: USB hub found
Jul 26 19:50:47 dimtux hub 4-0:1.0: 6 ports detected
Jul 26 19:51:05 dimtux PCI: Setting latency timer of device 0000:00:1f.5 to 64
Jul 26 19:51:08 dimtux intel8x0_measure_ac97_clock: measured 968970 usecs
Jul 26 19:51:08 dimtux intel8x0: measured clock 5638 rejected
Jul 26 19:51:08 dimtux intel8x0: clocking to 48000
Jul 26 19:51:11 dimtux PCI: Setting latency timer of device 0000:00:1f.6 to 64
Jul 26 19:51:13 dimtux MC'97 1 converters and GPIO not ready (0xf200)
Jul 26 19:51:23 dimtux ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
Jul 26 19:51:23 dimtux ieee1394.agent[31640]: ... no drivers for IEEE1394 product 0x/0x/0x
Jul 26 19:51:24 dimtux ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[d2004000-d20047ff] Max Packet=[2048]
Jul 26 19:51:28 dimtux Linux Kernel Card Services
Jul 26 19:51:28 dimtux options: [pci] [cardbus] [pm]
Jul 26 19:51:28 dimtux Yenta: CardBus bridge found at 0000:02:04.0 [1179:ff00]
Jul 26 19:51:29 dimtux ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f332d003ec7]
Jul 26 19:51:29 dimtux Yenta: ISA IRQ mask 0x0898, PCI irq 10
Jul 26 19:51:29 dimtux Socket status: 30000006
Jul 26 19:51:29 dimtux Yenta: CardBus bridge found at 0000:02:04.1 [1179:ff00]
Jul 26 19:51:29 dimtux ieee1394.agent[31716]: ... no drivers for IEEE1394 product 0x/0x/0x
Jul 26 19:51:30 dimtux Yenta: ISA IRQ mask 0x0898, PCI irq 10
Jul 26 19:51:30 dimtux Socket status: 30000006
Jul 26 19:51:37 dimtux ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Jul 26 19:51:37 dimtux ohci_hcd: block sizes: ed 64 td 64
Jul 26 19:51:41 dimtux rc-scripts: 'modprobe i82365' failed
Jul 26 19:51:41 dimtux rc-scripts: Trying alternative PCIC driver: yenta_socket
Jul 26 19:51:47 dimtux cardmgr[32140]: watching 2 sockets
Jul 26 19:51:47 dimtux cs: IO port probe 0x0c00-0x0cff: clean.
Jul 26 19:51:47 dimtux cs: IO port probe 0x0800-0x08ff: clean.
Jul 26 19:51:48 dimtux cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x20f 0x378-0x37f 0x4d0-0x4d7
Jul 26 19:51:48 dimtux cs: IO port probe 0x0a00-0x0aff: clean.
Jul 26 19:51:48 dimtux cardmgr[32140]: starting, version is 3.2.5
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:56 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:58 dimtux logger: ACPI action lid is not defined
Jul 26 19:51:59 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:00 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:00 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:00 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:00 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:03 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:04 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:09 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:10 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:11 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:13 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:18 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:19 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:22 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:22 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:23 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:26 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:28 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:29 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:31 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:33 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:34 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:35 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:36 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:38 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:39 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:40 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:41 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:42 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:43 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:45 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:46 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:48 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:49 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:51 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:52 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:54 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:55 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:57 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:58 dimtux logger: ACPI action lid is not defined
Jul 26 19:52:59 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:00 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:01 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:03 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:04 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:06 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:07 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:08 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:09 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:10 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:12 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:14 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:15 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:16 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:17 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:19 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:19 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:20 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:21 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:22 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:24 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:25 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:27 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:28 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:30 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:33 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:34 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:35 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:35 dimtu
Back to top
View user's profile Send private message
zmedico
Developer
Developer


Joined: 02 Jan 2004
Posts: 338
Location: California USA

PostPosted: Tue Jul 27, 2004 3:33 am    Post subject: Reply with quote

dimfox2 wrote:
when resumes the computer becomes very, very slow, probably take 3 seconds to see a reaction, e.g. the letter you typed displayed, or using alt+Fn to switch between consoles.

Maybe some process is out of control? You can use "top" in the console to check your cpu usage and "free" to check your memory usage. From the log it looks like maybe acpid is caught in an endless loop.
_________________
Zac
Back to top
View user's profile Send private message
aloha99
n00b
n00b


Joined: 06 Jun 2004
Posts: 20

PostPosted: Tue Jul 27, 2004 4:45 am    Post subject: Re: howto: get swsusp2 (hibernate, suspend to disk) working Reply with quote

tuxlover wrote:
I guess this was supposed to read 2.0.0.100...?
Exactly ... updated my post, thanks.
Back to top
View user's profile Send private message
dimfox2
n00b
n00b


Joined: 10 Jul 2004
Posts: 24

PostPosted: Tue Jul 27, 2004 7:05 pm    Post subject: Reply with quote

zmedico wrote:

Maybe some process is out of control? You can use "top" in the console to check your cpu usage and "free" to check your memory usage. From the log it looks like maybe acpid is caught in an endless loop.


If the acpid is the problem, I can just stop the acpid when hibernate. I remeber there's a post in this thread that closing and reopening the lid when hibernate will generate tons of acpi events, I don't know if he has the same slowing down problem.


I hate to deal with this kind of things, because you have to reboot again and again.

Thanks for the advice, I will try to look at the cpu and memory useage next time this happens.
Back to top
View user's profile Send private message
zmedico
Developer
Developer


Joined: 02 Jan 2004
Posts: 338
Location: California USA

PostPosted: Wed Jul 28, 2004 4:21 am    Post subject: Reply with quote

dimfox2 wrote:
[tons of acpi events

Maybe if you put a call to "sleep" in the acpid script (sleep for 1 second or so) then it won't consume the whole cpu when there are tons of events.

dimfox2 wrote:
you have to reboot again and again.

It shouldn't take long to reboot if software suspend is working. I use it on my desktop computer for fast boot/shutdown times and it works great.
_________________
Zac
Back to top
View user's profile Send private message
mlybarger
Guru
Guru


Joined: 04 Sep 2002
Posts: 463

PostPosted: Thu Aug 05, 2004 2:49 pm    Post subject: Reply with quote

i'm having a few minor inconveniences with suspending on my laptop that hopefully i could get resolved. i am using a stock gentoo-dev-sources for my kernel. in there under the acpi/apm secion there's two items for suspend to ram and suspend to disk i think. i have those enabled and my grub.conf looks for resume on my swap space. i have acpid installed, and when i close my lid, it suspends to disk. i turn it back on and boot to linux and i'm back where i was. good. the problem is that i have to manually bring networking down and back up again when i restart it. it thinks it's up but it shouldn't be up at all. i might be on a different network, or no network at all when i resume (wifi)

so, am i shooting myself in the foot by using what ever suspend is in the gentoo-dev-sources default?

the with the swsup2 patches, does networking work like i'd expect it to?

also, is there a "soft" suspend where things go into a low power state and can wake up w/ having to go through boot sequence (grub and all).?

thanks.
Back to top
View user's profile Send private message
bfkeats
Apprentice
Apprentice


Joined: 20 Feb 2004
Posts: 268

PostPosted: Thu Aug 05, 2004 3:48 pm    Post subject: Reply with quote

Take a look in either /etc/suspend.conf or /etc/hibernate/hibernate.conf (I can't rember which). You can configure the script to bring down eth0 and not bring it up again. I don't know of a 'low power' type suspend.

Brian
Back to top
View user's profile Send private message
tuxlover
Apprentice
Apprentice


Joined: 21 Oct 2003
Posts: 297
Location: weltweit

PostPosted: Thu Aug 05, 2004 9:35 pm    Post subject: Reply with quote

mark_lybarger wrote:
so, am i shooting myself in the foot by using what ever suspend is in the gentoo-dev-sources default?

This howto-thread is about swsusp2. What you're using is swsusp1. I'm not sure about the configuration of swsusp1, but swsusp2 just works much better definitely.
Quote:
the with the swsup2 patches, does networking work like i'd expect it to?

It's easy to configure. Just install it and take a look at the config file.
Quote:
also, is there a "soft" suspend where things go into a low power state and can wake up w/ having to go through boot sequence (grub and all).?

What you want is called suspend to RAM. The kernel supports it (if you have the acpi patch installed which is in the gentoo-(dev-)sources. Read about how to activate it at http://acpi.sf.net/

dimfox wrote:
Here's the log (sorry for the lengthy post)
Jul 25 18:59:26 dimtux Software Suspend 2.0.0.96: Initiating a software_suspend cycle.
.... a lot of stuff...
Jul 26 19:53:35 dimtux logger: ACPI action lid is not defined
Jul 26 19:53:35 dimtu

Well, that really was lengthy :) Maybe you could edit your post and make it a little bit shorter... The gentoo forum search / database will thank you for it ;) Please post such lengthy logs like this: "...and then every second about 5 lines like this: ..."
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3 ... 5, 6, 7 ... 12, 13, 14  Next
Page 6 of 14

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum