Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Fri, 2005-07-22 at 09:27 -0700, Zac Medico wrote: > Joseph wrote: > >>>Finally I was able to emerge KDE, it really took a lot of time. > >>>Though, looking at the motherboard's ASUS A8V IRQ setting: > >>>They put a lot of devices on IRQ5: > >>> > >>>skge - network controller > >>>libata - I think this is sata ATA controller > >>>ethci_Hcd:usb2, usb2 > >>>VIA8237 - sound ship > >>> > >>>No wonder I'm having problem (and some others) with Sata Drive, if it is > >>>sharing an IRQ with so many devices. In comparison IDE controller have > >>>all their own IRQ's Primary IRQ 14 and Secondary IRQ 15 > >>> > >> > >>Great! So, did you physically remove the sata drive? The sata drivers are > >>still enabled though? The ouput from dmesg should give you an idea what > >>drivers the kernel is actively using. > >> > >>Zac > > > > > > No, I still have the same Sata Drive is just I'm playing with IRQ > > assignment and configuration. > > I've changed to BIOS PnP to YES, so my skge (network controller) and > > libata (Sata Controller are shifted to IRQ 10 > > > > But it makes me wonder both controllers on the Motherboard are different > > chips, so why do they share IRQ? Is there a way to shift them to a > > different IRQ since Linux control IRQ assignment now? > > > > A quick look through linux/Documentation/kernel-parameters.txt shows > that many drivers support direct irq assignment. Also, > linux/Documentation/pnp.txt may be of use. > > Considering the positive results that you've gotten so far, it seems > like you may be on the right track here. It makes me less concerned > about any possible overheating, but if you wanted to be paranoid about > it, you could get another heat probe to double check the readings from > the first one ;-). > > Zac Yes, it looks like a gold mind of information but at the moment it is beyond my comprehension especially that I'm looking for quick verification. I'll settle for a simple solution, disable BIOS Network Controller, put another network card on a PCI bus (making sure they are on a different IRQ) and try to re-emerge kde. If it will compile without any problem it would mean I've solved the problem. Another problem with that ASUS A8V motherboard is that they put all additional USB (above 4) on the same IRQ as Sata Controller and Network Controller. This is very bad design, having high demanding resources on the same IRQ. In addition they put Floppy Controller on a separate IRQ 6 without ability to re-assign it. So one IRQ 6 is waisted if you don't have floppy drive. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Joseph wrote: Finally I was able to emerge KDE, it really took a lot of time. Though, looking at the motherboard's ASUS A8V IRQ setting: They put a lot of devices on IRQ5: skge - network controller libata - I think this is sata ATA controller ethci_Hcd:usb2, usb2 VIA8237 - sound ship No wonder I'm having problem (and some others) with Sata Drive, if it is sharing an IRQ with so many devices. In comparison IDE controller have all their own IRQ's Primary IRQ 14 and Secondary IRQ 15 Great! So, did you physically remove the sata drive? The sata drivers are still enabled though? The ouput from dmesg should give you an idea what drivers the kernel is actively using. Zac No, I still have the same Sata Drive is just I'm playing with IRQ assignment and configuration. I've changed to BIOS PnP to YES, so my skge (network controller) and libata (Sata Controller are shifted to IRQ 10 But it makes me wonder both controllers on the Motherboard are different chips, so why do they share IRQ? Is there a way to shift them to a different IRQ since Linux control IRQ assignment now? A quick look through linux/Documentation/kernel-parameters.txt shows that many drivers support direct irq assignment. Also, linux/Documentation/pnp.txt may be of use. Considering the positive results that you've gotten so far, it seems like you may be on the right track here. It makes me less concerned about any possible overheating, but if you wanted to be paranoid about it, you could get another heat probe to double check the readings from the first one ;-). Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Fri, 2005-07-22 at 11:56 -0400, Robert Crawford wrote: > One other thought- I don't recall seeing any mention of this in this thread. > Are you sure your heatsink/fan combo is rated for your AMD 64 cpu? > The heatsink came with the CPU, so I assume it should be adequate. In addition I just check the CPU temp. in Bios and it went down to 35C. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
One other thought- I don't recall seeing any mention of this in this thread. Are you sure your heatsink/fan combo is rated for your AMD 64 cpu? On Friday 22 July 2005 11:26 am, Joseph wrote: > On Fri, 2005-07-22 at 10:00 -0400, Robert Crawford wrote: > > > > I have an old IDE drive, maybe I can squeeze Gentoo on it for > > > > testing. Bob has a good idea too regarding the CPU compound under the > > > > heat-sink but at CPU temp. 39C I don't see how that could cause any > > > > problem. > > > > > > > > -- > > > > #Joseph > > > > No matter what the temp sensors are reading, your problem definitely > > sounds like it's heat related. Temp sensor readings can, and often are > > not accurate, sometimes to an amazing degree. I don't know what type of > > sensor your cpu uses, but if it's the type under the cpu, it might not be > > in good contact with the cpu itself, thus giving false readings, I > > wouldn't be surprised if your cpu temp was really over 50C. In my > > experience, temps over 50C. with AMD 32bit cpus start giving problems > > like this, no matter what AMD says about it. Seeing as how you have an > > AMD 64, I'm not sure about the sensor type- all I'm saying is that the > > readings can vary wildly, and are not to be trusted, especially > > considering your current problems. > > > > Robert Crawford\ > > I'll try to get to the bottom of it. > > 1.) First, I have noticed that the Sata Controller share one IRQ with > Network Controller, this is not a good combination. I don't know if it > is possible to re-assign and IRQ so they will be on a different one > (BIOS does not have this option). > If not I'll install another network card and disable the one on the > Motherboard. > > 2.) Heat could be a problem as you have mentioned, I'll try to change > the thermal padding under the heatsink. > > -- > #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Fri, 2005-07-22 at 10:00 -0400, Robert Crawford wrote: > > > I have an old IDE drive, maybe I can squeeze Gentoo on it for testing. > > > Bob has a good idea too regarding the CPU compound under the heat-sink > > > but at CPU temp. 39C I don't see how that could cause any problem. > > > > > > -- > > > #Joseph > > No matter what the temp sensors are reading, your problem definitely sounds > like it's heat related. Temp sensor readings can, and often are not accurate, > sometimes to an amazing degree. I don't know what type of sensor your cpu > uses, but if it's the type under the cpu, it might not be in good contact > with the cpu itself, thus giving false readings, I wouldn't be surprised if > your cpu temp was really over 50C. In my experience, temps over 50C. with > AMD 32bit cpus start giving problems like this, no matter what AMD says about > it. Seeing as how you have an AMD 64, I'm not sure about the sensor type- all > I'm saying is that the readings can vary wildly, and are not to be trusted, > especially considering your current problems. > > Robert Crawford\ I'll try to get to the bottom of it. 1.) First, I have noticed that the Sata Controller share one IRQ with Network Controller, this is not a good combination. I don't know if it is possible to re-assign and IRQ so they will be on a different one (BIOS does not have this option). If not I'll install another network card and disable the one on the Motherboard. 2.) Heat could be a problem as you have mentioned, I'll try to change the thermal padding under the heatsink. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
> > I have an old IDE drive, maybe I can squeeze Gentoo on it for testing. > > Bob has a good idea too regarding the CPU compound under the heat-sink > > but at CPU temp. 39C I don't see how that could cause any problem. > > > > -- > > #Joseph No matter what the temp sensors are reading, your problem definitely sounds like it's heat related. Temp sensor readings can, and often are not accurate, sometimes to an amazing degree. I don't know what type of sensor your cpu uses, but if it's the type under the cpu, it might not be in good contact with the cpu itself, thus giving false readings, I wouldn't be surprised if your cpu temp was really over 50C. In my experience, temps over 50C. with AMD 32bit cpus start giving problems like this, no matter what AMD says about it. Seeing as how you have an AMD 64, I'm not sure about the sensor type- all I'm saying is that the readings can vary wildly, and are not to be trusted, especially considering your current problems. Robert Crawford -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
> > Finally I was able to emerge KDE, it really took a lot of time. > > Though, looking at the motherboard's ASUS A8V IRQ setting: > > They put a lot of devices on IRQ5: > > > > skge - network controller > > libata - I think this is sata ATA controller > > ethci_Hcd:usb2, usb2 > > VIA8237 - sound ship > > > > No wonder I'm having problem (and some others) with Sata Drive, if it is > > sharing an IRQ with so many devices. In comparison IDE controller have > > all their own IRQ's Primary IRQ 14 and Secondary IRQ 15 > > > > Great! So, did you physically remove the sata drive? The sata drivers are > still enabled though? The ouput from dmesg should give you an idea what > drivers the kernel is actively using. > > Zac No, I still have the same Sata Drive is just I'm playing with IRQ assignment and configuration. I've changed to BIOS PnP to YES, so my skge (network controller) and libata (Sata Controller are shifted to IRQ 10 But it makes me wonder both controllers on the Motherboard are different chips, so why do they share IRQ? Is there a way to shift them to a different IRQ since Linux control IRQ assignment now? -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
my bid is: 1) is that sata_via kernel/module actualy loading? 2) update bios 3) check mbr hope i'm not wastig your time. I have similar box, except sata drive, but lot of sata stuf is loadin' Linux 2.6.11.11 #1 Fri Jun 17 11:19:52 EEST 2005 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux martins On Friday 22 July 2005 07:26, Joseph wrote: > > > The latest news. > > > After taking the cover off; the temp. of the CPU went down by 3C to > > > 37C and Motherboard down by 3C as well to 26C. but that still didn't > > > prevent the the kernel panic message: > > > Kernel panic - not syncing: Aiee, killing interupt handler. > > > > > > So my next solution is to get another Drive but an IDE type and put the > > > SATA one on the shelf, and reinstall Gentoo. > > > > Ideally, it would be nice if you could test this idea before taking such > > a large step. Maybe you can boot from a livecd, reproduce the error, and > > then try to reproduce the error again without your sata driver loaded. > > > > Zac > > I have an old IDE drive, maybe I can squeeze Gentoo on it for testing. > Bob has a good idea too regarding the CPU compound under the heat-sink > but at CPU temp. 39C I don't see how that could cause any problem. > > -- > #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Joseph wrote: Another theory I have is that it could be related to IRQ timing / sharing of the Serial SATA with PCI slot 3 on the A8V motherboard. They are sharing the same IRQ base on the information from the Manual, though the manual is not saying which IRQ is it. How can I find out? Maybe I can disable or select option RESERVER for that IRQ from Bios. It looks like you can do "lspci -vv" to get the IRQ. At least an IRQ problem would be consistent with the "killing interrupt handler" message you got. BTW, you get a full oops message out of this? That might be useful for debugging. Zac Finally I was able to emerge KDE, it really took a lot of time. Though, looking at the motherboard's ASUS A8V IRQ setting: They put a lot of devices on IRQ5: skge - network controller libata - I think this is sata ATA controller ethci_Hcd:usb2, usb2 VIA8237 - sound ship No wonder I'm having problem (and some others) with Sata Drive, if it is sharing an IRQ with so many devices. In comparison IDE controller have all their own IRQ's Primary IRQ 14 and Secondary IRQ 15 Great! So, did you physically remove the sata drive? The sata drivers are still enabled though? The ouput from dmesg should give you an idea what drivers the kernel is actively using. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Thu, 2005-07-21 at 22:09 -0700, Zac Medico wrote: > Joseph wrote: > > [snip] > > > >>The latest news. > >>After taking the cover off; the temp. of the CPU went down by 3C to 37C > >>and Motherboard down by 3C as well to 26C. but that still didn't prevent > >>the the kernel panic message: > >>Kernel panic - not syncing: Aiee, killing interupt handler. > >> > >>So my next solution is to get another Drive but an IDE type and put the > >>SATA one on the shelf, and reinstall Gentoo. > > > > > > Another theory I have is that it could be related to IRQ timing / > > sharing of the Serial SATA with PCI slot 3 on the A8V motherboard. > > They are sharing the same IRQ base on the information from the Manual, > > though the manual is not saying which IRQ is it. > > How can I find out? > > Maybe I can disable or select option RESERVER for that IRQ from Bios. > > > > It looks like you can do "lspci -vv" to get the IRQ. At least an IRQ problem > would be consistent with the "killing interrupt handler" message you got. > BTW, you get a full oops message out of this? That might be useful for > debugging. > > Zac Finally I was able to emerge KDE, it really took a lot of time. Though, looking at the motherboard's ASUS A8V IRQ setting: They put a lot of devices on IRQ5: skge - network controller libata - I think this is sata ATA controller ethci_Hcd:usb2, usb2 VIA8237 - sound ship No wonder I'm having problem (and some others) with Sata Drive, if it is sharing an IRQ with so many devices. In comparison IDE controller have all their own IRQ's Primary IRQ 14 and Secondary IRQ 15 -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Joseph wrote: [snip] The latest news. After taking the cover off; the temp. of the CPU went down by 3C to 37C and Motherboard down by 3C as well to 26C. but that still didn't prevent the the kernel panic message: Kernel panic - not syncing: Aiee, killing interupt handler. So my next solution is to get another Drive but an IDE type and put the SATA one on the shelf, and reinstall Gentoo. Another theory I have is that it could be related to IRQ timing / sharing of the Serial SATA with PCI slot 3 on the A8V motherboard. They are sharing the same IRQ base on the information from the Manual, though the manual is not saying which IRQ is it. How can I find out? Maybe I can disable or select option RESERVER for that IRQ from Bios. It looks like you can do "lspci -vv" to get the IRQ. At least an IRQ problem would be consistent with the "killing interrupt handler" message you got. BTW, you get a full oops message out of this? That might be useful for debugging. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
> > The latest news. > > After taking the cover off; the temp. of the CPU went down by 3C to 37C > > and Motherboard down by 3C as well to 26C. but that still didn't prevent > > the the kernel panic message: > > Kernel panic - not syncing: Aiee, killing interupt handler. > > > > So my next solution is to get another Drive but an IDE type and put the > > SATA one on the shelf, and reinstall Gentoo. > > > > Ideally, it would be nice if you could test this idea before taking such a > large step. Maybe you can boot from a livecd, reproduce the error, and then > try to reproduce the error again without your sata driver loaded. > > Zac I have an old IDE drive, maybe I can squeeze Gentoo on it for testing. Bob has a good idea too regarding the CPU compound under the heat-sink but at CPU temp. 39C I don't see how that could cause any problem. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Joseph wrote: On Thu, 2005-07-21 at 19:05 -0700, Zac Medico wrote: Bob Sanders wrote: On Thu, 21 Jul 2005 16:50:49 -0600 Joseph <[EMAIL PROTECTED]> wrote: I wasn't clear, the computer runs usually for 20 to 30minus and kernel panic comes up on the screen. I'm still googling for some solutions and I can only find some suggestion; no clear answer. i I think you have hardware problems - maybe a heat issue. have you tried running with the covers off and a fan blowing onto the system? Good thinking Bob! That 20 to 30 minutes certainly seems symptomatic of overheating. I've been confused throughout this whole thread thinking that the kernel panic and kde compile were somehow related. I know, sounds crazy, but that's how I interpreted Joseph's explanation of the situation. Zac The latest news. After taking the cover off; the temp. of the CPU went down by 3C to 37C and Motherboard down by 3C as well to 26C. but that still didn't prevent the the kernel panic message: Kernel panic - not syncing: Aiee, killing interupt handler. So my next solution is to get another Drive but an IDE type and put the SATA one on the shelf, and reinstall Gentoo. Ideally, it would be nice if you could test this idea before taking such a large step. Maybe you can boot from a livecd, reproduce the error, and then try to reproduce the error again without your sata driver loaded. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Thu, 21 Jul 2005 18:46:42 -0600 Joseph <[EMAIL PROTECTED]> wrote: > I couldn't find the 32-bit mode feature in BIOS setting. > Under what menu is it? > Usually associated with the IDE controller or drives. Most newer bios' have it set to - AUTO, which should switch it into 32-bit, aka LBA mode. Probably under - Integrated Peripherals. It may also say something like - IDE Primary MASTER UDMA Auto. > Previously as was able to compile only few packages running for 20min > before crashing. > Now, I was able to keep compiling for about 2-hours before kernel panic > showed up. > >From what you've said, I think it might be useful to remove the cpu heatsink and check the state of the thermal material. Look to see if the cpu is in full contact with it. The downside to doing this is the thermal material is single use only. You'll need some alcohol to remove the material, after inspecting, then some decent Thermal compound to replace it. While it's been shown not to make a lot of difference in the short run, I tend to prefer the Artic Silver products because they are stable over time. The normal white grease drys out as do some others. The single use thermal pads are fine and generally work well. Bob - -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
[snip] > > The latest news. > After taking the cover off; the temp. of the CPU went down by 3C to 37C > and Motherboard down by 3C as well to 26C. but that still didn't prevent > the the kernel panic message: > Kernel panic - not syncing: Aiee, killing interupt handler. > > So my next solution is to get another Drive but an IDE type and put the > SATA one on the shelf, and reinstall Gentoo. Another theory I have is that it could be related to IRQ timing / sharing of the Serial SATA with PCI slot 3 on the A8V motherboard. They are sharing the same IRQ base on the information from the Manual, though the manual is not saying which IRQ is it. How can I find out? Maybe I can disable or select option RESERVER for that IRQ from Bios. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Fri, 2005-07-22 at 14:46 +1200, Jamie Dobbs wrote: > > The latest news. > > After taking the cover off; the temp. of the CPU went down by 3C to 37C > > and Motherboard down by 3C as well to 26C. but that still didn't prevent > > the the kernel panic message: > > Kernel panic - not syncing: Aiee, killing interupt handler. > > > > So my next solution is to get another Drive but an IDE type and put the > > SATA one on the shelf, and reinstall Gentoo. > > If you haven't done so already I'd recommend a thorough memory check > before you do anything else, I have seen (albiet on rare occassions) > faulty RAM causing these sorts of issues. > I've run memtest86 last night 17-passes, not a single error. So it is not the memory. It could be the Sata Via driver in the Kernel. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
> The latest news. > After taking the cover off; the temp. of the CPU went down by 3C to 37C > and Motherboard down by 3C as well to 26C. but that still didn't prevent > the the kernel panic message: > Kernel panic - not syncing: Aiee, killing interupt handler. > > So my next solution is to get another Drive but an IDE type and put the > SATA one on the shelf, and reinstall Gentoo. If you haven't done so already I'd recommend a thorough memory check before you do anything else, I have seen (albiet on rare occassions) faulty RAM causing these sorts of issues. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Thu, 2005-07-21 at 19:05 -0700, Zac Medico wrote: > Bob Sanders wrote: > > On Thu, 21 Jul 2005 16:50:49 -0600 > > Joseph <[EMAIL PROTECTED]> wrote: > > > > > > > >>I wasn't clear, the computer runs usually for 20 to 30minus and kernel > >>panic comes up on the screen. I'm still googling for some solutions and > >>I can only find some suggestion; no clear answer. > >>i > > > > > > I think you have hardware problems - maybe a heat issue. have you tried > > running > > with the covers off and a fan blowing onto the system? > > > > > > Good thinking Bob! That 20 to 30 minutes certainly seems symptomatic of > overheating. > > I've been confused throughout this whole thread thinking that the kernel > panic and kde compile were somehow related. I know, sounds crazy, but that's > how I interpreted Joseph's explanation of the situation. > > Zac The latest news. After taking the cover off; the temp. of the CPU went down by 3C to 37C and Motherboard down by 3C as well to 26C. but that still didn't prevent the the kernel panic message: Kernel panic - not syncing: Aiee, killing interupt handler. So my next solution is to get another Drive but an IDE type and put the SATA one on the shelf, and reinstall Gentoo. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Thu, 2005-07-21 at 17:09 -0700, Zac Medico wrote: > Joseph wrote: > > > > I wasn't clear, the computer runs usually for 20 to 30minus and kernel > > panic comes up on the screen. I'm still googling for some solutions and > > I can only find some suggestion; no clear answer. > > > > I think I went too fast for AMD64; I should have stayed with x86 and old > > good IDE drive. > > Somebody suggested: "Enabling 32 bit mode for the drives in the BIOS to > > cure this problem." I'll check my Bios the next time it will crash :-/ > > > > If the only problem is the sata controller then you can try > interfacing your hard drive some other way until the sata driver > situation clears up. > > I actually boot my system off of a 3.5" hard drive that's in an > external usb 2.0 enclosure. That way I can plug into practically any > computer and have my complete gentoo system! I've even though about > buying USB 2.0/IDE bridges for internal use (rather than for an > external enclosure) because they are inexpensive and allow for hot > swapping. I was browsing the net and I've noticed that a lot of people are getting similar error and a lot of them mentioned SCSI drive. I happened with back to kernel 2.4 and 1999 year so it could be related to SCSI driver, not sure about it. I've taken the cover off to allow more air into the box (most of my other boxes run without any covers). If I still get that error: Kernel panic - not syncing: Aiee, killing interupt handler. I'll buy an IDE drive and put this SATA drive on a shelve, and see if will make a difference. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Bob Sanders wrote: On Thu, 21 Jul 2005 16:50:49 -0600 Joseph <[EMAIL PROTECTED]> wrote: I wasn't clear, the computer runs usually for 20 to 30minus and kernel panic comes up on the screen. I'm still googling for some solutions and I can only find some suggestion; no clear answer. i I think you have hardware problems - maybe a heat issue. have you tried running with the covers off and a fan blowing onto the system? Good thinking Bob! That 20 to 30 minutes certainly seems symptomatic of overheating. I've been confused throughout this whole thread thinking that the kernel panic and kde compile were somehow related. I know, sounds crazy, but that's how I interpreted Joseph's explanation of the situation. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
[snip] > > I think you have hardware problems - maybe a heat issue. have you tried > running > with the covers off and a fan blowing onto the system? I've checked: CPU temp. was 40C and MB temp was 29C Though, I've taken the cover off and run it for a while without cover. > > > I think I went too fast for AMD64; I should have stayed with x86 and old > > good IDE drive. > > Somebody suggested: "Enabling 32 bit mode for the drives in the BIOS to > > cure this problem." I'll check my Bios the next time it will crash :-/ > >i > > Yes, 32-bit should be enabled, but I can't see where it would cause this > problem. I couldn't find the 32-bit mode feature in BIOS setting. Under what menu is it? Previously as was able to compile only few packages running for 20min before crashing. Now, I was able to keep compiling for about 2-hours before kernel panic showed up. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Thu, 21 Jul 2005 16:50:49 -0600 Joseph <[EMAIL PROTECTED]> wrote: > > I wasn't clear, the computer runs usually for 20 to 30minus and kernel > panic comes up on the screen. I'm still googling for some solutions and > I can only find some suggestion; no clear answer. > i I think you have hardware problems - maybe a heat issue. have you tried running with the covers off and a fan blowing onto the system? > I think I went too fast for AMD64; I should have stayed with x86 and old > good IDE drive. > Somebody suggested: "Enabling 32 bit mode for the drives in the BIOS to > cure this problem." I'll check my Bios the next time it will crash :-/ >i Yes, 32-bit should be enabled, but I can't see where it would cause this problem. fwiw - this is being sent from an AMD64 3000, nforce3 chipset, Shuttle box, IDE drive, running Gentoo - # uname -av Linux chi 2.6.12-gentoo-r4 #1 Mon Jul 11 19:02:55 PDT 2005 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux [ I] kde-base/kdebase (3.4.1-r1): KDE base packages: the desktop, panel, window [ I] sys-devel/gcc (3.4.3-r1): The GNU Compiler Collection. Includes C/C++, Bob - -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Joseph wrote: I wasn't clear, the computer runs usually for 20 to 30minus and kernel panic comes up on the screen. I'm still googling for some solutions and I can only find some suggestion; no clear answer. I think I went too fast for AMD64; I should have stayed with x86 and old good IDE drive. Somebody suggested: "Enabling 32 bit mode for the drives in the BIOS to cure this problem." I'll check my Bios the next time it will crash :-/ If the only problem is the sata controller then you can try interfacing your hard drive some other way until the sata driver situation clears up. I actually boot my system off of a 3.5" hard drive that's in an external usb 2.0 enclosure. That way I can plug into practically any computer and have my complete gentoo system! I've even though about buying USB 2.0/IDE bridges for internal use (rather than for an external enclosure) because they are inexpensive and allow for hot swapping. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Thu, 2005-07-21 at 15:31 -0700, Zac Medico wrote: > Joseph wrote: > > [snip] > > > >>Maybe you just need to run fix_libtool_files.sh, which is normal after a > >>compiler upgrade. > >> > >>Zac > > > > > > I don't know if that helped but it deeps running for over 20min. so > > hopefully maybe I'll be done by Sunday. If not I will have to take a > > drastic measure and move to another dystro; which I don't like but don't > > have very many options. > > > > It shouldn't take too long, 20 minutes seems excessive. Does it seem like > it's doing anything? If not do ctrl-c to kill it, then maybe run it again. > Also, use a process manager (ps will do it) to find out what program it's > hung up in. > > I like Portage so much that I'd rather use all GRP packages than go back to > an rpm based distro. > > Zac I wasn't clear, the computer runs usually for 20 to 30minus and kernel panic comes up on the screen. I'm still googling for some solutions and I can only find some suggestion; no clear answer. I think I went too fast for AMD64; I should have stayed with x86 and old good IDE drive. Somebody suggested: "Enabling 32 bit mode for the drives in the BIOS to cure this problem." I'll check my Bios the next time it will crash :-/ -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Joseph wrote: [snip] Maybe you just need to run fix_libtool_files.sh, which is normal after a compiler upgrade. Zac I don't know if that helped but it deeps running for over 20min. so hopefully maybe I'll be done by Sunday. If not I will have to take a drastic measure and move to another dystro; which I don't like but don't have very many options. It shouldn't take too long, 20 minutes seems excessive. Does it seem like it's doing anything? If not do ctrl-c to kill it, then maybe run it again. Also, use a process manager (ps will do it) to find out what program it's hung up in. I like Portage so much that I'd rather use all GRP packages than go back to an rpm based distro. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
[snip] > > Maybe you just need to run fix_libtool_files.sh, which is normal after a > compiler upgrade. > > Zac I don't know if that helped but it deeps running for over 20min. so hopefully maybe I'll be done by Sunday. If not I will have to take a drastic measure and move to another dystro; which I don't like but don't have very many options. -- #Joseph -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
Joseph wrote:
Both bugs are back.
I've tried to emerge kde-meta (split kde ebuild) and it hang up on:
ERROR: kde-base/kdepim-kresources-3.4.1 filed.
Few lines above it starts with:
Code: 48 89 4a 08 ...
RIP {buffered_rmqueue+262} RSP
CR2: ...
libtool: link: '/usr/kde/3.4/lib64/libDCOP.la' is not a valid libtool
archive
make[4]: *** [kabc_kolab.la] Error 1
This is a new install so I can not retype all the errors by hand.
Anyhow, I think I have enough compiling on AMD64, I've been trying to
install something since last Friday and still not getting anywhere, so
after almost one week of compiling it didn't achieve anything.
I'll try to install Ubuntu on this box and see what happens.
Thanks everybody for your help.
#Joseph
Maybe you just need to run fix_libtool_files.sh, which is normal after a
compiler upgrade.
Zac
--
gentoo-user@gentoo.org mailing list
[gentoo-user] Going to Ubuntu - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler
On Thu, 2005-07-21 at 11:47 -0700, Zac Medico wrote:
> Joseph wrote:
> >
> > I think they solved the problem with gcc-3.4.3-r1
> > The only problem is left is the Kernel Panic:
> > Kernel panic - not syncing: Aiee, killing interupt handler.
> >
> > Every few packages it emerges it the machine hangs up on kernel panic.
> >
>
> So, 1) and 2) from your original email are completely separate issues? If
> so, I was confused and thought they were related somehow.
>
> You've definitely got a kernel bug there. Have you searched to see if anyone
> else has experienced this problem? Like Patrick said in the first reply, you
> might need to pursue this one upstream with the kernel developers.
>
> Zac
Both bugs are back.
I've tried to emerge kde-meta (split kde ebuild) and it hang up on:
ERROR: kde-base/kdepim-kresources-3.4.1 filed.
Few lines above it starts with:
Code: 48 89 4a 08 ...
RIP {buffered_rmqueue+262} RSP
CR2: ...
libtool: link: '/usr/kde/3.4/lib64/libDCOP.la' is not a valid libtool
archive
make[4]: *** [kabc_kolab.la] Error 1
This is a new install so I can not retype all the errors by hand.
Anyhow, I think I have enough compiling on AMD64, I've been trying to
install something since last Friday and still not getting anywhere, so
after almost one week of compiling it didn't achieve anything.
I'll try to install Ubuntu on this box and see what happens.
Thanks everybody for your help.
#Joseph
--
#Joseph
--
gentoo-user@gentoo.org mailing list
