[Bug 104673] drm lockups on g965 hardware
Public bug reported: Binary package hint: linux-source-2.6.20 All Feisty needs to support 3D on Intel g965 hardware without frequent crashes or lockups is to use a newer version of the kernel drm drivers. It has i915 drm 1.6.0, but libdrm from git is currently at 1.9.0. Running feisty's AMD64 2.6.20-14-generic, and with X started in an AMD64 feisty chroot, some openGL programs can trigger a bug, and get a message like: Apr 8 03:34:25 tesla kernel: [133430.971457] [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 16309404 emitted: 16312306 And the X server exits, leaving the image on screen unchanged. re- starting X fails, because the hardware is confused. (A reboot, or at least a suspend/resume to re-POST the video is needed.) How frequently this happens depends on the program. Some games seem to trigger this within 15 minutes to an hour. Others not at all. I think it depends on what graphics effects are enabled, too. Anyway, currently feisty on g965 hardware will, I think, give the average gamer crashes on the order of once in an hour of gameplay. Using kernel-side drm modules compiled from the latest git makes Feisty's mesa work great. (i915 version 1.9.0). I played nexuiz for 8 hours on it :) With Feisty's kernel drm modules, nexuiz sometimes made the video lock up, as above. So as I said, kernel drm modules are the only thing holding Feisty back from working fairly solidly out of the box on g965 hardware. (2D support is ok already). It might not be necessary to go all the way to 1.9.0. I've been compiling the latest drm and mesa on edgy for months now, with quite good results. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- drm lockups on g965 hardware https://bugs.launchpad.net/bugs/104673 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75702] Re: ~/.drirc is not read
The bug is still present in feisty, as of libgl1-mesa-dri 6.5.2-3ubuntu7. I installed feisty in a chroot, and I'm using Feisty's kernel anyway. BTW, there's only one serious problem with Feisty's support for g965 hardware: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/104673 not counting this bug as serious, although it might be for people who want to enable force_s3tc, for a game with pre-compressed textures. -- ~/.drirc is not read https://bugs.launchpad.net/bugs/75702 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68380] Re: [SRU] eclipse for edgy-updates
did you try rm -rf ~/.eclipse? Or just rm ~/.eclipse/org.eclipse.platform_3.2.0/configuration/org.eclipse.osgi/bundles/5/1/.cp/libswt-pi-gtk-3235.so I had to do that, because there's a .so buried deep in there!?! If you've tried to start eclipse and had it fail (with the memmove error), then it will keep failing even after you get a working eclipse installed. I have to say, I'm really unimpressed by that kind of behaviour, or even by keeping a .so in the user's home directory at all. Home directories are supposed to be shareable across machines that have different library versions, or even architectures. I totally wasn't expecting that, and only found it after poking through an strace -f -efile log on eclipse, after trying the edgy- proposed packages, then Martin Majlis's binary packages, and then a set I compiled myself. I guess they were all exactly the same, and it's just stupid eclipse, wasting my time. Grrr. I'd probably sound less hostile in an hour or two, so please try not to take it personally. Hopefully by posting I can save someone else the trouble of figuring this out. -- [SRU] eclipse for edgy-updates https://launchpad.net/bugs/68380 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94331] please consider omitting libc6 dependency in linux-headers...-generic
Public bug reported: Binary package hint: linux-source-2.6.20 I run AMD64 Edgy on a Core2Duo w/ an Intel g965 motherboard. I use the Ubuntu kernel from Feisty because it has a couple newer drivers (e.g. pata-marvell, needed for my IDE dvdrw). The only problem is that linux-headers-...-generic depends on Feisty's libc6, and installing it breaks Edgy's gcc. Installing the headers package with dpkg --force-depends-version (or by hacking the control file in the package) lets me compile working kernel modules. (Yes, I know Feisty packages on an Edgy system is unsupported. That's why I'm just filing a wishlist bug. Although the kernel is kind of special, since a recent kernel is often needed for new hardware.) There are some dynamic ELF executables in the package, e.g. genksyms, so I guess this dependency is warranted. When I started writing this, I didn't think there were any binaries in the package, so removing the libc6 dep would have been really easy. I guess that makes this even more wishlist than it was already, since to be strictly correct, you'd have split the package or drop the binaries. (They are of questionable usefulness, IMHO. I'm not a kernel expert, but I think if I was doing something with those tools I'd probably want a full kernel source tree. Unless m-a calls those tools when building modules?) Also, the binaries probably all work fine with libc6 2.4... (I know that doesn't count for much...) I think I've run out of useful arguments... I'm just saying that what I do works for me, and would be easier if I didn't have to hack the binary packages. I know I could just compile my own kernels from source, but the Ubuntu team does such a nice job of making a nice up-to-date kernel. I admin enough machines that I don't want to spend all my time at home being a sysadmin. I'd mark this as a wishlist bug if the web form let me. If reportbug did more than just post to a mailing list in Ubuntu, I'd rather use it. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- please consider omitting libc6 dependency in linux-headers...-generic https://launchpad.net/bugs/94331 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94331] Re: please consider omitting libc6 dependency in linux-headers...-generic
sorry, I meant to report this against the linux-source-2.6.20 source package, not the binary package. The binary package in question is linux-headers-2.6.20-12-generic. The same thing applied to linux- headers-2.6.20-9-generic, which is why I just went for the source pacakge. -- please consider omitting libc6 dependency in linux-headers...-generic https://launchpad.net/bugs/94331 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75702] Re: ~/.drirc is not read
On Wed, Mar 07, 2007 at 05:47:18PM -, Timo Aaltonen wrote: can you try with Feisty Herd5, which has mesa-6.5.2 It's fixed in mesa-6.5.3 (current git), which is what I'm using now. g965 is new enough hardware that it's worth keeping up... If I can update just my mesa package, I'll try it. Otherwise, well, maybe. ** Changed in: mesa (Ubuntu) Status: Unconfirmed = Needs Info -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces! -- Plautus, 200 BC -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75702] Re: ~/.drirc is not read
On Thu, Mar 08, 2007 at 10:06:09AM -, Timo Aaltonen wrote: can you find the changeset which fixed this? git-blame src/mesa/drivers/dri/i965/intel_context.c shows 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 333)intel-sarea = saPriv; 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 334) 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 335)driParseConfigFiles (intel-optionCache, intelScreen-optionCache, 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 336) intel-driScreen-myNum, i965); 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 337) 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 338)intel-vblank_flags = (intel-intelScreen-irq_active != 0) 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 339)? driGetDefaultVBlankFlags(intel-optionCache) : VBLANK_FLAG_NO_IRQ; 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 340) 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 341) ctx-Const.MaxTextureMaxAnisotropy = 2.0; 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 342) That might be it. Does that help? I'd have to go read the git docs some more to dig any deeper. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces! -- Plautus, 200 BC -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88585] Re: dga corrupts its pagetable
** Attachment added: first r128, then i965 http://librarian.launchpad.net/6565140/kern.log -- dga corrupts its pagetable https://launchpad.net/bugs/88585 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88585] Re: dga corrupts its pagetable
** Attachment added: r128 Xorg.1.log http://librarian.launchpad.net/6565141/Xorg.1.log -- dga corrupts its pagetable https://launchpad.net/bugs/88585 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88585] Re: dga corrupts its pagetable
** Attachment added: i965 Xorg.0.log http://librarian.launchpad.net/6565144/Xorg.0.log -- dga corrupts its pagetable https://launchpad.net/bugs/88585 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88585] dga corrupts its pagetable
Public bug reported: Binary package hint: xf86dga I run AMD64 Ubuntu Edgy on a core2duo with onboard g965 and PCI r128 video hardware, in a multiseat setup. (-sharevts, evdev input devices). I know this is probably the wrong package to report this on, since dga is just the client, not the library that's doing all the fancy stuff. I hope you know which package to transfer it to. Running sudo dga makes my screen blink (i.e. a relay in the CRT cilcks, so the video signal must have been affected), and the screen stops updating. The X server also stops reading the keyboard. The X server was still running, and xdpyinfo worked. Killing my wm made my startx session exit, including the X server. Starting X again didn't show any signs of video corruption, so it didn't leave the card in a weird state. (the text console was screwed up, of course.) This happens on both the i965 head and the r128 head. crashing one doesn't affect the other. The interesting part is that the kernel log shows that the dga process had a corrupt pagetable. I'll attach my kern.log, from doing dga on the r128 head, and then on the i965 head. ** Affects: xf86dga (Ubuntu) Importance: Undecided Status: Unconfirmed -- dga corrupts its pagetable https://launchpad.net/bugs/88585 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88585] Re: dga corrupts its pagetable
** Attachment added: my xorg.conf http://librarian.launchpad.net/6565146/xorg.conf -- dga corrupts its pagetable https://launchpad.net/bugs/88585 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88585] Re: dga corrupts its pagetable
I reproduced this with sudo X -config ... to load a vanilla config file, that doesn't do any multiseat or even multihead stuff. It also doesn't have the int10 module commented or anything. Nor does it have the omit xfree86-dga option! Anyway, this time the xterm I ran dga in shows: 1 addr:0x2aafc61b000, width 1024, bank size 6291456, depth 24 planes Otherwise everything's the same. Maybe dga is broken on amd64? Note that I'm running the kernel from Feisty, which (with mesa 6.5.2) improved the stability of X a lot. -- dga corrupts its pagetable https://launchpad.net/bugs/88585 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87422] crash on load on AMD64
Public bug reported: Binary package hint: xevil Ubuntu Edgy, AMD64: $ xevil XEvil(TM) version 2.02r2 http://www.xevil.com [EMAIL PROTECTED] XETP1.00 Copyright(C) 1994,2000 Steve Hardt and Michael Judge XEvil is free software under the Gnu General Public License. XEvil comes with absolutely no warranty. Type 'xevil -info' for license information and information on no warranty. 'xevil -help' for usage and network-play instructions. *** glibc detected *** xevil: munmap_chunk(): invalid pointer: 0x009ad198 *** === Backtrace: = /lib/libc.so.6(__libc_free+0x17a)[0x2b41b44269aa] xevil[0x4181ed] xevil[0x41a4c6] xevil[0x4507da] /lib/libc.so.6(__libc_start_main+0xf4)[0x2b41b43d50c4] xevil(__gxx_personality_v0+0x121)[0x403989] === Memory map: 0040-005fe000 r-xp fe:10 4194474 /usr/games/xevil 006fe000-0072a000 rw-p 001fe000 fe:10 4194474 /usr/games/xevil 0072a000-009b3000 rw-p 0072a000 00:00 0 [heap] 2b41b3b1d000-2b41b3b39000 r-xp 09:00 41108 /lib/ld-2.4.so 2b41b3b39000-2b41b3b97000 rw-p 2b41b3b39000 00:00 0 2b41b3c38000-2b41b3c3a000 rw-p 0001b000 09:00 41108 /lib/ld-2.4.so 2b41b3c3a000-2b41b3c4a000 r-xp fe:10 16869725 /usr/lib/libXpm.so.4.11.0 2b41b3c4a000-2b41b3d4a000 ---p 0001 fe:10 16869725 /usr/lib/libXpm.so.4.11.0 2b41b3d4a000-2b41b3d4b000 rw-p 0001 fe:10 16869725 /usr/lib/libXpm.so.4.11.0 2b41b3d4b000-2b41b3e25000 r-xp fe:10 16853149 /usr/lib/libX11.so.6.2.0 2b41b3e25000-2b41b3f24000 ---p 000da000 fe:10 16853149 /usr/lib/libX11.so.6.2.0 2b41b3f24000-2b41b3f29000 rw-p 000d9000 fe:10 16853149 /usr/lib/libX11.so.6.2.0 2b41b3f29000-2b41b400f000 r-xp fe:10 17555475 /usr/lib/libstdc++.so.6.0.8 2b41b400f000-2b41b410e000 ---p 000e6000 fe:10 17555475 /usr/lib/libstdc++.so.6.0.8 2b41b410e000-2b41b4114000 r--p 000e5000 fe:10 17555475 /usr/lib/libstdc++.so.6.0.8 2b41b4114000-2b41b4117000 rw-p 000eb000 fe:10 17555475 /usr/lib/libstdc++.so.6.0.8 2b41b4117000-2b41b4129000 rw-p 2b41b4117000 00:00 0 2b41b4129000-2b41b41a9000 r-xp 09:00 41162 /lib/libm-2.4.so 2b41b41a9000-2b41b42a8000 ---p 0008 09:00 41162 /lib/libm-2.4.so 2b41b42a8000-2b41b42aa000 rw-p 0007f000 09:00 41162 /lib/libm-2.4.so 2b41b42aa000-2b41b42ab000 rw-p 2b41b42aa000 00:00 0 2b41b42ab000-2b41b42b8000 r-xp 09:00 41156 /lib/libgcc_s.so.1 2b41b42b8000-2b41b43b7000 ---p d000 09:00 41156 /lib/libgcc_s.so.1 2b41b43b7000-2b41b43b8000 rw-p c000 09:00 41156 /lib/libgcc_s.so.1 2b41b43b8000-2b41b44ee000 r-xp 09:00 41131 /lib/libc-2.4.so 2b41b44ee000-2b41b45ee000 ---p 00136000 09:00 41131 /lib/libc-2.4.so 2b41b45ee000-2b41b45f1000 r--p 00136000 09:00 41131 /lib/libc-2.4.so 2b41b45f1000-2b41b45f3000 rw-p 00139000 09:00 41131 /lib/libc-2.4.so 2b41b45f3000-2b41b45f8000 rw-p 2b41b45f3000 00:00 0 2b41b45f8000-2b41b45fa000 r-xp fe:10 16869671 /usr/lib/libXau.so.6.0.0 2b41b45fa000-2b41b46fa000 ---p 2000 fe:10 16869671 /usr/lib/libXau.so.6.0.0 2b41b46fa000-2b41b46fb000 rw-p 2000 fe:10 16869671 /usr/lib/libXau.so.6.0.0 2b41b46fb000-2b41b46fc000 rw-p 2b41b46fb000 00:00 0 2b41b46fc000-2b41b4701000 r-xp fe:10 16869689 /usr/lib/libXdmcp.so.6.0.0 2b41b4701000-2b41b480 ---p 5000 fe:10 16869689 /usr/lib/libXdmcp.so.6.0.0 2b41b480-2b41b4801000 rw-p 4000 fe:10 16869689 /usr/lib/libXdmcp.so.6.0.0 2b41b4801000-2b41b4803000 r-xp 09:00 41148 /lib/libdl-2.4.so 2b41b4803000-2b41b4903000 ---p 2000 09:00 41148 /lib/libdl-2.4.so 2b41b4903000-2b41b4905000 rw-p 2000 09:00 41148 /lib/libdl-2.4.so 2b41b4905000-2b41b4907000 rw-p 2b41b4905000 00:00 0 2b41b4907000-2b41b490d000 r-xp fe:10 8389965 /usr/lib/X11/locale/common/xlibi18n.so.2.0.0 2b41b490d000-2b41b4a0c000 ---p 6000 fe:10 8389965 /usr/lib/X11/lAborted ** Affects: xevil (Ubuntu) Importance: Undecided Status: Unconfirmed -- crash on load on AMD64 https://launchpad.net/bugs/87422 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87465] nearly unplayable (game speed?)
Public bug reported: Binary package hint: trophy Ubuntu Edgy AMD64. Trophy is nearly unplayable, because turns are so fast that you can hardly get the car pointed in the direction you want. Even the AI can't handle it; the AI always gets stuck on the inside of the first corner, and then oscillates turning left and right somewhere. I've never seen an AI complete a lap. Well, maybe once, while I was on my fifth. The turn rate is ~20 full 360degree turns in 10 game seconds (which look about like real-time seconds). It's less like driving and more like flying a rocket by directing thrust. And of course the AI never does anything interesting, and just clogs up the track near the first corner. Trophy shows 500-1000 FPS on my Core 2 Duo 6600, i965 onboard graphics, dual channel DDR2-6400 RAM. trophy is using 75% CPU time, Xorg 25%. Maybe the game speed depends on the computer speed... Trophy should also acknowledge the influence of the commercial DOS game Death Rally. Lines like Petrol in my Veins are lifted directly from it, not to mention the whole game concept. ** Affects: trophy (Ubuntu) Importance: Undecided Status: Unconfirmed -- nearly unplayable (game speed?) https://launchpad.net/bugs/87465 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87465] Re: nearly unplayable (game speed?)
BTW, it plays fine at 1024x768 on the second head on this machine: an ATI AIW r128 PCI vid card. 30FPS. -- nearly unplayable (game speed?) https://launchpad.net/bugs/87465 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87465] Re: nearly unplayable (game speed?)
fullscreen mode make it segfault, though. (-f switch, or in-game config menu) -- nearly unplayable (game speed?) https://launchpad.net/bugs/87465 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87246] fails on files with names ending in space
Public bug reported: Binary package hint: fslint I ran fslint-gui in duplicate-check mode over my multimedia collection, and it reported this error: exceptions.OSError: [Errno 2] No such file or directory: '/mnt/unpackfs/data/shared/downloaded/showtunes/02 -' I have a file with that name, except with a trailing space. I don't know why I had such a file, so don't ask... This came from the python part of program, since I followed its progress, first traversing the tree, then md5sum, then sha1sum, then python. (can there be a tickbox to turn off one or the other of sha1/md5sum in the gui? The chances of an accidental collision are pretty low.) fslint is slow enough already, esp. when running over a FUSE mount (unpackfs in my case). I'll try the command line options... I looked at the shell script, but I don't have a fix for the bug. ** Affects: fslint (Ubuntu) Importance: Undecided Status: Unconfirmed -- fails on files with names ending in space https://launchpad.net/bugs/87246 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70167] Re: Labplot is unstable
On AMD64 Edgy, I can crash labplot like this: run labplot open a spreadsheet type in some xy pairs (I left some blank rows, in case that matters) plot it close the plot labplot crashes: ... (no debugging symbols found) (no debugging symbols found) 0x2b9df2328c40 in nanosleep () from /lib/libc.so.6 #0 0x2b9df2328c40 in nanosleep () from /lib/libc.so.6 #1 0x2b9df2328a94 in sleep () from /lib/libc.so.6 #2 0x2b9def146575 in KCrash::startDrKonqi () from /usr/lib/libkdecore.so.4 #3 0x2b9def15ab07 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x2b9df22c4510 in killpg () from /lib/libc.so.6 #5 0x in ?? () -- Labplot is unstable https://launchpad.net/bugs/70167 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 68191] Re: Dual core sets each core to different cpufreq governor after resume
On Sat, Jan 06, 2007 at 02:24:12PM -, Luka Renko wrote: Marking as confirmed due to many duplicates. Not sure if the package is appropriate, I would think kernel is more likely responsible for this. The kernel could preserve that state across suspend, but it doesn't have to be the kernel's job. user-space should apply the configured policy for CPU hotplug events. This would ensure correct behaviour in all CPU hotplug cases, not just suspend-resume where the kernel hot-unplugs all but one CPU before suspend. (This is maybe only likely to happen with virtual machines, because most desktop hardware isn't physically hotplug safe. And AFAIK Xen prevents cpufreq from working.) -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces! -- Plautus, 200 BC -- Dual core sets each core to different cpufreq governor after resume https://launchpad.net/bugs/68191 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76500] doesn't manage local machine
Public bug reported: Binary package hint: xenman I installed xenman on my AMD64 Edgy system, on a core 2 duo. I'm running the kernel from xen-image-xen0-2.6.16-11.2-generic 2.6.16-11.2 as dom0 on xen-hypervisor-3.0-amd64 3.0.3-0ubuntu1. I don't have any domUs, but xen-utils-3.0 is installed, and xend is running. xenman claims the local machine will show up as a manageable node if the prereqs are met, but it doesn't say what the pre-reqs are for the local machine, only for remote machines. The docs don't say exactly how it tries to interact with xen, so I can't tell if it doesn't like what it finds in some config file, or what. ** Affects: xenman (Ubuntu) Importance: Undecided Status: Unconfirmed -- doesn't manage local machine https://launchpad.net/bugs/76500 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76500] Re: doesn't manage local machine
I found something in an strace, around line 6940 (57%): 9220 open(/proc/xen/privcmd, O_RDWR) = 7 9220 fcntl(7, F_GETFD) = 0 9220 fcntl(7, F_SETFD, FD_CLOEXEC) = 0 9220 mlock(0x7fea3950, 32) = 0 9220 ioctl(7, SNDCTL_DSP_RESET, 0x7fea38f0) = -1 ENOSYS (Function not imple 9220 ioctl(7, SNDCTL_DSP_RESET, 0x7fea38f0) = -1 ENOSYS (Function not imple 9220 close(7) = 0 So maybe a newer kernel would help, but I haven't found anything but 2.6.16.* kernels, even in the xen unstable mercurial repository. I need the drivers in 2.6.19 (e1000 and PATA_MARVELL) to do more than play with xen. :/ -- doesn't manage local machine https://launchpad.net/bugs/76500 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
I saw this again on my system, this time on a single-head setup with just the r128. Again while running googleearth. This time the server wasn't able to recover from the segfault and restore text mode, and went into an infinite loop. I had to send it a SIGKILL before it would die. Xorg.0.log is 3.8GB (although 7zip takes it down to 568kB, an impressive factor of 7000). Google Earth ran ok once (although flickery). I turned off aniso filtering and reduced the detail level, and set texture depth to 16bit. Then I exited and started it again. This time X froze while its splash screen was up. I sshed in from another machine to kill it, but the X server kept writing its log file (and the kernel log file was growing too; up to 218MB). Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0x71) [0x480b81] 1: /lib/libc.so.6 [0x2b3fd2948510] 2: /lib/libc.so.6(memcpy+0x60) [0x2b3fd298eb10] 3: /usr/lib/xorg/modules/extensions/libglx.so [0x2b3fd360384e] 4: /usr/lib/dri/r128_dri.so(__driUtilUpdateDrawableInfo+0x10a) [0x2b3fd5af9448] 5: /usr/lib/dri/r128_dri.so [0x2b3fd5af98ca] 6: /usr/lib/xorg/modules/extensions/libglx.so [0x2b3fd3602aa1] 7: /usr/lib/xorg/modules/extensions/libglx.so(DoMakeCurrent+0x42d) [0x2b3fd35e1c 7d] 8: /usr/lib/xorg/modules/extensions/libglx.so [0x2b3fd35e459a] 9: /usr/X11R6/bin/X(Dispatch+0x1ba) [0x4483aa] 10: /usr/X11R6/bin/X(main+0x455) [0x431035] 11: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b3fd29350c4] 12: /usr/X11R6/bin/X(FontFileCompleteXLFD+0xa1) [0x430339] Fatal server error: Caught signal 11. Server aborting (II) AIGLX: Suspending AIGLX clients for VT switch (EE) R128(0): R128CCEWaitForIdle: CCE idle -22 (EE) R128(0): Idle timed out, resetting engine... (EE) R128(0): R128CCEWaitForIdle: CCE stop -22 (EE) R128(0): R128CCEWaitForIdle: CCE reset -22 (EE) R128(0): R128CCEWaitForIdle: CCE start -22 (EE) R128(0): R128CCEWaitForIdle: CCE idle -22 (EE) R128(0): Idle timed out, resetting engine... (EE) R128(0): R128CCEWaitForIdle: CCE stop -22 (EE) R128(0): R128CCEWaitForIdle: CCE reset -22 (EE) R128(0): R128CCEWaitForIdle: CCE start -22 (EE) R128(0): R128CCEWaitForIdle: CCE idle -22 I don't think you need to see 3.8GB of that. It compresses that well because it's pretty redundant... kernel: Dec 14 02:27:00 tesla kernel: [ 212.047457] [drm] Initialized drm 1.1.0 20060810 Dec 14 02:27:00 tesla kernel: [ 212.048563] ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 16 Dec 14 02:27:00 tesla kernel: [ 212.048693] [drm] Initialized i915 1.6.0 20060119 on minor 0 Dec 14 02:50:23 tesla kernel: [ 1614.136780] ACPI: PCI Interrupt :06:01.0[A] - GSI 22 (level, low) - IRQ 22 Dec 14 02:50:23 tesla kernel: [ 1614.136937] [drm] Initialized r128 2.5.0 20030725 on minor 1 Dec 14 03:54:23 tesla kernel: [ 5454.112739] [drm:r128_cce_idle] *ERROR* r128_cce_idle called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112763] [drm:r128_cce_stop] *ERROR* r128_cce_stop called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112780] [drm:r128_cce_reset] *ERROR* r128_cce_reset called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112787] [drm:r128_cce_start] *ERROR* r128_cce_start called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112794] [drm:r128_cce_idle] *ERROR* r128_cce_idle called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112805] [drm:r128_cce_stop] *ERROR* r128_cce_stop called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112820] [drm:r128_cce_reset] *ERROR* r128_cce_reset called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112827] [drm:r128_cce_start] *ERROR* r128_cce_start called without lock held repeating, sometimes so fast that the dd reading kmsg couldn't keep up, and the messages got corrupted. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
It's probably important to note that the r128 card was not the system's primary vid card. The text console was on the internal g965, and that's the hardware the BIOS POSTed; my BIOS is explicitly set to use the internal vga as the primary VGA device. X servers that start after the nasty hang that required SIGKILLing the X server all crash. They seem to be using the g965 video BIOS with the r128, even though the r128 is the only device configured. There's a line in the log like (II) R128(0): VESA VBE Total Mem: 262080 kB (II) R128(0): VESA VBE OEM: Intel(r)Broadwater-G Graphics Chip Accelerated VGA BIOS *snicker* that's some confused hardware. A reboot took care of it... Also, all X backtraces seem to include FontFileCompleteXLFD. I was confused before about which direction the backtrace was going and thought it was significant; F.F.C.XLFD is somehow showing up as the parent of _libc_start_main. So X must do something to the stack that the backtracer doesn't like. It's obviously not significant that all the backtraces have the same parent, since it's the same program. Sorry for any confusion. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75726] DRI broken on r128 on dual head r128 + i965 (non Xinerama)
Public bug reported: My system: core 2 duo on DG965WH (onboard g965 graphics), AMD64 Edgy, 2.6.19-mm1. r128 pci card installed, too. Xorg 2D driver i810_drv v1.7.3 built from git source. libgl1-mesa-dri built with -fno-strict- aliasing from Edgy source. With a dual-head non-xinerama setup, dri works on the primary head (the g965), but on the r128 head it gives weird errors and doesn't work. e.g. glxinfo ... the info for screen 0 Error: nConfigOptions (3) does not match the actual number of options in\n __driConfigOptions (4). ... check the attached strace for lines that start write(2, for its stderr messages. dri works when the r128 is used as a single head (even though it's still not the machine's primary VGA). ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Unconfirmed -- DRI broken on r128 on dual head r128 + i965 (non Xinerama) https://launchpad.net/bugs/75726 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75726] Re: DRI broken on r128 on dual head r128 + i965 (non Xinerama)
You'll have to get the stdout and stderr messages from the strace, which was done with -s256 so they're all there. I didn't save the Xorg.0.log, either. I can probably use that setup again and reproduce it if you need more info. BTW, glxgears, tuxkart, and others print the same errors and can't open their window. 2D and XVideo works fine. ** Attachment added: glxinfo strace http://librarian.launchpad.net/5392654/glxinfo.r128-2nd.errors.trace -- DRI broken on r128 on dual head r128 + i965 (non Xinerama) https://launchpad.net/bugs/75726 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75728] xv on r128 hard locked whole machine
Public bug reported: core 2 duo, dg965wh mobo (onboard g965 as primary vga, pci r128 installed). AMD64 Edgy. single headed r128 X setup (even though the r128 is the secondary VGA card in the system). I ran xine on a video, and as soon as it initialed xv, the machine locked hard. I didn't see any frames of video or hear any sound, but I didn't say immediately because xine displays a window before it starts using Xv... hard lock = no ping, no numlock led response, no ALT+SYSRQ+anything. Also no video signal (monitor goes to power saving off mode). ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: Unconfirmed -- xv on r128 hard locked whole machine https://launchpad.net/bugs/75728 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75728] Re: xv on r128 hard locked whole machine
with vlc on a different file, X is kind of locked (no cursor movement), but the system is fine. I hear sound, and I can pause and unpause with the keyboard (I think). X seems to have exitted eventually on its own. end of the log file: (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025 (EE) R128(0): Idle timed out, resetting engine... (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025 (EE) R128(0): Idle timed out, resetting engine... (II) R128(0): [drm] removed 1 reserved context for kernel (II) R128(0): [drm] unmapping 8192 bytes of SAREA 0x2f00 at 0x2b33e6f4f000 I was able to ssh in. I'll try disabling DMAforXv in my X config. -- xv on r128 hard locked whole machine https://launchpad.net/bugs/75728 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75728] Re: xv on r128 hard locked whole machine
I'll try disabling DMAforXv in my X config. Yeah, that was the trick. Sorry, I forgot about that what with all the other things that have been making X crash while I mess around. Anyway, it's already documented as unstable, and I enabled it, so it's all my fault :) You should probably close this bug. ** Description changed: core 2 duo, dg965wh mobo (onboard g965 as primary vga, pci r128 installed). AMD64 Edgy. single headed r128 X setup (even though the r128 is the secondary VGA - card in the system). + card in the system). (edit: DMAforXv was enable, and disabling it + helped. Just close this bug. Sorry!) I ran xine on a video, and as soon as it initialed xv, the machine locked hard. I didn't see any frames of video or hear any sound, but I didn't say immediately because xine displays a window before it starts using Xv... hard lock = no ping, no numlock led response, no ALT+SYSRQ+anything. Also no video signal (monitor goes to power saving off mode). -- xv on r128 hard locked whole machine https://launchpad.net/bugs/75728 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75695] huge performance hit for -i with UTF-8 locales
Public bug reported: On a source tree with 28MB of .c and .h files (Mesa), grep is slow with -i and fast without it with the default Ubuntu locale settings (LANG=en_US.UTF-8, no LC_ variables set). Actually, even some [Vv] style patterns are much faster with LANG=C, so this is even more like https://bugs.launchpad.net/distros/ubuntu/+source/grep/+bug/47634 My box is a core 2 duo (2.4GHz), which makes a beast like gnome feel almost as snappy as fluxbox :) Everything is in the disk cache, so I/O isn't a factor. Neither is memory bandwidth. The machine was otherwise idle. I'm running AMD64 Edgy. [EMAIL PROTECTED]:/usr/local/src/g965/mesa$ locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 ... (all the same) (times are measured for the second run in a row, so the CPU core it runs on is at full clock speed the whole time.) time find -name '*.[ch]' | xargs grep -i 'volatile_s3tc' real0m3.498s; user0m3.483s; sys 0m0.023s time find -name '*.[ch]' | xargs grep 'volatile.*s3tc' real0m0.076s; user0m0.050s; sys 0m0.023s Non UTF-8 locales are just as fast as without -i time find -name '*.[ch]' | LANG=C xargs grep -i 'volatile.*s3tc' real0m0.083s; user0m0.067s; sys 0m0.020s time find -name '*.[ch]' | LANG=en_CA xargs grep -i 'volatile.*s3tc' real0m0.079s; user0m0.050s; sys 0m0.027s Making a case insensitive pattern takes more time, but is not really slow. However, it probably doesn't really match everything that grep -i would on input that wasn't all 7 bit ASCII: time find -name '*.[ch]' | xargs grep '[Vv][Oo][Ll][Aa][Tt][Ii][Ll][Ee].*[Ss]3[Tt][Cc]' real0m0.340s; user0m0.313s; sys 0m0.027s It is affected by locale settings, too. time find -name '*.[ch]' | LANG=C xargs grep '[Vv][Oo][Ll][Aa][Tt][Ii][Ll][Ee].*[Ss]3[Tt][Cc]' real0m0.096s; user0m0.080s; sys 0m0.027s ** Affects: grep (Ubuntu) Importance: Undecided Status: Unconfirmed -- huge performance hit for -i with UTF-8 locales https://launchpad.net/bugs/75695 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66645] Re: On 965G glxgears fails with DRM_I830_CMDBUFFER: -22
It's not fixed in AMD64 Edgy. I had to apt-get source ... to build with -fno-strict-aliasing. That fixed that problem. -- On 965G glxgears fails with DRM_I830_CMDBUFFER: -22 https://launchpad.net/bugs/66645 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75702] ~/.drirc is not read
Public bug reported: system info: AMD64 Edgy on a Core 2 Duo on a DG965WH (onboard g965 video). Kernel 2.6.19-mm1. strace -o gl.tr glxgears. (don't 21 | less, or it will block your X server and you'll have to a text console and kill strace.) shows that GL progs never read /etc/drirc or ~/.drirc. This file is written by driconf. On my Debian unstable system, it had an effect. I was able to enable hardware s3tc support on my ATI Radeon (AIW 7200). This may be an upstream bug; even with the latest mesa, drm, and xf86 -video-intel from git, drirc is still ignored (so I can't enable force_s3tc_enable). ./src/mesa/drivers/dri/common/xmlconfig.c in the mesa source obviously has code to look for drirc, but it never gets to the point of making any system calls involving the filename. The latest xf86-video-intel xorg driver (v 1.7.3) fixes the b0rked video problem I've been having after X has to restore text mode and then start again. I'll file a separate report about that. This is stopping me from playing TA Spring on this box. :( ** Affects: mesa (Ubuntu) Importance: Undecided Status: Unconfirmed -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75706] new upstream version fixes mode save/restore problem
Public bug reported: I'm running Ubuntu Edgy AMD64 on a Core 2 Duo (Intel DG965WH mobo w/ onboard g965 video). X usually started fine the first time, but stopping and restarting, or switching to a text console and back often resulted in video corruption. The VGA out was outputting a signal, but my monitor couldn't sync to it, so I saw basically an average of all the colours on the screen. connecting to the display with x11vnc worked. Suspending and resuming (ACPI S3 - suspend to RAM) the whole system fixed the video, because that re-POSTs the card. (This mobo has pretty good ACPI support. :) I grabbed the latest xf86-video-intel git tree, and the driver from that totally solved the problem. It's v1.7.3. I haven't seen the bad video output thing with it at all. I'm not sure if this is a good place to explain how I did it, for the benefit of other users, but here it is. I did apt-get build-dep xserver-xorg-video-i810 to get all the dev packages. I got the source using the git command listed at http://www.intellinuxgraphics.org/download.html. (note that Mesa uses git now, too, so don't use the cvs command listed there.) build the source cd /usr/lib/xorg/modules/drivers sudo dpkg-divert --local --rename $PWD/i810_drv.so copy the new i810_drv.so to new/..., and use ln -s to make a symlink so you can easily switch back and forth between your custom module and the distro version. Use dpkg-divert to remove the diversion when Ubuntu catches up with your custom module and you want to stop messing around with this. ** Affects: xserver-xorg-video-i810 (Ubuntu) Importance: Undecided Status: Unconfirmed -- new upstream version fixes mode save/restore problem https://launchpad.net/bugs/75706 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
I guess I'm the fourth person with an X crash in FontFileCompleteXLFD. Other reports are: https://bugs.launchpad.net/distros/ubuntu/+source/xorg-server/+bug/68135 https://bugs.launchpad.net/distros/ubuntu/+source/xorg-server/+bug/67613 I have a Core 2 Duo on an Intel DG965WH (g965 graphics), running AMD64 Ubuntu Edgy. 3D was fine (except for no s3tc) with the i965 driver. Then I put in an r128 AIW card and enabled Xinerama, which disables DRI. (And I guess any indirect accel, too.) Now googleearth (an ia32 binary; installed from the medibuntu repository) crashes my X server while starting. This seemed very repeatable, and happened even with latest upstream xf86-video-intel. (ge is a 32bit app that comes with its own libraries, so it wasn't using the 64bit libdrm or mesa client-side libs I compiled.) (The Xorg.0.log I attached was with the Edgy versions of everything, though.) Some other GL progs, like glxgears and tuxkart, ran without crashing (tuxkart slowly, glxgears pretty fast on this CPU :). ** Attachment added: X backtrace from googleearth-induced crash http://librarian.launchpad.net/5392191/Xorg.0.log.old.ubuntu.ge-crash -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
And with Xinerama disabled, running glxinfo on the second head (r128) makes the server segfault! That screen (:0.1) wasn't using DRI. I think the root cause was that the r128 kernel module wasn't loaded. Maybe there's another bug here somewhere, since X should cause the dri module to load like it does for i915 for the first head. The server's i810_drv.so is v1.7.3, that I compiled myself, and the client libGL and libdrm are also the latest git versions that I compiled locally. The only files outside of /usr/local that are locally compiled are i810_drv.so, and /usr/X11R6/lib/modules/dri. No, that isn't where ubuntu puts r128_dri.so, but that's where mesa 6.5.2 in /usr/local/lib looks for them... Err, /usr/lib/dri/* is from libgl1-mesa-dri, which I built locally from Ubuntu source, because I needed to compile with -fno-strict-aliasing for the i965 driver to work. Anyway, I'll attach my Xorg log file in the hope that it's of some use even though it's not with the Ubuntu versions of everything. It's a big pain to use Edgy's i810_drv.so, because it screws up the vid mode. I'll send this now before I do anything that risks crashing X and losing what I've typed in firefox, since I'm not running it in Xvnc or anything! ** Attachment added: Xorg log from glxinfo crash http://librarian.launchpad.net/5392246/Xorg.0.log.glxinfo-r128-second-head.crash -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75702] Re: ~/.drirc is not read
This seems to be specific to the i965 (or ixxx?) mesa driver. I put a PCI R128 AIW card into the machine (to use as a second head). After finding and reporting some bugs with two X screens, I set X to use the r128 as its only screen. Now glxgears and glxinfo read ~/.drirc, and look for /etc/drirc. Configuring the swap interval actually has an effect: setting it to 1 makes glxgears -printfps go at 70FPS, the monitor refresh rate. 0 gives 265FPS. (The g965 hardware does more like 1220FPS :) It's the last thing it does before it starts doing 3D: ... open(/usr/lib/x86_64-linux-gnu/libtxc_dxtn.so, O_RDONLY) = -1 ENOENT (No such file or directory) munmap(0x2b06e727, 70806) = 0 open(/etc/drirc, O_RDONLY)= -1 ENOENT (No such file or directory) open(/home/peter/.drirc, O_RDONLY)= 5 read(5, driconf\ndevice screen=\0\..., 4096) = 290 read(5, , 4096) = 0 close(5)= 0 mmap(NULL, 1417216, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x 2b06e727 brk(0x593000) = 0x593000 brk(0x5bd000) = 0x5bd000 ... then pretty soon the string of ioctl()s... -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 9805] Re: Use performance governor during boot
I thought bootup was mostly I/O limited on most systems, unless the readahead really gets almost everything into the cache. disk seeks are slow, and there are a _lot_ of small config files to read. And then there's sleeps while modules detect hardware after they load, and network (dhcp) delays. Won't a reasonable governor bump up the cpu speed when needed? It seems like a real waste to have the cpu at full speed while waiting for DHCP. Of course, I can't argue with real data. What CPU, RAM, and disk do you have? and how fast is your disk: RPM is a pretty good measure of seek time, and hdparm -t /dev/hda is a useful sequential read test. -- Use performance governor during boot https://launchpad.net/bugs/9805 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75438] seconds CPU uses performance governor after resume
Public bug reported: Binary package hint: powernowd Apparently the kernel handles ACPI suspend by using CPU hotplug to stop all but one CPU, and then using non-SMP-safe freeze code. This results in the symptom I see on my core 2 duo desktop running AMD64 edgy: after a resume, the governor for the second CPU is performance, even though powernowd is still running, and the first CPU is still being governed properly by the userspace governor. (The easiest way to check the current state is to run cpufreq-info from the cpufrequtils package). So powernowd needs to do something after a resume, probably by dropping a script into /etc/acpi/resume.d. ** Affects: powernowd (Ubuntu) Importance: Undecided Status: Unconfirmed -- seconds CPU uses performance governor after resume https://launchpad.net/bugs/75438 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75315] libc6-dev 2.5 doesn't work with Edgy's gcc
Public bug reported:
(I reported this with reportbug, but with a bogus default email address.
I think I also left out the actual error message. sorry!)
Upgrading libc6-dev breaks Edgy's gcc; It can no longer link with
libc:
[EMAIL PROTECTED]:~$ gcc zero.c -o zero
/lib/libc.so.6: file not recognized: File format not recognized
collect2: ld returned 1 exit status
[EMAIL PROTECTED]:~$ cat zero.c
//int _start(){return 0;} // for -nostdlib
int main(){return 0;}
[EMAIL PROTECTED]:~$ gcc --version
gcc (GCC) 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)
gcc -nostdlib can create an executable that will run (and immediately
segfault, if you don't make an exit(2) syscall), so the compiler still
works except for linking libc. I didn't have any problems running
programs that were already linked (i.e. everything in /usr/bin).
Fortunately, downgrading back to the Edgy libc6 restores things to
working order. (And I'm running reportbug after the downgrade, so I
just switched the version numbers in the report myself.)
It looks like libc6-dev 2.5 needs a versioned Conflicts: with
gcc-4.1, and any other affected compilers. I haven't experimented..
I'm running a freshly installed AMD64 Ubuntu Edgy on a core 2 duo, with
a Fiesty Fawn kernel: linux-image-2.6.19-7-generic version 2.6.19-7.11.
-- System Information:
Debian Release: testing/unstable
APT prefers edgy-updates
APT policy: (990, 'edgy-updates'), (990, 'edgy-security'), (990, 'edgy'),
(500, 'feisty')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.19-7-generic
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages libc6-dev recommends:
ii gcc [c-compiler]4:4.1.1-6ubuntu3 The GNU C compiler
ii gcc-4.1 [c-compiler]4.1.1-13ubuntu5 The GNU C compiler
-- no debconf information
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
libc6-dev 2.5 doesn't work with Edgy's gcc
https://launchpad.net/bugs/75315
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61951] Re: 965/x3000 video not supported
kernel log message: [48096.418558] [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed This was due to a miscompiled libgl1-mesa-dri. See https://bugs.launchpad.net/distros/ubuntu/+source/mesa/+bug/62135 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394311 tuxkart and ppracer are fine now, but the vid mode thing is still sometimes a problem. -- 965/x3000 video not supported https://launchpad.net/bugs/61951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61951] Re: 965/x3000 video not supported
I have an Intel DG956WH motherboard (G965, GMA X3000). I installed AMD64 Edgy from cd, using an IDE-USB adapter (handy gadget to have around). I had my CRT connected to the VGA port through a KVM during the install. I have since discovered that the KVM doesn't pass DDC signals, which explains my 60Hz refresh rate, and might have something to do with other problems. (which I maybe should have filed as separate bugs; let me know if I should split this up.) Video worked fine out of the box for me. Switching to a text console and back screwed up the video, though. My CRT loses vertical sync, and the screen becomes a flicker of the average colour of whatever is displayed. (I think the output image is fine, it's just not in a vid mode the monitor can sync to or something. I can ssh in and use x11vnc -display :0 and continue using my login session, which is how I can compare the displayed image with the colour of the flicker.) Upgrading the kernel to linux-image-2.6.19-7-generic 2.6.19-7.11 made switching to a text console safe, but starting a second X server (e.g. with gnome's switch user feature, or presumably with startx -- :1) still screws it up. With Edgy's 2.6.17 kernel, CTRL+ALT+Backspace to shut down the X server (so gdb restarts it) didn't help. The restarted X server outputs the same bad video. (I haven't tested that now because I unwisely started bonnie++ in a gnome-terminal tab on my 500GB WD RE2 hard drive, and it will probably take another 20 hours...) Further observations with 2.6.19: While switched to a text console, x11vnc shows a corner of the screen tiled across the whole 1024x768 . This doesn't work properly on other machines with other drivers; e.g. nvidia (proprietary) on i386 Edgy. This probably can't work because the X server can't hold onto the video RAM where the image is if another X server is going to be able to start. With 2.6.17 and 2.6.19, glx is a little flaky. [EMAIL PROTECTED]:~$ glxgears libGL warning: 3D driver claims to not support visual 0x5a but it does work. So do other opengl apps, like xmoto. (I've attached output of glxinfo). Sometimes trying to run an opengl program fails, and there's even a kernel log message: [48096.418558] [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed I'll attach my Xorg.0.log, too. The splash boot video is kind of corrupted (mostly gray, not full colour), even with 2.6.19. The difference I saw with switching to tty1 and back might just have been because I took the splash option out of my grub menu.lst before the reboot with the new kernel. The boot splash is fine with the i386 Edgy CD, but not the amd64 CD. (unsurprisingly, it's the same booting from the AMD64 CD as with the splash option after the install.) So I'm booting with a colour VGA+ 80x25 console. fbcon and vesafb are loaded, but their use count is zero, and there's nothing the the kernel log about switching to an fb console. OTOH, the console font does change to a very spindly one after some boot scripts run. But fbset says no such device opening /dev/fb0, so I guess it's real text mode. Anyway, booting without the splash fixes VT switching, except for switching between two X servers. Actually starting the second X server worked ok, just switching back screwed things up. I think that's about it. Xv works. DDC works when I plug my monitor straight into the mobo. Intel DG965WH boards are pretty nice... And since it's made by Intel, if the VBE BIOS needs some fixes, they are hopefully actually likely to do something (right?). ** Attachment added: output of glxinfo http://librarian.launchpad.net/5335645/glxinfo.txt -- 965/x3000 video not supported https://launchpad.net/bugs/61951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61951] Re: 965/x3000 video not supported
one other note: hibernate and suspend work out of the box on AMD64 Edgy on the DG965WH :). IIRC, suspend/resume screwed up the video with the old kernel with splash boot. (with the same unsynced output, which my monitor's OSD measures as 60Hz vert, 48.3kHz horiz.) ** Attachment added: Xorg.0.log, including openGL error. http://librarian.launchpad.net/5335686/Xorg.0.log -- 965/x3000 video not supported https://launchpad.net/bugs/61951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61951] Re: 965/x3000 video not supported
** Attachment added: kernel log http://librarian.launchpad.net/5335698/dmesg -- 965/x3000 video not supported https://launchpad.net/bugs/61951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44958] Re: Use p7zip for RAR archives?
I checked out the situation on my new AMD64 Edgy system. unrar-free can't even extract uncompressed files from rar archives created with rar 3.0. 7z can get the uncompressed files (method m0g), but can't extract the compressed files (e.g. method m3g). So it does look like 7z is better. unrar (non-free) is available (now, if it wasn't before) in multiverse, and works even on compressed rar 3.0 files (e.g. v2.9, compression method m3g). [EMAIL PROTECTED]:~$ file /usr/bin/unrar /usr/bin/unrar: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, stripped unrar is non-free, but open source, so it should be available on any arch. Still, using 7z for Free rar support would be an improvement. -- Use p7zip for RAR archives? https://launchpad.net/bugs/44958 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66278] Re: Bug#393079: update-grub: savedefault can cause problems
On Sun, Oct 15, 2006 at 12:02:14PM +0200, Robert Millan wrote: Btw, your Mail-followup-to header screwed my reply. Please don't use that header when submitting bugs to BTS. Sorry; I used Ubuntu's reportbug and then changed some headers without realizing all the headers it sets. Hopefully I'm not causing more problems by CC'ing Ubuntu's BTS on this. : Also sorry for the delay; enough computer problems at work that I didn't want to look at this one again :( On Sun, Oct 15, 2006 at 12:00:39PM +0200, Robert Millan wrote: On Sat, Oct 14, 2006 at 06:08:03PM -0300, Peter Cordes wrote: So I don't know where grub could save defaults to, and I'm not shocked that savedefault doesn't work. I've always been suspicious about by default writing to the hard drive while booting, but this is the first time savedefault has ever actually caused a problem. My opinion is that it's not such a great default. The standard grub menu.lst doesn't use the saved default anyway. I would suggest making savedefault another automagic-comment configurable item, defaulting to off. Yes indeed, savedefault is implemented by writing into MBR. Unfortunately, we had to diverge from upstream on this, and it resulted into a handful of problems I'd rather not get into. Given that it's not enabled by default, though, I think it's safe to do another release with it. It actually is enabled by default. It's the savedefault in every entry that's the problem, not when reading it by specifying default saved. update-grub always writes savedefault in every entry (except the alternate ones), right? Maybe update-grub could have an option for including savedefault or not, or it could include it only if it sees a default saved or fallback saved? That sounds likely to confuse anyone who actually wanted to figure out what was going on, but might just work for more people. The error message I included was for Ubuntu's default boot menu, which has no noticeable difference from Debian's. (no surprise there...) For etch+1 this will all be taken over by GRUB 2. Happy hacking :) -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces! -- Plautus, 200 BC -- update-grub: savedefault can cause problems https://launchpad.net/bugs/66278 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55706] python-uncertainities python2.3/2.4 breakage.
Public bug reported: Binary package hint: python-uncertainities On a fresh install of Dapper Drake (i386), installed from the live DVD: $ sudo aptitude install python-uncertainities ... Setting up python-uncertainities (0.001-3.1ubuntu1) ... /var/lib/dpkg/info/python-uncertainities.postinst: line 20: /usr/bin/python2.3: No such file or directory dpkg: error processing python-uncertainities (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: python-uncertainities E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up python-uncertainities (0.001-3.1ubuntu1) ... /var/lib/dpkg/info/python-uncertainities.postinst: line 20: /usr/bin/python2.3: No such file or directory dpkg: error processing python-uncertainities (--configure): subprocess post-installation script returned error exit status 1 The package claims Depends: on python2.4, but installs into /usr/lib/python2.3. The postinst checks whether it should run python2.3 or python2.4, or whatever, by using dpkg --listfiles and seeing what python directory it uses. I guess a package with a typo in its name doesn't have much to live up to... ** Affects: python-uncertainities (Ubuntu) Importance: Untriaged Status: Unconfirmed -- python-uncertainities python2.3/2.4 breakage. https://launchpad.net/bugs/55706 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 13851] ubiquity
ubiquity doesn't handle the grub+xfs thing at all, it just crashes. I booted the i386 live DVD on a laptop, and shrunk the windows partition, then used the install menu item. I don't think I did anything to confuse ubiquity, but I hadn't used it before. (I'm used to installing Debian with the debian-installer menu interface, but I wanted to try this install thing in the menu...) Anyway, I made / and /home XFS, and I didn't use a /boot. Ubiquity died right at the end, with no warning that I could have a GRUB+XFS problem. (At least I don't think it warned. Maybe it did, but it wasn't very emphatic about it, so it sounded like it wouldn't hurt to try.) In any case it shouldn't crash, it should recognize that grub failed. I saved the error logs and stuff, so I can create a new bug # if you want. I thought there looked like plenty of bugs open already about the installer crashing. -- Grub will not install to XFS Formatted Partition https://launchpad.net/bugs/13851 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
