Re: Solving the linux-2.6 firmware issue
On Sat, Jan 6, 2007 at 12:42:56 +0100, Frans Pop wrote: What I meant is that a name change for the source package to linux-2.6.18 means that any packages that now have a (build) dep on linux-2.6 will need to change that dependency (and again when, after the release the kernel team switches back to linux-2.6). This seems like work that should, if possible, be avoided. How would they have a (build) dep on a source package? Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#410956: xorg: xserver freezes irregularly when applications use lots of memory
severity 410956 important reassign 410956 linux-2.6 thanks On Wed, Feb 14, 2007 at 22:13:11 +0100, Arjen Bax wrote: Package: xorg Version: 1:7.1.0-11 Severity: critical Justification: breaks the whole system From time to time, especially when using big applications (e.g., Gimp) the system just freezes, leaving nothing in the syslog. The only way of recovering is by switching off and on the power switch. I finally succeeded in capturing some log messages that appeared on the tty of a remote logged-in user. It mentions 'kernel BUG' and the process Xorg, so I thought it wise to send in a bug report. I'll be happy to send in any extra info you'll need, but so far I have not succeeded in reliably reproducing the freeze events. This looks like a kernel bug to me, reassigning. cut Message from [EMAIL PROTECTED] at Wed Feb 14 10:04:52 2007 ... aglarond kernel: [ cut here ] aglarond kernel: kernel BUG at mm/rmap.c:587! aglarond kernel: invalid opcode: [#1] aglarond kernel: SMP aglarond kernel: CPU:0 aglarond kernel: EIP is at page_remove_rmap+0x14/0x2d aglarond kernel: eax: ebx: c10bf640 ecx: c10bf640 edx: c10bf640 aglarond kernel: esi: b232d000 edi: 0020 ebp: c5f2dcb4 esp: da7e7f00 aglarond kernel: ds: 007b es: 007b ss: 0068 aglarond kernel: Process Xorg (pid: 3015, ti=da7e6000 task=da601000 task.ti=da7e6000) aglarond kernel: Stack: c014b88f b2317000 cbe62da0 da7e7f6c b240 d9cecb20 aglarond kernel:d9c3fac0 c14040c0 ffea c10be5ac d9cecb20 003e9000 b26a3000 aglarond kernel: c14040c0 d9c3fac0 d9f56d4c cef662cc c014de97 b26a3000 da7e7f68 aglarond kernel: Call Trace: aglarond kernel: Code: ff ff 85 c0 89 c6 75 c9 b0 01 86 43 28 83 c4 20 89 e8 5b 5e 5f 5d c3 89 c1 90 83 40 08 ff 0f 98 c0 84 c0 74 1e 8b 41 08 40 79 08 0f 0b 4b 02 15 aa 29 c0 8b 51 10 89 c8 83 f2 01 83 e2 01 e9 f3 aglarond kernel: EIP: [c01506e9] page_remove_rmap+0x14/0x2d SS:ESP 0068:da7e7f00 /cut (Each 'aglarond' line was preceded with a similar 'Message from' line, which I removed except the very first.) lspci reports as graphics card: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 04) -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xorg depends on: ii gnome-terminal [x-term 2.14.2-1 The GNOME 2 terminal emulator appl ii konsole [x-terminal-em 4:3.5.5a.dfsg.1-5 X terminal emulator for KDE ii libgl1-mesa-dri6.5.1-0.5 A free implementation of the OpenG ii libgl1-mesa-glx6.5.1-0.5 A free implementation of the OpenG ii libglu1-mesa 6.5.1-0.5 The OpenGL utility library (GLU) ii rxvt [x-terminal-emula 1:2.6.4-10VT102 terminal emulator for the X ii type-handling [not+spa 0.2.19dpkg architecture generation scrip ii xbase-clients 1:7.1.ds1-2 miscellaneous X clients ii xfonts-100dpi 1:1.0.0-3 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-3 75 dpi fonts for X ii xfonts-base1:1.0.0-4 standard fonts for X ii xfonts-scalable1:1.0.0-6 scalable fonts for X ii xkb-data 0.9-4 X Keyboard Extension (XKB) configu ii xserver-xorg 1:7.1.0-11the X.Org X server ii xterm [x-terminal-emul 222-1etch2X terminal emulator ii xutils 1:7.1.ds.3-1 X Window System utility programs xorg recommends no packages. -- no debconf information pgpaklTuIhKJt.pgp Description: PGP signature
Re: Bug#456007: xserver-xorg-video-intel: solution on resume after suspend to ram
reassign 456007 linux-2.6 tag 456007 fixed-upstream kthxbye On Tue, Feb 12, 2008 at 19:28:03 +0100, Filippo Giunchedi wrote: On Tue, Feb 12, 2008 at 06:48:35PM +0100, Filippo Giunchedi wrote: On Fri, Dec 28, 2007 at 10:37:10AM +0300, Aleksey Midenkov wrote: I have 965GM and in my situation none of suggested workarounds work apart from turning to text mode and back to xorg. It must be noted that text mode is broken after resume. But there is a good news that upstream developers have implemented suspend/resume code in i915 DRM module whish can be downloaded from git repository: $ git-clone git://anongit.freedesktop.org/git/mesa/drm I've tested it, works great on 2.6.23.12! Restores graphic and text modes like a charm! You mean the backlight is turned on after resume both in X and console? Is there any particular setting I should check? I am using 2.6.24-rc7 Confirmed, the backlight is restored on resume with today's mesa/drm git (d63b57749f097b36df04c6beff9b35a1dd859523) Corresponding fixes have been included in linus's tree between 2.6.25-rc2 and -rc3. Reassigning to the kernel. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426792: linux-image-2.6.21-1-686: soft lockup detected on CPU#1 (tick_sched_timer)
Package: linux-2.6 Version: 2.6.21-4 Severity: normal Hi, since the upgrade to 2.6.21, I get the messages shown below in dmesg (the machine is an intel core duo-based laptop). Cheers, Julien -- Package-specific info: ** Version: Linux version 2.6.21-1-686 (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070518 (prerelease) (Debian 4.1.2-8)) #1 SMP Sat May 26 16:14:59 UTC 2007 ** Not tainted ** Kernel log: [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === BUG: soft lockup detected on CPU#1! [c014aad3] softlockup_tick+0xa6/0xb5 [c012a05b] update_process_times+0x3b/0x5e [c0138d60] tick_sched_timer+0x78/0xbb [c01358e0] hrtimer_interrupt+0x131/0x1bd [c0138ce8] tick_sched_timer+0x0/0xbb [c0114bbd] smp_apic_timer_interrupt+0x6c/0x7d [c01f7e1a] acpi_hw_register_write+0x11b/0x14b [c010481c] apic_timer_interrupt+0x28/0x30 [f882a967] acpi_processor_idle+0x235/0x40a [processor] [c01023b5] cpu_idle+0xb5/0xd6 === ** Loaded modules: Module Size Used by button 7952 0 psmouse34952 0 snd_hda_intel 20248 4 michael_mic 2496 0 ieee80211_crypt_tkip10528 0 aes27680 0 ieee80211_crypt_ccmp 7008 0 ext2 60168 0 usb_storage76384 0 arc42016 2 ecb 3392 2 blkcipher 5956 1 ecb ieee80211_crypt_wep 5056 1 i915 21280 2 drm
Bug#426792: linux-image-2.6.21-1-686: soft lockup detected on CPU#1 (tick_sched_timer)
On Thu, May 31, 2007 at 03:04:42 +0200, Julien Cristau wrote: This looks similar to #426738, i'll try to test with 2.6.22-rc3 in a few days and report back. The BUG() doesn't seem to happen with linux-image-2.6.22-rc3-686 version 2.6.22~rc3-1~experimental.1~snapshot.8828 from buildserver.net. Cheers, Julien signature.asc Description: Digital signature
Bug#436166: lirc FTBFS
On Fri, Aug 10, 2007 at 14:37:03 +1000, Steffen Joeris wrote: Hi The linux/compiler.h file was in the linux-kernel-headers package, which got removed from unstable. The file as available for all archs, although afaik the code is not absoluteley arch-indep. The best way would probably be to put some ifdef conditions into the code and only use it, if it is present. No, the best way would be to stop including this file from userspace altogether. Cheers, Julien signature.asc Description: Digital signature
Re: Debian's Linux kernel continues to regress on freedom
On Wed, Sep 12, 2007 at 08:10:17 +0100, Colin Tuckley wrote: Nathanael Nerode wrote: drivers/media/video/dabfirmware.h ... drivers/net/tokenring/3c359_microcode.h In other words, *all* of the above drivers. Wrong! Those are not the *drivers* they are the source code header files needed to link to them. No they're not. You could just look at the files, you know... Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
synaptics touchpad not working
unmerge 475852 close 461760 2:1.4.1~git20080131-4 reassign 475852 linux-2.6 kthxbye On Fri, May 2, 2008 at 08:35:04 +0200, David Paleino wrote: Hi Julien, I've just upgraded my system and this wasn't fixed. I believe that this is a kernel problem though, but I don't know which package I should assign it to: kernel? linux-image? I've found, googling a bit, that this might be related (kernel option i8042.debug=1 at boot time -- relevant bits only): === dmesg === ... [1.357240] PNP: PS/2 Controller [PNP0303:C297,PNP0f13:C298] at 0x60,0x64 irq 1,12 [1.357480] drivers/input/serio/i8042.c: 20 - i8042 (command) [0] [1.357541] drivers/input/serio/i8042.c: 65 - i8042 (return) [0] [1.357547] drivers/input/serio/i8042.c: 60 - i8042 (command) [0] [1.357606] drivers/input/serio/i8042.c: 74 - i8042 (parameter) [0] ... (so on for a while) [1.359293] i8042.c: Detected active multiplexing controller, rev 1.1. ... [1.360088] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.360189] serio: i8042 AUX0 port at 0x60,0x64 irq 12 [1.360292] serio: i8042 AUX1 port at 0x60,0x64 irq 12 [1.360394] serio: i8042 AUX2 port at 0x60,0x64 irq 12 [1.360496] serio: i8042 AUX3 port at 0x60,0x64 irq 12 [1.363310] mice: PS/2 mouse device common for all mice ... [1.384094] drivers/input/serio/i8042.c: MUX error, status is 75, data is fe [7] [1.384097] drivers/input/serio/i8042.c: fe - i8042 (interrupt, 3, 12, timeout) [7] ... [1.386792] drivers/input/serio/i8042.c: 91 - i8042 (command) [7] [1.386850] drivers/input/serio/i8042.c: ed - i8042 (parameter) [7] [1.387027] drivers/input/serio/i8042.c: MUX error, status is 75, data is fe [7] [1.387030] drivers/input/serio/i8042.c: fe - i8042 (interrupt, 3, 12, timeout) [7] [1.391204] drivers/input/serio/i8042.c: 92 - i8042 (command) [8] [1.391263] drivers/input/serio/i8042.c: f2 - i8042 (parameter) [8] [1.391738] drivers/input/serio/i8042.c: MUX error, status is b5, data is fe [8] [1.391741] drivers/input/serio/i8042.c: fe - i8042 (interrupt, 4, 12, timeout) [8] [1.391750] drivers/input/serio/i8042.c: 92 - i8042 (command) [8] [1.391808] drivers/input/serio/i8042.c: ed - i8042 (parameter) [8] [1.392637] drivers/input/serio/i8042.c: MUX error, status is b5, data is fe [9] ... === === I attach my dmesg to this mail, so that anyone can see it. Please Julien, consider re-assigning this bug (as soon as possible, I'll try downgrading the whole system to testing, and see which package has problems) reassigning to the kernel. Please tell us what kernel image are you using, which version, etc, and if your touchpad used to work, what kernel you were using at the time. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#485528: pci-sysfs resourceN files are not available on all architectures
Package: libpciaccess,linux-2.6 Severity: important the pci_device_map_range() function from libpciaccess which is used by the X drivers to map pci BARs is implemented on linux using sysfs resourceN files, which the kernel only creates on architectures where HAVE_PCI_MMAP is defined. This is not the case for alpha, parisc, mips and m68k, as far as I can tell. See pci_create_resource_files() in linux/drivers/pci/pci-sysfs.c, and the respective include/asm-*/pci.h headers. This means that future versions of X (starting with xorg-server 1.5) are not going to work on these architectures unless this is fixed. We need to either get the kernel fixed, or fall back to mmaping /dev/mem in libpciaccess. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#514418: [FIX]: ultra45 boot failing...
On Mon, 2009-02-09 at 01:21 -0800, David Miller wrote: No, I would have said that if time is tight at least we can use fbdev as the Xorg driver for PCI devices on sparc until we have a better fix for Xorg. We can probably do that for r1. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514418: [FIX]: ultra45 boot failing...
On Mon, 2009-02-09 at 12:49 +0100, Julien Cristau wrote: On Mon, 2009-02-09 at 01:21 -0800, David Miller wrote: No, I would have said that if time is tight at least we can use fbdev as the Xorg driver for PCI devices on sparc until we have a better fix for Xorg. We can probably do that for r1. OK so here is a tentative patch to fall back to the fbdev driver on sparc. I'd appreciate if people could test it against lenny's xorg-server, and/or suggest better ways to do this. Cheers, Julien 0001-Add-an-fbdev-screen-as-a-fallback-on-sparc.patch Description: application/mbox
Bug#514418: [FIX]: ultra45 boot failing...
On Wed, 2009-02-25 at 13:41 +0100, Julien Cristau wrote: On Mon, 2009-02-09 at 12:49 +0100, Julien Cristau wrote: On Mon, 2009-02-09 at 01:21 -0800, David Miller wrote: No, I would have said that if time is tight at least we can use fbdev as the Xorg driver for PCI devices on sparc until we have a better fix for Xorg. We can probably do that for r1. OK so here is a tentative patch to fall back to the fbdev driver on sparc. I'd appreciate if people could test it against lenny's xorg-server, and/or suggest better ways to do this. I uploaded this to stable-proposed-updates, sparc binaries should appear after the next mirror push. There's still time to tweak things before the point release, so testing reports from sparc X users to 488...@bugs.debian.org are welcome (whether things work or not). Make sure you have xserver-xorg-video-fbdev installed. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522920: ELANTECH and lenny xorg
On Tue, Apr 7, 2009 at 12:25:59 -0700, Matt Taggart wrote: Regarding turning on CONFIG_MOUSE_PS2_ELANTECH... According the kernel help text, Note that if you enable this driver you will need an updated X.org Synaptics driver that does not require ABS_PRESSURE reports from the touchpad (i.e. post 1.5.0 version). You can grab a patch for the driver here: http://userweb.kernel.org/~dtor/synaptics-no-abspressure.patch The lenny version does not contain this patch. As long as being able to backport a newer kernel to lenny is a goal, this driver shouldn't be turned on. Or we could just add the xf86-input-synaptics patch in lenny r2, if somebody cares to file a bug against that... Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525896: linux-image-2.6.26-2-686: GUI mode (X.org) does not start on a HP DC7100
On Mon, Apr 27, 2009 at 08:10:48PM +0200, Pierre Bauduin wrote: I am using Debian Live on USB memory sticks. When the kernel that comes with Debian 5.0 was linux-image-2.6.26-1-686, I could flawlessly boot Debian Live in GUI mode (X.org) on a Hewlett Packard (HP) DC7100 machine. Now that Debian 5.0 has been updated, and that the kernel is linux-image-2.6.26-2-686, Debian Live won't boot in GUI mode (X.org) on the very same Hewlett Packard (HP) DC7100 machine. Debian Live starts in command-line mode, then attempts to start X. The screen goes blank for about five seconds, then it comes back to command-line mode. Note that is bug is about linux-image-2.6.26-2-686 but it is similar to Debian Bug 525482: same problem on the same hardware. I have included below output from lspci, lshw, as well as the contents of /var/log/Xorg.log please send the Xorg log from the working case. This doesn't sound like a kernel problem... Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514418: [FIX]: ultra45 boot failing...
On Wed, Feb 25, 2009 at 13:41:08 +0100, Julien Cristau wrote: On Mon, 2009-02-09 at 12:49 +0100, Julien Cristau wrote: On Mon, 2009-02-09 at 01:21 -0800, David Miller wrote: No, I would have said that if time is tight at least we can use fbdev as the Xorg driver for PCI devices on sparc until we have a better fix for Xorg. We can probably do that for r1. OK so here is a tentative patch to fall back to the fbdev driver on sparc. I'd appreciate if people could test it against lenny's xorg-server, and/or suggest better ways to do this. That patch doesn't work, because X craps itself if both a pci and a fb driver are loaded. I plan to revert it for lenny r2, and if time permits I'll try to make the xserver-xorg package generate an xorg.conf with Driver set to fbdev instead.. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#394690: cdparanoia: Current version causes system freeze on SATA attached cdrom at least
severity 394690 grave thanks On Sun, Oct 22, 2006 at 16:25:34 +0200, Brice Goglin wrote: Same problem here on thinkpads T43 and R52, with 2.6.17, 2.6.18 and 2.6.19-rc2. Even sysrq does not work after the freeze. Might be kernel related. Cloning to linux-2.6. My system freezes too using linux-image-2.6.17-2-686 version 2.6.17-9, and cdparanoia 3.10+debian~pre0-2. /proc/scsi/scsi reads: Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Hitachi HTS72108 Rev: MC4O Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: TSSTcorp Model: CDRW/DVD TSL462C Rev: DE06 Type: CD-ROM ANSI SCSI revision: 05 The machine is a Dell Latitude D520. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#502387: complete system hangup
severity 502387 important retitle 502387 [G4X] complete system hang kthxbye On Thu, Oct 16, 2008 at 08:48:12 +0200, Nico Schottelius wrote: Since some days, maybe since the upgrade from xserver-xorg-core from 2:1.4.2-6 to 2:1.4.2-7, the system has a total hangup when I specify to use the intel driver in xorg.conf. It runs fine without specification, in which case xorg choses vesa (that`s why I report the bug for the intel package). There's a reason we don't use the intel driver on cantiga by default. It seems the problems got tracked down recently though, see below. As seen below, I have the Intel Cantiga chipset runnin on the Lenovo X200. This happens with plain debian kernel (2.6.26) and also with 2.6.27-rc6. The patches at [1] and [2] might help. d-k: can we get the kernel part of this bug fixed in lenny? Cheers, Julien [1] http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commitdiff_plain;h=2052746fc8397130c120f0194a89938b0b62b6cb [2] http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=4dd00681dd0f9fce8dfd4592b46418edbbd2eeb4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#502387: complete system hangup
tag 502387 patch
clone 502387 -1
reassign -1 linux-2.6
retitle -1 [intel agp] stolen memory counting broken on G4X
kthxbye
On Thu, Oct 16, 2008 at 13:45:28 +0200, Julien Cristau wrote:
On Thu, Oct 16, 2008 at 08:48:12 +0200, Nico Schottelius wrote:
Since some days, maybe since the upgrade from xserver-xorg-core
from 2:1.4.2-6 to 2:1.4.2-7, the system has a total hangup when
I specify to use the intel driver in xorg.conf.
It runs fine without specification, in which case xorg choses
vesa (that`s why I report the bug for the intel package).
There's a reason we don't use the intel driver on cantiga by default.
It seems the problems got tracked down recently though, see below.
As seen below, I have the Intel Cantiga chipset runnin on the
Lenovo X200.
This happens with plain debian kernel (2.6.26) and also with
2.6.27-rc6.
The patches at [1] and [2] might help.
d-k: can we get the kernel part of this bug fixed in lenny?
Cheers,
Julien
[1]
http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commitdiff_plain;h=2052746fc8397130c120f0194a89938b0b62b6cb
[2]
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=4dd00681dd0f9fce8dfd4592b46418edbbd2eeb4
The kernel patch is now in mainline, commit id
82e14a6215cbc9804ecc35281e973c6c8ce22fe7 (attached). I'll apply the X
driver fix soon.
Cheers,
Julien
From 82e14a6215cbc9804ecc35281e973c6c8ce22fe7 Mon Sep 17 00:00:00 2001
From: Eric Anholt [EMAIL PROTECTED]
Date: Tue, 14 Oct 2008 11:28:58 -0700
Subject: [PATCH] agp: Fix stolen memory counting on G4X.
On the GM45, the amount of stolen memory mapped to the GTT was underestimated,
even though we had 508KB more available since the GTT doesn't take from
stolen memory. On the non-GM45 G4X, we overestimated how much stolen was
mapped to the GTT by 4KB, resulting in GPU page faults when that page was
accessed.
This update requires a corresponding update to xf86-video-intel to work
correctly.
Signed-off-by: Eric Anholt [EMAIL PROTECTED]
Signed-off-by: Dave Airlie [EMAIL PROTECTED]
---
drivers/char/agp/intel-agp.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
index 016fdf0..f1fe749 100644
--- a/drivers/char/agp/intel-agp.c
+++ b/drivers/char/agp/intel-agp.c
@@ -54,8 +54,7 @@
agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965Q_HB || \
agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965G_HB || \
agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965GM_HB || \
- agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965GME_HB || \
- agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_GM45_HB)
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965GME_HB)
#define IS_G33 (agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G33_HB || \
agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_Q35_HB || \
@@ -63,7 +62,8 @@
#define IS_G4X (agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_IGD_E_HB || \
agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_Q45_HB || \
- agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G45_HB)
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G45_HB || \
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_GM45_HB)
extern int agp_memory_reserved;
@@ -525,8 +525,10 @@ static void intel_i830_init_gtt_entries(void)
size += 4;
} else if (IS_G4X) {
/* On 4 series hardware, GTT stolen is separate from graphics
- * stolen, ignore it in stolen gtt entries counting */
- size = 0;
+ * stolen, ignore it in stolen gtt entries counting. However,
+ * 4KB of the stolen memory doesn't get mapped to the GTT.
+ */
+ size = 4;
} else {
/* On previous hardware, the GTT size was just what was
* required to map the aperture.
--
1.5.6.5
Re: Firmware removal progress
On Fri, Oct 17, 2008 at 00:44:45 +0100, Ben Hutchings wrote: On Fri, 2008-10-17 at 00:34 +0100, Ben Hutchings wrote: I'm going to post a series of patches that aim to fix the RC bugs relating to sourceless firmware. Unfortunately, a quick search suggests that there is still more left: file licence distributable -- drivers/char/drm/mga_ucode.h GPLv2 no * Copyright 1999 Matrox Graphics Inc. * All Rights Reserved. * * Permission is hereby granted, free of charge, to any person obtaining a * copy of this software and associated documentation files (the Software), * to deal in the Software without restriction, including without limitation * the rights to use, copy, modify, merge, publish, distribute, sublicense, * and/or sell copies of the Software, and to permit persons to whom the * Software is furnished to do so, subject to the following conditions: * * The above copyright notice and this permission notice shall be included * in all copies or substantial portions of the Software. * * THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL * MATROX GRAPHICS INC., OR ANY OTHER CONTRIBUTORS BE LIABLE FOR ANY CLAIM, * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE * OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. That's not GPLv2, and is distributable. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502606: Bug#502387: complete system hangup
On Sat, Oct 18, 2008 at 11:47:48 +0200, Julien Cristau wrote:
The kernel patch is now in mainline, commit id
82e14a6215cbc9804ecc35281e973c6c8ce22fe7 (attached).
Doesn't apply as-is because 2.6.26 is missing 'intel_agp: official name
for GM45 chipset' (99d32bd5c7b1caa05d1fe3c89b08aabd459bc12a). Is the
attached patch ok (it seems to apply fine)?
Cheers,
Julien
Index: changelog
===
--- changelog (revision 12346)
+++ changelog (working copy)
@@ -1,3 +1,10 @@
+linux-2.6 (2.6.26-10) UNRELEASED; urgency=low
+
+ * intel_agp: official name for GM45 chipset
+ * agp: Fix stolen memory counting on G4X (closes: #502606).
+
+ -- Julien Cristau [EMAIL PROTECTED] Sat, 18 Oct 2008 16:46:28 +0200
+
linux-2.6 (2.6.26-9) unstable; urgency=low
[ Bastian Blank ]
Index: patches/bugfix/x86/agp-Fix-stolen-memory-counting-on-G4X.patch
===
--- patches/bugfix/x86/agp-Fix-stolen-memory-counting-on-G4X.patch (revision 0)
+++ patches/bugfix/x86/agp-Fix-stolen-memory-counting-on-G4X.patch (revision 0)
@@ -0,0 +1,60 @@
+From 82e14a6215cbc9804ecc35281e973c6c8ce22fe7 Mon Sep 17 00:00:00 2001
+From: Eric Anholt [EMAIL PROTECTED]
+Date: Tue, 14 Oct 2008 11:28:58 -0700
+Subject: [PATCH] agp: Fix stolen memory counting on G4X.
+
+On the GM45, the amount of stolen memory mapped to the GTT was underestimated,
+even though we had 508KB more available since the GTT doesn't take from
+stolen memory. On the non-GM45 G4X, we overestimated how much stolen was
+mapped to the GTT by 4KB, resulting in GPU page faults when that page was
+accessed.
+
+This update requires a corresponding update to xf86-video-intel to work
+correctly.
+
+Signed-off-by: Eric Anholt [EMAIL PROTECTED]
+Signed-off-by: Dave Airlie [EMAIL PROTECTED]
+---
+ drivers/char/agp/intel-agp.c | 12 +++-
+ 1 files changed, 7 insertions(+), 5 deletions(-)
+
+diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
+index 016fdf0..f1fe749 100644
+--- a/drivers/char/agp/intel-agp.c
b/drivers/char/agp/intel-agp.c
+@@ -54,8 +54,7 @@
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965Q_HB || \
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965G_HB || \
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965GM_HB || \
+- agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965GME_HB || \
+- agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_GM45_HB)
++ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_82965GME_HB)
+
+ #define IS_G33 (agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G33_HB || \
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_Q35_HB || \
+@@ -63,7 +62,8 @@
+
+ #define IS_G4X (agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_IGD_E_HB || \
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_Q45_HB || \
+- agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G45_HB)
++ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G45_HB || \
++ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_GM45_HB)
+
+ extern int agp_memory_reserved;
+
+@@ -525,8 +525,10 @@ static void intel_i830_init_gtt_entries(void)
+ size += 4;
+ } else if (IS_G4X) {
+ /* On 4 series hardware, GTT stolen is separate from graphics
+- * stolen, ignore it in stolen gtt entries counting */
+- size = 0;
++ * stolen, ignore it in stolen gtt entries counting. However,
++ * 4KB of the stolen memory doesn't get mapped to the GTT.
++ */
++ size = 4;
+ } else {
+ /* On previous hardware, the GTT size was just what was
+ * required to map the aperture.
+--
+1.5.6.5
+
Index: patches/bugfix/x86/intel_agp-official-name-for-GM45-chipset.patch
===
--- patches/bugfix/x86/intel_agp-official-name-for-GM45-chipset.patch (revision 0)
+++ patches/bugfix/x86/intel_agp-official-name-for-GM45-chipset.patch (revision 0)
@@ -0,0 +1,69 @@
+From 99d32bd5c7b1caa05d1fe3c89b08aabd459bc12a Mon Sep 17 00:00:00 2001
+From: Zhenyu Wang [EMAIL PROTECTED]
+Date: Wed, 30 Jul 2008 12:26:50 -0700
+Subject: [PATCH] intel_agp: official name for GM45 chipset
+
+Signed-off-by: Zhenyu Wang [EMAIL PROTECTED]
+Cc: Dave Airlie [EMAIL PROTECTED]
+Signed-off-by: Andrew Morton [EMAIL PROTECTED]
+Signed-off-by: Dave Airlie [EMAIL PROTECTED]
+---
+ drivers/char/agp/intel-agp.c | 14 +++---
+ 1 files changed, 7 insertions(+), 7 deletions(-)
+
+diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
+index df70264..e0d68aa 100644
+--- a/drivers/char/agp/intel-agp.c
b/drivers/char/agp/intel-agp.c
+@@ -32,8 +32,8 @@
+ #define PCI_DEVICE_ID_INTEL_Q35_IG 0x29B2
+ #define PCI_DEVICE_ID_INTEL_Q33_HB 0x29D0
+ #define PCI_DEVICE_ID_INTEL_Q33_IG 0x29D2
+-#define PCI_DEVICE_ID_INTEL_IGD_HB 0x2A40
+-#define PCI_DEVICE_ID_INTEL_IGD_IG 0x2A42
++#define PCI_DEVICE_ID_INTEL_GM45_HB 0x2A40
++#define PCI_DEVICE_ID_INTEL_GM45_IG 0x2A42
+ #define
Bug#500358: Fix found
On Tue, Nov 11, 2008 at 18:22:57 +0100, Bastian Blank wrote: The first patch is fine. The revert is not. Even if the revert is the only way to get X to work on those machines in lenny? Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500358: Fix found
On Tue, Nov 11, 2008 at 22:10:03 +0100, Bastian Blank wrote: On Tue, Nov 11, 2008 at 08:20:01PM +0100, Julien Cristau wrote: On Tue, Nov 11, 2008 at 18:22:57 +0100, Bastian Blank wrote: The first patch is fine. The revert is not. Even if the revert is the only way to get X to work on those machines in lenny? I fail to see the _kernel_ bug it fixes. I now know that this change triggers a bug in the old (considered broken by design[1]) PCI code in _X.org_. The revert doesn't fix a kernel bug. It works around an X bug. I thought that was clear all along, sorry if it wasn't. Even if the revert breaks other things, it wouldn't be a regression from previous releases, though. We're not going to ship a newer Xorg in lenny, so with that revert we'd be fixing a known important regression by reopening a long-standing bug. I agree it's not ideal, but it doesn't seem like we can make everyone happy here, and that seems to be the least bad solution for this bug as far as lenny is concerned. Thanks for considering it. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#513604: linux-libc-dev: drm headers conflict with libdrm-dev
Package: linux-libc-dev Version: 2.6.28-1~experimental.1~snapshot.12651 Severity: serious Justification: undeclared file conflict Hi, the kernel started installing drm headers which previously came with libdrm-dev. If we decide to do things this way for squeeze, linux-libc-dev will need to Replaces appropriate versions of libdrm-dev, and libdrm will stop shipping these headers. However, maybe it'd make sense to stop shipping these headers from linux-libc-dev for now, until this can be uploaded to sid after lenny? Another temporary solution is to have an unversioned Replaces... Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 495673 to linux-2.6 ...
reassign 495673 linux-2.6 2.6.26-5 retitle 495673 linux-2.6: synaptics touchpad not detected (worked with 2.6.22-3) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: imminent 2.6.26 sid upload
On Wed, Jul 23, 2008 at 09:02:26 -0300, Otavio Salvador wrote: I'd prefer to have it on experimental before upload it to unstable so first and more urgent issues wouldn't bother us and users however this is more up to you and RM team then me. My preference would be: - upload to experimental - wait for at least 5 days without issues That's just adding an arbitrary 5 days delay. Uploading to experimental won't uncover new issues, because nobody uses packages in experimental. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: imminent 2.6.26 sid upload
On Tue, Jul 29, 2008 at 10:12:32 -0300, Otavio Salvador wrote: maximilian attems [EMAIL PROTECTED] writes: shall we give a README.Debian note on the vserser-xen flavour dropping? I'd say a NEWS entry. If the package doesn't exist anymore, it can't have a NEWS file. And spamming the users of every other image with a note that some flavour they don't use got dropped doesn't sound optimal. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On Fri, Feb 19, 2010 at 09:56:53 +0100, Michal Suchanek wrote: When kms is enabled the radeon module cannot be unloaded. rmmod complains that the module is busy while the X server is not running. This is different from my experience with intel KMS and quite annoying. err, it's exactly the same with i915. You can't unload it before unbinding the console. Anyway, I think this bug can be closed with 2.6.32-9, which turns VT_HW_CONSOLE_BINDING on. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100220125452.ga25...@radis.liafa.jussieu.fr
Bug#550562: [fwd] [Bug 14535] Memory corruption detected in low memory
Ben, any chance you could try the kernel branch Dave points to in the message below? Thanks, Julien - Forwarded message from bugzilla-dae...@bugzilla.kernel.org - From: bugzilla-dae...@bugzilla.kernel.org Date: Sun, 21 Feb 2010 19:55:47 GMT To: dri-de...@lists.sourceforge.net Subject: [Bug 14535] Memory corruption detected in low memory http://bugzilla.kernel.org/show_bug.cgi?id=14535 --- Comment #20 from Dave Airlie airl...@linux.ie 2010-02-21 19:55:41 --- I've tried to reproduce this locally and haven't had any luck using Fedora running in user mode setting. It would help if someone could try with an old kernel and see it still happens. Alternatively can someone test this with git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-radeon-testing We haven't touched the non-kms radeon driver much, the only thing that seems to be happening is mesa is getting better at creating fully used command buffers and the kernel has gotten worse at giving out large kmallocs (64k), there are fixes for this in drm-radeon-testing to avoid the larger mallocs which will hopefully help in some way, I'll see if I can spot a codepath where we send crap to the GPU, but we currently test the offsets userspace gives us and validate them for crap to avoid just this. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. - End forwarded message - -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100222133637.gl2...@patate.is-a-geek.org
Bug#571215: Backlight turned off during bootup
On Wed, Feb 24, 2010 at 12:58:54 +0100, Uli Schlachter wrote: Feb 24 12:34:40 psytux kernel: [0.548357] vesafb: framebuffer at 0x8000, mapped to 0xc9001098, using 5120k, total 5120k Feb 24 12:34:40 psytux kernel: [0.548360] vesafb: mode is 1280x1024x32, linelength=5120, pages=0 Feb 24 12:34:40 psytux kernel: [0.548362] vesafb: scrolling: redraw Feb 24 12:34:40 psytux kernel: [0.548364] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0 Feb 24 12:34:40 psytux kernel: [0.588241] Console: switching to colour frame buffer device 160x64 Feb 24 12:34:40 psytux kernel: [0.628004] fb0: VESA VGA frame buffer device [...] Feb 24 12:34:40 psytux kernel: [0.732304] [drm] Initialized drm 1.1.0 20060810 Feb 24 12:34:40 psytux kernel: [0.743618] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 Feb 24 12:34:40 psytux kernel: [0.743622] i915 :00:02.0: setting latency timer to 64 Feb 24 12:34:40 psytux kernel: [0.758588] alloc irq_desc for 29 on node -1 Feb 24 12:34:40 psytux kernel: [0.758592] alloc kstat_irqs on node -1 Feb 24 12:34:40 psytux kernel: [0.758601] i915 :00:02.0: irq 29 for MSI/MSI-X Feb 24 12:34:40 psytux kernel: [0.758608] [drm] set up 63M of stolen space Feb 24 12:34:40 psytux kernel: [1.320148] [drm] TV-20: set mode NTSC 480i 0 Feb 24 12:34:40 psytux kernel: [1.466907] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Feb 24 12:34:40 psytux kernel: [1.467017] fb1: inteldrmfb frame buffer device Screwed up handoff from vesafb to i915. Should be fixed with today's 2.6.32-9 hopefully. Although really you shouldn't be using vesafb. Cheers, Julien signature.asc Description: Digital signature
Re: [ubuntu-x] Status of kernel X drivers
On Sun, Feb 21, 2010 at 23:20:14 +, Ben Hutchings wrote: Fedora has been backporting drm (and nouveau) for a long time but it's not so clear what means for RHEL. I think this is something we will also consider doing in Debian. A year from now I expect nv to be dead and radeon UMS to be removed upstream, making it impractical to backport new hardware support. Given that, the maintenance burden for 2.6.33 drm should be lower. But this is really outside my area of expertise and certainly not my decision to make. For radeon it seems clear that we need the 2.6.33 code or stay with UMS, and nouveau is not in .32, so basically the question seems to be about i915. My impression is that 2.6.32 was quite bad, and 2.6.32.x has gotten it into a better shape (except for 8xx, but that's been broken for quite a while, and not just with kms, so...). Now if we're confident that either i915 in 2.6.33 is better than .32.9 already or that the regressions it introduces can be fixed in the next month or couple of months, then backporting drm from .33 seems like it would be a good thing to do for squeeze. Cheers, Julien signature.asc Description: Digital signature
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On Mon, Mar 1, 2010 at 09:31:52 +0100, Michal Suchanek wrote: On 26 February 2010 17:23, Moritz Muehlenhoff j...@inutil.org wrote: On Sat, Feb 20, 2010 at 01:54:52PM +0100, Julien Cristau wrote: On Fri, Feb 19, 2010 at 09:56:53 +0100, Michal Suchanek wrote: When kms is enabled the radeon module cannot be unloaded. rmmod complains that the module is busy while the X server is not running. This is different from my experience with intel KMS and quite annoying. err, it's exactly the same with i915. You can't unload it before unbinding the console. Anyway, I think this bug can be closed with 2.6.32-9, which turns VT_HW_CONSOLE_BINDING on. Michal, 2.6.32-9 is in unstable now. Can you please retest? I don't see any difference. It doesn't just work. If I am supposed to rebind the vgacon driver manually then I have no idea how. Yes, you need to unbind radeon manually to be able to unload it. Is this documented somewhere? I don't know. Probably. I have no idea why anyone would want to do that anyway. I tried to restore my setup with radeonfb but it no longer loads for me automatically and I found there is no documentation whatsoever for radeonfb :-S You don't want to use radeonfb. Cheers, Julien signature.asc Description: Digital signature
Bug#572067: linux-libc-dev: Can not install, file conflict with libdrm
On Fri, Mar 5, 2010 at 04:03:15 +, Ben Hutchings wrote: On Mon, 2010-03-01 at 13:50 +0100, Jens-Michael Hoffmann wrote: Package: linux-libc-dev Version: 2.6.33-1~experimental.2 Severity: normal When trying to install linux-libc-dev from experimental, dpkg shows the following error message: dpkg: error processing /var/cache/apt/archives/linux-libc-dev_2.6.33-1~experimental.2_amd64.deb (--unpack): trying to overwrite '/usr/include/drm/nouveau_drm.h', which is also in package libdrm-dev 0:2.4.18-2 It makes no sense to have the DRM headers split between libdrm-dev and linux-libc-dev. I'm happy to have libdrm-dev provide them all. What do you want to do? I think we should go back to libdrm-dev installing the headers. I sent a patch to dri-devel a few days ago that makes libdrm install its headers in $(includedir)/libdrm so they don't conflict with the ones installed by the kernel, waiting for some feedback on that… Cheers, Julien signature.asc Description: Digital signature
Bug#574630: linux-base: postinst fails if udev's persistent-cd.rules has duplicates
Package: linux-base Version: 2.6.32-10 Severity: serious Due to some old bug in udev, my /etc/udev/rules.d/70-persistent-cd.rules had a number of duplicate rules (timestamp on the file suggests it might have been #374539). This leads to an error in linux-base.postinst: Modification of non-creatable array value attempted, subscript -1 at /var/lib/dpkg/info/linux-base.postinst line 667, GEN6 line 12. dpkg: error processing linux-base (--configure): subprocess installed post-installation script returned error exit status 9 After removing the duplicates from the rules file, installation worked fine (but warned me that it left /dev/scd0 unchanged in fstab). Cheers, Julien -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii libapt-pkg-perl 0.1.24 Perl interface to libapt-pkg ii libuuid-perl 0.02-3+b1 Perl extension for using UUID inte linux-base recommends no packages. linux-base suggests no packages. -- debconf information: * linux-base/disk-id-manual: linux-base/disk-id-convert-plan-no-relabel: true * linux-base/disk-id-convert-auto: true * linux-base/disk-id-convert-plan: true 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
Re: Bug#543815: Processed: Bug#543815: Establishing a Severity rating
On Tue, Sep 1, 2009 at 18:25:20 +0200, Moritz Muehlenhoff wrote: The problem is that the standard severities cannot be mapped 1:1 on the kernel package. Since the kernel is the core component of 99% of all Debian systems, it's in the nature of the beast that any problem which makes a system unbootable renders the package unusable for the person filing the bug and the default descriptions lead bug reporters to believe that grave or above is the correct severity. A solution might be for the kernel packages to include the below information in a 'presubj' file to be shown by reportbug? As far as the kernel is concerned, the severies applied by current practice are more or less: critical: - bugs leading to data loss on a wide range of systems grave: - security bugs leading to remote denial of service or local privilege escalation - bugs which make the package unusable on a wide range of systems serious: - a severe violation of Debian policy (as in the standard severities) important: - bugs which render some systems (e.g. a certain model or systems with a specific adaptor/device) unusable normal to wishlist are treated as in standard policies. Since this is a common mistake, it might be a good idea to display different descriptions when filing a bug against the linux-2.6 source package. This is what Maks's bug report is about. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Sun, Aug 16, 2009 at 14:41:24 +0200, Marc Brockschmidt wrote: * How many big transitions will the upcoming changes cause? When should those happen? Can we do something to make them easier? One more thing. Intel plans to deprecate userspace mode setting with their Q4 2009 release (meaning December this year, so probably something we'll want for squeeze, depending on the freeze date you pick). This means the intel X driver won't work with lenny's kernel, so we might have to figure out an upgrade path somehow (which might be to make the driver fall back to the vesa driver if it doesn't find a modesetting-capable kernel). This might also mean that we'll want to turn kms on by default in the debian kernel, or have xserver-xorg-video-intel install a file in /etc/modprobe.d/ to set i915.modeset. cc:ing debian-kernel as a heads-up. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Wed, Sep 9, 2009 at 12:36:58 +0200, Bastian Blank wrote: On Wed, Sep 09, 2009 at 11:37:18AM +0200, Julien Cristau wrote: One more thing. Intel plans to deprecate userspace mode setting with their Q4 2009 release (meaning December this year, so probably something we'll want for squeeze, depending on the freeze date you pick). Oh, no. Not again. It does not yet properly work without the new memory manager (#538442). And KMS is completely unusable currently on this kernels. This might also mean that we'll want to turn kms on by default in the debian kernel, Is KMS backward compatible with older versions of the intel driver? No :/ I guess we could also decide to freeze on the intel Q3 bits, but then we're likely to be on our own for new hardware support and stuff like that. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Wed, Sep 9, 2009 at 14:42:52 +0200, Xavier Bestel wrote: On Wed, 2009-09-09 at 13:31 +0200, Julien Cristau wrote: On Wed, Sep 9, 2009 at 12:36:58 +0200, Bastian Blank wrote: On Wed, Sep 09, 2009 at 11:37:18AM +0200, Julien Cristau wrote: This might also mean that we'll want to turn kms on by default in the debian kernel, Is KMS backward compatible with older versions of the intel driver? No :/ Running the kernel with intel.modeset=0 doesn't help ? Yeah that works (with s/intel/i915/), but it's not quite user friendly to crash unless that's manually added to the kernel command line. So it's probably better to default kms off in the kernel, and have the new userspace turn it on via /etc/modprobe.d/. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: X.org plans for the squeeze cycle
On Thu, Sep 10, 2009 at 09:07:34 +0200, Vincent Danjean wrote: And in 2.6.31-rc6, KMS is not stable enought to be used for my day-to-day work. It even leads to data corruption. See #545517 Since I remove KMS (ie since my bug report), I had no problem at all (with many many suspend-resume cycles) Please file that as a bug on https://bugs.freedesktop.org/enter_bug.cgi?product=DRIcomponent=DRM%2FIntel There's no way it's going to get fixed otherwise. I haven't used suspend to disk in years, eg... See also http://intellinuxgraphics.org/how_to_report_bug.html Thanks, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#541307: xserver-xorg: x locks requires reboot
reassign 541307 src:linux-2.6 2.6.30-1 retitle 541307 agp/intel: gpu lockups on 865G tag 541307 upstream patch kthxbye On Thu, Aug 20, 2009 at 11:27:39 -0700, Carl Worth wrote: Excerpts from Brice Goglin's message of Thu Aug 20 00:07:26 -0700 2009: 865G support is severely broken unfortunately. It was supposed to improve when disabling render acceleration in driver 2.8.0-2 but it still miserably fails on my machine. I had to downgrade to 2.7.1 without UXA to get something to work. Hi Brice, I'm glad to see this message from you. Just moments ago I fired up an 865 machine planning to disable RenderAccel for 8xx in the upstream code. It's interesting to learn that this isn't enough to fix things, (since we know that the RenderAccel code is very broken for 8xx). Have you had any luck discovering more about what's happening here, (for example, doing any bisecting or so?). I'm interested in getting the driver to be stable on all hardware in current use as quickly as possible, (even if that means just reverting to the old code as in 2.7.1 for 8xx for example). Anyway, I'll start experimenting with my 865 here, but any input you might be able to provide will be appreciated. I'm reassigning this to the kernel since it turned out to be a bug in the intel_agp chipset flush routine. The patch is queued at http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=e517a5e97080bbe52857bd0d7df9b66602d53c4d Kernel maintainers, any chance to get this into sid soonish? Thanks, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
BUG in agp_generic_create_gatt_table
clone 546714 -1 submitter -1 Fredrik Häll freh...@gmail.com reassign -1 linux-2.6 2.6.30-6 tag -1 - moreinfo retitle -1 [agpgart-sis] BUG: unable to handle kernel NULL pointer dereference kthxbye On Wed, Sep 23, 2009 at 17:32:16 +0200, Fredrik Häll wrote: [0.00] Linux version 2.6.30-1-686 (Debian 2.6.30-6) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-1) ) #1 SMP Sat Aug 15 19:11:58 UTC 2009 [...] [1.415000] Linux agpgart interface v0.103 [1.417646] agpgart-sis :00:00.0: SiS chipset [1039/0760] [1.417998] agpgart-sis :00:00.0: AGP aperture is 4M @ 0xe000 [1.420680] agpgart-sis :00:00.0: AGP bridge [1039/0760] [1.420715] BUG: unable to handle kernel NULL pointer dereference at 0008 [1.420796] IP: [de74b964] agp_generic_create_gatt_table+0x53/0x176 [agpgart] [1.420861] *pde = [1.420911] Oops: [#1] SMP [1.420983] last sysfs file: /sys/module/agpgart/initstate [1.421011] Modules linked in: amd64_agp(+) sis_agp agpgart thermal fan thermal_sys [1.421203] [1.421231] Pid: 431, comm: modprobe Not tainted (2.6.30-1-686 #1) Aspire 3000 [1.421260] EIP: 0060:[de74b964] EFLAGS: 00010246 CPU: 0 [1.421294] EIP is at agp_generic_create_gatt_table+0x53/0x176 [agpgart] [1.421322] EAX: 0002 EBX: 00cc ECX: 0002 EDX: [1.421350] ESI: dc2faec0 EDI: 01de EBP: 0010 ESP: dc2bbcfc [1.421378] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [1.421406] Process modprobe (pid: 431, ti=dc2ba000 task=dc369ba0 task.ti=dc2ba000) [1.421434] Stack: [1.421459] dc2bbd00 00cc 0100 01de dc2faec0 de74a226 de729e5c [1.421652] e000 dd8db800 de729abc e000 00a0 dc2faec0 [1.421893] a020c914 dd8bb800 0001 dd8db858 0002 0070 [1.422161] Call Trace: [1.422189] [de74a226] ? agp_add_bridge+0x13f/0x32e [agpgart] [1.422249] [de729abc] ? agp_amd64_probe+0x508/0x550 [amd64_agp] [1.422305] [de717000] ? agp_amd64_init+0x0/0xac [amd64_agp] [1.422360] [de71708e] ? agp_amd64_init+0x8e/0xac [amd64_agp] [1.422415] [c0101148] ? do_one_initcall+0x5f/0x17a [1.422472] [c014458e] ? each_symbol+0x3b/0x1f3 [1.422526] [c0144ee4] ? find_symbol_in_section+0x0/0xb1 [1.422581] [c01ff3d4] ? idr_get_empty_slot+0x145/0x202 [1.422637] [c01ff3d4] ? idr_get_empty_slot+0x145/0x202 [1.422691] [c01ff565] ? ida_get_new_above+0xd4/0x178 [1.422744] [c01ff3d4] ? idr_get_empty_slot+0x145/0x202 [1.422798] [c01ff565] ? ida_get_new_above+0xd4/0x178 [1.422852] [c01c9430] ? sysfs_ilookup_test+0x0/0xd [1.422907] [c019b837] ? ifind+0x22/0x50 [1.422961] [c01c9430] ? sysfs_ilookup_test+0x0/0xd [1.423015] [c01c99f0] ? sysfs_addrm_finish+0x13/0x199 [1.423068] [c01c96d4] ? __sysfs_add_one+0x20/0x69 [1.423122] [c01c975a] ? sysfs_add_one+0x10/0xad [1.423175] [c0146fa3] ? load_module+0x1165/0x12e7 [1.423229] [c0179f7d] ? __do_fault+0x325/0x355 [1.423286] [c015f9ce] ? marker_update_probe_range+0x16/0x1d4 [1.423342] [c016091a] ? tracepoint_module_notify+0x21/0x24 [1.423396] [c0139ef6] ? notifier_call_chain+0x2a/0x47 [1.423451] [c013a14b] ? __blocking_notifier_call_chain+0x3f/0x49 [1.423505] [c01471ac] ? sys_init_module+0x87/0x187 [1.423559] [c01030e9] ? syscall_call+0x7/0xb [1.423613] Code: 56 10 0f 84 89 00 00 00 89 c5 45 c1 e5 04 8b 46 04 8b 40 0c 83 f8 01 74 12 72 10 83 f8 02 74 0b 31 ff c7 04 24 00 00 00 00 eb 09 8b 7a 08 8b 52 04 89 14 24 89 fa b8 d0 00 00 00 e8 59 40 a2 e1 [1.424017] EIP: [de74b964] agp_generic_create_gatt_table+0x53/0x176 [agpgart] SS:ESP 0068:dc2bbcfc [1.424017] CR2: 0008 [1.425305] ---[ end trace d271a550c1613267 ]--- looks like a kernel bug, moving your issue over there. the initial report was from someone else and may well be different. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548290: marked as done (linux-image-2.6.30-2-686: 2.6.30 cannot find root file system)
On Mon, Sep 28, 2009 at 19:15:52 +0200, Jonathan Kaye wrote: /pre /blockquote Hi Vincent,br I would be delighted, no overjoyed to give you all the information you want. Please tell me what you need and I'll do my best to supply that information.br br I did try to use the UUID in the grub root parameter as well as in the fstab file but to no avail.br Regards,br Jonathanbr br /body /html First thing to do is don't use the -quiet email address for the bug report, as that won't reach anyone. Next, send plain text mail, not html. Finally, describe as precisely as you can your setup, what you tried and what the result was for each attempt. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#549335: xorg: DRI/DRM hangs machine for ati/r128 driver (squeeze;powerpc)
reassign 549335 linux-2.6 2.6.30-6 close 549335 2.6.30-7 kthxbye On Fri, Oct 2, 2009 at 13:31:36 -0400, Jeffrey B. Green wrote: [ 59.363422] [drm] Initialized drm 1.1.0 20060810 [ 59.400604] [drm] Initialized r128 2.5.0 20030725 for :00:10.0 on minor 0 [ 59.484082] agpgart-uninorth :00:0b.0: putting AGP V2 device into 1x mode [ 59.484117] aty128fb :00:10.0: putting AGP V2 device into 1x mode [ 59.924656] platform r128_cce.0: firmware: requesting r128/r128_cce.bin [ 60.042432] r128_cce: Failed to load firmware r128/r128_cce.bin [ 60.042465] [drm:r128_do_init_cce] *ERROR* Failed to load firmware! [ 60.042655] Unable to handle kernel paging request for data at address 0x0094 [ 60.042671] Faulting instruction address: 0xea0c1afc [ 60.042691] Oops: Kernel access of bad area, sig: 11 [#1] [ 60.042703] PowerMac [ 60.042711] Modules linked in: r128 drm nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc joydev airport wacom evdev orinoco ext3 jbd mbcache dm_mod usbhid hid aic7xxx scsi_transport_spi firewire_ohci sungem sungem_phy firewire_core crc_itu_t ide_cd_mod cdrom scsi_mod uninorth_agp agpgart i2c_powermac [last unloaded: scsi_wait_scan] [ 60.042855] NIP: ea0c1afc LR: ea09a228 CTR: ea0c1a54 [ 60.042875] REGS: c1f61d20 TRAP: 0300 Not tainted (2.6.30-1-powerpc) [ 60.042888] MSR: 9032 EE,ME,IR,DR CR: 20042444 XER: 2000 [ 60.042921] DAR: 0094, DSISR: 4000 [ 60.042936] TASK = e7873510[2303] 'Xorg' THREAD: c1f6 [ 60.042947] GPR00: 0001 c1f61dd0 e7873510 e5f4 c1f61df8 c1e33840 e907 0fadc568 [ 60.042983] GPR08: c1e337e0 80086442 0004 101eccc0 101adde0 101addec [ 60.043018] GPR16: 10070ef0 101e4d28 101e4d2c 1008bf50 1009bb50 0001 bfc2e85c [ 60.043053] GPR24: 109d2e18 e5f4 ea0c1a54 80086442 e5f4 c1f61df8 c1e33840 [ 60.043136] NIP [ea0c1afc] r128_cce_stop+0xa8/0x14c [r128] [ 60.043327] LR [ea09a228] drm_ioctl+0x250/0x36c [drm] [ 60.043339] Call Trace: [ 60.043376] [c1f61dd0] [c009cef4] generic_file_aio_write+0x74/0xf0 (unreliable) [ 60.043455] [c1f61df0] [ea09a228] drm_ioctl+0x250/0x36c [drm] [ 60.043481] [c1f61ea0] [c00d4428] vfs_ioctl+0x68/0x80 [ 60.043501] [c1f61eb0] [c00d4a2c] do_vfs_ioctl+0x5c8/0x664 [ 60.043522] [c1f61f10] [c00d4b20] sys_ioctl+0x58/0x88 [ 60.043547] [c1f61f40] [c0014df8] ret_from_syscall+0x0/0x40 [ 60.043575] --- Exception: c01 at 0xfadc568 [ 60.043582] LR = 0xfadc4cc [ 60.043592] Instruction dump: [ 60.043606] 80e90040 38638564 38840054 54c6 7fc8f378 7c852378 480064dd 3860ffea [ 60.043642] 48a0 801d 2f80 419e0038 813f0094 81290010 39290714 7c0004ac [ 60.043686] ---[ end trace 88264052174689a3 ]--- [ 60.057198] [drm:drm_release] *ERROR* Device busy: 1 Thanks for the log. This is likely a duplicate of bug#541630, which is fixed in the kernel package in unstable. You'll probably also want to install the firmware-linux package, which will provide the necessary firmware to enable DRI on your hardware. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525896: linux-image-2.6.26-2-686: GUI mode (X.org) does not start on a HP DC7100
reassign 525896 xserver-xorg-video-intel 2:2.3.2-2+lenny6 kthxbye On Wed, Apr 29, 2009 at 09:16:48 +0200, Pierre Bauduin wrote: Hi and thanks for your interest... Here's the /var/log/Xorg.log when I boot a Debian Live system based on Debian 5.0 (not 5.0.1) based on linux-image-2.6.26-1-686. In that case the GUI mode (X.org) does start on the HP DC7100: Good to know that works. There shouldn't be any relevant software difference between 5.0 and 5.0.1 though, so this seems weird. Your non-working log shows that the VGA output is not detected by the driver, whereas the working log shows the VGA output as connected. Can you check that the cable is connected properly on both ends? Is the monitor directly connected to the machine (not through a KVM or similar device)? Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550981: DRM output from dmesg for i915:modeset=1
On Wed, Oct 14, 2009 at 13:32:26 -0400, Dominique Brazziel wrote: The previous information was from a successful (X starts w/1152x864) run. Below is the relevant DRM info from the unsuccessful (1024x768) run, with complete dmesg and X log info attached: Thanks for this. Could you test with 2.6.31 from experimental, and if that still has the bogus LVDS output, forward this on to intel at bugs.freedesktop.org? There's some guidelines at http://intellinuxgraphics.org/how_to_report_bug.html I guess the output of 'grep -r . /sys/class/dmi/' and video bios could be helpful to them as well. You can get the bios with: echo 1 /sys/devices/pci:00/:00:02.0/rom cat /sys/devices/pci:00/:00:02.0/rom /tmp/vbios echo 0 /sys/devices/pci:00/:00:02.0/rom Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550981: Undelivered Mail Returned to Sender
On Wed, Oct 14, 2009 at 20:15:42 +0200, Mail Delivery System wrote: dbrazz...@snet.net: host snetmx3.prodigy.net[207.115.20.24] said: 553 5.3.0 flpd124 - n9EIFfZx003955, DNSBL:ATTRBL 521 91.121.16.100 _is_blocked.__For_information_see_http://att.net/blocks (in reply to MAIL FROM command) sigh... -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550981: DRM output from dmesg for i915:modeset=1
Your ISP rejects my mail, so trying again... On Wed, Oct 14, 2009 at 20:17:41 +0200, Julien Cristau wrote: On Wed, Oct 14, 2009 at 13:32:26 -0400, Dominique Brazziel wrote: The previous information was from a successful (X starts w/1152x864) run. Below is the relevant DRM info from the unsuccessful (1024x768) run, with complete dmesg and X log info attached: Thanks for this. Could you test with 2.6.31 from experimental, and if that still has the bogus LVDS output, forward this on to intel at bugs.freedesktop.org? There's some guidelines at http://intellinuxgraphics.org/how_to_report_bug.html I guess the output of 'grep -r . /sys/class/dmi/' and video bios could be helpful to them as well. You can get the bios with: echo 1 /sys/devices/pci:00/:00:02.0/rom cat /sys/devices/pci:00/:00:02.0/rom /tmp/vbios echo 0 /sys/devices/pci:00/:00:02.0/rom Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552237: 2.6.30/2.6.31: iwlagn page allocation failure. order:4, mode:0xd0
Package: linux-image-2.6.30-2-amd64 Version: 2.6.30-8 Severity: normal Hi, wireless connection suddenly disconnected, dmesg shows: [432878.569664] wlan0: disassociating by local choice (reason=3) [432878.573647] wlan0: direct probe to AP 00:24:97:89:f5:70 try 1 [432878.928058] wlan0: deauthenticating by local choice (reason=3) [432888.127757] NetworkManager: page allocation failure. order:4, mode:0xd0 [432888.127770] Pid: 2299, comm: NetworkManager Not tainted 2.6.30-2-amd64 #1 [432888.127776] Call Trace: [432888.127795] [80297eb9] ? __alloc_pages_internal+0x404/0x427 [432888.127805] [802bb124] ? kmem_getpages+0x68/0x12b [432888.127813] [802bb33a] ? fallback_alloc+0x153/0x1cd [432888.127821] [802bb4c4] ? cache_alloc_node+0x110/0x12f [432888.127829] [802bc01d] ? kmem_cache_alloc+0xf9/0x16a [432888.127862] [a0288d16] ? iwl_tx_queue_init+0x8d/0x276 [iwlcore] [432888.127888] [a0289089] ? iwl_txq_ctx_reset+0x18a/0x20d [iwlcore] [432888.127915] [a0284631] ? iwl_hw_nic_init+0x11d/0x13c [iwlcore] [432888.127936] [a029fd2e] ? __iwl_up+0x2df/0x2ee [iwlagn] [432888.127953] [a02a031a] ? iwl_mac_start+0x5dd/0x756 [iwlagn] [432888.127964] [8047da14] ? addrconf_notify+0x6f5/0x769 [432888.127973] [80482063] ? fib6_walk+0x5f/0x65 [432888.127982] [804820ea] ? fib6_clean_all+0x81/0xa3 [432888.127990] [80481adf] ? fib6_age+0x0/0x68 [432888.127998] [80482912] ? fib6_clean_node+0x0/0x96 [432888.128057] [a022e2eb] ? ieee80211_open+0x2cc/0x759 [mac80211] [432888.128069] [8020e5fa] ? __switch_to+0xff/0x263 [432888.128079] [80359ec4] ? __nla_reserve+0x1e/0x46 [432888.128088] [80413035] ? dev_open+0x75/0xb7 [432888.128096] [80412b06] ? dev_change_flags+0xaf/0x16d [432888.128106] [8041a40a] ? do_setlink+0x2a2/0x36f [432888.128114] [8041a669] ? rtnl_setlink+0x113/0x117 [432888.128124] [8041b33d] ? rtnetlink_rcv_msg+0x0/0x1f5 [432888.128132] [8041b33d] ? rtnetlink_rcv_msg+0x0/0x1f5 [432888.128141] [8042b7db] ? netlink_rcv_skb+0x34/0x7d [432888.128149] [8041b337] ? rtnetlink_rcv+0x1f/0x25 [432888.128156] [8042b358] ? netlink_unicast+0xe2/0x148 [432888.128165] [80235608] ? __wake_up+0x30/0x44 [432888.128173] [8042b623] ? netlink_sendmsg+0x265/0x278 [432888.128180] [802355b5] ? __wake_up_sync_key+0x3a/0x56 [432888.128191] [80403f24] ? sock_sendmsg+0xa3/0xbb [432888.128200] [80254742] ? autoremove_wake_function+0x0/0x2e [432888.128209] [804038ce] ? sock_aio_read+0xb9/0xc4 [432888.128218] [8040c628] ? verify_iovec+0x46/0x82 [432888.128226] [80404153] ? sys_sendmsg+0x217/0x28a [432888.128236] [804065c6] ? lock_sock_nested+0x9b/0xa6 [432888.128244] [804038f3] ? sockfd_lookup_light+0x1a/0x51 [432888.128254] [802ce79c] ? d_kill+0x4c/0x55 [432888.128264] [8020fa42] ? system_call_fastpath+0x16/0x1b [432888.128269] Mem-Info: [432888.128274] Node 0 DMA per-cpu: [432888.128281] CPU0: hi:0, btch: 1 usd: 0 [432888.128286] CPU1: hi:0, btch: 1 usd: 0 [432888.128291] Node 0 DMA32 per-cpu: [432888.128297] CPU0: hi: 186, btch: 31 usd: 0 [432888.128303] CPU1: hi: 186, btch: 31 usd: 6 [432888.128314] Active_anon:184809 active_file:40735 inactive_anon:62659 [432888.128317] inactive_file:401417 unevictable:7 dirty:69192 writeback:12 unstable:0 [432888.128321] free:5294 slab:53425 mapped:14736 pagetables:4998 bounce:0 [432888.128327] Node 0 DMA free:10456kB min:20kB low:24kB high:28kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB present:9328kB pages_scanned:0 all_unreclaimable? no [432888.128342] lowmem_reserve[]: 0 2967 2967 2967 [432888.128352] Node 0 DMA32 free:10720kB min:6956kB low:8692kB high:10432kB active_anon:739236kB inactive_anon:250636kB active_file:162940kB inactive_file:1605668kB unevictable:28kB present:3038380kB pages_scanned:0 all_unreclaimable? no [432888.128368] lowmem_reserve[]: 0 0 0 0 [432888.128377] Node 0 DMA: 4*4kB 3*8kB 1*16kB 3*32kB 3*64kB 3*128kB 2*256kB 0*512kB 1*1024kB 0*2048kB 2*4096kB = 10456kB [432888.128402] Node 0 DMA32: 1850*4kB 56*8kB 2*16kB 1*32kB 0*64kB 0*128kB 1*256kB 1*512kB 0*1024kB 1*2048kB 0*4096kB = 10728kB [432888.128426] 499312 total pagecache pages [432888.128430] 0 pages in swap cache [432888.128435] Swap cache stats: add 0, delete 0, find 0/0 [432888.128439] Free swap = 0kB [432888.128443] Total swap = 0kB [432888.162238] 774221 pages RAM [432888.162245] 12328 pages reserved [432888.162249] 339839 pages shared [432888.162252] 480634 pages non-shared [432888.162262] iwlagn :0c:00.0: kmalloc for auxiliary BD structures failed [432888.162307] iwlagn :0c:00.0: Tx 12 queue init failed [432888.163080] iwlagn :0c:00.0: Unable to init nic rmmod/modprobe doesn't seem
Re: Bug#550977: Re: Bug#550977: libgl1-mesa-dri: direct rendering crashes the whole system on Thinkpad T40 with Radeon Mobility 7500
reassign 550977 linux-2.6 2.6.30-8 retitle 550977 filesystem corruption (drm related?) on thinkpad t40 kthxbye On Sat, Nov 7, 2009 at 22:25:46 +0100, ender wrote: Did this filesystem corruption happen only once, or more than that? It did happen every time I tried, with one exception. Is just X crashing, or is the system completely unresponsive (including over the network)? If the former, do you have corresponding X and kernel logs? It's not like a freeze of X. For example I'm able to switch to a serial terminal but I can't login. The response is: /bin/login: error while loading shared libraris: /lib/libpam_misc.so.0: invalid ELF header Ext3-fs error (device hda6): ext3_lookup: deletet inode referenced: On the other hand some tools like pwd might still work. However the system is unusable after a crash because it's impossible to start basic programs or even login and I guess it won't work over the network either. I didn't try that but samba didn't work anymore. Anyway I'm going to add kernel and Xorg logs. Maybe you'll find something interesting in there. One Crash happened Nov 7. approx 13:00 that one is in the kern.log filesystem corruption is likely to be a kernel bug, so reassigning this bug over there. As another data point, does this also happen after a fresh boot, or only after a suspend/resume cycle? Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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
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
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
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
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#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
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
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
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
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
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
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
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#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#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#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
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#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
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#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: 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#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#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
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#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
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
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#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#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#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
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
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
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: 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 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
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
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
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
