Red Hat Bugzilla – Bug 119547
Installing will hang the machine/Kernel panic: Fatal exception in interrupt
Last modified: 2007-11-30 17:10:39 EST
Description of problem:
Installing Fedora Core 2 Test 2 on my PC will freeze my PC when trying
to create a filesystem.
Version-Release number of selected component (if applicable):
(see attached files)
Everytime I install the system the installer will hang when starting
to install the selected components.
When I select 'format disk' it will hang when starting to create the
When I don't select 'format disk' it starts to install the packages.
After some packages the system freezes.
When I boot from CD/DVD and go into rescue mode (or use the normal
installer and go to another console) and try to 'mkefs' a partition
the system will hang with something like:
Stack: c24d9bfc 00000000 ....
Code: 0f ...
<0> Kernel panic: Fatal exception in interrupt
In interrupt handler - not syning
(If you really need the whole text, drop me a line and I will type in
that whole page!)
The system runs without any real problem with WindowsXP, Mandrake 10
and RedHat 9!
Created attachment 98993 [details]
Output of the cmd lspci -vvv
Created attachment 98994 [details]
/proc/modules, /proc/scsi/scsi, /proc/cpuinfo
yes, the whole panic text is needed.
(we don't need the hex numbers tho, only the names)
Created attachment 99030 [details]
kernel BUG at mm/slab.c:1808! Process mke2fs
Created attachment 99031 [details]
kernel BUG at mm/slab.c:1808! Process pdflush
Created attachment 99032 [details]
kernel BUG at mm/slab.c:1808! Process anaconda
Created attachment 99033 [details]
kernel BUG at mm/slab.c:2013! Process kswapd0
I hope that this weren't too much files!
This panic is a little different from the others...
how much memory do you have?
does this go away if you pass "mem=xxxM" on the kernel commandline
(that very first prompt in the installer) (where xxx is the amount of
memory you have in megabytes minus 32)
The machine has 2GB memory.
The mem-trick doesn't (also with mem=800) help. The same problem as
But this time I was able to say dmesg (see attachment 'dmesg.txt')
after the installer freezes (thanks to the guys who made that serial
console stuff) and this notes a 'DMA timeout', which I can't believe,
because this happens on a second machine we have, too!
Maybe it's a problem of the S-ATA stuff inside the kernel?
Created attachment 99034 [details]
Attachment for text above. (I will never learn bugzilla.)
I did some tests and now I think it's the kernel.
I installed Fedora Core 1 on the PC. The PC is stable with this.
Then I installed kernel-2.6.3-18.104.22.168.1.i686.rpm from 'Core 2 Test
2' on the machine and the problem described above starts to happen again!
Then I installed kernel-2.6.4-1.303.i686.rpm (plus glibc-2.3.3-20 and
friends) from the development directory and the machine seems to be
stable now. (OK there are some warning about USB and other stuff, but
this seems to be because the rest of the system is for kernel 2.4....)
So if anyone promises me that the final Fedore Core 2 will contain at
least that kernel-2.6.4-1.303.i686.rpm I would state this problem as
P.S.: Yes, that is also true for the SMP-version!
I installed FC2 test3 (which uses kernel 2.6.5) and the problem is fixed!