Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
found 689268 linux/3.2.32-1 fixed 689268 linux/3.3.6-1~experimental.1 , linux/3.5.5-1~experimental.1 quit Per Foreby wrote: I've been running 3.3.6-1~experimental.1 for 10 days without problems. Just tried 3.2.32-1 and the system froze after 18 minutes. Now back on 3.3. Perfect. Marking so. Could you try 3.3~rc6-1~experimental.1? (I expect it will also work fine, but there's always a chance that we could get lucky and narrow down the range by a lot.) If it works ok, here are instructions for testing 3.3-rc6 with drm code from 3.2: 0. prerequisites apt-get install git build-essential 1. get the kernel history, if you don't already have it git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2. configure, build, test cd linux git checkout v3.3-rc6 cp /boot/config-$(uname -r) .config; # current configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root reboot Hopefully it works fine. So 3. try drm code from 3.2 cd linux git checkout v3.2 -- include/drm drivers/gpu/drm make deb-pkg; # maybe with -j4 dpkg -i ..name of package; # as root reboot Hopefully it reproduces the bug. If that works, we'll be ready to run a reverse bisect on the drm code like Daniel suggested. Thanks again for your patient efforts on this. Sorry it has been taking so long. 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/20121103081431.GD8326@elie.Belkin
Processed: Re: Intel HD 4000 (Ivy Bridge) graphics freeze
Processing commands for cont...@bugs.debian.org: found 689268 linux/3.2.32-1 Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Marked as found in versions linux/3.2.32-1. fixed 689268 linux/3.3.6-1~experimental.1 , linux/3.5.5-1~experimental.1 Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze The source linux and version 3.3.6-1~experimental.1 do not appear to match any binary packages Marked as fixed in versions linux/3.5.5-1~experimental.1 and linux/3.3.6-1~experimental.1. quit Stopping processing here. Please contact me if you need assistance. -- 689268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268 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.135193048229026.transcr...@bugs.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
tags 691902 - moreinfo quit Janne Boman wrote: just installed wheezy (managed to get netinst cd working) Same restart issue persists. I attached the output from reportbug --template linux-image-$(uname -r), for this latest installation also. Methods that I tried for shutdown: - From Gnome - From terminal: shutdown -h now, halt, poweroff Lovely, thanks. Please attach full acpidump and dmesg output. If you get a chance to try 3.6.y from experimental, that would also be very useful. If we're lucky then d8e725f356fd ACPI: Ignore invalid _PSS entries, but use valid ones which is included in that version will fix this. 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/20121103082112.GE8326@elie.Belkin
Processed: Re: [squeeze-wheezy regression] Unable to shutdown via normal means
Processing commands for cont...@bugs.debian.org: tags 691902 - moreinfo Bug #691902 [src:linux] Unable to shutdown Debian Wheezy via normal means Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 691902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691902 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.135193090231894.transcr...@bugs.debian.org
Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out
Uwe Kleine-König wrote: On Mon, Oct 29, 2012 at 11:49:37PM -0700, Jonathan Nieder wrote: Uwe Kleine-König wrote: For DEBIAN_KERNEL_DISABLE_DEBUG it might even be worth to default to no debug packages and use -d to enable them?! Sounds sane. How about something like this? Looks good, only some nitpicking below ... Thanks for the review. Except for the + - :+ change (using the non-: form allows users to override the default in their environment), I like all your proposed changes. I guess it would be nice to have a separate bugreport so this doesn't get forgotten if you're interested. (Or to send the latest patch to debian-kernel@ and then apply it if appropriate. I don't know what the commit policy is.) Sincerely, 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/20121103093338.GA27123@elie.Belkin
Processed: Re: Intel HD 4000 (Ivy Bridge) graphics freeze
Processing commands for cont...@bugs.debian.org: notfixed 689268 linux/3.3.6-1~experimental.1 Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze The source linux and version 3.3.6-1~experimental.1 do not appear to match any binary packages No longer marked as fixed in versions linux/3.3.6-1~experimental.1. fixed 689268 linux-2.6/3.3.6-1~experimental.1 Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Marked as fixed in versions linux-2.6/3.3.6-1~experimental.1. End of message, stopping processing here. Please contact me if you need assistance. -- 689268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268 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.135193535029635.transcr...@bugs.debian.org
Re: Uploading linux (3.2.32-1)
On Fri, 2012-11-02 at 21:59 +, Adam D. Barratt wrote:
On Fri, 2012-10-19 at 14:44 +0100, Ben Hutchings wrote:
I intend to upload linux version 3.2.32-1 to unstable this weekend.
This brings in various fixes from stable updates 3.2.{31,32} and
elsewhere, and should fix the previous FTBFS on mips{,el}.
Unblocked after an ack from KiBi on IRC; thanks.
You should unblock linux-latest as well.
Ben.
--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett
signature.asc
Description: This is a digitally signed message part
Re: Uploading linux (3.2.32-1)
On Sat, 2012-11-03 at 14:20 +, Ben Hutchings wrote:
On Fri, 2012-11-02 at 21:59 +, Adam D. Barratt wrote:
On Fri, 2012-10-19 at 14:44 +0100, Ben Hutchings wrote:
I intend to upload linux version 3.2.32-1 to unstable this weekend.
This brings in various fixes from stable updates 3.2.{31,32} and
elsewhere, and should fix the previous FTBFS on mips{,el}.
Unblocked after an ack from KiBi on IRC; thanks.
You should unblock linux-latest as well.
Yep:
linux-latest | 46 | testing | source
linux-latest | 46 | unstable | source
Regards,
Adam
--
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/1351953934.4348.14.ca...@jacala.jungle.funky-badger.org
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
Am 03.11.2012 09:14, schrieb Jonathan Nieder: found 689268 linux/3.2.32-1 fixed 689268 linux/3.3.6-1~experimental.1 , linux/3.5.5-1~experimental.1 quit Just a proposal: is it possible to apply this patch from Intel to the 3.2 kernel: http://lists.freedesktop.org/archives/intel-gfx/2012-February/015005.html? This would allow to figure out by manually activating different rc6 states whether rc6 implementation is the root cause. From kernel 3.3 on the settings and default beheavior of the parameter i915_enable_rc6 have changed. Wheezy's 3.2 kernel does not include this patch according to 'modinfo i915' Ingo -- 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/5095493c.6000...@gmx.net
Processed: your mail
Processing commands for cont...@bugs.debian.org: found 690428 4:4.8.4-4 Bug #690428 [kde-window-manager] kwin: GTK Menus randomly fail to render if Fade Effect disabled Marked as found in versions kde-workspace/4:4.8.4-4. found 684352 3.2.32-1 Bug #684352 [src:linux] [Presario V4000T] hp-wmi: wifi blocked at boot, network-manager and wifi button don't unblock Marked as found in versions linux/3.2.32-1. thanks. Stopping processing here. Please contact me if you need assistance. -- 684352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684352 690428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690428 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.135196209715747.transcr...@bugs.debian.org
Bug#692225: linux-image-3.6-trunk-amd64: screen starts to flicker after suspend-to-disk
Package: src:linux Version: 3.6.4-1~experimental.1 Severity: wishlist I've recently upgrade from 3.2 to 3.6. Since the upgrade after resuming from supsend-to-disk the screen starts to flicker and the kernel log contains the following traceback: [ 4730.108047] [ cut here ] [ 4730.108073] WARNING: at /build/buildd-linux_3.6.4-1~experimental.1-amd64-QnAy6j/linux-3.6.4/drivers/gpu/drm/i915/intel_display.c:1225 intel_crtc_disable+0x52/0x86 [i915]() [ 4730.108074] Hardware name: 7458WTH [ 4730.108076] pipe B assertion failure (expected off, current on) [ 4730.108125] Modules linked in: snap [ 4730.108161] Pid: 12434, comm: kworker/u:6 Not tainted 3.6-trunk-amd64 #1 Debian 3.6.4-1~experimental.1 [ 4730.108167] Call Trace: [ 4730.108173] [8103caa3] ? warn_slowpath_common+0x78/0x8c [ 4730.108176] [8105c375] ? async_schedule+0xc/0xc [ 4730.108178] [8103cb4f] ? warn_slowpath_fmt+0x45/0x4a [ 4730.108180] [8105c375] ? async_schedule+0xc/0xc [ 4730.108189] [a04dfcfc] ? intel_crtc_disable+0x52/0x86 [i915] [ 4730.108192] [a042fe47] ? drm_helper_disable_unused_functions+0xd0/0xfb [drm_kms_helper] [ 4730.108195] [a043061e] ? drm_helper_resume_force_mode+0xf1/0xff [drm_kms_helper] [ 4730.108197] [8105c375] ? async_schedule+0xc/0xc [ 4730.108203] [a04be17f] ? i915_drm_thaw+0xd4/0x10b [i915] [ 4730.108208] [a04be501] ? i915_resume+0x3b/0x50 [i915] [ 4730.108212] [811d607d] ? pci_legacy_resume+0x39/0x39 [ 4730.108214] [8126bac3] ? dpm_run_callback.isra.5+0x26/0x54 [ 4730.108216] [8126c3aa] ? device_resume+0xd0/0x110 [ 4730.108218] [8126c3fe] ? async_resume+0x14/0x38 [ 4730.108220] [8105c412] ? async_run_entry_fn+0x9d/0x174 [ 4730.108222] [81052bfd] ? process_one_work+0x17e/0x29d [ 4730.108224] [810538ec] ? worker_thread+0x1fe/0x29f [ 4730.108226] [810536ee] ? manage_workers+0x223/0x223 [ 4730.108227] [810536ee] ? manage_workers+0x223/0x223 [ 4730.108229] [81056d51] ? kthread+0x67/0x6f [ 4730.108232] [81370604] ? kernel_thread_helper+0x4/0x10 [ 4730.108233] [81056cea] ? kthread_freezable_should_stop+0x3c/0x3c [ 4730.108235] [81370600] ? gs_change+0x13/0x13 [ 4730.108236] ---[ end trace 9da7aea57c4d16f6 ]--- After a reboot everything works fine again. If you need any more information, please feal free to ask. Kind regards -- Package-specific info: ** Version: Linux version 3.6-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Debian 3.6.4-1~experimental.1 ** Command line: BOOT_IMAGE=/vmlinuz-3.6-trunk-amd64 root=/dev/mapper/mercury2-root ro resume=/dev/mapper/mercury2-swap acpi_sleep=s3_bios ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 4729.54] usb usb8: root hub lost power or was reset [ 4729.541126] ehci_hcd :00:1d.7: setting latency timer to 64 [ 4729.541143] usb usb2: root hub lost power or was reset [ 4729.542793] ehci_hcd :00:1a.7: cache line size of 64 is not supported [ 4729.542804] pci :00:1e.0: setting latency timer to 64 [ 4729.542820] ahci :00:1f.2: setting latency timer to 64 [ 4729.542846] iwlwifi :03:00.0: RF_KILL bit toggled to enable radio. [ 4729.544456] dpm_run_callback(): pnp_bus_resume+0x0/0x62 returns -19 [ 4729.544457] PM: Device 00:0a failed to restore: error -19 [ 4729.545458] ehci_hcd :00:1d.7: cache line size of 64 is not supported [ 4729.547182] Extended CMOS year: 2000 [ 4729.860042] ata2: SATA link down (SStatus 0 SControl 300) [ 4729.860070] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 4729.861890] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 4729.861893] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 4729.861960] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded [ 4729.861962] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 4729.913721] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 4729.913724] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 4729.913819] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded [ 4729.913822] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 4729.916402] ata1.00: configured for UDMA/133 [ 4729.932170] sd 0:0:0:0: [sda] Starting disk [ 4729.937887] iwlwifi :03:00.0: L1 Disabled; Enabling L0S [ 4729.938301] iwlwifi :03:00.0: Radio type=0x0-0x2-0x0 [ 4730.008101] usb 1-6: reset high-speed USB device number 3 using ehci_hcd [ 4730.108047] [ cut here ] [ 4730.108073] WARNING: at /build/buildd-linux_3.6.4-1~experimental.1-amd64-QnAy6j/linux-3.6.4/drivers/gpu/drm/i915/intel_display.c:1225 intel_crtc_disable+0x52/0x86 [i915]() [ 4730.108074] Hardware name: 7458WTH [ 4730.108076] pipe B assertion failure (expected off, current on) [ 4730.108125]
Processed: Re: [squeeze-wheezy regression] Unable to shutdown via normal means
Processing commands for cont...@bugs.debian.org: found 691902 linux/3.6.4-1~experimental.1 Bug #691902 [src:linux] Unable to shutdown Debian Wheezy via normal means Marked as found in versions linux/3.6.4-1~experimental.1. End of message, stopping processing here. Please contact me if you need assistance. -- 691902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691902 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.135196453032556.transcr...@bugs.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
found 691902 linux/3.6.4-1~experimental.1
quit
Janne Boman wrote:
acpidump dmesg attached
3.6 from experimental did not work...
Thanks for checking so quickly. By did not work, you mean that
after booting that kernel, shutting down caused the computer to
reboot, right?
Please test the pre-compiled 3.2.13-1 and 3.2.14-1 packages from
http://snapshot.debian.org/package/linux-2.6/, or if you prefer,
please test the attached patch against a 3.7-rc3 or newer kernel, for
example by using the following directions:
0. prerequisites
apt-get install git build-essential
1. get the kernel history, if you don't already have it
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
2. configure, build, test
cd linux
git fetch origin
git checkout origin/master
cp /boot/config-3.6-trunk-amd64 .config; # stock configuration
scripts/config --disable DEBUG_INFO
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -jnum for parallel build
dpkg -i ../name of package; # as root
shut down, unplug, remove battery, wait a few seconds
restore power, boot
shutdown -h now
Hopefully it reproduces the bug, so
3. try the patch
cd linux
git revert 41c7f7424259
:wq
make deb-pkg; # maybe with -j4
dpkg -i ../name of package; # as root
... power down completely, test it ...
Hope that helps,
Jonathan
From: Jonathan Nieder jrnie...@gmail.com
Date: Sat, 3 Nov 2012 10:58:20 -0700
Subject: Revert rtc: Disable the alarm in the hardware (v2)
This reverts commit 41c7f7424259ff11009449f87c95656f69f9b186,
which should tell us whether Alessandro will want to know about
these shutdown failures.
Not signed off, only for testing.
---
drivers/rtc/interface.c | 15 ++-
1 file changed, 2 insertions(+), 13 deletions(-)
diff --git a/drivers/rtc/interface.c b/drivers/rtc/interface.c
index 9592b936b71b..c11596b9ba4e 100644
--- a/drivers/rtc/interface.c
+++ b/drivers/rtc/interface.c
@@ -782,14 +782,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)
-{
- if (!rtc-ops || !rtc-ops-alarm_irq_enable)
- return;
-
- rtc-ops-alarm_irq_enable(rtc-dev.parent, false);
-}
-
/**
* rtc_timer_remove - Removes a rtc_timer from the rtc_device timerqueue
* @rtc rtc device
@@ -811,10 +803,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);
@@ -877,8 +867,7 @@ again:
err = __rtc_set_alarm(rtc, alarm);
if (err == -ETIME)
goto again;
- } else
- rtc_alarm_disable(rtc);
+ }
mutex_unlock(rtc-ops_lock);
}
--
1.8.0
Processed: Re: [squeeze-wheezy regression] Unable to shutdown via normal means
Processing commands for cont...@bugs.debian.org: found 691902 linux/3.6.4-1~experimental.1 Bug #691902 [src:linux] Unable to shutdown Debian Wheezy via normal means Marked as found in versions linux/3.6.4-1~experimental.1; no longer marked as found in versions linux/3.6.4-1~experimental.1. quit Stopping processing here. Please contact me if you need assistance. -- 691902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691902 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.135196607811822.transcr...@bugs.debian.org
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
Ingo wrote: Just a proposal: is it possible to apply this patch from Intel to the 3.2 kernel: http://lists.freedesktop.org/archives/intel-gfx/2012-February/015005.html? This would allow to figure out by manually activating different rc6 states whether rc6 implementation is the root cause. What happens if you use i915.i915_enable_rc6=0 with the stock kernel? If that doesn't work, I doubt other modes (which are only more aggressive about power management) will. -- 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/20121103181803.GC2685@elie.Belkin
Bug#692225: [3.2-3.6.4 regression] screen starts to flicker after suspend-to-disk
tags 692225 + upstream forwarded 692225 http://thread.gmane.org/gmane.comp.video.dri.devel/75108 # regression severity 692225 important quit Hi Bjørn, Sebastian Ramacher wrote[1]: I've recently upgrade from 3.2 to 3.6. Since the upgrade after resuming from supsend-to-disk the screen starts to flicker and the kernel log contains the following traceback: [ 4730.108047] [ cut here ] [ 4730.108073] WARNING: at /build/buildd-linux_3.6.4-1~experimental.1-amd64-QnAy6j/linux-3.6.4/drivers/gpu/drm/i915/intel_display.c:1225 intel_crtc_disable+0x52/0x86 [i915]() [ 4730.108074] Hardware name: 7458WTH [ 4730.108076] pipe B assertion failure (expected off, current on) Looks like http://thread.gmane.org/gmane.comp.video.dri.devel/75108. Do you know if this got fixed? Thanks, Jonathan [1] http://bugs.debian.org/692225 -- 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/20121103182630.GD2685@elie.Belkin
Processed: Re: [3.2-3.6.4 regression] screen starts to flicker after suspend-to-disk
Processing commands for cont...@bugs.debian.org: tags 692225 + upstream Bug #692225 [src:linux] linux-image-3.6-trunk-amd64: screen starts to flicker after suspend-to-disk Added tag(s) upstream. forwarded 692225 http://thread.gmane.org/gmane.comp.video.dri.devel/75108 Bug #692225 [src:linux] linux-image-3.6-trunk-amd64: screen starts to flicker after suspend-to-disk Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.comp.video.dri.devel/75108'. # regression severity 692225 important Bug #692225 [src:linux] linux-image-3.6-trunk-amd64: screen starts to flicker after suspend-to-disk Severity set to 'important' from 'wishlist' quit Stopping processing here. Please contact me if you need assistance. -- 692225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692225 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.135196720119065.transcr...@bugs.debian.org
Processed: Re: [3.2-3.6.4 regression] screen starts to flicker after suspend-to-disk
Processing commands for cont...@bugs.debian.org: # [1] forwarded 692225 https://bugs.freedesktop.org/56118 Bug #692225 [src:linux] linux-image-3.6-trunk-amd64: screen starts to flicker after suspend-to-disk Changed Bug forwarded-to-address to 'https://bugs.freedesktop.org/56118' from 'http://thread.gmane.org/gmane.comp.video.dri.devel/75108' quit Stopping processing here. Please contact me if you need assistance. -- 692225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692225 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.13519697413347.transcr...@bugs.debian.org
Bug#692225: [3.2-3.6.4 regression] screen starts to flicker after suspend-to-disk
# [1] forwarded 692225 https://bugs.freedesktop.org/56118 quit Sebastian Ramacher wrote: I've recently upgrade from 3.2 to 3.6. Since the upgrade after resuming from supsend-to-disk the screen starts to flicker and the kernel log contains the following traceback: [ 4730.108047] [ cut here ] [ 4730.108073] WARNING: at /build/buildd-linux_3.6.4-1~experimental.1-amd64-QnAy6j/linux-3.6.4/drivers/gpu/drm/i915/intel_display.c:1225 intel_crtc_disable+0x52/0x86 [i915]() [ 4730.108074] Hardware name: 7458WTH [ 4730.108076] pipe B assertion failure (expected off, current on) Oh, here's a better link: [1]. This is said to be fixed by fa55583797d1 drm/i915: fixup the plane-pipe fixup code A naive backport of that depends on 24929352481f drm/i915: read out the modeset hw state at load and resume time which in turn depends on the series *: implement get_hw_state *: convert to encoder-disable/enable 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/20121103190851.GE2685@elie.Belkin
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Hi, after ~48 hours of memtest86+ (almost 60 tests) , it has founded no errors on the 'problematic' RAM (the 4gB ram B of the 8gB set). I'm now trying again to use that ram to run debian, to see if i have a crash also this time. ciao, Asdrubale -- 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/22561044.9318171351972642373.JavaMail.defaultUser@defaultHost
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
Ingo wrote:
Am 03.11.2012 21:05, schrieb Jonathan Nieder:
Ingo wrote:
I did set it now to 0 and suprisingly power consumption does not
change by a single watt in both cases: idle desktop and graphics/monitor
off by DPMS. I'll leave it now like this and see - last time it took 3
weeks until the freeze happend. I'll report here again if any freeze
happens.
Thanks. Do you mind if I forward this information to the bug log?
Please go ahead, thanks.
[...]
linux-2.6 (3.2.7-1) unstable; urgency=low
* [x86] drm/i915: do not enable RC6p on Sandy Bridge (Closes: #660265)
What about Ivy Bridge - that's what me and Per are using. Is there
anwhere a table on which devices which rc6 states are enabled?
From drivers/gpu/drm/i915/intel_display.c:
| static bool intel_enable_rc6(struct drm_device *dev)
| {
| /*
|* Respect the kernel parameter if it is set
|*/
| if (i915_enable_rc6 = 0)
| return i915_enable_rc6;
|
| /*
|* Disable RC6 on Ironlake
|*/
| if (INTEL_INFO(dev)-gen == 5)
| return 0;
|
| /*
|* Disable rc6 on Sandybridge
|*/
| if (INTEL_INFO(dev)-gen == 6) {
| DRM_DEBUG_DRIVER(Sandybridge: RC6 disabled\n);
| return 0;
| }
| DRM_DEBUG_DRIVER(RC6 enabled\n);
| return 1;
| }
[...]
| if (intel_enable_rc6(dev_priv-dev))
| rc6_mask = GEN6_RC_CTL_RC6_ENABLE |
| ((IS_GEN7(dev_priv-dev)) ? GEN6_RC_CTL_RC6p_ENABLE :
0);
Ivy Bridge is gen7. So RC6p is not masked out by default, and setting
i915_enable_rc6=0 will mask it out along with RC6. If you pass
drm.debug=0x2 (or anything with that bit set, such as 0xe) on the
kernel command line then you can tell if RC6 is enabled by looking for
an RC6 enabled line in the kernel log.
--
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/20121103203638.GG2685@elie.Belkin
Processed: Re: Intel HD 4000 (Ivy Bridge) graphics freeze
Processing commands for cont...@bugs.debian.org: clone 689268 -1 Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Bug 689268 cloned as bug 692234 submitter -1 Ingo ingo.stei...@gmx.net Bug #692234 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Changed Bug submitter to 'Ingo ingo.stei...@gmx.net' from 'Per Foreby p...@foreby.se' retitle -1 Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use Bug #692234 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Changed Bug title to 'Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use' from 'linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze' notfound -1 linux/3.2.32-1 Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use No longer marked as found in versions linux/3.2.32-1. notfixed -1 linux-2.6/3.3.6-1~experimental.1, linux/3.5.5-1~experimental.1 Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use No longer marked as fixed in versions linux-2.6/3.3.6-1~experimental.1 and linux/3.5.5-1~experimental.1. End of message, stopping processing here. Please contact me if you need assistance. -- 689268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268 692234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692234 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.13519756109666.transcr...@bugs.debian.org
Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
Jonathan Nieder wrote: Hi Ingo, [...] There seem to be some differences in symptoms here, so please file a separate bug. We can merge them later if they turn out to have the same cause. I've assigned you bug#692234. Please attach output from reportbug --template linux-image-$(uname -r) so we can get to know your hardware better. 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/20121103211131.GH2685@elie.Belkin
Bug#692234: Intel HD 4000 (Ivy Bridge) graphics freeze
Am 03.11.2012 22:11, schrieb Jonathan Nieder: Jonathan Nieder wrote: Hi Ingo, [...] There seem to be some differences in symptoms here, so please file a separate bug. We can merge them later if they turn out to have the same cause. I've assigned you bug#692234. Many thanks Please attach output from reportbug --template linux-image-$(uname -r) -- Package-specific info: ** Version: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz root=/dev/sda2 ro i915_enable_rc6=0 drm.debug=0x2 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [5.067690] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [5.068703] wmi: Mapper loaded [5.071376] [drm] Initialized drm 1.1.0 20060810 [5.073829] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [5.073906] ACPI: Power Button [PWRF] [5.080647] input: PC Speaker as /devices/platform/pcspkr/input/input5 [5.082947] snd_hda_intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [5.083058] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X [5.083082] snd_hda_intel :00:1b.0: setting latency timer to 64 [5.088670] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [5.128078] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input6 [5.133604] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input7 [5.133814] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [5.133881] i915 :00:02.0: setting latency timer to 64 [5.187108] mtrr: type mismatch for e000,1000 old: write-back new: write-combining [5.187192] [drm] MTRR allocation failed. Graphics performance may suffer. [5.187514] [drm:intel_opregion_setup], graphic opregion physical addr: 0xda3d1018 [5.187537] [drm:intel_opregion_setup], SWSCI supported [5.187561] i915 :00:02.0: irq 44 for MSI/MSI-X [5.187566] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.187636] [drm] Driver supports precise vblank timestamp query. [5.187769] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed [5.188079] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [5.242913] [drm:gm45_get_vblank_counter], trying to get vblank count for disabled pipe B [5.242918] [drm:gm45_get_vblank_counter], trying to get vblank count for disabled pipe B [5.243687] [drm:gm45_get_vblank_counter], trying to get vblank count for disabled pipe C [5.243690] [drm:gm45_get_vblank_counter], trying to get vblank count for disabled pipe C [5.244761] [drm:intel_enable_rc6], RC6 enabled [5.430264] [drm:init_status_page], render ring hws offset: 0x [5.430505] [drm:init_status_page], gen6 bsd ring hws offset: 0x00022000 [5.430660] [drm:init_status_page], blt ring hws offset: 0x00043000 [5.452946] [drm:pch_irq_handler], PCH HDCP audio interrupt [5.653336] fbcon: inteldrmfb (fb0) is primary device [5.710016] [drm:intel_dp_mode_set], Enabling DP audio on pipe A [5.710020] [drm:intel_write_eld], ELD on [CONNECTOR:18:DP-2], [ENCODER:19:TMDS-19] [5.710023] [drm:ironlake_write_eld], ELD on pipe A [5.710029] [drm:ironlake_write_eld], Audio directed to unknown port [5.710033] [drm:ironlake_write_eld], ELD: DisplayPort detected [5.710037] [drm:ironlake_write_eld], ELD size 8 [5.841720] Console: switching to colour frame buffer device 240x67 [5.847013] [drm:intel_prepare_page_flip], preparing flip with no unpin work? [5.852403] fb0: inteldrmfb frame buffer device [5.852404] drm: registered panic notifier [5.890468] acpi device:4a: registered as cooling_device9 [5.890772] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input8 [5.890932] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [5.891043] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 20.511015] EXT4-fs (sda2): re-mounted. Opts: (null) [ 20.861214] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro [ 20.887405] loop: module loaded [ 20.897977] w83627ehf: Found NCT6775F chip at 0xa00 [ 20.904046] fuse init (API version 7.17) [ 21.766490] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 22.076108] e1000e :00:19.0: irq 40 for MSI/MSI-X [ 22.128572] e1000e :00:19.0: irq 40 for MSI/MSI-X [ 22.129385] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 23.682466] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 23.682536] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 23.683348] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 27.733909] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input9 [ 28.748616] RPC: Registered
Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Hi, The 4gB module B of the 8gB set isnt working. (B is the one that caused a system crash the last time i used it. It is the same that gave me *no* errors when i tested it via memtest86+) after 4 hours i had a kernel panic: the notebook started a continuos 'beeep' and on the screen syslog-like messages appeared. I remember reading something about swapper and then at the bottom of the screen kernel panic. I was downloading a file via iceweasel and watching a movie via IRC/xdcc with the command: nc -v -v -n IP PORT|pv|mplayer -cache 50 - when suddently all crashed. the ramdisk was 1gB and the tmpfs mounts (are they ramdisks?) are: /run (376M) /run/lock (5M) /run/shm (752M) Now i have replaced the module B with the module A* and i'm going to do exactly the same things i was doing (a web dwl + an Irc stream opened bia mplayer with cache == 500M ) to see if it crash again. * (the other 4gB module of the 8gB set, A is the one that worked well last time i used it alone) ciao, Asdrubale -- 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/1734894.6062461351988376723.JavaMail.defaultUser@defaultHost
Bug#689420: Re: Re: Linux does not boot on Intel Core i7-3720QM Processor (2.60GHz Turbo)
On Fri, 2012-11-02 at 23:37 +0400, jaakov jaakov wrote: I turned on +x in /etc/init.d/acpi-support and did some final screenshots with acpi=off quiet elevator=noop with kernel 3.2.0-4. Then I removed, as you suggested, acpi=off, made screenshots and tried to produce a sys log. Photos Foto-0130, Foto-0131, Foto-0132 show the final stages of booting with acpi=off. Photos Foto-0133, Foto-0134, Foto-0135, Foto-0136, Foto-0137, Foto-0138 show some stages of the booting process without acpi=off. There is definitely some memory corruption, but it's not going to be easy to work out what caused it. For my future reference: Foto-0135 shows an assertion failure in slab's cache_alloc_refill(): /* * The slab was either on partial or free list so * there must be at least one object available for * allocation. */ BUG_ON(slabp-inuse = cachep-num); Foto-0136,0137 show a page fault in fpu_copy(). Foto-0138 maybe shows another page fault. Alas, it seems that SysRq did not produce the right effect, see the last line on Foto-0138. [...] Sorry, I was running a custom kernel (3.2.33-rc1) when I checked this. You used the right keys but this feature is disabled by default in Debian packaged kernels, due to security concerns. You can re-enable it by adding this line to /etc/sysctl.conf: kernel.sysrq = 1 But this will only produce interesting information if the kernel didn't already crash as shown in your photos 0135-0138. Can you tell me the model of laptop you are using? Can you also test Linux 3.6.6 when it is available (it should be in experimental in a few days). Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot signature.asc Description: This is a digitally signed message part
