Re: Squeeze point release (6.0.6)
On Fri, 2012-09-07 at 21:43 +0200, Philipp Kern wrote: I'd like to arrange a point release to be done as soon as feasible. So I'd like to propose a bunch of weekends here: * Sep 22/23: I'm personally busy on the 23th * Sep 29/30: ok from RT side This is looking like the favourite so far, which would mean having p-u ready and closed next weekend. * Oct 6/7: Adam's busy for the weekend, hence we'd like to avoid that if possible * Oct 13/14: BSP attended by adsb/Sledge, not ideal to schedule it there [...] Dear Kernel team: Which changes are still pending for 6.0.6? When could we get them into the archive? For 22nd we'd close p-u-NEW on the 15th, which would leave us with a week. -kernel / -live ping? 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/1347706305.28617.40.ca...@jacala.jungle.funky-badger.org
Bug#619711: console-setup: breaks copying keymap to initramfs
[I am sending CC also to 532...@bugs.debian.org] On Thu, Sep 13, 2012 at 05:33:50PM +0200, Ralf Jung wrote: is there any progress on this one? This recently bit me quite hard when I installed a system with full-disk encryption, using a password which required the correct keyboard layout to be entered. As far as I can understand, this bug can be fixed in two ways - by code provided by console-setup, or by code provided by initramfs-tools. Almost all of the code required in order to fix this bug has been implemented in console-setup for quite some time. Unfortunately there are two problems: 1. I (as one of the maintainers of console-setup) can not guarantee that I will be able to maintain this code in future. Not because this will be too complex or too time consuming (no, it won't be...), but rather because I don't feel myself wanting to keep myself updated with any future changes in the initrd build process. 2. I suppose the maintainers of initramfs-tools can say something analogous... I am willing to provide any required development, education, whatever, the moment there appears a developer willing to maintain this. Anton Zinoviev -- 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/20120915114404.ga20...@logic.fmi.uni-sofia.bg
Bug#665881: [wheezy] module ath5k is blocking wlan-card
According to this thread [1], these two patches [2][3] should fix the issue. Can you backport to Wheezy kernel? Cheers [1] https://bbs.archlinux.org/viewtopic.php?id=139270 [2] http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=62e2c102cc1d2600381410c089ca9a37359577d2 [3] http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=5c17ddc4a047c59638c7eb8537aa887a1ddb9b0b -- 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+o8Mt0_1GZ2_SKxwW=-3ahabbm4v6dwpgexxabyp7szwey...@mail.gmail.com
Bug#687737: Please package ene-ub6250 firmware for ums_eneub6250 driver
Package: firmware-linux-nonfree Version: 0.36 Severity: wishlist Hi, Please consider packaging the ene-ub6250 firmware from the linux-firmware git tree, used by the ums_eneub6250 driver. This firmware is required for the correct operation of ENE UB6250 SD card readers which can be found at least on Acer Aspire One netbooks, a widely distributed model. Currently we have to download and install it manually in /lib/firmware/ene-ub6250/ which is far from ideal for new Debian users. I hope I'm reporting to the correct package, whether you include that firmware in firmware-linux-nonfree or you create a new, independent package. Best regards. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (902, 'stable-updates'), (902, 'testing'), (902, 'stable'), (802, 'unstable'), (2, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-linux-nonfree depends on no packages. firmware-linux-nonfree recommends no packages. Versions of packages firmware-linux-nonfree suggests: ii initramfs-tools 0.107 ii linux-image-3.2.0-3-amd64 [linux-image] 3.2.23-1 -- 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/50548bac.6070...@free.fr
Bug#687768: [INTL: it] Italian translation of debconf messages - firmware-nonfree
Quoting Beatrice Torracca (beatri...@libero.it): Package: firmware-nonfree Severity: wishlist Tags: l10n patch Hi. Please find attached the Italian translation of firmware-nonfree debconf messages proofread by the Italian localization team. As a string has double spaces, I fixed it in the English version...which fuzzies the translation. Unfuzzied translation attached. it.po Description: application/gettext signature.asc Description: Digital signature
Bug#687781: use fixed, IANA-registered port for rpc.mountd
Package: nfs-kernel-server Version: 1:1.2.6-3 Now that there's a IANA-registered port for rpc.mountd, I believe it be used by default, for such a move is likely to simplify the firewall configuration (see, e. g., [1].) TIA. --cut: http://www.iana.org/assignments/port-numbers/ -- mountd 20048/tcp NFS mount protocol mountd 20048/udp NFS mount protocol # Nicolas Williams Nicolas.Williamsoracle.com 09 August 2010 --cut: http://www.iana.org/assignments/port-numbers/ -- [1] http://wiki.debian.org/SecuringNFS -- FSF associate member #7257 -- 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/86vcff6ub2@gray.siamics.net
Processed: taffit forgot to downgrade these
Processing commands for cont...@bugs.debian.org: severity 686211 important Bug #686211 [linux-base] Please allow translation of all debconf templates Severity set to 'important' from 'serious' severity 686258 important Bug #686258 [uswsusp] Please allow translation of all debconf templates Severity set to 'important' from 'serious' #see http://release.debian.org/wheezy/rc_policy.txt thanks Stopping processing here. Please contact me if you need assistance. -- 686211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686211 686258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686258 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.134773249519781.transcr...@bugs.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
tags 681232 - moreinfo quit elrond wrote: According to this thread [1], these two patches [2][3] should fix the issue. Don't those depend on the calibration rework from 3.3? Thanks, Jonathan [1] https://bbs.archlinux.org/viewtopic.php?id=139270 [2] [...];h=62e2c102cc1d2600381410c089ca9a37359577d2 [3] [...];h=5c17ddc4a047c59638c7eb8537aa887a1ddb9b0b -- 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/20120915182407.GA528@mannheim-rule.local
Processed: Re: [wheezy] module ath5k is blocking wlan-card
Processing commands for cont...@bugs.debian.org: tags 681232 - moreinfo Bug #681232 [src:linux] linux-image-3.2.0-3-amd64: Atheros WiFi Adapter couldn't find networks gain calibration timeout Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 681232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681232 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.134773336726236.transcr...@bugs.debian.org
Bug#679545: IA64 (Itanium) Wheezy, doesn't detect DVD drive, new patch proposal
Hi Jonathan, I think we should not do that, if at all possible. The old IDE subsystem has a number of problems --- e.g., see http://www.mail-archive.com/stable@vger.kernel.org/msg15564.html for a recent report. thanks for pointing me to the right direction ;-). Back to the unmodified Debian Wheezy kernel. I realized that ata_piix also has a support for the ICH4-L (8086:24cb) but it couldn't initialize. A snippet from dmesg: ... [0.065516] pci :00:1f.1: [8086:24cb] type 0 class 0x000101 [0.065530] pci :00:1f.1: reg 10: [io 0x-0x0007] [0.065541] pci :00:1f.1: reg 14: [io 0x-0x0003] [0.065552] pci :00:1f.1: reg 18: [io 0x-0x0007] [0.065563] pci :00:1f.1: reg 1c: [io 0x-0x0003] [0.065574] pci :00:1f.1: reg 20: [io 0x1000-0x100f] [0.065585] pci :00:1f.1: reg 24: [mem 0x-0x03ff] ... [1.640965] libata version 3.00 loaded. [1.641656] ata_piix :00:1f.1: version 2.13 [1.641671] ata_piix :00:1f.1: device not available (can't reserve [mem 0x-0x03ff]) [1.641747] ata_piix: probe of :00:1f.1 failed with error -22 ... lspci -vvxxx reports: 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: Intel Corporation Device 3404 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 0 Region 0: I/O ports at 01f0 [size=8] Region 1: I/O ports at 03f4 [size=1] Region 2: I/O ports at 0170 [size=8] Region 3: I/O ports at 0374 [size=1] Region 4: I/O ports at 1000 [size=16] 00: 86 80 cb 24 05 00 80 02 02 8a 01 01 00 00 00 00 10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 20: 01 10 00 00 00 00 00 00 00 00 00 00 86 80 04 34 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 40: 03 a3 00 80 00 00 00 00 01 00 02 00 00 00 00 00 50: 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 60: 08 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 60 0f 00 00 00 00 00 00 The Intel 82801DB I/O Controller Hub 4 (ICH4) datasheet (http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82801db-io-controller-hub-4-datasheet.pdf) clarifies the dump of the PCI configuration registers. Section 10.1 PCI Configuration Registers (IDE-D31:F1) on page 383. I think the most important registers are: Offset Mnemonic Register Name Default Type 00?01h VID Vendor ID 8086h RO 02?03h DID Device ID 24CBh RO 04?05h CMD Command Register 00h R/W, RO 09hPIProgramming Interface 8Ah RO 10?13h PCMD_BAR Primary Command Block Base Address0001h R/W 14?17h PCNL_BAR Primary Control Block Base Address0001h R/W 18?1Bh SCMD_BAR Secondary Command Block Base Address 0001h R/W 1C?1Fh SCNL_BAR Secondary Control Block Base Address 0001h R/W 20?23h BAR Base Address Register 0001h R/W 24?27h EXBAR Expansion BAR 00h R/W ... PCMD_BAR, PCNL_BAR, SCMD_BAR, SCNL_BAR registers, primary/secondary Command Block Base Address/Control Block Base Address These registers determine the I/O start of the four I/O spaces of the IDE hostadapter. bit 31:16 Reserved bit 15:2 Base Address ? R/W. Base address of the I/O space. bit 1 Reserved bit 0 Resource Type Indicator (RTE) ? RO. This bit is set to one, indicating a request for I/O space. PM_BASE (same as BAR, same offset) register The Bus Master IDE interface function uses Base Address register 5 to request a 16-byte I/O space to provide a software interface to the Bus Master functions. bit 31:16 Reserved bit 15:4 Base Address ? R/W. Base address of the I/O space (16 consecutive I/O locations). bit 3:1 Reserved bit 0 Resource Type Indicator (RTE) ? RO. Hardwired to 1, indicating a request for I/O space. EXBAR register This is a memory mapped BAR that requires 1 KB of DWord-aligned memory that is Intel reserved for future functionality. BIOS needs to program the base address for a 1-KB memory space. 31:0 Intel Reserved for Future Functionality :-). (If the EXBAR would implement a usable memory range of the PCI device, the datasheet would read bit
Bug#679545: IA64 (Itanium) Wheezy, doesn't detect DVD drive, new patch proposal
On Sat, 2012-09-15 at 21:15 +0200, Stephan Schreiber wrote:
Hi Jonathan,
I think we should not do that, if at all possible. The old IDE
subsystem has a number of problems --- e.g., see
http://www.mail-archive.com/stable@vger.kernel.org/msg15564.html
for a recent report.
thanks for pointing me to the right direction ;-).
Back to the unmodified Debian Wheezy kernel.
I realized that ata_piix also has a support for the ICH4-L
(8086:24cb)
That device ID is documented as being for ICH-4, actually. Though the
PCI device list in your initial bug report was missing many of the PCI
functions that are supposed to be part of the ICH-4 (even fewer than are
included in the L variant).
but it couldn't initialize.
A snippet from dmesg:
...
[0.065516] pci :00:1f.1: [8086:24cb] type 0 class 0x000101
[0.065530] pci :00:1f.1: reg 10: [io 0x-0x0007]
[0.065541] pci :00:1f.1: reg 14: [io 0x-0x0003]
[0.065552] pci :00:1f.1: reg 18: [io 0x-0x0007]
[0.065563] pci :00:1f.1: reg 1c: [io 0x-0x0003]
[0.065574] pci :00:1f.1: reg 20: [io 0x1000-0x100f]
[0.065585] pci :00:1f.1: reg 24: [mem 0x-0x03ff]
...
[1.640965] libata version 3.00 loaded.
[1.641656] ata_piix :00:1f.1: version 2.13
[1.641671] ata_piix :00:1f.1: device not available (can't
reserve [mem 0x-0x03ff])
[1.641747] ata_piix: probe of :00:1f.1 failed with error -22
...
I would expect the kernel to fix this up - not sure why this isn't being
done.
By the way, the reason the old IDE driver worked is that
drivers/ide/setup-pci.c has a fallback for this:
if (pci_enable_device(dev)) {
ret = pci_enable_device_io(dev);
It was added almost exactly 10 years ago without any specific comment.
[...]
The ICH4-L IDE works with the ata_piix module now. The DVD drive
works
without a flaw.
What do think about the patch?
diff -ur linux-3.2.23-old/arch/ia64/pci/fixup.c
linux-3.2.23/arch/ia64/pci/fixup.c
--- linux-3.2.23-old/arch/ia64/pci/fixup.c 2012-09-15 10:53:02.0
+0200
+++ linux-3.2.23/arch/ia64/pci/fixup.c 2012-09-15 10:59:43.0 +0200
@@ -67,3 +67,42 @@
}
}
DECLARE_PCI_FIXUP_HEADER(PCI_ANY_ID, PCI_ANY_ID, pci_fixup_video);
+
+
+/*
+ * Fixup the EFI-BIOS bug of Intel's SR870 platform
It's just 'EFI', it has nothing to do with the PC BIOS.
+ * The EFI-BIOS of Intel's SR870BH2 and SR870BN4 including their OEM
+ * equivalents by Fujitsu and Dell doesn't configure the built-in ICH4-L IDE
+ * hostadapter correctly. The 6th resource of the ICH4-L is a memory
resource;
+ * Intel's datasheet Intel 82801DB I/O Controller Hub 4 (ICH4) (Document
+ * Number: 290744-001) states in section 10.1.15 EXBAR - Expansion Base
+ * Address Register (IDE-D31:F1) on page 389:
+ * This is a memory mapped BAR that requires 1 KB of DWord-aligned memory
+ * that is Intel reserved for future functionality. BIOS needs to program the
+ * base address for a 1-KB memory space.
+ * The EFI-BIOS doesn't care about that and doesn't configure the memory
+ * resource. Since the PCI configuration registers have their default values
+ * after reset, the memory resource is configured with 0x0-0x3FF. The Kernel
+ * can't use it due to memory address conflicts, and the ata_piix driver
fails
+ * to initialize.
+ *
+ * This quirk function disables the EXBAR memory resource of the device if it
+ * has the default values after reset.
+ */
This is perhaps too verbose. And the Intel documentation doesn't even
make sense (PCI memory BARs always have the same size and alignment, so
1K size implies 1K alignment). I would summarise it as:
The ICH-4 has an memory BAR for expansion (EXBAR), and ata_piix uses
pcim_enable_device() which enables this along with the I/O BARs.
In systems based on the Intel SR870 platform the firmware does not
initialise the EXBAR and pcim_enable_device() fails because the memory
region 0x0-0x3FF cannot be allocated. Since nothing uses the EXBAR, we
hide it so that only the I/O BARs will be enabled.
+static void __devinit pci_fixup_sr870_ich4l(struct pci_dev *pdev)
+{
+struct resource *r;
+
+r = pdev-resource[5];
+if ((r-flags IORESOURCE_MEM)
+ r-start == 0 r-end != 0) {
+dev_info(pdev-dev,
+SR870 EFI-BIOS bug workaround; fake an unimplemented EXBAR
+resource, which is Intel reserved for future
functionality.\n);
I don't think it's necessary to log this long message.
+r-flags = 0;
+r-end = 0;
+}
+}
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL,
PCI_DEVICE_ID_INTEL_82801DB_11, pci_fixup_sr870_ich4l);
This seems like it should work, and you have evidence that it does. :-)
But I wonder whether there is a cleaner way that would result in the BAR
being properly reprogrammed.
Anyway: please send your patch to
Bug#679545: IA64 (Itanium) Wheezy, doesn't detect DVD drive, new patch proposal
tags 679545 = d-i upstream patch moreinfo quit Hi, Stephan Schreiber wrote[1]: [0.065560] pci :00:1f.1: reg 24: [mem 0x-0x03ff] [0.065576] pci :00:1f.1: SR870 EFI-BIOS bug workaround; fake an unimplemented EXBAR resource, which is Intel reserved for future functionality. Please send your patch inline (not attached) in a message to linux-i...@vger.kernel.org with a subject line starting with [RFC/PATCH], cc-ing Alan Cox a...@lxorguk.ukuu.org.uk, linux-...@vger.kernel.org, linux-...@vger.kernel.org, and linux-ker...@vger.kernel.org to get review, and let us know when your patch or some alternative fix is accepted. (Also please feel free to cc me on the discussion so we can track it.) Be sure to mention which kernel versions you have tested and what happened with each, since that will make it clearer when the regression was introduced. We will be happy to pick up the patch once it is accepted upstream. See Documentation/SubmittingPatches for more hints, especially section 12 labelled Sign your work. Some context so I don't forget: http://thread.gmane.org/gmane.linux.kernel/31301/focus=31459 http://thread.gmane.org/gmane.linux.kernel/31301/focus=31781 368c73d4f689 Thanks much, and good luck, 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/20120915220054.GA156@mannheim-rule.local
Processed: Re: IA64 (Itanium) Wheezy, doesn't detect DVD drive, new patch proposal
Processing commands for cont...@bugs.debian.org: tags 679545 = d-i upstream patch moreinfo Bug #679545 [src:linux] IA64 Wheezy, doesn't detect DVD drive and NIC Added tag(s) upstream and moreinfo; removed tag(s) wheezy. quit Stopping processing here. Please contact me if you need assistance. -- 679545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679545 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.134774637220294.transcr...@bugs.debian.org
Processed: retitle 687791 to sky2: TX watchdog timeout on Yukon-2 FE+
Processing commands for cont...@bugs.debian.org: retitle 687791 sky2: TX watchdog timeout on Yukon-2 FE+ Bug #687791 [src:linux] sky2 (?) module leads to kernel oops with message about net/sched/sch_generic.c and dev_watchdog Changed Bug title to 'sky2: TX watchdog timeout on Yukon-2 FE+' from 'sky2 (?) module leads to kernel oops with message about net/sched/sch_generic.c and dev_watchdog' thanks Stopping processing here. Please contact me if you need assistance. -- 687791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687791 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.134774767732027.transcr...@bugs.debian.org
Processed: tagging 658460
Processing commands for cont...@bugs.debian.org: tags 658460 + pending Bug #658460 [linux-libc-dev] SOCK_NONBLOCK doubly defined in system headers on Alpha Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 658460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658460 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.13477479702525.transcr...@bugs.debian.org
Processed: tagging 685604
Processing commands for cont...@bugs.debian.org: tags 685604 + pending Bug #685604 [src:linux] linux-image-3.2.23-3-custom02-amd64: Radeon may try to read past end of video bios (memory allocation in acpi driver) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 685604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685604 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.13477479712541.transcr...@bugs.debian.org
Processed: tagging 685953
Processing commands for cont...@bugs.debian.org: tags 685953 + pending Bug #685953 [linux] linux: crash on speakup goto operation Ignoring request to alter tags of bug #685953 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 685953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685953 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.13477479742570.transcr...@bugs.debian.org
Bug#625922: RE: Bug#625922: Failures with ST2000DL003-9VT166
On 15/06/11 22:15, Paul Faure wrote: I upgraded my raid disks to 4 ST32000644NS (Seagate Constellation 2TB) and I haven't had an issue since. I have also moved the cheaper ST2000DL003-9VT166 disks to a Windows XP box (in a non raid environment) and haven't seen a problem in days now. There are plenty of references online now popping up saying that green disks are not designed or supported in a raid environment. Weather or not that's because of a physical issue, or a software issue, im not sure. Paul Just a guess: One of the features of green drivers is that they park the heads every few seconds [1] without disk activity. Can this be the root of the problem? Perhaps the HDDs are slow responding when they have the heads parked (which tends to happen too much often than with normal drives) and this causes this issue. You can disable this by forcing a one-hour timeout for parking the heads with: hdparm -S 242 /dev/sdX This needs to be done at boot time each time. Perhaps an init.d script would help. You can check the SMART attribute 193 of your drives, which tells you how many times the drive has parked the head in its life. You will see that this number is far greater on such green drivers than on normal drives. smartctl -a /dev/sdX | grep 193 Regards! [1] http://forums.anandtech.com/showthread.php?t=2085685 signature.asc Description: OpenPGP digital signature
Bug#625922: Failures with ST2000DL003-9VT166
In my case the head-parking and the power-on (real power on) values are the same, seems that I have that feature disabled. 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 76 9 Power_On_Hours 0x0032 086 086 000Old_age Always - 12291 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 80 193 Load_Cycle_Count0x0032 100 100 000Old_age Always - 80 On 16/09/2012, at 00:13, Carlos Alberto Lopez Perez clo...@igalia.com wrote: On 15/06/11 22:15, Paul Faure wrote: I upgraded my raid disks to 4 ST32000644NS (Seagate Constellation 2TB) and I haven't had an issue since. I have also moved the cheaper ST2000DL003-9VT166 disks to a Windows XP box (in a non raid environment) and haven't seen a problem in days now. There are plenty of references online now popping up saying that green disks are not designed or supported in a raid environment. Weather or not that's because of a physical issue, or a software issue, im not sure. Paul Just a guess: One of the features of green drivers is that they park the heads every few seconds [1] without disk activity. Can this be the root of the problem? Perhaps the HDDs are slow responding when they have the heads parked (which tends to happen too much often than with normal drives) and this causes this issue. You can disable this by forcing a one-hour timeout for parking the heads with: hdparm -S 242 /dev/sdX This needs to be done at boot time each time. Perhaps an init.d script would help. You can check the SMART attribute 193 of your drives, which tells you how many times the drive has parked the head in its life. You will see that this number is far greater on such green drivers than on normal drives. smartctl -a /dev/sdX | grep 193 Regards! [1] http://forums.anandtech.com/showthread.php?t=2085685 -- 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/bc431625-d488-4229-bdfa-a7da9e108...@claunia.com
Processed: reassign 687644 to src:linux
Processing commands for cont...@bugs.debian.org: reassign 687644 src:linux 3.2.23-1 Bug #687644 [linux-image-686-pae] linux-image-686-pae: Please enable I2C for i810 Bug reassigned from package 'linux-image-686-pae' to 'src:linux'. Ignoring request to alter found versions of bug #687644 to the same values previously set Ignoring request to alter fixed versions of bug #687644 to the same values previously set Bug #687644 [src:linux] linux-image-686-pae: Please enable I2C for i810 Marked as found in versions linux/3.2.23-1. thanks Stopping processing here. Please contact me if you need assistance. -- 687644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687644 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.134775412610692.transcr...@bugs.debian.org
Processed (with 1 errors): reassign 577106 to src:linux, found 577106 in linux-2.6/2.6.32-9, merging 577106 687644
Processing commands for cont...@bugs.debian.org:
reassign 577106 src:linux
Bug #577106 [linux-2.6] linux-image-2.6.32-3-686: Enable FB_I810_GTF and
FB_I810_I2C by default for Samsung SMT-7020S
Bug reassigned from package 'linux-2.6' to 'src:linux'.
Ignoring request to alter found versions of bug #577106 to the same values
previously set
Ignoring request to alter fixed versions of bug #577106 to the same values
previously set
found 577106 linux-2.6/2.6.32-9
Bug #577106 [src:linux] linux-image-2.6.32-3-686: Enable FB_I810_GTF and
FB_I810_I2C by default for Samsung SMT-7020S
Marked as found in versions linux-2.6/2.6.32-9.
merge 577106 687644
Bug #577106 [src:linux] linux-image-2.6.32-3-686: Enable FB_I810_GTF and
FB_I810_I2C by default for Samsung SMT-7020S
Unable to merge bugs because:
severity of #687644 is 'wishlist' not 'normal'
Failed to merge 577106: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1f00488)',
'requester', 'Ben Hutchings b...@decadent.org.uk', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1347754295-2365-bts-...@decadent.org.uk', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 536
Debbugs::Control::Service::control_line('line', 'merge 577106 687644',
'clonebugs', 'HASH(0x1e799e8)', 'limit', 'HASH(0x1e79430)',
'common_control_options', 'ARRAY(0x1e79478)', 'errors', ...) called at
/usr/lib/debbugs/service line 471
thanks
Stopping processing here.
Please contact me if you need assistance.
--
577106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577106
687644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687644
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.134775430011567.transcr...@bugs.debian.org
Processed (with 1 errors): reassign 588882 to src:linux, merging 577106 588882
Processing commands for cont...@bugs.debian.org:
reassign 52 src:linux
Bug #52 [linux-2.6] linux-image-2.6: Enabling FB-I810-GTF and FB-I810-I2C
Bug reassigned from package 'linux-2.6' to 'src:linux'.
Ignoring request to alter found versions of bug #52 to the same values
previously set
Ignoring request to alter fixed versions of bug #52 to the same values
previously set
merge 577106 52
Bug #577106 [src:linux] linux-image-2.6.32-3-686: Enable FB_I810_GTF and
FB_I810_I2C by default for Samsung SMT-7020S
Unable to merge bugs because:
severity of #52 is 'wishlist' not 'normal'
Failed to merge 577106: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x35f4458)',
'requester', 'Ben Hutchings b...@decadent.org.uk', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1347754350-414-bts-...@decadent.org.uk', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 536
Debbugs::Control::Service::control_line('line', 'merge 577106 52',
'clonebugs', 'HASH(0x356d9e8)', 'limit', 'HASH(0x356d430)',
'common_control_options', 'ARRAY(0x356d478)', 'errors', ...) called at
/usr/lib/debbugs/service line 471
thanks
Stopping processing here.
Please contact me if you need assistance.
--
577106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577106
52: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52
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.134775435512274.transcr...@bugs.debian.org
Processed: tagging 687644
Processing commands for cont...@bugs.debian.org: tags 687644 + pending Bug #687644 [src:linux] linux-image-686-pae: Please enable I2C for i810 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 687644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687644 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.134775479214227.transcr...@bugs.debian.org
Processed: forcibly merging 687644 577106 588882
Processing commands for cont...@bugs.debian.org: forcemerge 687644 577106 52 Bug #687644 [src:linux] linux-image-686-pae: Please enable I2C for i810 Bug #577106 [src:linux] linux-image-2.6.32-3-686: Enable FB_I810_GTF and FB_I810_I2C by default for Samsung SMT-7020S Severity set to 'wishlist' from 'normal' Marked as found in versions linux/3.2.23-1. Added tag(s) pending. Bug #687644 [src:linux] linux-image-686-pae: Please enable I2C for i810 Marked as found in versions linux-2.6/2.6.32-9. Bug #52 [src:linux] linux-image-2.6: Enabling FB-I810-GTF and FB-I810-I2C Marked as found in versions linux-2.6/2.6.32-9 and linux/3.2.23-1. Added tag(s) pending. Merged 577106 52 687644 thanks Stopping processing here. Please contact me if you need assistance. -- 577106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577106 52: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52 687644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687644 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.134775485314766.transcr...@bugs.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
On Sat, 2012-09-15 at 14:39 +0200, elrond wrote: According to this thread [1], these two patches [2][3] should fix the issue. Can you backport to Wheezy kernel? [...] These are not obviously applicable to 3.2; in fact I think they may be fixing a different problem. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#687791: sky2 (?) module leads to kernel oops with message about net/sched/sch_generic.c and dev_watchdog
On Fri, 2012-09-14 at 18:48 +0100, Julian Gilbey wrote: Package: src:linux Version: 3.2.23-1 Severity: normal I've had four oopses today when trying to connect to an ethernet. [...] If the log doesn't actually say 'Oops', it's not an oops. In fact this is a WARNING. Anyway, the important message is: 'NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out' which basically means the hardware transmit path got stuck. When this happens the driver is called to reset the hardware, but this seems to have been unsuccessful as the driver log messages are repeated. As you say this is is not easily reproducible, I'm not sure how to make progress on it. Thinking about what might have made a difference: have you made any changes to the physical network connection recently (different cable or plugged into something different)? Was the room colder/hotter than normal when you started the computer? Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky signature.asc Description: This is a digitally signed message part
Bug#625922: Failures with ST2000DL003-9VT166
I found the following blog post that contains some useful tips about this issue: http://paul.sullivan.za.org/kernel-disables-sata-drive-under-heavy-load-action-0x6-frozen/ signature.asc Description: OpenPGP digital signature
Bug#625922: Failures with ST2000DL003-9VT166
For me it the bug has appeared on other drives (not only Seagate), with no system load at all, and without the kernel killing tasks On 16/09/2012, at 01:53, Carlos Alberto Lopez Perez clo...@igalia.com wrote: I found the following blog post that contains some useful tips about this issue: http://paul.sullivan.za.org/kernel-disables-sata-drive-under-heavy-load-action-0x6-frozen/ -- 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/cbe90e97-65c5-47ee-8f0c-30e09b618...@claunia.com
Bug#669314: NFS: kernel forces trailing slash for export in /proc/self/mounts
On Tue, 2012-06-19 at 12:43 -0700, Chris Hiestand wrote:
Hi Alexander Viro et al,
This is an escalation of Debian Bug #669314 http://bugs.debian.org/669314,
which I will
re-elaborate in this email for your convenience.
You committed a change to the way the linux kernel reports NFS mounts - now
with a
trailing slash for the remote export (among other changes). The change
happened here:
commit c7f404b40a3665d9f4e9a927cc5c1ee0479ed8f9
Author: Al Viro v...@zeniv.linux.org.uk
Date: Wed Mar 16 06:59:40 2011 -0400
vfs: new superblock methods to override /proc/*/mount{s,info}
a) -show_devname(m, mnt) - what to put into devname columns in mounts,
mountinfo and mountstats
b) -show_path(m, mnt) - what to put into relative path column in
mountinfo
Leaving those NULL gives old behaviour. NFS switched to using those.
Signed-off-by: Al Viro v...@zeniv.linux.org.uk
The problematic behavior is that NFS exports now have a trailing slash in
/proc/self/mounts.
[...]
If there is a new convention to display the trailing slash, we need to update
our tools to handle this change. If there is not a new convention, I'd argue
this is a bug.
So is this a new convention or not? What is the appropriate way for
Debian to move forward?
Al, Trond, what's going on here? This sure looks like it broke
userland, in which case we need to revert the change in behaviour.
How about the following (untested) change?
Ben.
---
Subject: nfs: Show original device name verbatim in /proc/*/mount{s,info}
Since commit c7f404b ('vfs: new superblock methods to override
/proc/*/mount{s,info}'), nfs_path() is used to generate the mounted
device name reported back to userland.
nfs_path() always generates a trailing slash when the given dentry is
the root of an NFS mount, but userland may expect the original device
name to be returned verbatim (as it used to be). Make this
canonicalisation optional and change the callers accordingly.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Cc: sta...@vger.kernel.org # v2.6.39+
---
fs/nfs/internal.h |4 ++--
fs/nfs/namespace.c | 15 ++-
fs/nfs/nfs4namespace.c |2 +-
fs/nfs/super.c |2 +-
4 files changed, 14 insertions(+), 9 deletions(-)
diff --git a/fs/nfs/internal.h b/fs/nfs/internal.h
index d554438..c38224a 100644
--- a/fs/nfs/internal.h
+++ b/fs/nfs/internal.h
@@ -354,7 +354,7 @@ extern void nfs_sb_deactive(struct super_block *sb);
/* namespace.c */
extern char *nfs_path(char **p, struct dentry *dentry,
- char *buffer, ssize_t buflen);
+ char *buffer, ssize_t buflen, bool canonical);
extern struct vfsmount *nfs_d_automount(struct path *path);
struct vfsmount *nfs_submount(struct nfs_server *, struct dentry *,
struct nfs_fh *, struct nfs_fattr *);
@@ -491,7 +491,7 @@ static inline char *nfs_devname(struct dentry *dentry,
char *buffer, ssize_t buflen)
{
char *dummy;
- return nfs_path(dummy, dentry, buffer, buflen);
+ return nfs_path(dummy, dentry, buffer, buflen, true);
}
/*
diff --git a/fs/nfs/namespace.c b/fs/nfs/namespace.c
index 6559253..059975e 100644
--- a/fs/nfs/namespace.c
+++ b/fs/nfs/namespace.c
@@ -33,6 +33,8 @@ int nfs_mountpoint_expiry_timeout = 500 * HZ;
* @dentry - pointer to dentry
* @buffer - result buffer
* @buflen - length of buffer
+ * @canonical - ensure there is exactly one slash after the original
+ * device (export) name; if false, return it verbatim
*
* Helper function for constructing the server pathname
* by arbitrary hashed dentry.
@@ -41,7 +43,8 @@ int nfs_mountpoint_expiry_timeout = 500 * HZ;
* server side when automounting on top of an existing partition
* and in generating /proc/mounts and friends.
*/
-char *nfs_path(char **p, struct dentry *dentry, char *buffer, ssize_t buflen)
+char *nfs_path(char **p, struct dentry *dentry, char *buffer, ssize_t buflen,
+ bool canonical)
{
char *end;
int namelen;
@@ -74,7 +77,7 @@ rename_retry:
rcu_read_unlock();
goto rename_retry;
}
- if (*end != '/') {
+ if (canonical *end != '/') {
if (--buflen 0) {
spin_unlock(dentry-d_lock);
rcu_read_unlock();
@@ -91,9 +94,11 @@ rename_retry:
return end;
}
namelen = strlen(base);
- /* Strip off excess slashes in base string */
- while (namelen 0 base[namelen - 1] == '/')
- namelen--;
+ if (canonical) {
+ /* Strip off excess slashes in base string */
+ while (namelen 0 base[namelen - 1] == '/')
+ namelen--;
+ }
buflen -= namelen;
if (buflen 0) {
spin_unlock(dentry-d_lock);
diff --git
Processed: tagging 669314
Processing commands for cont...@bugs.debian.org: tags 669314 + patch Bug #669314 [src:linux-2.6] linux-source-3.2: After mounting nfs export, kernel forces trailing slash for export in /proc/self/mounts Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 669314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669314 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.134776210530589.transcr...@bugs.debian.org
Bug#684265: Debian Installer 7.0 Beta2 release bug #684265
On Thu, 2012-09-13 at 14:58 -0700, Rick Thomas wrote: [...] 1) It seems likely that adding a udeb for fuse-modules will allow os- prober to identify other Linux OS root partitions and get them added to the boot-loader config file... But only as long as those partitions are not LVM partitions. I have not performed definitive experiments to verify either half of this assertion, but the evidence so far does point in that direction. When can I expect the udeb for fuse fix to be included in an upcoming daily iso? I'll be happy to test it when it's available. [...] Will be included in the next linux upload to unstable, hopefully this weekend. I don't know how long that will take to get into a daily installer. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#687567: marked as done (linux-image-3.2.0-2-amd64: Patch to support D-Link DUB-E100 variant)
Your message dated Sun, 16 Sep 2012 05:00:39 +0100 with message-id 1347768039.13258.230.ca...@deadeye.wl.decadent.org.uk and subject line Re: Bug#687567: linux-image-3.2.0-2-amd64: Patch to support D-Link DUB-E100 variant has caused the Debian Bug report #687567, regarding linux-image-3.2.0-2-amd64: Patch to support D-Link DUB-E100 variant 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.) -- 687567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.15-1 Severity: wishlist Tags: patch Any chance the patch at http://grinkin.ru/dlink-DUB-E100.html could get rolled in? It appears D-Link is now building a variant of this ethernet dongle with a different USB id (1a02 vs 1a00) and chipset. Thanks, De -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: OptiPlex 980 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A01 board_vendor: Dell Inc. board_name: 0D441T board_version: A00 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0040] (rev 12) Subsystem: Dell Device [1028:02da] 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 Capabilities: access denied Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express x16 Root Port [8086:0041] (rev 12) (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=01, sec-latency=0 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:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02da] 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 Interrupt: pin A routed to IRQ 43 Region 0: Memory at f7c0 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at ec90 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) Subsystem: Dell Device [1028:02da] 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 Interrupt: pin A routed to IRQ 11 Region 0: Memory at feda6000 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:16.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset PT IDER Controller [8086:3b66] (rev 06) (prog-if 85 [Master SecO PriO]) Subsystem: Dell Device [1028:02da] 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 Interrupt: pin C routed to IRQ 18 Region 0: I/O ports at fe80 [size=8] Region 1: I/O ports at fe90 [size=4] Region 2: I/O ports at fea0 [size=8] Region 3: I/O ports at feb0 [size=4] Region 4: I/O ports at fef0 [size=16] Capabilities: access denied Kernel driver in use: ata_generic 00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400 Series
Bug#687515: Coredumped after wakeup from suspend, mentioning ifconfig
On Thu, 2012-09-13 at 13:06 +0200, Gunnar Stahl wrote: package: net-tools version: 1.60-24.1 severity: normal After wakeup from suspend the system coredumped. Only thing I can decifer in the dump is the mention of ifconfig after a nullpointer. The system is an acer aspire one 722, sporting an amd c60 dualcore cpu. I've upgraded the ram to 8GB. UName -a shows Linux jeheskix 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux. System runs on wheezy. In the attached kernel.log.1 (Stuff starts at timestamp Sep 13 10:17:56) the system shows a nullpointer. In case of any questions don't hesitate to ask. Has this happened more than once? What are you using to configure networking? [62312.392369] BUG: unable to handle kernel NULL pointer dereference at (null) [62312.392536] IP: [811aea34] memcmp+0x8/0x1d [62312.392635] PGD 16c555067 PUD 204891067 PMD 0 [62312.392728] Oops: [#1] SMP [62312.392795] CPU 1 [62312.392832] Modules linked in: fuse ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables bnep rfcomm bluetooth binfmt_misc uinput nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop kvm_amd kvm snd_hda_codec_conexant snd_hda_codec_hdmi joydev arc4 snd_hda_intel radeon ath9k ath9k_common snd_hda_codec ath9k_hw uvcvideo snd_hwdep snd_pcm videodev snd_page_alloc ttm snd_seq snd_seq_device snd_timer v4l2_compat_ioctl32 media drm_kms_helper ath mac80211 snd sp5100_tco drm psmouse i2c_piix4 cfg80211 soundcore acer_wmi sparse_keymap rfkill i2c_algo_bit powernow_k8 i2c_core mperf serio_raw pcspkr evdev k10temp ac processor battery video wmi button power_supply thermal_sys ext4 crc16 jbd2 mbcache cryptd aes_x86_64 aes_generic xts gf128mul dm_crypt dm_mod ums_realtek usb_storage uas sg sd_mod crc_t10dif atl1c ahci libahci ohci_hcd libata scsi_mod ehci_hcd usbcore usb_common [last unloaded: scsi_wait_scan] [62312.394657] [62312.394692] Pid: 11771, comm: ifconfig Tainted: G O 3.2.0-3-amd64 #1 Acer AO722/JE10-BZ [62312.394851] RIP: 0010:[811aea34] [811aea34] memcmp+0x8/0x1d [...] [62312.396023] Call Trace: [62312.396023] [a0225500] ? __cfg80211_mlme_deauth+0x6a/0x116 [cfg80211] [62312.396023] [a02282bb] ? __cfg80211_disconnect+0xf8/0x174 [cfg80211] [...] [62312.401606] Code: 74 15 3c 31 eb 0a 3c 6e 74 0d 3c 79 74 04 3c 59 75 0b c6 06 01 eb 03 c6 06 00 31 c0 c3 b8 ea ff ff ff c3 31 c9 eb 11 0f b6 04 0f 44 0f b6 04 0e 48 ff c1 44 29 c0 75 07 48 39 d1 75 ea 31 c0 c3 [62312.401606] RIP [811aea34] memcmp+0x8/0x1d [62312.401606] RSP 880101a03bc0 [62312.401606] CR2: [62312.463864] ---[ end trace fa4487d311830802 ]--- For future reference, this appears to mean that the kernel got to this code in __cfg80211_disconnect(): /* wdev-conn-params.bssid must be set if SCANNING */ err = __cfg80211_mlme_deauth(rdev, dev, wdev-conn-params.bssid, NULL, 0, reason, false); if (err) return err; and wdev-conn-params.bssid was *not* set as the comment says it must be. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Processed: tagging 687515
Processing commands for cont...@bugs.debian.org: tags 687515 + moreinfo Bug #687515 [src:linux] Coredumped after wakeup from suspend, mentioning ifconfig Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 687515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687515 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.134776947313331.transcr...@bugs.debian.org
Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support
On Wed, 2012-09-12 at 21:21 +0200, Carsten Grohmann wrote: Package: src:linux Version: 3.2.23-1 Severity: normal Dear Maintainer, please add support for Intel Ivy Bridge processors to the Debian standard kernel. The current Debian kernel 3.2.0 doesn't support the new Intel processors with built-in GPU. Sure it does. Certainly the driver has an entry for your GPU's device ID: INTEL_VGA_DEVICE(0x0162, intel_ivybridge_d_info), /* GT2 desktop */ Now, there may be *bugs*, but that's another matter. The kernel 3.2.0 has booted the system successfully after the processor has been replaced by a new Intel Ivy Bridge i5-3570K. Unfortunately neither X nor audio were working. An update to kernel 3.5 from experimental tree solved all issues. But audio has nothing to do with the processor... unless you are talking about audio over HDMI? We are *considering* updating some or all of the graphics drivers to the versions found in Linux 3.4, which might fix this. I don't know if packages are available for test yet. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#687380: marked as done (Please verify DRBD data corruption bug / patch)
Your message dated Sun, 16 Sep 2012 05:44:26 +0100 with message-id 1347770666.13258.249.ca...@deadeye.wl.decadent.org.uk and subject line Re: Bug#687380: Please verify DRBD data corruption bug / patch has caused the Debian Bug report #687380, regarding Please verify DRBD data corruption bug / patch 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.) -- 687380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-amd64 Severity: important In their current newsletter, LINBIT states: DRBD 8.4.2 Has been Released For any user of DRBD-8.4, we suggest an upgrade to 8.4.2 as changes to the kernel in version 2.6.36 or newer have caused an issue that may cause data corruption on a Secondary/Sync target when using protocols A or B. (In the 8.3 series this was already fixed with the 8.3.13 release). It is worth noting that all previous DRBD releases did not enforce correct ordering of (some) write operations on a resync-target node. It is a rare condition that could trigger the potential data corruption. It may cause corruption in the sense that it looks like if a single block write was not executed on the secondary. Actually it was overwritten with the previous version of the data. This second write originates from the resync process. Apart from that those nasty bugs, we have also fixed a condition where disk-barrier no and disk-flushes no were ineffective. This was the reason why some people were reporting drbd-8.3 is faster than drbd-8.4. Referenced GIT commit: http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=tag;h=refs/tags/drbd-8.4.2 Please verify if this bug(fix) applies to any Debian maintained kernel! Thank you, Raoul -- DI (FH) Raoul Bhatia M.Sc. email. r.bha...@ipax.at Technischer Leiter IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at Barawitzkagasse 10/2/2/11 email.off...@ipax.at 1190 Wien tel. +43 1 3670030 FN 277995t HG Wien fax.+43 1 3670030 15 ---End Message--- ---BeginMessage--- On Wed, 2012-09-12 at 11:40 +0200, Raoul Bhatia [IPAX] wrote: Package: linux-image-amd64 Severity: important In their current newsletter, LINBIT states: DRBD 8.4.2 Has been Released For any user of DRBD-8.4, we suggest an upgrade to 8.4.2 as changes to the kernel in version 2.6.36 or newer have caused an issue that may cause data corruption on a Secondary/Sync target when using protocols A or B. (In the 8.3 series this was already fixed with the 8.3.13 release). It is worth noting that all previous DRBD releases did not enforce correct ordering of (some) write operations on a resync-target node. It is a rare condition that could trigger the potential data corruption. It may cause corruption in the sense that it looks like if a single block write was not executed on the secondary. Actually it was overwritten with the previous version of the data. This second write originates from the resync process. Apart from that those nasty bugs, we have also fixed a condition where disk-barrier no and disk-flushes no were ineffective. This was the reason why some people were reporting drbd-8.3 is faster than drbd-8.4. Referenced GIT commit: http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=tag;h=refs/tags/drbd-8.4.2 Please verify if this bug(fix) applies to any Debian maintained kernel! We don't track out-of-tree drivers. If you can identify relevant bug fixes in the mainline Linux kernel, please do so. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#684441: [PATCH v2] [media] rc: ite-cir: Initialise ite_dev::rdev earlier
I upgrade my system yesterday, and this morning, it panic always, even I boot another system first and reboot. Both the kernel in testing and experimental have this problem. On Wed, Aug 29, 2012 at 4:48 AM, Luis Henriques luis.henriq...@canonical.com wrote: On Tue, Aug 28, 2012 at 10:09:55AM -0700, Ben Hutchings wrote: On Tue, 2012-08-28 at 12:44 +0100, Luis Henriques wrote: On Mon, Aug 20, 2012 at 12:32:27AM +0100, Ben Hutchings wrote: ite_dev::rdev is currently initialised in ite_probe() after rc_register_device() returns. If a newly registered device is opened quickly enough, we may enable interrupts and try to use ite_dev::rdev before it has been initialised. Move it up to the earliest point we can, right after calling rc_allocate_device(). I believe this is the same bug: https://bugzilla.kernel.org/show_bug.cgi?id=46391 And the bug is present in other IR devices as well. I've sent a proposed fix: http://marc.info/?l=linux-kernelm=134590803109050w=2 It might be a worthwhile fix. But it doesn't fix this bug - after that patch, the driver will still enable its IRQ before initialising ite_dev::rdev. You're absolutely right, sorry for the noise. I should have taken a closer look at your patch. Cheers, -- Luis Ben. Cheers, -- Luis References: http://bugs.debian.org/684441 Reported-and-tested-by: YunQiang Su wzss...@gmail.com Signed-off-by: Ben Hutchings b...@decadent.org.uk Cc: sta...@vger.kernel.org --- Unlike the previous version, this will apply cleanly to the media staging/for_v3.6 branch. Ben. drivers/media/rc/ite-cir.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/rc/ite-cir.c b/drivers/media/rc/ite-cir.c index 36fe5a3..24c77a4 100644 --- a/drivers/media/rc/ite-cir.c +++ b/drivers/media/rc/ite-cir.c @@ -1473,6 +1473,7 @@ static int ite_probe(struct pnp_dev *pdev, const struct pnp_device_id rdev = rc_allocate_device(); if (!rdev) goto failure; + itdev-rdev = rdev; ret = -ENODEV; @@ -1604,7 +1605,6 @@ static int ite_probe(struct pnp_dev *pdev, const struct pnp_device_id if (ret) goto failure3; - itdev-rdev = rdev; ite_pr(KERN_NOTICE, driver has been successfully loaded\n); return 0; -- Ben Hutchings It is a miracle that curiosity survives formal education. - Albert Einstein -- YunQiang Su -- 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/cakcpw6wvcm99-vzqoofyib7ggknp57corb6e5f3ep2218c1...@mail.gmail.com
Bug#686939: linux-image-3.2.0-3-686-pae: fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
On Fri, 2012-09-07 at 19:37 +0800, Steven Shiau wrote: Source: linux Version: 3.2.23-1 Severity: important Dear Maintainer, When using nomodeset and vga=788 in the boot parameters, the machine hang at fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver on a machine with Intel VGA card. This happens no matter it's 686-pae kernel, or i486 one. Since the Intel VGA card in very common, please consider to make framebuffer work for KMS disabled. DRM drivers with KMS *are* framebuffer drivers. I think you mean 'keep VGA console working'. How to reproduce this: 1. Create a Debian live based on Sid: http://live-build.debian.net/cgi-bin/live-build 2. Burn the created iso on a CD, then boot it on a machine with Intel VGA card 3. In the 1st boot menu of isolinux, press Tab key to modify the boot parameters. Just append nomodeset vga=788, then press enter to continue boot 4. The above error will shown, and it just hangs there. This is really weird because i915 just shouldn't register a console at all if you do that... Ah, but xserver-video-xorg-intel still installs a configuration file which *overrides* nomodeset (/etc/modprobe.d/i915-kms.conf). (There was a very good reason for doing that in squeeze, but I think it can be dropped now.) So you could avoid installing xserver-video-xorg-intel, or empty the configuration file. Still, the kernel should be able to switch without hanging (and normally does). Does this *only* happen if you use 'nomodeset vga=788' or does it also happen if you use 'vga=788'? Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Processed: tagging 686939
Processing commands for cont...@bugs.debian.org: tags 686939 + moreinfo Bug #686939 [src:linux] linux-image-3.2.0-3-686-pae: fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 686939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686939 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.13477724511530.transcr...@bugs.debian.org
Bug#684441: [PATCH v2] [media] rc: ite-cir: Initialise ite_dev::rdev earlier
On Sun, 2012-09-16 at 12:56 +0800, YunQiang Su wrote: I upgrade my system yesterday, and this morning, it panic always, even I boot another system first and reboot. Both the kernel in testing and experimental have this problem. [...] I haven't uploaded a fixed package yet. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
