| Summary: | glibc-2.3.4.20040808 leads to lock-ups | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Prakash Punnoor <prakashp> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Prakash Punnoor
2004-08-11 01:02:26 UTC
no bugs that i know of, but i dont use NPTL... and i would need a -lot- more information to debug this since this version works perfectly here. Hi, I installed glibc-2.3.4.20040808 last night and let the computer run through the whole night after that. Not even one single lockup the last eight hours... Poly Well, maybe it is nvidia binary driver related. I am using 61.06 and glibc 20040619-r1 and since yesterday all is fine again. Anyone here using nvidia driver? Mybe we will get more lock-ups reports from nvidia users since now glibc 20040808 has become ~x86... I posted a comment to the forums regarding a problem I've consistently seen with glibc-2.3.3-20040808. In short, all of the computers I've updated to glibc-2.3.3-20040808 have lost network connectivity. E.g., I cannot SSH into any of the computers after they're updated, ping common addresses outside our LAN like www.yahoo.com or www.google.com from them, or browse the internet or check mail from them. Every one of ten computers I've updated to this version of glibc has demonstrated this behavior. Whoops, I forgot to note that the problem goes away after a reboot. |