[00:19] jbarnes: "current sequence" does not seem to be incrementnig [00:19] bryce: ok just wanted to make extra sure the gpu was hung [00:19] albert23's last dump shows that we started executing junk [00:21] I've waited a couple hours since the freeze, and no files in /sys/kernel/debug/dri/0 have changed [04:12] bryce_: what's the purpose exactly, of adding lspci entries to the bug descrption? [04:34] pwnguin: needed for upstreaming the bug [05:53] Caesar: yes? [06:42] tjaalton: libxcb [06:42] We're seeing problems with it in Hardy [06:43] On amd64 [06:43] Both the 64-bit version and what's in ia32-libs [06:44] Apparently the problems went away when I rebuilt the ia32-libs version without optimisation [06:44] Make of that what you will [06:44] I haven't tried making a non-optimised 64-bit version yet to see if that solves the other problems [06:44] I was wondering if you had any thoughts on the whole situation? There's been one or two libxcb-related bugs bouncing around I think [06:49] Caesar: which ones? [06:49] and what problems? [06:51] tjaalton: various crashes [06:51] I'm not VPNed into work at the moment, so I can't check our bug tracking system [06:52] ok, are they on lp too? [06:53] I'd be interested to know if they happen on jaunty too [06:53] since we're going to be fully 64bit in a few months ;) [06:53] I know that there used to be some java issues [06:53] but java was fixed since [06:54] and so was libxcb, so that it can't fail the same way anymore [06:54] java was one of the problematic things [06:55] Let me see which lp bugs we're subscribed to [06:58] So there's #220628 [06:58] and #232364 is less pressing [06:59] I'd have to doublecheck what we've got internally tomorrow [06:59] sure [07:00] so there's a patch for the former.. have you tried backporting it? [07:01] Not yet [07:01] I've still been trying to wrap my head around all of the issues [07:01] think I've seen this bug myself, good to know there's a fix :) [07:01] Actually, let me search my email, that should turn up something useful [07:03] I'll be moving the next week or so, which means I'm unable to work on it before early May perhaps, but I'll keep an eye on it because it seems important [07:04] Yeah, it seems to be fairly important [07:05] I think we did a backport of that patch for a single user to see how it worked out for them [07:05] Firefox still seemed to crash, just less [07:05] I'll assign myself to the bug [07:06] I had someone look at some other crashes, and he said: [07:06] I can't see how $EBX is meant to be maintained. The generated code looks optimised (non static functions have been inlined). This feels like an optimization bug. [07:06] (that was for the ia32-libs version) [07:06] So I went and rebuilt it without optimisation [07:06] and that seemed to fix the problem [07:07] So something's very wrong if just changing the optimisation level fixes the problem [07:07] that was some other bug? [07:12] Yeah [07:12] It's very internal, so it's hard to file a meaningful lp bug [07:13] heh, ok [07:14] could that be a compiler bug? [07:14] I guess it could be [07:14] talk to doko about it [07:14] he might have ideas [07:14] ok [10:03] Hi there, I have Xorg crashing on "first reboot" after installing jaunty. It worked for months, but the latest version of X works only on first boot, that's very strange. Perhaps related to kernel. It's bug #364488 [10:03] Launchpad bug 364488 in ubuntu "After some day of installation, Xorg won't start anymore (black screen and locked keyboard)" [Undecided,New] https://launchpad.net/bugs/364488 [10:23] tjaalton: i switched the package to xorg on this bug (not wacom) --> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/364488 [10:23] Launchpad bug 364488 in xorg "After some day of installation, Xorg won't start anymore (black screen and locked keyboard)" [Undecided,New] [10:23] tjaalton: or why did you set wacom-tools on it? [10:24] mnemo: because it's likely a dupe of another bug (can't find it now) [10:25] aaah ok [10:26] does wacom-tools request xorg.log etc just like xorg does when you run the apport-collect thing? [10:26] not necessarily a wacom bug, could be in the xserver [10:26] yes [10:26] ok would you like me to change it back to wacom-tools then? [10:26] yes [10:26] will do [10:26] thanks [10:27] tjaalton: btw, I have wacom HW [10:30] mnemo: ok, you could check bug 358643 and see if you can reproduce the issues [10:30] Launchpad bug 358643 in wacom-tools "Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()" [Medium,Confirmed] https://launchpad.net/bugs/358643 [10:30] sure [10:31] there are also proposed fixes, and I've yet to grok the reply from gomyhr [10:34] its my gf's wacom actually so I never tried it in ubuntu before.... anyway now when I connected it, things just worked out of the box... [10:34] like I got this in dmesg --> http://pastebin.com/m1124224 [10:34] and I can move around the mouse cursor at least [10:34] no special xorg.conf [10:35] right, it works if you _don't_ have anything in the conffile [10:35] but I'm worried about the people upgrading :) [10:36] it'll be mentioned on the release notes though [10:36] but an SRU would be nice [10:36] right.. [10:36] anyway, lunch -> [10:36] yea [10:36] cya [11:12] tseliot: have you had time to prepare the new stable nvidia for testing? [11:12] tjaalton: I prepared and I'm using 180.51 but I think it's still a prerelease [11:13] http://www.nvnews.net/vbulletin/showthread.php?t=122606 [11:13] Current official release: 180.44 (x86 / x86_64) [11:13] Current prerelease: 180.51 [11:13] Current beta release: 185.19 [11:14] ah [11:14] ok [11:14] no regressions so far [11:15] we might do an SRU when the stable version is released [11:15] right [11:15] I should probably test the gf9600gt's a bit more [11:15] we'll be getting a 100 of those :/ [11:16] unfortunately I don't own one [11:45] jbarnes, hi ... trying to get a handle on the tiling performance issues associated with MCHBAR, and wondering what happened with the patch 'allocate MCHBAR space & enable if necessary', i think i remember there being a replacement proposed but cannot find it === rickspencer31 is now known as rickspencer3 [13:18] hmm, x hung [13:19] i shouldnt have hacked out the blacklist ;) [13:19] is there anything i can quickly do to get debugging before i have to reboot? [13:21] i have a quick gdb bt [13:21] Ng: do you have all the bits (2.6.30 + patched i915.ko, the reg-dumper= [13:22] no, stock jaunty [13:22] ok [13:23] gah. i have to reboot npw [13:39] so obviously I'm behind on all the debugging/testing things I should be doing [14:07] An acquaintance of mine just ran update-manager to do the intrepid->jaunty upgrade and it told him that there wasn't an fglrx driver for his card. It's an x1400. Is that accurate? [14:09] If it is, he'll be moved to the free driver, right? I'm told they don't support 3D acceleration. [14:09] If that's indeed the case, the upgrade will mean he'll lose 3D capabilities. However, I don't see any mention of anything like this in the release notes? [14:09] soren: what is the pci id of this card (the x1400) ? [14:09] mvo: I'll check. [14:10] soren: I doN't think he will loose 3d acceleration, but it may be less well supported, iirc the x1400 is a r500 based card and the 3d support for the free driver is pretty solid there [14:10] (compiz should run just fine, not sure about more advanced stuff like real games) [14:16] mvo: 1002:7145 [14:20] soren: from the modaliases it looks like this is indeed just r600+ support now [14:20] fglrx, you mean? [14:21] So he'll be automatically switched to the free driver? That's the one called "radeon", is it? [14:21] soren: yes - and http://www.x.org/wiki/RadeonFeature looks pretty good for the r500 [14:21] mvo: Fantastic. Thank you. [14:21] soren: let me know how the upgrade goes and if everything works as expected please [14:22] mvo: Still... I understand why he was startled by that message. Losing 3D would be a showstopper for lots of people, I think. [14:22] mvo: Will do. [14:23] are we could to put in such a message for i965? [14:24] soren: right. I understand. I'm not familiar enough with the free ati driver to judge how well the individual chips are supported, so I decided to go with the "conservative" message [14:24] Ng: only in a sru at this point [14:24] soren: the r5xx series has free 3D support [14:25] since intrepid [14:25] tjaalton: Cool. [14:26] I'm just passing the message on... He was rather concerned by the message, and the release notes don't mention anything about this. [14:26] mvo: fair enough [14:26] and r6/7xx will probably get it for the next release [14:27] Perhaps it's worth mentioning the transition in the release notes. [14:27] mvo: He's doing the upgrade later today and promised he'd get back to me with the results. I'll keep you posted :) [14:35] jcristau, tjaalton: is it "good enough" to not show a warning at all for all r5xx chips? [14:35] mvo: where's the full text? [14:36] http://paste.ubuntu.com/155350/ [14:39] I guess it could only worry people [14:40] although the text is technically correct :) [14:56] Hello, is there a way to disable the RandR extension of Xorg? [14:56] It conflicts with my fglrx driver from ATi (9.4) [14:56] mvo: for basic desktop (3D) usage it should be enough, and largely at least there is zero reduction in desktop effects. games do suffer until radeon-rewrite comes for karmic. [14:57] I've played stuff like Neverwinter Nights on my (former) Radeon X800 without problems, but things like Doom 3 do not work (yet) [14:58] Mirv: thanks! that is valauble information, so the warning is probably a good idea [14:58] mvo: warning, or just a release note about decreased game performance on R500 [14:58] Shappie__: that doesn't make sense [14:59] of course, there might indeed be a bunch of gamers using something like X1650-X1950, for them it's an important piece of information [14:59] jcristau: What you mean? When i type in terminal the command with sudo aticonfig to make dualscreen setup its says error due to RandR 1.2 enabled [14:59] You need the exact error? I have it somewhere... [15:00] but if using the warning message, just remove the "desktop effects, and " [15:00] Shappie__: shrug. i don't know what aticonfig is, so i probably couldn't help with it anyway. [16:19] apw: it's under "pnp: add PNP resource range checking function" on intel-gfx [16:19] apw: I split it in two because the pnp part needed to be generic [16:29] jbarnes, ahh thanks will look at it [17:02] jbarnes, i see that bjorn came back with an alternative generic check, did that get tested yet? [17:03] apw: no, do you have a test platform you could try it with? [17:03] you'd need to add an EXPORT_SYMBOL for it and a prototype [17:03] i have users who are upset its not working [17:03] should be easy to do though [17:03] so i suspect they would be willing to test anything, as their performance sucks without your fix [17:04] would be great to get some test results so we could push it upstream soon [17:11] morning [17:17] morning [17:31] bryce: did you see my last update to imad? [17:31] my mailer is giving me trouble, just want to make sure it went out [17:31] was in reply to mdz's comment [17:32] jbarnes: no emails from you for today in my inbox [17:33] just sent again... [17:45] jbarnes: anything else I could do to help you guys? [17:46] not atm I think [17:46] looking at albert's dumps now [20:28] tjaalton: I've updated https://wiki.ubuntu.com/X/Drivers to indicate the latest info for our main drivers, can you please review it when you get a chance, and add any other information that's worth including? [20:37] bryce: ^ beta version of xserver? [20:38] bryce: the -intel entry has a wrong version [20:38] good catches... updated [20:39] bryce: I'm a bit lost about wacom actually, there are some bugs suggesting that xsetwacom/wacomcpl doesn't work, but actually they do if the correct device name is used [20:39] but I've yet to confirm that [20:40] ok [20:40] tjaalton: don't forget to update the release notes if this is a known issue, esp. if there's a workaround people can use [20:41] bryce: I thought the sony panel problem was fixed? [20:42] jbarnes: might be, this known issue list is old (2.6.1-ish) [20:42] at least the linked bug is fixed :) [20:42] * jbarnes checks the commit id [20:43] bryce: I will take the crappy oem tablet with me tomorrow, so I can play with the patches [20:43] and update relnotes accordingly [20:43] bryce: yeah 2.6.3 has the sony panel fix so you can remove that bit [20:43] okies [20:44] tjaalton: awesome thanks [20:45] bryce: also, tv out properties and the sdvo tv stuff should be pretty easy to backport, you could ping yingying about getting that done maybe [20:52] bryce: re wiki: the link to fd.o 19274 is wrong [20:53] jbarnes: is that strictly -intel stuff or does it require kernel changes? [20:53] for non-kms they're just 2d driver updates [20:54] tormod: ok thanks, what should it be linked to? [20:54] * bryce hmms @ sru-ability of tv stuff [20:55] don't know how much user demand you have for it [20:55] anyway just a thought since upstream has those bits [20:55] yeah [20:57] we've got one TV out properties related bug, but it's medium priority [20:59] looks like we don't have a lot of user demand for it; guess we'll just snag it for karmic when we merge [21:10] bryce: I googled for "frontbuffer rendering broken" and found 19174 :) [21:11] I will fix it in the wiki [21:11] yikes [21:11] thanks [21:13] bryce: you had a lock on the page, any pending changes in your browser? [21:13] none [21:14] saved === ubott2 is now known as ubottu [22:18] hey I'm on Jaunty and playing video crashes X on most cases [22:20] on intel, of anyone wondered [22:20] s/of/if [22:21] do you have specified a Virtual size? [22:22] tormod: I don't know about that. [22:23] your xorg.conf is the default one? [22:24] well actually the Display Preferences GUI will rewrite it if you play with dual screen [22:24] Well, I'm using a single one [22:26] http://paste.ubuntu.com/155570/ my xorg.conf [22:27] hmm how come you have that "greedy" in there if you never touched it? [22:27] I didn¿t said I never touched it [22:27] *didn't [22:28] I just added that line in hopes the graphics performance increased [22:28] at least compiz isn't hanging now [22:50] is there a reason why Ubuntu patches Xorg to allow only 20 input-devices instead of the default 128? [23:00] bryce: is there somewhere compiz isn't running anymore on my intel card bugs should go? [23:01] bdmurray: it's currently disabled [23:01] due to 359392 [23:01] jbarnes: right, I realize that I was wondering if there was some master bug they should be made a duplicate of [23:01] ubottu: that's bug 359392 btw [23:01] Launchpad bug 359392 in xserver-xorg-video-intel "[i965] X freezes starting on April 3rd" [Critical,Triaged] https://launchpad.net/bugs/359392 [23:01] Error: I am only a bot, please don't think I'm intelligent :) [23:02] bdmurray: maybe that one [23:16] ah, let's not dupe to that one; it's long enough as is, and we still need it for working on [23:16] * bryce looks for better one to dupe to [23:17] yikes, >300 bugs on intel [23:19] bdmurray: 363821 looks suitable to dupe against [23:19] I'll update that one [23:24] bryce: yeah don't remind me [23:24] bryce: we've got >300 open at fdo also [23:24] and I seriously doubt all the ubuntu ones have fdo analogs :/ [23:25] likely not [23:59] https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/364895 --> feature request for karmic ツ [23:59] Launchpad bug 364895 in xorg-server "MAXDEVICES too low for some purposes" [Undecided,New]