Bug#652955: [linux-headers-3.1.0-1-common] Naming inconsistancy? can cause dkms/m-a problems
Package: linux-headers-3.1.0-1-common Version: 3.1.5-1 Severity: normal --- Please enter the report below this line. --- I am not sure this package has the bug but here goes: If I have the same kernel version installed for both i686 and amd64, for example. The debian nvidia kernel modules will dkms successfully on both while the debian virtualbox kernel modules will dkms only for one of them. I would assume this applies to m-a as well since going to /usr/src and doing make (OK) and sudo make install (FAILS do to architecture inconstancy). If there be differing linux-headers-common for differing architectures, they would need unique packaging just as the headers themselves. Maybe this is not the problem and someone more knowledgable could accomplish as simple work-around, i.e. with some EXPORT= Worth a look. --- System information. --- Architecture: i386 Kernel: Linux 3.1.0-1-686-pae Debian Release: wheezy/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 1 experimentalftp.us.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- 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/201112221008.20303.d_ba...@012.net.il
Bug#652955: [linux-headers-3.1.0-1-common] Naming inconsistancy? can cause dkms/m-a problems
tags 652955 + moreinfo quit Hi David, David Baron wrote: If I have the same kernel version installed for both i686 and amd64, for example. The debian nvidia kernel modules will dkms successfully on both while the debian virtualbox kernel modules will dkms only for one of them. Please supply details, including the error message. Thanks for writing, Jonathan -- 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/20111222081712.GA2908@elie.Belkin
Processed: Re: [linux-headers-3.1.0-1-common] Naming inconsistancy? can cause dkms/m-a problems
Processing commands for cont...@bugs.debian.org: tags 652955 + moreinfo Bug #652955 [linux-headers-3.1.0-1-common] [linux-headers-3.1.0-1-common] Naming inconsistancy? can cause dkms/m-a problems Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 652955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132454184531486.transcr...@bugs.debian.org
Bug#652955: [linux-headers-3.1.0-1-common] Naming inconsistancy? can cause dkms/m-a problems
On Thursday 26 Kislev 5772 10:17:12 Jonathan Nieder wrote: tags 652955 + moreinfo quit Hi David, David Baron wrote: If I have the same kernel version installed for both i686 and amd64, for example. The debian nvidia kernel modules will dkms successfully on both while the debian virtualbox kernel modules will dkms only for one of them. Please supply details, including the error message. I had removed the headers for the kernel Reinstalling them (running the 32-bit kernel): ...Selecting previously unselected package linux-headers-3.1.0-1-amd64. (Reading database ... 522370 files and directories currently installed.) Unpacking linux-headers-3.1.0-1-amd64 (from .../linux-headers-3.1.0-1- amd64_3.1.5-1_i386.deb) ... Setting up linux-headers-3.1.0-1-amd64 (3.1.5-1) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.1.0-1-amd64 Good news! Module version 4.1.6_Debian for vboxdrv.ko exactly matches what is already found in kernel 3.1.0-1-amd64. DKMS will not replace this module. You may override by specifying --force. Good news! Module version 4.1.6_Debian for vboxnetadp.ko exactly matches what is already found in kernel 3.1.0-1-amd64. DKMS will not replace this module. You may override by specifying --force. Good news! Module version 4.1.6_Debian for vboxnetflt.ko exactly matches what is already found in kernel 3.1.0-1-amd64. DKMS will not replace this module. You may override by specifying --force. Error! Module version 4.1.6_Debian for vboxpci.ko is not newer than what is already found in kernel 3.1.0-1-amd64 (4.1.6_Debian). You may override by specifying --force. Yesterday when I was in that kernel, it did not load these modules so they may be built for the wrong architecture. Next time I boot up the 64 bit kernel, I will try again. (That pci module fails in all the kernels. I generally only need the vboxdrv module.) -- 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/201112221038.21095.d_ba...@012.net.il
Bug#627372: Console turns black during boot.
Hi Alan, Alan Zimmerman wrote: I revisited this problem tonight, and it seems related to the xserver-xorg-video-intel package. In desperation, I uninstalled it. # uname -a Linux alanz-laptop 3.1.0-1-686-pae #1 SMP Mon Nov 14 08:24:20 UTC 2011 i686 GNU/Linux It now boots without problems. [...] Extract from /var/log/Xorg.0.log --- [39.149] (II) LoadModule: intel [39.251] (WW) Warning, couldn't open module intel When the console turns black, is the machine still usable? (For example, can you use ctrl-alt-delete to reboot?) Please also check whether booting in recovery mode with xserver-xorg-video-intel installed works. If it does, please get dmesg output and output from /usr/share/bug/xserver-xorg-video-intel/script 31 after booting and reproducing the problem. It should be possible to get this information by either driving blind or ssh-ing in from another machine. Thanks and hope that helps, Jonathan -- 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/20111222101617.GB6548@elie.Belkin
Bug#652869: Laptop auto power-on after correct shutdown and being powered-off
severity 652869 important
quit
Hey,
Antonio-M. Corbi Bellot wrote:
After upgrading to linux-image-3.1.0-amd64 (3.1.5-1) the laptop I use
works as expected but after shutting it down and being correctly
powered-off it automatically powers-on after 5 or 6 minutes (this is
always the same time).
Booting this laptop with linux-image-3.0.0-2-amd64 (3.0.0-6) I can't
reproduce this problem, even with previous linux-image-3.1.0-amd64
(prior to 3.1.5-1) I did not have this problem.
Fun.
Please send full dmesg output from immediately after bootup.
Could you try this patch[1]?
[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
-- 8 --
Subject: Revert rtc: Disable the alarm in the hardware
This reverts commit 0cbc008c56f7b4a11ba6fe80e196d7ab322baabf.
---
Thanks and hope that helps,
Jonathan
drivers/rtc/interface.c | 44 ++--
1 files changed, 10 insertions(+), 34 deletions(-)
diff --git a/drivers/rtc/interface.c b/drivers/rtc/interface.c
index 3d9d2b976560..44e91e598f8d 100644
--- a/drivers/rtc/interface.c
+++ b/drivers/rtc/interface.c
@@ -318,20 +318,6 @@ int rtc_read_alarm(struct rtc_device *rtc, struct
rtc_wkalrm *alarm)
}
EXPORT_SYMBOL_GPL(rtc_read_alarm);
-static int ___rtc_set_alarm(struct rtc_device *rtc, struct rtc_wkalrm *alarm)
-{
- int err;
-
- if (!rtc-ops)
- err = -ENODEV;
- else if (!rtc-ops-set_alarm)
- err = -EINVAL;
- else
- err = rtc-ops-set_alarm(rtc-dev.parent, alarm);
-
- return err;
-}
-
static int __rtc_set_alarm(struct rtc_device *rtc, struct rtc_wkalrm *alarm)
{
struct rtc_time tm;
@@ -355,7 +341,14 @@ static int __rtc_set_alarm(struct rtc_device *rtc, struct
rtc_wkalrm *alarm)
* over right here, before we set the alarm.
*/
- return ___rtc_set_alarm(rtc, alarm);
+ if (!rtc-ops)
+ err = -ENODEV;
+ else if (!rtc-ops-set_alarm)
+ err = -EINVAL;
+ else
+ err = rtc-ops-set_alarm(rtc-dev.parent, alarm);
+
+ return err;
}
int rtc_set_alarm(struct rtc_device *rtc, struct rtc_wkalrm *alarm)
@@ -769,20 +762,6 @@ static int rtc_timer_enqueue(struct rtc_device *rtc,
struct rtc_timer *timer)
return 0;
}
-static void rtc_alarm_disable(struct rtc_device *rtc)
-{
- struct rtc_wkalrm alarm;
- struct rtc_time tm;
-
- __rtc_read_time(rtc, tm);
-
- alarm.time = rtc_ktime_to_tm(ktime_add(rtc_tm_to_ktime(tm),
-ktime_set(300, 0)));
- alarm.enabled = 0;
-
- ___rtc_set_alarm(rtc, alarm);
-}
-
/**
* rtc_timer_remove - Removes a rtc_timer from the rtc_device timerqueue
* @rtc rtc device
@@ -804,10 +783,8 @@ static void rtc_timer_remove(struct rtc_device *rtc,
struct rtc_timer *timer)
struct rtc_wkalrm alarm;
int err;
next = timerqueue_getnext(rtc-timerqueue);
- if (!next) {
- rtc_alarm_disable(rtc);
+ if (!next)
return;
- }
alarm.time = rtc_ktime_to_tm(next-expires);
alarm.enabled = 1;
err = __rtc_set_alarm(rtc, alarm);
@@ -869,8 +846,7 @@ again:
err = __rtc_set_alarm(rtc, alarm);
if (err == -ETIME)
goto again;
- } else
- rtc_alarm_disable(rtc);
+ }
mutex_unlock(rtc-ops_lock);
}
--
1.7.8
--
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/20111222102812.GC6548@elie.Belkin
Processed: Re: Laptop auto power-on after correct shutdown and being powered-off
Processing commands for cont...@bugs.debian.org: severity 652869 important Bug #652869 [linux-2.6] linux-image-3.1.0-1-amd64: Laptop auto power-on after correct shutdown and being powered-off Severity set to 'important' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 652869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13245497094501.transcr...@bugs.debian.org
Bug#645547: New processes segfault after several resume from hibernation
retitle 645547 [i915] intermittent memory corruption after hibernation unless i915.modeset=0 severity 645547 important found 645547 linux-2.6/3.2~rc4-1~experimental.1 quit Hi, Kjö Hansi Glaz wrote: I tried appending `i915.modeset=0` and thus falling back to vesa makes hibremation/resume working. I also tested 3.2.0-rc4 from experimetal (with modesetting enabled) and experience the same kind of problems that with 3.1.0. Sometimes processes segfault, sometimes the whole kernel hangs. Thanks. Nice detective work. That means it's most likely a bug in the i915 driver. Please follow the instructions at [1] to report this upstream and let us know the bug number so we can track it. Regards, Jonathan [1] http://intellinuxgraphics.org/how_to_report_bug.html -- 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/20111222103635.GD6548@elie.Belkin
Processed: Re: New processes segfault after several resume from hibernation
Processing commands for cont...@bugs.debian.org: retitle 645547 [i915] intermittent memory corruption after hibernation unless i915.modeset=0 Bug #645547 [linux-2.6] linux-image-3.0.0-1-amd64: New processes segfault after several resume from hibernation Changed Bug title to '[i915] intermittent memory corruption after hibernation unless i915.modeset=0' from 'linux-image-3.0.0-1-amd64: New processes segfault after several resume from hibernation' severity 645547 important Bug #645547 [linux-2.6] [i915] intermittent memory corruption after hibernation unless i915.modeset=0 Severity set to 'important' from 'normal' found 645547 linux-2.6/3.2~rc4-1~experimental.1 Bug #645547 [linux-2.6] [i915] intermittent memory corruption after hibernation unless i915.modeset=0 Bug Marked as found in versions linux-2.6/3.2~rc4-1~experimental.1. quit Stopping processing here. Please contact me if you need assistance. -- 645547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13245502127224.transcr...@bugs.debian.org
Bug#652119: Bad pagetable 000f
Hey Matthew, Matthew Wakeling wrote: Running the par2 program causes a bad pagetable fault which has killed the process and killed the machine on two different occasions. The machine is completely stable running other programs. The problem occurs when running par2 to generate 13.5GB of recovery data for 50GB of data in eleven equal size files, a task that should take about 10 hours on my system. The task seems to cause a crash after about two hours. Can you reproduce this on demand? If so, some questions: - was this a regression? (I.e., do you know of any older kernel versions without this bug?) - can you reproduce it with a recent kernel from sid or experimental? (The only packages from outside squeeze you should need in order to test this aside from the kernel image itself are linux-base and initramfs-tools.) If this is reproducible with newish kernels, we can get help from upstream. If it isn't, we can try to find what change fixed it and try applying the same fix to squeeze. Thanks and hope that helps, Jonathan -- 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/20111222105412.GB7180@elie.Belkin
Processed: Re: kernel panic - linux-image-3.1.0-1-486
Processing commands for cont...@bugs.debian.org: reassign 652056 src:linux-2.6 3.1.5-1 Bug #652056 [linux-2.6] kernel panic - linux-image-3.1.0-1-486 Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug #652056 [src:linux-2.6] kernel panic - linux-image-3.1.0-1-486 Bug Marked as found in versions linux-2.6/3.1.5-1. found 652056 linux-2.6/3.1.4-1 Bug #652056 [src:linux-2.6] kernel panic - linux-image-3.1.0-1-486 Bug Marked as found in versions linux-2.6/3.1.4-1. End of message, stopping processing here. Please contact me if you need assistance. -- 652056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132455167114475.transcr...@bugs.debian.org
Re: Request to upload linux-2.6 (various suites)
On Thu, Dec 22, 2011 at 01:17:16AM +, Ben Hutchings wrote:
I think the following versions should be uploaded soon:
stable-proposed-updates: 2.6.32-40
Upstream stable updates 2.6.32.{47,48,49,50,51}, a few other fixes, and
backport of isci driver.
unstable: 3.1.6-1
Upstream stable update and a few other fixes. 3.1.5-1 should go into
testing first.
experimental: 3.2~rc6-1~experimental.1
New upstream release candidate, and various config changes.
I will spend much of the rest of the year offline, so I do *not*
currently plan to make these uploads myself. Any volunteers?
I can do them the upcoming week, maybe some before.
--
maks
--
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/20111222105308.gf12...@vostochny.stro.at
Bug#582487: FYI: A workaround
tags 582487 - moreinfo merge 582088 582487 quit Hi Kingsley, Kingsley G. Morse Jr. wrote: For what it's worth, I seem to have found a way to work around this bug. Having the same error message does not imply having the same bug. The bug you're responding to looks like another episode in the bug#582088 saga. Merging them. Kind regards, Jonathan -- 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/20111222110853.GE7180@elie.Belkin
Bug#580026: [drm/i915] invalid opcode: 0000 [#1] SMP in i915_gem_execbuffer
merge 582088 580026 593793 quit Thiemo Nagel wrote (regarding an oops in i915_gem_execbuffer): Let's see whether I hit the problem again. I assume the odds are low, though, as I've only seen it once in 2.6.32-4. Ok, smells like another randomish symptom of memory corruption. I assume this is the same machine as bug#582088, so merging. -- 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/20111222112532.GA7629@elie.Belkin
Processed: Re: [drm/i915] invalid opcode: 0000 [#1] SMP in i915_gem_execbuffer
Processing commands for cont...@bugs.debian.org: merge 582088 580026 593793 Bug#580026: [drm/i915] invalid opcode: [#1] SMP in i915_gem_execbuffer Bug#582088: [Eee PC 1000HG, fuse] symptoms of memory corruption Bug#593793: BUG: unable to handle kernel NULL pointer dereference at 0041 (__d_lookup+0xb5/0xd3) Bug#582487: linux-image-2.6.32-5-686: bad page state Bug#585731: linux-image-2.6.32-5-686: unable to handle kernel paging request at ff3a3b3a EIP: rb_insert_color+0x57/0xb5 Bug#593792: [Eee PC 1000HG, fuse] symptoms of memory corruption Merged 580026 582088 582487 585731 593792 593793. quit Stopping processing here. Please contact me if you need assistance. -- 593793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593793 582487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582487 585731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585731 593792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593792 580026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580026 582088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132455315321030.transcr...@bugs.debian.org
Bug#590582: vortex driver hangs
tags 590582 + moreinfo quit Hi, Jonathan Nieder wrote: Karol Szkudlarek wrote: eth0: Resetting the Tx ring pointer. [ cut here ] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x8f/0xdc() [...] after copying large file (about 1GB) copying stops, networking stops completly and only reset helped Hm. Ok, please try a 3.x.y kernel from sid or experimental; the only packages aside from the kernel image itself from outside squeeze that should be needed for this are linux-base and initramfs-tools. Did you get a chance to try that? If not, any hints for others trying to reproduce this and pursue a fix? Thanks, Jonathan -- 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/20111222113147.GA7738@elie.Belkin
Processed: Re: vortex driver hangs
Processing commands for cont...@bugs.debian.org: tags 590582 + moreinfo Bug #590582 [linux-2.6] linux-image-2.6.26-2-686: 3c59x: NETDEV WATCHDOG: transmit timed out Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 590582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132455352722853.transcr...@bugs.debian.org
Re: Request to upload linux-2.6 (various suites)
On Thu, Dec 22, 2011 at 01:17:16AM +, Ben Hutchings wrote: I will spend much of the rest of the year offline, so I do *not* currently plan to make these uploads myself. Any volunteers? Consider it done. Bastian -- There is a multi-legged creature crawling on your shoulder. -- Spock, A Taste of Armageddon, stardate 3193.9 -- 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/20111222113432.gd2...@wavehammer.waldi.eu.org
Bug#593183: broken rt2860 support after upgrade to 2.6.32-18 from -16
tags 593183 + moreinfo quit Hi, Jonathan Nieder wrote: Raphael Geissert wrote: I just tried with a visible AP (using the same crypto settings) and it works. So, the changes to the module appear to only break support for hidden APs. [...] 1. Just to check, can you still reproduce the trouble with the latest squeeze kernel? Ping. Just a reminder that we are still curious about this. :) Thanks again for your help (and all the other work you do in Debian). Jonathan -- 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/20111222114352.GA7924@elie.Belkin
Processed: Re: broken rt2860 support after upgrade to 2.6.32-18 from -16
Processing commands for cont...@bugs.debian.org: tags 593183 + moreinfo Bug #593183 [linux-2.6] broken rt2860 support after upgrade to 2.6.32-18 from -16 Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 593183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132455424725641.transcr...@bugs.debian.org
Re: Request to upload linux-2.6 (various suites)
On Thu, Dec 22, 2011 at 01:17:16AM +, Ben Hutchings wrote: unstable: 3.1.6-1 Upstream stable update and a few other fixes. 3.1.5-1 should go into testing first. 3.1.5-1 is in testing. Bastian -- Without followers, evil cannot spread. -- Spock, And The Children Shall Lead, stardate 5029.5 -- 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/20111222115105.ga3...@wavehammer.waldi.eu.org
Processed: reassign 652955 to virtualbox-dkms
Processing commands for cont...@bugs.debian.org: reassign 652955 virtualbox-dkms Bug #652955 [linux-headers-3.1.0-1-common] [linux-headers-3.1.0-1-common] Naming inconsistancy? can cause dkms/m-a problems Bug reassigned from package 'linux-headers-3.1.0-1-common' to 'virtualbox-dkms'. Bug No longer marked as found in versions linux-2.6/3.1.5-1. thanks Stopping processing here. Please contact me if you need assistance. -- 652955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132455485128091.transcr...@bugs.debian.org
Bug#644174:
Scenario 0: Nothing plugged to no USB 2.0/3.0 port: - can boot 2.6.32-5-amd64 - can boot 2.6.39-bpo.2-amd64 - can boot 3.1.0-1-amd64 Scenario 1: Mouse plugged to USB 2.0 port: - can not boot 2.6.32-5-amd64 - can boot 2.6.39-bpo.2-amd64 - can boot 3.1.0-1-amd64 Scenario 2: Mouse plugged to USB 3.0 port: - can not boot 2.6.32-5-amd64 - can not boot 2.6.39-bpo.2-amd64 - can not boot 3.1.0-1-amd64 -- Mathieu -- 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/ca+7wusx1y9njxoatrcx0ojhuwfplu79f1f79o_ptw+msuyk...@mail.gmail.com
Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI
On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder jrnie...@gmail.com wrote: - Please test a v3.2 release candidate from experimental. The only packages from outside squeeze that should be needed for this, aside from the kernel image itself, are linux-base and initramfs-tools. - If it reproduces the problem, please blacklist the xhci_hcd module by writing blacklist xhci_hcd to a file /etc/modprobe.d/mm-blacklist-xhci.conf, run update-initramfs -u -k all and reboot to try again without USB 3.0 support. If we're very lucky, this will work around the problem. In that case, please write a summary of the problem to upstream (linux-...@vger.kernel.org, cc-ing Sarah Sharp sarah.a.sh...@linux.intel.com and either me or this bug log so we can track the resulting discussion). Be sure to include: - steps to reproduce the problem - symptoms, and how they differ from what you expected - ways to avoid triggering the problem (maybe some USB ports trigger it and others don't? etc) - full dmesg output from booting, and a photo of the screen after reproducing the problem (ideally by running modprobe xhci_hcd in the very same run of Linux), as attachments - which kernel versions you've tested, and what happened with each - a link to this bug log for the full story - any other weird symptoms or observations System: Dell System Vostro 3750 / Portable Computer Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental. No mouse plugged to USB 2.0/3.0 interface: boot is fine Mouse plugged to USB 2.0 interface: boot is fine Mouse plugged to USB 3.0 interface: boot simply stops As suggested by Jonathan N. [1] here is what I did next: $ cat /etc/modprobe.d/mm-blacklist-xhci.conf blacklist xhci_hcd $ update-initramfs -u -k all $ sudo reboot 3.2.0-rc4-amd64 refuse to boot as soon as I plug my mouse to USB 3.0 port (screenshot at [2]). USB 2.0 and no mouse still boot fine. I am attaching dmesg from a kernel boot, when mouse is attached to USB 2.0 port (see [3]). I think I'll revert to 2.6.39-bpo.2-amd64 because kernel does not seems to like my video card. When I suspend/resume, screen is displayed on screen Ctrl+Shift+F8, while pointer stays on Ctrl+Shift+F7. I can type fine from Ctrl+Shift+F7, since I can see results on Ctrl+Shift+F8. I'll try to compile the nvidia kernel and see if suspend/resume works. Refs: [1] http://bugs.debian.org/644174 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#64 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#69 Thanks, -- Mathieu -- 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/CA+7wUsxRg52yC+wu7uO-YChPEbQ3vaYWG6F7ee=ipx8yx7o...@mail.gmail.com
Bug#644174:
Adding lspci + lshw output from 3.2.0-rc4-amd64, mouse on USB 2.0. maester description: Computer width: 64 bits capabilities: vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 5902MiB *-cpu product: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 800MHz capacity: 800MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm ida arat epb xsaveopt pln pts tpr_shadow vnmi flexpriority ept vpid cpufreq *-pci description: Host bridge product: Sandy Bridge DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 09 width: 32 bits clock: 33MHz configuration: driver=agpgart-intel resources: irq:0 *-pci:0 description: PCI bridge product: Sandy Bridge PCI Express Root Port vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 09 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:40 ioport:4000(size=4096) memory:f000-f10f ioport:c000(size=301989888) *-display UNCLAIMED description: VGA compatible controller product: nVidia Corporation vendor: nVidia Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list configuration: latency=0 resources: memory:f000-f0ff memory:c000-cfff memory:d000-d1ff ioport:4000(size=128) memory:f100-f107 *-display description: VGA compatible controller product: Sandy Bridge Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:43 memory:f140-f17f memory:e000-efff ioport:5000(size=64) *-communication UNCLAIMED description: Communication controller product: Cougar Point HECI Controller #1 vendor: Intel Corporation physical id: 16 bus info: pci@:00:16.0 version: 04 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: latency=0 resources: memory:f2b05000-f2b0500f *-usb:0 description: USB Controller product: Cougar Point USB Enhanced Host Controller #2 vendor: Intel Corporation physical id: 1a bus info: pci@:00:1a.0 version: 05 width: 32 bits clock: 33MHz capabilities: ehci bus_master cap_list configuration: driver=ehci_hcd latency=0 resources: irq:16 memory:f2b0a000-f2b0a3ff *-multimedia description: Audio device product: Cougar Point High Definition Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@:00:1b.0 version: 05 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:45 memory:f2b0-f2b03fff *-pci:1 description: PCI bridge product: Cougar Point PCI Express Root Port 1 vendor: Intel Corporation physical id: 1c bus info: pci@:00:1c.0 version: b5 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 memory:f2a0-f2af *-network description: Wireless interface product: Intel Corporation
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #646376 (http://bugs.debian.org/646376) # Bug title: xserver-xorg-video-ati: Massive screen corruption in few hours after login # * https://bugs.freedesktop.org/show_bug.cgi?id=40221 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 646376 + fixed-upstream Bug #646376 [linux-2.6] xserver-xorg-video-ati: Massive screen corruption in few hours after login Added tag(s) fixed-upstream. usertags 646376 - status-NEW Bug#646376: xserver-xorg-video-ati: Massive screen corruption in few hours after login Usertags were: status-NEW. Usertags are now: . usertags 646376 + status-RESOLVED resolution-FIXED Bug#646376: xserver-xorg-video-ati: Massive screen corruption in few hours after login There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 646376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132457199715265.transcr...@bugs.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #646376 (http://bugs.debian.org/646376) # Bug title: xserver-xorg-video-ati: Massive screen corruption in few hours after login # * https://bugs.freedesktop.org/show_bug.cgi?id=40221 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 646376 + fixed-upstream usertags 646376 - status-NEW usertags 646376 + status-RESOLVED resolution-FIXED thanks -- 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/20111222163956.3795.3912.btsl...@busoni.debian.org
Bug#652119: Bad pagetable 000f
On Thu, 22 Dec 2011, Jonathan Nieder wrote: Can you reproduce this on demand? Yes. It seems to take about two hours to fail. Thinking about it, par2 was accessing about 1400 independent areas of memory on a loop, so it would be causing cache thrash and TLB thrash. I'm thinking it might almost be worth having a look at the par2 program to see if it could improve its memory access pattern. But as it stands, it is probably a pretty good TLB management stress test. - was this a regression? (I.e., do you know of any older kernel versions without this bug?) I have seen this happen before on an older kernel. Not sure exactly which one - maybe 2.6.26? - can you reproduce it with a recent kernel from sid or experimental? (The only packages from outside squeeze you should need in order to test this aside from the kernel image itself are linux-base and initramfs-tools.) I'll have to physically attend the machine to do this, which won't happen until January. Even then, testing will involve crashing my machine a few times, so it won't be the first thing I do. If this is reproducible with newish kernels, we can get help from upstream. If it isn't, we can try to find what change fixed it and try applying the same fix to squeeze. Sure. How out of date is the squeeze kernel anyway? Matthew -- People who love sausages, respect the law, and work with IT standards shouldn't watch any of them being made. -- Peter Gutmann -- 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/alpine.DEB.2.00.1112221745200.15317@localhost
Bug#652119: Bad pagetable 000f
Matthew Wakeling wrote: On Thu, 22 Dec 2011, Jonathan Nieder wrote: - was this a regression? (I.e., do you know of any older kernel versions without this bug?) I have seen this happen before on an older kernel. Not sure exactly which one - maybe 2.6.26? Thanks. [...] If this is reproducible with newish kernels, we can get help from upstream. If it isn't, we can try to find what change fixed it and try applying the same fix to squeeze. Sure. How out of date is the squeeze kernel anyway? The 2.6.32.y series stabilized for about a year and a couple of months before squeeze was released. (v2.6.33 was released on 24 February 2010.) Since then, the 2.6.32.y kernel has received lots of fixes, so in that sense it is up to date. Upstream developers prefer to debug something closer to the codebase they are working on day-to-day. [...] I'll have to physically attend the machine to do this, which won't happen until January. Even then, testing will involve crashing my machine a few times, so it won't be the first thing I do. No problem; we can wait. Other tests that would be useful might include (1) running memtest86+ and (2) trying the same workload using a livecd with some other kernel, like the kernel of FreeBSD, to see if this is likely to be a hardware bug or a kernel bug. Jonathan -- 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/20111222192219.GA8650@elie.Belkin
Bug#627372: Console turns black during boot.
Alan Zimmerman wrote: I reinstalled the video-intel package. When the console turns black, the machine is still usable. Booting in recovery mode makes no difference. I see. Removing the intel driver means removing the file in /etc/modprobe.d that enables kernel mode setting (see NEWS.Debian.gz), which works around the bug. Attached are the dmesg logs, and the bug script output, after booting normally with the driver installed. Here's the relevant snippet: fbcon: inteldrmfb (fb0) is primary device [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state render error detected, EIR: 0x0010 IPEIR: 0x IPEHR: 0x INSTDONE: 0xfffe INSTPS: 0x INSTDONE1: 0x ACTHD: 0x page table error PGTBL_ER: 0x0001 [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking Please also provide the content of the /debug/dri/0/i915_error_state file. Then we can take this upstream, following instructions from [1]. Thanks for a clear report, Jonathan [1] http://intellinuxgraphics.org/how_to_report_bug.html -- 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/20111222193647.GB8650@elie.Belkin
Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI
Hi, Mathieu Malaterre wrote: Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental. No mouse plugged to USB 2.0/3.0 interface: boot is fine Mouse plugged to USB 2.0 interface: boot is fine Mouse plugged to USB 3.0 interface: boot simply stops As suggested by Jonathan N. [1] here is what I did next: $ cat /etc/modprobe.d/mm-blacklist-xhci.conf blacklist xhci_hcd $ update-initramfs -u -k all $ sudo reboot 3.2.0-rc4-amd64 refuse to boot as soon as I plug my mouse to USB 3.0 port (screenshot at [2]). USB 2.0 and no mouse still boot fine. So do I understand correctly, that blacklisting the xhci driver does _not_ avoid trouble? Can you confirm that the blacklisting worked, by booting and checking that the xhci_hcd module is not loaded? If so, this presumably has nothing to do with the xhci driver, and is probably caused by something lower level. Happy holidays, Jonathan -- 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/20111222194705.GC8650@elie.Belkin
Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI
On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote: On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder jrnie...@gmail.com wrote: - Please test a v3.2 release candidate from experimental. The only packages from outside squeeze that should be needed for this, aside from the kernel image itself, are linux-base and initramfs-tools. - If it reproduces the problem, please blacklist the xhci_hcd module by writing blacklist xhci_hcd to a file /etc/modprobe.d/mm-blacklist-xhci.conf, run update-initramfs -u -k all and reboot to try again without USB 3.0 support. If we're very lucky, this will work around the problem. In that case, please write a summary of the problem to upstream (linux-...@vger.kernel.org, cc-ing Sarah Sharp sarah.a.sh...@linux.intel.com and either me or this bug log so we can track the resulting discussion). Be sure to include: - steps to reproduce the problem - symptoms, and how they differ from what you expected - ways to avoid triggering the problem (maybe some USB ports trigger it and others don't? etc) - full dmesg output from booting, and a photo of the screen after reproducing the problem (ideally by running modprobe xhci_hcd in the very same run of Linux), as attachments - which kernel versions you've tested, and what happened with each - a link to this bug log for the full story - any other weird symptoms or observations System: Dell System Vostro 3750 / Portable Computer Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental. No mouse plugged to USB 2.0/3.0 interface: boot is fine Mouse plugged to USB 2.0 interface: boot is fine Mouse plugged to USB 3.0 interface: boot simply stops Does the boot stop when you have a non-HID USB device plugged into the USB 3.0 port (e.g. hub or flash drive or USB speaker)? It could be an issue with a buggy BIOS trying to use the mouse and keyboard (HID devices) attached to the USB 3.0 host. Perhaps it changes the ACPI tables when it tries to use the USB 3.0 host controller, and accidentally overlaps the regions? But if your keyboard and mouse were under USB 2.0, maybe it will only map in the USB 2.0 host controller. As suggested by Jonathan N. [1] here is what I did next: $ cat /etc/modprobe.d/mm-blacklist-xhci.conf blacklist xhci_hcd $ update-initramfs -u -k all $ sudo reboot Were you blacklisting xhci only because of the xhci_hcd :03:00.0: WARN: Stalled endpoint messages? Because those messages are harmless, and don't mean anything is *wrong* with the host controller. Even if there's no xHCI driver loaded, it seems that ACPI is noticing the conflict between the PCI registers and another region. So unloading the xHCI driver won't help your system boot. You'd need to get a fix into the ACPI subsystem to work around the conflict. I don't think any xHCI driver modification can help here. 3.2.0-rc4-amd64 refuse to boot as soon as I plug my mouse to USB 3.0 port (screenshot at [2]). USB 2.0 and no mouse still boot fine. I am attaching dmesg from a kernel boot, when mouse is attached to USB 2.0 port (see [3]). I think I'll revert to 2.6.39-bpo.2-amd64 because kernel does not seems to like my video card. When I suspend/resume, screen is displayed on screen Ctrl+Shift+F8, while pointer stays on Ctrl+Shift+F7. I can type fine from Ctrl+Shift+F7, since I can see results on Ctrl+Shift+F8. I'll try to compile the nvidia kernel and see if suspend/resume works. Refs: [1] http://bugs.debian.org/644174 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#64 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174#69 Sarah Sharp -- 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/20111222195243.GB18208@xanatos
Bug#646376: xserver-xorg-video-ati: Massive screen corruption in few hours after login
found 646376 linux-2.6/3.0.0-3
tags 646376 + upstream patch moreinfo
quit
Michel Dänzer wrote:
Valentyn Pavliuchenko wrote:
I have ATI Cayman (Radeon HD 6790). When working with a PC for for an hour I
got corruption of different parts of screen (like windows captions, menus,
whole windows, window shadows, etc.). The corruption looks like using
uninitializaed memory instead of textures. After reboot everything is ok.
See the upstream bug report referenced above. Looks like it's finally
about to be fixed.
Thanks, Michel.
Valentyn, could you try this patch and see if helps? [1] has
instructions.
[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
From: Jerome Glisse jgli...@redhat.com
Date: Wed, 26 Oct 2011 11:41:22 -0400
Subject: drm/radeon: flush read cache for gtt with fence on r6xx and newer GPU
V3
commit 77b1bad423599c9841ea282a82172f039bb2ff92 upstream.
Cayman seems to be particularly sensitive to read cache returning
old data after bind/unbind to GTT. Flush read cache for GTT range
with each fences for all new hw. Should fix several rendering glitches.
Like
V2 flush whole address space
V3 also flush shader read cache
https://bugs.freedesktop.org/show_bug.cgi?id=40221
https://bugs.freedesktop.org/show_bug.cgi?id=38022
https://bugzilla.redhat.com/show_bug.cgi?id=738790
Signed-off-by: Jerome Glisse jgli...@redhat.com
Reviewed-by: Alex Deucher alexander.deuc...@amd.com
Signed-off-by: Dave Airlie airl...@redhat.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
drivers/gpu/drm/radeon/evergreen_blit_kms.c |4 ++--
drivers/gpu/drm/radeon/r600.c | 16
drivers/gpu/drm/radeon/r600_blit_kms.c |4 ++--
3 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/radeon/evergreen_blit_kms.c
b/drivers/gpu/drm/radeon/evergreen_blit_kms.c
index 2eb251858e72..80ef4401ee9e 100644
--- a/drivers/gpu/drm/radeon/evergreen_blit_kms.c
+++ b/drivers/gpu/drm/radeon/evergreen_blit_kms.c
@@ -779,9 +779,9 @@ int evergreen_blit_prepare_copy(struct radeon_device *rdev,
int size_bytes)
ring_size = num_loops * dwords_per_loop;
/* set default + shaders */
ring_size += 55; /* shaders + def state */
- ring_size += 10; /* fence emit for VB IB */
+ ring_size += 16; /* fence emit for VB IB */
ring_size += 5; /* done copy */
- ring_size += 10; /* fence emit for done copy */
+ ring_size += 16; /* fence emit for done copy */
r = radeon_ring_lock(rdev, ring_size);
if (r)
return r;
diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
index 9b62a97742a7..0991e63191c8 100644
--- a/drivers/gpu/drm/radeon/r600.c
+++ b/drivers/gpu/drm/radeon/r600.c
@@ -2327,6 +2327,14 @@ void r600_fence_ring_emit(struct radeon_device *rdev,
if (rdev-wb.use_event) {
u64 addr = rdev-wb.gpu_addr + R600_WB_EVENT_OFFSET +
(u64)(rdev-fence_drv.scratch_reg -
rdev-scratch.reg_base);
+ /* flush read cache over gart */
+ radeon_ring_write(rdev, PACKET3(PACKET3_SURFACE_SYNC, 3));
+ radeon_ring_write(rdev, PACKET3_TC_ACTION_ENA |
+ PACKET3_VC_ACTION_ENA |
+ PACKET3_SH_ACTION_ENA);
+ radeon_ring_write(rdev, 0x);
+ radeon_ring_write(rdev, 0);
+ radeon_ring_write(rdev, 10); /* poll interval */
/* EVENT_WRITE_EOP - flush caches, send int */
radeon_ring_write(rdev, PACKET3(PACKET3_EVENT_WRITE_EOP, 4));
radeon_ring_write(rdev,
EVENT_TYPE(CACHE_FLUSH_AND_INV_EVENT_TS) | EVENT_INDEX(5));
@@ -2335,6 +2343,14 @@ void r600_fence_ring_emit(struct radeon_device *rdev,
radeon_ring_write(rdev, fence-seq);
radeon_ring_write(rdev, 0);
} else {
+ /* flush read cache over gart */
+ radeon_ring_write(rdev, PACKET3(PACKET3_SURFACE_SYNC, 3));
+ radeon_ring_write(rdev, PACKET3_TC_ACTION_ENA |
+ PACKET3_VC_ACTION_ENA |
+ PACKET3_SH_ACTION_ENA);
+ radeon_ring_write(rdev, 0x);
+ radeon_ring_write(rdev, 0);
+ radeon_ring_write(rdev, 10); /* poll interval */
radeon_ring_write(rdev, PACKET3(PACKET3_EVENT_WRITE, 0));
radeon_ring_write(rdev, EVENT_TYPE(CACHE_FLUSH_AND_INV_EVENT) |
EVENT_INDEX(0));
/* wait for 3D idle clean */
diff --git a/drivers/gpu/drm/radeon/r600_blit_kms.c
b/drivers/gpu/drm/radeon/r600_blit_kms.c
index 9aa74c3f8cb6..d198b89cd403 100644
--- a/drivers/gpu/drm/radeon/r600_blit_kms.c
+++ b/drivers/gpu/drm/radeon/r600_blit_kms.c
@@ -632,9 +632,9 @@ int r600_blit_prepare_copy(struct radeon_device *rdev, int
size_bytes)
ring_size = num_loops *
Processed: Re: xserver-xorg-video-ati: Massive screen corruption in few hours after login
Processing commands for cont...@bugs.debian.org: found 646376 linux-2.6/3.0.0-3 Bug #646376 [linux-2.6] xserver-xorg-video-ati: Massive screen corruption in few hours after login Bug Marked as found in versions linux-2.6/3.0.0-3. tags 646376 + upstream patch moreinfo Bug #646376 [linux-2.6] xserver-xorg-video-ati: Massive screen corruption in few hours after login Added tag(s) upstream, moreinfo, and patch. quit Stopping processing here. Please contact me if you need assistance. -- 646376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132458463918963.transcr...@bugs.debian.org
Bug#582487: FYI: A workaround
Hi Jonathan, Happy holidays. I checked out the bug#582088 saga that you mentioned. I happened to notice it has a different stack trace than bug 582487. If I asked you nicely, would you please elaborate on why you think they're the same bug? Thanks, Kingsley On 12/22/11 05:08, Jonathan Nieder wrote: tags 582487 - moreinfo merge 582088 582487 quit Hi Kingsley, Kingsley G. Morse Jr. wrote: For what it's worth, I seem to have found a way to work around this bug. Having the same error message does not imply having the same bug. The bug you're responding to looks like another episode in the bug#582088 saga. Merging them. Kind regards, Jonathan -- 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/2011104436.ga19...@loaner.com
Bug#582487: FYI: A workaround
Thank you for sharing your detailed thoughts. I may owe you an apology for being too terse in my bug report. It seems to me that it may be important to explain: 1.) I encountered a stack trace like the one in bug#582487 after adding RAM, and then pretty much every time I booted the computer. My stack trace was consistent. It looked like the one in bug#582487. 2.) I encountered a bug on a different machine than the one(s) in bug#582487 and bug#582088. I have an MSI (Micro Star) MS-6712 (KT4V) motherboard, but the bug report you merged (#582088) to says Eee PC 1000HG, fuse. At the moment, it seems to me that bug#582487 and #582088 are different, and I humbly suggest un-merging them. Thanks, Kingsley On 12/22/11 14:49, Jonathan Nieder wrote: Kingsley G. Morse Jr. wrote: I happened to notice it has a different stack trace than bug 582487. If I asked you nicely, would you please elaborate on why you think they're the same bug? Sure. It's because they both are examples of inconsistent state pointing to memory corruption, each only happened once, and both happened on the same machine. -- 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/2011112523.gb19...@loaner.com
Bug#582487: FYI: A workaround
Kingsley G. Morse Jr. wrote: At the moment, it seems to me that bug#582487 and #582088 are different, and I humbly suggest un-merging them. You didn't report bug#582487 in the first place! Yes, you tripped the same assertion that Thiemo did. In your case, it seems it was due to a hardware problem. If you really want to track that in the BTS, please file a new bug. Thanks for your interest, and hope that helps. Regards, Jonathan -- 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/2011113241.GF8650@elie.Belkin
Bug#653026: Add support for new Terratec DVB USB IDs
Package: linux-patch-debian-3.1
Version: 3.1.5-1
Severity: wishlist
Tags: patch
Hello,
current revision of the Cinergy S2 USB box from Terratec seems to use
another USB-IDs. The manufacturer provides patches at
http://linux.terratec.de/tv_en.html and it seems like the only
difference is really just the new ID and a couple of init flag changes.
Their patch is not exactly for the linux-3.x tree but for the current
s2-liplianin drivers, OTOH they still look similar enough and porting
the patch was straight-forward. I also added the patch for Terratec S7
which is not tested yet but shouldn't do any harm.
See attachment.
Regards,
Eduard.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
From: Eduard Bloch bl...@debian.org
Date: Thu, 22 Dec 2011 19:46:54 +0100
Subject: new device IDs used by some Terratec USB devices
The changes are extracted from ID patches in tarballs at
http://linux.terratec.de/tv_en.html (for S7 and Cinergy S2 USB HD), and
slightly modified to match the state of s2-liplianin tree used in linux-3.x so
far.
---
diff -urd linux-2.6-3.1.5.debian/drivers/media/dvb/dvb-usb/az6027.c linux-2.6-3.1.5/drivers/media/dvb/dvb-usb/az6027.c
--- linux-2.6-3.1.5.debian/drivers/media/dvb/dvb-usb/az6027.c 2011-12-09 17:57:05.0 +0100
+++ linux-2.6-3.1.5/drivers/media/dvb/dvb-usb/az6027.c 2011-12-22 19:42:25.655675023 +0100
@@ -1090,6 +1090,7 @@
{ USB_DEVICE(USB_VID_TECHNISAT, USB_PID_TECHNISAT_USB2_HDCI_V1) },
{ USB_DEVICE(USB_VID_TECHNISAT, USB_PID_TECHNISAT_USB2_HDCI_V2) },
{ USB_DEVICE(USB_VID_ELGATO, USB_PID_ELGATO_EYETV_SAT) },
+ { USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_DVBS2CI_V3) },
{ },
};
@@ -1135,7 +1136,7 @@
.i2c_algo = az6027_i2c_algo,
- .num_device_descs = 6,
+ .num_device_descs = 7,
.devices = {
{
.name = AZUREWAVE DVB-S/S2 USB2.0 (AZ6027),
@@ -1161,6 +1162,10 @@
.name = Elgato EyeTV Sat,
.cold_ids = { az6027_usb_table[5], NULL },
.warm_ids = { NULL },
+ }, {
+ .name = TERRATEC S7 Rev.3,
+ .cold_ids = { az6027_usb_table[6], NULL },
+ .warm_ids = { NULL },
},
{ NULL },
}
diff -urd linux-2.6-3.1.5.debian/drivers/media/dvb/dvb-usb/dvb-usb-ids.h linux-2.6-3.1.5/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
--- linux-2.6-3.1.5.debian/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2011-12-09 17:57:05.0 +0100
+++ linux-2.6-3.1.5/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2011-12-22 19:40:02.208934727 +0100
@@ -319,6 +319,7 @@
#define USB_PID_AZUREWAVE_AZ6027 0x3275
#define USB_PID_TERRATEC_DVBS2CI_V1 0x10a4
#define USB_PID_TERRATEC_DVBS2CI_V2 0x10ac
+#define USB_PID_TERRATEC_DVBS2CI_V3 0x10b0
#define USB_PID_TECHNISAT_USB2_HDCI_V1 0x0001
#define USB_PID_TECHNISAT_USB2_HDCI_V2 0x0002
#define USB_PID_TECHNISAT_AIRSTAR_TELESTICK_2 0x0004
diff -urd linux-2.6-3.1.5.debian/drivers/media/dvb/dvb-usb/dw2102.c linux-2.6-3.1.5/drivers/media/dvb/dvb-usb/dw2102.c
--- linux-2.6-3.1.5.debian/drivers/media/dvb/dvb-usb/dw2102.c 2011-12-09 17:57:05.0 +0100
+++ linux-2.6-3.1.5/drivers/media/dvb/dvb-usb/dw2102.c 2011-12-22 19:43:16.588387654 +0100
@@ -1181,6 +1181,14 @@
{
u8 obuf[3] = { 0xe, 0x80, 0 };
u8 ibuf[] = { 0 };
+
+ if (dvb_usb_generic_rw(d-dev, obuf, 3, ibuf, 1, 0) 0)
+ err(command 0x0e transfer failed.);
+
+ //power on su3000
+ obuf[0] = 0xe;
+ obuf[1] = 0x02;
+ obuf[2] = 1;
if (dvb_usb_generic_rw(d-dev, obuf, 3, ibuf, 1, 0) 0)
err(command 0x0e transfer failed.);
@@ -1451,6 +1459,7 @@
{USB_DEVICE(0x9022, USB_PID_TEVII_S480_1)},
{USB_DEVICE(0x9022, USB_PID_TEVII_S480_2)},
{USB_DEVICE(0x1f4d, 0x3100)},
+ {USB_DEVICE(USB_VID_TERRATEC, 0x00b0)},
{ }
};
@@ -1824,7 +1833,7 @@
}
}
},
- .num_device_descs = 3,
+ .num_device_descs = 4,
.devices = {
{ SU3000HD DVB-S USB2.0,
{ dw2102_table[10], NULL },
@@ -1838,6 +1847,10 @@
{ dw2102_table[14], NULL },
{ NULL },
},
+ { Terratec Cinergy S2 USB HD Rev.2,
+ { dw2102_table[15], NULL },
+ { NULL },
+ },
}
};
Bug#653026: Add support for new Terratec DVB USB IDs
tags 653026 + upstream forwarded 653026 http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/42219 quit Eduard Bloch wrote: current revision of the Cinergy S2 USB box from Terratec seems to use another USB-IDs. The manufacturer provides patches at http://linux.terratec.de/tv_en.html and it seems like the only difference is really just the new ID and a couple of init flag changes. Their patch is not exactly for the linux-3.x tree but for the current s2-liplianin drivers, OTOH they still look similar enough and porting the patch was straight-forward. Thanks. Let's take this upstream. -- 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/2011135255.GC10497@elie.Belkin
Processed: Re: Add support for new Terratec DVB USB IDs
Processing commands for cont...@bugs.debian.org: tags 653026 + upstream Bug #653026 [linux-patch-debian-3.1] Add support for new Terratec DVB USB IDs Added tag(s) upstream. forwarded 653026 http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/42219 Bug #653026 [linux-patch-debian-3.1] Add support for new Terratec DVB USB IDs Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/42219'. quit Stopping processing here. Please contact me if you need assistance. -- 653026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132459798618935.transcr...@bugs.debian.org
Processed: reassign 653026 to src:linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 653026 src:linux-2.6 3.1.5-1 Bug #653026 [linux-patch-debian-3.1] Add support for new Terratec DVB USB IDs Bug reassigned from package 'linux-patch-debian-3.1' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/3.1.5-1. Bug #653026 [src:linux-2.6] Add support for new Terratec DVB USB IDs Bug Marked as found in versions linux-2.6/3.1.5-1. thanks Stopping processing here. Please contact me if you need assistance. -- 653026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132459981227759.transcr...@bugs.debian.org
Bug#596297: unrar crashed with kernel error message
# letting version tracking do its work tags 596297 - squeeze tags 596297 + moreinfo quit Hi Stefan, Stefan Arnold wrote: As I told the kernel gave me a error message during unpacking an archive. The unrar process did not die and i could not even kill it with -9. Oh, dear. Sorry for the slow response. BUG: unable to handle kernel NULL pointer dereference at 0800 IP: [c10cd8e7] unmap_underlying_metadata+0x1f/0x3a *pde = Oops: 0002 [#1] SMP Was this reproducible? Is it still? [...] Pid: 5036, comm: unrar Tainted: P (2.6.32-5-686 #1) To Be Filled By O.E.M. [...] [c10ce286] ? __block_prepare_write+0x163/0x297 [c10ce50d] ? block_write_begin+0x70/0xc6 [f805fe2b] ? ext3_get_block+0x0/0xd1 [ext3] [f80610f3] ? ext3_write_begin+0xe6/0x1d2 [ext3] [f805fe2b] ? ext3_get_block+0x0/0xd1 [ext3] [c1087ab7] ? generic_file_buffered_write+0xd0/0x21d [c1088001] ? __generic_file_aio_write+0x265/0x28d [c102cdb6] ? try_to_wake_up+0x25d/0x269 [c10beac7] ? pollwake+0x5c/0x65 [c108807a] ? generic_file_aio_write+0x51/0x93 [c10b2652] ? do_sync_write+0xc0/0x107 [c10437ee] ? autoremove_wake_function+0x0/0x2d [c10b239e] ? fsnotify_modify+0x5a/0x61 [c1101994] ? security_file_permission+0xc/0xd [c10b2592] ? do_sync_write+0x0/0x107 [c10b2f7e] ? vfs_write+0x7e/0xd6 [c10b306e] ? sys_write+0x3c/0x63 [c10030fb] ? sysenter_do_call+0x12/0x28 Code: 75 08 89 d8 5b e9 cc ff ff ff 5b c3 57 89 c7 56 89 ce 53 89 d3 e8 5c df 19 00 89 da 89 f1 89 f8 e8 54 f1 ff ff 85 c0 89 c3 74 17 3e 80 20 fd e8 ba ff ff ff 3e 80 23 f7 89 d8 5b 5e 5f e9 ef f3 If this is reproducible, please provide full dmesg output from booting and triggering the bug, without the nvidia driver loaded. (If the bug is only reproducible in the presence of the nvidia driver, that's fine too, and we can pass the report to that driver's authors.) Thanks and hope that helps, Jonathan -- 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/20111223003016.GA11875@elie.Belkin
Processed: Re: unrar crashed with kernel error message
Processing commands for cont...@bugs.debian.org: # letting version tracking do its work tags 596297 - squeeze Bug #596297 [linux-2.6] linux-image-2.6.32-5-686: unrar crashed with kernel error message Removed tag(s) squeeze. tags 596297 + moreinfo Bug #596297 [linux-2.6] linux-image-2.6.32-5-686: unrar crashed with kernel error message Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 596297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132460023229348.transcr...@bugs.debian.org
Bug#596649: linux-image-2.6.32-5-openvz-amd64: system crash using rtl818x USB wlan
Hi Steven, Steven Chamberlain wrote: After several hours or days of running aircrack-ng (in this instance only 90 minutes) on a USB rtl8187 wlan interface, a strange kind of kernel lockup happens. Many processes hang, I think when they attempt some kind of disk I/O. I remember having a similar issue in 2.6.26 kernels, too, on the same system. Is this still reproducible? If so, two pieces of information would make it easier to move forward: 1. Please provide a summary of blocked tasks when reproducing this, for example by using the magic sysrq key T, D, or W. You might need to run echo 1 /proc/sys/kernel/sysrq first, to enable permission to use those commands. See Documentation/sysrq.txt for details. 2. Please test with a 3.x.y kernel from sid or experimental. The only packages from outside squeeze aside from the kernel image itself you should need in order to test are linux-base and initramfs-tools. The first piece would help investigate what is causing the deadlock. The latter would let us get help from upstream if the problem still exists there, or start to look for an existing patch with a fix if it doesn't. Thanks and hope that helps, Jonathan -- 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/20111223004745.GA12892@elie.Belkin
Processed: tagging 650652
Processing commands for cont...@bugs.debian.org: tags 650652 + pending Bug #650652 [linux-2.6] linux-image-2.6.32-5-amd64: Kernel IPsec code rejects 288-bit keys for AES-CTR as being too long Ignoring request to alter tags of bug #650652 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 650652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.132460512818000.transcr...@bugs.debian.org
Bug#649563: Acknowledgement (linux-image-3.1.0-1-amd64 can't load initial ramdisk anymore)
After upgrading to kernel linux-image-3.1.0-1-amd64 3.1.5-1 the kernel boots without errors. The Bug can be closed. Regards Friedemann -- 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/20111223061057.ga10...@excelsior.lab.swapon.de
