[03:49] Does anyone know where the sata-sil24 driver can be found in the Karmic kernels? [03:49] I can only find it in the -ec2 kernel === sconklin is now known as sconklin-gone [12:30] good morning [12:35] Good morning BenC [13:13] howdy! could someone tell me what was the URL to Ubuntu packages of vanilla kernels? [13:14] Q-FUNK, http://kernel.ubuntu.com/~kernel-ppa/mainline/ [13:15] tgardner: thanks! [13:19] bouncy tgardner [13:19] apw, at least mine rebooted OK [13:20] maybe that is why keybuk is missing, he can't boot [13:20] This time it rebooted as well [13:20] smb, hrm ... not another race [13:21] I should go back and retry the Tylersburg with bind mounts. Its pretty much guaranteed to hang. [13:25] apw, Gah, and it would be nice if this would not always put sda6 into mtab when I am on sda8 [13:25] hrm [13:25] ericm_: wrong list [13:36] apw, Ok, at least that strangeness is solved. It does not matter what uuid you have in fstab for root as long as the grub line is correct. But mtab will get confusing if you do [13:52] apw, Bringing up gfx seems to be racy. With plymouth it seems to get stuck at some point. Without I sometimes get text login and sometimes it wors [13:52] works [13:53] Hm, seems to be having the "enter" drop to gdm problem [14:06] apw, Are you aware of issues like "after suspend-resume, screen on i915 may go completely blank at random times" [14:06] smb, is this something you are seeing? [14:06] smb, does suspend/resume fix it [14:07] apw, or not seeing my contents, yes [14:07] smb is this an older i915 chipset ? [14:07] apw, Let me try after the upgrade I do over ssh is done [14:07] apw, likely [14:07] if all the above are yes ... then reboot with i915.powersave=0 and let me know if that fixes it [14:07] apw, Its the Aspire one [14:08] apw, Ack [14:08] akgraner is meant to be reporting back today as she was seeing randomness too and was trying powersave off for older kit ... ak ? [14:08] apw, I usually get a screen goes crazy for a few seconds warning slightly before [14:09] smb seen the same on my atom as well, think older less featureful i915 still needs powersave [14:09] apw, hey- yeah I need to figure out who to right it up? :-( without using words like the "thingy" the "watchchacallit" and such :-) [14:09] s/who/how :-) [14:09] Sarvatt, you were mentioning this i915.powersave=0 requirement for older i915 [14:10] but it only locked up once and I think it has to do with the mouse [14:10] Sarvatt, i think i was hoping for a bug from you with the 'whihc ones are still afected' boundary [14:10] akgraner, well thats a vast improvement over 25 times in a day ... so i think you qualify as fixed for the original bug with powersave=0 [14:10] * apw will hastle Sarvatt to find out if they know the split [14:10] apw, Is 945GME considered old? [14:11] apw - I am happy and it wasn't so locked up that I had to reboot that time [14:11] smb, i don't think its old in terms of age but older in terms of technology, lile 965 and newer powersave works and 945 and older does not ... but i don't have the exact boundary to add the switch [14:12] will hastle graphicy people to find out [14:12] apw, this is one time I am going to sit down with pgraner and reproduce this problem had seek some help from him on documenting this for you [14:13] akgraner, the powersave one? [14:13] apw, Ok, and I test here. Powersaving sounds quite reasonable. It seems to put contents up. Though backlight is still on (and gets affected by inactivity and typing) [14:13] I mean to put no contents up [14:13] apw, yep - I don't know how to file bugs without using apport and well it didn't work for this particular problem [14:14] smb, powersave at that level doesn't do anything visible, it down and up clocks the output dacs on activity in the framebuffer [14:14] akgraner, just find the +filebug link and file it manually [14:14] just say "i915: graphics hangs with i915.powersave=1 on some cards" [14:15] apw, Well powering down all clocks _is_ somewhat visible [14:15] and let me know the number [14:15] akgraner, http://bugs.launchpad.net/ubuntu/+filebug [14:15] smb, its not meant to turn them all off [14:15] tgardner, thanks :-) [14:15] apw, I'll do this now :-) [14:16] apw, If that helps anybody: [14:16] Interrupt enable: 00028c53 [14:16] Interrupt identity: 00000000 [14:16] Interrupt mask: fffd73ae [14:16] Pipe A stat: 00000000 [14:16] Pipe B stat: 80000302 [14:17] Interrupts received: 1009 [14:17] Current sequence: 3186277 [14:17] Waiter sequence: 0 [14:17] IRQ sequence: 3186019 [14:17] smb, if it stays like that thats a gpu hang [14:17] apw, It does [14:17] specifically the current and irq sequence numbers [14:18] then we need to get a GPU hang dump off it [14:18] and a bug, blah blah blah [14:19] I think waiter sequence 0 is not very good at all. Let me collect and if powersave fixes it put it there [14:36] smb ta [14:40] apw, I think I did this right :-) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539609 [14:40] Malone bug 539609 in linux "i915.powersave causes desk top to hang." [Undecided,New] [14:41] I wonder if powersave is what is killing my d420 [14:42] tgardner, the link you gave me redirects to this page - https://help.ubuntu.com/community/ReportingBugs - didn't know if you knew that or not :-) [14:42] [35198.621213] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [14:42] [35198.621232] render error detected, EIR: 0x00000000 [14:42] what link was it akgraner? [14:42] akgraner: do you get that in your kernel log at all? [14:43] akgraner, hmm, it doesn't do that for me. the Launchpad folks are making it really tough to submit a bug that doesn't conform to one of their categories [14:43] apw - for the can you reproduce this bug" - I put no, b/c the was no maybe button however I think I can. [14:44] JFo, http://bugs.launchpad.net/ubuntu/+filebug [14:44] akgraner, s'ok in this case as i know what the bug is and how to fix it, just need input from X on which cards are affected [14:44] heh, no maybe button... you kill me [14:45] BenC, is there a GUI for getting to the kernel log? [14:46] akgraner: I just did "dmesg" from a terminal [14:46] akgraner: also, /var/log/kern.log [14:47] BenC, not I don't seem to have that message [14:47] s/not/nope [14:48] BenC, For what its worth, I got that neither [14:48] JFo, well I think there should be a "maybe" and a "several times a day" button :-) [14:48] heh [14:49] JFo, but seeing as how I am just now learning how to file bugs - it might just be me :-) [14:54] smb, akgraner: Ok, guess I have a diff problem, but I'm going to test the powersave disable anyway :) [14:54] ## [14:54] ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting [14:54] ## agenda: https://wiki.ubuntu.com/KernelTeam/Meeting [14:54] ## [14:54] right now I've left it in low graphics mode and haven't had a lockup or resume failure in a few days [14:59] apw did you do an upgrade on your 10v today? [15:00] manjo, nope ... always risky around now [15:00] problems? [15:00] apw, after I upgrade and reboot I just got the logo spinning and no progress... [15:00] smb, sound like your issue? [15:00] apw, looks like my root was mounted readonly and I had a ton of uread ahead messages [15:00] Yeah could be [15:01] my 10v has ssd [15:01] manjo, Does pressing "s" help? [15:01] smb, trying again [15:02] now its searching for disk errors ... I will let it complete .. [15:03] * BenC plays the wait-and-see game now [15:05] hmmm disk check is taking for ever at 73% [15:08] heh BenC do what i am doing, wait till smb et al stop whining :) [15:08] ok missive on built-in modules on the kernel-team list ... [15:08] ok missive on built-in modules on the kernel-team list ... [15:09] * tgardner suspects apw is mumbling to himself out load again. [15:09] apw, ? [15:10] won't be the first time either [15:10] cking, tgardner Guess he wanted to draw some attention to some mail [15:13] hehe [15:26] apw, how come we are reviewing this now ? [15:27] apw, Keybuk Seems there is something still not quite right with plymouth. I get see the splash screen turn to one with the 4 dots lightened and then have a crash report for plymouthd and a daemon I cannot kill together with X running. I was able to kill X, this caused the plymouthd to end and gdm to start [15:29] At that point in time I could ssh in, but mouse and keyboard locally were not responding [15:29] smb: got the crash report? [15:29] a segfault of plymouth tends to be quite catastrophic thanks to this bit of the kernel being written by spastics [15:29] Keybuk, Its still there [15:33] "it" ? [15:34] Keybuk, Uploading, just a sec [15:41] Keybuk, It is bug 539655 [15:41] Malone bug 539655 in plymouth "Boot screen locks up while X starts" [Undecided,New] https://launchpad.net/bugs/539655 [15:44] you see all four dots fill? [15:44] does it jump to all four dots? [15:44] Keybuk, yes [15:44] ok [15:44] that means X should be starting [15:45] Keybuk, It was running [15:45] Just not displayed [15:45] you said there was a segfault? [15:45] Keybuk, maybe not correctly stated. I meant the report in /var/crash [15:45] that's unrelated [15:46] you're on Ubuntu not Kubuntu right? [15:46] Right [15:46] When I logged in plymouthd was in state D [15:46] But ssh login works and shows a plymoutd process (in state D), the call to stop it and an X process running. [15:47] .. [15:47] could you attach this "ps" output to the bug [15:47] also I don't suppose you could gdb attach to plymouthd and get a backtrace? [15:47] Let me try whether it gets into the same state again. [15:48] Those things tend to go away when one looks too close [15:49] Grr, disk check [15:49] Hm, seems the similar fate. [15:49] Goes to 70% and then there is a flicker [15:50] Then it comes back with 70% but stops moving [15:53] Keybuk, Hm, not using gdb too often... How would I break to a gdb command line after attaching to the process [15:54] does it not break? [15:54] ooh, kernel bug [15:54] strace instead of gdb? [15:54] No it just tells me attached to process x and stays there [15:54] Keybuk, I see the same issue [15:54] I don't think it will show much as it seems to be stuck [15:54] yikes [15:54] right, it's stuck in a syscall [15:54] which syscall? [15:55] init: plymouth main process (318) killed by SEGV signal [15:55] manjo: can you get that segfault? [15:55] Keybuk, trying ... I tried to switch VT and it seems to be frozen ... restarting [15:56] yes, you'll need to ssh in etc [15:58] s**t looks like I messed up my filesyste ... now I cannot seem to mount my / [15:59] manjo: I've done that about twice a day for the last two weeks :p [16:00] Keybuk, strace seems to lockup too, but maybe /proc/x/wchan = nouveau_gem_ioctl_cpu_fini helps? [16:01] Keybuk, how did you manage to fix ? I don't seem to be able to fsck it ... tried init=/bin/bash and fsck but does not fix [16:02] Xorg restarting randomly is a painful experience [16:03] manjo: oh, I just blast and reinstall the machines [16:03] heh! [16:03] smb: oh, yes, that helps :D [16:03] smb: that helps a lot [16:04] Keybuk, Likely you can now point at the kernel :-P [16:04] oh yes [16:04] that's a card hang [16:04] iirc [16:04] it's waiting for a command response from the gpu I think [16:04] Keybuk, Well not completely [16:05] As I can kill -9 X and then everything works [16:05] yeah it's X that's hanging here not plymouth afaict [16:05] if you see all four dots, plymouth is gone [16:06] well, other than waiting to close the drm connection once X has it [16:06] if X hangs, plymouth will just be waiting for X to go [16:07] Seems plymouthd waits for some final drm response while X already started up somewhat but the screen rendered is the plymouth screen and keys seem to go not to X as well [16:07] no, not that I know of [16:08] plymouth is just trying to close the drm file descriptor [16:08] actually [16:08] sorry [16:08] I'm talking crap [16:08] you're on nouveau [16:08] you have just one monitor right? [16:09] right [16:09] so there should be no DRM involved here [16:09] I'll have to check the code in a sec, but I'm pretty sure plymouth just uses the frame-buffer renderer on single-monitor nouveau [16:09] plymouth doesn't really like GEM [16:09] plymouth is pretty damn picky [16:10] Keybuk, OK, and I attach the ps-ax and wchan info to the bug for completeness [16:10] please [16:10] apw: not really, GEM is pretty crappy to program [16:10] it's harder than just writing to the frame buffer [16:10] and slower [16:10] so on GEM drivers, plymouth writes to the frame buffer [16:10] unless you have multi-head, in which case it grudgingly deals with GEM so it can use each native resolution [16:10] oh, right [16:11] and there's no way to do the "leave what I just had on the screen" with GEM [16:11] so you always get a black screen [16:11] (that's probably half of the reason it avoids GEM actually) [16:11] ahh ... i found external screens even on intel sucked with plymouth [16:11] triggering all sorts of resolution changes [16:11] huh [16:11] that shouldn't be the case [16:12] Intel is TTM [16:12] Plymouth likes TTM [16:12] plymouth did nice things, purple on main, and black on external (with the logo) [16:12] huh [16:12] it's supposed to be purple on each [16:12] and then gdm got pissed off and reset the resolution and mirrored t [16:12] each in their native resolution [16:12] logo centered on each [16:12] oh, maybe gdm sucks ;) [16:12] to both ... and then on login it switched back [16:12] plymouth is doing pure DRM + FB [16:13] so it's more like wayland than X [16:13] i couldn't see purple under the external screen logs [16:13] logo [16:13] neat test of plymouth multi-head [16:13] Keybuk, oh i did wonder on the purple background, could it be made to stop one 'character' from each side? [16:13] while running X : [16:13] sudo plymouthd; sudo plymouth --show-splash [16:14] to avoid the cursor cuttting holdes in it [16:14] apw: you shouldn't see the cursor [16:14] Keybuk, that didn't work at all well [16:14] apw: what version of plymouth are you running? [16:15] ii plymouth 0.8.0~-12 graphical boot animation and logger - main p [16:15] i got both the splashes on my left monitor, at about 1/4 natural resolution [16:15] eeeeeep [16:15] yeah don't run that on that version of plymouth ;) [16:15] right, that's what you should see - it just makes two X windows of different sizes to test that themes scale and centre properly [16:16] anyway your plymouth is awy out of date [16:16] you have the buggy crap plymouth [16:16] oh ok then it worked :) [16:16] unfortunately, you're about to lose your X server [16:16] :D [16:16] i have a plymouth thats is sufficinetly old that boot works for me [16:16] no, you have the one before I fixed it all [16:16] it always generally worked on intel though [16:16] i am waiting for smb to stop whining his boot doesn't work at all with your new stuff [16:16] before i install it :) [16:16] from the sound of it, smb's problem is nouveau related [16:17] :-P [16:17] talking of nouveau [16:17] I have a laptop here with an nvidia card in it [16:17] how do I install? [16:17] yep, ... [16:17] nouveau is default [16:17] yes [16:17] either it works or it doesn't [16:17] and I get a screen full of crap and corruption [16:18] Sounds my last ati install [16:18] noodeset help at all? [16:18] nomodeset ? [16:18] how do I add that now we don't have a boot menu? [16:18] Keybuk, now you'd have to ask someone in foundations about that :) [16:18] :D [16:18] There is one if you press escape [16:18] hold shift i assume? [16:19] oh hrm a different button? most unintuitive [16:19] this is on the installer - SYSLINUX :p [16:19] gurgle [16:19] beep [16:19] * Keybuk changes the config on the USB key :p [16:19] your call could not be connected at this time [16:19] though it sounds like ESC is worth a shot, i suspect smb has been using it a lot [16:19] While doing the kvm tests, yes [16:20] The picture you see is very much _not_ intuitive [16:20] does nouveau work on *anything* ? [16:20] Keybuk, and where is my x-server going? [16:20] apw: well, when you get bored and run "sudo plymouth quit" [16:20] Keybuk, i have been told by bryceh yes [16:20] apw: save your work first [16:20] really? [16:20] Speaking of intuitivity, the [SM] on mountall is another example :-P [16:20] because I have two nvidia machines [16:20] Keybuk, oh i went for killall plymouthd, seemed to work [16:20] and I have never seen nouveau work :p [16:20] apw: ah ;P [16:20] apw: you might be lucky there [16:21] seems i was lucky :) [16:21] Keybuk, It worked before todays update [16:21] smb: mountall likes pain [16:21] bryceh, hey ... where are our testing results for Nouveau [16:21] i am sure we have some around here somewhere [16:21] fortunately these machines are all Dells [16:21] and we don't have any kind of relationship with Dell [16:21] sadly i have nothing but intel h/w so i cannot test myself [16:21] Keybuk, And it works mostly when I disable plymouth. *grrr* [16:21] and Dell would never ship an NVIDIA card or chip anyway [16:21] [16:22] Keybuk, i soooooo wish [16:22] need to know if nomodeset works on them if modeset does not [16:22] and if so we need to record that and blacklist them [16:22] have patches to allow blacklisting, just no list of black [16:22] smb: does it work if you remove "splash" from the cmdline? [16:23] hmm... with the latest nouveau bits from the ppa, the boot hangs at the plymouth splash screen, just before switching to gdm [16:23] booting without splash works [16:23] someone else on #u-x bitching about something changing [16:23] meh [16:23] I really need some hardware for this [16:23] Keybuk, Yes, well mostly, sometimes X does not start, but other times it does [16:23] *all* of our reported problems are nvidia now [16:23] as nouveau hasn't changes for ages... i suspect that there is something else at work here [16:23] smb, yours worked until today right? [16:23] yesterday and the day before? [16:23] Right [16:24] and the kernel has not changed [16:24] But I cannot say when my last update was [16:24] until today ?! [16:24] so ... whatever it is its not the nouveau driver [16:24] smb, your logs will tell you when yo last updated before that [16:24] and see if the kernel changed in the pile [16:24] /var/log/dpkg.log ftw [16:24] also see if plymouth or X changed [16:24] But at least I had either your franken kernel or -16 [16:24] or gdm for that metter [16:26] apw, Keybuk Seems at least linux-image-2.6.32-16.25 was installed today as well. [16:27] smb what did you have before kernel wise [16:27] grep "update linux-image" /var/log/dpkg.log [16:27] err [16:27] grep "upgrade linux-image" /var/log/dpkg.log [16:29] That seems to be the meta package numbers... [16:29] upgrade linux-image-generic 2.6.32.15.16 2.6.32.16.17 [16:30] Strangely dpkg -l tells me -15.22 was last but I am pretty sure I did apw's preview kernels there for testing [16:31] was that with the nouveau backport? [16:31] as in with LBM [16:31] Once with LBM, but also your drmbackport version in kernel [16:32] But that package were -15.21~xxx [16:32] so got replaced in between [16:32] smb, ahh yes would have [16:35] so nouveau was changed today [16:35] and things started breaking today? :p [16:35] Keybuk, I had the same version of nouveau before. Just as a testing kernel. [16:38] Keybuk, But to be honest, plymouth was turned of before because of the press enter to die bug on 64bit. I turned it back on as there was a problem that looked like mountall waiting for something but not telling issue [16:39] *sigh* [16:39] Some days you forget where you started because every step takes you to another issue [16:39] yes, I understand :-/ [16:39] but this is a problem we really need to fix [16:39] it's a bit disheartening actually [16:39] I have a large pile of hardware here [16:40] and the only machines that can boot right now are the Intel ones [16:40] (pure Intel) [16:40] Intel with ATI graphics => won't boot [16:40] Intel with NVIDIA graphics => won't boot [16:40] AMD64 with NVIDIA graphics => won't boot [16:40] etc. [16:40] from my, admittedly limited, testing pool, I've come to the conclusion that this will be our worst release ever for hardware support [16:41] Probably we need to find out whether it needs a step back and not have splash for anything than intel helps [16:41] karmic wasn't too good either. [16:42] Q-FUNK: karmic at least works on all of the machines here [16:42] smb: but it isn't just splash [16:42] like this one I'm trying to install right now [16:42] Dell Latitude D620 [16:42] Keybuk: not here. [16:42] this is pretty much one of our bread-and-butter machines [16:42] Keybuk, my D620 is working fine [16:42] a lot of us have Dell Latitude Dx[23]0 [16:43] JFo: with nvidia or intel graphics? [16:43] but then I did an upgrade [16:43] nvidia [16:43] it works with modeset? [16:43] is is exactly as installed [16:43] because all I got when trying to boot today's daily was a corrupt screen [16:43] I have made no boot mods [16:43] modeset=0 seems to work, but with the wrong resolutions [16:44] Keybuk, let me reboot and I will let you know if today's update causes any problems [16:44] brb... either here or on my mini [16:45] ## [16:45] ## Ubuntu Kernel Team Meeting - in 15 minutes - #ubuntu-meeting [16:45] ## [16:47] Keybuk, the only issue I am seeing is that the font for the splash is not correct [16:47] it isn't the new style [16:47] font? [16:48] yeah, the new looking ubuntu font [16:48] what font? :p [16:48] heh [16:48] could you describe the splash screen for me? [16:48] :-P [16:48] it is purple [16:48] [16:48] :) [16:48] and what does it have written on it? [16:48] Ubuntu 10.04 [16:48]