Bug#602853: Workaround documented in errata
On Tue, Feb 1, 2011 at 14:59:37 +0100, Julien Cristau wrote: On Tue, Feb 1, 2011 at 08:14:05 +, Jurij Smakov wrote: Thanks for providing a patch, it has been on my todo list for a while, however I was not able to find time to take care of it so far. One of the users affected by this problem has confirmed that booting with 'video=atyfb:off' provides a workaround for this issue [0]. It has now been (or should be) documented in release errata [1]. [0] http://bugs.debian.org/609466 [1] http://lists.debian.org/debian-boot/2011/01/msg01001.html I can't see that on http://www.debian.org/devel/debian-installer/errata, did that get missed? That's the errata for d-i. I'll push something similar to the release notes for squeeze. Thanks. Committed the following. Cheers, Julien diff --git a/en/issues.dbk b/en/issues.dbk index 398c6ff..06497a6 100644 --- a/en/issues.dbk +++ b/en/issues.dbk @@ -290,6 +290,21 @@ works for literalroot/literal. /para /section +section arch=sparc + !-- bug#602853 -- + titleBoot hangs on certain SPARC systems/title + para +Systems using aty graphics cards (for example, Ultra 10) may not boot +correctly, with kernel freezing early in the boot stage with last message +quoteconsole [tty0] enabled, bootconsole disabled/quote. The issue +may be worked around by adding a kernel boot parameter +literalvideo=atyfb:off/literal to turn off the framebuffer during +boot, which allows the installer (and regular kernel) to be booted on such +systems. A fixed kernel should be available in the first update to +releasename; (Debian 6.0.1). + /para +/section + /section section id=apache2 condition=fixme signature.asc Description: Digital signature
Bug#602853: Workaround documented in errata
On Tue, Feb 1, 2011 at 08:14:05 +, Jurij Smakov wrote: Thanks for providing a patch, it has been on my todo list for a while, however I was not able to find time to take care of it so far. One of the users affected by this problem has confirmed that booting with 'video=atyfb:off' provides a workaround for this issue [0]. It has now been (or should be) documented in release errata [1]. [0] http://bugs.debian.org/609466 [1] http://lists.debian.org/debian-boot/2011/01/msg01001.html That's the errata for d-i. I'll push something similar to the release notes for squeeze. Thanks. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#608253: [Pkg-xen-devel] Release notes addition for Xen support in Debian
On Tue, Jan 25, 2011 at 15:34:23 +, Justin B Rye wrote: # para # Upgrades from Lenny will not automatically install Xen version 4.0. Instead # you need to install Xen 4.0 and a corresponding dom0 kernel explicitly. See # the wiki page for instructions on how to set up the Xen hypervisor and dom0 # kernel under Squeeze. # /para Is this actually true? Don't the xen-linux-system-2.6-xen-* metapackages take care of this upgrade? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#608253: [Pkg-xen-devel] Release notes addition for Xen support in Debian
On Sat, Jan 29, 2011 at 17:32:51 +, Ian Campbell wrote: BTW, why do we refer users to the wiki instead of including the advice inline in the release notes? Is that just the way the release notes are normally written? No, if the information can reasonably be included inline then we should do that. Pointing at other sources for more information is ok, but basic instructions should be included in the release notes directly, IMO. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#568088: cdrom: Debian does not boot right after installation
reassign 568088 linux-2.6 2.6.26-21 severity 568088 important tag 568088 moreinfo kthxbye On Mon, Feb 1, 2010 at 22:46:28 +0100, Volodymyr Shcherbyna wrote: Package: cdrom Severity: critical Justification: breaks the whole system After installation of debian 5.0.3 x64 the OS does not boot. If I load kernel with noapic nolapic acpi=off ide=nodma it works. Should you have any questions about my configuration does not hesitate to ask ;) On Tue, Feb 2, 2010 at 12:40:32 +0100, Volodymyr Shcherbyna wrote: I was able to isolate the issue. My system freezes and only acpi=off makes it possible to boot. My system configuration is: Asus P5QL Pro Intel Core 2 Quad 2.5 Ghz I used latest stable netinstaller for 5.0.3 Debian, x64. Does this still occur? If yes, can you provide kernel logs? At which point in the boot does the system hang? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#607368: Please decide how kernel ABI should be managed
On Sun, Dec 19, 2010 at 19:30:58 +0100, Julien BLACHE wrote: I think it would be best if this matter would be decided upon before the release of Squeeze, or not too long after it, so as to avoid further breakages in early kernel updates for Squeeze. We're getting close to the squeeze release. Is the technical committee going to reach a decision on this? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#610851: base: Crash at boot time
reassign 610851 linux-2.6 severity 610851 important kthxbye On Sun, Jan 23, 2011 at 12:25:10 +0100, Charles-Henry Houdemer wrote: Package: base Severity: critical Justification: breaks the whole system Hello, I have a rather serious problem here appearing after a fresh install. It happens that my system crashes at boot time. But it does so intermitently. First I will (try to) describe the symptoms, then the suspected culprit and finally an ugly way to fix it. So the symptoms : Sometimes (around 3/4 times) my debian crashes when I try to boot it. To be more precise, it happens as soon as just after the first fsck and might happen a bit later. All that I can say is that a segmentation fault appears along with its trace. And then it is impossible to do anything except a hard reboot directly on the machine or with a sysrq. The suspected culprit : My ati 4870X2. My suspitions went on it because even updating the whole system the problem remained. And also because it could not have been a problem coming from the installer as it was used to install the same debian on my laptop without problem. And also because the problem appeared again after a second installation. An ugly fix : My suspitions on the graphic card, I wondered if the absence of the proprietary firmware could be the cause. So I installed them. And the problem disappeared (~10 reboots without any problem). Just to be sure, I tried to remove them. And the problem is back. So if you want any additional information, I am ready to do (nearly) anything possible to help you. Have a nice day. Please capture the kernel logs from this error, and/or the console output (e.g. with a camera). Cheers, Julien signature.asc Description: Digital signature
Bug#610644: linux-image-2.6.32-5-amd64 oopses when using Matlab
On Thu, Jan 20, 2011 at 19:37:08 +0100, ant...@free.fr wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Hi, I have a problem with Linux oopsing when using Matlab. I was able to catch the following log Can you reproduce without using aufs? Cheers, Julien signature.asc Description: Digital signature
Bug#609961: linux-headers-2.6.32-5-common: scripts symlink breaks module compiling when /usr/src is symlink
On Sat, Jan 15, 2011 at 01:28:53 +1300, James Hook wrote: There are two fixes for this (for anyone who stumbles across this error): 1. Fix the symlinks in /mnt/mythtv/src/linux-headers-2.6.32-5-common to be absoultly linked to /usr/lib not ../../lib. 2. In the directory above the physical source directory add a symlink for lib back to /usr/lib Or simply use a bind mount instead of symlinks. Cheers, Julien signature.asc Description: Digital signature
Bug#593683: fixed as far as I'm concerned
user release.debian@packages.debian.org usertag 593683 squeeze-can-defer tag 593683 squeeze-ignore kthxbye As far as I'm concerned this is fixed. Not closing again because waldi reopened it, but tagging as not a blocker. Cheers, Julien signature.asc Description: Digital signature
Bug#609615: linux-2.6: please do not build in nvidiafb on powerpc systems
Michel, as our resident powerpc + graphics expert, any advice about the below? On Tue, Jan 11, 2011 at 02:11:06 +, Ben Hutchings wrote: On Tue, 2011-01-11 at 02:58 +0100, Julien Cristau wrote: On Tue, Jan 11, 2011 at 01:53:53 +, Ben Hutchings wrote: On Mon, 2011-01-10 at 22:58 +, Daniel Kahn Gillmor wrote: Package: linux-2.6 Severity: normal in http://bugs.debian.org/608846 , i encountered difficulties with an NVIDIA chipset on powerpc. These difficulties appear to be exacerbated by the fact that debian's powerpc kernel has set CONFIG_FB_NVIDIA=y Please set this option to 'm' for powerpc (this course of action was suggested by jcristau on #debian-x, who helped me find a workaround to the earlier problem). Thanks for maintaining the Linux kernel in debian, As I understand it, we cannot rely on VGA text-mode or a common firmware interface as a basis for the console on PowerPC. This means we must have a suitable framebuffer driver loaded even before loading the initramfs, so most such drivers are built-in. offb should work, [...] On a PowerMac, yes, but I thought the PowerPC port supported PReP and CHRP machines too. Perhaps we should have offb and vga16fb built-in, and that would cover them all? Thanks, Julien signature.asc Description: Digital signature
Bug#609615: linux-2.6: please do not build in nvidiafb on powerpc systems
On Tue, Jan 11, 2011 at 01:53:53 +, Ben Hutchings wrote: On Mon, 2011-01-10 at 22:58 +, Daniel Kahn Gillmor wrote: Package: linux-2.6 Severity: normal in http://bugs.debian.org/608846 , i encountered difficulties with an NVIDIA chipset on powerpc. These difficulties appear to be exacerbated by the fact that debian's powerpc kernel has set CONFIG_FB_NVIDIA=y Please set this option to 'm' for powerpc (this course of action was suggested by jcristau on #debian-x, who helped me find a workaround to the earlier problem). Thanks for maintaining the Linux kernel in debian, As I understand it, we cannot rely on VGA text-mode or a common firmware interface as a basis for the console on PowerPC. This means we must have a suitable framebuffer driver loaded even before loading the initramfs, so most such drivers are built-in. offb should work, and framebuffer handoff between such a driver and a kms driver works (or can be made to work); and indeed dkg managed to get nouveau kms going after turning off nvidiafb on .37. At boot fbcon is on offb, when udev starts it switches to nouveau. That handoff doesn't work for hw drivers like nvidiafb or radeonfb, it's restricted to generic ones such as efifb/offb/vesafb/vga16fb. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#609330: release-notes: update-grub seems not to be called by the kernel upon upgrade
tag 609330 - squeeze reassign 609330 linux-2.6 unarchive 593683 found 593683 2.6.32-29 forcemerge 593683 609330 kthxbye On Sat, Jan 8, 2011 at 17:37:30 +0100, Philipp Kern wrote: Package: release-notes Severity: normal Hi, I just tried to upgrade a system following the release notes to the letter. This means doing first apt-get upgrade, then installing a new kernel and udev, reboot, then doing a full dist-upgrade. After reboot only the *old* kernel was present in the grub menu, not the new one. grub2 (to replace the installed grub1) was only installed *after* the reboot during the dist-upgrade. (So I did upgrade, install linux and udev, reboot, update-grub, reboot, dist-upgrade instead.) After the installation of grub2 I properly get a hook in /etc/kernel/postinst.d to call update-grub. Is it possible that you should either update grub2 more early in the process or run update-grub manually after the kernel installation and before the reboot? It's not entirely clear to me how it's supposed to happen or if it's just user error in the configuration files of the Lenny installation that was upgraded. waldi says the kernel should break pre-policy versions of bootloader packages, and apparently grub was missed. Cheers, Julien signature.asc Description: Digital signature
Bug#608185: btrfs-tools: balance tree action should be only triggered by root
user release.debian@packages.debian.org usertag 608185 squeeze-can-defer tag 608185 squeeze-ignore kthxbye On Tue, Dec 28, 2010 at 21:53:06 +0800, Aron Xu wrote: Package: btrfs-tools Version: 0.19+20100601-3, 0.19+20101101-1 Severity: serious Balance tree action of btrfs command should be limited to only root user, because it may cause data corrupt and usually result in an uninterruptible process which is causing a heavy I/O load (the process may keep runing for a long time because the action is not a easy deal). This can be fixed post release through security if necessary, so not a blocker for squeeze. Tagging accordingly. Cheers, Julien signature.asc Description: Digital signature
Bug#576274: Possible Bug Fix?
On Thu, Jan 6, 2011 at 02:55:25 +, Ben Hutchings wrote: The correct driver is 'intel' I don't how why you ended up with 'i810', but in any case that would be a bug in xdebconfigurator, not the kernel. Possibly 'i810' just works as an alias for 'intel'. Yes, i810 is the old name for the driver. Lenny has: lrwxrwxrwx 1 root root 12 Sep 5 01:42 /usr/lib/xorg/modules/drivers/i810_drv.so - intel_drv.so In later versions that compat symlink was removed, and the xserver-xorg maintainer scripts make the corresponding update in xorg.conf. Cheers, Julien signature.asc Description: Digital signature
Bug#603957: linux-2.6: consider raising CONFIG_HZ to 1000
On Thu, Nov 18, 2010 at 22:08:27 +0100, Julien Cristau wrote: I think I mentioned this a while back on irc, but filing here for reference. clock_gettime(CLOCK_MONOTONIC) is expensive, so people want to use CLOCK_MONOTONIC_COARSE instead. See e.g. http://lists.x.org/pipermail/xorg-devel/2010-August/012483.html However X would like millisecond granularity, which means HZ=1000 instead of the current 250, in order to be able to use the coarse timer. Maybe something to consider for wheezy? Patch is now in xserver master: http://cgit.freedesktop.org/xorg/xserver/commit/?id=44adb31bfece29260a9bbd9075c9212ebf00d24d It only uses CLOCK_MONOTONIC_COARSE if its resolution is sub-millisecond. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#607242: syslog shows messages from psmouse.c
reassign 607242 linux-2.6 kthxbye Reassigning to the kernel as this doesn't look like an X bug in any case. On Thu, Dec 23, 2010 at 23:34:48 +0530, shirish शिरीष wrote: In-line :- On Thu, Dec 23, 2010 at 23:05, Jim Hill gjth...@gmail.com wrote: I'm getting this too. Here's the tail of my syslog. The parity messages make me kinda suspect failing hardware. snipped Thank you gjthill for also giving me one place to look. I also took a look there and found this out. Dec 23 19:07:48 deb-home kernel: [ 1354.471364] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Dec 23 20:11:26 deb-home kernel: [ 5172.509267] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Dec 23 21:51:15 deb-home kernel: [11161.670849] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Dec 23 22:15:34 deb-home kernel: [12620.856362] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Dec 23 22:42:55 deb-home kernel: [14261.187782] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Although there are no bad parity statements in my syslog. If needed can attach the syslog as well. On Thu, Dec 23, 2010 at 10:36:20 -0800, Jim Hill wrote: Okay, digging it seems this is a common hardware problem that Windows solves by ignoring: https://bugzilla.kernel.org/show_bug.cgi?id=6105 Linux does too since 2.6.34: $ git describe 6b9d363c49d22395d0cf8729c5963f83cfbb6d69 v2.6.34-rc1-31-g6b9d363 Not sure this is what shirish is seeing since he doesn't get the parity error message, but it's either a kernel bug or hardware fail as far as I can tell. Thanks for digging this up though. Cheers, Julien signature.asc Description: Digital signature
Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure
On Wed, Oct 6, 2010 at 22:54:03 +0100, Ben Hutchings wrote: On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote: Package: linux-2.6 Version: 2.6.32-23 Severity: normal iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot, because it was unhappy after resume. You also told me that this machine had no swap enabled, which is an unusual configuration and restricts the ability of the VM to defragment memory. I got the error again today (on 2.6.32-27, with 40 days uptime), and this time I tried to create a swap file and then reload the module. That seems to have worked. If you don't want to go ahead with the patch you proposed for this in squeeze, feel free to close as fixed, since AIUI that allocation was reduced in newer kernels. Cheers, Julien signature.asc Description: Digital signature
Bug#607484: upgrade-reports: unusable on intel i810
On Mon, Dec 20, 2010 at 22:58:05 +0100, relat...@gmx.net wrote: the upstream bug is: https://bugs.freedesktop.org/show_bug.cgi?id=26345 as you can see in the report this was reported many times and appears to affect all 845G chipsets, so please do not ship squeeze without a fix or the following workaround. it took me about 30 reboots to figure this out. the workaround is: Option Shadow true in the xorg.conf Device section. Shadow is enabled by default on 845, so that shouldn't make any difference. Cheers, Julien signature.asc Description: Digital signature
Re: old kernel packages
On Fri, Dec 10, 2010 at 19:17:43 +0100, folkert wrote: Hi, I'm looking for old kernel debian images to track down in which kernel some problem with rs232 handling was introduced. I'm looking for kernel images starting at 2.16.18 upto 2.6.26 (but of course not including as it is on the web), i386 images. Where can I find these? http://snapshot.debian.org/package/linux-2.6/ Cheers, Julien signature.asc Description: Digital signature
Re: Bug#604814: upgrade-reports: Upgrade lenny to squeeze mostly successful
On Wed, Nov 24, 2010 at 14:53:59 +0100, David Kuehling wrote:
Some warnings were printed during upgrade:
***
update-initramfs: Generating /boot/initrd.img-2.6.26-2-686
cryptsetup: WARNING: target sda2_crypt has a random key, skipped
/tmp/mkinitramfs_vkMxi2/scripts/local-top/cryptroot: line 11: [: too many
arguments
***
No problems so far, my crypto-root is booting without problems.
1 #!/bin/sh
2
3 #
4 # Standard initramfs preamble
5 #
6 prereqs()
7 {
8 # Make sure that cryptroot is run last in local-top
9 for req in $(dirname $0)/*; do
10 script=${req##*/}
11 if [ $script != cryptroot ]; then
12 echo $script
13 fi
14 done
15 }
16
17 case $1 in
18 prereqs)
19 prereqs
20 exit 0
Weird. Maybe the cryptsetup or initramfs-tools maintainer will have an
idea.
Cheers,
Julien
signature.asc
Description: Digital signature
Re: Bug#604814: upgrade-reports: Upgrade lenny to squeeze mostly successful
On Wed, Nov 24, 2010 at 14:50:08 +, maximilian attems wrote: On Wed, Nov 24, 2010 at 14:53:59 +0100, David Kuehling wrote: Some warnings were printed during upgrade: *** update-initramfs: Generating /boot/initrd.img-2.6.26-2-686 cryptsetup: WARNING: target sda2_crypt has a random key, skipped /tmp/mkinitramfs_vkMxi2/scripts/local-top/cryptroot: line 11: [: too many arguments *** fix for the second line was added in 2:1.1.0-2.1 it actively breaks initramfs build. Thus should initramfs-tools grow a breaks for cryptsetup below that version? That would probably help getting these packages upgraded in the right order. Thanks. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#604459: libdrm-nouveau1: fresh install with Squeeze Beta 1 netinst-amd64 results in hang on boot on MacBook 5, 3
reassign 604459 linux-2.6 2.6.32-27 tag 604459 moreinfo kthxbye On Mon, Nov 22, 2010 at 04:21:13 -0700, Nicholas Holley wrote: Package: libdrm-nouveau1 Version: 2.4.21-1~squeeze3 Severity: important After installing Squeeze Beta 1 using the netinst-amd64 image, I was unuable to boot past nouveau. My laptop would hang and require a restart. The issue was resolved by specifying nouveau.noaccel=1 in Grub. Please attach your kernel log, lspci -nn and Xorg log. Cheers, Julien signature.asc Description: Digital signature
Re: Minutes of the Debian linux-2.6 Group Meeting
On Thu, Nov 18, 2010 at 11:23:39 -0800, Kees Cook wrote: On Thu, Nov 11, 2010 at 13:52:12 +, maximilian attems wrote: LSM: Enable AppArmor? as well as/instead of Tomoyo? --- As the LSM need to be built we can't enable them. This needs a technical solution were code can be disregarded as init sections or similar. AppArmor seems more popular as Opensuse and Ubuntu uses it. Technicaly Tomoyo is said to be cleaner. What do you mean by can't here? You can build _all_ of them, actually. The active LSM is just selected at boot-time through the kernel command line arguments. If it's a concern over kernel size, upstream specifically removed the ability to make the LSM modular, so this means that no additional LSMs will ever be available in Debian? See the second sentence. This needs a technical solution where code can be disregarded as init sections or similar. So your kernel has a bunch of LSMs builtin, but at boot time one of them is selected and you release the memory taken by the rest of them instead of keeping the code lying there unused. Cheers, Julien signature.asc Description: Digital signature
Bug#603957: linux-2.6: consider raising CONFIG_HZ to 1000
Package: linux-2.6 Version: 2.6.32-27 Severity: wishlist Hi, I think I mentioned this a while back on irc, but filing here for reference. clock_gettime(CLOCK_MONOTONIC) is expensive, so people want to use CLOCK_MONOTONIC_COARSE instead. See e.g. http://lists.x.org/pipermail/xorg-devel/2010-August/012483.html However X would like millisecond granularity, which means HZ=1000 instead of the current 250, in order to be able to use the coarse timer. Maybe something to consider for wheezy? Cheers, Julien -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Re: Bug#603469: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back
reassign 603469 linux-2.6 2.6.32-27 kthxbye On Sun, Nov 14, 2010 at 14:32:40 +0100, lauren wrote: Package: xserver-xorg-video-ati Version: 1:6.13.1-2 Severity: important after some random time period my screen goes black and nothing i do short of rebooting can bring it back ... i have gotten quite good at switching to a new console and logging in and rebooting without being able to see what i'm doing btw the system is still running normally but no display at all i am using the open source ati driver with a Thinkpad T500 ... KMS is enabled and the DRM module is loading correctly [...] [ 949.420558] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting [ 949.420570] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing F6D8 (len 487, WS 0, PS 4) @ 0xF719 Sounds like a kernel issue, reassigning. Is this reproducible with 2.6.36 (available in experimental). Cheers, Julien signature.asc Description: Digital signature
Bug#603158: [fwd] Re: [oss-security] CVE request: kernel: possible kernel oops from user MSS
retitle 603158 CVE-2010-4165: possible kernel oops from user MSS kthxbye fyi, CVE assigned Cheers, Julien - Forwarded message from Josh Bressers bress...@redhat.com - From: Josh Bressers bress...@redhat.com Reply-To: oss-secur...@lists.openwall.com Date: Fri, 12 Nov 2010 08:19:57 -0500 (EST) To: oss-secur...@lists.openwall.com Cc: Steven M. Christey co...@linus.mitre.org Subject: Re: [oss-security] CVE request: kernel: possible kernel oops from user MSS Message-ID: 1301976200.802341289567997556.javamail.r...@zmail01.collab.prod.int.phx2.redhat.com - Eugene Teo eug...@redhat.com wrote: With commit f5fff5dc8a7a3f395b0525c02ba92c95d42b7390, a user program can pass in TCP_MAXSEG of 12 (or TCPOLEN_TSTAMP_ALIGNED), and cause kernel oops with division by 0 in tcp_select_initial_window. Proposed patch: http://www.spinics.net/lists/netdev/msg146495.html Reference: http://www.spinics.net/lists/netdev/msg146405.html Please use CVE-2010-4165. Thanks. -- JB - End forwarded message - signature.asc Description: Digital signature
Bug#601997: base: Irregular sync flashes on 8086:2a42
On Sun, Oct 31, 2010 at 16:33:49 +, Russel Winder wrote: Package: base Severity: normal A report was filed on Launchpad against Ubuntu Lucid reporting that the kernel upgrade from Karmic to Lucid introduced irregular sync flashes on the screen. cf. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/538648. The problem reported there is also seeming to affect Debian Squeeze. The upgrade to Ubuntu Maverick has caused the problem to go away when using that OS. Sadly though the problem still afflicts Debian Squeeze. Is there any way the information from the Ubuntu-oriented investigation can be applied to Debian Squeeze? The ubuntu bug doesn't seem to point to a fix (or it's to much of a mess for me to find it). Somebody would have to bisect between 2.6.33 and a fixed kernel to find out what fixed this, I guess. Cheers, Julien signature.asc Description: Digital signature
Bug#602095: linux-image-2.6.32-5-amd64: black screen after boot - conflict with Nouveau driver
On Mon, Nov 1, 2010 at 17:20:49 +, Julien Tailleur wrote: Everything went smoothly but after reboot I had a black screen and nothing happening (shortly after grub). I looked around and found bug #580894 in which someone said that there was a conflict between the nvidia driver and the nouveau driver. At this time I had not installed the nvidia driver so I thought it should not be this bug but I thought that maybe there was something wrong with the nouveau driver. I thus blacklisted it and installed the nvidia instead, and things work fine now. Please remove the nvidia driver, unblacklist nouveau, and attach the resulting dmesg. Thanks, Julien signature.asc Description: Digital signature
Bug#601962: linux-image-2.6.32-5-amd64: removal fails in a clean chroot
On Sun, Oct 31, 2010 at 12:46:55 +0100, Lucas Nussbaum wrote: Removing linux-image-2.6.32-5-amd64 in a clean chroot fails: # apt-get remove --purge linux-image-2.6.32-5-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-2.6.32-5-amd64* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 99.0 MB disk space will be freed. Do you want to continue [Y/n]? (Reading database ... 9662 files and directories currently installed.) Removing linux-image-2.6.32-5-amd64 ... dpkg: error processing linux-image-2.6.32-5-amd64 (--purge): subprocess installed pre-removal script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: linux-image-2.6.32-5-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Any chance you can test that with set -x? Cheers, Julien signature.asc Description: Digital signature
Bug#577747: linux-image-2.6.32-5-amd64 - same bug, different HW
On Mon, Oct 25, 2010 at 22:25:15 +0100, Ben Hutchings wrote:
Please build and install a kernel package with the attached patch,
following the instructions at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
and then try disabling TSO using the ethtool command
('ethtool -K eth0 tso off').
Forgot to attach the patch?
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#599877: Please enable FANOTIFY
On Tue, Oct 12, 2010 at 03:23:24 +0200, Michael Biebl wrote: Package: linux-2.6 Version: 2.6.36~rc6-1~experimental.1 Severity: wishlist File: /boot/config-2.6.36-rc6-686 Hi, I'd like to test a new readahead implementation which uses the new fanotify mechanism. Please consider enabling CONFIG_FANOTIFY Looks like the fanotify syscalls were pulled from .36 (http://lwn.net/Articles/409681/). Cheers, Julien signature.asc Description: Digital signature
Bug#599927: Kernel crashes when I start X on my Dell Latitude D505
On Wed, Oct 13, 2010 at 13:45:13 +0200, Petter Reinholdtsen wrote: reassign 599927 linux-2.6 found 599927 2.6.32-23 thanks [Ben Hutchings] This is extremely short on information. Please use reportbug. Sure. Here is the info collected by reportbug. Assume it also include the kernel log Julien asked for. This is a freshly installed Squeeze system. What more can I do to test and try to pinpoint the problem? Install the kernel and xserver-xorg-video-intel from sid. Cheers, Julien signature.asc Description: Digital signature
Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure
On Sun, Oct 10, 2010 at 20:03:13 +0100, Ben Hutchings wrote: On Thu, 2010-10-07 at 09:51 +0200, Johannes Berg wrote: On Wed, 2010-10-06 at 22:54 +0100, Ben Hutchings wrote: On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote: Package: linux-2.6 Version: 2.6.32-23 Oct 6 21:05:02 radis kernel: [378665.326381] NetworkManager: page allocation failure. order:4, mode:0x40d0 Oct 6 21:05:02 radis kernel: [378665.326393] Pid: 2, comm: NetworkManager Not tainted 2.6.32-5-amd64 #1 [...] Oct 6 21:05:02 radis kernel: [378665.363630] iwlagn :0c:00.0: kmalloc for auxiliary BD structures failed [...] This particular allocation is for an array which is not used for DMA and therefore could be stored in non-contiguous pages allocated with vmalloc(). But there may be some good reason not to do this. I have, however much more recently than that kernel, cleaned this up in commit ff0d91c3eea6e25b47258349b455671f98f1b0cd -- this particular allocation is now 2048 or 4096 bytes depending on the architecture (32 vs 64 bit pointers). If you want to backport this, there are two or three more commits right before it that would probably be required. It seems like we can get away with a much smaller change though. Julien, could you test this patch? Getting lots of those in dmesg: iwlagn :0c:00.0: Too many chunks: 2 Doesn't seem to prevent the network from working though. Cheers, Julien signature.asc Description: Digital signature
Bug#599927: Kernel crashes when I start X on my Dell Latitude D505
On Tue, Oct 12, 2010 at 15:34:16 +0200, Petter Reinholdtsen wrote: Package: linux-image-2.6.32-5-686 Version: 2.6.32-23 Severity: important The X server involved is as far as I know xserver-xorg-video-intel version 2:2.9.1-4. When I install the current Squeeze on my test laptop, a Dell Latitude D505, starting kdm kill the machine. This is what happen when I start X manually when logged in via ssh: r...@pxe-test0-pre:~# X X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-686 i686 Debian Current Operating System: Linux pxe-test0-pre.uio.no 2.6.32-5-686 #1 SMP Sat Sep 18 02:14:45 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/vg_system-root ro quiet Build Date: 20 September 2010 03:40:46PM xorg-server 2:1.7.7-7 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Oct 12 15:26:01 2010 (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) open /dev/fb0: No such file or directory After this, the network connection is dead and the screen and keyboard on the laptop is black and dead. What hardware is this on? Please provide X and kernel log. Cheers, Julien signature.asc Description: Digital signature
Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure
Package: linux-2.6 Version: 2.6.32-23 Severity: normal iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot, because it was unhappy after resume. Bit of kern.log: Oct 6 21:05:02 radis kernel: [378665.326381] NetworkManager: page allocation failure. order:4, mode:0x40d0 Oct 6 21:05:02 radis kernel: [378665.326393] Pid: 2, comm: NetworkManager Not tainted 2.6.32-5-amd64 #1 Oct 6 21:05:02 radis kernel: [378665.326398] Call Trace: Oct 6 21:05:02 radis kernel: [378665.326417] [810b9f30] ? __alloc_pages_nodemask+0x55b/0x5cf Oct 6 21:05:02 radis kernel: [378665.326427] [810b8f2d] ? __get_free_pages+0x9/0x46 Oct 6 21:05:02 radis kernel: [378665.326461] [a03eaaa7] ? iwl_tx_queue_init+0xf1/0x2e6 [iwlcore] Oct 6 21:05:02 radis kernel: [378665.326477] [a03e981f] ? _iwl_grab_nic_access+0x39/0xbe [iwlcore] Oct 6 21:05:02 radis kernel: [378665.326493] [a03eae13] ? iwl_txq_ctx_reset+0x177/0x1fc [iwlcore] Oct 6 21:05:02 radis kernel: [378665.326510] [a03e4e83] ? iwl_hw_nic_init+0x123/0x142 [iwlcore] Oct 6 21:05:02 radis kernel: [378665.326524] [a04213fe] ? __iwl_up+0x179/0x321 [iwlagn] Oct 6 21:05:02 radis kernel: [378665.326534] [812f99eb] ? _cond_resched+0x24/0x2f Oct 6 21:05:02 radis kernel: [378665.326547] [a0421c2a] ? iwl_mac_start+0x684/0x7f6 [iwlagn] Oct 6 21:05:02 radis kernel: [378665.326558] [810fc23e] ? pollwake+0x53/0x59 Oct 6 21:05:02 radis kernel: [378665.326569] [81049fee] ? default_wake_function+0x0/0x9 Oct 6 21:05:02 radis kernel: [378665.326578] [8103f81e] ? __wake_up+0x30/0x44 Oct 6 21:05:02 radis kernel: [378665.326587] [812691ab] ? netlink_broadcast+0x266/0x29d Oct 6 21:05:02 radis kernel: [378665.326611] [a038f852] ? ieee80211_open+0x27b/0x653 [mac80211] Oct 6 21:05:02 radis kernel: [378665.326629] [a0292498] ? cfg80211_netdev_notifier_call+0x391/0x3a7 [cfg80211] Oct 6 21:05:02 radis kernel: [378665.326642] [8124fe17] ? dev_open+0xa4/0xe6 Oct 6 21:05:02 radis kernel: [378665.326651] [8124f5e2] ? dev_change_flags+0xaf/0x16d Oct 6 21:05:02 radis kernel: [378665.326661] [8125744b] ? do_setlink+0x284/0x351 Oct 6 21:05:02 radis kernel: [378665.326670] [812576d2] ? rtnl_setlink+0x12f/0x144 Oct 6 21:05:02 radis kernel: [378665.326680] [81258462] ? rtnetlink_rcv_msg+0x64/0x1f5 Oct 6 21:05:02 radis kernel: [378665.326688] [812583fe] ? rtnetlink_rcv_msg+0x0/0x1f5 Oct 6 21:05:02 radis kernel: [378665.326696] [81269610] ? netlink_rcv_skb+0x34/0x7c Oct 6 21:05:02 radis kernel: [378665.326704] [812583f8] ? rtnetlink_rcv+0x1f/0x25 Oct 6 21:05:02 radis kernel: [378665.326711] [81269404] ? netlink_unicast+0xe2/0x148 Oct 6 21:05:02 radis kernel: [378665.326719] [81247595] ? __alloc_skb+0x69/0x15a Oct 6 21:05:02 radis kernel: [378665.326727] [81269b30] ? netlink_sendmsg+0x242/0x255 Oct 6 21:05:02 radis kernel: [378665.326738] [8123ff25] ? sock_sendmsg+0xa3/0xbb Oct 6 21:05:02 radis kernel: [378665.326746] [8123fe29] ? sock_recvmsg+0xa6/0xbe Oct 6 21:05:02 radis kernel: [378665.326755] [810649ee] ? autoremove_wake_function+0x0/0x2e Oct 6 21:05:02 radis kernel: [378665.326763] [810649ee] ? autoremove_wake_function+0x0/0x2e Oct 6 21:05:02 radis kernel: [378665.326772] [812488ec] ? verify_iovec+0x46/0x82 Oct 6 21:05:02 radis kernel: [378665.326780] [81240167] ? sys_sendmsg+0x22a/0x2b5 Oct 6 21:05:02 radis kernel: [378665.326789] [812425cb] ? lock_sock_nested+0xa0/0xab Oct 6 21:05:02 radis kernel: [378665.326797] [8104033d] ? set_next_entity+0x34/0x56 Oct 6 21:05:02 radis kernel: [378665.326807] [81010b42] ? system_call_fastpath+0x16/0x1b Oct 6 21:05:02 radis kernel: [378665.326814] Mem-Info: Oct 6 21:05:02 radis kernel: [378665.326818] Node 0 DMA per-cpu: Oct 6 21:05:02 radis kernel: [378665.326825] CPU0: hi:0, btch: 1 usd: 0 Oct 6 21:05:02 radis kernel: [378665.326831] CPU1: hi:0, btch: 1 usd: 0 Oct 6 21:05:02 radis kernel: [378665.326835] Node 0 DMA32 per-cpu: Oct 6 21:05:02 radis kernel: [378665.326841] CPU0: hi: 186, btch: 31 usd: 0 Oct 6 21:05:02 radis kernel: [378665.326847] CPU1: hi: 186, btch: 31 usd: 0 Oct 6 21:05:02 radis kernel: [378665.326860] active_anon:160995 inactive_anon:81502 isolated_anon:1 Oct 6 21:05:02 radis kernel: [378665.326863] active_file:175919 inactive_file:132273 isolated_file:0 Oct 6 21:05:02 radis kernel: [378665.326866] unevictable:26 dirty:167 writeback:0 unstable:0 Oct 6 21:05:02 radis kernel: [378665.326869] free:90365 slab_reclaimable:83403 slab_unreclaimable:19585 Oct 6 21:05:02 radis kernel: [378665.326872] mapped:14852 shmem:8390 pagetables:6025 bounce:0 Oct 6 21:05:02 radis kernel: [378665.326878] Node 0 DMA
Bug#599208: release-notes: drop kernel-package info?
Package: release-notes Severity: minor Tags: squeeze The kernel-metapackage section of the release notes includes this text: para For the more adventurous there is an easy way to compile your own custom kernel on debian;. Install the systemitem role=packagekernel-package/systemitem tool and read the documentation in filename/usr/share/doc/kernel-package/filename. /para AFAIK kernel-package is mostly deprecated these days in favour of the upstream 'make deb-pkg' target. Maybe this should be dropped or updated? (cc:ed to debian-kernel) Cheers, Julien signature.asc Description: Digital signature
Re: Uploading linux-2.6
On Mon, Sep 27, 2010 at 16:57:02 +0100, Ben Hutchings wrote: I intend to upload a new version of linux-2.6 (2.6.32-24) on Tuesday night or Wednesday morning. This will include stable update 2.6.32.23 which has a number of security fixes, therefore urgency will be 'high'. Unblocked. Cheers, Julien signature.asc Description: Digital signature
Re: Missing headers in linux-headers-2.6.32-bpo.5-common
On Thu, Sep 30, 2010 at 18:34:55 +0300, Volkan YAZICI wrote: Excuse my ignorance, but I still couldn't understand why there doesn't exist a bug report page for linux-headers-2.6.32-bpo.5-common. Isn't it officially supported by the Debian GNU/Linux? If so, why is it located in the official repositories? The bug tracking system knows about packages on the main ftp.debian.org archive, not on the backports archive. See 'Report bugs' at http://backports.debian.org/Instructions/#index5h2 Cheers, Julien signature.asc Description: Digital signature
Bug#598644: linux-2.6: README.Debian gets installed in the wrong package
Package: linux-2.6 Version: 2.6.32-24 Severity: minor README.Debian gets installed in linux-tools-2.6.32. It would probably be better to have it in linux-base. Cheers, Julien -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#598492: linux-image-2.6.35-trunk-amd64: suspend/hibernate is totally fucked up
On Thu, Sep 30, 2010 at 21:09:17 +0200, Pierre Habouzit wrote: Okay it seems it still happens with .36 so let's say it's an X bug then. It's a separate issue from what you reported initially, and it doesn't even sound like a bug. Cheers, Julien signature.asc Description: Digital signature
Bug#598312: gdm crashes
On Tue, Sep 28, 2010 at 10:55:16 +0200, Sven Joachim wrote: This means that the Debian kernel from squeeze/sid is not suitable because it has KMS disabled on i845, see #596453. Well, it's suitable for use with the vesa X driver. Cheers, Julien signature.asc Description: Digital signature
Bug#598104: does not load i915 driver [Toshiba Satellite C650]
On Sun, Sep 26, 2010 at 17:47:52 +0200, Mirosław Zalewski wrote: [0.162165] ACPI: EC: Look up EC in DSDT [0.165576] ACPI: Executed 1 blocks of module-level executable AML code [0.167253] ACPI: BIOS _OSI(Linux) query ignored [0.188008] ACPI Error (psargs-0359): [IF1] Namespace lookup failure, AE_NOT_FOUND [0.188013] ACPI Error (psparse-0537): Method parse/execution failed [\FLNK] (Node 8800b723bb40), AE_NOT_FOUND [0.188049] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPC_.LREG] (Node 8800b72443e0), AE_NOT_FOUND [0.188089] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._INI] (Node 8800b723a980), AE_NOT_FOUND [0.188138] ACPI Error: The DSDT has been corrupted or replaced - old, new headers below (20090903/tbutils-372) [0.188142] ACPI: DSDT (null) 094DE (v01 TOSINV TOSINV00 0001 MSFT 0113) [0.188149] ACPI: DSDT (null) 0555C (v01 TOSINV TOSINV00 0001 INTL 20051117) [0.188153] ACPI Error: Please send DMI info to linux-a...@vger.kernel.org [0.188154] If system does not work as expected, please boot with acpi=copy_dsdt (20090903/tbutils-378) [0.188250] ACPI Error (psargs-0359): [ID A] Namespace lookup failure, AE_NOT_FOUND [0.188254] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.P32_._PRW] (Node 8800b7243220), AE_NOT_FOUND [0.188429] ACPI Warning for \_SB_.PCI0.AZAL._PRW: Return type mismatch - found Integer, expected Package (20090903/nspredef-1006) [0.188433] ACPI Error (uteval-0307): Return object type is incorrect [\_SB_.PCI0.AZAL._PRW] (Node 8800b72472c0), AE_TYPE [0.188443] ACPI Error: Type returned from _PRW was incorrect: Integer, expected Btypes: 8 (20090903/uteval-313) [0.188509] ACPI: Interpreter enabled [0.188511] ACPI: (supports S0ACPI Error (psargs-0359): [GPRW] Namespace lookup failure, AE_NOT_FOUND [0.188529] ACPI Error (psparse-0537): Method parse/execution failed [\_GPE._L16] (Node 8800b723a160), AE_NOT_FOUND [0.188574] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L16] (20090903/evgpe-568) [0.188597] S3 S4 S5) [0.188619] ACPI: Using IOAPIC for interrupt routing [0.188629] ACPI Error: Null stack entry at 8800b7316660 (20090903/exresop-175) [0.188634] ACPI Error (psparse-0537): Method parse/execution failed [\_PIC] (Node 8800b723a180), AE_AML_INTERNAL [0.188671] ACPI Exception: AE_AML_INTERNAL, Evaluating _PIC (20090903/bus-828) [0.192382] = [0.192438] BUG Acpi-ParseExt: Objects remaining on kmem_cache_close() [0.192488] - [0.192489] [0.192585] INFO: Slab 0xea00028123d8 objects=56 used=1 fp=0x8800b72ed240 flags=0x180 [0.192641] Pid: 1, comm: swapper Not tainted 2.6.32-5-amd64 #1 [0.192643] Call Trace: [0.192650] [810e423b] ? slab_err+0xba/0xdf [0.192654] [811c60c6] ? acpi_os_vprintf+0x16/0x2c [0.192657] [811c612a] ? acpi_os_printf+0x4e/0x56 [0.192661] [8119404a] ? vsnprintf+0x9e/0x449 [0.192665] [81074bcb] ? generic_exec_single+0x64/0x80 [0.192668] [810e4c54] ? flush_cpu_slab+0x0/0x39 [0.192671] [810e5299] ? list_slab_objects+0xa3/0x16a [0.192674] [810e3f1f] ? add_partial+0x11/0x58 [0.192677] [810e4c3b] ? deactivate_slab+0xb4/0xcd [0.192680] [810e87e1] ? kmem_cache_destroy+0x11d/0x20c [0.192684] [81517d2f] ? acpi_init+0x0/0x2de [0.192687] [811c5936] ? acpi_os_delete_cache+0x9/0xe [0.192691] [811e51c2] ? acpi_ut_delete_caches+0x6c/0x7b [0.192694] [811e63b5] ? acpi_terminate+0x41/0x4c [0.192697] [81517f64] ? acpi_init+0x235/0x2de [0.192699] [81515bf3] ? fbmem_init+0x0/0x98 [0.192703] [8100a065] ? do_one_initcall+0x64/0x174 [0.192707] [814ef66b] ? kernel_init+0x14c/0x1a2 [0.192711] [814ef140] ? early_idt_handler+0x0/0x71 [0.192714] [81011baa] ? child_rip+0xa/0x20 [0.192717] [814ef140] ? early_idt_handler+0x0/0x71 [0.192720] [814ef51f] ? kernel_init+0x0/0x1a2 [0.192722] [81011ba0] ? child_rip+0x0/0x20 [0.192727] INFO: Object 0x8800b72ed288 @offset=648 [0.192776] = [0.192828] BUG Acpi-ParseExt: Objects remaining on kmem_cache_close() [0.192875] - [0.192876] [0.192972] INFO: Slab 0xea0002812170 objects=56 used=1 fp=0x8800b72e22d0 flags=0x180 [0.193027] Pid: 1, comm:
Bug#595103: framebuffer gone for intel i915 starting 2.6.32-21
On Thu, Sep 23, 2010 at 08:59:54 +0800, jida...@jidanni.org wrote: However, until it is fixed, one cannot dream of running X windows. Even just running on the console will eventually lead to a black screen, and the need to reboot, disks having been synced or not. This is not true. You can get X up with vesa just fine. Cheers, Julien signature.asc Description: Digital signature
Bug#597706: linux-image-2.6.32-5-kirkwood: Kernel panic during net initialization
On Wed, Sep 22, 2010 at 13:35:31 +0200, Roland Mas wrote: Uncompressing Linux... done, booting the kernel. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 Thu Aug 26 03:31:56 UTC 2010 That's -21, not -23. Maybe you need to run flash-kernel? Cheers, Julien signature.asc Description: Digital signature
Bug#597132: [linux-2.6] Postinstall Error Leaves Package Partly Installed
reassign 597132 extlinux tag 597132 - unreproducible help moreinfo severity 597132 serious kthxbye On Tue, Sep 21, 2010 at 15:35:59 +0200, Daniel Baumann wrote: reassign 597132 linux-2.6 thanks since squeeze, you're not supposed to have do_bootloader being used. if you're upgrading from lenny, then linux-2.6 needs to take care about that, thus reassigning. NAK, the bug is in extlinux-update, it's writing to stdout, which is owned by debconf. Don't do that. Cheers, Julien signature.asc Description: Digital signature
Bug#581830: still present in linux-2.6 2.6.32-20
On Fri, Aug 13, 2010 at 15:44:39 +0200, Vincent Lefevre wrote: This bug is still present in linux-2.6 2.6.32-20, even though it is fixed upstream. When will the driver be updated in Debian? Do you know what the fix is? The kernel in sid will be updated after squeeze release, in the mean time newer kernels go to experimental. Cheers, Julien signature.asc Description: Digital signature
Bug#596961: [initramfs-tools] missing radeon firmware (from firmware-linux-nonfree) in initramfs
On Wed, Sep 15, 2010 at 17:25:14 +0200, Anarky wrote: I'm sorry if I'm mistaken and wasting your time. Could you provide me some test that I could run to check for sure that the driver is loaded after the root FS has been mounted. zcat /boot/initrd.img-`uname -r` | cpio -t | grep drm This should be empty. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#595521: i915: system locks up when starting X
On Sun, Sep 5, 2010 at 14:09:55 +0100, Edward Allcutt wrote: Kernel-team: to me these two bugs could be merged. Since #594623 is considered grave (same issue reported against X driver), any objection to upping the severity of #595511/#595521 which was downgraded to important by the forcemerge? Yes. We'll sort things out before release, but having 8xx blacklisted from KMS is not a critical kernel bug. Cheers, Julien signature.asc Description: Digital signature
Bug#595103: xwindows gone starting at 2.6.32-21
On Wed, Sep 1, 2010 at 17:35:01 +0800, jida...@jidanni.org wrote: BH == Ben Hutchings b...@decadent.org.uk writes: BH On Wed, 2010-09-01 at 11:38 +0800, jida...@jidanni.org wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: important Upon upgrading to -21 xdm nor nodm will not start. -20 worked fine. /var/log/Xorg.0.log says (EE) open /dev/fb0: No such file or directory (EE) intel(0): No kernel modesetting driver detected. (II) UnloadModule: intel (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found BH [...] BH Which version of xserver-xorg-video-intel are you using? 2:2.12.0+legacy1-1 Indeed, that combined with _your bad kernel_ caused me several times to have to hit the power button, as ALT+CTRL+F1, SysRq... all didn't work. My disks had to be fscked all over again and fsck even exited with value 1 etc. misery. That sounds like #594623. Only after downgrading xserver-xorg-video-intel from 2:2.12.0+legacy1-1 to 2:2.11.0-1. 2.11.0 requires KMS, the 2.6.32-21 kernel blacklists 8xx chips from KMS, so that combination can't work. was I able to even get the above error messages, else nothing was even written to disk. Then I tried downgrading the kernel. That fixed it. So I now upgraded xserver-xorg-video-intel back. Cheers, Julien signature.asc Description: Digital signature
Bug#579017: autodetection fails when booting with 64-bit kernel on 32-bit userland
On Tue, May 4, 2010 at 11:44:29 +0400, Stanislav Maslovski wrote: On Mon, May 03, 2010 at 08:16:50PM +0200, Julien Cristau wrote: reassign 579017 linux-2.6 2.6.32-9 kthxbye On Sat, Apr 24, 2010 at 15:27:11 +0400, Stanislav Maslovski wrote: Package: xserver-xorg-input-synaptics Version: 1.2.2-2 Severity: normal Without giving the explicit options (commented out in my xorg.conf below) the touchpad gets configured in a mouse-emulation mode (no scrolling, etc.) when I boot with a 64-bit kernel on a 32-bit userland. This sounds like a kernel bug. Can you attach the contents of /proc/bus/input/devices for both the 32bit and the 64bit kernel? I seem to remember a similar report a while back, but can't find it now... I have just updated to the last versions of the kernels and udev, and the bug is still there. The devices file from the 64bit kernel lists that strange thing Macintosh mouse button emulation on /devices/virtual/input/input0, which I do not have physically (my laptop is a DELL Vostro 1400) The requested files are attached. 686: I: Bus=0011 Vendor=0002 Product=0008 Version=7325 N: Name=AlpsPS/2 ALPS GlidePoint P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse1 event5? B: EV=f B: KEY=420 0 7000f 0 0 0 0 0 0 0 0 B: REL=3 B: ABS=103 amd64: I: Bus=0011 Vendor=0002 Product=0008 Version=7325 N: Name=AlpsPS/2 ALPS GlidePoint P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input7 U: Uniq= H: Handlers=mouse2 event7? B: EV=f B: KEY=420 7000f 0 0 0 0 B: REL=3 B: ABS=103 The 'KEY' line looks suspicious. From what I can tell the sysfs attributes are exported as an array of longs, which is broken when a long is not the same thing for userspace and kernel. udev detects a touchpad when BTN_TOOL_FINGER (0x145) is set in capabilities/key. When reading '420 7000f 0 0 0 0' as an array of 32-bit quantities, that's not set. Cheers, Julien signature.asc Description: Digital signature
Bug#595016: linux-image-2.6.32-5-amd64: the .deb file doesn't include the hisax isdn modules anymore
On Tue, Aug 31, 2010 at 15:32:56 +0200, Jens R. wrote: Package: linux-2.6 Version: 2.6.32-18 Severity: normal Since linux-image-2.6.32-5-amd64 this package doesn't include the old hisax isdn (and related) modules anymore. As far as I could investigate, there is no hint to this in the changelog, so I assume this happened by mistake. The changelog for 2.6.32-16 says [ Bastian Blank ] * Disable mISDN support for NETJet cards. The driver binds a generic PCI bridge. * Disable ISDN4Linux drivers. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#595033: xserver-xorg-video-ati: Only one display works at a time with RV620 [FirePro 2260] with two DisplayPort output
reassign 595033 linux-2.6 tag 595033 fixed-upstream patch kthxbye On Tue, Aug 31, 2010 at 11:51:33 -0400, Alex Deucher wrote: On Tue, Aug 31, 2010 at 10:59 AM, Thomas PIERSON web.pier...@gmail.com wrote: I have an issue with 2 monitors connected on two DislpayPort output. The card is an ATI FirePro 2260. And only one display can works at a time. $ lspci | grep VGA 02:00.0 VGA compatible controller: ATI Technologies Inc RV620 [FirePro 2260] My issue looks like this archived bug : http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=569970 The symptoms are that only one display can be driven at a time. It also talk about two DisplayPort connections. So, the 2 monitor are connected and activated in clone mode : $ xrandr Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192 DisplayPort-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 408mm x 255mm 1680x1050 60.0 + 1600x1200 60.0 1400x1050 60.0 1280x1024 75.0 60.0* 1440x900 59.9 1280x960 60.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 640x400 70.0 DisplayPort-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 380mm x 305mm 1280x1024 60.0*+ 75.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 But only one display works. After that if I run for example : xrandr --output DisplayPort-0 --left-of DisplayPort-1 I have a black screen on the 2 monitors and I can't access to a terminal. I noticed something else : When I turn off and on again the second monitor (manually) an kernel error occurred : [18515.140220] [drm:radeon_process_aux_ch] *ERROR* Buffer to small for return answer 1 6 During some seconds, the main monitor get stranges color and lights intensity! It seem to be the same problem that the bug #569970 but I am not sure. Someone have an idea to solve this? Tell me if you need other logs or informations. You need this patch most likely: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5137ee940c3e593ae5578a7a12a604eb8f239ac0 which means 2.6.36rc3 or newer. Thanks for the pointer Alex, reassigning to the kernel package. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On Mon, Aug 30, 2010 at 00:52:40 +0300, Kamen Naydenov wrote:
If I run glxgears X crashes badly - black screen or screen shot and
only SysRq commands works (can't test network access).
OK, I can reproduce a crash when running glxgears.
Program received signal SIGSEGV, Segmentation fault.
0xb760d91e in ?? () from /lib/i686/cmov/libc.so.6
(gdb) bt full
#0 0xb760d91e in ?? () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#1 0xb76107fc in ?? () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb7610d2d in realloc () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#3 0x080a9cf3 in Xrealloc (ptr=0xb76e43a0, amount=3077456856)
at ../../os/utils.c:1122
No locals.
#4 0x080a107e in miRectAlloc (pRgn=0x94a2494, n=20) at ../../mi/miregion.c:392
data = value optimized out
#5 0x080a2890 in miAppendNonO (badreg=0xbffbe398, pOverlap=0xbffbe3bc)
at ../../mi/miregion.c:530
pNextRect = value optimized out
#6 miRegionOp (badreg=0xbffbe398, pOverlap=0xbffbe3bc)
at ../../mi/miregion.c:793
bot = value optimized out
numRects = value optimized out
ytop = value optimized out
newSize = value optimized out
prevBand = 10
top = value optimized out
ybot = value optimized out
curBand = 0
r2y1 = value optimized out
oldData = value optimized out
r1y1 = value optimized out
#7 miRegionValidate (badreg=0xbffbe398, pOverlap=0xbffbe3bc)
at ../../mi/miregion.c:1377
half = 1
numRects = 10
ri = 0x94a2480
numRI = 3
sizeRI = value optimized out
i = value optimized out
rit = value optimized out
box = 0x94a2494
riBox = value optimized out
ret = 1
#8 0x0815eafc in miValidateTree (pParent=0x9160e30, pChild=0x93c6210,
kind=VTMap) at ../../mi/mivaltree.c:741
totalClip = {extents = {x1 = 0, y1 = 25, x2 = 1024, y2 = 600},
data = 0x0}
childClip = {extents = {x1 = 0, y1 = 0, x2 = 0, y2 = 0},
data = 0x81effb8}
childUnion = {extents = {x1 = 0, y1 = 0, x2 = 0, y2 = 600},
data = 0x956a650}
exposed = {extents = {x1 = 0, y1 = 0, x2 = 0, y2 = 0},
data = 0x81effb8}
pScreen = 0x91223a0
pWin = 0x93c6210
overlap = 1
viewvals = value optimized out
forward = -1074011240
#9 0x080992f5 in MapWindow (pWin=0x93c6210, client=0x9393990)
at ../../dix/window.c:2671
event = {u = {u = {type = 19 '\023', detail = 0 '\000',
sequenceNumber = 983}, keyButtonPointer = {pad00 = 64421907,
time = 242, root = 14681649, event = 0, child = 0, rootX = 0,
rootY = 0, eventX = 0, eventY = 0, state = 0,
sameScreen = 0 '\000', pad1 = 0 '\000'}, enterLeave = {
pad00 = 64421907, time = 242, root = 14681649, event = 0,
child = 0, rootX = 0, rootY = 0, eventX = 0, eventY = 0,
state = 0, mode = 0 '\000', flags = 0 '\000'}, focus = {
pad00 = 64421907, window = 242, mode = 49 '1', pad1 = 6 '\006',
pad2 = 224 '\340', pad3 = 0 '\000'}, expose = {pad00 = 64421907,
window = 242, x = 1585, y = 224, width = 0, height = 0,
count = 0, pad2 = 0}, graphicsExposure = {pad00 = 64421907,
drawable = 242, x = 1585, y = 224, width = 0, height = 0,
minorEvent = 0, count = 0, majorEvent = 0 '\000',
pad1 = 0 '\000', pad2 = 0 '\000', pad3 = 0 '\000'},
noExposure = {pad00 = 64421907, drawable = 242, minorEvent = 1585,
majorEvent = 224 '\340', bpad = 0 '\000'}, visibility = {
pad00 = 64421907, window = 242, state = 49 '1', pad1 = 6 '\006',
pad2 = 224 '\340', pad3 = 0 '\000'}, createNotify = {
pad00 = 64421907, parent = 242, window = 14681649, x = 0, y = 0,
width = 0, height = 0, borderWidth = 0, override = 0 '\000',
bpad = 0 '\000'}, destroyNotify = {pad00 = 64421907,
event = 242, window = 14681649}, unmapNotify = {
pad00 = 64421907, event = 242, window = 14681649,
fromConfigure = 0 '\000', pad1 = 0 '\000', pad2 = 0 '\000',
pad3 = 0 '\000'}, mapNotify = {pad00 = 64421907, event = 242,
window = 14681649, override = 0 '\000', pad1 = 0 '\000',
pad2 = 0 '\000', pad3 = 0 '\000'}, mapRequest = {
pad00 = 64421907, parent = 242, window = 14681649}, reparent = {
pad00 = 64421907, event = 242, window = 14681649, parent = 0,
x = 0, y = 0, override = 0 '\000', pad1 = 0 '\000',
pad2 = 0 '\000', pad3 = 0 '\000'}, configureNotify = {
pad00 = 64421907, event = 242, window = 14681649,
aboveSibling = 0, x = 0, y = 0, width = 0, height = 0,
borderWidth = 0, override
Re: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On Sun, Aug 29, 2010 at 13:25:07 +0300, Kamen Naydenov wrote: On Sat, Aug 28, 2010 at 15:10, Julien Cristau jcris...@debian.org wrote: Could you guys test the driver pointed at http://lists.freedesktop.org/pipermail/intel-gfx/2010-August/007910.html? (probably with the 2.6.32-20 kernel) I'll try it if you guide me how to compile and test it, or give me links where to read how to test. I already downloaded xf86-video-intel-shadow.tar.gz but I cant figure how to check dependencies, compile it and to test it On Sun, Aug 29, 2010 at 13:17:39 +0200, dmso...@edu.xunta.es wrote: When I have time, I'll try to compile your shadow version and see what happens. Is there a .deb package of the shadow version? It would be easier to try. There are i386 packages at http://people.debian.org/~jcristau/intel-shadow/ which work for me on minimal testing. Although it looks like they crash the X server in dri2 code when I run glxinfo, so I put xserver packages with a fix for that crash at the same place. If you can see if that's more stable than the stock unstable packages when running on kms that would be good. You'll need a Device section in xorg.conf such as: Section Device Identifier intel Option shadow EndSection sha1sums for those files: 7434f94eeff53742888db5747cdfb4efe3db2a24 xserver-xorg-video-intel-dbg_2.12.0-2_i386.deb 6e232126f89b2759ef095135c35070c5432ebbfd xserver-xorg-video-intel_2.12.0-2_i386.deb ad83a07bd714d1b9429a3c087a83b8297f2a21f1 xdmx-tools_1.7.7-5_i386.deb ccc4117d74c88b5d3ae6ccb7b426b65de92f4611 xdmx_1.7.7-5_i386.deb 649fcf10c7bf9943802e018b4d0f2d078ec23af3 xnest_1.7.7-5_i386.deb 942870f5eba5eef813ab13a95efc1b2be93db2e8 xorg-server_1.7.7-5_i386.changes b6d97bb80f41f18b4ef1a9548f1271fea00ad126 xserver-common_1.7.7-5_all.deb f339e415a741e0dba64dff3a50f4973d4292f2fe xserver-xephyr_1.7.7-5_i386.deb dea987480865749bc5292f31d3f391aa91f05cb7 xserver-xfbdev_1.7.7-5_i386.deb 6fa64fb8d406e44a30041080a7c2e71abb496efa xserver-xorg-core-dbg_1.7.7-5_i386.deb f9c21349b0a075f21cb4c74d5d2fe0f6f14fffb1 xserver-xorg-core-udeb_1.7.7-5_i386.udeb 4c86e5cdf9481844d2f48d38eb4894bb03c145ef xserver-xorg-core_1.7.7-5_i386.deb 83d12f4daaf4ff78332f1898e2382febac9d57b7 xserver-xorg-dev_1.7.7-5_i386.deb 2baed634647ec3b7c6499ca945e7ed6219d44fa0 xvfb_1.7.7-5_i386.deb Cheers, Julien signature.asc Description: Digital signature
Re: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On Sat, Aug 28, 2010 at 00:36:31 +0200, Cesare Leonardi wrote: I've also tried (don't know if it make sense) with 2.6.34-1~expermental.2, always with i915.modeset=0: same freeze. OK, it's starting to sound like this 'legacy' experiment is a failure so far. On my 945GM, legacy crashes on UMS on gnome startup (gdm is ok) reporting a lockup. I don't have an i8xx board to play with. Could you guys test the driver pointed at http://lists.freedesktop.org/pipermail/intel-gfx/2010-August/007910.html? (probably with the 2.6.32-20 kernel) Cheers, Julien signature.asc Description: Digital signature
Re: Bug#594623: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On Fri, Aug 27, 2010 at 23:28:39 +0200, Cesare Leonardi wrote: Package: xserver-xorg-video-intel Version: 2:2.12.0+legacy1-1 Severity: normal I cc the kernel team, since i believe it is something that relates to them also. I have the same problem as reported by Kamen: when GDM try to start, the screen goes black and the CPU fan starts to go at full speed (as if something is hanging in a loop) and the system stops responding completely. After reboot i can see nothing in syslog or X.log. Before this version, I was using 2.12.0 from experimental with KMS and that worked well with 2.6.32, .34, .35 (but only with .35rc*, because with .35 i cannot see the mouse pointer, as explained in #592415). Does the legacy driver work with UMS at all (on a different kernel, e.g.)? Cheers, Julien signature.asc Description: Digital signature
Bug#594342: linux-image-2.6.32-5-686: DVD video playback fails with 2.6.32-20 (works with 2.6.32-19)
On Wed, Aug 25, 2010 at 09:44:44 -0400, Daniel Kahn Gillmor wrote: Package: linux-2.6 Version: 2.6.32-20 Severity: normal I'm trying to play a commercial DVD, using totem or vlc on a squeeze system. with 2.6.32-19, i can play it successfully in both players. when i upgrade to 2.6.32-20, totem simply crashes, while vlc can play the audio, but no video is rendered. The Totem crash emits these errors to ~/.xsession-errors: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 124 error_code 11 request_code 132 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Can you attach the X log and output of xvinfo? maybe this has to do with the recent kernel fix mentioned in http://lwn.net/Articles/400746/ ? That fix will be in -21. Cheers, Julien signature.asc Description: Digital signature
Bug#593432: Black screen with kms and i915
retitle 593432 [i830] Black screen with kms and i915 kthxbye On Wed, Aug 18, 2010 at 07:53:29 +0200, san...@zedat.fu-berlin.de wrote: When booting the screen goes black at the moment the frame buffer is switched on. Booting continues until the 'login prompt', but the screen remains black. When switching to a text screen, the screen gets darker for a second, but no text login appears. I can then, however, login blind and the machine works. For example, I can reboot it when logging in as root and calling 'shutdown' (all blind, of course). The problem goes away when adding the line options i915 modeset=0 to the file /etc/modprobe.d/i915-kms.conf, so I guess it is a kms problem. If I wasn't a newbie I'd mark this bug as 'important', because it left a freshly installed machine more or less completely unusable. Is this a regression from a previous revision? Can you attach the dmesg from a kms boot? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#589075: xserver-xorg-video-intel: rendering errors with driver from experimental
reassign 589077 linux-2.6 2.6.32-18 reassign 589075 linux-2.6 2.6.32-18 fixed 589077 2.6.35-1~experimental.1 fixed 589075 2.6.35-1~experimental.1 kthxbye On Mon, Aug 9, 2010 at 22:59:12 +0200, Wolfram Quester wrote: On Wed, Jul 14, 2010 at 07:45:04PM +0100, Julien Cristau wrote: On Wed, Jul 14, 2010 at 20:31:28 +0200, Wolfram Quester wrote: Hi altogether, I'm on a Macbook from 2007 an testing the intel driver in experimental requested on debian-devel. Since I upgraded I have rendering errors, especially of text in gnome-terminal (sometimes letter are missing, sometimes whole lines look as if someone wiped over them with a dirty sponge on a black board). Sometimes this not only affects the text or inner area of windows, but also Window decorations and menus with the distortion reaching into the inner areas of the winows. This artifact mainly happens in the upper left areas of the windows, rarely in other areas. Please report this upstream, following the instructions at http://intellinuxgraphics.org/how_to_report_bug.html I reported bug 589077 upstream and got the following reply from Chris Wilson: That's a result of an underrun, and since it only happens when both displays are connected it sounds like we are incorrectly using a low power mode, such as self-refresh or framebuffer compression, with multiple active pipes. This is fixed in 2.6.35. [9c928d168] So I upgraded to linux-image and linux-base 2.6.35 currently in experimental and both bugs I reported against xserver-xorg-video-intel disappeared. So hands-up for the experimental drivers, but it seems using them with kernel 2.6.32 is error-prone. Thanks, I'll reassign both bugs to the kernel then. 9c928d168 can be cherry-picked to squeeze's kernel to fix 589077, and if the fix for the other bug can be tracked down as well that would be great. Cheers, Julien signature.asc Description: Digital signature
Bug#592290: [linux-source-2.6.32] X.org does not work with Intel driver and 4GB RAM
On Mon, Aug 9, 2010 at 00:50:24 +0200, Matthias Breier wrote: I'm not sure how to proceed in my case. How can I test if the changes mentioned in the upstream bug report ( http://bugs.freedesktop.org/show_bug.cgi?id=25510 ) have reached the Squeeze's current kernel version? I'm pretty sure they are. If your issue is still present in 2.6.35 (available in experimental), please file a bug against product=DRI, component=DRM/intel at http://bugs.freedesktop.org/ and let us know the bug number so we can track it. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#590893: Squeeze on Dell E6510, i5, intel graphics
reassign 590893 linux-2.6 kthxbye On Thu, Jul 29, 2010 at 15:46:40 -0700, n...@cantrip.org wrote: Boot method: debian-testing-amd64-businesscard Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/jigdo-cd/debian-testing-amd64-businesscard.jigdo Date: 2010-07-27 17:26 Machine: Dell E6510, intel GMA 1920x1080 panel, intel 6200 wireless Processor: i5-520 Memory: 3 GB [...] 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Subsystem: Dell Device [1028:040b] Kernel driver in use: i915 [...] Major Problems: 1. Installation of Grub2 MBR failed, with no suggestions offered. Installation of Grub 1 MBR failed. Installation of LILO succeeded. After that, installation of Grub2 succeeded, and worked. I'm hoping this is one of the bugs Colin is working on or has fixed, so I'll just focus this bug on the other issue: 2. Starting X failed and froze the whole machine (flashing LEDs). This turns out to be because the i915 kernel module in available kernels is busted. Starting up in recovery mode with i915.modeset=0, Xorg -configure generated an xorg.conf file that Xorg.0.log said worked, but the screen remained black. After changing the video driver named in xorg.conf to vesa, startup proceeded correctly to a working graphical desktop, although screen brightness varies randomly. Which exact kernel version was that (as reported in /proc/version)? 3. The i915 driver found in experimental linux-image-2.6.35-rc6-amd64 is fixed. Installing that with apt-get fails for dependencies on unavailable linux-base and firmware-linux-free. I built my own from apt-get source and make-kpkg, and it works. Hopefully there'll be some more fixes in 2.6.35.1 for that, but please report the 2.6.35 issue at bugs.freedesktop.org against product DRI, component DRM/Intel anyway, so we can track it more easily. Cheers, Julien signature.asc Description: Digital signature
Bug#590893: Squeeze on Dell E6510, i5, intel graphics
On Tue, Aug 3, 2010 at 14:52:00 -0700, n...@cantrip.org wrote: /proc/version says Linux version 2.6.32-5-amd64 (Debian 2.6.32-18) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 01:47:24 UTC 2010 But the failure is pretty robust. Upstream 2.6.32.17 has various of the i915 fixes found in 2.6.35. When those get into unstable's 2.6.32 kernel, I'll try them and report. Probably loading i915 with modeset=0 under upstream 2.6.32.17 would kernel-panic, if experience with 2.6.35 is any predictor. There's no UMS support for the newest intel chips so modeset=0 is useless on those machines. Thanks for the additional info. Cheers, Julien signature.asc Description: Digital signature
Bug#574412: linux-image-2.6.32-3-amd64: unloading and realoding ide-cd-mod breaks system
On Mon, Aug 2, 2010 at 20:34:41 +0200, Michal Suchanek wrote: If the official kernel has finally switched to libata this should no longer be an issue as well as various other breakage caused by the old ide drivers. It is certainly so for the 2.6.34-1 kernel, not sure offhand about the testing/unstable kernels. The switch to libata was done in 2.6.32-10. Cheers, Julien signature.asc Description: Digital signature
Bug#585625: Switch to i915/KMS lefts console unusable
On Tue, Jul 27, 2010 at 13:31:00 -0400, Andrew Lee wrote: Dear Kernel Team, This bug would block a lot of out users to use and install Debian squeeze on their computer with intel graphic card. Could you please backport this fix from 2.6.35-rc5 into squeeze stock kernel? Which fix? Also how did you determine this bug and 585910 are the same? Cheers, Julien signature.asc Description: Digital signature
Bug#585625: Switch to i915/KMS lefts console unusable
On Tue, Jul 27, 2010 at 14:29:01 -0400, Andrew Lee wrote: Does any patch available that I can test to determine this bug are solved? No, that's why I asked you what fix you were talking about. If you want to bisect where your bug got fixed between 2.6.33 and 2.6.35 that would be appreciated. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#590226: linux-tools-2.6: uninstallable
On Sun, Jul 25, 2010 at 15:16:50 +0200, Bastian Blank wrote: On Sun, Jul 25, 2010 at 01:12:42PM +0100, Ben Hutchings wrote: On Sun, 2010-07-25 at 09:27 +0300, Török Edwin wrote: [...] Why does linux-tools-2.6 require a specific version of binutils? It uses libbfd. Okay, so linux-2.6 is now part of a much larger bunch of tightly coupled packages. perf in bundling userspace utilities in the kernel source tree is a bad idea shocker. Would it be possible to link it against libbfd.a instead? Cheers, Julien signature.asc Description: Digital signature
Bug#573264: Also with 2.6.32-5-686 (Debian 2.6.32-15)
On Sat, Jul 24, 2010 at 13:46:41 +0100, Robert Scott wrote: FWIW I am also getting this on squeeze with ii xserver-xorg 1:7.4+4 ii xserver-xorg-core 2:1.6.3.901-1 ii xserver-xorg-video-intel 2:2.8.1-2 These are very old versions, please use the latest from sid or experimental. Linux version 2.6.32-5-686 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:59:47 UTC 2010 It's very rare - only happened once to me at random while I was working. Please file your own bug for this. If you can reproduce it with 2.6.34 or later, grab /sys/kernel/debug/dri/0/i915_error_state after the hang and attach it to your bug (not this one). Cheers, Julien signature.asc Description: Digital signature
Bug#590193: i915: fix for intel gen3 hangs
Package: linux-2.6 Version: 2.6.32-18 Severity: normal Tags: patch upstream fixed-upstream Hi, 2.6.35-rc6 included two patches fixing various gpu hangs on intel gen3 hw (915/945), it would be good to have them in sid. The first provides some register definitions, the second has the actual fix. commit 45503ded966c98e604c9667c0b458d40666b9ef3 Author: Keith Packard kei...@keithp.com Date: Mon Jul 19 21:12:35 2010 -0700 drm/i915: Define MI_ARB_STATE bits The i915 memory arbiter has a register full of configuration bits which are currently not defined in the driver header file. Signed-off-by: Keith Packard kei...@keithp.com cc: sta...@kernel.org Signed-off-by: Dave Airlie airl...@redhat.com commit 944001201ca0196bcdb088129e5866a9f379d08c Author: Dave Airlie airl...@redhat.com Date: Tue Jul 20 13:15:31 2010 +1000 drm/i915: enable low power render writes on GEN3 hardware. A lot of 945GMs have had stability issues for a long time, this manifested as X hangs, blitter engine hangs, and lots of crashes. one such report is at: https://bugs.freedesktop.org/show_bug.cgi?id=20560 along with numerous distro bugzillas. This only took a week of digging and hair ripping to figure out. Tracked down and tested on a 945GM Lenovo T60, previously running x11perf -copypixwin500 or x11perf -copywinpix500 repeatedly would cause the GPU to wedge within 4 or 5 tries, with random busy bits set. After this patch no hangs were observed. cc: sta...@kernel.org Signed-off-by: Dave Airlie airl...@redhat.com Cheers, Julien signature.asc Description: Digital signature
Bug#583968: xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled
tag 583968 patch kthxbye On Mon, May 31, 2010 at 17:15:41 -0400, Andres Cimmarusti wrote: When I try suspending using KMS my computer (an HP Pavilion dv5035nr laptop) does not resume. Furthermore I've tried logging into it remotely to obtain a backtrace from X with no success (following this procedure: http://ubuntuforums.org/showthread.php?t=1228332). I'm letting NetworkManager handle my network interfaces, however, I also tried using dhcp directly in the /etc/network/interfaces file. Unfortunately as soon as the resuming process starts (and fails) I am unable to establish a connection the laptop (wired or wireless). On top of this, upon hard reboot I have no network connectivity (if managed by network manager): http://mail.gnome.org/archives/networkmanager-list/2010-March/msg00123.html The workaround for the last bit has been to erase the stale file and reboot. When using UMS the resume process happens perfectly. I don't know how else to get a backtrace. The laptop screen is completely blank so I can't switch to another session. I've marked this bug as important because suspend/hibernate are almost essential features in a laptop. Patch seems to be http://article.gmane.org/gmane.comp.video.dri.devel/48108 Cheers, Julien signature.asc Description: Digital signature
Bug#545125: Intel + KSM still corrupt memory after resuming from suspend to disk
On Wed, Jul 14, 2010 at 15:57:32 +0200, Vincent Danjean wrote: reopen 545125 found 545125 2.6.32-17 thanks Hi, Even if the problem occurs less often, I still experiment it sometimes with 2.6.32-17. The last time (yesterday), just after a resume, any new processus segfault within the ld.so code... So I rebooted. And today, I discovered, just before submitting a new bug, that the fact that bash core dump each time I hit [tab] or [backspace] was due to a disk corruption of bash binary (ie pb fixed by reinstalling my current version of bash). I will now start a global fsck to check if other on-disk structures have been corrupted or not. So, this bug is not fully fixed. New patch in mainline: commit cd9f040df6ce46573760a507cb88192d05d27d86 Author: Linus Torvalds torva...@linux-foundation.org Date: Sun Jul 18 09:44:37 2010 -0700 drm/i915: add 'reclaimable' to i915 self-reclaimable page allocations The hibernate issues that got fixed in commit 985b823b9192 (drm/i915: fix hibernation since i915 self-reclaim fixes) turn out to have been incomplete. Vefa Bicakci tested lots of hibernate cycles, and without the __GFP_RECLAIMABLE flag the system eventually fails to resume. With the flag added, Vefa can apparently hibernate forever (or until he gets bored running his automated scripts, whichever comes first). The reclaimable flag was there originally, and was one of the flags that were dropped (unintentionally) by commit 4bdadb978569 (drm/i915: Selectively enable self-reclaim) that introduced all these problems, but I didn't want to just blindly add back all the flags in commit 985b823b9192, and it looked like __GFP_RECLAIM wasn't necessary. It clearly was. I still suspect that there is some subtle reason we're missing that causes the problems, but __GFP_RECLAIMABLE is certainly not wrong to use in this context, and is what the code historically used. And we have no idea what the causes the corruption without it. Reported-and-tested-by: M. Vefa Bicakci bic...@superonline.com Cc: Dave Airlie airl...@gmail.com Cc: Chris Wilson ch...@chris-wilson.co.uk Cc: KOSAKI Motohiro kosaki.motoh...@jp.fujitsu.com Cc: Hugh Dickins hugh.dick...@tiscali.co.uk Cc: sta...@kernel.org Signed-off-by: Linus Torvalds torva...@linux-foundation.org Maybe this time it'll be fixed for good... Cheers, Julien signature.asc Description: Digital signature
Bug#534422: X hangs with blank screen when it is in use
On Thu, Jul 15, 2010 at 10:18:29 +0800, Darren Hoo wrote: I experienced blank screen with only cursor on the screen after resume from suspension now and then before 2.6.32-17, but after I upgraded to 2.6.32-17, X hangs with blank screen when it is in use. I am sure whether it is related to this bug. Please file your own bug. here's part of syslog: Jul 15 09:58:24 debian kernel: [ 3153.980040] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Jul 15 09:58:24 debian kernel: [ 3153.980055] render error detected, EIR: 0x Jul 15 09:58:24 debian kernel: [ 3153.980119] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 496217 at 496216) Jul 15 09:58:36 debian kernel: [ 3165.549011] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Jul 15 09:58:36 debian kernel: [ 3165.549017] render error detected, EIR: 0x and Xorg.log: (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output error. When filing your own bug, please include the following information: What version of libdrm-intel1 and xserver-xorg-video-intel? Does that still happen with the versions from experimental? What about the kernel from experimental? Does the hang happen on resume, or when doing something else (what?)? If you reproduce with 2.6.34+, please grab i915_error_state from /sys/kernel/debug/dri/0/ and include it in a bug report following instructions at http://intellinuxgraphics.org/how_to_report_bug.html Thanks, Julien signature.asc Description: Digital signature
Bug#545125: Intel + KSM still corrupt memory after resuming from suspend to disk
On Wed, Jul 14, 2010 at 15:57:32 +0200, Vincent Danjean wrote: Even if the problem occurs less often, I still experiment it sometimes with 2.6.32-17. The last time (yesterday), just after a resume, any new processus segfault within the ld.so code... So I rebooted. And today, I discovered, just before submitting a new bug, that the fact that bash core dump each time I hit [tab] or [backspace] was due to a disk corruption of bash binary (ie pb fixed by reinstalling my current version of bash). I will now start a global fsck to check if other on-disk structures have been corrupted or not. So, this bug is not fully fixed. I don't suppose it's possible that this was earlier on-disk corruption still showing up after the reboot on the new kernel? Cheers, Julien signature.asc Description: Digital signature
Bug#588780: linux-image-2.6.34-1-amd64: X fails to start because modesetting is off
On Mon, Jul 12, 2010 at 10:22:09 +0200, Michal Suchanek wrote: When I boot modesetting is off resulting in inability to start X. When I boot modesetting is off resulting in inability to start X. When I boot modesetting is off resulting in inability to start X. Instead of repeating this line 3 times maybe you could give some actual information? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#572712: use hardened sysctl net.* settings per default
On Sat, Jul 10, 2010 at 14:37:36 +0200, Moritz Muehlenhoff wrote: If you want to change the standard Debian sysctl settings, this should probably be changed by netbase providing a /etc/sysctl.d snippet. The kernel package is not the right place. Reassigning to netbase. Can you explain why the kernel package is not the right place to change kernel defaults? I think it would be inappropriate for netbase to change these things... Cheers, Julien signature.asc Description: Digital signature
Re: Bug#572712: use hardened sysctl net.* settings per default
On Sat, Jul 10, 2010 at 13:45:44 +0100, Julien Cristau wrote: On Sat, Jul 10, 2010 at 14:37:36 +0200, Moritz Muehlenhoff wrote: If you want to change the standard Debian sysctl settings, this should probably be changed by netbase providing a /etc/sysctl.d snippet. The kernel package is not the right place. Reassigning to netbase. Can you explain why the kernel package is not the right place to change kernel defaults? I think it would be inappropriate for netbase to change these things... My point is, either the request is legitimate and the defaults should be changed in the kernel where they belong, or they aren't, and the bug should be closed. Cheers, Julien signature.asc Description: Digital signature
Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine
On Thu, Jul 8, 2010 at 10:36:48 +0200, Vincent Danjean wrote: Package: linux-2.6 Version: 2.6.32-16 Severity: important Hi, I tried to install linux-image-2.6.32-5-amd64/2.6.32-16 in a kvm virtual machine. With this kernel, it fails to boot. The virtual machine freeze after the line: [0.324387] Write protecting the kernel read-only data: 4220k (see below the full boot log taken from a serial console) I tried to boot both with a serial console (attached to a tty in the host) and with a vga video emulated screen. Same things happened. The kvm machine is a lenny with a few package from unstable Regards, Vincent PS: the severity can be increased if lots of people experiments the same thing or lowered if this is specific to my configuration. Likely the same as reported by weasel at http://lkml.indiana.edu/hypermail/linux/kernel/1007.0/02385.html Cheers, Julien signature.asc Description: Digital signature
Bug#587887: linux-base: please suppress useless debconf messages on first install
On Sat, Jul 3, 2010 at 12:54:12 +0200, Holger Levsen wrote: How are older installations relevant? How are they not? Cheers, Julien signature.asc Description: Digital signature
Bug#545517: Intel/KMS/suspend-to-disk bug still present on 2.6.34
Hi Vincent,
On Mon, Jun 14, 2010 at 22:15:17 +0200, Vincent Danjean wrote:
Since the introduction of KMS, suspend-to-disk never works reliably
on my laptop. Todays, it is so unstable that I do not try it. The
biggest problem is that, when it does not work, the session is restored
but (I think) memory corruption occurs. So the symptom can differ from
time to time.
My classical symptom is applications crashing or refusing to be
load (with a segv in libc when trying to run ls for example).
In these cases, I immediately hard-switch-off the laptop so that
in-memory corruption was not writen-back on disk (I had several
difficult fsck before I do that).
I'm not sure that this is related to KMS but it begins to occurs when
KMS has been introduced and (in the first time, I do not recheck recently),
I have no problems when I disabled KMS.
#534422 can be linked to this bug.
This bug is also reported to xorg:
https://bugs.freedesktop.org/show_bug.cgi?id=23836
This may be fixed by commit 985b823b919273fe1327d56d2196b4f92e5d0fae
(included below).
Can you test it?
commit 985b823b919273fe1327d56d2196b4f92e5d0fae
Author: Linus Torvalds torva...@linux-foundation.org
Date: Fri Jul 2 10:04:42 2010 +1000
drm/i915: fix hibernation since i915 self-reclaim fixes
Since commit 4bdadb9785696439c6e2b3efe34aa76df1149c83 (drm/i915:
Selectively enable self-reclaim), we've been passing GFP_MOVABLE to the
i915 page allocator where we weren't before due to some over-eager
removal of the page mapping gfp_flags games the code used to play.
This caused hibernate on Intel hardware to result in a lot of memory
corruptions on resume. See for example
http://bugzilla.kernel.org/show_bug.cgi?id=13811
Reported-by: Evengi Golov (in bugzilla)
Signed-off-by: Dave Airlie airl...@redhat.com
Tested-by: M. Vefa Bicakci bic...@superonline.com
Cc: sta...@kernel.org
Cc: Chris Wilson ch...@chris-wilson.co.uk
Cc: KOSAKI Motohiro kosaki.motoh...@jp.fujitsu.com
Cc: Hugh Dickins hugh.dick...@tiscali.co.uk
Signed-off-by: Linus Torvalds torva...@linux-foundation.org
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 9ded3da..0743858 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -2239,7 +2239,7 @@ i915_gem_object_get_pages(struct drm_gem_object *obj,
mapping = inode-i_mapping;
for (i = 0; i page_count; i++) {
page = read_cache_page_gfp(mapping, i,
- mapping_gfp_mask (mapping) |
+ GFP_HIGHUSER |
__GFP_COLD |
gfpmask);
if (IS_ERR(page))
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#587627: linux-image-2.6.32-5-686: Unable to use 1600x1200 resolution on external screen, screen not syncing
On Wed, Jun 30, 2010 at 14:17:40 +0200, Julien Blanc wrote: When booting, after the grub menu, the external screen starts being unable to sync as soon as KMS sets the mode for the screen (1600x1200, which is the native resolution). Display on the laptop screen at 800x480 is ok. When Xorg starts, the screen syncs again because it sets another resolution. All resolutions work fine, except the native one (1600x1200), even after disabling the laptop screen. Upgrading to kernel 2.6.34-1 still gives the same results. Note that the problem also occurs with kms disabled. This screen works fine with a different computer with an intel chipset (G31 express). Please report this at http://bugs.freedesktop.org/enter_bug.cgi?product=DRIcomponent=DRM/Intel and attach the information requested at http://intellinuxgraphics.org/how_to_report_bug.html (in particular dmesg from booting with drm.debug=6). Then tell us the bug number so we can track it. Thanks, Julien signature.asc Description: Digital signature
Bug#584744: linux-2.6: radeonfb builtin on sparc and powerpc
On Sun, Jun 6, 2010 at 14:36:12 +0200, Bastian Blank wrote: On Sun, Jun 06, 2010 at 11:07:51AM +0200, Julien Cristau wrote: the sid kernel has radeonfb builtin on some archs: debian/config/powerpc/config:CONFIG_FB_RADEON=y debian/config/sparc/config:CONFIG_FB_RADEON=y This is likely to conflict with the fb provided by the radeon drm driver with kms. Maybe they can be made =m instead? That is a problem. Both powerpc and sparc have no text console. So do you have another suggestion to avoid the conflict? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#586292: xserver-xorg-core: deadlocks for no apparent reason
reassign 586292 linux-2.6 2.6.32-15 kthxbye On Fri, Jun 18, 2010 at 09:57:31 +0200, Ulrich Klauer wrote: I'm running a regularly updated squeeze/testing system (at most a few days lag behind the current version). Earlier this week, I experienced for the first time a complete freeze of my X system, for no apparent reason - just browsing the web (using Iceweasel), nothing dangerous. Today, this has happened again, again while browsing, but this may be a coincidence. The desktop stops responding to any key presses or mouse movements; automatically updated displays like the clock stop too. No reaction to Ctrl-Alt-BS or Ctrl-Alt-Del. However, Magic SysRq is still working. I am including the relevant part of syslog, which shows a deadlock warning first from events and then from Xorg. Please note that the file Xorg.0.log automatically included below is not of before the crash, but of the reboot. However, the differences are minimal - see attached diff. Sounds like a kernel bug to me, so reassigning. Jun 18 08:30:23 chalkos kernel: [ 99.655588] CE: hpet increasing min_delta_ns to 15000 nsec Jun 18 08:33:52 chalkos anacron[1263]: Job `cron.daily' started Jun 18 08:33:52 chalkos anacron[2247]: Updated timestamp for job `cron.daily' to 2010-06-18 Jun 18 08:53:44 chalkos kernel: [ 1500.100506] CE: hpet increasing min_delta_ns to 22500 nsec Jun 18 08:53:44 chalkos kernel: [ 1500.100506] CE: hpet increasing min_delta_ns to 33750 nsec Jun 18 08:56:44 chalkos kernel: [ 1680.532322] INFO: task events/0:9 blocked for more than 120 seconds. Jun 18 08:56:44 chalkos kernel: [ 1680.532331] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jun 18 08:56:44 chalkos kernel: [ 1680.532337] events/0 D 880001815640 0 9 2 0x Jun 18 08:56:44 chalkos kernel: [ 1680.532348] 880079101530 0046 88003ab65fff 0001 Jun 18 08:56:44 chalkos kernel: [ 1680.532357] 81033d99 f8a0 88007bb9bfd8 Jun 18 08:56:44 chalkos kernel: [ 1680.532366] 00015640 00015640 88007bb53f90 88007bb54288 Jun 18 08:56:44 chalkos kernel: [ 1680.532374] Call Trace: Jun 18 08:56:44 chalkos kernel: [ 1680.532391] [81033d99] ? change_page_attr_set_clr+0x2f2/0x394 Jun 18 08:56:44 chalkos kernel: [ 1680.532404] [8100f792] ? __switch_to+0x27b/0x297 Jun 18 08:56:44 chalkos kernel: [ 1680.532429] [a02b8c80] ? ttm_bo_wait_unreserved+0x102/0x11c [ttm] Jun 18 08:56:44 chalkos kernel: [ 1680.532438] [81064afa] ? autoremove_wake_function+0x0/0x2e Jun 18 08:56:44 chalkos kernel: [ 1680.532448] [81041add] ? pick_next_task_fair+0xcd/0xd8 Jun 18 08:56:44 chalkos kernel: [ 1680.532461] [a02b8d0d] ? ttm_bo_reserve_locked+0x73/0xc4 [ttm] Jun 18 08:56:44 chalkos kernel: [ 1680.532472] [a02b95aa] ? ttm_bo_cleanup_refs+0xe4/0x248 [ttm] Jun 18 08:56:44 chalkos kernel: [ 1680.532484] [a02b9796] ? ttm_bo_delayed_delete+0x88/0xf7 [ttm] Jun 18 08:56:44 chalkos kernel: [ 1680.532495] [a02b9817] ? ttm_bo_delayed_workqueue+0x12/0x26 [ttm] Jun 18 08:56:44 chalkos kernel: [ 1680.532505] [810614d3] ? worker_thread+0x188/0x21d Jun 18 08:56:44 chalkos kernel: [ 1680.532516] [a02b9805] ? ttm_bo_delayed_workqueue+0x0/0x26 [ttm] Jun 18 08:56:44 chalkos kernel: [ 1680.532523] [81064afa] ? autoremove_wake_function+0x0/0x2e Jun 18 08:56:44 chalkos kernel: [ 1680.532531] [8106134b] ? worker_thread+0x0/0x21d Jun 18 08:56:44 chalkos kernel: [ 1680.532537] [8106482d] ? kthread+0x79/0x81 Jun 18 08:56:44 chalkos kernel: [ 1680.532545] [81011baa] ? child_rip+0xa/0x20 Jun 18 08:56:44 chalkos kernel: [ 1680.532551] [810647b4] ? kthread+0x0/0x81 Jun 18 08:56:44 chalkos kernel: [ 1680.532558] [81011ba0] ? child_rip+0x0/0x20 Jun 18 08:56:44 chalkos kernel: [ 1680.532583] INFO: task Xorg:1689 blocked for more than 120 seconds. Jun 18 08:56:44 chalkos kernel: [ 1680.532587] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jun 18 08:56:44 chalkos kernel: [ 1680.532592] Xorg D 0 1689 1676 0x0044 Jun 18 08:56:44 chalkos kernel: [ 1680.532600] 8145b1f0 0082 00ffa02fc679 Jun 18 08:56:44 chalkos kernel: [ 1680.532609] 8800376c29b8 00ff8800376c2fb0 f8a0 88007ab51fd8 Jun 18 08:56:44 chalkos kernel: [ 1680.532617] 00015640 00015640 88007905bf90 88007905c288 Jun 18 08:56:44 chalkos kernel: [ 1680.532625] Call Trace: Jun 18 08:56:44 chalkos kernel: [ 1680.532637] [a02b865b] ? ttm_bo_wait+0x13c/0x160 [ttm] Jun 18 08:56:44 chalkos kernel: [ 1680.532646] [812f982c] ? schedule_timeout+0x2e/0xdd Jun 18 08:56:44 chalkos kernel: [ 1680.532658]
Bug#584744: linux-2.6: radeonfb builtin on sparc and powerpc
Package: linux-2.6 Version: 2.6.32-10 Severity: important Hi, the sid kernel has radeonfb builtin on some archs: debian/config/powerpc/config:CONFIG_FB_RADEON=y debian/config/sparc/config:CONFIG_FB_RADEON=y This is likely to conflict with the fb provided by the radeon drm driver with kms. Maybe they can be made =m instead? Cheers, Julien signature.asc Description: Digital signature
Bug#580601: [drm/i915] flickering and artifacts on (some?) gm45 with powersave' from 'xserver-xorg-core: Flickering and artifacts after update, using intel driver
On Wed, Jun 2, 2010 at 20:04:21 -0300, Fernando Lemos wrote: Some days ago linux-image-2.6.32-14 was released, and one of the entries in the changelog says: * Add drm changes from stable 2.6.33.5: - i915: Disable FBC on 915GM and 945GM (Closes: #582427) I think that's the patch: https://patchwork.kernel.org/patch/86999/ #582427 could be related to this issue. However, I just booted into 2.6.32-15 with powersave=1 commented out (this time I'm using modprobe.d instead of defaults/grub, and I re-ran update-grub afterwards to make sure I really was not setting powersave=0 or powersave=1) and the problem is still there (the screen flickered several times in just a few minutes). #582427 was about a different chip generation than this bug. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#582427: screen corruption
reassign 582427 linux-2.6 2.6.32-10 kthxbye On Thu, May 20, 2010 at 14:01:28 -0400, Joey Hess wrote: With this version and also experimental 2:2.11.0-1, on not one, but *two* Dell Mini 9 laptops, I have started seeing multiple types of screen corruption. * Twice, a blue screen of death, that appeared without warning while I was using just gnome-terminal and/or chromium-browser. Suspending and resuming cleared it up. * Occasionally the screen will go black for a minute, and come back, similar to past problems with reprobing the resolution unnecessarily. Does not happen much. * Sometimes on resume from suspend certian characters in gnome-terminal's font display with minor corruption. Like the lines of the 'k' not quite meeting in the middle. * Most frequently, I will be using gnome-terminal and an area of the screen will temporarily get corrupted. Like part of what is displayed on the left is displayed over on the right. Sometimes for just for a very short time, so the screen appears to flicker. Sometimes for longer, in which case it goes away when I hit enter or something in the terminal. It seems to be brought on by gnome-terminal scrolling, especially fast scrolling, and possibly also cleaned up by more scrolling. This has been going on for approximatly a week or two. I only switched my drive to the other laptop yesterday and have verified it's not broken video memory or something, since I quickly reproduced it on the other laptop. I suspect but am not sure that this started happening after a kernel upgrade. I'm fairly sure that the system does not start experiencing these problems until after I have suspended it (to ram), and resumed. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-12) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-10) ) #1 SMP Sat May 1 04:16:37 UTC 2010 Hopefully this will be fixed by drm-i915-disable-fbc-on-915gm-and-945gm.patch currently queued for 2.6.33.x, so reassigning to the kernel. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#580601: Related to KMS in 2.6.32
reassign 580601 linux-2.6 2.6.32-12 found 580601 2.6.34-1~experimental.1 forwarded 580601 http://bugs.freedesktop.org/show_bug.cgi?id=27589 retitle 580601 [drm/i915] flickering and artifacts on (some?) gm45 with powersave kthxbye On Sat, May 22, 2010 at 17:12:47 -0300, Fernando Lemos wrote: The screen flickered 4 times during the time I was composing this e-mail, so I guess it's not fixed upstream yet. Oh well. Thanks for testing anyway. http://bugs.freedesktop.org/show_bug.cgi?id=27589 has 0 comment from Intel and is a month old, I'll try and get Jesse to comment... FWIW I've never seen this on my gm45 (dell latitude e4200). If there's anything else I can test, please let me know. Will do, thanks again. Cheers, Julien signature.asc Description: Digital signature
Bug#582105: 855GM: hard hang when closing lid
On Tue, May 18, 2010 at 14:10:14 +0200, Juliusz Chroboczek wrote: Package: linux-image-2.6.33-2-686 Version: 2.6.33-1~experimental.5 A laptop with 855GM video chipset (Dell Latitude X300) hangs whenever I close the lid. Using kms. Julien is telling me that this is a known issue, but I cannot find a relevant bug report. I was thinking of the bug fixed by: commit 7b9c5abee98c54f85bcc04bd4d7ec8d5094c73f4 Author: Jesse Barnes jbar...@virtuousgeek.org Date: Fri Feb 12 09:30:00 2010 -0800 drm/i915: give up on 8xx lid status These old machines more often than not lie about their lid state. So don't use it to detect LVDS presence, but leave the event handler to deal with lid open/close, when we might need to reset the mode. Fixes kernel bug #15248 Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org Cc: sta...@kernel.org Signed-off-by: Eric Anholt e...@anholt.net but that's apparently a different issue (that seems to only affect initial detection). Can you try setting up netconsole to get some more info? The remaining 855GM issue I know of is https://bugs.freedesktop.org/show_bug.cgi?id=27187 Also, again, please use reportbug to file bugs… Cheers, Julien signature.asc Description: Digital signature
Bug#580894: linux-image-2.6.32-5-amd65: linux-image-2.6.32-5-amd64 crashes at boot
On Wed, May 12, 2010 at 18:45:21 +0200, Vincent Lefevre wrote: On 2010-05-11 11:36:58 -0400, Jeff Ratliff wrote: Workaround is to blacklist the nouveau driver. In /etc/modprobe.d/blacklist.conf insert the line: blacklist nouveau However, recent updates in Sid fix this for me. Packages are libdrm-nouveau1 2.4.18-5 xserver-xorg-video-nouveau 1:0.0.15+git20100329+7858345-3 On my system, this is no longer a bug. I now have: linux-image-2.6.32-5-amd64 2.6.32-12 libdrm-nouveau1 2.4.18-5 xserver-xorg-video-nouveau 1:0.0.15+git20100329+7858345-3 (and everything concerning Xorg being up-to-date from unstable), and the problem still occurs. Please file your own separate bugs for your own issues. Cheers, Julien signature.asc Description: Digital signature
Bug#580894: linux-image-amd64
On Sun, May 9, 2010 at 19:39:31 +0200, Hans-J. Ullrich wrote: If required, I can send you the whole kernel.log, too. Yes, please send the full kernel and X logs. Cheers, Julien signature.asc Description: Digital signature
Bug#581430: linux-image-2.6.32-3-amd64: KMS does not work after upgrade from 2.6.30-2-amd64
On Wed, May 12, 2010 at 23:50:11 +0200, Niklaus Giger wrote: Package: linux-2.6 Version: 2.6.32-9 Severity: normal Please test 2.6.32-12. Cheers, Julien signature.asc Description: Digital signature
Bug#580661: linux-image-2.6.32-5-686: 2.6.32-5-686 makes VGA compatible controller sick
On Fri, May 7, 2010 at 15:47:15 +0200, Gijs Hillenius wrote: Package: linux-2.6 Version: 2.6.32-12 Severity: important Running linux-image-2.6.32-5-686 garbles the screen of this laptop, both inside and outside of X. It makes the kernel unusable. What version were you using before? Unfortunately, I see nothing in dmesg, /var/log/Xorg.0.log, syslog or messages that points to the cause ... please attach the X log and dmesg anyway. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#580026: xserver-xorg: crashed with invalid opcode
reassign 580026 linux-2.6 2.6.32-11 retitle 580026 [drm/i915] invalid opcode: [#1] SMP in i915_gem_execbuffer kthxbye On Mon, May 3, 2010 at 10:25:46 +0200, Thiemo Nagel wrote: Package: xserver-xorg Version: 1:7.5+5 Severity: normal The crash happened while switching tabs in the KDE konsole program. Kernel log and server log are attached. Reassigning to the kernel. If this is reproducible with linux-image-2.6.32-5-686 (version 2.6.32-12), please file upstream at http://bugs.freedesktop.org/enter_bug.cgi?product=DRIcomponent=DRM/Intel (attach the dmesg and X log there as well) and let us know the bug number for tracking. [40050.898683] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [40051.238684] invalid opcode: [#1] SMP [40051.238703] last sysfs file: /sys/devices/virtual/block/loop1/queue/rotational [40051.238713] Modules linked in: ext4 jbd2 nls_cp437 vfat fat usbhid hid nls_utf8 cifs ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc ppdev lp parport sco bridge stp bnep l2cap crc16 bluetooth acpi_cpufreq cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats binfmt_misc fuse loop snd_hda_codec_realtek arc4 snd_hda_intel ecb snd_hda_codec option uvcvideo usbserial snd_hwdep videodev snd_pcm_oss snd_mixer_oss v4l1_compat usb_storage ath5k snd_pcm snd_seq_midi mac80211 snd_rawmidi snd_seq_midi_event ath i915 snd_seq drm_kms_helper snd_timer uhci_hcd drm snd_seq_device joydev ehci_hcd cfg80211 eeepc_laptop i2c_algo_bit snd i2c_core rfkill soundcore usbcore video atl1e rng_core pci_hotplug output nls_base psmouse led_class evdev snd_page_alloc battery processor button ac serio_raw ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc dm_crypt dm_mod sd_mod crc_t10dif thermal fan thermal_sys ata_generic ata_piix libata scsi_mod [40051.238989] [40051.239005] Pid: 1739, comm: Xorg Not tainted (2.6.32-4-686 #1) 1000HG [40051.239016] EIP: 0060:[f846f587] EFLAGS: 00213202 CPU: 1 [40051.239071] EIP is at i915_gem_execbuffer+0x210/0x225 [i915] [40051.239083] EAX: 0019 EBX: 0005 ECX: EDX: ef4ae000 [40051.239093] ESI: ef4afe98 EDI: EBP: c1f56600 ESP: ef4afe20 [40051.239104] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [40051.239118] Process Xorg (pid: 1739, ti=ef4ae000 task=ef5a0440 task.ti=ef4ae000) [40051.239126] Stack: [40051.239132] ef506100 f6fc4800 e3472400 e3472550 c1f566c0 097662b0 0005 [40051.239157] 0 01a0 [40051.239181] 0 0001 f837f5da f837e744 f837f5a7 ef4afe98 ef506880 f849124c [40051.239208] Call Trace: [40051.239296] [f8372586] ? drm_ioctl+0x210/0x2a9 [drm] [40051.239353] [f846f377] ? i915_gem_execbuffer+0x0/0x225 [i915] [40051.239378] [c10b3041] ? do_sync_read+0xc0/0x107 [40051.239427] [f8372376] ? drm_ioctl+0x0/0x2a9 [drm] [40051.239446] [c10bd710] ? vfs_ioctl+0x1c/0x5f [40051.239460] [c10bdca4] ? do_vfs_ioctl+0x4aa/0x4e5 [40051.239474] [c10b2c25] ? fsnotify_access+0x5a/0x61 [40051.239492] [c104b5e0] ? ktime_get_ts+0xcd/0xd5 [40051.239508] [c10bdd20] ? sys_ioctl+0x41/0x58 [40051.239525] [c10030fb] ? sysenter_do_call+0x12/0x28 [40051.239535] Code: ea e8 38 78 cc c8 85 c0 74 1c 6a f2 bf f2 ff ff ff ff 76 08 68 ac 66 48 f8 68 ad c6 48 f8 e8 cc 7b df c8 83 c4 10 89 e8 e8 12 c5 ff ff 8b 44 24 08 e8 09 c5 ff ff 83 c4 54 89 f8 5b 5e 5f 5d c3 [40051.239677] EIP: [f846f587] i915_gem_execbuffer+0x210/0x225 [i915] SS:ESP 0068:ef4afe20 [40051.239742] ---[ end trace 06b65af4d9140fb8 ]--- [40051.286498] [drm:drm_release] *ERROR* Device busy: 1 lient 1739[0:0] has disconnected Cheers, Julien signature.asc Description: Digital signature
Bug#580026: [drm/i915] invalid opcode: 0000 [#1] SMP in i915_gem_execbuffer
On Mon, May 3, 2010 at 14:15:51 +0200, Thiemo Nagel wrote: If this is reproducible with linux-image-2.6.32-5-686 (version 2.6.32-12) Where can I get 2.6.32-5? Should be on the mirrors since earlier today, I think. http://packages.debian.org/sid/linux-image-2.6.32-5-686 Cheers, Julien signature.asc Description: Digital signature
Re: Bug#579017: autodetection fails when booting with 64-bit kernel on 32-bit userland
reassign 579017 linux-2.6 2.6.32-9 kthxbye On Sat, Apr 24, 2010 at 15:27:11 +0400, Stanislav Maslovski wrote: Package: xserver-xorg-input-synaptics Version: 1.2.2-2 Severity: normal Without giving the explicit options (commented out in my xorg.conf below) the touchpad gets configured in a mouse-emulation mode (no scrolling, etc.) when I boot with a 64-bit kernel on a 32-bit userland. This sounds like a kernel bug. Can you attach the contents of /proc/bus/input/devices for both the 32bit and the 64bit kernel? I seem to remember a similar report a while back, but can't find it now... Cheers, Julien signature.asc Description: Digital signature
Re: Bug#579858: X fails to find nouveau device
reassign 579858 linux-2.6 2.6.32-11 retitle 579858 xen + nouveau → fail (page fault related) kthxbye On Mon, May 3, 2010 at 23:50:59 +0530, Ritesh Raj Sarraf wrote: Package: xserver-xorg-video-nouveau Version: 1:0.0.15+git20100329+7858345-3 Severity: normal This is awesome. ON the non-xen kernel, nouveau works nice. It also does extended display. xrandr works. So the problem is only seen with nouveau + Xen kernel (2.6.32-4-xen-686) I am again attaching the dmesg logs. This time, there's no kernel errors. Reassigning to the kernel, thanks. Copying part of the earlier dmesg here for kernel maintainers: [ 61.554777] 1 multicall(s) failed: cpu 1 [ 61.554782] Pid: 2615, comm: Xorg Tainted: GW 2.6.32-4-xen-686 #1 [ 61.554787] Call Trace: [ 61.554795] [c1004151] ? xen_mc_flush+0xa2/0x150 [ 61.554803] [c1004bde] ? xen_mc_issue+0x11/0x1f [ 61.554811] [c10a4830] ? insert_pfn+0x58/0x96 [ 61.554819] [c10a488d] ? vm_insert_mixed+0x1f/0x28 [ 61.554832] [edbfa58b] ? ttm_bo_vm_fault+0x19e/0x1ed [ttm] [ 61.554840] [c10a1342] ? __do_fault+0x53/0x3fb [ 61.554849] [c1005dec] ? xen_force_evtchn_callback+0xc/0x10 [ 61.554857] [c10a3541] ? handle_mm_fault+0x403/0x954 [ 61.554866] [c1005dec] ? xen_force_evtchn_callback+0xc/0x10 [ 61.554874] [c1006454] ? check_events+0x8/0xc [ 61.554882] [c100644b] ? xen_restore_fl_direct_end+0x0/0x1 [ 61.554890] [c103cca0] ? do_softirq+0x39/0x3c [ 61.554898] [c102283f] ? do_page_fault+0x271/0x287 [ 61.554906] [c10225ce] ? do_page_fault+0x0/0x287 [ 61.554915] [c1288073] ? error_code+0x73/0x78 [ 61.554922] call 1/1: op=1 arg=[c40298d0] result=-22 xen_mc_entry+0x2b/0x2f [ 61.554927] [ cut here ] [ 61.554934] WARNING: at /build/buildd-linux-2.6_2.6.32-11-i386-4fW2zP/linux-2.6-2.6.32/debian/build/source_i386_xen/arch/x86/xen/multicalls.c:182 xen_mc_issue+0x11/0x1f() [ 61.554940] Hardware name: MXC062 [ 61.554945] Modules linked in: aes_i586 aes_generic ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables sco bnep +rfcomm l2cap iscsi_trgt crc32c container pci_slot power_meter sbs sbshc bridge stp xen_evtchn xenfs ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi +fuse ext3 jbd dm_round_robin dm_multipath scsi_dh nouveau ttm drm_kms_helper drm i2c_algo_bit dm_crypt snd_hda_codec_idt btusb bluetooth uvcvideo snd_hda_intel videodev snd_usb_audio snd_hda_codec snd_pcm_oss +snd_mixer_oss snd_pcm snd_usb_lib snd_seq_midi snd_hwdep v4l1_compat snd_rawmidi snd_seq_midi_event arc4 snd_seq ecb iwl3945 joydev snd_timer snd_seq_device iwlcore mac80211 led_class dell_laptop cfg80211 rfkill +snd i2c_i801 rng_core soundcore snd_page_alloc dcdbas i2c_core battery evdev ac processor wmi pcspkr psmouse serio_raw ext4 mbcache jbd2 crc16 usbhid h id dm_mod sg sd_mod crc_t10dif sr_mod cdrom b44 ssb ata_generic mmc_core ata_piix libata uhci_hcd ehci_hcd pcmcia pcmcia_core mii video output button scsi_mod usbcore nls_base thermal fan thermal_sys [last +unloaded: scsi_wait_scan] [ 61.555299] Pid: 2615, comm: Xorg Tainted: GW 2.6.32-4-xen-686 #1 [ 61.555304] Call Trace: [ 61.555312] [c1037aed] ? warn_slowpath_common+0x5e/0x8a [ 61.555320] [c1037b23] ? warn_slowpath_null+0xa/0xc [ 61.555328] [c1004bde] ? xen_mc_issue+0x11/0x1f [ 61.555336] [c10a4830] ? insert_pfn+0x58/0x96 [ 61.555344] [c10a488d] ? vm_insert_mixed+0x1f/0x28 [ 61.555356] [edbfa58b] ? ttm_bo_vm_fault+0x19e/0x1ed [ttm] [ 61.555364] [c10a1342] ? __do_fault+0x53/0x3fb [ 61.555373] [c1005dec] ? xen_force_evtchn_callback+0xc/0x10 [ 61.555381] [c10a3541] ? handle_mm_fault+0x403/0x954 [ 61.555390] [c1005dec] ? xen_force_evtchn_callback+0xc/0x10 [ 61.555398] [c1006454] ? check_events+0x8/0xc [ 61.555406] [c100644b] ? xen_restore_fl_direct_end+0x0/0x1 [ 61.555414] [c103cca0] ? do_softirq+0x39/0x3c [ 61.555422] [c102283f] ? do_page_fault+0x271/0x287 [ 61.555430] [c10225ce] ? do_page_fault+0x0/0x287 [ 61.555439] [c1288073] ? error_code+0x73/0x78 [ 61.555444] ---[ end trace c6fe7832ae6b5410 ]--- Cheers, Julien signature.asc Description: Digital signature
Re: Bug#551256: xserver-xorg-video-intel: display flickers on login or xrandr -q since recent update
reassign 551256 linux-2.6 close 551256 2.6.32-10 kthxbye On Thu, Apr 8, 2010 at 15:25:23 -0400, John Lindgren wrote: Upstream report has it that the flicker is fixed by upgrading the kernel to 2.6.33. I don't have the hardware to test with any more. https://bugs.freedesktop.org/show_bug.cgi?id=25800#c7 The drm subsystem from 2.6.33 was backported to the debian kernel recently, so I'm closing this bug. Thanks for your report. Cheers, Julien signature.asc Description: Digital signature
Bug#577541: linux-image-2.6.32-4-amd64: Wrong resolution detected
tag 577541 - experimental kthxbye On Mon, Apr 12, 2010 at 17:18:11 +0200, Örjan Askhult wrote: After update I can't get the previous used screen resolution 1280x1024, only 1024x768. ** Kernel log: [ 1472.410429] [drm:i915_add_request], 14101 [ 1472.410487] [drm:i915_add_request], 14102 [ 1472.908013] [drm:intel_gpu_idle_timer], idle timer fired, downclocking [ 1473.408014] [drm:intel_crtc_idle_timer], idle timer fired, downclocking [ 1473.408030] [drm:intel_crtc_idle_timer], idle timer fired, downclocking [ 1475.523604] [drm:i915_add_request], 14103 [ 1475.523812] [drm:i915_add_request], 14104 [...] I asked Örjan to use drm.debug=6 before running reportbug (he reported this issue on #debian-x), hoping that the full dmesg would make it to the report, but apparently not. Örjan, could you get the full kernel log from /var/log/kern.log and attach it to this bug? Thanks, Julien signature.asc Description: Digital signature
Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770
On Wed, Mar 24, 2010 at 12:40:36 +0100, Mathieu Roy wrote: Regarding X, only xserver-xorg-core, xserver-xorg, xserver-xorg-video-radeon was recently upgraded. The latest xserver-xorg-video-radeon package enables kernel mode setting. This is incompatible with the radeonhd X driver. You should use the radeon driver instead. Cheers, Julien signature.asc Description: Digital signature
Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770
On Wed, Mar 24, 2010 at 14:51:40 +0100, Mathieu Roy wrote: severity 575226 minor retitle 575226 firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- video-radeonhd and should suggest xserver-xorg-video-radeon thanks firmware-linux-nonfree has nothing to do with this. Le mercredi 24 mars 2010, Julien Cristau a écrit : On Wed, Mar 24, 2010 at 12:40:36 +0100, Mathieu Roy wrote: Regarding X, only xserver-xorg-core, xserver-xorg, xserver-xorg-video-radeon was recently upgraded. The latest xserver-xorg-video-radeon package enables kernel mode setting. This is incompatible with the radeonhd X driver. You should use the radeon driver instead. I did not know that. To me, it seemed like radeonhd driver was the future and radeon some kind of legacy driver. Apparently, it is not. Right, radeonhd is dying at this point. I switched to the radeon driver and now it works (only with the latest kernel). I think it should be documented somewhere. And considering the results of running firmware-linux-nonfree with xserver-xorg-video-radeonhd (blank screen), maybe it would be nice to add a conflict against xserver-xorg-video- radeonhd and a suggest in favor of xserver-xorg-video-radeon. If nothing else, it will be documented in radeon's NEWS.Debian file (http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-ati.git;a=blob;f=debian/xserver-xorg-video-radeon.NEWS), and probably in the release notes for squeeze. Cheers, Julien signature.asc Description: Digital signature
Re: Processed: Re: Bug#575226: Info received (Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770)
reassign 575226 xserver-xorg-video-radeonhd retitle 575226 radeonhd broken with KMS severity 575226 serious tag 575226 sid kthxbye On Wed, Mar 24, 2010 at 14:18:03 +, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: reassign 575226 firmware-linux-nonfree Bug #575226 [xserver-xorg-video-radeonhd] firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- Bug reassigned from package 'xserver-xorg-video-radeonhd' to 'firmware-linux-nonfree'. thanks Stopping processing here. Please don't second-guess package maintainers. Cheers, Julien signature.asc Description: Digital signature
