Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver
Steinar Bang s...@dod.no writes:
Ben Hutchings b...@decadent.org.uk:
Please send a readable photograph of this text.
The problem occurred for the third time, and I couldn't find the camera,
so I'm typing in what's shown on the console.
This time it had happened while the macine was sitting unmanned and I
can't say it had anything to do with the screen saver, unless someone
unintentionally have moved the mouse.
I also note that it says invalid opcode. This machine has an Intel P4
CPU. Is it too old for the current kernels?
Console text follows:
[523708.506472] [ cut here ]---
[523708.506472] kernel BUG at
/build/build-linux_3.2.32-1-i386-Z3rOrf/linux-3.2.32/kernel/workqueue.c:1040!
This should not be a BUG IMHO, and it is in fact made easier debuggable
in newer kernels:
commit f5b2552b4ebbeadcadde1532d7bbd3f850719046
Author: Dan Carpenter dan.carpen...@oracle.com
Date: Fri Apr 13 22:06:58 2012 +0300
workqueue: change BUG_ON() to WARN_ON()
This BUG_ON() can be triggered if you call schedule_work() before
calling INIT_WORK(). It is a bug definitely, but it's nicer to just
print a stack trace and return.
Reported-by: Matt Renzelmann m...@cs.wisc.edu
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
Signed-off-by: Tejun Heo t...@kernel.org
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 5abf42f..66ec08d 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -1032,7 +1032,10 @@ static void __queue_work(unsigned int cpu, struct
workqueue_struct *wq,
cwq = get_cwq(gcwq-cpu, wq);
trace_workqueue_queue_work(cpu, cwq, work);
- BUG_ON(!list_empty(work-entry));
+ if (WARN_ON(!list_empty(work-entry))) {
+ spin_unlock_irqrestore(gcwq-lock, flags);
+ return;
+ }
cwq-nr_in_flight[cwq-work_color]++;
work_flags = work_color_to_flags(cwq-work_color);
Any chance that could be included in Debian wheezy kernels, although I
guess it does not meet stable requirements?
[523708.506472] invalid opcode: [#1] SMP
[523708.506472] Modules linked in: mperf speedstep_lib ip6table_filter
ip6_tables cpufreq_powersave iptable_filter ip_tables cpufreq_stats
cpufreq_conservative cpufreq_userspace ebtable_nat ebtables x_tables ppdev lp
bnep rfcomm bluetooth rfkill crc16 binfmt_misc fuse nfsd nfs nfs_acl
auth_rpcgss fscache lockd sunrpc loop snd_intel8x0 snd_ac97_codec i915
snd_pcm_oss snd_mixer_oss snd_pcm video snd_page_alloc drm_kms_helper
snd_seq_midi snd_seq_midi_event psmouse snd_rawmidi snd_seq snd_seq_device
snd_timer snd pcspkr drm i2c_i801 i2c_algo_bit soundcore ac97_bus i2c_core
iTCO_wdt serio_raw evdev parport_pc iTCO_vendor_support parport processor
thermal_sys rng_core button shpchp usbhid hid ext3 mbcache jbd dm_mod sg
sd_mod sr_mod cdrom crc_t10dif ata_generic floppy ata_piix libata uhci_hcd e
hci_hcd tg3 usbcore libphy scsi_mod usb_common [last unloaded:
scsi_wait_scan]
[523708.506472]
[523708.506472] Pid: 0, comm: swapper/0 Not tainted 3.2.0-4-686-pae #1 Debian
3.2.32-1 Hewlett-Packard HP d530 CMT(DZ036T)/085Ch
[523708.506472] EIP: 0060:[c10494b1] EFLAGS: 00010013 CPU: 0
[523708.506472] EIP is at __queue_work+0x193/0x1f4
[523708.506472] EAX: f739e56c EBX: f708c800 ECX: 0020 EDX: f739e568
[523708.506472] ESI: c14b5240 EDI: 0010 EBP: 0046 ESP: f5809f60
[523708.506472] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[523708.506472] Process swapper/0 (pid: 0, ti=f5808000 task=c13defe0
task.ti=c13d8000)
[523708.506472] Stack:
[523708.506472] f739e568 f085fe80 f085fe80 0010
f7398000 c1049555
[523708.506472] f739e568 f739e000 f0871400 f85abe17 c11e601f 0c00a511
8000 1930
[523708.506472] f739e568 0006 f739e028 0046 0046 f71147c0
f58068d4 0010
[523708.506472] Call Trace:
[523708.506472] [c1049555] ? queue_work_on+0x25/0x30
[523708.506472] [f85abe17] ? i8xx_irq_handler+0x6b/0x1dc [i915]
I took a quick look at this, and my guess is that i8xx_irq_handler
tries to queue an error event through i915_handle_error() here.
The error_work work_struct is initialized in intel_irq_init(), so I
cannot see how the error can happen unless something scribbles over it
at some point. Which may be what happens here? That would be a lot
easier to see if we could have queue_work fail with a warning instead.
Maybe add a few extra debugging tests to i915_handle_error() to see if
this is indeed what happens here? Completely untested of course:
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index 32e1bda..614f3f4 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -1414,6 +1414,19 @@ static void i915_report_and_clear_eir(struct drm_device
*dev)
}
}
+/* debugging helper only... */
+static bool safe_queue_work(struct workqueue_struct *wq, struct work_struct
*work)
+{
+
Processed: reassign 693227 to src:linux, forcibly merging 690886 693227
Processing commands for cont...@bugs.debian.org: reassign 693227 src:linux 3.2.32-1 Bug #693227 [debian-installer] missing driver for ISCI (Intel C600 SAS) (not iscsi!) Bug reassigned from package 'debian-installer' to 'src:linux'. Ignoring request to alter found versions of bug #693227 to the same values previously set Ignoring request to alter fixed versions of bug #693227 to the same values previously set Bug #693227 [src:linux] missing driver for ISCI (Intel C600 SAS) (not iscsi!) Marked as found in versions linux/3.2.32-1. forcemerge 690886 693227 Bug #690886 [src:linux] installation-reports: wheezy: isci.ko driver missing Bug #693227 [src:linux] missing driver for ISCI (Intel C600 SAS) (not iscsi!) Severity set to 'important' from 'critical' Marked as found in versions linux/3.2.23-1. Added tag(s) pending. Bug #690886 [src:linux] installation-reports: wheezy: isci.ko driver missing Marked as found in versions linux/3.2.32-1. Merged 690886 693227 thanks Stopping processing here. Please contact me if you need assistance. -- 690886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690886 693227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693227 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.135291106421375.transcr...@bugs.debian.org
Bug#693227: missing driver for ISCI (Intel C600 SAS) (not iscsi!)
forcemerge 690886 693227 # On Mittwoch, 14. November 2012, Ben Hutchings wrote: # This was already reported as #690886 and the fix is pending. 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/201211142024.39828.hol...@layer-acht.org
Processed: Re: Bug#693227: missing driver for ISCI (Intel C600 SAS) (not iscsi!)
Processing commands for cont...@bugs.debian.org: forcemerge 690886 693227 Bug #690886 [src:linux] installation-reports: wheezy: isci.ko driver missing Bug #693227 [src:linux] missing driver for ISCI (Intel C600 SAS) (not iscsi!) Bug #693227 [src:linux] missing driver for ISCI (Intel C600 SAS) (not iscsi!) Merged 690886 693227 # On Mittwoch, 14. November 2012, Ben Hutchings wrote: # This was already reported as #690886 and the fix is pending. thanks Stopping processing here. Please contact me if you need assistance. -- 690886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690886 693227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693227 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.135292108523825.transcr...@bugs.debian.org
Bug#692234: Intel DH77EB (H77): sporadic freeze and increased power consumption
Am 08.11.2012 16:55, schrieb Jonathan Nieder: Ingo wrote: I have now been running kernel 3.3.0-rc6-amd64 for 4 days. I did even try with different BIOS settings for IGD DVMT Memory especially with Maximum DVMT which according to the manual corresponds to 1.7GB. With this configuration I did have freezes few times a day with Wheezy stock kernel before. This is *fixed in kernel 3.3.0-rc6-amd64*. All is 100% stable. That's a comfort. Thanks for checking. Do you want me to continue with this test? No, please use whatever kernel is most convenient for now. Hopefully we will find some patch to test against 3.2.y soon. I have now extensively tested with kernel 3.4.4-1~experimental.1 from snapshots with all available BIOS settings for IGD DVMT Memory as: 128 MB 256 MB 512 MB Maximum DVMT (1.7 GB) All is 100% stable, s2ram works smoothly, ... BIOS setting is totally ignored and Wheezy always assigns 256 MB video RAM according to 'dmesg': agpgart-intel :00:00.0: AGP aperture is 256M @ 0xe000 This kernel also enables RC6p: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off I can't go with a newer kernel, because VirtualBox 4.1.18 does not support (and crashes) with kernels = 3.5. 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/50a3fe17.8070...@gmx.net
Bug#689420: A succeeding boot with errors
Upon inserting a delay I (unexpectedly pleasantly) got a succeeding boot. Three log files (/var/log/boot, /var/log/dmesg, /var/log/messages) are attached; dmesg shows diverse errors which were (luckily) not critical for this startup. logs.tar.bz2 Description: application/bzip
Bug#674243: Dell XPS 14z: Kernel crash when closing the lid
On 11/14/2012 12:10 AM, Mike Miller wrote:
fixed 674243 linux/3.2.32-1
thanks
Yes, it will continue to be built in to the kernel (see #663433).
I completely forgot that when I tested yesterday
Can you confirm that the crash is gone for you as well running the
3.2.32-1 Debian kernel?
The crash is indeed gone when running 3.2.32-1, I can see the error
message in the dmesg. I also tested 3.2.30-1, it crashes, in dmesg, I
was able to see that it successfully loaded acpiphp:
[0.838148] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[0.838277] acpiphp: Slot [1] registered
That fix ('PCI: acpiphp: check whether _ADR evaluation succeeded')
causes acpiphp to give up on some devices that it can't or shouldn't
handle. It doesn't necessarily stop acpiphp from being loaded, if
it's a module.
I guess what's happening here, is that acpiphp was handling devices it
should not, and it segfaulted when the system was suspending (but only
by closing the lid, suspending via the menu was working).
Btw, I am unable to load it as a module on 3.6.6, let me know if I
should try to pass an argument to bypass this error.
Sylvain
--
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/50a4581a.6000...@laposte.net
c150B.pilship.com Virus removed from message
The following viruses were repaired or dropped from the message (MID 4350153) 'Troj/ZipMal-AW', 'W32/MyDoom-O' And, Attachments dropped during repair. Actions taken: Message delivered Original Envelope Sender: From debian-kernel@lists.debian.org Thu Nov 15 12:52:12 2012 Message Headers: From: debian-kernel@lists.debian.org To: r...@sha.pilship.com Subject: Mail System Error - Returned Mail Date: Thu, 15 Nov 2012 10:51:48 +0600 Content-Type: multipart/mixed; boundary==_NextPart_000_0003_2DEF9C0F.4CE715F2 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600. X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600. X-AntiAbuse: This header was added to track abuse, please include it with any abuse report -- 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/20121115050520.c290...@bendel.debian.org
Processed: notfound 674243 in linux/3.2.32-1
Processing commands for cont...@bugs.debian.org: notfound 674243 linux/3.2.32-1 Bug #674243 [linux-2.6] linux-image-3.2.0-2-amd64: Kernel crash when closing the lid No longer marked as found in versions linux/3.2.32-1. thanks Stopping processing here. Please contact me if you need assistance. -- 674243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674243 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.13529576728190.transcr...@bugs.debian.org
Bug#674243: marked as done (linux-image-3.2.0-2-amd64: Kernel crash when closing the lid)
Your message dated Thu, 15 Nov 2012 05:34:10 + with message-id 1352957650.4867.59.ca...@deadeye.wl.decadent.org.uk and subject line Re: Bug#674243: Dell XPS 14z: Kernel crash when closing the lid has caused the Debian Bug report #674243, regarding linux-image-3.2.0-2-amd64: Kernel crash when closing the lid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 674243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.18-1 Severity: normal Tags: upstream Hello On my Dell XPS 14z laptop running SID up-to-date, I have a kernel oops whenever I close the lid. It's configured to suspend, but the system crashes. If I suspend from the menum it works fine. The bug seems to appeare in 3.1.0 because it's working with 3.0.0. I also tried the kernel from experimental, 3.3.0 and I have the same problem. As you can see in this thread, http://lists.debian.org/debian- user/2012/05/msg02078.html, if affects other laptop running similar hardware. I installed kerneloops, but I'm not sure it's working correctly because I can't find the trace in syslog anymore... kerneloops.org seems currently down as well. Here's the concerned part in syslog May 21 18:20:12 TichoLaptop laptop-mode: Warning: Configuration file /etc /laptop-mode/conf.d/board-specific/*.conf is not readable, skipping. May 21 18:20:12 TichoLaptop laptop-mode: Laptop mode May 21 18:20:12 TichoLaptop laptop-mode: enabled, May 21 18:20:12 TichoLaptop laptop-mode: not active [unchanged] May 21 18:20:15 TichoLaptop kernel: [ 1658.787327] BUG: unable to handle kernel paging request at c9001193396c May 21 18:20:15 TichoLaptop kernel: [ 1658.787415] IP: [812474b8] gen6_write_entry+0x4c/0x4f May 21 18:20:15 TichoLaptop kernel: [ 1658.787493] PGD 1cf023067 PUD 1cf024067 PMD 1c89ee067 PTE 0 May 21 18:20:15 TichoLaptop kernel: [ 1658.787570] Oops: 0002 [#1] SMP May 21 18:20:15 TichoLaptop kernel: [ 1658.787614] CPU 1 May 21 18:20:15 TichoLaptop kernel: [ 1658.787637] Modules linked in: aesni_intel cryptd aes_x86_64 aes_generic acpi_cpufreq mperf cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats bnep rfcomm fuse loop ixgb 8390 8139too mii uvcvideo videodev v4l2_compat_ioctl32 media snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb bluetooth crc16 arc4 sr_mod cdrom iwlwifi snd_hda_intel i915 snd_hda_codec mac80211 snd_hwdep drm_kms_helper cfg80211 drm snd_pcm xhci_hcd snd_page_alloc processor battery dell_wmi dell_laptop ehci_hcd usbcore rfkill rts_pstor(C) snd_timer i2c_algo_bit i2c_i801 dcdbas iTCO_wdt i2c_core iTCO_vendor_support snd ac psmouse sparse_keymap serio_raw power_supply button soundcore video atl1c usb_common wmi thermal_sys evdev pcspkr ext3 mbcache jbd sd_mod crc_t10dif ahci libahci libata scsi_mod May 21 18:20:15 TichoLaptop kernel: [ 1658.788707] May 21 18:20:15 TichoLaptop kernel: [ 1658.788732] Pid: 9739, comm: Xorg Tainted: G C 3.2.0-2-amd64 #1 Dell Inc. XPS L412Z/008DD8 May 21 18:20:15 TichoLaptop kernel: [ 1658.788847] RIP: 0010:[812474b8] [812474b8] gen6_write_entry+0x4c/0x4f May 21 18:20:15 TichoLaptop kernel: [ 1658.788951] RSP: 0018:8801c49b3aa0 EFLAGS: 00010202 May 21 18:20:15 TichoLaptop kernel: [ 1658.789017] RAX: 738b2015 RBX: 0500 RCX: 00010001 May 21 18:20:15 TichoLaptop kernel: [ 1658.789098] RDX: 0001738b2010 RSI: c9001193396c RDI: 0001738b2000 May 21 18:20:15 TichoLaptop kernel: [ 1658.789178] RBP: ce5b R08: R09: 00049e04 May 21 18:20:15 TichoLaptop kernel: [ 1658.789261] R10: c9001190 R11: 2d2d R12: May 21 18:20:15 TichoLaptop kernel: [ 1658.789328] R13: 00010001 R14: 8801b0ba2000 R15: 0001 May 21 18:20:15 TichoLaptop kernel: [ 1658.789388] FS: 7fbff0f5a880() GS:8801cfa4() knlGS: May 21 18:20:15 TichoLaptop kernel: [ 1658.789456] CS: 0010 DS: ES: CR0: 80050033 May 21 18:20:15 TichoLaptop kernel: [ 1658.789503] CR2: c9001193396c CR3: 0001a9c1c000 CR4: 000406e0 May 21 18:20:15 TichoLaptop kernel: [ 1658.789562] DR0: DR1: DR2: May 21 18:20:15 TichoLaptop kernel: [ 1658.789622] DR3: DR6: 0ff0 DR7: 0400 May 21 18:20:15 TichoLaptop kernel: [ 1658.789681] Process Xorg (pid: 9739, threadinfo 8801c49b2000, task 8801c644d6d0) May 21
