Processed: Re: xserver-xorg: xserver freeze after I close my laptop lid
Processing commands for cont...@bugs.debian.org: # Brice Goglin wrote: # # Can you try this patch ? # http://lists.freedesktop.org/archives/intel-gfx/2010-February/005902.html # # Patch refers to an upstream regression v2.6.31 - v2.6.32: # Closing and re-opening the lid does not reactivate the backlight # kernel.org is down so I can't check that it's the same bug, but it # looks similar enough for the moment. forwarded 570417 http://bugzilla.kernel.org/show_bug.cgi?id=14997 Bug #570417 [linux-2.6] xserver-xorg: xserver freeze after I close my laptop lid Set Bug forwarded-to-address to 'http://bugzilla.kernel.org/show_bug.cgi?id=14997'. End of message, stopping processing here. Please contact me if you need assistance. -- 570417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570417 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.13158074413133.transcr...@bugs.debian.org
Processed: Re: Bug#641244: [linux-image] kernel failure at boot but still works
Processing commands for cont...@bugs.debian.org: reassign 641244 src:linux-2.6 Bug #641244 [linux-image] [linux-image] kernel failure at boot but still works Warning: Unknown package 'linux-image' Bug reassigned from package 'linux-image' to 'src:linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. -- 641244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641244 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.131580991314422.transcr...@bugs.debian.org
Bug#586494: Dell PowerEdge 4200's don't work with 2.6.26
Hi, trouble daemon wrote: I am using a pair of Dell PowerEdg 4200's that have been working with debian since 2002 or so, 100% perfectly. [...] - 2.6.26 kernel that panics (latest unmodified debian kernel): http://pastebin.ca/1886636 - 2.6.18 kernel that works (latest unmodified debian kernel): http://pastebin.ca/1886641 pastebin.ca doesn't seem to exist any more, alas. [...] Ben Hutchings wrote: Another option that may be worth trying is 'noapic'. Wow, that worked just fine actually on 2.6.26 stock kernel. Thanks a lot! [...] f8924e770e048429ae13bfabe1ddad9bf1e64df7 is first bad commit commit f8924e770e048429ae13bfabe1ddad9bf1e64df7 Author: Alexey Starikovskiy astarikovs...@suse.de Date: Fri Apr 4 23:42:21 2008 +0400 x86: unify mp_bus_info [...] I have verified that checking out the patch just before this one works fine on the machines. Sorry we dropped the ball on this. Dan, any news (e.g., do later kernels do any better)? Alexey, any ideas for tracking this down? 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/20110912065150.GA7818@elie
Bug#586494: Dell PowerEdge 4200's don't work with 2.6.26
forwarded 586494 http://thread.gmane.org/gmane.linux.kernel/1000807/focus=1190336 quit Last message bounced since suse addresses don't work any more (oops). Let's just 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/20110912065953.GA6512@elie
Processed: Re: Dell PowerEdge 4200's don't work with 2.6.26
Processing commands for cont...@bugs.debian.org: forwarded 586494 http://thread.gmane.org/gmane.linux.kernel/1000807/focus=1190336 Bug #586494 [linux-2.6] linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26 Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel/1000807/focus=1190336'. quit Stopping processing here. Please contact me if you need assistance. -- 586494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494 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.131581080518505.transcr...@bugs.debian.org
Bug#586494: Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26
Hello, On Mon, Sep 12, 2011 at 2:56 AM, Jonathan Nieder jrnie...@gmail.com wrote: Sorry we dropped the ball on this. Dan, any news (e.g., do later kernels do any better)? Alexey, any ideas for tracking this down? No worries, not like these machines are useful for much beyond museum pieces any more ;) Sorry about the pastebin.ca though, I didn't realize that they were gone. As for later kernels, I have no idea tbh. Currently they seem to run flawless with noapic, so that is what I use when installing and running them. I do know that the Debian Squeeze installer chokes if I don't use noapic, however. If you are interested in some closure, I suppose I could take a shot at installing something a little more recent and see if I can get away with removing noapic though. Just let me know what kernel source (vanilla/deb sid/etc), version, or any particular .config options that you would like me to test, and I can see about pasting the console terminal output when running without noapic disabled. I won't use a pastebin this time, I promise ;) -- 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/cak82gmfduy5dm+fpkrjueep9w6bffgl4u0h-fp8b6bmmhah...@mail.gmail.com
Bug#598104: does not load i915 driver [Toshiba Satellite C650]
retitle 598104 Toshiba Satellite C650: DSDT is borked (acpi errors, slow boot,
wifi fails, etc)
reassign 598104 src:linux-2.6 2.6.32-23
fixed 598104 linux-2.6/2.6.36-1~experimental.1
tags 598104 + patch
quit
Hi,
Mirosław Zalewski wrote:
After testing Ubuntu kernel on Debian, I decided to compile my own
kernel from sources. At first I checked Debian patches, where I found
about Debian bug #596709 [1]. Then I learned about kernel bug #14679 [2] and
patch which solves it [3].
Could you test with 2.6.36 and 2.6.36~rc6 from http://snapshot.debian.org/
to confirm the fix, or apply the following three patches to a squeeze
kernel as described at [1]?
[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2
Thanks, and sorry for the slow response.
commit 1b6ea24923f1
Author: Lin Ming ming.m@intel.com
Date: Thu Apr 1 10:47:56 2010 +0800
ACPICA: Add detection of corrupted/replaced DSDT
commit 729df0f848daf2f17d02107199fa92efe909d995 upstream.
This change adds support to detect a DSDT that has been corrupted
and/or replaced from outside the OS (by firmware). This is
typically catastrophic for the system, but has been seen on
some machines.
https://bugzilla.kernel.org/show_bug.cgi?id=14679
Signed-off-by: Lin Ming ming.m@intel.com
Signed-off-by: Bob Moore robert.mo...@intel.com
Signed-off-by: Len Brown len.br...@intel.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
diff --git a/drivers/acpi/acpica/acglobal.h b/drivers/acpi/acpica/acglobal.h
index 29ba66d5a790..db509183876e 100644
--- a/drivers/acpi/acpica/acglobal.h
+++ b/drivers/acpi/acpica/acglobal.h
@@ -160,6 +160,11 @@ ACPI_EXTERN struct acpi_generic_address
acpi_gbl_xpm1a_enable;
ACPI_EXTERN struct acpi_generic_address acpi_gbl_xpm1b_status;
ACPI_EXTERN struct acpi_generic_address acpi_gbl_xpm1b_enable;
+/* DSDT information. Used to check for DSDT corruption */
+
+ACPI_EXTERN struct acpi_table_desc *acpi_gbl_DSDT;
+ACPI_EXTERN struct acpi_table_header acpi_gbl_original_dsdt_header;
+
/*
* Handle both ACPI 1.0 and ACPI 2.0 Integer widths. The integer width is
* determined by the revision of the DSDT: If the DSDT revision is less than
diff --git a/drivers/acpi/acpica/actables.h b/drivers/acpi/acpica/actables.h
index 01c76b8ea7ba..37bcb67a61e4 100644
--- a/drivers/acpi/acpica/actables.h
+++ b/drivers/acpi/acpica/actables.h
@@ -107,6 +107,8 @@ u8 acpi_tb_checksum(u8 *buffer, u32 length);
acpi_status
acpi_tb_verify_checksum(struct acpi_table_header *table, u32 length);
+void acpi_tb_check_dsdt_header(void);
+
void
acpi_tb_install_table(acpi_physical_address address,
char *signature, u32 table_index);
diff --git a/drivers/acpi/acpica/psxface.c b/drivers/acpi/acpica/psxface.c
index dd9731c29a79..6133894936be 100644
--- a/drivers/acpi/acpica/psxface.c
+++ b/drivers/acpi/acpica/psxface.c
@@ -220,6 +220,10 @@ acpi_status acpi_ps_execute_method(struct
acpi_evaluate_info *info)
ACPI_FUNCTION_TRACE(ps_execute_method);
+ /* Quick validation of DSDT header */
+
+ acpi_tb_check_dsdt_header();
+
/* Validate the Info and method Node */
if (!info || !info-resolved_node) {
diff --git a/drivers/acpi/acpica/tbutils.c b/drivers/acpi/acpica/tbutils.c
index 1f15497f00d1..2d860ab8990c 100644
--- a/drivers/acpi/acpica/tbutils.c
+++ b/drivers/acpi/acpica/tbutils.c
@@ -349,6 +349,44 @@ u8 acpi_tb_checksum(u8 *buffer, u32 length)
/***
*
+ * FUNCTION:acpi_tb_check_dsdt_header
+ *
+ * PARAMETERS: None
+ *
+ * RETURN: None
+ *
+ * DESCRIPTION: Quick compare to check validity of the DSDT. This will detect
+ * if the DSDT has been replaced from outside the OS and/or if
+ * the DSDT header has been corrupted.
+ *
+
**/
+
+void acpi_tb_check_dsdt_header(void)
+{
+
+ /* Compare original length and checksum to current values */
+
+ if (acpi_gbl_original_dsdt_header.length !=
+ acpi_gbl_DSDT-pointer-length
+ || acpi_gbl_original_dsdt_header.checksum !=
+ acpi_gbl_DSDT-pointer-checksum) {
+ ACPI_ERROR((AE_INFO,
+ The DSDT has been corrupted or replaced - old, new
headers below));
+ acpi_tb_print_table_header(0, acpi_gbl_original_dsdt_header);
+ acpi_tb_print_table_header(acpi_gbl_DSDT-address,
+ acpi_gbl_DSDT-pointer);
+
+ /* Disable further error messages */
+
+ acpi_gbl_original_dsdt_header.length =
+ acpi_gbl_DSDT-pointer-length;
+ acpi_gbl_original_dsdt_header.checksum =
+ acpi_gbl_DSDT-pointer-checksum;
+ }
+}
+
Processed: Re: does not load i915 driver [Toshiba Satellite C650]
Processing commands for cont...@bugs.debian.org: retitle 598104 Toshiba Satellite C650: DSDT is borked (acpi errors, slow boot, wifi fails, etc) Bug #598104 [linux-2.6] xserver-xorg-video-intel: does not load i915 driver [Toshiba Satellite C650] Changed Bug title to 'Toshiba Satellite C650: DSDT is borked (acpi errors, slow boot, wifi fails, etc)' from 'xserver-xorg-video-intel: does not load i915 driver [Toshiba Satellite C650]' reassign 598104 src:linux-2.6 2.6.32-23 Bug #598104 [linux-2.6] Toshiba Satellite C650: DSDT is borked (acpi errors, slow boot, wifi fails, etc) Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions xserver-xorg-video-intel/2:2.9.1-4. Bug #598104 [src:linux-2.6] Toshiba Satellite C650: DSDT is borked (acpi errors, slow boot, wifi fails, etc) Bug Marked as found in versions linux-2.6/2.6.32-23. fixed 598104 linux-2.6/2.6.36-1~experimental.1 Bug #598104 [src:linux-2.6] Toshiba Satellite C650: DSDT is borked (acpi errors, slow boot, wifi fails, etc) Bug Marked as fixed in versions linux-2.6/2.6.36-1~experimental.1. tags 598104 + patch Bug #598104 [src:linux-2.6] Toshiba Satellite C650: DSDT is borked (acpi errors, slow boot, wifi fails, etc) Added tag(s) patch. quit Stopping processing here. Please contact me if you need assistance. -- 598104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598104 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.131581248826610.transcr...@bugs.debian.org
Bug#605318: radeon: horizontal interference lines on screen
found 605318 linux-2.6/2.6.32-35 quit Hi, Matt Pandina wrote: I too was experiencing horizontal lines (so bad that I could barely see the screen!) [...] Finally I managed to see through the horizontal lines enough to go to: System Preferences Monitors and told it to rotate the screen upside-down. The lines were still there, but they stopped after I switched the rotation back to normal. Thanks. Mike, do you experience the same? Both: - can you describe the horizontal lines more? Are they one pixel tall or are they thicker? How quickly do they flash? Are they always there or only sometimes? Do they move? Do they cover the screen or only part of it? Can you take a photo? - do you have firmware-linux-nonfree installed? - can you reproduce this with a kernel from sid or experimental? (To install one to try, the only additional dependencies that should be needed are recent linux-base and initramfs-tools.) - If so, please report this upstream at bugs.freedesktop.org, product DRI, component DRM/Radeon and let us know the bug number so we can track it. (Don't worry about duplicating each other --- it's nicer to have the information for each machine separately and mark one as a dup if appropriate later anyway.) - otherwise, we can try to find the fix and backport it; if you have time to find the first working verison at snapshot.debian.org by the bisection method, that would be helpful. Sorry for the slow response, 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/20110912074849.GA25821@elie
Processed: Re: radeon: horizontal interference lines on screen
Processing commands for cont...@bugs.debian.org: found 605318 linux-2.6/2.6.32-35 Bug #605318 [src:linux-2.6] radeon: horizontal interference lines on screen Bug Marked as found in versions linux-2.6/2.6.32-35. quit Stopping processing here. Please contact me if you need assistance. -- 605318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605318 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.1315813747397.transcr...@bugs.debian.org
Bug#592497: linux-image-2.6.32-bpo.5-686-bigmem: Kernel panic in put_cred_rcu()
Thanks. FWIW the kernels installed in the past are listed in /var/log/dpkg.log*. Yes, I actually did install squeeze's 2.6.32-35 but I didn't use it immediately, I kept using lenny-backport 2.6.32 by mistake. I made a short test with squeeze's 2.6.32-35 and it crashed 2 hours later. Unfortunately kdump didn't work and switched to squeeze-backport 2.6.38-bpo.2-686-bigmem. There is no way I can tell if the bug is similar to the one we had with lenny but 2.6.38 seems more stable on our server so we will keep using version for now. Jo. -- 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/d7bde23a-c062-4817-8d07-ef0287e8e...@gmail.com
Bug#613074: xserver-xorg-input-synaptics: Touchpad left and right physical buttons send only button2 events instead of left and right clicks as expected
found 613074 linux-2.6/2.6.32-30 quit Cyril Brulebois wrote: Tayroni Francisco de Alencar tayroni.al...@gmail.com (13/02/2011): and the output of evtest /dev/input/event7 (on tty1) Input driver version is 1.0.0 Input device ID: bus 0x11 vendor 0x2 product 0x8 version 0x7321 Input device name: AlpsPS/2 ALPS GlidePoint [...] Event: time 1297647718.798783, type 1 (Key), code 272 (LeftBtn), value 1 Event: time 1297647718.798787, type 1 (Key), code 273 (RightBtn), value 1 Event: time 1297647718.798790, -- Report Sync Event: time 1297647718.957825, type 1 (Key), code 272 (LeftBtn), value 0 Event: time 1297647718.957829, type 1 (Key), code 273 (RightBtn), value 0 Event: time 1297647718.957831, -- Report Sync [... snip the above repeated three more times ...] I've pressed two times the left physical button and then, two times the right button. Thanks, Tayroni. As you can see, LeftBtn+RightBtn is sent every time, so that's not a bug on the X side, rather on the kernel side. Reassigning there. Thanks for a clear report. Basic questions: - has this always acted this way since you started using Debian, or did the problem begin with an upgrade (i.e., is it a regression)? - can you reproduce this with the kernel from sid or experimental? (It should be possible to test on a squeeze system by just installing recent versions of the linux-image-foo, linux-base, and initramfs-tools packages.) If so, we can report this upstream, and if not, we can try to find the fix and backport it. - please attach output of /usr/share/bug/linux-image-$(uname -r)/script 31 so we can get to know the hardware and drivers involved. - any hunches, workarounds, or other weird symptoms? Sorry for the delay, 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/20110912080445.GA25904@elie
Processed: Re: xserver-xorg-input-synaptics: Touchpad left and right physical buttons send only button2 events instead of left and right clicks as expected
Processing commands for cont...@bugs.debian.org: found 613074 linux-2.6/2.6.32-30 Bug #613074 [src:linux-2.6] xserver-xorg-input-synaptics: Touchpad left and right physical buttons send only button2 events instead of left and right clicks as expected Bug Marked as found in versions linux-2.6/2.6.32-30. quit Stopping processing here. Please contact me if you need assistance. -- 613074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613074 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.13158147064996.transcr...@bugs.debian.org
Bug#627594: access to SUBSYSTEM=power_supply sysfs nodes causes a remove/add/change events flood
Hi Marco, Marco d'Itri wrote: [Subject: access to SUBSYSTEM=power_supply sysfs nodes causes a remove/add/change events flood] This has been happening for a few months and makes upowerd unusable since the events flood make it use too much CPU and disk bandwidth. How to reproduce: [...] Alas, I'm not able to reproduce it with v3.1-rc5. What kernel version do you use? Does this still happen? Could you attach output from the /usr/share/bug/$(uname -r)/script 31 command? 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/20110912082036.GA25971@elie
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
Hi Anton, Anton Ivanov wrote: When an export is exported and mounted via autofs using BOTH NFSv3 and NFSv4 the NFSv4 one deadlocks. We ought to have put this in the hands of upstream about a year ago. Better late than never, so I will echo Ben: Ben Hutchings wrote: OK. Next, can you test whether the kernel version in unstable (linux-image-2.6.32-4-* version 2.6.32-10) or testing (linux-image-2.6.32-3-* version 2.6.32-9) also has this bug? Can you reproduce this with a recent (3.x) kernel? (If so, upstream might care, and if not, we can try to find the fix and backport it.) Thanks for an interesting report, and sorry to have left it hanging. 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/20110912090624.GA14120@elie
Bug#619326: upgrade-reports: x-server not working any longer after updating from 6.0.0 to 6.0.1
Hi, Mister_Ka wrote: After updating from a working 6.0.0 standard version to 6.0.1 booting ends in a total black screen just illuminated by its backlight. Could you provide (1) output from /usr/share/bug/linux-image-$(uname -r)/script 31 (which includes basic information about your hardware) (2) output from running dmesg after booting with a kernel that triggers this problem (you can get it over ssh, for example) ? Thanks for reporting, 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/20110912092410.GA21743@elie
Bug#627594: access to SUBSYSTEM=power_supply sysfs nodes causes a remove/add/change events flood
On Sep 12, Jonathan Nieder jrnie...@gmail.com wrote: Alas, I'm not able to reproduce it with v3.1-rc5. What kernel version do you use? Does this still happen? Could you attach output from the /usr/share/bug/$(uname -r)/script 31 command? I can still reproduce the bug with 3.0.0. If I do not kill upowerd at startup, the system uses too much CPU. ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-3) ) #1 SMP Sun Jul 24 15:06:18 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-amd64 root=UUID=8e36f28b-e47b-4dd5-9148-d8a9bad0e55a ro ** Not tainted ** Kernel log: [2393718.789568] pci :03:01.1: restoring config space at offset 0xf (was 0x4020200, writing 0x4020203) [2393718.789588] pci :03:01.1: restoring config space at offset 0x3 (was 0x80, writing 0x804010) [2393718.789594] pci :03:01.1: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [2393718.789613] sdhci-pci :03:01.2: restoring config space at offset 0xf (was 0x300, writing 0x30b) [2393718.789631] sdhci-pci :03:01.2: restoring config space at offset 0x4 (was 0x0, writing 0xf68ff600) [2393718.789636] sdhci-pci :03:01.2: restoring config space at offset 0x3 (was 0x80, writing 0x804010) [2393718.789642] sdhci-pci :03:01.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [2393718.789799] PM: early resume of devices complete after 1.508 msecs [2393718.789864] i915 :00:02.0: setting latency timer to 64 [2393718.789904] pci:00: wake-up capability disabled by ACPI [2393718.789908] e1000e :00:19.0: PME# disabled [2393718.789985] e1000e :00:19.0: irq 43 for MSI/MSI-X [2393718.792136] uhci_hcd :00:1a.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [2393718.792141] uhci_hcd :00:1a.0: setting latency timer to 64 [2393718.792167] usb usb3: root hub lost power or was reset [2393718.792179] uhci_hcd :00:1a.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [2393718.792184] uhci_hcd :00:1a.1: setting latency timer to 64 [2393718.792209] usb usb4: root hub lost power or was reset [2393718.792220] uhci_hcd :00:1a.2: PCI INT C - GSI 22 (level, low) - IRQ 22 [2393718.792226] uhci_hcd :00:1a.2: setting latency timer to 64 [2393718.792249] usb usb5: root hub lost power or was reset [2393718.792262] ehci_hcd :00:1a.7: PCI INT C - GSI 22 (level, low) - IRQ 22 [2393718.792268] ehci_hcd :00:1a.7: setting latency timer to 64 [2393718.792309] HDA Intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [2393718.792321] HDA Intel :00:1b.0: setting latency timer to 64 [2393718.792359] HDA Intel :00:1b.0: irq 47 for MSI/MSI-X [2393718.792401] uhci_hcd :00:1d.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [2393718.792406] uhci_hcd :00:1d.0: setting latency timer to 64 [2393718.792432] usb usb6: root hub lost power or was reset [2393718.792443] uhci_hcd :00:1d.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [2393718.792448] uhci_hcd :00:1d.1: setting latency timer to 64 [2393718.792473] usb usb7: root hub lost power or was reset [2393718.792483] uhci_hcd :00:1d.2: PCI INT C - GSI 22 (level, low) - IRQ 22 [2393718.792489] uhci_hcd :00:1d.2: setting latency timer to 64 [2393718.792512] usb usb8: root hub lost power or was reset [2393718.792525] ehci_hcd :00:1d.7: PCI INT A - GSI 20 (level, low) - IRQ 20 [2393718.792531] ehci_hcd :00:1d.7: setting latency timer to 64 [2393718.792569] pci :00:1e.0: setting latency timer to 64 [2393718.792582] ahci :00:1f.2: setting latency timer to 64 [2393718.792658] pci :03:01.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [2393718.792667] sdhci-pci :03:01.2: PCI INT C - GSI 18 (level, low) - IRQ 18 [2393718.794061] sd 0:0:0:0: [sda] Starting disk [2393718.859008] dell_wmi: Received unknown WMI event (0x11) [2393719.003731] serial 00:09: activated [2393719.013122] Extended CMOS year: 2000 [2393719.120077] ata6: SATA link down (SStatus 0 SControl 300) [2393719.128054] ata5: SATA link down (SStatus 0 SControl 300) [2393719.156067] usb 1-6: reset high speed USB device number 3 using ehci_hcd [2393719.284070] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [2393719.297471] ata2.00: configured for UDMA/100 [2393719.400063] usb 5-1: reset full speed USB device number 2 using uhci_hcd [2393719.473216] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input138 [2393719.568911] usbfs 5-1:0.1: no reset_resume for driver usbfs? [2393719.969340] dell_wmi: Received unknown WMI event (0x11) [2393720.428234] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2393720.430375] ata1.00: configured for UDMA/100 [2393720.532682] PM: resume of devices complete after 1742.846 msecs [2393720.532909] PM: Finishing wakeup. [2393720.532911] Restarting tasks ... [2393720.538604] wlan0: deauthenticated from 00:18:f3:6b:3b:6c (Reason: 7) [2393720.543924] done. [2393720.543934]
Bug#628214: linux-image-2.6.32-5-amd64: Samba or prftpd freeze server
Hi Matthias, Ben Hutchings wrote: On Sat, 2011-05-28 at 12:23 +0200, Matthias Steup wrote: When trying to copy a bigger file (16 MB) to the linux-server form a windows client via samba or ftp the linux system freezes in a way that you can't ping it from any client on the the network. [...] Did this also happen when using earlier Debian kernel versions based on 2.6.32? Do any messages appear in the kernel log around this time? Ping. I assume this is reproducible. Is this a new installation, is it a longstanding bug, or did the bug appear on upgrade? Could you attach dmesg output after triggering it? -- 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/20110912092925.GA21776@elie
Processed: another dup (Re: linux-image-2.6.32-5-686-bigmem: Squeeze1 kernel update unable to handle kernel paging request...)
Processing commands for cont...@bugs.debian.org: forcemerge 640966 641025 Bug#640966: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641025: linux-image-2.6.32-5-686-bigmem: Squeeze1 kernel update unable to handle kernel paging request... Bug#640973: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641018: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641034: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641040: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641121: gnome-system-monitor and chrome fail while using linux-image-2.6.32-5-686 from security.debian (update from 09.09.11). It looks like this bug has fixed https://lkml.org/lkml/2011/3/27/17 Bug#641171: linux-headers-2.6.32-5-all: kernel oops with google-chrome-unstable Forcibly Merged 640966 640973 641018 641025 641034 641040 641121 641171. End of message, stopping processing here. Please contact me if you need assistance. -- 641018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641018 641040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641040 641025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641025 640973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640973 641121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641121 641034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641034 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 641171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641171 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.131581766218772.transcr...@bugs.debian.org
Bug#603670: marked as done (early kernel panic as node under kvm (div-by-zero in pvclock_tsc_khz))
Your message dated Mon, 12 Sep 2011 04:18:57 -0500 with message-id 20110912091857.GA21705@elie and subject line Re: early kernel panic as node under kvm (div-by-zero in pvclock_tsc_khz) has caused the Debian Bug report #603670, regarding early kernel panic as node under kvm (div-by-zero in pvclock_tsc_khz) 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.) -- 603670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-27 Severity: important Found: linux-image-2.6.30-2-amd64/2.6.30-8squeeze1 Found: linux-image-2.6.36-trunk-amd64/2.6.36-1~experimental.1 Hi, I get an early kernel panic when i try to run testing/unstable/experimental kernels in a vm under kvm. The physical host runs 2.6.32-5-amd64, and uses qemu-kvm/0.12.5+dfsg-4 with libvirt 0.8.3-4. The stable kernel does not panic: linux-image-2.6.26-2-amd64 2.6.26-25 Example log for 2.6.32-5-amd64 (experimental has similar backtrace); the panic is caused by a div-by-zero in pvclock_tsc_khz here (v2.6.36 source): http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=arch/x86/kernel/pvclock.c;h=239427ca02af05f8671aacaf9820aa298e94bff1;hb=f6f94e2ab1b33f0082ac22d71f66385a60d8157f#l113 [0.00] kvm-clock: cpu 0, msr 0:14f1701, boot clock PANIC: early exception 00 rip 10:8102cd63 error 0 cr2 0 [0.00] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 [0.00] Call Trace: [0.00] [814f319e] ? early_idt_handler+0x5e/0x71 [0.00] [8102cd63] ? pvclock_tsc_khz+0x13/0x2a [0.00] [81503f17] ? kvmclock_init+0x133/0x18c [0.00] [8150ccbe] ? parse_crashkernel+0x46/0x23f [0.00] [814f75f8] ? setup_arch+0x8f6/0x9cb [0.00] [811f6a9f] ? extract_entropy+0x6a/0x125 [0.00] [814f3140] ? early_idt_handler+0x0/0x71 [0.00] [814f39d0] ? start_kernel+0xdb/0x3e8 [0.00] [814f33b7] ? x86_64_start_kernel+0xf9/0x106 [0.00] RIP pvclock_tsc_khz+0x13/0x2a Regards, Stefan Loading Linux 2.6.32-5-amd64 ... Loading initial ramdisk ... [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-27) (m...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 14:18:21 UTC 2010 [0.00] Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/vg0-stefan ro single console=tty0 console=ttyS0,38400 earlyprintk=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3fffb000 (usable) [0.00] BIOS-e820: 3fffb000 - 4000 (reserved) [0.00] BIOS-e820: fffbc000 - 0001 (reserved) [0.00] bootconsole [earlyser0] enabled [0.00] DMI 2.4 present. [0.00] last_pfn = 0x3fffb max_arch_pfn = 0x4 [0.00] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106 [0.00] init_memory_mapping: -3fffb000 [0.00] RAMDISK: 2f87f000 - 3003c109 [0.00] ACPI: RSDP 000f8830 00014 (v00 BOCHS ) [0.00] ACPI: RSDT 3fffde30 00034 (v01 BOCHS BXPCRSDT 0001 BXPC 0001) [0.00] ACPI: FACP 3e70 00074 (v01 BOCHS BXPCFACP 0001 BXPC 0001) [0.00] ACPI: DSDT 3fffdfd0 01E22 (v01 BXPC BXDSDT 0001 INTL 20090123) [0.00] ACPI: FACS 3e00 00040 [0.00] ACPI: SSDT 3fffdf90 00037 (v01 BOCHS BXPCSSDT 0001 BXPC 0001) [0.00] ACPI: APIC 3fffdeb0 00072 (v01 BOCHS BXPCAPIC 0001 BXPC 0001) [0.00] ACPI: HPET 3fffde70 00038 (v01 BOCHS BXPCHPET 0001 BXPC 0001) [0.00] No NUMA configuration found [0.00] Faking a node at -3fffb000 [0.00] Bootmem setup node 0 -3fffb000 [0.00] NODE_DATA [9000 - 00010fff] [0.00] bootmap [00011000 - 00018fff] pages 8 [0.00] (7
Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use
On 12/09/11 10:07, Jonathan Nieder wrote: Hi Anton, Anton Ivanov wrote: When an export is exported and mounted via autofs using BOTH NFSv3 and NFSv4 the NFSv4 one deadlocks. We ought to have put this in the hands of upstream about a year ago. Better late than never, so I will echo Ben: Ben Hutchings wrote: OK. Next, can you test whether the kernel version in unstable (linux-image-2.6.32-4-* version 2.6.32-10) or testing (linux-image-2.6.32-3-* version 2.6.32-9) also has this bug? Can you reproduce this with a recent (3.x) kernel? (If so, upstream might care, and if not, we can try to find the fix and backport it.) I will try to find some time to retest with current and 3.x this week. I do not recall seeing it on 2.6.32 lately. I have, however, changed back to v3 a lot of autofs entries so this is not indicative. Thanks for an interesting report, and sorry to have left it hanging. No worries. Jonathan -- Humans are allergic to change. They love to say, We've always done it this way. I try to fight that. That's why I have a clock on my wall that runs counter-clockwise. -- R.A. Grace Hopper A. R. Ivanov E-mail: anton.iva...@kot-begemot.co.uk -- 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/4e6dd52a.9000...@kot-begemot.co.uk
Processed: Re: Bug#641151: sl-modem-source: Fails to compile on Linux 3.0 kernels
Processing commands for cont...@bugs.debian.org: reassign 641151 linux-2.6 Bug #641151 [sl-modem-source] sl-modem-source: Fails to compile on Linux 3.0 kernels Bug reassigned from package 'sl-modem-source' to 'linux-2.6'. Bug No longer marked as found in versions sl-modem/2.9.11~20110321-3. quit Stopping processing here. Please contact me if you need assistance. -- 641151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641151 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.13158287559549.transcr...@bugs.debian.org
Bug#641151: Processed: Re: Bug#641151: sl-modem-source: Fails to compile on Linux 3.0 kernels
The correct way to invoke kbuild is: make -C /lib/modules/$(uname -r)/build M=$(PWD) Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#641151: Processed: Re: Bug#641151: sl-modem-source: Fails to compile on Linux 3.0 kernels
On Mon, 2011-09-12 at 13:07 +0100, Ben Hutchings wrote: The correct way to invoke kbuild is: make -C /lib/modules/$(uname -r)/build M=$(PWD) Without looking at the source, I suspect that the makefile tries to distinguish between 2.6.x (where the above works) and 2.4.x (where it doesn't). And 3.0 is wrongly being treated as the latter. You should remove the version test and make it always use kbuild, since 2.4.x is obsolete. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#641288: linux-image-2.6.32-5-686: Can not read appendable cdroms/dvds.
Package: linux-2.6 Version: 2.6.32-35squeeze2 Severity: normal Hi. This bug continues bug 583949 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583949 I open a new bug report, as suggested there. appendable cdroms/dvds can not be read. Checked in 2.6.32-35squeeze2 and 2.6.39-bpo.2-686-pae (i686). It is an external usb drive, so I tried to plug it in a different hole. Last message is when I decided to put there a blank dvd. Thanks. [ 16.314596] ip_tables: (C) 2000-2006 Netfilter Core Team [ 16.767449] cdrom: This disc doesn't have any tracks I recognize! [ 19.916303] sr 4:0:0:0: [sr1] Unhandled sense code [ 19.916309] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 19.916316] sr 4:0:0:0: [sr1] Sense Key : Blank Check [current] [ 19.916324] Info fld=0x0 [ 19.916327] sr 4:0:0:0: [sr1] vendor ASC=0xab ASCQ=0x80ASC=0xab vendor ASCQ=0x80 [ 19.916339] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 [ 19.916354] end_request: critical target error, dev sr1, sector 0 [ 19.922336] Buffer I/O error on device sr1, logical block 0 [ 19.928610] Buffer I/O error on device sr1, logical block 1 [ 21.084109] sr 4:0:0:0: [sr1] Unhandled sense code [ 21.084115] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 21.084122] sr 4:0:0:0: [sr1] Sense Key : Blank Check [current] [ 21.084130] Info fld=0x0 [ 21.084133] sr 4:0:0:0: [sr1] vendor ASC=0xab ASCQ=0x80ASC=0xab vendor ASCQ=0x80 [ 21.084145] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 [ 21.084160] end_request: critical target error, dev sr1, sector 0 [ 21.090334] Buffer I/O error on device sr1, logical block 0 [ 21.096553] Buffer I/O error on device sr1, logical block 1 [ 22.262538] sr 4:0:0:0: [sr1] Unhandled sense code [ 22.262545] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 22.262551] sr 4:0:0:0: [sr1] Sense Key : Blank Check [current] [ 22.262559] Info fld=0x2 [ 22.262563] sr 4:0:0:0: [sr1] vendor ASC=0xab ASCQ=0x80ASC=0xab vendor ASCQ=0x80 [ 22.262575] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00 [ 22.262592] end_request: critical target error, dev sr1, sector 8 [ 22.268897] Buffer I/O error on device sr1, logical block 2 [ 22.275134] Buffer I/O error on device sr1, logical block 3 [ 23.441082] sr 4:0:0:0: [sr1] Unhandled sense code [ 23.441087] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 23.441092] sr 4:0:0:0: [sr1] Sense Key : Blank Check [current] [ 23.441098] Info fld=0x2 [ 23.441101] sr 4:0:0:0: [sr1] vendor ASC=0xab ASCQ=0x80ASC=0xab vendor ASCQ=0x80 [ 23.441110] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00 [ 23.441122] end_request: critical target error, dev sr1, sector 8 [ 23.447200] Buffer I/O error on device sr1, logical block 2 [ 23.453489] Buffer I/O error on device sr1, logical block 3 [ 25.148170] cdrom: This disc doesn't have any tracks I recognize! [ 27.948827] sr 4:0:0:0: [sr1] Unhandled sense code [ 27.948832] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 27.948837] sr 4:0:0:0: [sr1] Sense Key : Blank Check [current] [ 27.948844] Info fld=0x0 [ 27.948847] sr 4:0:0:0: [sr1] vendor ASC=0xab ASCQ=0x80ASC=0xab vendor ASCQ=0x80 [ 27.948856] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 [ 27.948868] end_request: critical target error, dev sr1, sector 0 [ 27.953782] Buffer I/O error on device sr1, logical block 0 [ 27.958870] Buffer I/O error on device sr1, logical block 1 [ 29.127272] sr 4:0:0:0: [sr1] Unhandled sense code [ 29.127277] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 29.127282] sr 4:0:0:0: [sr1] Sense Key : Blank Check [current] [ 29.127289] Info fld=0x0 [ 29.127291] sr 4:0:0:0: [sr1] vendor ASC=0xab ASCQ=0x80ASC=0xab vendor ASCQ=0x80 [ 29.127301] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 [ 29.127313] end_request: critical target error, dev sr1, sector 0 [ 29.132203] Buffer I/O error on device sr1, logical block 0 [ 29.137164] Buffer I/O error on device sr1, logical block 1 [ 30.305684] sr 4:0:0:0: [sr1] Unhandled sense code [ 30.305689] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 30.305694] sr 4:0:0:0: [sr1] Sense Key : Blank Check [current] [ 30.305700] Info fld=0x2 [ 30.305703] sr 4:0:0:0: [sr1] vendor ASC=0xab ASCQ=0x80ASC=0xab vendor ASCQ=0x80 [ 30.305712] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00 [ 30.305725] end_request: critical target error, dev sr1, sector 8 [ 30.310558] Buffer I/O error on device sr1, logical block 2 [ 30.315610] Buffer I/O error on device sr1, logical block 3 [ 31.473360] sr 4:0:0:0: [sr1] Unhandled sense code [ 31.473365] sr 4:0:0:0: [sr1] Result: hostbyte=invalid driverbyte=DRIVER_SENSE [ 31.473370] sr 4:0:0:0: [sr1] Sense Key : Blank Check
Processed: reassign 641151 to sl-modem
Processing commands for cont...@bugs.debian.org: reassign 641151 sl-modem 2.9.11~20110321-3 Bug #641151 [linux-2.6] sl-modem-source: Fails to compile on Linux 3.0 kernels Bug reassigned from package 'linux-2.6' to 'sl-modem'. Bug #641151 [sl-modem] sl-modem-source: Fails to compile on Linux 3.0 kernels There is no source info for the package 'sl-modem' at version '2.9.11~20110321-3' with architecture '' Unable to make a source version for version '2.9.11~20110321-3' Bug Marked as found in versions 2.9.11~20110321-3. thanks Stopping processing here. Please contact me if you need assistance. -- 641151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641151 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.131583177022726.transcr...@bugs.debian.org
Bug#640672: moving files to arch specific include breaks compilations with -m32
The same is obviously true the other way around: on a 32bit x86 userspace it was possible to compile 64bit binaries using -m64. Now this is broken in exactly the same way as it is for -m32 on 64bits. -- 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/4e6e05f5.6080...@msgid.tls.msk.ru
Processed: severity of 637419 is normal
Processing commands for cont...@bugs.debian.org: severity 637419 normal Bug #637419 [linux-libc-dev] gnat-4.6 ftbfs with eglibc-2.13-16 Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 637419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637419 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.131583577411203.transcr...@bugs.debian.org
Processed: Re: Bug#640974: After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed
Processing commands for cont...@bugs.debian.org: reassign 640974 linux-image-2.6.32-5-amd64 Bug #640974 [popularity-contest] After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed Bug reassigned from package 'popularity-contest' to 'linux-image-2.6.32-5-amd64'. Bug No longer marked as found in versions popularity-contest/1.49. quit Stopping processing here. Please contact me if you need assistance. -- 640974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640974 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.13158413436625.transcr...@bugs.debian.org
Bug#640974: After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed
Hi Alexander, Alexander Fortin wrote: This I what I get when I run /etc/cron.daily/popularity-contest: Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] Oops: [#5] SMP Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] last sysfs file: /sys/devices/pci:00/:00:01.1/host0/target0:0:1/0:0:1:0/block/sdb/stat [...] Thanks for reporting it. Basic questions: - is this reproducible? - did it always happen, or did it only start happening after a kernel upgrade, and in the latter case, what were the last working and first broken versions? (The history of installed kernel image packages is in /var/log/dpkg.log*.) - Could you attach the output of /usr/share/bug/linux-image-$(uname -r)/script 31 (which lets us get to know your hardware and drivers), plus the output of dmesg after triggering the bug (which includes a fuller trace)? 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/20110912154011.GA26867@elie
Bug#641008: Acknowledgement (linux-image-2.6.32-5-amd64: X11 mouse dropping left on text console when switching VTs; doesn't go away )
Image (link below) of graphical mouse pointer left behind whenever you Ctrl-Alt-Shift-F# to text VTs while Xorg is running with an external screen connected on an Arrandale. http://i.imgur.com/VkJRu.jpg The pointer does not move or go away; it stays in that spot as you use the text console, even if text, gpm, etc, paints under that area of the screen. This happens every time. It blocks use of that area of the screen and makes users think they are in Xorg when they are not. -- 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+8+cattj3zygkkcs_yy5i5qhhwbpx54jcs1i1xlta4tzmz...@mail.gmail.com
Processed: reassign 640974 to linux-2.6, forcibly merging 640966 640974
Processing commands for cont...@bugs.debian.org: reassign 640974 linux-2.6 2.6.32-35squeeze1 Bug #640974 [linux-image-2.6.32-5-amd64] After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 'linux-2.6'. Bug #640974 [linux-2.6] After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed There is no source info for the package 'linux-2.6' at version '2.6.32-35squeeze1' with architecture '' Unable to make a source version for version '2.6.32-35squeeze1' Bug Marked as found in versions 2.6.32-35squeeze1. forcemerge 640966 640974 Bug#640966: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#640974: After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed Bug#640973: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641018: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641025: linux-image-2.6.32-5-686-bigmem: Squeeze1 kernel update unable to handle kernel paging request... Bug#641034: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641040: Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug#641121: gnome-system-monitor and chrome fail while using linux-image-2.6.32-5-686 from security.debian (update from 09.09.11). It looks like this bug has fixed https://lkml.org/lkml/2011/3/27/17 Bug#641171: linux-headers-2.6.32-5-all: kernel oops with google-chrome-unstable Forcibly Merged 640966 640973 640974 641018 641025 641034 641040 641121 641171. thanks Stopping processing here. Please contact me if you need assistance. -- 641018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641018 641040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641040 641025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641025 640974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640974 640973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640973 641121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641121 641034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641034 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 641171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641171 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.131584202310197.transcr...@bugs.debian.org
Bug#640974: After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed
On Fri, Sep 09, 2011 at 08:55:31AM +0200, Alexander Fortin wrote: Package: popularity-contest Version: 1.49 Severity: normal This I what I get when I run /etc/cron.daily/popularity-contest: Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] Oops: [#5] SMP Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] last sysfs file: /sys/devices/pci:00/:00:01.1/host0/target0:0:1/0:0:1:0/block/sdb/stat Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] Stack: Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] Call Trace: Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] Code: 48 89 df e8 e3 c2 f1 ff 31 c0 40 84 ed 49 0f 45 c4 5b 5d 41 5c c3 55 53 48 83 ec 08 48 85 f6 48 8b 6f 60 74 1a 48 3b 75 10 74 14 48 8b 1e 48 8d 7b 60 e8 dd 86 f3 ff 48 89 df e8 ac c2 f1 ff 48 Message from syslogd@asimov at Sep 9 08:49:07 ... kernel:[41285.840016] CR2: fff3 Killed [...] Most of the call trace is missing, but the last line strongly suggests this is the regression that has just been fixed in 2.6.32-35squeeze2. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20110912154239.ga18...@decadent.org.uk
Bug#640974: After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed
Alexander Fortin wrote: [66878.232276] BUG: unable to handle kernel paging request at fff3 [66878.232309] IP: [8112f98d] m_stop+0x15/0x4c Yep, that's the bug described at http://bugs.debian.org/640966 that Ben mentioned (fixed by upstream patch 76597cd31470 proc: fix oops on invalid /proc/pid/maps access which was included in 2.6.32-35squeeze2). Thanks for checking. -- 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/20110912161717.GA2@elie
Bug#640974: After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed
On 09/12/2011 06:17 PM, Jonathan Nieder wrote: Yep, that's the bug described athttp://bugs.debian.org/640966 that Ben mentioned (fixed by upstream patch 76597cd31470 proc: fix oops on invalid/proc/pid/maps access which was included in 2.6.32-35squeeze2). Thanks for checking. Thank you guys! -- Alexander Fortin http://about.me/alexanderfortin/ -- 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/4e6e30fd.1060...@gmail.com
Bug#641008: X11 mouse dropping left on text console when switching VTs; doesn't go away
Hi Thomas, Thomas Shanks wrote: Image (link below) of graphical mouse pointer left behind whenever you Ctrl-Alt-Shift-F# to text VTs while Xorg is running with an external screen connected on an Arrandale. [...] The pointer does not move or go away; it stays in that spot as you use the text console, even if text, gpm, etc, paints under that area of the screen. A few questions: - is this a regression? If so, what was the last working version? - can you reproduce this with the kernel from sid or experimental? (It should only be necessary to install updated linux-base, linux-image-foo, and initramfs-tools to check.) If so, we can report this upstream, and if not, we can look for a fix to backport. - some of the hints at http://intellinuxgraphics.org/how_to_report_bug.html might also be helpful (especially re finding out if anything interesting was logged during the modeswitch). Thanks for reporting, 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/20110912162544.GB2@elie
Bug#641340: nfs-common: mount fails with mount.nfs: Connection timed out message
Package: nfs-common Version: 1:1.2.4-1 Severity: important Yesterday I did dist-upgrade and nfs mounted share stopped working. Tried to mount it manually - it waits for 120s and fails with message $ sudo mount -t nfs 192.168.1.1:/luna luna mount.nfs: Connection timed out On the other side there is OpenWRT Backfire 10.03 router with usb disk shared via nfs, it works as usual. -- rpcinfo to the nfs server from client -- $ rpcinfo -p 192.168.1.1 program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000211 udp 32777 nlockmgr 1000213 udp 32777 nlockmgr 1000214 udp 32777 nlockmgr 1000211 tcp 32777 nlockmgr 1000213 tcp 32777 nlockmgr 1000214 tcp 32777 nlockmgr 132 udp 2049 nfs 133 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs 152 udp 32780 mountd 152 tcp 32780 mountd 153 udp 32780 mountd 153 tcp 32780 mountd -- verbose mount output -- # mount -vvv -t nfs 192.168.1.1:/luna luna mount: fstab path: /etc/fstab mount: mtab path: /etc/mtab mount: lock path: /etc/mtab~ mount: temp path: /etc/mtab.tmp mount: UID:0 mount: eUID: 0 mount: spec: 192.168.1.1:/luna mount: node: luna mount: types: nfs mount: opts: (null) mount: external mount: argv[0] = /sbin/mount.nfs mount: external mount: argv[1] = 192.168.1.1:/luna mount: external mount: argv[2] = luna mount: external mount: argv[3] = -v mount: external mount: argv[4] = -o mount: external mount: argv[5] = rw mount.nfs: timeout set for Tue Sep 13 01:37:47 2011 mount.nfs: trying text-based options 'vers=4,addr=192.168.1.1,clientaddr=192.168.1.236' mount.nfs: mount(2): Connection timed out mount.nfs: Connection timed out # -- Package-specific info: -- rpcinfo -- program vers proto port 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 41108 status 1000241 tcp 56305 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = localdomain [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- 192.168.1.1:/luna /home/me/luna nfs soft,bg 0 0 -- /proc/mounts -- rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.113 ii initscripts 2.88dsf-13.11 ii libc6 2.13-20 ii libcap2 1:2.22-1 ii libcomerr21.42~WIP-2011-07-02-1 ii libevent-1.4-21.4.14b-stable-1 ii libgssapi-krb5-2 1.9.1+dfsg-2 ii libgssglue1 0.3-3 ii libk5crypto3 1.9.1+dfsg-2 ii libkeyutils1 1.5.2-2 ii libkrb5-3 1.9.1+dfsg-2 ii libnfsidmap2 0.24-1 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-21 ii lsb-base 3.2-28 ii rpcbind 0.2.0-6 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.6.7-3 nfs-common suggests no packages. -- debconf-show failed -- 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/20110912174320.25599.91918.reportbug@localhost.localdomain
Bug#641288: linux-image-2.6.32-5-686: Can not read appendable cdroms/dvds.
Hi Victor, Victor Pablos Ceruelo wrote: appendable cdroms/dvds can not be read. Checked in 2.6.32-35squeeze2 and 2.6.39-bpo.2-686-pae (i686). At [1], I believe you wrote that 2.6.38-5 reproduces the bug and 2.6.39-3 does not. Am I remembering correctly? If you have time, please test 2.6.39~rc7-1~experimental.1 and 2.6.39-1 from snapshot.debian.org (maybe the former reproduces it and the latter fixes it), and if that doesn't help, bisect (first using kernels from snapshot.debian.org, then kernels built from source as described at [2]) to narrow down when the fix happened. Full dmesg output (i.e., including bootup) after reproducing the problem could also help. Thanks much, Jonathan [1] http://bugs.debian.org/583949#90 [2] http://bugs.debian.org/583949#95 -- 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/20110912175614.GA28705@elie
Bug#622971: Still having issues
With kernel 3.0 uname -a Linux deb001 3.0.0-1-amd64 #1 SMP Sat Aug 27 16:21:11 UTC 2011 x86_64 GNU/Linux it keeps the same, not working ok yet. Same issue, starts working but suddenly it fails, and modprobe -r ath9k doesn't fix it. If I can contribute with something to help.
Bug#641243: linux: kernel failure at startup, but boots
Hi Joshua, Joshua Beck wrote: WARNING: at [...]/drivers/tty/tty_ldisc.c:766 tty_ldisc_reinit+0x46/0x77() Is this reproducible? Is the message and backtrace the same every time? Can you reproduce when booting without the nvidia kernel module (e.g., by temporarily uninstalling or blacklisting it)? Does it happen with the kernel from experimental, too (I don't see why it wouldn't, but it can't hurt to check)? Is this a regression? If so, what is the last version not showing the warning and first version showing the warning you've tried? Thanks for reporting, 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/20110912181159.GA28856@elie
Bug#622971: ath9k: Ath9K wireless quite unreliable since upgrade to 2.6.38
Jose A. Medrano wrote: Same issue, starts working but suddenly it fails, and modprobe -r ath9k doesn't fix it. Unfortunately I suspect this bug is tracking a batch of related issues, since details like that vary from submitter to submitter. :/ Please feel free to file a separate report with something reproducible and concrete (we can merge reports that turn out to have the same cause later). What is the newest version you've tried that worked without trouble and the oldest that exhibited problems? Can you narrow the regression range with a bisection search through packages at snapshot.debian.org? 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/20110912181730.GB28856@elie
Bug#622146: nfs-common: compatibility between squeeze and sid broken
On Mon, 2011-09-05 at 12:46 -0400, Sam Hartman wrote: Adam == Adam D Barratt a...@adam-barratt.org.uk writes: Adam The krb5 package was uploaded and I've (somewhat belatedly) Adam marked it for acceptance at the next dinstall. What's the Adam status of the nfs-utils upload? My guess is they were waiting for krb5. Remember they have to increase build-depends for the krb5 you just accepted. If it requires a versioned build-dependency, then both packages could just have been uploaded at the same time. Even if we accepted them both from p-u-NEW together, the buildds would have put nfs-common in to the build-deps uninstallable state until the necessary version of krb5 was available. 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/1315851892.7688.5.ca...@hathi.jungle.funky-badger.org
Bug#605318: radeon: horizontal interference lines on screen
Hi Jonathon, glad you are onto this. The problem is much less on mine as each flash is only about 1-2 cms long and I guess 1px wide, and they only occur on certain parts of the screen on solid dark colours and appear to be completely random. They vary in colour. They show up on the grey background of gwenview well, and on Chromiums top window frame, which I have dark blue, and that gets blue flashes. Strange, but I dont see any interference on my desktop background, which has a large area of solid black. This is on a testbed install of Crunchbang Statler, which is pretty much pure Squeeze, for checking out stock kernels and open source drivers and have been trying to get a video screenshot to send to you but I can't get vnc2swf to work, as it bombs out with an error. If I can get some video of it, I will send it so you can see exactly what it looks like. firmware-linux-nonfree is installed. I have not tried sid kernels, but I also have a testbed install of Mint LMDE (based on Testing), and the problem seems to be fixed in that with the current kernel and radeon driver, though suspend does not work properly if I remember correctly. I have everything working perfectly on my Squeeze production install with this workaround, which is to use: Kernel-2.6.34-2.dmz.3-liquorix-amd64 x86_64 + Catalyst version 10.12. Graphics info : Card ATI Mobility Radeon HD 3400 Series X.Org 1.7.7 Res: 1600x900@60.2hz GLX Renderer ATI Mobility Radeon HD 3400 Series GLX Version 3.3.10317 Compatibility Profile Context This is the first combination of driver and kernel I found that works properly on this machine in Squeeze, including working resume from suspend to ram, so I am sticking to it on my production install. I removed the stock debian kernel so I don't get updates to it any more when I upgrade. I can do a new testbed install of straight Debian Squeeze and give feedback from that if it will help. Cheers, Mike On Mon, 12 Sep 2011 08:48:49 +0100, Jonathan Nieder jrnie...@gmail.com wrote: found 605318 linux-2.6/2.6.32-35 quit Hi, Matt Pandina wrote: I too was experiencing horizontal lines (so bad that I could barely see the screen!) [...] Finally I managed to see through the horizontal lines enough to go to: System Preferences Monitors and told it to rotate the screen upside-down. The lines were still there, but they stopped after I switched the rotation back to normal. Thanks. Mike, do you experience the same? Both: - can you describe the horizontal lines more? Are they one pixel tall or are they thicker? How quickly do they flash? Are they always there or only sometimes? Do they move? Do they cover the screen or only part of it? Can you take a photo? - do you have firmware-linux-nonfree installed? - can you reproduce this with a kernel from sid or experimental? (To install one to try, the only additional dependencies that should be needed are recent linux-base and initramfs-tools.) - If so, please report this upstream at bugs.freedesktop.org, product DRI, component DRM/Radeon and let us know the bug number so we can track it. (Don't worry about duplicating each other --- it's nicer to have the information for each machine separately and mark one as a dup if appropriate later anyway.) - otherwise, we can try to find the fix and backport it; if you have time to find the first working verison at snapshot.debian.org by the bisection method, that would be helpful. Sorry for the slow response, and hope that helps, Jonathan -- Mike Sumner Phone: 01507 568735 Web: http://www.treereportsandsurveys.co.uk http://www.msumner.co.uk -- 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/op.v1pkw3lkv46o6b@vaio
Re: Bug#641313: udev: blu-ray writer not detected - no /dev/sr0
reassign 641313 linux-2.6 thanks On Sep 12, Gary Dale garyd...@eol.ca wrote: After the last kernel update I rebooted the computer. Now there is no /dev/sr0 listed for the blu-ray writer. Blame the kernel then. Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) -- ciao, Marco signature.asc Description: Digital signature
Processed: Re: Bug#641313: udev: blu-ray writer not detected - no /dev/sr0
Processing commands for cont...@bugs.debian.org: reassign 641313 linux-2.6 Bug #641313 [udev] udev: blu-ray writer not detected - no /dev/sr0 Bug reassigned from package 'udev' to 'linux-2.6'. Bug No longer marked as found in versions udev/164-3. thanks Stopping processing here. Please contact me if you need assistance. -- 641313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641313 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.13158533518318.transcr...@bugs.debian.org
Bug#605318: radeon: horizontal interference lines on screen
Mike Sumner wrote: [...] each flash is only about 1-2 cms long and I guess 1px wide, and they only occur on certain parts of the screen on solid dark colours and appear to be completely random. They vary in colour. They show up on the grey background of gwenview well, and on Chromiums top window frame, which I have dark blue, and that gets blue flashes. Strange, but I dont see any interference on my desktop background, which has a large area of solid black. [...] I have not tried sid kernels, but I also have a testbed install of Mint LMDE (based on Testing), and the problem seems to be fixed in that with the current kernel and radeon driver Thanks, this helps a lot. My random guess at the moment is that this is related to the bug described at http://bugs.debian.org/597358, which was fixed upstream in v2.6.37-rc1. There is a series of three patches in that bug log that could be worth a try if you have the time (see [1]). [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2 -- 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/20110912185259.GA3@elie
Re: Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
reassign 641176 linux-2.6 2.6.32-35 kthxbye On Mon, Sep 12, 2011 at 10:27:21 +0200, Michel Dänzer wrote: On Son, 2011-09-11 at 10:37 +0300, Tomi Leppänen wrote: Package: xserver-xorg-video-radeon Version: 1:6.13.1-2+squeeze1 Severity: important Tags: upstream This bug prevents me from using X because it won't start with this graphics card. I also have these lines in my dmesg, they may be important. [0.120429] pci :01:00.0: BAR 0: no parent found for of device [0xd000-0xdfff] [0.120504] pci :01:00.0: BAR 0: can't allocate resource [0.125917] pnp 00:00: mem resource (0xcd000-0xc) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125939] pnp 00:00: mem resource (0xf-0xf7fff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125960] pnp 00:00: mem resource (0xf8000-0xfbfff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125982] pnp 00:00: mem resource (0xfc000-0xf) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126003] pnp 00:00: mem resource (0x0-0x9) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126024] pnp 00:00: mem resource (0x10-0x1ffe) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.173856] pci :01:00.0: BAR 0: can't allocate mem resource [0xe000-0xe7ff] [7.488362] [drm] Detected VRAM RAM=0M, BAR=0M Though these are probably related to Linux itself. Indeed, looks like a kernel (or possibly BIOS) PCI failure. This should probably be reassigned to the kernel, and you might want to try newer kernels. Reassigning with this message. Tomi, can you check if a newer kernel fixes this, or if there are BIOS updates available for your machine? Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110912185753.gb5...@radis.liafa.jussieu.fr
Processed: Re: Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Processing commands for cont...@bugs.debian.org: reassign 641176 linux-2.6 2.6.32-35 Bug #641176 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M Bug reassigned from package 'xserver-xorg-video-radeon' to 'linux-2.6'. Bug No longer marked as found in versions xserver-xorg-video-ati/1:6.13.1-2+squeeze1. Bug #641176 [linux-2.6] xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M There is no source info for the package 'linux-2.6' at version '2.6.32-35' with architecture '' Unable to make a source version for version '2.6.32-35' Bug Marked as found in versions 2.6.32-35. kthxbye Stopping processing here. Please contact me if you need assistance. -- 641176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176 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.131585388911433.transcr...@bugs.debian.org
Processed: tagging 641176
Processing commands for cont...@bugs.debian.org: tags 641176 + moreinfo Bug #641176 [linux-2.6] xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 641176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176 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.131585390211512.transcr...@bugs.debian.org
Bug#603469: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back
Uwe Kleine-König wrote: On Mon, Nov 15, 2010 at 12:18:00PM +0100, lauren wrote: The following packages have unmet dependencies: linux-image-2.6.36-trunk-686 : Depends: linux-base (= 2.6.36-1~experimental.1) but 2.6.32-27 is to be installed Recommends: firmware-linux-free (= 2.6.36) but 2.6.32-27 is to be installed E: Broken packages ah, try apt-get -t experimental install linux-image-2.6.36-trunk-686 Sorry for the fuss and the long silence. Perhaps apt-get -t experimental install linux-image-foo linux-base \ initramfs-tools firmware-linux-free would do. -- 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/20110912191248.GA30434@elie
Bug#599901: base: System Crash with ata3.00 error
Hi Kevin, Kevin wrote: I encountered a serious problem of ata3.00 error when I was running the system, /var/log/kernel.log: kernel: [ 872.444136] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 kernel: [ 872.444146] ata3.00: BMDMA stat 0x25 kernel: [ 872.444153] ata3.00: failed command: READ DMA Sorry for the long silence. Is this reproducible (e.g., does it happen often, or do you know how to provoke it)? Please attach output from /usr/share/bug/linux-image-$(uname -r)/script 31 so we can get to know what hardware and drivers you are using. Does the hard drive seem to be in good shape (smartctl -a name of disk from smartmontools can help figure that out)? Is there a crash or just a delay during bootup? 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/20110912192723.GA30494@elie
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Ben Hutchings wrote: On Wed, Aug 31, 2011 at 11:08:30PM +0200, Thibault Manlay wrote: Issue comes from CONFIG_LOCKUP_DETECTOR=y (issue disappears when unsetting it). But why would this option/feature locks-up the system? It doesn't. It just tells you when a process is stuck for a long time. If the process eventually recovers, and this option is disabled, then you might not notice. That's the theory, but if Thibault has to use the power button to reboot to recover, then something's going wrong, no? Anyway, it seems it's time to take this upstream. Thibault, could you send a summary of findings so far (i.e., what the state is like when closing the lid, problem only shows up with CONFIG_LOCKUP_DETECTOR=y, the nolapic kernel parameter works around it, whatever logs it was possible to get of what happens until the lid closes, and an acpidump) to the linux-a...@vger.kernel.org list (no subscription needed, since the convention is to always reply-to-all), cc-ing this bug log? Sorry for the trouble, and good luck. 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/20110912193656.GA30915@elie
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
On 12/09/11 21:36, Jonathan Nieder wrote: That's the theory, but if Thibault has to use the power button to reboot to recover, then something's going wrong, no? Anyway, it seems it's time to take this upstream. Thibault, could you send a summary of findings so far (i.e., what the state is like when closing the lid, problem only shows up with CONFIG_LOCKUP_DETECTOR=y, the nolapic kernel parameter works around it, whatever logs it was possible to get of what happens until the lid closes, and an acpidump) to the linux-a...@vger.kernel.org list (no subscription needed, since the convention is to always reply-to-all), cc-ing this bug log? Sorry for the trouble, and good luck. Hello, I tried to get a kernel dump with kdump/kexec to have something I could work on, but no success. The kernel hangs and doesn't reboot on the crash kernel. Disabling SMP solves the problem too (it is required for kdump, but SMP can be enabled if you tell kdump to use one cpu), I feel a little bit discouraged. Since I can't find any pertinent similar problem (they are either too old or with no answer, or both) I begin to believe this is a hardware problem on my laptop. I'll try to patch the BIOS someday. Fun fact : closing lid hangs the system, but after I have done a single suspend-to-ram, I can close the lid as much as I want without getting the system to hang... Thanks, -- Thibault Manlay signature.asc Description: OpenPGP digital signature
Bug#548630: linux-image-2.6.26-2-686: Crash/Hang with heavy disk write when using SATA AHCI mode
Hi Jonathan,
I cannot use the hardware to reproduce. It is currently my LAMP server, and
used 24/7. Sorry. I was able to fix at that time the bug by putting the two
DDR modules in 32 bit configuration, and not in 64 bit.
I hope this helps a bit...
Best regards
Hans
On Sat, Sep 3, 2011 at 7:36 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi,
Hans IJ wrote:
I can reproduce this problem on both an ASUS P5Q-VM and Intel DG45ID
Motherboard. Both MB's have same ICH10 chipset.
Let me know if you need more.
Sorry for the loong delay. The assertion triggered here is in
mm/vmscan.c, function isolate_lru_pages():
switch (__isolate_lru_page(page, mode, file)) {
case 0:
[...]
case -EBUSY:
[...]
continue;
default:
BUG();
}
eax contains -EINVAL, so chances are that was the error code. It
means the PageLRU flag was clear, the page's mode didn't match mode,
the page's is_file_cache flag didn't match file, or the page was
unevictable.
Maybe this is fixed by v2.6.39~59 (mm: check PageUnevictable in
lru_deactivate_fn(), 2011-05-11), even though the case that prompted
that patch was not broken until v2.6.39-rc1~329 (2011-03-22). Can you
still reproduce this? If so, could you test 2.6.39 (which would
work according to that hypothesis) and 2.6.39-rc7 (which wouldn't) to
check?
Hope that helps,
Jonathan
--
To unsubscribe, send mail to 548630-unsubscr...@bugs.debian.org.
Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555
Thibault Manlay wrote: Since I can't find any pertinent similar problem (they are either too old or with no answer, or both) I begin to believe this is a hardware problem on my laptop. I'll try to patch the BIOS someday. Fun fact : closing lid hangs the system, but after I have done a single suspend-to-ram, I can close the lid as much as I want without getting the system to hang... Neat. Yes, it's probably a BIOS bug, but with acpidump output from before and after suspending, the people at linux-acpi@vger might be able to help. -- 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/20110912202545.ga2...@elie.gateway.2wire.net
Bug#548630: linux-image-2.6.26-2-686: Crash/Hang with heavy disk write when using SATA AHCI mode
tags 548630 + moreinfo quit Hi, Hans IJ wrote: I cannot use the hardware to reproduce. It is currently my LAMP server, and used 24/7. Sorry. I was able to fix at that time the bug by putting the two DDR modules in 32 bit configuration, and not in 64 bit. I hope this helps a bit... No problem. If there won't be time in the next month or so I guess we should close the bug and reopen when someone else experiences it or it happens again. If you or anyone else experiencing this ends up in a position to reproduce it, in addition to trying a recent kernel it would be interesting to try the debugging patch from [1] (the surrounding thread is about a different bug that was introduced in a newer kernel, but the patch makes the kernel print the right information). Also, it's possible (though unlikely) that a description of the problem (plus hardware information they ask about in follow-up) could be enough to ring a bell for the Linux memory management subsystem maintainers; feel free to ask them at linux...@kvack.org (no subscription required and the convention is always to reply-to-all there), cc-ing this bug. Sorry I have no better insights. Jonathan [1] http://thread.gmane.org/gmane.linux.kernel.mm/66536 -- 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/20110912211551.gb2...@elie.gateway.2wire.net
Processed: Re: linux-image-2.6.26-2-686: Crash/Hang with heavy disk write when using SATA AHCI mode
Processing commands for cont...@bugs.debian.org: tags 548630 + moreinfo Bug #548630 [linux-2.6] linux-image-2.6.26-2-686: Crash/Hang with heavy disk write when using SATA AHCI mode Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 548630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548630 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.131586223219995.transcr...@bugs.debian.org
Bug#640974: After installing linux-image-2.6.32-35squeeze1 popularity-contest daily cronjob gets killed
On Mon, Sep 12, 2011 at 11:17:17AM -0500, Jonathan Nieder wrote: Alexander Fortin wrote: [66878.232276] BUG: unable to handle kernel paging request at fff3 [66878.232309] IP: [8112f98d] m_stop+0x15/0x4c Yep, that's the bug described at http://bugs.debian.org/640966 that Ben mentioned (fixed by upstream patch 76597cd31470 proc: fix oops on invalid /proc/pid/maps access which was included in 2.6.32-35squeeze2). Thanks for checking. I like to add that popularity-contest does ... open MAPS, /proc/$_/maps or next; ... so this bug is a time bomb for popcon users. Glad you fixed it already! Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- 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/20110912211800.GA6136@yellowpig
Bug#603469: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back
i've moved over to arch these days so this doesn't affect me anymore :) On 09/12/2011 09:12 PM, Jonathan Nieder wrote: Uwe Kleine-König wrote: On Mon, Nov 15, 2010 at 12:18:00PM +0100, lauren wrote: The following packages have unmet dependencies: linux-image-2.6.36-trunk-686 : Depends: linux-base (= 2.6.36-1~experimental.1) but 2.6.32-27 is to be installed Recommends: firmware-linux-free (= 2.6.36) but 2.6.32-27 is to be installed E: Broken packages ah, try apt-get -t experimental install linux-image-2.6.36-trunk-686 Sorry for the fuss and the long silence. Perhaps apt-get -t experimental install linux-image-foo linux-base \ initramfs-tools firmware-linux-free would do. -- 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/4e6e78b7.3060...@gagfoot.com
Bug#603469: marked as done (xserver-xorg-video-ati: screen randomly goes black with no way to bring it back)
Your message dated Mon, 12 Sep 2011 16:45:18 -0500 with message-id 20110912214509.ga2...@elie.chipublib.org and subject line Re: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back has caused the Debian Bug report #603469, regarding xserver-xorg-video-ati: screen randomly goes black with no way to bring it back 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.) -- 603469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-ati Version: 1:6.13.1-2 Severity: important after some random time period my screen goes black and nothing i do short of rebooting can bring it back ... i have gotten quite good at switching to a new console and logging in and rebooting without being able to see what i'm doing btw the system is still running normally but no display at all i am using the open source ati driver with a Thinkpad T500 ... KMS is enabled and the DRM module is loading correctly -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Dec 27 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1733468 Oct 10 14:03 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 /etc/X11/xorg.conf does not exist. Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-27) (m...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 22:47:19 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 33504 Nov 14 13:50 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.23-dsa-ia32 i686 Debian Current Operating System: Linux BUZZ 2.6.32-5-686 #1 SMP Sat Oct 30 22:47:19 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=564cf89a-18e1-46e3-acd0-159224283f2e ro quiet Build Date: 10 October 2010 11:57:07AM xorg-server 2:1.7.7-8 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Nov 14 13:50:44 2010 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81ecca0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 1002:9591:17aa:2117 ATI Technologies Inc Mobility Radeon HD 3650 rev 0, Mem @ 0xd000/268435456, 0xcfff/65536, I/O @ 0x2000/256, BIOS @ 0x/131072 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension
Bug#603469: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back
reopen 603469 submitter 603469 ! retitle 603469 radeon: atombios stuck executing F6D8 (screen randomly goes black with no way to get it back) quit Hi again, lauren wrote: no problem and thanks for following up On second thought, I'm reopening this as an excuse to consider drm patches for backporting. I've set myself as submitter so hopefully you won't get any spam from it after this message. While I have your attention, could you help with one puzzle? The X log from the initial report contains: | Current Operating System: Linux BUZZ 2.6.32-5-686 #1 SMP Sat Oct 30 22:47:19 UTC 2010 i686 Which sounds like 2.6.32-27. But dmesg contains: | [7.120450] [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on minor 0 | [ 949.420558] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting | [ 949.420570] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing F6D8 (len 487, WS 0, PS 4) @ 0xF719 This doesn't look like the standard squeeze kernel, since squeeze doesn't contain v2.6.34-rc4~12^2~50^2~17 (drm/radeon/kms: catch atombios infinite loop and break out of it, 2010-03-02). It can't be a mainline kernel, since the just-mentioned infinite loop checker was not introduced until after a radeon ABI bump (2.1.0). What did I miss? Puzzled, Jonathan (That mystery aside, here are some bugfix patches to consider backporting. - v2.6.34-rc4~12^2~50^2~17 (drm/radeon/kms: catch atombios infinite loop and break out of it, 2010-03-02) - v2.6.36-rc3~9^2~79^2~24 (drm/radeon/kms/atom: bump atom loop timeout from 1 sec to 5 secs, 2010-06-30) - v2.6.37-rc8~26^2~2 (drm/radeon/kms: reorder display resume to avoid problems, 2010-12-20): This fixes the infamous atombios timeouts on resume.) -- 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/20110912224817.gb2...@elie.chipublib.org
Processed: Re: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back
Processing commands for cont...@bugs.debian.org:
reopen 603469
Bug #603469 {Done: Jonathan Nieder jrnie...@gmail.com} [linux-2.6]
xserver-xorg-video-ati: screen randomly goes black with no way to bring it back
submitter 603469 !
Bug #603469 [linux-2.6] xserver-xorg-video-ati: screen randomly goes black with
no way to bring it back
Changed Bug submitter to 'Jonathan Nieder jrnie...@gmail.com' from 'lauren
lau...@gagfoot.com'
retitle 603469 radeon: atombios stuck executing F6D8 (screen randomly goes
black with no way to get it back)
Bug #603469 [linux-2.6] xserver-xorg-video-ati: screen randomly goes black with
no way to bring it back
Changed Bug title to 'radeon: atombios stuck executing F6D8 (screen randomly
goes black with no way to get it back)' from 'xserver-xorg-video-ati: screen
randomly goes black with no way to bring it back'
quit
Stopping processing here.
Please contact me if you need assistance.
--
603469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603469
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.131586770814965.transcr...@bugs.debian.org
Bug#631843: linux-image-2.6.32-5-amd64: General protection fault
Thomas Nilsson wrote: [6.566791] platform radeon_cp.0: firmware: requesting radeon/R100_cp.bin [6.632626] radeon_cp: Failed to load firmware radeon/R100_cp.bin [6.632707] [drm:r100_cp_init] *ERROR* Failed to load firmware! [...] Jun 26 02:11:05 server kernel: [25987.488029] general protection fault: [#1] SMP Jun 26 02:11:05 server kernel: [25987.488035] last sysfs file: /sys/devices/platform/coretemp.3/temp1_input [...] Jun 26 02:11:05 server kernel: [25987.488089] Pid: 1455, comm: hald-addon-stor Not tainted 2.6.32-5-amd64 #1 PRIMERGY TX100 S1 Jun 26 02:11:05 server kernel: [25987.488092] RIP: 0010:[810e7f8c] [810e7f8c] __kmalloc+0xd2/0x141 Are the GPFs reproducible? Does booting with firmware-linux-nonfree (temporarily) installed help? What version of the kernel was working before? Sorry for the trouble, 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/20110912231050.ga3...@elie.chipublib.org
Processed (with 1 errors): Re: Bug#636583: nvidia-kernel-dkms: 280.13 bad return status error 10
Processing commands for cont...@bugs.debian.org: reassign 636598 make 3.82-1 Bug #636598 [linux-2.6] make 3.82 breaks kernel module build: 'mixed implicit and normal rules' in linux-headers-* Bug reassigned from package 'linux-2.6' to 'make'. Bug No longer marked as found in versions 2.6.39-3 and 3.0.0-1. Bug #636598 [make] make 3.82 breaks kernel module build: 'mixed implicit and normal rules' in linux-headers-* Bug Marked as found in versions make-dfsg/3.82-1. severity 636598 serious Bug #636598 [make] make 3.82 breaks kernel module build: 'mixed implicit and normal rules' in linux-headers-* Severity set to 'serious' from 'important' merge 635317 636598 Bug#635317: make 3.82 breaks kernel module build: 'mixed implicit and normal rules' in linux-headers-* Bug#636598: make 3.82 breaks kernel module build: 'mixed implicit and normal rules' in linux-headers-* Mismatch - only Bugs in same state can be merged: Values for `affects' don't match: #635317 has `src:eglibc,src:nvidia-graphics-drivers,linux-2.6,nvidia-kernel-source,nvidia-kernel-dkms'; #636598 has `src:nvidia-graphics-drivers' End of message, stopping processing here. Please contact me if you need assistance. -- 636598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636598 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.131586963423682.transcr...@bugs.debian.org
Bug#603469: xserver-xorg-video-ati: screen randomly goes black with no way to bring it back
reopen 603469 submitter 603469 ! retitle 603469 radeon: atombios stuck executing F6D8 (screen randomly goes black with no way to get it back) quit Hi again, lauren wrote: no problem and thanks for following up On second thought, I'm reopening this as an excuse to consider drm patches for backporting. I've set myself as submitter so hopefully you won't get any spam from it after this message. While I have your attention, could you help with one puzzle? The X log from the initial report contains: | Current Operating System: Linux BUZZ 2.6.32-5-686 #1 SMP Sat Oct 30 22:47:19 UTC 2010 i686 Which sounds like 2.6.32-27. But dmesg contains: | [ 7.120450] [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on minor 0 | [ 949.420558] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting | [ 949.420570] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing F6D8 (len 487, WS 0, PS 4) @ 0xF719 This doesn't look like the standard squeeze kernel, since squeeze doesn't contain v2.6.34-rc4~12^2~50^2~17 (drm/radeon/kms: catch atombios infinite loop and break out of it, 2010-03-02). It can't be a mainline kernel, since the just-mentioned infinite loop checker was not introduced until after a radeon ABI bump (2.1.0). What did I miss? Puzzled, Jonathan (That mystery aside, here are some bugfix patches to consider backporting. - v2.6.34-rc4~12^2~50^2~17 (drm/radeon/kms: catch atombios infinite loop and break out of it, 2010-03-02) - v2.6.36-rc3~9^2~79^2~24 (drm/radeon/kms/atom: bump atom loop timeout from 1 sec to 5 secs, 2010-06-30) - v2.6.37-rc8~26^2~2 (drm/radeon/kms: reorder display resume to avoid problems, 2010-12-20): This fixes the infamous atombios timeouts on resume.) jonathan i always ran debian testing and so have had whatever was in those repos ... i use my machines for dev so try to keep away from anything too bleeding edge ... i doubt i would have added sid or experimental repos for fear of breaking things hth lauren
Bug#599901: marked as done (base: System Crash with ata3.00 error)
Your message dated Mon, 12 Sep 2011 18:41:33 -0500
with message-id 20110912233936.ga3...@elie.chipublib.org
and subject line Re: base: System Crash with ata3.00 error
has caused the Debian Bug report #599901,
regarding base: System Crash with ata3.00 error
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.)
--
599901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: base
Severity: important
Tags: d-i
I encountered a serious problem of ata3.00 error when I was running the system,
/var/log/kernel.log:
kernel: [ 872.444136] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action
0x0
kernel: [ 872.444146] ata3.00: BMDMA stat 0x25
kernel: [ 872.444153] ata3.00: failed command: READ DMA
kernel: [ 872.444168] ata3.00: cmd c8/00:08:3c:44:22/00:00:00:00:00/ed tag 0
dma 4096 in
kernel: [ 872.444172] res 51/40:00:3f:44:22/00:00:00:00:00/ed Emask
0x9 (media error)
kernel: [ 872.444180] ata3.00: status: { DRDY ERR }
kernel: [ 872.444185] ata3.00: error: { UNC }
kernel: [ 872.485549] ata3.00: configured for UDMA/133
kernel: [ 872.485578] ata3: EH complete
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Version: 3.0.0-3
Kevin Chen wrote:
No, I have not such problem any more since a update of linux-kernel.
/usr/share/bug/linux-image-$(uname -r)/script 31 gives
** Version:
Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc
version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011
Marking accordingly, thanks.
** Command line:
BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64
root=UUID=17861003-5274-4634-b8ea-42467b898bf8 ro quiet
** Not tainted
** Kernel log:
[8.488340] NET: Registered protocol family 31
[8.488343] Bluetooth: HCI device and connection manager initialized
[8.488346] Bluetooth: HCI socket layer initialized
[8.488349] Bluetooth: L2CAP socket layer initialized
[8.488829] Bluetooth: SCO socket layer initialized
[8.643049] Bluetooth: Generic Bluetooth USB driver ver 0.6
[8.643262] usbcore: registered new interface driver btusb
[8.764711] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[8.764717] i915 :00:02.0: setting latency timer to 64
[8.792078] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection
driver for Linux, in-tree:s
[8.792082] iwl3945: Copyright(c) 2003-2011 Intel Corporation
[8.792151] iwl3945 :06:00.0: power state changed by ACPI to D0
[8.792161] iwl3945 :06:00.0: power state changed by ACPI to D0
[8.792179] iwl3945 :06:00.0: PCI INT A - GSI 17 (level, low) - IRQ
17
[8.792194] iwl3945 :06:00.0: setting latency timer to 64
[8.846358] iwl3945 :06:00.0: Tunable channels: 13 802.11bg, 4 802.11a
channels
[8.846363] iwl3945 :06:00.0: Detected Intel Wireless WiFi Link 3945ABG
[8.846540] iwl3945 :06:00.0: irq 45 for MSI/MSI-X
[8.846832] Registered led device: phy0-led
[8.847690] i915 :00:02.0: irq 46 for MSI/MSI-X
[8.847698] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[8.847701] [drm] Driver supports precise vblank timestamp query.
[8.847761] vgaarb: device changed decodes:
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[8.886425] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[8.932424] pcmcia_socket pcmcia_socket0: cs: memory probe
0x0c-0x0f: excluding 0xc-0xc 0xe-0xf
[8.932468] pcmcia_socket pcmcia_socket0: cs: memory probe
0xa000-0xa0ff: clean.
[8.932507] pcmcia_socket pcmcia_socket0: cs: memory probe
0x6000-0x60ff: excluding 0x6000-0x60ff
[8.997058] tifm_7xx1 :09:04.2: PCI INT C - GSI 22 (level, low) -
IRQ 22
[9.104952] Linux media interface: v0.10
[9.108224] [drm] initialized overlay support
[9.121256] fbcon: inteldrmfb (fb0) is primary device
[9.123068] [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync,
-vsync)
[9.163498] Console: switching to colour frame buffer device 160x50
[9.166503] fb0: inteldrmfb frame buffer device
[9.166505] drm: registered panic notifier
[9.168589] acpi device:07: registered as
Processed: Re: linux-2.6: Removal and reinsertion of floppy or mtdblock device can cause oops
Processing commands for cont...@bugs.debian.org: # Ben Hutchings wrote: # # In any case, these changes are small and # seem low-risk; they were also accepted in stable version 2.6.27.51. tags 593304 + patch fixed-upstream Bug #593304 [linux-2.6] linux-2.6: Removal and reinsertion of floppy or mtdblock device can cause oops Added tag(s) fixed-upstream and patch. fixed 593304 linux-2.6/2.6.28-1 Bug #593304 [linux-2.6] linux-2.6: Removal and reinsertion of floppy or mtdblock device can cause oops Bug Marked as fixed in versions linux-2.6/2.6.28-1. End of message, stopping processing here. Please contact me if you need assistance. -- 593304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593304 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.13158727187637.transcr...@bugs.debian.org
Bug#607194: bugs.debian.org: Computer randomly fails on startup
Hi, Bergen A van wrote: The problem is visible at 21.885 seconds. It does occur randomly! [...] ACPI: EC: Look up EC in DSDT ACPI: BIOS _OSI(Linux) query ignored ACPI Error (psargs-0359): [OSYS] Namespace lookup failure, AE_NOT_FOUND ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.ACEL._STA] (Node 88007fb2dc40), AE_NOT_FOUND [... lots more of the same snipped ...] [Firmware Bug]: ACPI: ACPI brightness control misses _BQC function [Firmware Bug]: ACPI: ACPI brightness control misses _BQC function [...] general protection fault: [#1] SMP [...] Pid: 940, comm: modprobe Not tainted 2.6.32-5-amd64 #1 HP Pavilion dv2 Notebook PC The ACPI tables seem to be broken. Questions: - did this problem arise with an upgrade, or has it always worked this way? If the former, what version of the kernel worked? - how did you install / recover logs? - is your BIOS up to date? - if there's a configuration that allows a stable boot, could you attach output of /usr/share/bug/linux-image-$(uname -r)/script 31 (which gives an overview of hardware and drivers used) and acpidump (which gives a dump of ACPI tables as Linux sees them)? - does a more recent kernel behave the same way? (For example, one can check if it's possible to boot with a wheezy installation CD.) Sorry for the long delay, 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/20110913002732.ga3...@elie.chipublib.org
Processed: Re: sata_mv: frozen/hard reset on 4-port 5041 chip
Processing commands for cont...@bugs.debian.org: # more details in title (in particular that this is an etch - lenny # regression) retitle 524876 sata_mv: timeouts/hard resets on 4-port 5041 chip after upgrade to lenny, using slow drives in md raid Bug #524876 [linux-2.6] sata_mv: frozen/hard reset on 4-port 5041 chip Changed Bug title to 'sata_mv: timeouts/hard resets on 4-port 5041 chip after upgrade to lenny, using slow drives in md raid' from 'sata_mv: frozen/hard reset on 4-port 5041 chip' End of message, stopping processing here. Please contact me if you need assistance. -- 524876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524876 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.131587723728156.transcr...@bugs.debian.org
Processed: Re: linux-image-2.6.26-1-amd64: XFS internal error / xfs_force_shutdown
Processing commands for cont...@bugs.debian.org: # because unreproducible severity 512779 normal Bug #512779 [linux-2.6] linux-image-2.6.26-1-amd64: XFS internal error / xfs_force_shutdown Bug #532386 [linux-2.6] XFS on LVM2 filesystem crashses Severity set to 'normal' from 'important' Severity set to 'normal' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 512779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512779 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.131587732328426.transcr...@bugs.debian.org
Processing of linux-2.6_2.6.32-36_multi.changes
linux-2.6_2.6.32-36_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-36.dsc linux-2.6_2.6.32-36.diff.gz linux-doc-2.6.32_2.6.32-36_all.deb linux-manual-2.6.32_2.6.32-36_all.deb linux-patch-debian-2.6.32_2.6.32-36_all.deb linux-source-2.6.32_2.6.32-36_all.deb linux-support-2.6.32-5_2.6.32-36_all.deb firmware-linux-free_2.6.32-36_all.deb linux-base_2.6.32-36_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1r3kkq-0005jx...@franck.debian.org
Bug#641069: [src:linux-2.6]
Package: src:linux-2.6 --- Please enter the report below this line. --- The log is : Sep 10 04:19:08 debian kernel: [73718.356032] usb 1-7: reset high speed USB device using ehci_hcd and address 4 Sep 10 04:22:52 debian kernel: [73942.740041] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Sep 10 04:23:22 debian kernel: [73973.112043] usb 1-2: reset high speed USB device using ehci_hcd and address 3 Sep 10 04:29:40 debian kernel: [74351.112034] usb 1-2: reset high speed USB device using ehci_hcd and address 2 Sep 10 04:30:45 debian kernel: [74416.112027] usb 1-2: reset high speed USB device using ehci_hcd and address 2 Sep 10 04:32:50 debian kernel: [74541.112044] usb 1-2: reset high speed USB device using ehci_hcd and address 2 Sep 10 04:34:05 debian kernel: [74616.112036] usb 1-2: reset high speed USB device using ehci_hcd and address 2 --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686 Debian Release: 6.0.2 500 stable-updates debian.ens-cachan.fr 500 stable www.debian-multimedia.org 500 stable security.debian.org 500 stable dl.google.com 500 stable debian.ens-cachan.fr 500 proposed-updates debian.ens-cachan.fr --- 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/4e6ee288.6000...@system-linux.net
Bug#641069: [src:linux-2.6]
Le 11/09/2011 12:36, Uwe Kleine-König a écrit : tag 641069 + moreinfo thanks On Sun, Sep 11, 2011 at 10:57:41AM +0200, Laurent Besson wrote: Sep 10 04:14:42 debian kernel: [73453.112032] usb 1-7: reset high speed USB device using ehci_hcd and address 4 Sep 10 04:14:53 debian kernel: [73463.356029] usb 1-7: reset high speed USB device using ehci_hcd and address 4 Sep 10 04:18:57 debian kernel: [73708.112048] usb 1-7: reset high speed USB device using ehci_hcd and address 4 Sep 10 04:19:08 debian kernel: [73718.356032] usb 1-7: reset high speed USB device using ehci_hcd and address 4 It's not clear to me why these messages impose a problem. Can you please describe the problems you have in detail? AFAIK an occasional usb reset shouldn't hurt. Best regards Uwe Hi I'm sorry I forgot to explain what hapened when this log arrived. There's some freeze when copied data from or to this storage (Samsung Wave II) But a friend of mine had the same message for his mouse, and when it hapened the mouse stop moving during 1-2-3-4 seconds... It's difficult to produce this, because it's erratic (sometimes work and after not... ?) A solution on debian is to remove module when I plug my smartphone (then I copied with 1-2Mb/s) , when it's finished I remove my smartphone and reload module... It's not really clean... but works ! For my friend it's different, cause Ubuntu use usbhid managing USB 1... so no solution than changing hardware ! (DELL V420 to V430!) Thank's -- 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/4e6ee5b7.9010...@system-linux.net
Bug#641069: [src:linux-2.6]
If my english is not enough clear you can tell me... I can make more for my english ! Is being French could be an excuse ? :) -- 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/4e6ee888.1030...@system-linux.net
Bug#640672: moving files to arch specific include breaks compilations with -m32
On Tue, Sep 06, 2011 at 03:14:58PM +0100, Ben Hutchings wrote: On Tue, 2011-09-06 at 14:44 +0200, Daniel Bayer wrote: Package: linux-libc-dev Version: 3.0.0-3 Severity: normal File: /usr/include/x86_64-linux-gnu/asm/errno.h since asm/errno.h was moved to the arch specific sub directory it is no longer possible to create 32 Bit Binaries on amd64: | $ echo '#include errno.h' | gcc -E -o - -m32 - | [...] | # 1 /usr/include/bits/errno.h 1 3 4 | # 25 /usr/include/bits/errno.h 3 4 | # 1 /usr/include/linux/errno.h 1 3 4 | In file included from /usr/include/bits/errno.h:25:0, | from /usr/include/errno.h:36, | from stdin:1: | /usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or directory | compilation terminated. I guess with multiarch I should install the i386 deb, too. But this is not yet supported by dpkg in unstable, is it? [...] It's not. And since the kernel uses the same set of header files for 32-bit and 64-bit versions of each architecture, I wonder whether that would make sense. Maybe the right way to do this is: - linux-libc-dev (multiarch: same) becomes a metapackage depending on linux-libc-dev-$SRCARCH - linux-libc-dev-$SRCARCH (not multiarch) provides headers for all architectures built from kernel $SRCARCH, with symlinks I think this entire bug report is based on a misunderstanding of how gcc -m32 is supposed to work. 'gcc -m32' is not guaranteed to work unless the gcc-multilib package is installed; and if gcc-multilib is installed, you get a /usr/include/asm compatibility symlink pointing to /usr/include/$triplet/asm. There are still some problems with this setup, but I don't agree that the issue reported here is one of them and I don't see any reason to change the linux-libc-dev package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
