Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
Am Thursday 21 July 2005 04:08 schrieb Joseph: I have a brand new (conservative box) AMD64 3000, Sata Drive with Asus AV8, I have two problems: 1.) Kernel panic - not syncing: Aiee, killing interupt handler. It appear during every few hours during compiling, I've seen other folks having the same problem but no solution. Sorry, I've seen this thread to late to be just in time. This is just for information. I've installed my box completely new. CFLAGS=-O2 -march=pentium4 -fomit-frame-pointer -pipe Kernel 2.6.12-gentoo-r4 and r6 I got Kernel panic - not syncing: Fatal exception in interrupt by mounting the scsi-cdrom. I took the same configuration like the old system, was 2.6.9-ac9. I've testet 2.6.11-ac7 with the same config, works pretty well. Regards Christian pgpFqCA1w2jcn.pgp Description: PGP signature
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
On Wed, 20 Jul 2005, Joseph wrote: I wasn't thinking about masking KDE but gcc-3.4.1 on AMD64 platform and make stable 3.3 version. I run onto one posting claiming that there is some kind of bug in gcc-3.4.1 (and this version is the only stable version on AMD64. I think that if you use cutting edge hardware you also need to use cutting edge software. For example the newer your kernel, the better support it probably has for your hardware. It is the same with gcc, the newer the version the better your chances that issues with new processors like amd64 are fixed. It's building the code for your processor after all. Consequently, you also need to use the newest software versions as they often have bugs fixed in order to support that new gcc... -- T.G. -- gentoo-user@gentoo.org mailing list
[gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
I have a brand new (conservative box) AMD64 3000, Sata Drive with Asus
AV8,
I have two problems:
1.) Kernel panic - not syncing: Aiee, killing interupt handler.
It appear during every few hours during compiling, I've seen other folks
having the same problem but no solution.
2,) I'm constantly getting the error when I try to emerge kde
kde-base/kdebase-3.4.1-r1 failed
Function kde_compile, line 164,
I've tried re-emerge qt, it did not help
my make.conf:
CFLAGS=-march=k8 -O2
CHOST=x86_64-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2
I've tried new kde-split, same error.
Somebody pointed out that it has something do to with gcc-3.4.3-r1 but
this is the only stable version available on AMD64.
So, I have this new box - good for nothing, well it might run
Windows :-(
#Joseph
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
On Wednesday 20 July 2005 22:08, Joseph wrote:
I have a brand new (conservative box) AMD64 3000, Sata Drive with Asus
AV8,
I have two problems:
1.) Kernel panic - not syncing: Aiee, killing interupt handler.
It appear during every few hours during compiling, I've seen other folks
having the same problem but no solution.
2,) I'm constantly getting the error when I try to emerge kde
kde-base/kdebase-3.4.1-r1 failed
Function kde_compile, line 164,
I've tried re-emerge qt, it did not help
my make.conf:
CFLAGS=-march=k8 -O2
CHOST=x86_64-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2
I've tried new kde-split, same error.
Somebody pointed out that it has something do to with gcc-3.4.3-r1 but
this is the only stable version available on AMD64.
So, I have this new box - good for nothing, well it might run
Windows :-(
#Joseph
So try the unstable gcc :-D
In all seriousness, this seams like an issue destined for a more specific
mailing list; try to contact others who have this issue and you can work it
out together.
It's very puzzling, good luck (hopefully someone on this gentoo list can help
too).
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
On Wed, 2005-07-20 at 22:23 -0400, Patrick Rutkowski wrote:
On Wednesday 20 July 2005 22:08, Joseph wrote:
I have a brand new (conservative box) AMD64 3000, Sata Drive with Asus
AV8,
I have two problems:
1.) Kernel panic - not syncing: Aiee, killing interupt handler.
It appear during every few hours during compiling, I've seen other folks
having the same problem but no solution.
2,) I'm constantly getting the error when I try to emerge kde
kde-base/kdebase-3.4.1-r1 failed
Function kde_compile, line 164,
I've tried re-emerge qt, it did not help
my make.conf:
CFLAGS=-march=k8 -O2
CHOST=x86_64-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2
I've tried new kde-split, same error.
Somebody pointed out that it has something do to with gcc-3.4.3-r1 but
this is the only stable version available on AMD64.
So, I have this new box - good for nothing, well it might run
Windows :-(
#Joseph
So try the unstable gcc :-D
In all seriousness, this seams like an issue destined for a more specific
mailing list; try to contact others who have this issue and you can work it
out together.
It's very puzzling, good luck (hopefully someone on this gentoo list can help
too).
Eventually, I'll try to go back to gcc-3.3-something and maybe I'll be
able to compile KDE.
With kernel panic I just have to live with it, maybe someday they will
solve it.
--
#Joseph
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
Joseph wrote:
I have a brand new (conservative box) AMD64 3000, Sata Drive with Asus
AV8,
I have two problems:
1.) Kernel panic - not syncing: Aiee, killing interupt handler.
It appear during every few hours during compiling, I've seen other folks
having the same problem but no solution.
2,) I'm constantly getting the error when I try to emerge kde
kde-base/kdebase-3.4.1-r1 failed
Function kde_compile, line 164,
I've tried re-emerge qt, it did not help
my make.conf:
CFLAGS=-march=k8 -O2
CHOST=x86_64-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2
I've tried new kde-split, same error.
Somebody pointed out that it has something do to with gcc-3.4.3-r1 but
this is the only stable version available on AMD64.
So, I have this new box - good for nothing, well it might run
Windows :-(
#Joseph
Well, it's got something to do with the kernel ;-). What kernel version is it?
If it's not 2.6.12, I'd try that, first thing.
Zac
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
On Wed, 2005-07-20 at 19:57 -0700, Zac Medico wrote:
Joseph wrote:
I have a brand new (conservative box) AMD64 3000, Sata Drive with Asus
AV8,
I have two problems:
1.) Kernel panic - not syncing: Aiee, killing interupt handler.
It appear during every few hours during compiling, I've seen other folks
having the same problem but no solution.
2,) I'm constantly getting the error when I try to emerge kde
kde-base/kdebase-3.4.1-r1 failed
Function kde_compile, line 164,
I've tried re-emerge qt, it did not help
my make.conf:
CFLAGS=-march=k8 -O2
CHOST=x86_64-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2
I've tried new kde-split, same error.
Somebody pointed out that it has something do to with gcc-3.4.3-r1 but
this is the only stable version available on AMD64.
So, I have this new box - good for nothing, well it might run
Windows :-(
#Joseph
Well, it's got something to do with the kernel ;-). What kernel version is
it? If it's not 2.6.12, I'd try that, first thing.
Zac
I'm on gentoo-sources 2.6.12-gentoo-r6 it makes no difference.
So I either get a kernel panic or kdebase-3.4.1-r1 fails.
I think kdebase-3.4.1 should be masked as unstable.
I was googling and noticed that a lot of people have similar problem,
but no solution.
--
#Joseph
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
Joseph wrote:
On Wed, 2005-07-20 at 19:57 -0700, Zac Medico wrote:
Joseph wrote:
I have a brand new (conservative box) AMD64 3000, Sata Drive with Asus
AV8,
I have two problems:
1.) Kernel panic - not syncing: Aiee, killing interupt handler.
It appear during every few hours during compiling, I've seen other folks
having the same problem but no solution.
2,) I'm constantly getting the error when I try to emerge kde
kde-base/kdebase-3.4.1-r1 failed
Function kde_compile, line 164,
I've tried re-emerge qt, it did not help
my make.conf:
CFLAGS=-march=k8 -O2
CHOST=x86_64-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2
I've tried new kde-split, same error.
Somebody pointed out that it has something do to with gcc-3.4.3-r1 but
this is the only stable version available on AMD64.
So, I have this new box - good for nothing, well it might run
Windows :-(
#Joseph
Well, it's got something to do with the kernel ;-). What kernel version is it?
If it's not 2.6.12, I'd try that, first thing.
Zac
I'm on gentoo-sources 2.6.12-gentoo-r6 it makes no difference.
So I either get a kernel panic or kdebase-3.4.1-r1 fails.
I think kdebase-3.4.1 should be masked as unstable.
I was googling and noticed that a lot of people have similar problem,
but no solution.
Mask kde because building it triggers a kernel bug? I think not. It's
probably related to your hardware and/or kernel config. Is it happening with
split ebuilds too? Is there anything interesting in the output of dmesg or
/var/log/messages leading up to this?
Zac
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
[snip] I'm on gentoo-sources 2.6.12-gentoo-r6 it makes no difference. So I either get a kernel panic or kdebase-3.4.1-r1 fails. I think kdebase-3.4.1 should be masked as unstable. I was googling and noticed that a lot of people have similar problem, but no solution. Mask kde because building it triggers a kernel bug? I think not. It's probably related to your hardware and/or kernel config. Is it happening with split ebuilds too? Is there anything interesting in the output of dmesg or /var/log/messages leading up to this? Zac I wasn't thinking about masking KDE but gcc-3.4.1 on AMD64 platform and make stable 3.3 version. I run onto one posting claiming that there is some kind of bug in gcc-3.4.1 (and this version is the only stable version on AMD64. If I knew I'm going to have so much problem with AMD64, I would have gone with x86. So WARNING to everybody: A8V + Sata Drive + AMD64 3000 = DISASTER (for now). I have two other boxes running Gentoo on x86 and they are rock solid. If any kind of problem pops-up I can solve it withing an hour or faster. But these two problem on AMD64 turned this machine to a piece of junk (suitable only for Windows). Split KDE-ebuild is effected as well. I couldn't find anything in dmesg, what might be causing it. If it was a kernel configuration I would imaging somebody would discover it, but there are only suggestion that don't work. It most likely some bug in some kind of kernel driver pertaining to Sata Drive or AMD64 -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
Joseph wrote: [snip] I'm on gentoo-sources 2.6.12-gentoo-r6 it makes no difference. So I either get a kernel panic or kdebase-3.4.1-r1 fails. I think kdebase-3.4.1 should be masked as unstable. I was googling and noticed that a lot of people have similar problem, but no solution. Mask kde because building it triggers a kernel bug? I think not. It's probably related to your hardware and/or kernel config. Is it happening with split ebuilds too? Is there anything interesting in the output of dmesg or /var/log/messages leading up to this? Zac I wasn't thinking about masking KDE but gcc-3.4.1 on AMD64 platform and make stable 3.3 version. I run onto one posting claiming that there is some kind of bug in gcc-3.4.1 (and this version is the only stable version on AMD64. If I knew I'm going to have so much problem with AMD64, I would have gone with x86. So WARNING to everybody: A8V + Sata Drive + AMD64 3000 = DISASTER (for now). I have two other boxes running Gentoo on x86 and they are rock solid. If any kind of problem pops-up I can solve it withing an hour or faster. But these two problem on AMD64 turned this machine to a piece of junk (suitable only for Windows). Split KDE-ebuild is effected as well. I couldn't find anything in dmesg, what might be causing it. If it was a kernel configuration I would imaging somebody would discover it, but there are only suggestion that don't work. It most likely some bug in some kind of kernel driver pertaining to Sata Drive or AMD64 Maybe you should try gcc-3.4.4? You could go with a 32-bit userland until the problem is resolved. You can do that with a 64-bit kernel if you have IA32 emulation enabled (hopefully you won't encounter the same bug). Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
[snip] I wasn't thinking about masking KDE but gcc-3.4.1 on AMD64 platform and make stable 3.3 version. I run onto one posting claiming that there is some kind of bug in gcc-3.4.1 (and this version is the only stable version on AMD64. If I knew I'm going to have so much problem with AMD64, I would have gone with x86. So WARNING to everybody: A8V + Sata Drive + AMD64 3000 = DISASTER (for now). I have two other boxes running Gentoo on x86 and they are rock solid. If any kind of problem pops-up I can solve it withing an hour or faster. But these two problem on AMD64 turned this machine to a piece of junk (suitable only for Windows). Split KDE-ebuild is effected as well. I couldn't find anything in dmesg, what might be causing it. If it was a kernel configuration I would imaging somebody would discover it, but there are only suggestion that don't work. It most likely some bug in some kind of kernel driver pertaining to Sata Drive or AMD64 Maybe you should try gcc-3.4.4? You could go with a 32-bit userland until the problem is resolved. You can do that with a 64-bit kernel if you have IA32 emulation enabled (hopefully you won't encounter the same bug). Zac Thank you, that is a good suggestion. I'll be running memtest86 all night, just to be sure. And tomorrow I'll try gcc-3.4.4 it this will not help I'll try IA32 emulation. Though, I'll have to find some more info in this, how to do it. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 1.) Kernel panic - not syncing: Aiee, killing interupt handler; 2.) kdebase-3.4.1-r1 failed
Joseph wrote: [snip] I wasn't thinking about masking KDE but gcc-3.4.1 on AMD64 platform and make stable 3.3 version. I run onto one posting claiming that there is some kind of bug in gcc-3.4.1 (and this version is the only stable version on AMD64. If I knew I'm going to have so much problem with AMD64, I would have gone with x86. So WARNING to everybody: A8V + Sata Drive + AMD64 3000 = DISASTER (for now). I have two other boxes running Gentoo on x86 and they are rock solid. If any kind of problem pops-up I can solve it withing an hour or faster. But these two problem on AMD64 turned this machine to a piece of junk (suitable only for Windows). Split KDE-ebuild is effected as well. I couldn't find anything in dmesg, what might be causing it. If it was a kernel configuration I would imaging somebody would discover it, but there are only suggestion that don't work. It most likely some bug in some kind of kernel driver pertaining to Sata Drive or AMD64 Maybe you should try gcc-3.4.4? You could go with a 32-bit userland until the problem is resolved. You can do that with a 64-bit kernel if you have IA32 emulation enabled (hopefully you won't encounter the same bug). Zac Thank you, that is a good suggestion. I'll be running memtest86 all night, just to be sure. And tomorrow I'll try gcc-3.4.4 it this will not help I'll try IA32 emulation. Though, I'll have to find some more info in this, how to do it. It's easy, just enable it in your kernel config. You can use 32-bit module-init-tools to modprobe 64-bit modules. You need a 64-bit environment to build 64-bit stuff but you can chroot into a stage3 for that. Read the amd64 technotes part about 32-bit compatibility: http://www.gentoo.org/proj/en/base/amd64/technotes/index.xml?part=1chap=4 BTW, gcc-3.4.1 is no longer stable on amd64 but gcc-3.4.3-r1 is: http://packages.gentoo.org/packages/?category=sys-devel;name=gcc Zac -- gentoo-user@gentoo.org mailing list
