Re: 2.6.20.6 vanilla does't boot
On Wed, Apr 18, 2007 at 03:39:25PM -0400, Len Brown wrote: > On Sunday 15 April 2007 11:50, Michal Jaegermann wrote: > > > > A kernel derived from 2.6.21-rc6-git1 (2.6.20-1.3053.fc7.x86_64 from > > Fedora "rawhide" to be more precise) did boot on the hardware in > > question, though; but only when I gave it 'acpi=off'. Without that > > parameter it was getting stuck apparently when starting hotplug. > > In that kernel case disks were accessed using pata_atiixp driver. > > If "acpi=off" is necessary to boot the latest kernel, please > report an ACPI bug: > http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI I now travel and what I can do at this moment is somewhat limited. In particular I cannot gain an access to the hardware in question. But please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232490 and the most recent comments there in particular. > Please mention in the bug report what the latest working kernel was. This is mentioned in the referenced report as well. Michal - 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: 2.6.20.6 vanilla does't boot
On Sunday 15 April 2007 11:50, Michal Jaegermann wrote: > On Fri, Apr 13, 2007 at 03:38:18PM +0400, Denis Kirjanov wrote: > > I updated the BIOS to the latest version, but the problem persists. > > Boots option pci = noacpi not solved the problem. Reporting bios bug > > disappears when setting pci = nommconf, But the kernel is still not > > loaded ( The 2.6.15 dmesg do not give any clues to why 2.6.20.6 would not boot. Can you boot 2.6.20.6 with "debug" and capture the serial console log, or take a photo of what is on the screen when the boot hangs? Did anything between 2.6.15 and 2.6.20.6 work properly? Can you bisect where the failure started? > On x86_64 hardware using ata_piix I was unable to boot kernels > based on the current 2.6.20.x either. Regardless of extra kernel > parameters used I was getting consistently 'hdc: lost interrupt', > and/or similar and after something like that the whole machine > was dead. The only differences were if I could still reboot > from a keyboard or if I really have to pull a plug. > > A kernel derived from 2.6.21-rc6-git1 (2.6.20-1.3053.fc7.x86_64 from > Fedora "rawhide" to be more precise) did boot on the hardware in > question, though; but only when I gave it 'acpi=off'. Without that > parameter it was getting stuck apparently when starting hotplug. > In that kernel case disks were accessed using pata_atiixp driver. If "acpi=off" is necessary to boot the latest kernel, please report an ACPI bug: http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI Please mention in the bug report what the latest working kernel was. thanks, -Len - 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: 2.6.20.6 vanilla does't boot
On Friday 13 April 2007 02:35, Marat Buharov wrote: > > [17179569.184000] >>> ERROR: Invalid checksum > Seems like you have buggie bios. As the workaround try to start your > kernel with noacpi parameter. > Solution: Upgrade the BIOS firmware with the latest version available from the > manufacturer. ACPI: OEMB (v001 A M I AMI_OEM 0x05000504 MSFT 0x0097) @ 0x7ffae040 >>> ERROR: Invalid checksum ACPI: MCFG (v001 A M I OEMMCFG 0x05000504 MSFT 0x0097) @ 0x7ffa8810 The Invald checksum message refers to the table header that was just printed. In this case the OEMB table, which Linux doesn't use. -Len - 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: 2.6.20.6 vanilla does't boot
On Friday 13 April 2007 02:35, Marat Buharov wrote: [17179569.184000]ERROR: Invalid checksum Seems like you have buggie bios. As the workaround try to start your kernel with noacpi parameter. Solution: Upgrade the BIOS firmware with the latest version available from the manufacturer. ACPI: OEMB (v001 A M I AMI_OEM 0x05000504 MSFT 0x0097) @ 0x7ffae040 ERROR: Invalid checksum ACPI: MCFG (v001 A M I OEMMCFG 0x05000504 MSFT 0x0097) @ 0x7ffa8810 The Invald checksum message refers to the table header that was just printed. In this case the OEMB table, which Linux doesn't use. -Len - 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: 2.6.20.6 vanilla does't boot
On Sunday 15 April 2007 11:50, Michal Jaegermann wrote: On Fri, Apr 13, 2007 at 03:38:18PM +0400, Denis Kirjanov wrote: I updated the BIOS to the latest version, but the problem persists. Boots option pci = noacpi not solved the problem. Reporting bios bug disappears when setting pci = nommconf, But the kernel is still not loaded ( The 2.6.15 dmesg do not give any clues to why 2.6.20.6 would not boot. Can you boot 2.6.20.6 with debug and capture the serial console log, or take a photo of what is on the screen when the boot hangs? Did anything between 2.6.15 and 2.6.20.6 work properly? Can you bisect where the failure started? On x86_64 hardware using ata_piix I was unable to boot kernels based on the current 2.6.20.x either. Regardless of extra kernel parameters used I was getting consistently 'hdc: lost interrupt', and/or similar and after something like that the whole machine was dead. The only differences were if I could still reboot from a keyboard or if I really have to pull a plug. A kernel derived from 2.6.21-rc6-git1 (2.6.20-1.3053.fc7.x86_64 from Fedora rawhide to be more precise) did boot on the hardware in question, though; but only when I gave it 'acpi=off'. Without that parameter it was getting stuck apparently when starting hotplug. In that kernel case disks were accessed using pata_atiixp driver. If acpi=off is necessary to boot the latest kernel, please report an ACPI bug: http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI Please mention in the bug report what the latest working kernel was. thanks, -Len - 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: 2.6.20.6 vanilla does't boot
On Wed, Apr 18, 2007 at 03:39:25PM -0400, Len Brown wrote: On Sunday 15 April 2007 11:50, Michal Jaegermann wrote: A kernel derived from 2.6.21-rc6-git1 (2.6.20-1.3053.fc7.x86_64 from Fedora rawhide to be more precise) did boot on the hardware in question, though; but only when I gave it 'acpi=off'. Without that parameter it was getting stuck apparently when starting hotplug. In that kernel case disks were accessed using pata_atiixp driver. If acpi=off is necessary to boot the latest kernel, please report an ACPI bug: http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI I now travel and what I can do at this moment is somewhat limited. In particular I cannot gain an access to the hardware in question. But please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232490 and the most recent comments there in particular. Please mention in the bug report what the latest working kernel was. This is mentioned in the referenced report as well. Michal - 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: 2.6.20.6 vanilla does't boot
On Fri, Apr 13, 2007 at 03:38:18PM +0400, Denis Kirjanov wrote: > I updated the BIOS to the latest version, but the problem persists. > Boots option pci = noacpi not solved the problem. Reporting bios bug > disappears when setting pci = nommconf, But the kernel is still not > loaded ( On x86_64 hardware using ata_piix I was unable to boot kernels based on the current 2.6.20.x either. Regardless of extra kernel parameters used I was getting consistently 'hdc: lost interrupt', and/or similar and after something like that the whole machine was dead. The only differences were if I could still reboot from a keyboard or if I really have to pull a plug. A kernel derived from 2.6.21-rc6-git1 (2.6.20-1.3053.fc7.x86_64 from Fedora "rawhide" to be more precise) did boot on the hardware in question, though; but only when I gave it 'acpi=off'. Without that parameter it was getting stuck apparently when starting hotplug. In that kernel case disks were accessed using pata_atiixp driver. Michal - 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: 2.6.20.6 vanilla does't boot
On Fri, Apr 13, 2007 at 03:38:18PM +0400, Denis Kirjanov wrote: I updated the BIOS to the latest version, but the problem persists. Boots option pci = noacpi not solved the problem. Reporting bios bug disappears when setting pci = nommconf, But the kernel is still not loaded ( On x86_64 hardware using ata_piix I was unable to boot kernels based on the current 2.6.20.x either. Regardless of extra kernel parameters used I was getting consistently 'hdc: lost interrupt', and/or similar and after something like that the whole machine was dead. The only differences were if I could still reboot from a keyboard or if I really have to pull a plug. A kernel derived from 2.6.21-rc6-git1 (2.6.20-1.3053.fc7.x86_64 from Fedora rawhide to be more precise) did boot on the hardware in question, though; but only when I gave it 'acpi=off'. Without that parameter it was getting stuck apparently when starting hotplug. In that kernel case disks were accessed using pata_atiixp driver. Michal - 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: 2.6.20.6 vanilla does't boot
I updated the BIOS to the latest version, but the problem persists. Boots option pci = noacpi not solved the problem. Reporting bios bug disappears when setting pci = nommconf, But the kernel is still not loaded ( - 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: 2.6.20.6 vanilla does't boot
[17179569.184000] >>> ERROR: Invalid checksum Seems like you have buggie bios. As the workaround try to start your kernel with noacpi parameter. Solution: Upgrade the BIOS firmware with the latest version available from the manufacturer. - 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: 2.6.20.6 vanilla does't boot
[17179569.184000]ERROR: Invalid checksum Seems like you have buggie bios. As the workaround try to start your kernel with noacpi parameter. Solution: Upgrade the BIOS firmware with the latest version available from the manufacturer. - 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: 2.6.20.6 vanilla does't boot
I updated the BIOS to the latest version, but the problem persists. Boots option pci = noacpi not solved the problem. Reporting bios bug disappears when setting pci = nommconf, But the kernel is still not loaded ( - 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: 2.6.20.6 vanilla does't boot
I showed demsg output at the current running kernel. When booting kernel 2.6.20.6 I see only lines I have described above -- Regards, Denis - 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.20.6 vanilla does't boot
Hi all! I installed a new kernel 2.6.20.6 and it is unable to boot. During loading, I get some messages from the kernel, similar to the following PCI: BIOS Bug: MCFG area at x is not E820-reserved PCI: Not using MMCONFIG udevplug: make_queue: unable to create /dev/.udev/queue: No such file or directory udevplug: make_queue: unable to create /dev/.udev/queue: File exists sda: assuming drive cache: write through Then loading stops and after about 2 minutes boots BusyBox. Kernel version 2.6.18.8 and 2.6.16.44-rc2 loaded properly. the output of dmesg: [17179569.184000] Linux version 2.6.15-26-686 ([EMAIL PROTECTED]) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Fri Sep 8 20:16:40 UTC 2006 [17179569.184000] BIOS-provided physical RAM map: [17179569.184000] BIOS-e820: - 0009fc00 (usable) [17179569.184000] BIOS-e820: 0009fc00 - 000a (reserved) [17179569.184000] BIOS-e820: 000e4000 - 0010 (reserved) [17179569.184000] BIOS-e820: 0010 - 7ffa (usable) [17179569.184000] BIOS-e820: 7ffa - 7ffae000 (ACPI data) [17179569.184000] BIOS-e820: 7ffae000 - 7ffe (ACPI NVS) [17179569.184000] BIOS-e820: 7ffe - 8000 (reserved) [17179569.184000] BIOS-e820: ffb0 - 0001 (reserved) [17179569.184000] 1151MB HIGHMEM available. [17179569.184000] 896MB LOWMEM available. [17179569.184000] found SMP MP-table at 000ff780 [17179569.184000] On node 0 totalpages: 524192 [17179569.184000] DMA zone: 4096 pages, LIFO batch:0 [17179569.184000] DMA32 zone: 0 pages, LIFO batch:0 [17179569.184000] Normal zone: 225280 pages, LIFO batch:31 [17179569.184000] HighMem zone: 294816 pages, LIFO batch:31 [17179569.184000] DMI 2.3 present. [17179569.184000] ACPI: RSDP (v000 ACPIAM ) @ 0x000fad00 [17179569.184000] ACPI: RSDT (v001 A M I OEMRSDT 0x05000504 MSFT 0x0097) @ 0x7ffa [17179569.184000] ACPI: FADT (v001 A M I OEMFACP 0x05000504 MSFT 0x0097) @ 0x7ffa0200 [17179569.184000] ACPI: MADT (v001 A M I OEMAPIC 0x05000504 MSFT 0x0097) @ 0x7ffa0390 [17179569.184000] ACPI: OEMB (v001 A M I AMI_OEM 0x05000504 MSFT 0x0097) @ 0x7ffae040 [17179569.184000] >>> ERROR: Invalid checksum [17179569.184000] ACPI: MCFG (v001 A M I OEMMCFG 0x05000504 MSFT 0x0097) @ 0x7ffa8810 [17179569.184000] ACPI: DSDT (v001 A0229 A0229000 0x INTL 0x02002026) @ 0x [17179569.184000] ACPI: PM-Timer IO Port: 0x808 [17179569.184000] ACPI: Local APIC address 0xfee0 [17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [17179569.184000] Processor #0 15:4 APIC version 20 [17179569.184000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [17179569.184000] Processor #1 15:4 APIC version 20 [17179569.184000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [17179569.184000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [17179569.184000] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [17179569.184000] IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [17179569.184000] ACPI: IRQ0 used by override. [17179569.184000] ACPI: IRQ2 used by override. [17179569.184000] ACPI: IRQ9 used by override. [17179569.184000] Enabling APIC mode: Flat. Using 1 I/O APICs [17179569.184000] Using ACPI (MADT) for SMP configuration information [17179569.184000] Allocating PCI resources starting at 8800 (gap: 8000:7fb0) [17179569.184000] Built 1 zonelists [17179569.184000] Kernel command line: root=/dev/sda2 ro quiet vga=795 [17179569.184000] mapped APIC to d000 (fee0) [17179569.184000] mapped IOAPIC to c000 (fec0) [17179569.184000] Initializing CPU#0 [17179569.184000] PID hash table entries: 4096 (order: 12, 65536 bytes) [17179569.184000] Detected 3011.186 MHz processor. [17179569.184000] Using pmtmr for high-res timesource [17179569.184000] Console: colour dummy device 80x25 [17179572.764000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [17179572.764000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [17179572.868000] Memory: 2065764k/2096768k available (2115k kernel code, 29864k reserved, 595k data, 332k init, 1179264k highmem) [17179572.868000] Checking if this processor honours the WP bit even in supervisor mode... Ok. [17179572.948000] Calibrating delay using timer specific routine.. 6029.29 BogoMIPS (lpj=12058592) [17179572.948000] Security Framework v1.0.0 initialized [17179572.948000] SELinux: Disabled at boot. [17179572.948000] Mount-cache hash table entries: 512 [17179572.948000] CPU: After generic identify, caps: bfebfbff 2000
2.6.20.6 vanilla does't boot
Hi all! I installed a new kernel 2.6.20.6 and it is unable to boot. During loading, I get some messages from the kernel, similar to the following PCI: BIOS Bug: MCFG area at x is not E820-reserved PCI: Not using MMCONFIG udevplug: make_queue: unable to create /dev/.udev/queue: No such file or directory udevplug: make_queue: unable to create /dev/.udev/queue: File exists sda: assuming drive cache: write through Then loading stops and after about 2 minutes boots BusyBox. Kernel version 2.6.18.8 and 2.6.16.44-rc2 loaded properly. the output of dmesg: [17179569.184000] Linux version 2.6.15-26-686 ([EMAIL PROTECTED]) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Fri Sep 8 20:16:40 UTC 2006 [17179569.184000] BIOS-provided physical RAM map: [17179569.184000] BIOS-e820: - 0009fc00 (usable) [17179569.184000] BIOS-e820: 0009fc00 - 000a (reserved) [17179569.184000] BIOS-e820: 000e4000 - 0010 (reserved) [17179569.184000] BIOS-e820: 0010 - 7ffa (usable) [17179569.184000] BIOS-e820: 7ffa - 7ffae000 (ACPI data) [17179569.184000] BIOS-e820: 7ffae000 - 7ffe (ACPI NVS) [17179569.184000] BIOS-e820: 7ffe - 8000 (reserved) [17179569.184000] BIOS-e820: ffb0 - 0001 (reserved) [17179569.184000] 1151MB HIGHMEM available. [17179569.184000] 896MB LOWMEM available. [17179569.184000] found SMP MP-table at 000ff780 [17179569.184000] On node 0 totalpages: 524192 [17179569.184000] DMA zone: 4096 pages, LIFO batch:0 [17179569.184000] DMA32 zone: 0 pages, LIFO batch:0 [17179569.184000] Normal zone: 225280 pages, LIFO batch:31 [17179569.184000] HighMem zone: 294816 pages, LIFO batch:31 [17179569.184000] DMI 2.3 present. [17179569.184000] ACPI: RSDP (v000 ACPIAM ) @ 0x000fad00 [17179569.184000] ACPI: RSDT (v001 A M I OEMRSDT 0x05000504 MSFT 0x0097) @ 0x7ffa [17179569.184000] ACPI: FADT (v001 A M I OEMFACP 0x05000504 MSFT 0x0097) @ 0x7ffa0200 [17179569.184000] ACPI: MADT (v001 A M I OEMAPIC 0x05000504 MSFT 0x0097) @ 0x7ffa0390 [17179569.184000] ACPI: OEMB (v001 A M I AMI_OEM 0x05000504 MSFT 0x0097) @ 0x7ffae040 [17179569.184000]ERROR: Invalid checksum [17179569.184000] ACPI: MCFG (v001 A M I OEMMCFG 0x05000504 MSFT 0x0097) @ 0x7ffa8810 [17179569.184000] ACPI: DSDT (v001 A0229 A0229000 0x INTL 0x02002026) @ 0x [17179569.184000] ACPI: PM-Timer IO Port: 0x808 [17179569.184000] ACPI: Local APIC address 0xfee0 [17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [17179569.184000] Processor #0 15:4 APIC version 20 [17179569.184000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [17179569.184000] Processor #1 15:4 APIC version 20 [17179569.184000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [17179569.184000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [17179569.184000] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [17179569.184000] IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [17179569.184000] ACPI: IRQ0 used by override. [17179569.184000] ACPI: IRQ2 used by override. [17179569.184000] ACPI: IRQ9 used by override. [17179569.184000] Enabling APIC mode: Flat. Using 1 I/O APICs [17179569.184000] Using ACPI (MADT) for SMP configuration information [17179569.184000] Allocating PCI resources starting at 8800 (gap: 8000:7fb0) [17179569.184000] Built 1 zonelists [17179569.184000] Kernel command line: root=/dev/sda2 ro quiet vga=795 [17179569.184000] mapped APIC to d000 (fee0) [17179569.184000] mapped IOAPIC to c000 (fec0) [17179569.184000] Initializing CPU#0 [17179569.184000] PID hash table entries: 4096 (order: 12, 65536 bytes) [17179569.184000] Detected 3011.186 MHz processor. [17179569.184000] Using pmtmr for high-res timesource [17179569.184000] Console: colour dummy device 80x25 [17179572.764000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [17179572.764000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [17179572.868000] Memory: 2065764k/2096768k available (2115k kernel code, 29864k reserved, 595k data, 332k init, 1179264k highmem) [17179572.868000] Checking if this processor honours the WP bit even in supervisor mode... Ok. [17179572.948000] Calibrating delay using timer specific routine.. 6029.29 BogoMIPS (lpj=12058592) [17179572.948000] Security Framework v1.0.0 initialized [17179572.948000] SELinux: Disabled at boot. [17179572.948000] Mount-cache hash table entries: 512 [17179572.948000] CPU: After generic identify, caps: bfebfbff 2000
Re: 2.6.20.6 vanilla does't boot
I showed demsg output at the current running kernel. When booting kernel 2.6.20.6 I see only lines I have described above -- Regards, Denis - 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/
