Summary: | emerge hangs display (ususally not sshed session) during metadata stage | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Mike Hammill <michael> |
Component: | Core | Assignee: | PPC Porters <ppc> |
Status: | VERIFIED NEEDINFO | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mike Hammill
2005-05-11 14:39:19 UTC
What makes you think it is a GRP bug? Have you tried the 2005.0 GRP? Are you sure thi sisn't just a normal bug and should be assigned appropriately elsewhere? *** Bug 92371 has been marked as a duplicate of this bug. *** (In reply to comment #1) > What makes you think it is a GRP bug? Have you tried the 2005.0 GRP? > > Are you sure thi sisn't just a normal bug and should be assigned appropriately elsewhere? Interesting question. I really have no idea which section of Gentoo's bugzilla to submit the bug. I figured you could re-assign it at will if you thought the categorization was wrong. My thinking was that emerge is part of the basic Gentoo system so GRP seemed appropriate. Feel free to re-assign the categorization as you see fit. Of course, fixing the bug would be even better :-) Yeah... I can't fix it... I'm not a portage dev... reassigning... Try turning off power management in the kernel. This isn't a portage thing. It sounds like linux is blanking or turning off the screen after you haven't physically touched the machine for a while and you are unable to wake it up. Try `setterm -blank 0` before running emerge sync as well. Originally, I too figured it was a power management issue. However, that fact that when it happens it even kills remote ssh sessions sometimes (it even powered down the machine one time!) makes it clear is it not *just* blanking the screen. I give some examples of what the machine was doing when the crashing occurred in the discussion forum thread mentioined <http://forums.gentoo.org/viewtopic-t -46428-highlight-.html>. In brief, a portageq/emerge/ebuild was 99% of the time going on. When I happened to be around to see it in person, I can say I suspect it was in the step "Regenerating /etc/ ld.so.cache...". I'm sorry to say I am running Fedora Core 4 Test 3 on the machine now (no instability) because I couldn't take the instability of Gentoo. I'd prefer to run Gentoo on the PPC, as I do on other non-PPC machines, but until I can get a Gentoo LiveCD to boot on it (see bug 87650), or more stability, I will have to leave you with the evidence previously provided. Hope you can find something. I am willing to try testing again IF you get a bootable LiveCD that works. Best regards, /Mike (In reply to comment #5) > Try turning off power management in the kernel. This isn't a portage thing. It > sounds like linux is blanking or turning off the screen after you haven't > physically touched the machine for a while and you are unable to wake it up. > Try `setterm -blank 0` before running emerge sync as well. I'll ignore the "instability of gentoo" comment and pass this on to PPC whom might have experienced apparent hardware issues like this in the past. Please don't take my comment the wrong way. I would LOVE to have Gentoo running on my PPC. It seemed very promising when I tried it under 2004.3. I took the time to write a bug report to help improve Gentoo. Best of luck. If there is anything I can do to help, please let me know. If you're still running redhat, could you try creating a gentoo chroot within your install? I'd be interested to know if that locks up as well. I'm also wondering if a different kernel version would have helped. I do know of others who have installed fine on their Sawtooth G4's so I'm not sure what else to suggest. Please reopen the bug if you try it again and still have a problem. No reply. |