
the git-servers seemingly are undergoing maintenancewrc1944 wrote:I installed zen2 last night on another box, but today keep getting this:Is it just something on your end- like updating to a new version, or a server problem? Nothing seems wrong on this system.Code: Select all
amd64 src # git clone git://zen-sources.org/zen/zen-stable.git zen-sources Initialized empty Git repository in /usr/src/zen-sources/.git/ fatal: Unable to look up zen-sources.org (port 9418) (Temporary failure in name resolution) amd64 src # git clone git://zen-sources.org/zen/zen-stable.git zen-sources Initialized empty Git repository in /usr/src/zen-sources/.git/ fatal: read error: Connection reset by peer amd64 src #
http://git.zen-sources.org wrote: 404 - Not Found

Yeah, I am getting these again. I thought I had solved them - but no, they are still there. Suspend to RAM, Shutdown - nothing works.tranquilcool wrote:shutdown errors here too.broch wrote:I can confirm that with 2.6.31-zen2
suspend to RAM fails
in contrast patched with bfs vanilla 2.6.31.1 does not have problems with suspend-to-ram, so maybe this is not a bfs fault?
additionally, when shutting down kernel generates error regarding "mounting/read only"
system shuts down but error is a little bit worrying.
again, this is specific to zen, bfs patched vanilla *.31.1 works


I have a quad core. I thought it stood to reason that the selected frequency x # of cores/procs would be the real measure of ticks on a system. I'm not looking to run at the very lowest latencies on my system. I'm not looking to run at maximum bandwidth either. Since I can select a range from 100 to 1000 Hz in the Zen config with it seems that the author(s) share this same paradigm (of which you are one, correct?).cheater1034 wrote:If you're running a server/desktop i would disable dynticks. If you're running X on the server/desktop, set HZ=1000
voluntary preemption is junk, don't use it (you can't use it with bfs since it's disabled in Kconfig when bfs is selected. Full preemption is probably your best bet, no preemption is acceptable too - but if you are running X i'd suggest it.


Code: Select all
cp /disk1/$(largefile) /disk2/ $ sleep 3
time echo 1 > /proc/sys/vm/drop_caches
time sleep .2
time echo 1 > /proc/sys/vm/drop_caches
time sleep .2I have zen with BFQ on different dektops and notebooks installed. All but one desktop behaved great. It felt laggy and CPU kernel usage (red bar in htop) was unusually high. I compared kernel configs of my machines and it actually was particular SLAB allocator responsible for lack of responsiveness.DigitalCorpus wrote:I'm going to test CFQ over BFQ as my I/O scheduler and SLUB instead of SLQB to see if either of those have an effect.

Which ones worked best for you?Mr. Tao wrote:I have zen with BFQ on different dektops and notebooks installed. All but one desktop behaved great. It felt laggy and CPU kernel usage (red bar in htop) was unusually high. I compared kernel configs of my machines and it actually was particular SLAB allocator responsible for lack of responsiveness.DigitalCorpus wrote:I'm going to test CFQ over BFQ as my I/O scheduler and SLUB instead of SLQB to see if either of those have an effect.

git pull
fatal: The remote end hung up unexpectedly


Code: Select all
amd64 src # git clone git://zen-sources.org/zen/zen-stable.git zen-sources
Initialized empty Git repository in /usr/src/zen-sources/.git/
zen-sources.org[0: 134.155.50.250]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)Code: Select all
initialized empty Git repository in /usr/src/zen-sources/.git/
fatal: The remote end hung up unexpectedly

thanks !cheater1034 wrote:GIT is back up but the URLS HAVE CHANGED - so check out git.zen-sources.org for the new ones (i think the only change was removing /zen/

[remote "origin"]
url = git://zen-sources.org/zen/zen-stable.git
fetch = +refs/heads/*:refs/remotes/origin/*
when using (un)stable change[remote "origin"]
url = git://zen-sources.org/zen-stable.git
fetch = +refs/heads/*:refs/remotes/origin/*
[remote "origin"]
url = git://zen-sources.org/zen/zen.git
fetch = +refs/heads/*:refs/remotes/origin/*
in the file[remote "origin"]
url = git://zen-sources.org/zen.git
fetch = +refs/heads/*:refs/remotes/origin/*

Code: Select all
git clone git://zen-sources.org/zen-stable.git zen-sourcesCode: Select all
amd64 src #git clone git://zen-sources.org/zen-stable.git zen-sources
bash: clone: command not found
amd64 src #
you can wait for stable patches on http://zen-sources.org or you can also try a snapshot of the full source (the snapshot link on the right of the last commit, the first counting from beginning of page -wrc1944 wrote:This is really getting frustrating and consuming way too much time, all simply to patch a specific kernel with the great zen patches, which use to be a very simple matter. I have to echo another zen users comment (I think it was Jupiter1TX) that this has become a huge "mind fuck".

I have SLQB selected now. The problematic one was, if I'm not mistaken, SLOB.DigitalCorpus wrote:Which ones worked best for you?Mr. Tao wrote:I have zen with BFQ on different dektops and notebooks installed. All but one desktop behaved great. It felt laggy and CPU kernel usage (red bar in htop) was unusually high. I compared kernel configs of my machines and it actually was particular SLAB allocator responsible for lack of responsiveness.
cheater1034 wrote:Guys, guys, guys
settle down:
- zen.git isn't simply newer than zen-stable.git ........ it is the UNSTABLE zen, meaning -rc kernels, etc. so it's in the PROCESS of being rebased to 2.6.32, so naturally zen-stable.git is newer than zen.git if zen.git hasnt been updated since zen0
- you don't need patches on the downloads page - you can diff patches on gitweb, or use git itself (and diff patches actually using git?) - i wrote a tutorial on the FAQ page at zen-sources.org
- Cloning GIT is not like getting a patch, you can update git of course - you should only have to clone once as long as the tree is on your system, update with git pull
Jeez you guys make this harder than it has to be, of course zen is updated too guys - don't need to ask about bfs 300, when many of us are in #ck all the time when con makes the releases, if you are unsure pull and check the log (git log), and look for the commit message (search is / in less)
Always, if you simply want a patch, go to git.zen-sources.org, click on the git tree you want (zen.git/zen-stable.git) and read the tutorial on the FAQ on zen-sources.org