[OT] [KORG] BitTorrents?
Is there any reason for not putting the kernel(and it's updates) up on a tracker on kernel.org? I looked through the list and noted that there has not been any discussion in regards to this topic. I personally don't have enough up-stream bandwidth(384K) to support a tracker, but I have enough to contribute to a torrent... Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.13-rc6-git10 test report [x86_64]
Saw the new git today and thought I would test it out. Still running with pci=noacpi for my mobo, but compiles ok and runs well. Sean Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb pci=noacpi iommu=memaper=3) Linux version 2.6.13-rc6-git11 ([EMAIL PROTECTED]) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Fri Aug 19 13:15:31 PDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009e400 (usable) BIOS-e820: 0009e400 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff - bfff3000 (ACPI NVS) BIOS-e820: bfff3000 - c000 (ACPI data) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - 0001 (reserved) BIOS-e820: 0001 - 0001c000 (usable) ACPI: RSDP (v000 Nvidia) @ 0x000f7650 ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff3040 ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x0001 LTP 0x0001) @ 0xbfff9680 ACPI: SRAT (v001 AMDHAMMER 0x0001 AMD 0x0001) @ 0xbfff9880 ACPI: MCFG (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff99c0 ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff9580 ACPI: DSDT (v001 NVIDIA AWRDACPI 0x1000 MSFT 0x010e) @ 0x SRAT: PXM 0 -> APIC 0 -> CPU 0 -> Node 0 SRAT: PXM 1 -> APIC 1 -> CPU 1 -> Node 1 SRAT: Node 0 PXM 0 0-9 SRAT: Node 0 PXM 0 0-bfff SRAT: Node 0 PXM 0 0-13fff SRAT: Node 1 PXM 1 14000-1bfff Using 25 for the hash shift. Max adder is 1bfff Bootmem setup node 0 -00013fff Bootmem setup node 1 00014000-0001bfff On node 0 totalpages: 1310719 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 1306623 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 On node 1 totalpages: 524287 DMA zone: 0 pages, LIFO batch:1 Normal zone: 524287 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 Nvidia board detected. Ignoring ACPI timer override. ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Using ACPI for processor (LAPIC) configuration information Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: OEM0 <6>Product ID: PROD <6>APIC at: 0xFEE0 I/O APIC #4 Version 17 at 0xFEC0. Setting APIC routing to flat Processors: 2 Allocating PCI resources starting at c000 (gap: c000:2000) Checking aperture... CPU 0: aperture @ 1000 size 32 MB Aperture from northbridge cpu 0 too small (32 MB) Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 256 MB of RAM Mapping aperture over 262144 KB of RAM @ 1000 Built 2 zonelists Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb pci=noacpi iommu=memaper=3 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 3.579545 MHz PM timer. time.c: Detected 2010.343 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) Memory: 5908456k/7340032k available (2448k kernel code, 0k reserved, 1304k data, 224k init) Calibrating delay using timer specific routine.. 4024.90 BogoMIPS (lpj=8049809) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 0(1) -> Node 0 -> Core 0 mtrr: v2.0 (20020519) ACPI: setting ELCR to 1a28 (from 1828) Using IO-APIC 4 ..MP-BIOS bug: 8254 timer not connected to IO-APIC works. Using local APIC timer interrupts. Detected 12.564 MHz APIC timer. Booting processor 1/2 APIC 0x1 Initializing CPU#1 Calibrating delay using timer specific routine.. 2010.47 BogoMIPS (lpj=4020947) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 1(1) -> Node 1 -> Core 0 AMD Opteron(tm) Processor 246 stepping 0a CPU 1: Syncing TSC to CPU 0. Brough
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, 2005-08-19 at 08:59 -0700, Peter Buckingham wrote: > Andi Kleen wrote: > > On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote: > > > >>Andi Kleen wrote: > >> > >>>At least his original error message can only happen when CONFIG_GART_IOMMU > >>>is disabled. > >>> > >>>PCI-DMA: More that 4GB of RAM and no IOMMU > >>>PCI-DMA: 32bit PCI IO may malfunction.<6>PCI-DMA: Disabling IOMMU > >> > >>Yeah, I agree. In the later dmesgs, though, it seems to be enabled. > > > > > > Those don't show any failure. > > no they don't. basically it just says your bios hasn't configured enough > IOMMU space, so the kernel is going to do it anyway. it's really just a > warning or an fyi rather than an error. i may have chosen the word > poorly ;-) > > in short Sean, this isn't a big deal. you only really need to change > this if you want to remove a warning from your dmesg output. > > peter Well, there doesn't appear to be any reference to a setting in my BIOS for this size(IOMMU). So I don't think that I can change it! :( The machine is working quite a bit better with pci=noacpi in leu of disabling ACPI in the BIOS, but there are still those nasty errors in reference to the ACPI tables being broken: ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND search_node 8101428572c0 start_node 8101428572c0 return_node And this one about the 8254 timer: ..MP-BIOS bug: 8254 timer not connected to IO-APIC And finally, I think that something else kind of wierd is happening with the on-board sensors. lm_sensors is having trouble detecting the fan speeds and temperatures of the main board, but I will take that up with their developers. Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.13-rc6-git10 test report [x86_64]
Just finished building the latest git for my dual-opteron box(ASUS K8N-DL with 6GB Ram). No new issues noted, works about as well as 2.6.12 for me. ASUS still has not addressed their ACPI Table and I am doubtful that they ever will. In order to boot any kernel, I am disabling ACPI in the BIOS. If I enable ACPI, I now get a lock-up referencing the fact the machine has 6GB of RAM and no IOMMU. I have attached the "dmesg" of the boot with ACPI disabled if you folks are interested. Sean P.S. ASUS TechSupport is only slightly better than Belkin(Their KVM's suck) TechSupport! Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet iommu=memaper=3) Linux version 2.6.13-rc6-git10 ([EMAIL PROTECTED]) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Thu Aug 18 13:52:20 PDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009e400 (usable) BIOS-e820: 0009e400 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - c000 (usable) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - 0001 (reserved) BIOS-e820: 0001 - 0001c000 (usable) ACPI: Unable to locate RSDP Scanning NUMA topology in Northbridge 24 Number of nodes 2 Node 0 MemBase Limit 00013fff Node 1 MemBase 00014000 Limit 0001bfff Using 25 for the hash shift. Max adder is 1bfff Using node hash shift of 25 Bootmem setup node 0 -00013fff Bootmem setup node 1 00014000-0001bfff On node 0 totalpages: 1310719 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 1306623 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 On node 1 totalpages: 524287 DMA zone: 0 pages, LIFO batch:1 Normal zone: 524287 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 Nvidia board detected. Ignoring ACPI timer override. Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: OEM0 <6>Product ID: PROD <6>APIC at: 0xFEE0 Processor #0 15:5 APIC version 17 Processor #1 15:5 APIC version 17 I/O APIC #4 Version 17 at 0xFEC0. Setting APIC routing to flat Processors: 2 Allocating PCI resources starting at c000 (gap: c000:2000) Checking aperture... CPU 0: aperture @ 1000 size 32 MB Aperture from northbridge cpu 0 too small (32 MB) Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 256 MB of RAM Mapping aperture over 262144 KB of RAM @ 1000 Built 2 zonelists Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet iommu=memaper=3 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 2010.311 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) Memory: 5908512k/7340032k available (2448k kernel code, 0k reserved, 1303k data, 224k init) Calibrating delay using timer specific routine.. 4024.90 BogoMIPS (lpj=8049811) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 0(1) -> Node 0 -> Core 0 mtrr: v2.0 (20020519) Using IO-APIC 4 ..MP-BIOS bug: 8254 timer not connected to IO-APIC works. Using local APIC timer interrupts. Detected 12.564 MHz APIC timer. Booting processor 1/2 APIC 0x1 Initializing CPU#1 Calibrating delay using timer specific routine.. 4020.89 BogoMIPS (lpj=8041798) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 1(1) -> Node 1 -> Core 0 AMD Opteron(tm) Processor 246 stepping 0a CPU 1: Syncing TSC to CPU 0. CPU 1: synchronized TSC with CPU 0 (last diff -112 cycles, maxerr 788 cycles) Brought up 2 CPUs time.c: Using PIT/TSC based timekeeping. testing NMI watchdog ... OK. checking if image is initramfs... it is NET: Registered protocol family 16 PCI: Using configuration type 1 ACPI: Subsystem revision 20050408 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: Transparent bridge - :00:09.0 Boot video device is :04:00.0 PCI->APIC IRQ transform: :00:01.1[A] -> IRQ 11 PCI->APIC IRQ transform: :00:02.0[A] -> IRQ 9 PCI->APIC IRQ transform: :00:02.1[B] -> IRQ 3 PCI->APIC IRQ transform: :00:04.0[A] -> IRQ 5 PCI->APIC IRQ transform: :00:07.0[A] -> IRQ 5 PCI->APIC IRQ transform: :00:08.0[A] -
Re: Testing RC kernels [KORG]
On Tue, 2005-08-02 at 15:21 -0400, Steven Rostedt wrote: > I've been complaining about this for some time. Kernel.org really needs > to show more information about the rc kernels and how to create them. > We want more testers, but I wonder how many people go through the above > steps and just give up when things don't work. Luckly Sean was nice > enough to email the LKML and ask. > > My main gripe is that there's no link to 2.6.12 which is what most of > the other patches go against. > I would be more than willing to whip up an html how-to(and maintain it). Is there any interest in this? Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Testing RC kernels
On Tue, 2005-08-02 at 14:36 -0400, Lee Revell wrote: > On Tue, 2005-08-02 at 11:33 -0700, Sean Bruno wrote: > > > > > > I have been trying to test the 2.6.13 and can't quite get the patches > > applied cleanly. > > > > What kernel version (full kernel source tar ball) should I be using to > > apply the patches(rc5) with? Is it 2.6.12.3? > > No, 2.6.12. > > Lee > Ah! Thanks. Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Testing RC kernels
I have been trying to test the 2.6.13 and can't quite get the patches applied cleanly. What kernel version (full kernel source tar ball) should I be using to apply the patches(rc5) with? Is it 2.6.12.3? Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[WORKAROUND] For ASUS K8N-DL PCI allocation issues
I have determined that if you disable ACPI altogether in the BIOS I can actually use the on-board hardware. There are still allocation issues, but I can access the USB controller, Sound and Broadcom ethernet adapter at this point. I haven't tested any further and would like some other K8N-DL users to test my findings and make sure that this is the only setting required to make the board functional at this point. With BIOS 1003, enter the BIOS and move to POWER. Set ACPI APIC Support to Disabled and reboot. There is a small chance that you will also have to set the IRQ's of all device manually. Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ASUS K8N-DL Beta BIOS
On Mon, 2005-07-04 at 23:26 +0200, Andi Kleen wrote: > > 2.6.13-rc1 has some kind of issue with my board due to it's 6GB of RAM. > > It stops when it discovers that there is no "IOMMU". Since I don't see > > anything obvious in the BIOS to activate, I can't boot 2.6.13 at all. > > Full boot log please? > Well, that might take me a while. Since the system halts at this point, I will have to whack together a serial cable to redirect the kernel post. Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ASUS K8N-DL Beta BIOS
Even more fun today with the ASUS release 1004 of the BIOS. Looks like you CANNOT disable the Nvidia SATA controller without causing the system to lock. I can't seem to work around this new issue with the system without backing my BIOS down to 1003. With the Nvidia SATA controller enabled, 2.6.12.2 seems to go insane attempting to talk with it(nv_raid seems to have trouble). I am not going to document this issue, as there are so many other issues that are on-going with this board. It's starting to look like this is a large and expensive exchanger of electricity for heat at this point. 2.6.13-rc1 has some kind of issue with my board due to it's 6GB of RAM. It stops when it discovers that there is no "IOMMU". Since I don't see anything obvious in the BIOS to activate, I can't boot 2.6.13 at all. Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ASUS K8N-DL Beta BIOS
On Sun, 2005-07-03 at 09:37 +0200, Alexander Nyberg wrote: > lör 2005-07-02 klockan 21:32 -0700 skrev Sean Bruno: > > On Sat, 2005-07-02 at 21:44 +0200, Andi Kleen wrote: > > > > I can't really remember whether the detection problem was resolved; my > > > > specific (APIC related) issue was. > > > > > > > > Andi? > > > > > > Does it work with acpi_skip_timer_override ? > > > > > > -Andi > > > > Not to be a crank here, but I can't find reference to this > > function/variable/#DEFINE in any of the ACPI code nor can I find a > > decent reference to this in the lkml lists...So I must not understand > > your suggestion. > > > > What are you asking me to check? > > It's a boot command line parameter (Documentation/kernel-parameters.txt) Booted 2.6.12 with acpi_skip_timer_override. Here is the dmesg output for your review. Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb apic=debug acpi=verbose acpi_skip_timer_override) Linux version 2.6.12 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 SMP Sat Jun 18 10:21:14 PDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009e400 (usable) BIOS-e820: 0009e400 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff - bfff3000 (ACPI NVS) BIOS-e820: bfff3000 - c000 (ACPI data) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - 0001 (reserved) BIOS-e820: 0001 - 0001c000 (usable) ACPI: RSDP (v000 Nvidia) @ 0x000f7650 ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff3040 ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x0001 LTP 0x0001) @ 0xbfff9680 ACPI: SRAT (v001 AMDHAMMER 0x0001 AMD 0x0001) @ 0xbfff9880 ACPI: MCFG (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff99c0 ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff9580 ACPI: DSDT (v001 NVIDIA AWRDACPI 0x1000 MSFT 0x010e) @ 0x SRAT: PXM 0 -> APIC 0 -> Node 0 SRAT: PXM 1 -> APIC 1 -> Node 1 SRAT: Node 0 PXM 0 0-9 SRAT: Node 0 PXM 0 0-bfff SRAT: Node 0 PXM 0 0-13fff SRAT: Node 1 PXM 1 14000-1bfff node 1 shift 24 addr 14000 conflict 0 Bootmem setup node 0 -00013fff Bootmem setup node 1 00014000-0001bfff On node 0 totalpages: 1310719 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 1306623 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 On node 1 totalpages: 524287 DMA zone: 0 pages, LIFO batch:1 Normal zone: 524287 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: IOAPIC (id[0x04] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 4, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at c000 (gap: c000:2000) Checking aperture... CPU 0: aperture @ 800 size 32 MB Aperture from northbridge cpu 0 too small (32 MB) No AGP bridge found Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM Mapping aperture over 65536 KB of RAM @ 800 Built 2 zonelists Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb apic=debug acpi=verbose acpi_skip_timer_override Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 3.579545 MHz PM timer. time.c: Detected 2010.339 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) Inode-cache hash table entri
