FC2 Upgrade from FC1 - newbie needs help with 'kernel, panic' further info

[Steve]

Thanks Marc

not sure what you mean by the BIOS safe settings.

I did try the kernel params : 
acpi=off 
acpi=ht 
pci=noacpi 
 
but still the same Kernel panic. 
 
However, 
my actual trace info is different to the one listed at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124329
: 
 
Process swapper (pid: 1, threadinfo=f7d90000 task=f7d49630) 
Stack: 0000002b 00000000 c015a352 c02d4c80 00000000 0000002b c1997f84 
c02d4c80 
       c17fd9e0 c014f6d4 0000002b c016e2dc fffffff4 c199aa18 0000002c 
c199a980 
       c1997f84 c199b580 c1997fb0 00000000 c016e31d c199b580 c199b580 
c1997f91 
Call Trace: 
 [<c015a352>] simple_prepare_write+0x31/0x94 
 [<c014f6d4>] init_symlink+0x4e/0x10e 
 [<c016e2dc>] init_symlink+0x0/0xd 
 [<c016e31d>] sysfs_symlink+0x34/0x49 
 [<c016e49a>] sysfs_create_link+0xed/0x117 
 [<c01dbbc7>] bus_match+0x3f/0x45 
 [<c01dcc7b>] driver_attach+0x37/0x6a 
 [<c01dce8d>] bus_add_driver+0x6a/0x81 
 [<c01dd173>] driver_register+0x28/0x2c 
 [<c0199051>] pci_create_newid_file+0x15/0x1a 
 [<c0199315>] pci_register_driver+0x4b/0x67 
 [<c032f0fb>] agp_intel_init+0x20/0x27 
 [<c0320659>] do_initcalls+0x49/0x97 
 [<c010029e>] init+0x0/0xe2 
 [<c01002bb>] init+0x1d/0xe2 
 [<c01041d5>] kernel_thread_helper+0x5/0xb 
 
Code: 0f 0b 2a 00 78 90 29 c0 2b 0d cc 90 37 c0 c1 f9 05 c1 e1 0c 
 <0>Kernel panic: Attempted to kill init!

After some searching
>
> this is the same issue as reported at 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124329
>
> Steps to Reproduce:
> 1.  Turn on machine
> 2.  Insert FC2 disc 1
> 3.  Select graphic or text install
>   
> Actual Results:  Kernel panic.
>
> Expected Results:  Installation to proceed normally.
>
> Additional info:
>
> EIP is at acpi_ps_parse_aml+0xb2/0x1a4
> eax: 00000000  ebx: c147cc00  ecx: c02b38c9  edx: 00000d60
> esi: c147cc00  edi: c147bf44  ebp: 00000007  esp: dffd5f60
> ds: 007b  es: 007b  ss: 0068
> Process swapper (pid: 1, threadinfo=dffd5000 task=dfd47630)
> Stack: 00000000 00000000 c147cc00 dffe0284 00000001 c01aa473 dffe0144
> dffe0144
>       c037e634 00000000 c01aa492 dffe0144 c01a84bd dffe0144 00000000
> 00000000
>       c01a852e 00000000 00000000 00000000 c01a85e2 c01ae62d 00000001
> 000fc0d0
> Call Trace:
> [<c01aa473>] acpi_ns_one_complete_parse+0x6b/0x7b
> [<c01aa492>] acpi_ns_parse_table+0xf/0x29
> [<c01a84bd>] acpi_ns_load_table+0x6d/0x8f
> [<c01a852e>] acpi_ns_load_table_by_type+0x4f/0xea
> [<c01a85e2>] acpi_ns_load_namespace+0x19/0x34
> [<c01ae62d>] acpi_load_tables+0xd9/0x139
> [<c032ccc5>] acpi_bus_init+0x26/0x11b
> [<c032ce1c>] acpi_init+0x62/0xb4
> [<c0320659>] do_initcalls+0x49/0x97
> [<c010029e>] init+0x0/0xe2
> [<c01002bb>] init+0x1d/0xe2
> [<c01041d5>] kernel_thread_helper+0x5/0xb
>
> Code: 82 78 10 00 75 0e 80 48 09 08 8b 83 ac 01 00 00 c6 40 1c 01
> <0>Kernel panic: Attempted to kill init!
>
> -- I don't see any resolution yet, just the bug report.
>
> Steve
>

Steve - I don't think anyone has given you the most obvious answer yet:  
have you set your bios to default "safe" settings?  It seems to be an 
acpi problem - maybe a bios update or switch as much of the acpi stuff 
off as possible?

Hope this helps.

Marc