=== fbond|away is now known as fbond === fbond is now known as fbond|away === fbond|away is now known as fbond === mxpxpod [n=bryan@unaffiliated/mxpxpod] has joined #ubuntu-kernel === Lathiat [i=lathiat@ubuntu/member/pdpc.basic.lathiat] has left #ubuntu-kernel [] === crimsun_ [n=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-kernel === JaneW [n=JaneW@dsl-146-154-109.telkomadsl.co.za] has joined #ubuntu-kernel === doko [n=doko@dslb-084-059-069-105.pools.arcor-ip.net] has joined #ubuntu-kernel === mroth [n=mroth@unaffiliated/mroth] has joined #ubuntu-kernel === chmj [n=chmj@196.44.1.98] has joined #ubuntu-kernel === CataEnry [n=cataenry@host83-39.pool8248.interbusiness.it] has joined #ubuntu-kernel === CataEnry [n=cataenry@host83-39.pool8248.interbusiness.it] has joined #ubuntu-kernel === Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-kernel === doko [n=doko@dslb-084-059-112-177.pools.arcor-ip.net] has joined #ubuntu-kernel === mxpxpod [n=BryanFor@unaffiliated/mxpxpod] has joined #ubuntu-kernel === Keybuk [n=scott@82.108.80.246] has joined #ubuntu-kernel === cmvo [n=cmvo@62.225.11.174] has joined #ubuntu-kernel === allee [n=ach@allee.exgal.mpe.mpg.de] has joined #ubuntu-kernel [05:36] [17:21] Sun Galaxy X4100: mpt* drivers in dapper. Two (or one) simple disk are detected during installation. When 2 disk configured as RAID1 in the LSI controller, kernel fails to detect the disk [05:36] [17:22] scsi0 : ioc0: LSISAS1064, FwRev=01040000h, Ports=1, MaxQ=511, IRQ=169 [05:36] [17:22] Is this a limitation of the driver or a bug? [05:36] [17:23] SLES9 has no problem with the RAID1 of the LSI controler. And uses it as sda. [05:36] [17:28] SLES9 uses: Fusion MPT SAS Host driver 3.02.62sus [05:36] [17:28] ubuntu uses: [05:36] [17:28] Fusion MPT SAS Host driver 3.03.04 === svenl [n=svenl@LAubervilliers-151-12-84-108.w193-252.abo.wanadoo.fr] has joined #ubuntu-kernel [05:48] hi guys ... [05:49] is it true that you guys dropped the mkvmlinuz support for the dapper linux-image kernel ? [05:49] i heard a report claiming it was because "nobody uses oldworld machines anymore", which seems likevery clueless ... === mroth [n=mroth@unaffiliated/mroth] has joined #ubuntu-kernel [05:55] We've never supported oldworld machines [05:55] what is 'oldworld' ? [05:55] mkrufky: Pre-imac and blue and white G3s [05:58] When those were introduced, Apple went to a new Open Firmware version [05:58] So the ended up being called "old world" and "new world" macs [05:58] mjg59: yeah, but the mkvmlinuz support patch was not there for oldworld, but for chrp machines, including IBM chrp and genesis's pegasos machine. [05:58] ah, okay [05:59] mjg59: and genesis was just added recently as a ubuntu partner, so i doubt that sabotaging the pegasos support this way is the right thing to do. [05:59] svenl: If you are going to describe it as "sabotaging", then this conversation is over [05:59] mjg59: well. === svenl [n=svenl@LAubervilliers-151-12-84-108.w193-252.abo.wanadoo.fr] has left #ubuntu-kernel [] [05:59] mjg59: ++ [05:59] thanks === svenl [n=svenl@LAubervilliers-151-12-84-108.w193-252.abo.wanadoo.fr] has joined #ubuntu-kernel [06:01] mjg59: oh well, i will let my hierarchy handle this with the ubuntu hierarchy, but this is a repeat of what happened for the breezy release, so i am not overly sympathetic, especially since the ubuntu kernel guys are making noises about unification of the ubuntu kernel with the debian kernel on public forums and such. === svenl [n=svenl@LAubervilliers-151-12-84-108.w193-252.abo.wanadoo.fr] has left #ubuntu-kernel [] [06:02] Drive-by svenning === JaneW [n=JaneW@dsl-146-154-109.telkomadsl.co.za] has joined #ubuntu-kernel [06:16] uh?= [06:16] what noise? [06:16] when? [06:17] wth is he talking about? [06:18] No idea [06:18] neither do i [06:20] sorry guys, that was probably my fault [06:20] I don't think Sven can ever be anyone else's fault [06:21] the fact that he's re-evaluating ubuntu-kernel, that is [06:21] heh [06:21] Have you kicked him off debian-kernel yet? [06:22] no, i just angered him. i intend to get him ejected from the project completely. [06:22] dilinger: LOL [06:27] fabbione: btw, you have any pointers to architecture/design of ocfs2? [06:27] dilinger: the code? [06:28] it's the "usual" clustered FS [06:28] all transactions needs to go trough the DLM [06:28] it's journaled like ext3 (same backend) [06:29] fabbione: a coworker's evaluating cluster filesystems (pvfs2, gfs, ocfs2, etc).. i had was hoping for something to pass along for him to read [06:29] since he can't seem to find details about ocfs2 [06:29] dilinger: you can check on oss.oracle.com [06:29] the project is hosted there [06:29] but the concept behind each clusterFS is the same [06:30] and that's where the real power of FS comes frok [06:30] from [06:30] the Distributed Lock Manager [06:30] performance of the FS are highly dependent on that [06:31] also.. ocfs2 is the simplest one around.. at least that i have seen [06:31] it's really basic clustering [06:31] a more complete suite is the GFS/RH cluster [06:33] fabbione: simplest in terms of implementation? features? [06:34] features [06:35] in my experience: [06:35] - ocfs2 is faster, but needs more manual tuning to handle the timeouts between nodes properly. It does "only" cluster FS [06:36] - gfs/rh cluster suire is generally slower, no need of manual tuning, it offers a complete suite for clustering, from shared IP, switching services, etc. [06:49] ok, thanks [06:53] damn, I missed sven and his FUD === CataEnry [n=cataenry@host83-39.pool8248.interbusiness.it] has joined #ubuntu-kernel [08:10] dilinger: Lustre might be interesting for him to take a look at too; http://www.clusterfs.com/ [08:12] yep [08:12] i've been following lustre development ever since the clusterfs people abandonded intermezzo [08:13] would be nice to see it in Ubuntu :-) [08:13] yea [08:13] i was going to package it for debian ages ago [08:13] but decided not to based on their release policy [08:14] they've changed it since, but i haven't had time to look at it again [08:14] i may still package it [08:14] i think mrvn took over my ITP [08:14] a co-worker did a quick-a-dirty package of it last week [08:14] not sure how far he got though [08:15] i'd be interested in seeing it [08:15] like i said, my coworker's evaluating different cluster filesystems; if we decide to go w/ lustre, i'll probably end up maintaining packages [08:15] quick-and-dirty packages makes it that much easier for him to try out [08:17] he is on vacation this week, but if you send me a mail (otherwise I will forget it) I can ask him to get in touch with you === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-kernel [08:20] BenC: Around? [08:29] jbailey: yeah === trappist [i=trappist@tra.ppi.st] has left #ubuntu-kernel [] [08:39] BenC: Are you packaging newer kernels at all for testing? [08:40] I thought I saw some reports of some threading stuff fixed in newer kernels. If you've already got a set built, I might poke my head into them. [08:40] threading and signals. [08:40] jbailey: haven't had a chance to start merging to newer kernels yet [08:40] No worries. I'll try to remember how to build one myself for the test. [08:41] None of it's a regression from previous, but on some arches there are weird nptl responses and such. [08:41] jbailey: jumping from .15 to .16 is a big step due to all the mutex changes [08:42] merging back is difficul [08:42] +t [08:42] fabbione: Right, I'm not expecting to backport anything, more just curious if these are the problems refered to. [08:42] fabbione: I'm trying to figure out what the path to actually getting clean glibc results is. === torkel [i=torkel@69-188.umenet.t3.se] has joined #ubuntu-kernel === _fs [i=fs@213.178.77.98] has joined #ubuntu-kernel === mxpxpod [n=BryanFor@unaffiliated/mxpxpod] has joined #ubuntu-kernel === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-kernel === mkrufky [n=mk@68.160.103.77] has joined #ubuntu-kernel === sevrin [n=sevrin@202.75.186.154] has joined #ubuntu-kernel === infinity [n=adconrad@loki.0c3.net] has joined #ubuntu-kernel === mjg59 [n=mjg59@cavan.codon.org.uk] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-kernel === mkrufky [n=mk@68.160.103.77] has joined #ubuntu-kernel === sevrin [n=sevrin@202.75.186.154] has joined #ubuntu-kernel === infinity [n=adconrad@loki.0c3.net] has joined #ubuntu-kernel === mjg59 [n=mjg59@cavan.codon.org.uk] has joined #ubuntu-kernel === _fs is now known as fs === infinity [n=adconrad@loki.0c3.net] has joined #ubuntu-kernel === CataEnry [n=cataenry@host83-39.pool8248.interbusiness.it] has joined #ubuntu-kernel === bronson [n=bronson@pool-71-243-85-238.bos.east.verizon.net] has joined #ubuntu-kernel [11:17] Anybody here able to boot in recovery mode? [11:17] Regular mode works fine. [11:17] Recovery mode kernel panics pretty early on. [11:18] Dunno when this started... I don't go into recovery much. [11:18] Just wondering if this is a me-only thing, or are other people seeing it too? [11:18] (dapper, upgraded last night) === crimsun [i=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-kernel