[00:17] <amitk> cr3: I see many changes, for the server config, the IO scheduler is deadline, highmem is enabled, etc.
[00:23] <cr3> amitk: I see many changes by having downloaded the package as suggested by elmo, but the git tree looked the same. maybe I'm not looking at the right root: ubuntu/ubuntu-gutsy.git
[00:25] <amitk> cr3: that sounds right.
[00:28] <cr3> I'm grepping for CONFIG_HZ under /usr/src/linux/Documentation for more details about this kernel configuration parameter, but nothing is coming up. Is there another location to look for documentation about specific configuration parameters?
[00:30] <verwilst> is -xen based on -server?
[00:30] <verwilst> as in, server oriented?
[00:34] <johanbr> cr3: sched-nice-design.txt in the Documentation directory.
[00:45] <cr3> has the CONFIG_X86_BIGSMP configuration option been deprecated?
[00:55] <cr3> nevermind, I was looking at the wrong configuration. so, why isn't CONFIG_X86_BIGSMP enabled in the server kernel?
[01:22] <SirBob1701> you guys doing anything about the tty's being dropped after the upgrade?
=== chuck_ is now known as zul
=== rikai_ is now known as rikai
=== Whoopie_ is now known as Whoopie
[08:00] <kraut> moin
[08:30] <AnAnt> Hello ?
=== zul_ is now known as zul
[11:05] <xipietotec> are there known issues with the low-latency kernel and suspend?
[11:08] <xipietotec> I'm having issues with suspend only being able to sleep 1 of my cpu...it does this somewhat randomnly for lengths and lengths at a time, without me changing any of my settings. I thought this might be an nvidia thing, so I loaded vesa...same issue. The only thing I can think of is it might be an issue with the low-latency kernel
[11:38] <verwilst> hi zul
[11:38] <verwilst> hi * ;)
[11:55] <ln-> would it be possible to get this bug fixed in dapper's kernel: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/65631
[11:55] <ubotu> Launchpad bug 65631 in linux-source-2.6.15 "skge driver broken: invalid call to spin_unlock causes system crash" [Undecided,Confirmed] 
[12:02] <ln-> i do know how to use the attached patch and fix the problem for myself, but each time the kernel gets updated the patched driver is replaced and we need to manually copy the patched driver back to all four affected systems at the office.
[12:04] <ln-> i can only imagine how many people world-wide are experiencing random mysterious system lockups because of this bug.
[12:30] <verwilst> ln-: i have nothing to do with ubuntu-kernel-development, but it strikes me as silly that it's not patched by default by now idd
=== asac_ is now known as asac
[13:40] <Whoopie> To all of you: WELL DONE!
=== Traxer is now known as Traxer|on
=== Traxer|on is now known as Traxer
=== xipietotec_ is now known as xipietotec
=== ivoks_ is now known as ivoks
=== chuck_ is now known as zul
[23:23] <verwilst> zul: ping
[23:23] <zul> verwilst: yeah?
[23:23] <verwilst> zul: the patch i gave you, did it help?
[23:23] <zul> verwilst: no doesnt apply
[23:24] <verwilst> or did it look like it would help
[23:24] <verwilst> oh?
[23:24] <zul> its for 2.6.18
[23:24] <verwilst> hm
[23:24] <verwilst> how's your clock fix?
[23:24] <verwilst> had any crashes yet since?
[23:25] <zul> i used clock=pit nope
[23:25] <verwilst> hm
[23:25] <verwilst> and performance-wise?
[23:25] <verwilst> any downsides?
[23:26] <verwilst> zul: and -xen, is it like -server? server-oriented?
[23:26] <zul> no desktop it uses -generic kernel
[23:26] <verwilst> i mean tuned for throughput
[23:26] <verwilst> hm