Re: Bug#613317: dmesg + Xorg logs wanted
2011/3/13 Eddy Petrișor eddy.petri...@gmail.com: On 11.03.2011 12:55, Eddy Petrișor wrote: Hello, I see Brad has a similar problem on the official Debian linux kernel. I have just managed to compile the current vanilla 2.6.38+ version and installed it on my laptop. I will report about the results, either way they turn out. If necessary, I might do a bisect, but I hope someone with more expertise than myself will help us reduce the search area for the cause of the issue. I don't seem to experience the problem anymore with the vanilla 2.6.38 kernel (HEAD is git version 35d34df7). Spoke too soon. I've seen the problem after the 3rd or 4th hibernate-resume cycle (no reboot). Please tell me if I should try a bisect. Maybe I should try an older kernel... -- Regards, EddyP = Imagination is more important than knowledge A.Einstein -- 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/aanlktikoowuk1zbgtpp2ctn8fup6d96tkx6n-ntea...@mail.gmail.com
Bug#618309: linux-image-2.6-686: Comedi jr3_pci crash by incorrect ioremap call
Package: linux-image-2.6-686 Severity: important Tags: patch The Comedi drivers has a module jr3_pci for an specific kind of analog cards. This driver, when is loading crash with this message: [6.531366] comedi: module is from the staging directory, the quality is unknown, you have been warned. [6.580157] comedi: version 0.7.76 - http://www.comedi.org [6.637867] jr3_pci: module is from the staging directory, the quality is unknown, you have been warned. [6.639647] comedi0: jr3_pci [6.639672] resource map sanity check conflict: 0xfb00 0xfb1f 0xfb00 0xfb0f :04:02.0 [6.639676] [ cut here ] [6.639687] WARNING: at /build/buildd-linux-2.6_2.6.32-30-i386- UYhWt7/linux-2.6-2.6.32/debian/build/source_i386_none/arch/x86/mm/ioremap.c:135 __ioremap_caller+0x65/0x254() [6.639698] Hardware name: P4SCT [6.639701] Info: mapping multiple BARs. Your kernel is fine. [6.639705] Modules linked in: jr3_pci(C+) videobuf_core(+) btcx_risc tveeprom comedi(C) nouveau ttm wis_tw2804 drm_kms_helper rng_core drm i2c_algo_bit i6300esb shpchp i2c_i801 parport_pc snd_usb_audio go7007_usb pci_hotplug parport snd_usb_lib go7007 snd_hwdep videodev snd_seq_midi v4l1_compat button snd_rawmidi snd_go7007 snd_seq_midi_event snd_pcm_oss evdev pcspkr processor snd_seq snd_mixer_oss snd_pcm snd_timer snd_seq_device snd_page_alloc i2c_core snd soundcore ext4 mbcache jbd2 crc16 sg sr_mod cdrom fan sd_mod crc_t10dif ata_generic uhci_hcd ohci_hcd firewire_ohci ata_piix thermal firewire_core libata floppy e1000 ehci_hcd crc_itu_t thermal_sys scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] [6.639804] Pid: 635, comm: modprobe Tainted: G C 2.6.32-5-686 #1 [6.639808] Call Trace: [6.639818] [c10303fd] ? warn_slowpath_common+0x5e/0x8a [6.639827] [c103045b] ? warn_slowpath_fmt+0x26/0x2a [6.639834] [c101bbd0] ? __ioremap_caller+0x65/0x254 [6.639844] [c11449a6] ? __pci_request_selected_regions+0x25/0x57 [6.639850] [c101be7a] ? ioremap_nocache+0xd/0xf [6.639859] [f7cee777] ? jr3_pci_attach+0x4e3/0x506 [jr3_pci] [6.639867] [f7cee777] ? jr3_pci_attach+0x4e3/0x506 [jr3_pci] [6.639878] [f7c956ee] ? comedi_device_attach+0x96/0x31e [comedi] [6.639886] [f7c95aa2] ? comedi_auto_config+0x12c/0x171 [comedi] [6.639896] [f7c95b23] ? comedi_pci_auto_config+0x26/0x2a [comedi] [6.639905] [c1145fa5] ? local_pci_probe+0xb/0xc [6.639912] [c11468ef] ? pci_device_probe+0x41/0x63 [6.639921] [c11b2dee] ? driver_probe_device+0x8a/0x11e [6.639927] [c11b2ec2] ? __driver_attach+0x40/0x5b [6.639934] [c11b2831] ? bus_for_each_dev+0x37/0x5f [6.639942] [c11b2cc1] ? driver_attach+0x11/0x13 [6.639949] [c11b2e82] ? __driver_attach+0x0/0x5b [6.639955] [c11b22f9] ? bus_add_driver+0x99/0x1c5 [6.639962] [c11b30f3] ? driver_register+0x87/0xe0 [6.639969] [c1146ac0] ? __pci_register_driver+0x33/0x89 [6.639977] [f7c3e000] ? driver_jr3_pci_init_module+0x0/0x2d [jr3_pci] [6.639985] [c100113e] ? do_one_initcall+0x55/0x155 [6.639992] [c1057449] ? sys_init_module+0xa7/0x1d7 [6.640060] [c10030fb] ? sysenter_do_call+0x12/0x28 [6.640066] ---[ end trace 659b2733e74ceac3 ]--- [6.640368] p-channel f979 f978 (1) [6.640375] p-channel f981 f978 (9) [6.640383] jr3_pci :04:02.0: firmware: requesting comedi/jr3pci.idm [6.783020] Loading#0 131c bytes at 0004 [6.788516] Loading#0 0002 bytes at [6.788522] Loading#1 131c bytes at 0004 [6.793976] Loading#1 0002 bytes at [6.793990] Firmare load 0 [6.825015] Copyright JR3 1993-2000 I have contacted with upstream that confirm the bug and send a patch [1]. Please, apply it to the next upgrade of the kernel image. Thanks, Best regards, Leo [1] https://patchwork.kernel.org/patch/629011/ -- System Information: Debian Release: 6.0 Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201103140952.55004@alaxarxa.net
Bug#618319: linux-image-2.6.37-2-amd64: Framebuffer issues with RV620
Package: linux-2.6 Version: 2.6.37-2 Severity: normal As soon as the kernel switches to framebuffer mode on 2.6.37-2-amd64 the display becomes unrecoverably corrupted though everything appears to continue to run fine and a reboot can be initiated. With 2.6.32-5-amd64 the display appears fine. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Precision WorkStation T7500 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A07 board_vendor: Dell Inc. board_name: 06FW8P board_version: A00 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) Subsystem: Dell Device [1028:026d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 11 Capabilities: access denied 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=02, sec-latency=0 Memory behind bridge: f7a0-f7af Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: f7d0-f7ef Prefetchable memory behind bridge: d000-dfff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: f7b0-f7cf Prefetchable memory behind bridge: e000-efff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:14.0 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 22) (prog-if 00 [8259]) Subsystem: Device [0028:006d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Capabilities: access denied 00:14.1 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 22) (prog-if 00 [8259]) Subsystem: Device [0028:006d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Capabilities: access denied 00:14.2 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 22) (prog-if 00 [8259]) Subsystem: Device [0028:006d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
Bug#618331: Remove the patch for MOL
Package: linux-2.6 Version: 2.6.37-2 Severity: wishlist Hi, after the last package of MOL was removed from sid last week (#616495), you can drop from your package the patch for MOL, requested by #460667. Thanks for maintaining this patch for the past years. Regards, Jörg. -- System Information: Debian Release: unstable/experimental APT prefers unstable APT policy: (900, 'unstable'), (700, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.38-rc5.ledtest+ Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP
Bug#611750: Bug#613790: 2nd update (Re: Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate)
Le Sun, 06 Mar 2011 00:50:50 +, Ben Hutchings b...@decadent.org.uk a écrit : You can find all the individual patches as a quilt series in: git://git.kernel.org/pub/scm/linux/kernel/git/longterm/longterm-queue-2.6.32.git subdirectory releases/2.6.32.28. Since quilt doesn't have a bisect command you would have to have to keep track of good and bad positions in the series yourself. I would guess that it's most likely one of: releases/2.6.32.28/pm-hibernate-fix-pm_post_-notification-with-user-space-suspend.patch releases/2.6.32.28/x86-enable-the-intr-remap-fault-handling-after-local-apic-setup.patch so you could try reverting those before going through the whole series. Hello Ben, I've done the manual bisecting with 2.6.32.28 patches, and with 6 tries (and 2 more checks to be sure), I found that the patch causing hibernation resume failures was : x86-hotplug-use-mwait-to-offline-a-processor-fix-the-legacy-case.patch I've done about ten successfull hibernation/resume cycles with a 2.6.32-30 without this patch, and I'm using it since the end of my bisecting with success. I've also read on bug #611750's log that the new linux-image-2.6.32-5-686_2.6.32-31_i386 could have a fix for this problem, perhaps you could look if there is a patch in this latest version fixing the previous faulty patch I've identified here. With regards, Fred. -- 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/20110314130719.4283daee@prem6s
Bug#618319: Acknowledgement (linux-image-2.6.37-2-amd64: Framebuffer issues with RV620)
On Mon, Mar 14, 2011 at 11:15:04AM +, Debian Bug Tracking System wrote: If you wish to submit further information on this problem, please send it to 618...@bugs.debian.org. This appears to be resolved by 2.6.38-rc7. -- 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/20110314131339.gb2...@opensource.wolfsonmicro.com
Bug#618319: linux-image-2.6.37-2-amd64: Framebuffer issues with RV620
On Mon, 2011-03-14 at 11:06 +, Mark Brown wrote: Package: linux-2.6 Version: 2.6.37-2 Severity: normal As soon as the kernel switches to framebuffer mode on 2.6.37-2-amd64 the display becomes unrecoverably corrupted though everything appears to continue to run fine and a reboot can be initiated. With 2.6.32-5-amd64 the display appears fine. [...] I notice that this system is using the radeon driver but does not have the Radeon firmware installed. On older hardware the firmware is only needed for 3D acceleration, but I suspect that other functions also depend on it now. (And I've also seen some weird display glitches on a fairly old Mac when the firmware was not installed.) So, try installing firmware-linux-nonfree, if it doesn't offend your sensibilities. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#618331: marked as done (Remove the patch for MOL)
Your message dated Mon, 14 Mar 2011 13:25:37 + with message-id 1300109137.3962.30.camel@localhost and subject line Re: Bug#618331: Remove the patch for MOL has caused the Debian Bug report #618331, regarding Remove the patch for MOL 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.) -- 618331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.37-2 Severity: wishlist Hi, after the last package of MOL was removed from sid last week (#616495), you can drop from your package the patch for MOL, requested by #460667. Thanks for maintaining this patch for the past years. Regards, Jörg. -- System Information: Debian Release: unstable/experimental APT prefers unstable APT policy: (900, 'unstable'), (700, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.38-rc5.ledtest+ Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP ---End Message--- ---BeginMessage--- On Mon, 2011-03-14 at 11:54 +0100, Jörg Sommer wrote: Package: linux-2.6 Version: 2.6.37-2 Severity: wishlist Hi, after the last package of MOL was removed from sid last week (#616495), you can drop from your package the patch for MOL, requested by #460667. Thanks for maintaining this patch for the past years. I already did that. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#618319: linux-image-2.6.37-2-amd64: Framebuffer issues with RV620
On Mon, Mar 14, 2011 at 01:24:26PM +, Ben Hutchings wrote: I notice that this system is using the radeon driver but does not have the Radeon firmware installed. On older hardware the firmware is only needed for 3D acceleration, but I suspect that other functions also depend on it now. (And I've also seen some weird display glitches on a fairly old Mac when the firmware was not installed.) So, try installing firmware-linux-nonfree, if it doesn't offend your sensibilities. As well as upgrading to the new kernel I installed the firmware (since the new kernel prompted for firmware for the video card which hadn't been mentioned previously). Some combination of the two has resolved the issue for me. -- 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/20110314132716.gc2...@opensource.wolfsonmicro.com
Bug#618319: marked as done (linux-image-2.6.37-2-amd64: Framebuffer issues with RV620)
Your message dated Mon, 14 Mar 2011 13:35:57 + with message-id 1300109757.3962.32.camel@localhost and subject line Re: Bug#618319: linux-image-2.6.37-2-amd64: Framebuffer issues with RV620 has caused the Debian Bug report #618319, regarding linux-image-2.6.37-2-amd64: Framebuffer issues with RV620 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.) -- 618319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.37-2 Severity: normal As soon as the kernel switches to framebuffer mode on 2.6.37-2-amd64 the display becomes unrecoverably corrupted though everything appears to continue to run fine and a reboot can be initiated. With 2.6.32-5-amd64 the display appears fine. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Precision WorkStation T7500 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A07 board_vendor: Dell Inc. board_name: 06FW8P board_version: A00 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) Subsystem: Dell Device [1028:026d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 11 Capabilities: access denied 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=02, sec-latency=0 Memory behind bridge: f7a0-f7af Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: f7d0-f7ef Prefetchable memory behind bridge: d000-dfff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: f7b0-f7cf Prefetchable memory behind bridge: e000-efff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:14.0 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 22) (prog-if 00 [8259]) Subsystem: Device [0028:006d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Bug#618340: BUG: unable to handle kernel NULL pointer dereference at (null) w/ BTRFS
Package: linux-2.6 Version: 2.6.37-2 Severity: critical Tags: sid -- Package-specific info: ** Version: Linux version 2.6.37-2-686 (Debian 2.6.37-2) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-11) ) #1 SMP Sun Feb 27 10:51:32 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.37-2-686 root=/dev/mapper/sda2_crypt ro ** Not tainted ** Kernel log: [ 601.173886] btrfs: use compression [ 601.213129] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 666.969649] BUG: unable to handle kernel NULL pointer dereference at (null) [ 666.969731] IP: [c10203d8] kmap_atomic_prot+0x12/0xdd [ 666.969787] *pde = 2cb1c067 *pte = [ 666.969832] Oops: [#1] SMP [ 666.969869] last sysfs file: /sys/devices/virtual/backlight/acpi_video0/uevent [ 666.969932] Modules linked in: nls_utf8 nls_cp437 vfat fat btrfs zlib_deflate crc32c libcrc32c dm_snapshot tun ppdev lp sco bnep rfcomm l2cap crc16 vboxnetadp vboxnetflt vboxdrv binfmt_misc uinput acpi_cpufreq mperf cpufreq_powersave cpufreq_userspace cpufreq_stats cpufreq_conservative fuse firewire_sbp2 loop btusb bluetooth snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss thinkpad_acpi arc4 snd_pcm ecb snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq iwl3945 pl2303 usbserial iwlcore snd_timer i915 snd_seq_device mac80211 drm_kms_helper snd drm nsc_ircc cfg80211 pcmcia irda yenta_socket i2c_algo_bit i2c_i801 snd_page_alloc pcmcia_rsrc pcmcia_core parport_pc psmouse soundcore rng_core rfkill i2c_core video tpm_tis evdev parport pcspkr tpm nvram battery ac output processor crc_ccitt serio_raw power_supply tpm_bios button ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc dm_crypt dm_mirror dm_region_hash dm_log dm_mod sg sr_mod sd _mod rc_t10dif cdrom ata_generic ata_piix ahci libahci uhci_hcd libata sdhci_pci ehci_hcd firewire_ohci sdhci scsi_mod firewire_core e1000e usbcore mmc_core crc_itu_t thermal thermal_sys nls_base [last unloaded: scsi_wait_scan] [ 666.971242] [ 666.971259] Pid: 4326, comm: build-locale-ar Not tainted 2.6.37-2-686 #1 LENOVO 1703Y1F/1703Y1F [ 666.971348] EIP: 0060:[c10203d8] EFLAGS: 00210202 CPU: 1 [ 666.971397] EIP is at kmap_atomic_prot+0x12/0xdd [ 666.971437] EAX: EBX: ECX: ecb1e000 EDX: 0163 [ 666.971490] ESI: ecb1febc EDI: 00b2 EBP: ESP: ecb1fde0 [ 666.971543] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 666.971589] Process build-locale-ar (pid: 4326, ti=ecb1e000 task=f545a080 task.ti=ecb1e000) [ 666.971658] Stack: [ 666.971677] 00172000 ecb1febc 00b2 c108c1e0 00b2 [ 666.971770] 1000 0002 f85ae97c 00b2 1000 1b90 1c42 [ 666.971861] ef7b6c74 0002 f85b098a 1c42 ef7b6800 ecb1febc f5ff1820 0011a560 [ 666.971952] Call Trace: [ 666.971979] [c108c1e0] ? iov_iter_copy_from_user_atomic+0x26/0x5e [ 666.972008] [f85ae97c] ? btrfs_copy_from_user+0x50/0x8c [btrfs] [ 666.972008] [f85b098a] ? btrfs_file_aio_write+0x5c9/0x8fb [btrfs] [ 666.972008] [c10a2878] ? do_wp_page+0x5fd/0x61d [ 666.972008] [c10b9ca3] ? do_sync_write+0x9e/0xd3 [ 666.972008] [c10b9e78] ? rw_verify_area+0xcd/0xe7 [ 666.972008] [c10b9c05] ? do_sync_write+0x0/0xd3 [ 666.972008] [c10ba21d] ? vfs_write+0x7f/0xd9 [ 666.972008] [c10ba30a] ? sys_write+0x3c/0x60 [ 666.972008] [c12881bc] ? syscall_call+0x7/0xb [ 666.972008] Code: 00 00 00 00 c1 e8 0c c1 e0 05 8d 04 01 c3 8b 15 8c a6 45 c1 e9 5a fa ff ff 55 57 56 53 83 ec 04 89 e1 81 e1 00 e0 ff ff ff 41 14 8b 08 c1 e9 1e 69 c9 40 03 00 00 81 c1 40 b4 3d c1 2b 89 0c 03 [ 666.972008] EIP: [c10203d8] kmap_atomic_prot+0x12/0xdd SS:ESP 0068:ecb1fde0 [ 666.972008] CR2: [ 666.981145] ---[ end trace d3ae3d05ae164083 ]--- [ 666.981154] note: build-locale-ar[4326] exited with preempt_count 2 [ 666.981162] BUG: scheduling while atomic: build-locale-ar/4326/0x1002 [ 666.981169] Modules linked in: nls_utf8 nls_cp437 vfat fat btrfs zlib_deflate crc32c libcrc32c dm_snapshot tun ppdev lp sco bnep rfcomm l2cap crc16 vboxnetadp vboxnetflt vboxdrv binfmt_misc uinput acpi_cpufreq mperf cpufreq_powersave cpufreq_userspace cpufreq_stats cpufreq_conservative fuse firewire_sbp2 loop btusb bluetooth snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss thinkpad_acpi arc4 snd_pcm ecb snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq iwl3945 pl2303 usbserial iwlcore snd_timer i915 snd_seq_device mac80211 drm_kms_helper snd drm nsc_ircc cfg80211 pcmcia irda yenta_socket i2c_algo_bit i2c_i801 snd_page_alloc pcmcia_rsrc pcmcia_core parport_pc psmouse soundcore rng_core rfkill i2c_core video tpm_tis evdev parport pcspkr tpm nvram battery ac output processor crc_ccitt serio_raw power_supply tpm_bios button ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc dm_crypt dm_mirror dm_region_hash dm_log dm_mod sg sr_mod
Bug#618341: bnx2: MSI-X hang on 5709 NICs - nic dead
Package: linux-2.6
Version: 2.6.32-bpo.5
Severity: critical
Tags: squeeze patch lenny
Justification: breaks the whole system
http://marc.info/?l=linux-netdevm=127240304211909w=2
here is the description from the mail , repeated:
It has been reported that under certain heavy traffic conditions
in MSI-X
mode, the driver can lose an MSI-X vector causing all packets in
the
associated rx/tx ring pair to be dropped. The problem is caused
by
the chip dropping the write to unmask the MSI-X vector by the
kernel
(when migrating the IRQ for example).
This can be prevented by increasing the GRC timeout value for
these
register read and write operations.
Thanks to Dell for helping us debug this problem.
Signed-off-by: Michael Chan mc...@broadcom.com
we are using the 2.6.32 kernel and are bitten by this frequently.
vers/net/bnx2.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/net/bnx2.c b/drivers/net/bnx2.c
index a257bab..4c1e51e 100644
--- a/drivers/net/bnx2.c
+++ b/drivers/net/bnx2.c
@@ -4759,8 +4759,12 @@ bnx2_reset_chip(struct bnx2 *bp, u32 reset_code)
rc = bnx2_alloc_bad_rbuf(bp);
}
- if (bp-flags BNX2_FLAG_USING_MSIX)
+ if (bp-flags BNX2_FLAG_USING_MSIX) {
bnx2_setup_msix_tbl(bp);
+ /* Prevent MSIX table reads and write from timing out */
+ REG_WR(bp, BNX2_MISC_ECO_HW_CTL,
+ BNX2_MISC_ECO_HW_CTL_LARGE_GRC_TMOUT_EN);
+ }
return rc;
}
--
1.6.4.GIT
-- System Information:
Debian Release: 6.0
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.37-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
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/20110314135717.11072.32078.report...@jesaja.schuldei.org
Processed: tagging 618340, severity of 618340 is important
Processing commands for cont...@bugs.debian.org: tags 618340 - sid Bug #618340 [linux-2.6] BUG: unable to handle kernel NULL pointer dereference at (null) w/ BTRFS Removed tag(s) sid. severity 618340 important Bug #618340 [linux-2.6] BUG: unable to handle kernel NULL pointer dereference at (null) w/ BTRFS Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 618340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618340 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.13008622916.transcr...@bugs.debian.org
Processed: severity of 618341 is important
Processing commands for cont...@bugs.debian.org: severity 618341 important Bug #618341 [linux-2.6] bnx2: MSI-X hang on 5709 NICs - nic dead Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 618341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618341 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.130011184326790.transcr...@bugs.debian.org
Processed: tagging 618341
Processing commands for cont...@bugs.debian.org: tags 618341 - patch lenny Bug #618341 [linux-2.6] bnx2: MSI-X hang on 5709 NICs - nic dead Removed tag(s) lenny and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 618341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618341 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.13001136232898.transcr...@bugs.debian.org
Processed: tagging 618341, tagging 618341
Processing commands for cont...@bugs.debian.org: tags 618341 - squeeze Bug #618341 [linux-2.6] bnx2: MSI-X hang on 5709 NICs - nic dead Removed tag(s) squeeze. # i need to wake up... tags 618341 + patch Bug #618341 [linux-2.6] bnx2: MSI-X hang on 5709 NICs - nic dead Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 618341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618341 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.13001136372934.transcr...@bugs.debian.org
Uploading linux-2.6 (2.6.38-1)
I intend to upload linux-2.6 version 2.6.38-1 to unstable shortly after the upstream release, along with corresponding versions of linux-kbuild-2.6 and linux-latest-2.6. This should then progress into testing. The kernel team is discussing removal of the i386/686 flavour and renaming one or both of the remaining 32-bit flavours. If we can agree on what to do before upstream version 2.6.38, this change will be made in 2.6.38-1; otherwise it will be deferred. I will provide a patch for debian-installer kernel selection if necessary. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#617756: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#617756: linux-image-2.6.32-5-686: NMI received for unknown reason 3d on CPU 0.)
On 03/11/2011 08:36:06 AM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #617756: linux-image-2.6.32-5-686: NMI received for unknown reason 3d on CPU 0. It has been closed by Ben Hutchings b...@decadent.org.uk. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ben Hutchings b...@decadent.org.uk by replying to this email. -- 617756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ==quoted message from Ben Hutchings b...@decadent.org.uk, subject Re: Bug#617756: linux-image-2.6.32-5-686: NMI received for unknown reason 3d on CPU 0.== On Fri, 2011-03-11 at 00:22 -0600, Karl O. Pinc wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: normal *** Please type your report below this line *** Hi, I don't know whether this is a hardware problem or a kernel problem but figured I'd report it. I just upgraded to squeeze and am getting these messages on the console and in dmesg: [31934.320083] Uhhuh. NMI received for unknown reason 3d on CPU 0. [31934.320109] Do you have a strange power saving mode enabled? [31934.320125] Dazed and confused, but trying to continue [36364.673879] Uhhuh. NMI received for unknown reason 2d on CPU 0. [36364.673905] Do you have a strange power saving mode enabled? [36364.673922] Dazed and confused, but trying to continue I first noticed a problem, related or not, a month or so ago after the box crashed, twice over the course of a week, while still running lenny (stock kernel). I've not had a crash before or since but went looking and found (lenny kernel) messages in /var/log/kern.log like: [...] This is very likely a hardware fault. The power supply or RAM may be faulty, or the CPU may be overclocked or overheating. FYI. I ran memtest86+ on it for 48 hours and got 3 failures. This is a much lower frequency of errors than that in the dmesg output but is a clear indication of some problem. I'll see about replacing the ram and see if the problem goes away. Thanks for the help. (The CPU is not overclocked and should not be overheating because nothing has changed. I'll crack the case and see if there's anything obviously, like a fan has stoppped.) Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- 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/1300116869.15120.1@mofo
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #607301 (http://bugs.debian.org/607301) # * http://bugzilla.kernel.org/show_bug.cgi?id=10480 # * remote status changed: (?) - ASSIGNED usertags 607301 + status-ASSIGNED # remote status report for #607301 (http://bugs.debian.org/607301) # * http://bugzilla.kernel.org/show_bug.cgi?id=10480 # * remote status changed: (?) - ASSIGNED usertags 607301 + status-ASSIGNED # remote status report for #617508 (http://bugs.debian.org/617508) # * http://bugzilla.kernel.org/show_bug.cgi?id=30862 # * remote status changed: (?) - NEW usertags 617508 + status-NEW thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110314163738.28629.18876.btsl...@busoni.debian.org
Bug#618300: Looks like this may be a well-known issue.
Earlier, I failed to find some information relevant to my problem. The following link describes my symptoms to a tee, but with the RTL8102EL device. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/240470 Here's one more specific to the RTL8111: http://aplawrence.com/Linux/rtl811.html In any case, it looks like the answer is to: 1.) Download the latest rtl8168/rtl8111 source from Realtek. 2.) Boot into 2.6.32-5-amd64. 3.) Build the driver module. 4.) Remove the r8169.ko module from /lib/modules/2.6.32-5-amd64. 5.) Run depmod. 6.) Run update-initramfs -u -k 2.6.32-5-amd64. 7.) Reboot into 2.6.32-5-xen-amd64 and repeat steps 3-6. 8.) Reboot back into Xen, network's up and running. So far, no issues with the updated config.
Bug#615105: RaLink RT3090 still needs staging drivers to work
reassign 615105 src:linux-2.6 retitle 615105 RaLink RT3090 still needs staging drivers to work thanks I tried to compile a custom kernel, and noticed RaLink RT3090 Wireless PCIe worked again if built with CONFIG_RT2860=m option set. This option was previously disabled in revision 16207: http://svn.debian.org/viewsvn/kernel?view=revrevision=16207 -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- signature.asc Description: OpenPGP digital signature
Processed: RaLink RT3090 still needs staging drivers to work
Processing commands for cont...@bugs.debian.org: reassign 615105 src:linux-2.6 Bug #615105 [firmware-ralink] RaLink RT3090 no longer works with recent 2.6.37 and 2.6.38 kernels Bug reassigned from package 'firmware-ralink' to 'src:linux-2.6'. Bug No longer marked as found in versions firmware-nonfree/0.28. retitle 615105 RaLink RT3090 still needs staging drivers to work Bug #615105 [src:linux-2.6] RaLink RT3090 no longer works with recent 2.6.37 and 2.6.38 kernels Changed Bug title to 'RaLink RT3090 still needs staging drivers to work' from 'RaLink RT3090 no longer works with recent 2.6.37 and 2.6.38 kernels' thanks Stopping processing here. Please contact me if you need assistance. -- 615105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615105 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.13001417647135.transcr...@bugs.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: found 615105 2.6.35-1~experimental.3 Bug #615105 [src:linux-2.6] RaLink RT3090 still needs staging drivers to work Bug Marked as found in versions linux-2.6/2.6.35-1~experimental.3. End of message, stopping processing here. Please contact me if you need assistance. -- 615105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615105 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.13001419698532.transcr...@bugs.debian.org
Bug#614837: dvb-usb crash with dib0700 (Hauppauge Nova-T Stick)
Hi, On Thu, Feb 24, 2011 at 03:53:29AM +, Ben Hutchings wrote: On Wed, 2011-02-23 at 19:12 +0100, Adi Kriegisch wrote: Package: linux-2.6 Version: 2.6.37-1 Severity: important Tags: patch Trying to watch TV with Hauppauge Nova-T Stick leads to a kernel panic with 'unable to handle kernel NULL pointer'. This worked just fine with kernel 2.6.32 and below. The same issue has been reported: http://bugs.gentoo.org/show_bug.cgi?id=326511 and https://bugzilla.kernel.org/show_bug.cgi?id=20372 Patch for the issue: https://patchwork.kernel.org/patch/534231/ I applied this patch, recompiled the modules and it works fine, again. [...] Mauro, are you going to apply this patch? I have the same problem and tried the new 2.6.38~rc7-1~experimental.1 which seems to include the above fix and I can confirm that it works again now. Will the fix also be backported to 2.6.37 (i.e. unstable)? Thanks, Uwe. -- http://hermann-uwe.de | http://sigrok.org http://randomprojects.org | http://unmaintained-free-software.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/20110314232401.GA1714@greenwood
Bug#614837: dvb-usb crash with dib0700 (Hauppauge Nova-T Stick)
On Tue, Mar 15, 2011 at 12:24:01AM +0100, Uwe Hermann wrote: Hi, On Thu, Feb 24, 2011 at 03:53:29AM +, Ben Hutchings wrote: On Wed, 2011-02-23 at 19:12 +0100, Adi Kriegisch wrote: Package: linux-2.6 Version: 2.6.37-1 Severity: important Tags: patch Trying to watch TV with Hauppauge Nova-T Stick leads to a kernel panic with 'unable to handle kernel NULL pointer'. This worked just fine with kernel 2.6.32 and below. The same issue has been reported: http://bugs.gentoo.org/show_bug.cgi?id=326511 and https://bugzilla.kernel.org/show_bug.cgi?id=20372 Patch for the issue: https://patchwork.kernel.org/patch/534231/ I applied this patch, recompiled the modules and it works fine, again. [...] Mauro, are you going to apply this patch? I have the same problem and tried the new 2.6.38~rc7-1~experimental.1 which seems to include the above fix and I can confirm that it works again now. Will the fix also be backported to 2.6.37 (i.e. unstable)? No, we're going straight to 2.6.38 in unstable. 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/20110315001139.ga2...@decadent.org.uk
Processed: tagging 615035
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 615035 + pending Bug #615035 [linux-2.6] FIEMAP wrongly reports holes for delayed-allocation extents Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 615035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615035 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.130016793412448.transcr...@bugs.debian.org
