View Single Post
  #6  
Old 4th December 2006, 17:33
Merc Merc is offline
Junior Member
 
Join Date: Nov 2006
Location: Chemnitz, Germany
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Here's a bit from the dom0's dmesg output (some of the last lines):

Code:
ohci_hcd 0000:00:02.3: OHCI Host Controller
ohci_hcd 0000:00:02.3: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.3: irq 10, io mem 0xcffff000
8250_pnp: Unknown symbol serial8250_unregister_port
8250_pnp: Unknown symbol serial8250_register_port
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
Linux agpgart interface v0.101 (c) Dave Jones
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
8250_pnp: Unknown symbol serial8250_unregister_port
8250_pnp: Unknown symbol serial8250_register_port
sis630_smbus 0000:00:02.0: SIS630 comp. bus not detected, module not inserted.
sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x0c00
agpgart: Detected SiS 735 chipset
agpgart: AGP aperture is 4M @ 0xd0000000
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Adding 489972k swap on /dev/hda2.  Priority:-1 extents:1 across:489972k
EXT3 FS on hda1, internal journal
it87: Found IT8705F chip at 0x290, revision 1
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKC] -> GSI 12 (level, low) -> IRQ 12
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
NET: Registered protocol family 10
As you can see, the line "Adding 489972k swap on /dev/hda2. Priority:-1 extents:1 across:489972k" indicates, that swap is used by the dom0.
And it's also this line that I miss reviewing the kern.log output of the domU.

The really strange thing is this:

Code:
Broadcast message from root (tty1) (Mon Dec  4 16:29:41 2006):

The system is going down for system halt NOW!
INIT: Switching to runlevel: 0
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
Stopping X display manager: xdm not running (/var/run/xdm.pid not found).
Stopping periodic command scheduler: cron.
Stopping BitTorrent tracker: bttrack.bittorrent.
Stopping internet superserver: inetd.
Stopping OpenBSD Secure Shell server: sshd.
Stopping X font server: xfs.
Stopping kernel log daemon: klogd.
Stopping system log daemon: syslogd.
Sending all processes the TERM signal...done.
Sending all processes the KILL signal...done.
Saving random seed...done.
Unmounting remote and non-toplevel virtual filesystems...done.
Deconfiguring network interfaces...done.
Cleaning up ifupdown...done.
Deactivating swap...done.
Unmounting local filesystems...done.
System halted.
The line "Deactivating swap...done." pops into my eye.
Why would a system deactivate swap if it doesn't use it ?
Reply With Quote