On my main devel box, vanilla 2.6.23 on x86-64/Fedora-7, I'm seeing a certain behavior at least once a day. I'll start a kernel build (make -sj5 on this box), and it will "hang" in the following way:Specifically, the symptom is a process, often a simple one like cat(1) or rm(1) or somewhere in check-headers, will stay in the running state, accumulating CPU time. If I Ctrl-C the build, and start over, the build will normally -not- get stuck at the same point, but proceed to chew through one of a bazillion allmodconfig builds. I also see this occasionally on my main workstation (also 2.6.23/x86-64/Fedora-7), though not as frequently. This is a new behavior since the new scheduler was merged... I think. Nothing more concrete to report at this time. I cannot easily reproduce the behavior, as it happens [apparently] randomly sometime during the day. Generally, the files these programs are dealing with are -always- in the pagecache, if that makes any difference. Jeff -
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Re: init's children list is long and slows reaping children. |
| Kohei KaiGai | [PATCH 0/3] exporting capability name/code pairs (final#2) |
git: | |
| Gerrit Renker | [PATCH 33/37] dccp: Initialisation framework for feature negotiation |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Mark Ryden | Re: Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008 |
