Problem with jumbo frames and dhcp
Hi, I'm trying to set a MTU of 9k for my gigabit network. All works well for that, however it doesn't work with DHCP. In the dhcpd.conf file on the server, I put option interface-mtu 9000; and then in the /etc/network/interfaces file on the clients I put iface ethx inet dhcp, however when I do ifup on the dhcp clients it says SIOCSIFMTU: Invalid argument. The only way around this is to not use a dhcp client and set everything manually. I think this might be a bug. I'm using the official DHCP servers and clients from the ISC, with debian etch stable AMD64. _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
problems while setting up a counter-strike: source server
Hi, I have already sent this question, but it seems like the formatting of my email go destroyed, so I decided to send it again from another email address. Here is my original question: Hi, I want to run a counter-strike:source server. I followed a guide online, it says I must run an utility called 'steam' that will update the server to the latest version. I tried to run it, but I get an error: [EMAIL PROTECTED]:~$ ls -l total 21436 drwxr-x--- 2 srcds srcds4096 2007-05-08 21:53 bin drwxr-x--- 13 srcds srcds4096 2007-05-10 03:55 cstrike drwxr-x--- 7 srcds srcds 94 2007-05-08 21:53 hl2 -rwxr--r-- 1 srcds srcds 3513408 2007-05-08 16:29 hldsupdatetool.bin -rw-r--r-- 1 srcds srcds1395 2007-05-10 01:58 InstallRecord.blob -rw-r--r-- 1 srcds srcds 305 2007-05-10 01:57 maplist -rw-r--r-- 1 srcds srcds 690024 2007-05-10 01:58 out -rw-r--r-- 1 srcds srcds3413 2005-04-07 17:07 readme.txt -rwxr-xr-x 1 srcds srcds 105 2007-05-10 03:48 run -rwxr-xr-- 1 srcds srcds 183860 2007-05-08 21:53 srcds_amd -rwxr-xr-- 1 srcds srcds 183828 2007-05-08 21:53 srcds_i486 -rwxr-xr-- 1 srcds srcds 183828 2007-05-08 21:53 srcds_i686 -rwxr-xr-x 1 srcds srcds 57449 2007-05-10 01:57 srcds_master -rw-r--r-- 1 srcds srcds 344 2007-05-10 01:57 srcds_master.conf -rwxr-xr-- 1 srcds srcds 10164 2007-05-08 21:53 srcds_run -rwxr-xr-x 1 srcds srcds 7963393 2007-05-09 00:33 steam -r-xr-xr-x 1 srcds srcds 358301 2005-11-16 00:28 test1.so -r-xr-xr-x 1 srcds srcds 453372 2005-11-16 00:28 test2.so -r-xr-xr-x 1 srcds srcds 8306090 2005-11-16 00:28 test3.so [EMAIL PROTECTED]:~$ ./steam -command update -game Counter-Strike Source -dir . -verify_all -retry -bash: ./steam: No such file or directory also if I try to run the server it also shows an error: [EMAIL PROTECTED]:~$ ./srcds_run -console -game cstrike +map cs_assault Auto detecting CPU Using AMD Optimised binary. ./srcds_run: line 362: ./srcds_amd: No such file or directory Add -debug to the ./srcds_run command line to generate a debug.log to help with solving this problem Thu May 10 21:04:01 EDT 2007: Server Quit I use Debian Etch stable AMD64 I already tried to replace all files in case they were corrupted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problems while setting up a counter-strike:source server
Hi, I want to run a counter-strike:source server. I followed a guide online, it says I must run an utility called 'steam' that will update the server to the latest version. I tried to run it, but I get an error: [EMAIL PROTECTED]:~$ ls -ltotal 21436drwxr-x--- 2 srcds srcds4096 2007-05-08 21:53 bindrwxr-x--- 13 srcds srcds4096 2007-05-10 03:55 cstrikedrwxr-x--- 7 srcds srcds 94 2007-05-08 21:53 hl2-rwxr--r-- 1 srcds srcds 3513408 2007-05-08 16:29 hldsupdatetool.bin-rw-r--r-- 1 srcds srcds1395 2007-05-10 01:58 InstallRecord.blob-rw-r--r-- 1 srcds srcds 305 2007-05-10 01:57 maplist-rw-r--r-- 1 srcds srcds 690024 2007-05-10 01:58 out-rw-r--r-- 1 srcds srcds3413 2005-04-07 17:07 readme.txt-rwxr-xr-x 1 srcds srcds 105 2007-05-10 03:48 run-rwxr-xr-- 1 srcds srcds 183860 2007-05-08 21:53 srcds_amd-rwxr-xr-- 1 srcds srcds 183828 2007-05-08 21:53 srcds_i486-rwxr-xr-- 1 srcds srcds 183828 2007-05-08 21:53 srcds_i686-rwxr-xr-x 1 srcds srcds 57449 2007-05-10 01:57 srcds_master-rw-r--r-- 1 srcds srcds 344 2007-05-10 01:57 srcds_master.conf-rwxr-xr-- 1 srcds srcds 10164 2007-05-08 21:53 srcds_run-rwxr-xr-x 1 srcds srcds 7963393 2007-05-09 00:33 steam-r-xr-xr-x 1 srcds srcds 358301 2005-11-16 00:28 test1.so-r-xr-xr-x 1 srcds srcds 453372 2005-11-16 00:28 test2.so-r-xr-xr-x 1 srcds srcds 8306090 2005-11-16 00:28 test3.so [EMAIL PROTECTED]:~$ ./steam -command update -game Counter-Strike Source -dir . -verify_all -retry-bash: ./steam: No such file or directory also if I try to run the server it also shows an error: [EMAIL PROTECTED]:~$ ./srcds_run -console -game cstrike +map cs_assaultAuto detecting CPUUsing AMD Optimised binary../srcds_run: line 362: ./srcds_amd: No such file or directoryAdd -debug to the ./srcds_run command line to generate a debug.log to help with solving this problemThu May 10 21:04:01 EDT 2007: Server Quit I use Debian Etch stable AMD64 I already tried to replace all files in case they were corrupted. _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
RE: Problems with sarge to etch upgrade
Date: Sat, 21 Apr 2007 02:50:34 -0700 From: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Re: Problems with sarge to etch upgradehi patrick, you have a problem with the sgi xfs filesystem. i got currently the information there is a bug in linux--2.6 i am searching for it here: bugs.debian.org/linux-2.6 for xfs i had the same error on two completly differently machine's (hardware was different). both had debian sarge 2.6.8 with software-raid1 and lvm running. solution, run your rescue-cd (i worked with knoppix, but will test slax next time (smaller and faster than knoppix ;) start your raiddevices and volumegroups and run xfs_repair on that filesystem. maybe you have to repair without the journal, by using the -L option. looking for a solution, for the other server's ;) greetings thomas -- View this message in context: http://www.nabble.com/Problems-with-sarge-to-etch-upgrade-tf3551243.html#a10115414 Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Thanks a lot! I finally had some time to take the machine down and repair the filesystems: that was the problem! It now works perfectly, and can do all the things where it crashed before. It found some error in my /tmp and my /var. I have now stress tested the filesystems to make sure they really work and they seem fine. Here is what I did: Boot from knoppix cd (I used 4.0) ensure you have a network connection edit /etc/apt/sources.list in knoppix to make sure it downloads only from sarge instead of stable unstable testing experimental etc. aptitude update aptitude install lvm2 lndir /lib/lvm-200/ /usr/sbin/ vgscanvgchange -a ythen I can use xfs_check and xfs_repair on /dev/VGname/LVname I still don't know why this filesystem corruption occured while I was updating to etch... _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
RE: Aptitude does not start
Date: Fri, 20 Apr 2007 20:59:09 +0200 From: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Aptitude does not start All the sudden aptitude refuse to start. When I try to start it show little box saying Loading cache and then exit with: Uncaught exception: vs_progress.cc:38: virtual void vs_progress::paint(const style): Assertion Percent=0 Percent=100 failed. I apsolutlu have no idea what could causye this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I'm having a similar problem Uncaught exception: vs_progress.cc:38: virtual void vs_progress::paint(const style): Assertion Percent=0 Percent=100 failed. This happens when the ncurses-based interface starts (it seems to be just after it displays Reading extended state information) using aptitude in text-mode only (with commands like aptitude update) does work aptitude 0.4.4 compiled at Mar 14 2007 06:46:28Compiler: g++ 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) NCurses version: 5.5libsigc++ version: 2.0.17 debian is etch stable _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
RE: Problems with sarge to etch upgrade
From: [EMAIL PROTECTED]To: [EMAIL PROTECTED]CC: debian-user@lists.debian.orgSubject: RE: Problems with sarge to etch upgradeDate: Sun, 15 Apr 2007 17:37:37 -0400 Date: Sun, 15 Apr 2007 14:28:32 -0400 From: [EMAIL PROTECTED] CC: debian-user@lists.debian.org Subject: Re: Problems with sarge to etch upgrade To: debian-user@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrick Cummings escribió: The computer was working perfectly since almost 1 year before the upgrade and as far as I know there is no hardware problem with it. Thanks for your time Well, there's a problem with your RAM memory, try with another memory and check if the error persists, that's a warning only, you can start normally commenting the line you mentioned before but there'll be probably some crashes because of this. Regards, Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://talug.org.ve http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGIm7POKCtW8rKsRgRArIeAKCyhaSL/syrnozQlet4B1rUVufJ0gCgsG4c 0u/DSNV8x+miA1tjy+Q3n00= =uqmx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I will check my RAM with memtest when I can afford a downtime, however this problem appeared exactly after I upgraded from sarge to etch, so I find it weird it might be hardware related.Right now I'm running with my /tmp(was xfs) in the same partition as /(currently ext3), and it is stable. So I finally had some time and tested the memory with memtest. I got 5 passes without errors, so I guess it was not that. It's also ECC memory. However now the problem is getting worst. Sometimes it crashes ans I lose access to /var. It crashes every 30 minutes and I must restart the computer. Is there any way to get out of this without a clean install? I think that's what I will do. That will be very complex since there is so much on this computer. I guess I should have continued with sarge. _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
RE: permissions (samba and nfsd)
From: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: permissions (samba and nfsd) Date: Tue, 17 Apr 2007 16:45:13 +0200 Hi folks :-) I've on my debian stable: drwxrwx--T 6 root samba 4096 Nov 30 17:13 /samba so, only samba's users can read and write into the samba dir (no system user). Now, i've installed also nfsd, but when the clients try to mount the same dir, the permissions are: drwxrwx--T 6 root 1039 4096 2006-11-30 17:13 samba cd samba Permission denied Can i resolve this problem? Thanks! Pol -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Make sure that the values in `/etc/group` match for every machine that will use nfs. Here, 1039 is the group id of the samba group on your server. 1039 is undefined on your clients. _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
RE: Problems with sarge to etch upgrade
Date: Sun, 15 Apr 2007 14:28:32 -0400 From: [EMAIL PROTECTED] CC: debian-user@lists.debian.org Subject: Re: Problems with sarge to etch upgrade To: debian-user@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrick Cummings escribió: The computer was working perfectly since almost 1 year before the upgrade and as far as I know there is no hardware problem with it. Thanks for your time Well, there's a problem with your RAM memory, try with another memory and check if the error persists, that's a warning only, you can start normally commenting the line you mentioned before but there'll be probably some crashes because of this. Regards, Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://talug.org.ve http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGIm7POKCtW8rKsRgRArIeAKCyhaSL/syrnozQlet4B1rUVufJ0gCgsG4c 0u/DSNV8x+miA1tjy+Q3n00= =uqmx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I will check my RAM with memtest when I can afford a downtime, however this problem appeared exactly after I upgraded from sarge to etch, so I find it weird it might be hardware related. Right now I'm running with my /tmp(was xfs) in the same partition as /(currently ext3), and it is stable. _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
RE: Problems with sarge to etch upgrade
Date: Thu, 12 Apr 2007 08:58:56 -0400 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: Problems with sarge to etch upgrade Patrick Cummings wrote: I made a complete capture of the console output, I would love to know how you did that! Maybe I'm just a Debian n00b... Michael This is not something I did with debian. I simply pasted the text from a serial console. You can connect two computers' serial ports together using a null modem cable and then use it to control the computer using a terminal program on the second machine. All the text from the dmesg and all that stuff goes to the serial console because I set it as my default terminal. _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
RE: Problems with sarge to etch upgrade
Date: Tue, 10 Apr 2007 09:37:55 -0400 To: [EMAIL PROTECTED] Subject: Re: Problems with sarge to etch upgrade From: [EMAIL PROTECTED] On Tue, Apr 10, 2007 at 02:00:09AM -0400, Patrick Cummings wrote: Hello list, I just upgraded from sarge to etch using apt-get dist-upgrade. I have a few problems. The OS won't completely start. I made a complete capture of the console output, if anybody is kind enough to try to understand what is happening and help me. [snip a fine looking dmesg] I can get the computer to start perfectly if I comment out everything in the start section from /etc/init.d/x11-common and /etc/init.d/xfree86-common I find it weird that I have a problem from theses files since I don't use x11 at all.If you don't use x11 then purge anything related to X. Did you follow the upgrade instructions in the release notes? If you didn't, then you're not alone. If you did and still had a problem, then it could indicate a deficiency in the notes warranting a bug report. Doug. Ok, I did purge x11 and it fixed the problem. The gjc compiler was depending on it, so it got purged too. However, now the message I was getting after the boot appears at random times while the computer is running. Every time the message appears I need to restart the computer, or else it will only partially work. For example, after the message appears, it is impossible to access some samba shares stored locally on this computer. Here it is: BUG: unable to handle kernel NULL pointer dereference at virtual address 0060 printing eip: f8be4908 *pde = Oops: [#1] SMP Modules linked in: nfs nfsd exportfs lockd nfs_acl sunrpc ipv6 bridge ipt_MASQUERADE xt_limit xt_multiport ipt_LOG xt_tcpudp xt_state iptable_mangle iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables x_tables xfs raid0 md_mod fuse ide_disk evdev psmouse i2c_piix4 serio_raw i2c_core floppy pcspkr parport_pc parport rtc shpchp pci_hotplug sworks_agp agpgart sg ext3 jbd mbcache dm_mirror dm_snapshot dm_mod ide_cd cdrom sd_mod serverworks sata_sil ohci_hcd ips generic libata e1000 ide_core usbcore scsi_mod tlan e100 mii thermal processor fan CPU: 1 EIP: 0060:[f8be4908] Not tainted VLI EFLAGS: 00010246 (2.6.18-4-686 #1) EIP is at xfs_inobt_update+0x2b/0x87 [xfs] eax: 0001 ebx: f7d51812 ecx: bf8697df edx: esi: c013fb56 edi: 0008 ebp: esp: f64d1b24 ds: 007b es: 007b ss: 0068 Process vim (pid: 10122, ti=f64d task=f6d17550 task.ti=f64d) Stack: f58bac08 0001 c013fb57 f7d51812 0004 f58bac08 0001 f8be1f2d c013fb56 0008 0080 f5fde278 12000286 0008 0001 f7d42400 f7d51800 0001 Call Trace: [c013fb57] handle_IRQ_event+0x23/0x49 [f8be1f2d] xfs_dialloc+0x10ce/0x123d [xfs] [c013fb56] handle_IRQ_event+0x22/0x49 [c016a102] do_select+0x3b7/0x3d4 [c011669e] __wake_up+0x2a/0x3d [c013fb56] handle_IRQ_event+0x22/0x49 [c013fc54] __do_IRQ+0xd7/0xe8 [f8be8e37] xfs_ialloc+0x41/0x453 [xfs] [f8bfb561] xfs_dir_ialloc+0x62/0x241 [xfs] [f8c02579] xfs_mkdir+0x290/0x561 [xfs] [f8bb87d7] xfs_acl_get_attr+0x3b/0x5c [xfs] [f8c098d8] xfs_vn_mknod+0x1c0/0x380 [xfs] [c013fb57] handle_IRQ_event+0x23/0x49 [c0112613] end_level_ioapic_vector+0x14/0x7d [c013fc54] __do_IRQ+0xd7/0xe8 [c01050ea] do_IRQ+0x48/0x52 [c01036b6] common_interrupt+0x1a/0x20 [f8bd7765] xfs_dir_lookup+0x91/0xff [xfs] [f8c09dc2] xfs_vn_permission+0xf/0x13 [xfs] [c0165571] permission+0xa3/0xb6 [f8c09aa2] xfs_vn_mkdir+0xa/0xc [xfs] [c016588e] vfs_mkdir+0xba/0xf7 [c0167d56] sys_mkdirat+0x87/0xbb [c01050ea] do_IRQ+0x48/0x52 [c01036b6] common_interrupt+0x1a/0x20 [c0167d99] sys_mkdir+0xf/0x13 [c0102c11] sysenter_past_esp+0x56/0x79 Code: 55 57 56 53 83 ec 10 89 54 24 08 8b 74 24 24 89 04 24 8b 7c 24 28 8b 50 24 8b 40 44 0f c9 89 c5 89 44 24 04 c1 e5 04 8b 44 24 08 03 6a 60 0f c8 89 44 24 08 89 45 00 89 f8 89 4d 04 89 f1 0f c9 EIP: [f8be4908] xfs_inobt_update+0x2b/0x87 [xfs] SS:ESP 0068:f64d1b24 What does this kind of message means exactly? What can I do to find what kind of problem it is? I think it might be related with /tmp, because everytime this message appears my shells freezes if I try to do any accesses in /tmp. For example, man does not work because it writes to /tmp. _ Soyez parmi les premiers à essayer Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
Problems with sarge to etch upgrade
Hello list, I just upgraded from sarge to etch using apt-get dist-upgrade. I have a few problems. The OS won't completely start. I made a complete capture of the console output, if anybody is kind enough to try to understand what is happening and help me. Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon Mar 26 17:17:36 UTC 2007BIOS-provided physical RAM map: BIOS-e820: - 0009d400 (usable) BIOS-e820: 0009d400 - 000a (reserved) BIOS-e820: 000e4400 - 0010 (reserved) BIOS-e820: 0010 - 4fff (usable) BIOS-e820: 4fff - 4c00 (ACPI data) BIOS-e820: 4c00 - 5000 (ACPI NVS) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff0 - 0001 (reserved)383MB HIGHMEM available.896MB LOWMEM available.found SMP MP-table at 000f6900DMI 2.3 present.ACPI: PM-Timer IO Port: 0x404ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)Processor #0 6:8 APIC version 17ACPI: LAPIC (acpi_id[0x01] lapic_id[0x03] enabled)Processor #3 6:8 APIC version 17ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])ACPI: IOAPIC (id[0x04] address[0xfec0] gsi_base[0])IOAPIC[0]: apic_id 4, version 17, address 0xfec0, GSI 0-15ACPI: IOAPIC (id[0x05] address[0xfec01000] gsi_base[16])IOAPIC[1]: apic_id 5, version 17, address 0xfec01000, GSI 16-31ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 31 low level)Enabling APIC mode: Flat. Using 2 I/O APICsUsing ACPI (MADT) for SMP configuration informationAllocating PCI resources starting at 6000 (gap: 5000:aec0)Detected 999.840 MHz processor.Built 1 zonelists. Total pages: 327664Kernel command line: root=/dev/sda1 ro console=tty0 console=ttyS1,57600n8 Enabling fast FPU save and restore... done.Enabling unmasked SIMD FPU exception support... done.Initializing CPU#0PID hash table entries: 4096 (order: 12, 16384 bytes)Console: colour VGA+ 80x25Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)Memory: 1290548k/1310656k available (1544k kernel code, 18860k reserved, 577k data, 196k init, 393152k highmem)Checking if this processor honours the WP bit even in supervisor mode... Ok.Calibrating delay using timer specific routine.. 2000.58 BogoMIPS (lpj=4001174)Security Framework v1.0.0 initializedSELinux: Disabled at boot.Capability LSM initializedMount-cache hash table entries: 512CPU: L1 I cache: 16K, L1 D cache: 16KCPU: L2 cache: 256KIntel machine check architecture supported.Intel machine check reporting enabled on CPU#0.Compat vDSO mapped to e000.Checking 'hlt' instruction... OK.SMP alternatives: switching to UP codeACPI: Core revision 20060707CPU0: Intel Pentium III (Coppermine) stepping 0aSMP alternatives: switching to SMP codeBooting processor 1/0 eip 3000Initializing CPU#1Calibrating delay using timer specific routine.. 1999.60 BogoMIPS (lpj=3999219)CPU: L1 I cache: 16K, L1 D cache: 16KCPU: L2 cache: 256KIntel machine check architecture supported.Intel machine check reporting enabled on CPU#1.CPU1: Intel Pentium III (Coppermine) stepping 0aTotal of 2 processors activated (4000.19 BogoMIPS).ENABLING IO-APIC IRQs..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1checking TSC synchronization across 2 CPUs: passed.Brought up 2 CPUsmigration_cost=821checking if image is initramfs... it isFreeing initrd memory: 5100k freedNET: Registered protocol family 16ACPI: bus type pci registeredPCI: PCI BIOS revision 2.10 entry at 0xfdb57, last bus=3PCI: Using configuration type 1Setting up standard PCI resourcesACPI: Interpreter enabledACPI: Using IOAPIC for interrupt routingACPI: PCI Interrupt Link [IR1] (IRQs 5 10) *9ACPI: PCI Interrupt Link [LN0E] (IRQs *14)ACPI: PCI Interrupt Link [LN10] (IRQs *16)ACPI: PCI Interrupt Link [LN11] (IRQs *17)ACPI: PCI Interrupt Link [LN12] (IRQs *18)ACPI: PCI Interrupt Link [LN13] (IRQs *19)ACPI: PCI Interrupt Link [LN14] (IRQs *20)ACPI: PCI Interrupt Link [LN15] (IRQs *21)ACPI: PCI Interrupt Link [LN16] (IRQs *22)ACPI: PCI Interrupt Link [LN17] (IRQs *23)ACPI: PCI Interrupt Link [LN18] (IRQs *24)ACPI: PCI Interrupt Link [LN19] (IRQs *25)ACPI: PCI Interrupt Link [LN1A] (IRQs *26)ACPI: PCI Interrupt Link [LN1B] (IRQs *27)ACPI: PCI Interrupt Link [LN1C] (IRQs *28)ACPI: PCI Interrupt Link [LN1D] (IRQs *29)ACPI: PCI Root Bridge [PCI0] (:00)PCI: Firmware left :00:03.0 e100 interrupts enabled, disablingPCI: Firmware left :00:07.0 e100 interrupts enabled, disablingPCI: Firmware left :02:04.0 e100 interrupts enabled, disablingPCI: Firmware left :02:05.0 e100 interrupts enabled, disablingACPI: Embedded Controller [EC0] (gpe 4) interrupt
