=== k-s is now known as k-s[AWAY] === k-s[AWAY] is now known as k-s === k-s is now known as k-s[AWAY] [09:17] Will there be another kernel upload today or is the current one aimed at release? === `6og is now known as Kamping_Kaiser === asac_ is now known as asac [11:41] hi,did anybody manage to compile 2.6.30rc1 from u git [11:43] nvidia dkms failes with latest 2.6.30 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ === k-s[AWAY] is now known as k-s === _Purple_ is now known as _Purple_away === _Purple_away is now known as _Purple_ === thunderstruck is now known as gnomefreak === k-s is now known as k-s[AWAY] === k-s[AWAY] is now known as k-s === k-s is now known as k-s[AWAY] === thunderstruck is now known as gnomefreak === k-s[AWAY] is now known as k-s === k-s is now known as k-s[AWAY] [15:36] apw, can you please comment on https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/280669; I tested your DMA patch for the jax10 with bonnie++, but I don't seem to get any better performance [15:36] Malone bug 280669 in linux "DMA mode and driver jax10" [Low,Triaged] [15:37] NCommander, so if its not of benefit we don't need it then? [15:38] apw, that was my conclusion since bonnie++ only shoed a minor change (likely noise) [15:47] apw, As we were asked today about the hibernate prevention. I could propose a change that inhibits hibernation if that file is present. There would be two questions, though [15:47] a) It doesn't seem that file is automatically removed on reboot [15:47] smb_tp_, yeah looking at it right now as it happens [15:48] b) Is there a way to be more obvious than just not doing anything [15:48] there is lots of places which know how to do it. in theory desktop stuff should can implement it [15:48] i have been playing with using notify to show the inhibit as well [15:48] let me play for a bit [15:48] My approach was a hook in /usr/lib/pm-utils/sleep.d which call inhibit on fail [15:49] yeah. thats what i have been doing as the 'last fallback' was looking to see what we could do higher up too [15:49] /var/run gets wiped on reboot does it not? [15:49] Thinks... [15:50] Oh could be. Gosh, I always hibernated when things did not work correctly, so the file is there naturally. [15:50] forget a) then [15:50] right ... stilll looking at gnome-power-manager to see if tis easy to tell it too [15:51] it hink there is an official interface for desktop in general [15:51] but ... step one is to do it in pm utils so it works for everything [15:51] That would be a good thing [15:51] so ... i am working on it [15:52] Ok, then I leave it to you. I thought I might help as you actually should sleep, get breakfast and other stuff... [15:53] smb_tp_, who needs sleep [15:53] I usually do [15:53] :) === JayFo is now known as JFo [17:32] smb_tp_, one of the changes I made fixed the resume issue... but now I dont know which one :) [17:33] manjo, Well, proper solution there would be to take out one change after the other and retest. ;-) [17:34] :) heh that is what I am doing ... stupid me.. was working from the same tree all along [17:35] On the good side the number of changes you did is likely not too vast [17:35] no like 3 changes [17:48] manjo: fyi there's a patch available for the java crash [17:48] jbarnes, cool! [17:48] do u have a ppa that I can test ? [17:48] it really works around the core issue (server bug) but it works for me [17:49] manjo: bryce provided one... lemme get the url [17:49] ok [17:49] oh he didn't give a url, just said it was in his personal ppa [17:50] let me ping him [18:01] jbarnes, no responds from bryce ... [18:02] doesn't launchpad give you access to his ppa? [18:02] looking .. [18:04] all I see is a change in status from Triaged to In Progress... [18:05] waiting for bryce to respond .. will let you know what I find .. [18:09] ok [18:15] manjo: ping [18:15] pong [18:16] manjo, i'm adding a driver config (mvsas) [18:16] manjo, in the modules files in d-i what is the significance of the ? in the files? [18:17] which file is that ? [18:17] manjo, d-i/modules/scsi-modules [18:18] manjo, if you look at d-i/modules/fb-modules the lines don't have a ? after the driver === k-s[AWAY] is now known as k-s [18:25] bradf, dont know what that means... some have ? others dont ... [18:26] manjo: yup, that's why I was asking [18:26] bradf, something to do with python parser ? [18:27] majo, how do those files get used? [18:28] I think the debian-installer does some magic [18:28] I think it generates a dsc file from that list [18:28] they're used in debian/rules (around line 98) to exclude modules on a per-arch basis - the names can have shell glob expansions [18:30] IntuitiveNipple, so ? is unwanted ? [18:30] coz I dont see any regex for looking for ? [18:31] manjo: not sure on that; but that is how it is used (the final expansion is done with the "xargs rm -f") [18:32] hmm pure magic [18:59] bradf, ? disables the module [18:59] bradf, debian kernel wedge does some magic to take that out [18:59] mvsas in debian is under scsi-extra-modules [19:00] bradf, so adding mvsas without ? enables it for d-i [19:01] bradf, gen-control does some magic [19:02] manjo, thanks [19:03] manjo, might have pulled the trigger a little soon on my patch, sigh [19:04] heh u did not tst it ! [19:04] http://kmuto.jp/svn/d-i/etch/d-i/packages/kernel/kernel-wedge/commands/ [19:05] manjo, built it, don't have the hardware that matches the module [19:05] ah someone will report that it does not or does work ... u can fix then I guess [19:06] bradf, I posted the link with the commands that looks at those files ... you can look at the perl scripts and guess if that is exatcly what It dos [19:07] manjo, thanks, am looking at it now [19:07] debian builds are just magic... I am glad I dont have to mess with it [19:08] * manjo goes back to regular scheduled program of debugging [19:16] manjo, according to rtg: A '?' implies the module is optional, e.g., if it doesn't exist for a [19:16] particular config then its not an error. [19:17] ic === Keybuk_ is now known as Keybuk === Omegamoon is now known as Omegamoon|party === Omegamoon|party is now known as Omegamoon [22:14] Hi [22:17] Since a few weeks my filesystem is corrupting all the time. I'm on Jaunty (this first happened with ext3 so I thought it was a problem with it but from then on I've reinstalled Jaunty several times choosing ext2 and it still happens). Any idea? [22:21] (all the time = usually once a day or more often. I'll power off and when I start the PC again it'll run a fsck because of not being umounted properly and find lots of errors which it asks me to repair manually, or sometimes even grub will directly refuse to boot and I'll have to fsck from a live CD. Sometimes it even corrupts while I'm using it and / switches to read-only, and after a while fails completely and gives "read errors", also getting fixe [22:22] May this be because of the kernel or is it a hardware fault (which I doubt as the hard disk isn't even 5 months old)? [22:27] are updates involved at any step? [22:28] dtchen: Afaics no, but the lowest I've tried is plain Jaunty Alpha 5. [22:28] also, is this "plain ext3", or is it "ext3 on LVM", "ext3 on encrypted LVM", etc.? [22:29] plain ext3 [22:29] (err above in my first sentence ext3=ext4, ext2=ext3) [22:30] interesting. i cannot reproduce the symptom across fresh boots, but i can across week-long suspend-to-ram/resume cycles. [22:30] it's reproducible for me on plain ext3, ext3 on LVM, and ext3 on encrypted LVM [22:30] (however, i'm also using wl and nvidia, so who the heck knows?) [22:31] I'm downloading Lenny now, will see if it fails there too. (I've decided this is a signal for my to finally try out Debian :P). [22:32] i don't think it's Ubuntu's kernel, per se. i remember the first time i had a trashed jaunty install was while running the kernel-ppa mainline build of 2.6.29-rc5. [22:33] RainCT: when you say the FS is corrupting [22:33] arg [22:33] data loss, or fsck triggers? [22:33] (sorry, damn Ethernet cable :P) [22:33] RainCT: when you say FS is corrupting, do you mean data loss, or fsck triggers? [22:34] pwnguin: both, although usually the data loss is not serious [22:35] and you power off normally? [22:35] Yes [22:35] For some time there was some message before it powered off (if I booted without "quiet splash") [22:36] "could not iterate IDE devices" or something like that (I'm telling from memory from several days ago) [22:36] is there any raid involved? [22:36] nope [22:37] how old is the drive and whatever it plugs into? [22:38] It's a laptop, less than 5 months old, partitions: sda1 (ext3, /) and in an extended partition sda6 (ext3, /home) and sda5 (swap); both sda1 and sda6 have the problem [22:38] (I've reinstalled and recreated the partitions several times, btw) [22:39] (that's the exact error it gave: «unable to iterate IDE devices: no such files or directory») [22:40] by chance, do you have diagnostic cds or partitions? [22:40] RainCT: Has the laptop taken any unexpected knocks around the time this started? [22:40] (ah, gparted says the hard disk is an ATA TOSHIBA MK2552GS) [22:41] If it were a desktop I'd immediately say "check the cables" - as a laptop I'd say, have you opened the HD access panel and checked the SATA connection and drive are secure [22:41] and no, I haven't moved it much this last months [22:42] and no, I haven't opened it, and I can't (or warranty voids) [22:42] it sounds hardware related, so I'd be suspecting something loose or out of place or shorting or overheating [22:42] have you searched LP for your laptop model? [22:43] it sounds like a hardware thing, and if your model is susceptible, that might be an avenue to pursue [22:44] a google search with the model + launchpad only shows webcam support related stuff [22:44] you might also check smart for anything [22:45] smart says "passed", if there's anything else I can ask smart to do I'd need to know the command for that [22:46] (smartctl, that is) [22:50] hmm, yeah, too late for HDA enablements fixes for HP Minis [22:50] i'll queue these for -proposed === k-s is now known as k-s[AWAY] === lifeless_ is now known as lifeless === jbarnes is now known as j === j is now known as jbarnes