Bug#633942: linux-image-2.6.39-2-amd64: occasional freeze after resume
Package: linux-2.6 Version: 2.6.39-3 Severity: important My laptop (DELL Latitude E6400) sometimes freezes after resume: I can hear the fan, but the screen remains off and I cannot suspend the laptop again (with Fn+F1). This happened twice in the last 24 hours. I had to switch it off without a clean shutdown. -- Package-specific info: ** Version: Linux version 2.6.39-2-amd64 (Debian 2.6.39-3) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Tue Jul 5 02:51:22 UTC 2011 ** Command line: root=/dev/mapper/xvii-root ro quiet ** Not tainted ** Kernel log: [ 89.977744] sdhci-pci :03:01.2: restoring config space at offset 0x4 (was 0x0, writing 0xf1eff600) [ 89.977749] sdhci-pci :03:01.2: restoring config space at offset 0x3 (was 0x80, writing 0x804010) [ 89.977755] sdhci-pci :03:01.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [ 89.978003] PM: early resume of devices complete after 1.798 msecs [ 89.978067] pci:00: wake-up capability disabled by ACPI [ 89.978073] e1000e :00:19.0: PME# disabled [ 89.978154] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 89.978189] uhci_hcd :00:1a.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 89.978195] uhci_hcd :00:1a.0: setting latency timer to 64 [ 89.978219] usb usb3: root hub lost power or was reset [ 89.978232] uhci_hcd :00:1a.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [ 89.978239] uhci_hcd :00:1a.1: setting latency timer to 64 [ 89.978262] usb usb4: root hub lost power or was reset [ 89.978273] uhci_hcd :00:1a.2: PCI INT C - GSI 22 (level, low) - IRQ 22 [ 89.978278] uhci_hcd :00:1a.2: setting latency timer to 64 [ 89.978311] usb usb5: root hub lost power or was reset [ 89.978331] ehci_hcd :00:1a.7: PCI INT C - GSI 22 (level, low) - IRQ 22 [ 89.978340] ehci_hcd :00:1a.7: setting latency timer to 64 [ 89.978382] HDA Intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [ 89.978393] HDA Intel :00:1b.0: setting latency timer to 64 [ 89.978434] HDA Intel :00:1b.0: irq 47 for MSI/MSI-X [ 89.978467] uhci_hcd :00:1d.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 89.978473] uhci_hcd :00:1d.0: setting latency timer to 64 [ 89.978497] usb usb6: root hub lost power or was reset [ 89.978508] uhci_hcd :00:1d.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [ 89.978514] uhci_hcd :00:1d.1: setting latency timer to 64 [ 89.978537] usb usb7: root hub lost power or was reset [ 89.978548] uhci_hcd :00:1d.2: PCI INT C - GSI 22 (level, low) - IRQ 22 [ 89.978556] uhci_hcd :00:1d.2: setting latency timer to 64 [ 89.978579] usb usb8: root hub lost power or was reset [ 89.978591] ehci_hcd :00:1d.7: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 89.978596] ehci_hcd :00:1d.7: setting latency timer to 64 [ 89.978636] pci :00:1e.0: setting latency timer to 64 [ 89.978649] ahci :00:1f.2: setting latency timer to 64 [ 89.978694] [drm] nouveau :01:00.0: We're back, enabling device... [ 89.978714] nouveau :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 89.978734] nouveau :01:00.0: setting latency timer to 64 [ 89.978742] [drm] nouveau :01:00.0: POSTing device... [ 89.978745] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset 0xD601 [ 89.980668] iwlagn :0c:00.0: RF_KILL bit toggled to disable radio. [ 89.980687] sdhci-pci :03:01.2: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 89.982051] sd 0:0:0:0: [sda] Starting disk [ 90.003567] [drm] nouveau :01:00.0: 0xD7E0: i2c wr fail: -6 [ 90.008929] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset 0xD9B3 [ 90.015269] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset 0xE259 [ 90.015320] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset 0xE34B [ 90.016447] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset 0xE557 [ 90.016453] [drm] nouveau :01:00.0: Parsing VBIOS init table at offset 0xE5BC [ 90.036438] [drm] nouveau :01:00.0: Restoring GPU objects... [ 90.044149] firewire_core: skipped bus generations, destroying all nodes [ 90.044616] dell-wmi: Received unknown WMI event (0x11) [ 90.121933] serial 00:09: activated [ 90.156076] [drm] nouveau :01:00.0: Reinitialising engines... [ 90.156300] [drm] nouveau :01:00.0: Restoring mode... [ 90.300109] ata6: SATA link down (SStatus 0 SControl 300) [ 90.308104] ata5: SATA link down (SStatus 0 SControl 300) [ 90.344065] usb 1-6: reset high speed USB device number 3 using ehci_hcd [ 90.496264] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 90.575401] firewire_core: rediscovered device fw0 [ 90.607116] ata2.00: configured for UDMA/100 [ 90.643317] dell-wmi: Received unknown WMI event (0x11) [ 90.775702] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input16 [ 91.63] input: AT
linux-tools
Hi guys, Could you fix linux-tools package please? Now it depends on linux-tools-3.0.0-rc5 which is virtual. - Alex -- 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/4e2010be.2070...@gmail.com
Bug#631945: HFSC warning issue
On Wed, 2011-07-13 at 01:28 +0200, Michal Soltys wrote: That warning that gets triggered when next_time == 0 in hfsc_schedule_watchdog() implies, that hfsc_dequeue() tried to dequeue a packet, but no leaf had anything eligible for scheduling (realtime criterion) and linksharing was upperlimited. Now if there IS something to dequeue, then I don't see how next_time could possibly be zero - that would mean there's no packet to schedule at all. But if that happened, then hfsc_dequeue() would simply exit at the very beginning due to: if (sch-q.qlen == 0) . So it does look weird (like if something external messed with hfsc's qlen) ... Could it be related with setting a custom device qlen with iproute (wild guess)? Also note - the changes to sch_hfsc.c were pretty minimal since the last kernel that worked for you. You might be searching for something else ... Any idea where we could start searching? Is there any configuration we could try (with upperlimits maybe?) that could help identify or workaround this problem? Thanks, François. -- 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/1310727466.9924.6.ca...@luna.madrid.commsmundi.com
Bug#633961: linux images must conflict with unfixed input-utils
Package: linux-image-2.6.39-2-amd64 Version: 2.6.39-3 Severity: serious Upgrading the kernel without also upgrading input-utils (e.g. when using the version in squeeze or the version currently in testing) makes input-utils unusable (see #609300). After #609300 got fixed, the linux images should therefore add Breaks for all non-fixed versions of input-utils. -- 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/20110715130416.12008.876.reportbug@localhost
Processed: Add the blocking
Processing commands for cont...@bugs.debian.org: block 633961 by 609300 Bug #633961 [linux-image-2.6.39-2-amd64] linux images must conflict with unfixed input-utils Was not blocked by any bugs. Added blocking bug(s) of 633961: 609300 thanks Stopping processing here. Please contact me if you need assistance. -- 633961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633961 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.13107364724404.transcr...@bugs.debian.org
Bug#633738: ip6_tunnel: kernel BUG at net_namespace.c:497
On Thu, 2011-07-14 at 19:03 +0200, Arnaud Patard wrote: Alexander Clouter a...@digriz.org.uk writes: Hi, [ 33.356789] [c02397ec] (net_assign_generic+0x3c/0xbc) from [bf24d3d0] (ip6_tnl_init_net+0x98/0x19c [ip6_tunnel]) [ 33.367378] [bf24d3d0] (ip6_tnl_init_net+0x98/0x19c [ip6_tunnel]) from [c023942c] (register_pernet_operations+0x40/0xf4) [ 33.378658] [c023942c] (register_pernet_operations+0x40/0xf4) from [c02395c0] (register_pernet_device+0x20/0x54) [ 33.389240] [c02395c0] (register_pernet_device+0x20/0x54) from [bf25200c] (ip6_tunnel_init+0xc/0x84 [ip6_tunnel]) [ 33.399915] [bf25200c] (ip6_tunnel_init+0xc/0x84 [ip6_tunnel]) from [c002734c] (do_one_initcall+0x6c/0x1e4) [ 33.410062] [c002734c] (do_one_initcall+0x6c/0x1e4) from [c00738ec] (sys_init_module+0xc0/0x1f0) [ 33.419241] [c00738ec] (sys_init_module+0xc0/0x1f0) from [c0027ea0] (ret_fast_syscall+0x0/0x28) [ 33.428333] Code: e1a01000 e59f000c eb0a2ec7 e3a03000 (e5833000) [ 33.434502] ---[ end trace bf87ce5c849aaa8e ]--- Segmentation fault Failed to bring up iptv-shironeko. This is a regression as I was able to do all this with earlier kernels; definately 2.6.32-34squeeze1. hm... looks like it's from the backport of mainline commit d5aa407f59f5b83d2c50ec88f5bf56d40f1f8978. It's changing a call to register_pernet_gen_device() into a call to register_pernet_device(). [...] Right. And it looks like this affects lenny as well (since 2.6.26-26lenny3). Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Bug#627704: Realtek Ethernet adapters (r8169 driver)
On Thu, 2011-07-14 at 13:46 +0200, Markus Schade wrote: Hi, would it be possible to also include support for the 8168/8111E version? While the nic is working more or less, there seems to be a bit more setup necessary. Commits are 01dc7fec4025f6bb72b6b98ec88b375346b6dbbb and probably also 15ecd039b7182d725f4294e01f2fb12c3a88db17 Maybe, yes. I'll definitely look at changes from 2.6.38 to 3.0. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Bug#632187: megaraid vs i2o for PCI device ID 101e:1960
On Thu, 2011-07-14 at 11:16 +0200, Alexander Schier wrote: On 07/14/2011 09:19 AM, Alexander Schier wrote: Hi! On 07/13/2011 06:29 AM, Ben Hutchings wrote: Can you try adding 'blacklist=i2o_core' to the kernel parameters, so only the megaraid driver is used? We will try this. Now it works, when i2o_core is blacklisted. Alexander reported in http://bugs.debian.org/632187 that the kernel took a very long time to boot, and the log showed first i2o_core and then megaraid failing to probe a device (ID 101e:1960). But above he reports that megaraid is able to probe it successfully if i2o_core didn't break it first. Should this device be blacklisted from i2o_core? Are there likely other MegaRAID devices that use the I2O PCI class but don't work with this generic driver? Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Processed: bug 632187 is forwarded to linux-ker...@vger.kernel.org
Processing commands for cont...@bugs.debian.org: forwarded 632187 linux-ker...@vger.kernel.org Bug #632187 [linux-2.6] linux-image-2.6.32-5-amd64: kernel hangs for 120 seconds while booting Set Bug forwarded-to-address to 'linux-ker...@vger.kernel.org'. thanks Stopping processing here. Please contact me if you need assistance. -- 632187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632187 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.131074021620416.transcr...@bugs.debian.org
Bug#627655: linux-image-2.6.39-1-686-pae: missing NFS4.1 / pNFS support
On Wed, 2011-07-13 at 15:27 +0200, Paul Millar wrote: Hi Ben, On Monday 23 May 2011 18:48:56 Ben Hutchings wrote: [wishlist: NFS-4.1 / pNFS support] Anyway, I have no objection to enabling this unless it is likely to cause regressions for other NFS users. Is there any news on enabling NFS v4.1? Can I do anything to help? No news. The question remains, what the cost may be to other NFS users. Certainly NFS v4.1 is not a minor change, and it adds a lot of new code to the nfs module. I had a look at what RH is doing with this and noticed that in RHEL 6 they only enabled it for x86_64. This does suggest that it may be too expensive for smaller systems, but maybe it's just a random choice. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Bug#633722: task jsvc:7903 blocked for more than 120 seconds
On Wed, 2011-07-13 at 09:24 +0200, Giuseppe Sacco wrote: Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Hi, the system keep logging messages like the following one. Is this something I should report here? Is there any action I should do? The process jsvc is a tomcat55 instance, the one shipped by Debian. [...] Can you tell whether the disk(s) are busy while this happens? Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Bug#633961: linux images must conflict with unfixed input-utils
On Fri, 2011-07-15 at 16:04 +0300, Adrian Bunk wrote: Package: linux-image-2.6.39-2-amd64 Version: 2.6.39-3 Severity: serious This is not RC for the kernel. Upgrading the kernel without also upgrading input-utils (e.g. when using the version in squeeze or the version currently in testing) makes input-utils unusable (see #609300). After #609300 got fixed, the linux images should therefore add Breaks for all non-fixed versions of input-utils. Maybe. But first you have to make input-utils work with both the kernel version in squeeze and the version in sid. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Processed: severity of 633961 is important
Processing commands for cont...@bugs.debian.org: severity 633961 important Bug #633961 [linux-image-2.6.39-2-amd64] linux images must conflict with unfixed input-utils Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 633961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633961 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.131074117423706.transcr...@bugs.debian.org
Bug#632187: megaraid vs i2o for PCI device ID 101e:1960
Should this device be blacklisted from i2o_core? Are there likely other MegaRAID devices that use the I2O PCI class but don't work with this generic driver? I²O will probe I²O class devices. How well it works depends upon the firmware version of the specific board. The fix in this case is either updated firmware, or to go into the configuration for the board and turn off I2O support in the bios config. Alan -- 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/20110715154832.09647...@lxorguk.ukuu.org.uk
Bug#633961: linux images must conflict with unfixed input-utils
On Fri, Jul 15, 2011 at 03:45:58PM +0100, Ben Hutchings wrote: On Fri, 2011-07-15 at 16:04 +0300, Adrian Bunk wrote: Package: linux-image-2.6.39-2-amd64 Version: 2.6.39-3 Severity: serious This is not RC for the kernel. Upgrade makes another package completely unusable when not forcing an upgrade of that is not RC? Upgrading the kernel without also upgrading input-utils (e.g. when using the version in squeeze or the version currently in testing) makes input-utils unusable (see #609300). After #609300 got fixed, the linux images should therefore add Breaks for all non-fixed versions of input-utils. Maybe. But first you have to make input-utils work with both the kernel version in squeeze and the version in sid. A versioned build-dependency on linux-libc-dev and a breaks for older kernel images seems to be the minimal fix. Ben. cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- 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/20110715154159.ge4...@localhost.pp.htv.fi
Bug#633722: task jsvc:7903 blocked for more than 120 seconds
Il giorno ven, 15/07/2011 alle 15.35 +0100, Ben Hutchings ha scritto: On Wed, 2011-07-13 at 09:24 +0200, Giuseppe Sacco wrote: Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Hi, the system keep logging messages like the following one. Is this something I should report here? Is there any action I should do? The process jsvc is a tomcat55 instance, the one shipped by Debian. [...] Can you tell whether the disk(s) are busy while this happens? Sure: all disks were spinning a lot. They are in a raid10 volume of a SATA raid controller. Postgresql processes (used by the tomcat instance) are quite often in state D, but tomcat processes are normally sleeping. Bye, Giuseppe -- 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/1310744076.4442.9.camel@scarafaggio
Bug#627019: linux-2.6: linux-image-3.0.0-rc6-686-pae using debug=3 on the kernel commandline
Package: linux-2.6 Followup-For: Bug #627019 linux-image-3.0.0-rc6-686-pae If I add debug=3 to the kenrnel commandline I'm able to boot about 90% of the time. Instead of 5 or 6 different types of fatal kernel errors I now see only one type of kernel panic about 10% of the time. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-rc6-686-pae (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/bash [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.0.0-rc6-686-pae (Debian 3.0.0~rc6-1~experimental.1) (m...@debian.org) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Wed Jul 6 16:49:19 UTC 2011 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ef2fc00 (usable) [0.00] BIOS-e820: 3ef2fc00 - 3ef3 (ACPI NVS) [0.00] BIOS-e820: 3ef3 - 3ef4 (ACPI data) [0.00] BIOS-e820: 3ef4 - 3eff (ACPI NVS) [0.00] BIOS-e820: 3eff - 3f00 (reserved) [0.00] BIOS-e820: fecf - fecf1000 (reserved) [0.00] BIOS-e820: fed2 - feda (reserved) [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] DMI 2.3 present. [0.00] DMI: /D865GRH, BIOS BF86510A.86A.0077.P25.0508040031 08/04/2005 [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] last_pfn = 0x3ef2f max_arch_pfn = 0x100 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-E uncachable [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FC000 write-back [0.00] 1 disabled [0.00] 2 disabled [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] found SMP MP-table at [c00ff780] ff780 [0.00] initial memory mapped : 0 - 01a0 [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 [0.00] init_memory_mapping: -379fe000 [0.00] 00 - 20 page 4k [0.00] 20 - 003780 page 2M [0.00] 003780 - 00379fe000 page 4k [0.00] kernel direct mapping tables up to 379fe000 @ 19fa000-1a0 [0.00] RAMDISK: 36cb8000 - 37654000 [0.00] ACPI: RSDP 000f61e0 00014 (v00 ACPIAM) [0.00] ACPI: RSDT 3ef3 00038 (v01 INTEL D865GRH 20050804 MSFT 0097) [0.00] ACPI: FACP 3ef30200 00081 (v02 INTEL D865GRH 20050804 MSFT 0097) [0.00] ACPI: DSDT 3ef30370 04305 (v01 INTEL D865GRH 0001 MSFT 010D) [0.00] ACPI: FACS 3ef4 00040 [0.00] ACPI: APIC 3ef30300 00068 (v01 INTEL D865GRH 20050804 MSFT 0097) [0.00] ACPI: ASF! 3ef34680 00099 (v16 LEGEND I865PASF 0001 MSFT 010D) [0.00] ACPI: TCPA 3ef34719 00034 (v01 INTEL TBLOEMID 0001 MSFT 0097) [0.00] ACPI: WDDT 3ef3474d 00040 (v01 INTEL OEMWDDT 0001 MSFT 010D) [0.00] ACPI: Local APIC address 0xfee0 [0.00] 117MB HIGHMEM available. [0.00] 889MB LOWMEM available. [0.00] mapped low ram: 0 - 379fe000 [0.00] low ram: 0 - 379fe000 [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] Normal 0x1000 - 0x000379fe [0.00] HighMem 0x000379fe - 0x0003ef2f [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 - 0x009f [0.00] 0: 0x0100 - 0x0003ef2f [0.00] On node 0 totalpages: 257726 [0.00] free_area_init_node: node 0, pgdat c141e9c0, node_mem_map f64d8200 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 3951 pages, LIFO batch:0 [0.00] Normal zone: 1748 pages used for memmap [0.00] Normal zone: 221994 pages, LIFO batch:31 [0.00] HighMem zone: 235 pages used for memmap [0.00] HighMem zone: 29766 pages, LIFO batch:7 [
Bug#633961: linux images must conflict with unfixed input-utils
On Fri, Jul 15, 2011 at 06:41:59PM +0300, Adrian Bunk wrote: On Fri, Jul 15, 2011 at 03:45:58PM +0100, Ben Hutchings wrote: On Fri, 2011-07-15 at 16:04 +0300, Adrian Bunk wrote: Package: linux-image-2.6.39-2-amd64 Version: 2.6.39-3 Severity: serious This is not RC for the kernel. Upgrade makes another package completely unusable when not forcing an upgrade of that is not RC? Depends on the relative importance of the packages. Upgrading the kernel without also upgrading input-utils (e.g. when using the version in squeeze or the version currently in testing) makes input-utils unusable (see #609300). After #609300 got fixed, the linux images should therefore add Breaks for all non-fixed versions of input-utils. Maybe. But first you have to make input-utils work with both the kernel version in squeeze and the version in sid. A versioned build-dependency on linux-libc-dev and a breaks for older kernel images seems to be the minimal fix. This is wrong on so many levels. 1. There is no way to declare relations to 'all kernel packages'. 2. input-utils doesn't break them! They don't depend on input-utils; they'll keep on running. 3. You know how people complain about udev and kernel upgrade ordering dependencies? You're proposing to do the same thing. I suspect that the correct way to deal with this may be to build input-utils from the linux-2.6 source package and add some sort of wrapper in linux-base to select the right version (like we do for perf). Or, you change the program to check which protocol version to use at run-time. 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/20110715173041.gt29...@decadent.org.uk
Bug#633722: marked as done (task jsvc:7903 blocked for more than 120 seconds)
Your message dated Fri, 15 Jul 2011 18:36:37 +0100 with message-id 20110715173637.gu29...@decadent.org.uk and subject line Re: Bug#633722: task jsvc:7903 blocked for more than 120 seconds has caused the Debian Bug report #633722, regarding task jsvc:7903 blocked for more than 120 seconds 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.) -- 633722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Hi, the system keep logging messages like the following one. Is this something I should report here? Is there any action I should do? The process jsvc is a tomcat55 instance, the one shipped by Debian. Thanks, Giuseppe Jul 13 08:52:46 agenzia-f07 kernel: [432397.142910] INFO: task jsvc:7903 blocked for more than 120 seconds. Jul 13 08:52:46 agenzia-f07 kernel: [432397.142946] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jul 13 08:52:46 agenzia-f07 kernel: [432397.142990] jsvc D 0 7903 7894 0x0002 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143023] 88007f3654c0 0082 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143073] 88000382fc00 7c7a1c78 f9e0 880037aebfd8 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143123] 00015780 00015780 880037844db0 8800378450a8 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143173] Call Trace: Jul 13 08:52:46 agenzia-f07 kernel: [432397.143204] [a015626b] ? dm_table_unplug_all+0x3b/0x8f [dm_mod] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143236] [8110d294] ? sync_buffer+0x0/0x40 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143264] [812f736a] ? io_schedule+0x73/0xb7 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143290] [8110d2cf] ? sync_buffer+0x3b/0x40 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143317] [812f7755] ? __wait_on_bit_lock+0x3f/0x84 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143345] [8110d294] ? sync_buffer+0x0/0x40 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143371] [812f7805] ? out_of_line_wait_on_bit_lock+0x6b/0x77 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143401] [81064c7c] ? wake_bit_function+0x0/0x23 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143430] [a0174030] ? do_get_write_access+0x6f/0x40f [jbd] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143460] [8110c86a] ? __getblk+0x26/0x29a Jul 13 08:52:46 agenzia-f07 kernel: [432397.143486] [810678d6] ? hrtimer_try_to_cancel+0x3a/0x43 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143516] [a01743f2] ? journal_get_write_access+0x22/0x33 [jbd] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143549] [a01953b3] ? __ext3_journal_get_write_access+0x1e/0x47 [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143596] [a018919d] ? ext3_reserve_inode_write+0x3e/0x75 [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143641] [a01891f5] ? ext3_mark_inode_dirty+0x21/0x3c [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143672] [a0189347] ? ext3_dirty_inode+0x63/0x7b [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143701] [811075f5] ? __mark_inode_dirty+0x25/0x14a Jul 13 08:52:46 agenzia-f07 kernel: [432397.143730] [810feb47] ? file_update_time+0x101/0x130 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143759] [810ca8fd] ? do_wp_page+0x6cd/0x707 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143787] [8100f6ed] ? __switch_to+0x1d6/0x297 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143815] [810cc331] ? handle_mm_fault+0x7aa/0x80f Jul 13 08:52:46 agenzia-f07 kernel: [432397.143843] [81016529] ? read_tsc+0xa/0x20 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143870] [812faa96] ? do_page_fault+0x2e0/0x2fc Jul 13 08:52:46 agenzia-f07 kernel: [432397.143898] [812f8935] ? page_fault+0x25/0x30 ---End Message--- ---BeginMessage--- On Fri, Jul 15, 2011 at 05:34:36PM +0200, Giuseppe Sacco wrote: Il giorno ven, 15/07/2011 alle 15.35 +0100, Ben Hutchings ha scritto: On Wed, 2011-07-13 at 09:24 +0200, Giuseppe Sacco wrote: Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Hi, the system keep logging messages like the following one. Is this something I should report here? Is there any action I should do? The process jsvc is a tomcat55 instance, the one shipped by Debian. [...] Can you tell whether
Bug#633738: ip6_tunnel: kernel BUG at net_namespace.c:497
tags 633738 + lenny thanks On Fri, Jul 15, 2011 at 03:15:32PM +0100, Ben Hutchings wrote: On Thu, 2011-07-14 at 19:03 +0200, Arnaud Patard wrote: Alexander Clouter a...@digriz.org.uk writes: Hi, [ 33.356789] [c02397ec] (net_assign_generic+0x3c/0xbc) from [bf24d3d0] (ip6_tnl_init_net+0x98/0x19c [ip6_tunnel]) [ 33.367378] [bf24d3d0] (ip6_tnl_init_net+0x98/0x19c [ip6_tunnel]) from [c023942c] (register_pernet_operations+0x40/0xf4) [ 33.378658] [c023942c] (register_pernet_operations+0x40/0xf4) from [c02395c0] (register_pernet_device+0x20/0x54) [ 33.389240] [c02395c0] (register_pernet_device+0x20/0x54) from [bf25200c] (ip6_tunnel_init+0xc/0x84 [ip6_tunnel]) [ 33.399915] [bf25200c] (ip6_tunnel_init+0xc/0x84 [ip6_tunnel]) from [c002734c] (do_one_initcall+0x6c/0x1e4) [ 33.410062] [c002734c] (do_one_initcall+0x6c/0x1e4) from [c00738ec] (sys_init_module+0xc0/0x1f0) [ 33.419241] [c00738ec] (sys_init_module+0xc0/0x1f0) from [c0027ea0] (ret_fast_syscall+0x0/0x28) [ 33.428333] Code: e1a01000 e59f000c eb0a2ec7 e3a03000 (e5833000) [ 33.434502] ---[ end trace bf87ce5c849aaa8e ]--- Segmentation fault Failed to bring up iptv-shironeko. This is a regression as I was able to do all this with earlier kernels; definately 2.6.32-34squeeze1. hm... looks like it's from the backport of mainline commit d5aa407f59f5b83d2c50ec88f5bf56d40f1f8978. It's changing a call to register_pernet_gen_device() into a call to register_pernet_device(). [...] Right. And it looks like this affects lenny as well (since 2.6.26-26lenny3). Yep, I used basically the same backport for both updates. Apologies for the regression. Alexander, I'd appreciate it if you could test Arnaud's proposed fix in your configuration to help verify that no other issues remain. -- 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/20110715192439.gb30...@dannf.org
Processed: Re: Bug#633738: ip6_tunnel: kernel BUG at net_namespace.c:497
Processing commands for cont...@bugs.debian.org: tags 633738 + lenny Bug #633738 [linux-2.6] ip6_tunnel: kernel BUG at net_namespace.c:497 Added tag(s) lenny. thanks Stopping processing here. Please contact me if you need assistance. -- 633738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633738 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.131075788325857.transcr...@bugs.debian.org
Bug#633738: ip6_tunnel: kernel BUG at net_namespace.c:497
* dann frazier da...@dannf.org [2011-07-15 13:24:39-0600]: tags 633738 + lenny This is a regression as I was able to do all this with earlier kernels; definately 2.6.32-34squeeze1. hm... looks like it's from the backport of mainline commit d5aa407f59f5b83d2c50ec88f5bf56d40f1f8978. It's changing a call to register_pernet_gen_device() into a call to register_pernet_device(). [...] Right. And it looks like this affects lenny as well (since 2.6.26-26lenny3). Yep, I used basically the same backport for both updates. Apologies for the regression. Alexander, I'd appreciate it if you could test Arnaud's proposed fix in your configuration to help verify that no other issues remain. I can test it on an orion5x (armel) platform this weekend (and amd64), but on if you wanted it tested on a kirkwood device I cannot do that till Tuesday at the earliest. Looks to me that an amd64 test would be the most straight forward to do as it is not an ARM specific bug. Cheers -- Alexander Clouter .sigmonster says: BOFH excuse #412: Radial Telemetry Infiltration -- 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/20110715210035.GW4530@chipmunk
Bug#633738: ip6_tunnel: kernel BUG at net_namespace.c:497
On Fri, 2011-07-15 at 22:00 +0100, Alexander Clouter wrote: * dann frazier da...@dannf.org [2011-07-15 13:24:39-0600]: tags 633738 + lenny This is a regression as I was able to do all this with earlier kernels; definately 2.6.32-34squeeze1. hm... looks like it's from the backport of mainline commit d5aa407f59f5b83d2c50ec88f5bf56d40f1f8978. It's changing a call to register_pernet_gen_device() into a call to register_pernet_device(). [...] Right. And it looks like this affects lenny as well (since 2.6.26-26lenny3). Yep, I used basically the same backport for both updates. Apologies for the regression. Alexander, I'd appreciate it if you could test Arnaud's proposed fix in your configuration to help verify that no other issues remain. I can test it on an orion5x (armel) platform this weekend (and amd64), but on if you wanted it tested on a kirkwood device I cannot do that till Tuesday at the earliest. Looks to me that an amd64 test would be the most straight forward to do as it is not an ARM specific bug. Indeed not. Of course, you should verify that it does affect amd64 before testing that the fix works there. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Processed: bug 632231 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=38682
Processing commands for cont...@bugs.debian.org: forwarded 632231 https://bugzilla.kernel.org/show_bug.cgi?id=38682 Bug #632231 [linux-2.6] linux-image-3.0.0-rc5-amd64: B43 module do not work properly when I turn WiFi on after reboot Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38682'. thanks Stopping processing here. Please contact me if you need assistance. -- 632231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632231 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.131076504419839.transcr...@bugs.debian.org
Bug#632212: linux-image-2.6.39-2-686-pae: kernel locks up when starting udev, upon graphics mode switch
On Thu, 2011-06-30 at 16:59 +0200, Attila Kinali wrote: Package: linux-2.6 Version: 2.6.39-2 Severity: important I just upgraded my desktop from stable to testing and got the current 2.6.39.2 kernel package installed. During the boot process, when udev is started, the kernel switches from text mode into graphics mode. After this, the image on the screen is completely grabled (looks like the graphics card is using uninitialized memory as frame buffer, ie mostly noise with some images from earlier in the boot process visible in some corners) and locks up completely. [...] Can you test Linux 3.0-rc7, as packaged in experimental? You may also need to install the firmware for this card, which is included in firmware-linux-nonfree. This is definitely required for 3D acceleration and may be needed for some other functionality. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Processed: tagging 632212
Processing commands for cont...@bugs.debian.org: tags 632212 + moreinfo Bug #632212 [linux-2.6] linux-image-2.6.39-2-686-pae: kernel locks up when starting udev, upon graphics mode switch Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 632212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632212 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.131076585723700.transcr...@bugs.debian.org
Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically
Forwarded Message From: Shayan Mansuri shayanmans...@yahoo.com Reply-to: Shayan Mansuri shayanmans...@yahoo.com To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically Date: Wed, 29 Jun 2011 14:21:20 -0700 (PDT) in 2.6.32-5-amd64 #1 SMP grep . /sys/class/rfkill/*/* /sys/class/rfkill/rfkill1/claim:0 /sys/class/rfkill/rfkill1/index:1 /sys/class/rfkill/rfkill1/name:dell-wifi /sys/class/rfkill/rfkill1/persistent:0 /sys/class/rfkill/rfkill1/state:1 /sys/class/rfkill/rfkill1/type:wlan /sys/class/rfkill/rfkill1/uevent:RFKILL_NAME=dell-wifi /sys/class/rfkill/rfkill1/uevent:RFKILL_TYPE=wlan /sys/class/rfkill/rfkill1/uevent:RFKILL_STATE=1 /sys/class/rfkill/rfkill2/claim:0 /sys/class/rfkill/rfkill2/index:2 /sys/class/rfkill/rfkill2/name:dell-bluetooth /sys/class/rfkill/rfkill2/persistent:0 /sys/class/rfkill/rfkill2/state:1 /sys/class/rfkill/rfkill2/type:bluetooth /sys/class/rfkill/rfkill2/uevent:RFKILL_NAME=dell-bluetooth /sys/class/rfkill/rfkill2/uevent:RFKILL_TYPE=bluetooth /sys/class/rfkill/rfkill2/uevent:RFKILL_STATE=1 /sys/class/rfkill/rfkill3/claim:0 /sys/class/rfkill/rfkill3/index:3 /sys/class/rfkill/rfkill3/name:phy0 /sys/class/r fkill/rfkill3/persistent:0 /sys/class/rfkill/rfkill3/state:1 /sys/class/rfkill/rfkill3/type:wlan /sys/class/rfkill/rfkill3/uevent:RFKILL_NAME=phy0 /sys/class/rfkill/rfkill3/uevent:RFKILL_TYPE=wlan /sys/class/rfkill/rfkill3/uevent:RFKILL_STATE=1 /sys/class/rfkill/rfkill4/claim:0 /sys/class/rfkill/rfkill4/index:4 /sys/class/rfkill/rfkill4/name:hci0 /sys/class/rfkill/rfkill4/persistent:0 /sys/class/rfkill/rfkill4/state:1 /sys/class/rfkill/rfkill4/type:bluetooth /sys/class/rfkill/rfkill4/uevent:RFKILL_NAME=hci0 /sys/class/rfkill/rfkill4/uevent:RFKILL_TYPE=bluetooth /sys/class/rfkill/rfkill4/uevent:RFKILL_STATE=1 ~ $uname -a Linux keivan-laptop 2.6.39-2-amd64 #1 SMP Wed Jun 8 11:01:04 UTC 2011 x86_64 GNU/Linux ~ $ grep . /sys/class/rfkill/*/* /sys/class/rfkill/rfkill0/claim:0 /sys/class/rfkill/rfkill0/hard:0 /sys/class/rfkill/rfkill0/index:0 /sys/class/rfkill/rfkill0/name:dell-wifi /sys/class/rfkill/rfkill0/persistent:0 /sys/class/rfkill/rfkill0/soft:1 /sys/class/rfkill/rfkill0/state:0 /sys/class/rfkill/rfkill0/type:wlan /sys/class/rfkill/rfkill0/uevent:RFKILL_NAME=dell-wifi /sys/class/rfkill/rfkill0/uevent:RFKILL_TYPE=wlan /sys/class/rfkill/rfkill0/uevent:RFKILL_STATE=0 /sys/class/rfkill/rfkill1/claim:0 /sys/class/rfkill/rfkill1/hard:0 /sys/class/rfkill/rfkill1/index:1 /sys/class/rfkill/rfkill1/name:dell-bluetooth /sys/class/rfkill/rfkill1/persistent:0 /sys/class/rfkill/rfkill1/soft:1 /sys/class/rfkill/rfkill1/state:0 /sys/class/rfkill/rfkill1/type:bluetooth /sys/class/rfkill/rfkill1/uevent:RFKILL_NAME=dell-bluetooth /sys/class/rfkill/rfkill1/uevent:RFKILL_TYPE=bluetooth /sys/class/rfkill/rfkill1/uevent :RFKILL_STATE=0 /sys/class/rfkill/rfkill3/claim:0 /sys/class/rfkill/rfkill3/hard:1 /sys/class/rfkill/rfkill3/index:3 /sys/class/rfkill/rfkill3/name:phy0 /sys/class/rfkill/rfkill3/persistent:0 /sys/class/rfkill/rfkill3/soft:0 /sys/class/rfkill/rfkill3/state:2 /sys/class/rfkill/rfkill3/type:wlan /sys/class/rfkill/rfkill3/uevent:RFKILL_NAME=phy0 /sys/class/rfkill/rfkill3/uevent:RFKILL_TYPE=wlan /sys/class/rfkill/rfkill3/uevent:RFKILL_STATE=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/1310765922.8783.304.camel@localhost
Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically
I see you've also reported a bug at https://bugzilla.kernel.org/show_bug.cgi?id=38682. Based on the answer to that, I think that your Debian bug reports #632064 and #632231 are related to a single bug in the dell-laptop driver. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Processed: reassign 632231 to src:linux-2.6, forcibly merging 632064 632231
Processing commands for cont...@bugs.debian.org: reassign 632231 src:linux-2.6 3.0.0~rc5-1~experimental.1 Bug #632231 [linux-2.6] linux-image-3.0.0-rc5-amd64: B43 module do not work properly when I turn WiFi on after reboot Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 3.0.0~rc5-1~experimental.1. Bug #632231 [src:linux-2.6] linux-image-3.0.0-rc5-amd64: B43 module do not work properly when I turn WiFi on after reboot Bug Marked as found in versions linux-2.6/3.0.0~rc5-1~experimental.1. forcemerge 632064 632231 Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically Bug#632231: linux-image-3.0.0-rc5-amd64: B43 module do not work properly when I turn WiFi on after reboot Forcibly Merged 632064 632231. thanks Stopping processing here. Please contact me if you need assistance. -- 632064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632064 632231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632231 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.131076615525031.transcr...@bugs.debian.org
Processed: bug 632231 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=38682
Processing commands for cont...@bugs.debian.org: forwarded 632231 https://bugzilla.kernel.org/show_bug.cgi?id=38682 Bug #632231 [src:linux-2.6] linux-image-3.0.0-rc5-amd64: B43 module do not work properly when I turn WiFi on after reboot Bug #632064 [src:linux-2.6] linux-headers-2.6-amd64: Bluetooth turns off automatically Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38682'. Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=38682'. thanks Stopping processing here. Please contact me if you need assistance. -- 632231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632231 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.131076647125968.transcr...@bugs.debian.org
Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically
Yes. I can confirm. blacklisting the dell-laptop module solves this problem too. Thanks. From: Ben Hutchings b...@decadent.org.uk To: 632064-submit...@bugs.debian.org Cc: 632...@bugs.debian.org Sent: Saturday, July 16, 2011 2:11 AM Subject: Bug#632064: linux-headers-2.6-amd64: Bluetooth turns off automatically I see you've also reported a bug at https://bugzilla.kernel.org/show_bug.cgi?id=38682. Based on the answer to that, I think that your Debian bug reports #632064 and #632231 are related to a single bug in the dell-laptop driver. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
