Processed: cloning 782058, reassign -1 to debian-installer
Processing commands for cont...@bugs.debian.org: > clone 782058 -1 Bug #782058 [src:linux] Pegasos II: installer boots up to 'returning from prom_init' Bug 782058 cloned as bug 782059 > reassign -1 debian-installer Bug #782059 [src:linux] Pegasos II: installer boots up to 'returning from prom_init' Bug reassigned from package 'src:linux' to 'debian-installer'. No longer marked as found in versions linux/3.16.7-ckt7-1. Ignoring request to alter fixed versions of bug #782059 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 782058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782058 782059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782059 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: https://lists.debian.org/handler.s.c.14283775798004.transcr...@bugs.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
Package: src:linux Version: 3.16.7-ckt7-1 Severity: important Tags: d-i jessie The last line seen on the screen after installer CD boots is 'returning from prom_init'. This is a regression introduced in d-i rc2 which persist in daily builds. Connecting serial terminal and booting with 'console=ttyS0,9600' allows successful installation of jessie. (with some hiccups that warrant a separate bug report to mkvmlinuz). I'm aware that fix for bug #748398 actually introduced this regression. The radeonfb is currently compiled as module which is not included in the installer. I hope that including the radeonfb module in the installer will fix this issue. This report was generated on the same machine after successful installation. Could you please add radeonfb module to debian installer? Milan -- Package-specific info: ** Version: Linux version 3.16.0-4-powerpc (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.7-ckt7-1 (2015-03-01) ** Command line: root=/dev/sda2 ** Tainted: W (512) * Taint on warning. ** Kernel log: [9.107171] [drm] Connector 0: [9.107180] [drm] VGA-1 [9.107193] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [9.107206] [drm] Encoders: [9.107216] [drm] CRT1: INTERNAL_DAC1 [9.107227] [drm] Connector 1: [9.107237] [drm] DVI-I-1 [9.107246] [drm] HPD1 [9.107258] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [9.107269] [drm] Encoders: [9.107279] [drm] CRT2: INTERNAL_DAC2 [9.107290] [drm] DFP1: INTERNAL_TMDS1 [9.138249] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro [9.222863] [drm] fb mappable at 0xC004 [9.222913] [drm] vram apper at 0xC000 [9.222924] [drm] size 5242880 [9.222934] [drm] fb depth is 24 [9.222944] [drm]pitch is 5120 [9.275221] Console: switching to colour frame buffer device 160x64 [9.316086] radeon 0001:01:08.0: fb0: radeondrmfb frame buffer device [9.316398] radeon 0001:01:08.0: registered panic notifier [9.320300] [drm] Initialized radeon 2.39.0 20080528 for 0001:01:08.0 on minor 0 [9.679644] Adding 3012180k swap on /dev/sda3. Priority:-1 extents:1 across:3012180k FS [9.722815] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [9.732480] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [9.872623] snd_via82xx_modem: probe of :00:0c.6 failed with error -13 [9.873912] snd_via82xx :00:0c.5: enabling device ( -> 0001) [ 10.234992] systemd-journald[133]: Received request to flush runtime journal from PID 1 [ 10.425400] via-rhine :00:0d.0: enabling device ( -> 0003) [ 10.460940] via-rhine :00:0d.0 eth0: VIA Rhine II at 0xf1ffe900, 00:0b:2f:43:fb:04, IRQ 9 [ 10.462200] via-rhine :00:0d.0 eth0: MII PHY found at address 16, status 0x786d advertising 01e1 Link c5e1 [ 10.480763] uhci_hcd :00:0c.2: UHCI Host Controller [ 10.481103] uhci_hcd :00:0c.2: new USB bus registered, assigned bus number 1 [ 10.481482] uhci_hcd :00:0c.2: detected 2 ports [ 10.481768] uhci_hcd :00:0c.2: irq 9, io base 0x1040 [ 10.482306] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [ 10.482646] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.496172] usb usb1: Product: UHCI Host Controller [ 10.509022] usb usb1: Manufacturer: Linux 3.16.0-4-powerpc uhci_hcd [ 10.521857] usb usb1: SerialNumber: :00:0c.2 [ 10.587163] hub 1-0:1.0: USB hub found [ 10.587190] hub 1-0:1.0: 2 ports detected [ 10.587827] ehci-pci :00:05.2: EHCI Host Controller [ 10.587850] ehci-pci :00:05.2: new USB bus registered, assigned bus number 2 [ 10.588018] ehci-pci :00:05.2: irq 9, io mem 0x80002800 [ 10.596335] ehci-pci :00:05.2: USB 2.0 started, EHCI 1.00 [ 10.596575] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 10.596581] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.596585] usb usb2: Product: EHCI Host Controller [ 10.596589] usb usb2: Manufacturer: Linux 3.16.0-4-powerpc ehci_hcd [ 10.596593] usb usb2: SerialNumber: :00:05.2 [ 10.597535] hub 2-0:1.0: USB hub found [ 10.597685] hub 2-0:1.0: 5 ports detected [ 10.598436] uhci_hcd :00:0c.3: UHCI Host Controller [ 10.598457] uhci_hcd :00:0c.3: new USB bus registered, assigned bus number 3 [ 10.598473] uhci_hcd :00:0c.3: detected 2 ports [ 10.598522] uhci_hcd :00:0c.3: irq 9, io base 0x1060 [ 10.598731] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 10.598737] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.598741] usb usb3: Product: UHCI Host Controller [ 10.598744] usb usb3: Manufacturer: Linux 3.16.0-4-powerpc uhci_hcd [ 10.598748] usb usb3: SerialNumber: :00:0c.3 [ 10.599440] hub 3-0:1.0: USB hub found [ 10.599573] hub 3-0:1.0: 2 ports detected [ 10.946
Re: Bug#774620: debian-installer: scsi_transport_spi.ko is missing on the amd64 netboot image
Ben Hutchings (2015-04-06): > I don't get it. The netboot image isn't supposed to have SCSI support, > it's supposed to download the SCSI module packages if needed. Bah, colour me stupid… > As it happens, it does include usb-storage-modules and that depends on > scsi-core-modules, which now includes some of the traditional SCSI > transports. But that's an implementation detail. … and sorry for wasting your time. > Is anything broken in downloading of SCSI module packages? Or was this > just another case where the PXE files weren't updated at a point > release? The netboot image for Debian 7.8 amd64 works for me with > QEMU's SCSI HD emulation. Yeah, that's a possibility… Jean? Mraw, KiBi. signature.asc Description: Digital signature
Bug#780773: Please backport EDAC_IE31200 to Linux 3.16.x
Bug #780773 requests backporting a new EDAC (Error Detection And Correction) driver that is wanted on some Intel-based servers. It seems to be simple to backport to 3.16, but I'm not sure whether it meets the release criteria. EDAC drivers are not needed for hardware enablement, but they are needed for logging of correctable ECC errors and detailed information about uncorrectable ECC errors, which is important for highly reliable systems. Please can I have an ack or nak from the release team? Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Re: Uploading linux (3.16.7-ckt9-1)
On 2015-04-06 23:38, Ben Hutchings wrote: > On Mon, 2015-04-06 at 23:25 +0200, Niels Thykier wrote: >> On 2015-04-06 23:11, Ben Hutchings wrote: >>> I intend to upload linux version 3.16.7-ckt9-1 to unstable tomorrow >>> evening (Tuesday 7th April). > [...] >>> - Fix for data corruption on some Marvell Armada SoCs > [...] >> Thanks for the update. >> >> Could I perhaps convince you to comment on the RC bug #780858. It is >> tagged pending, but I do not see it listed above? > > It's there, just not with the same title. :-) > > Ben. > Ah thanks. I was confused by the absent "Closes"-statement, thanks for clarifying it. :) Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5522ff98.7010...@thykier.net
Bug#780686: linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell
Control: tag -1 upstream fixed-upstream On Mon, 2015-04-06 at 22:43 +0100, Chris Bainbridge wrote: > > Both of those fixes are included in 3.16.7-ckt7-1, the version you > > reported this against. Are you still seeing a similar problem? > > So they are. Hmm. I was getting a hang every day or so with > 3.16.7-ckt7-1. With latest linux git I am getting zero hangs. There > was also a report in the Launchpad bug from someone who was still > getting hangs using a kernel with the fix. So it appears there is some > other fix that is still missing, but there are a lot of drm/i915 > changes between 3.16 and current git. Do you mass import drm fixes or > do you require a cherry picked patch? We need cherry-picked patches. Pulling the whole lot is sure to bring in new regressions as well as fixes. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#780686: linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell
Processing control commands: > tag -1 upstream fixed-upstream Bug #780686 [src:linux] linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell Added tag(s) upstream and fixed-upstream. -- 780686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780686 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: https://lists.debian.org/handler.s.b780686.142835670026252.transcr...@bugs.debian.org
Bug#780686: linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell
> Both of those fixes are included in 3.16.7-ckt7-1, the version you > reported this against. Are you still seeing a similar problem? So they are. Hmm. I was getting a hang every day or so with 3.16.7-ckt7-1. With latest linux git I am getting zero hangs. There was also a report in the Launchpad bug from someone who was still getting hangs using a kernel with the fix. So it appears there is some other fix that is still missing, but there are a lot of drm/i915 changes between 3.16 and current git. Do you mass import drm fixes or do you require a cherry picked patch? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP-bSRaNjxDf4RG4AY88zRVez-YZRphjW=h3oe28ugenv5k...@mail.gmail.com
Re: Uploading linux (3.16.7-ckt9-1)
On Mon, 2015-04-06 at 23:25 +0200, Niels Thykier wrote: > On 2015-04-06 23:11, Ben Hutchings wrote: > > I intend to upload linux version 3.16.7-ckt9-1 to unstable tomorrow > > evening (Tuesday 7th April). [...] > > - Fix for data corruption on some Marvell Armada SoCs [...] > Thanks for the update. > > Could I perhaps convince you to comment on the RC bug #780858. It is > tagged pending, but I do not see it listed above? It's there, just not with the same title. :-) Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Re: Bug#774620: debian-installer: scsi_transport_spi.ko is missing on the amd64 netboot image
On Thu, 2015-02-26 at 06:00 +0100, Cyril Brulebois wrote: > Cyril Brulebois (2015-01-06): > > Hi Jean, > > > > and thanks for the report. > > > > Jean Weisbuch (2015-01-05): > > > Package: debian-installer > > > Version: 20130613+deb7u2 > > > Severity: important > > > Tags: d-i > > > > > > The debian-installer netboot image on wheezy is missing the module > > > "./lib/modules/3.2.0-4-amd64/kernel/drivers/scsi/scsi_transport_spi.ko" > > > which makes the mptspi module (which is used by VMWare virtual > > > controller among others) unloadable with "Unknown symbol" errors on > > > the dmesg resulting on the installer unable to detect the disk(s). > > > > > > As a side note, both the i386 netboot and the amd64 classic netinstall > > > images contains the module. > > > > > > Taking the module from the netinstall amd64 iso and > > > putting it on the initrd image solves the problem and the installer > > > works fine then. > > > > > > > > > It seems that the file has been missing for quite a long time : > > > https://lists.debian.org/debian-boot/2011/03/msg00233.html > > > > It seems to have been fixed in: > > | linux (3.14.13-2) unstable; urgency=medium > > | … > > | * Add scsi_transport_sas and scsi_transport_spi to scsi-core-modules > > udeb > > | as optional so that these modules do not end up in two different udebs > > | as dependencies. Remove them from the i386, ia64, powerpc and sparc > > | definition. > > | … > > | -- Aurelien Jarno Thu, 24 Jul 2014 21:05:08 +0200 > > > > which has been merged as r21638. > > > > Should probably be reassigned to src:linux, and the following patch > > against the wheezy branch should help? (I've verified these modules are > > indeed shipped in the linux-image package; some others exist as well, > > not sure they're worth shipping along…) > > Kernel-team: what's your opinion on this? > > I'm attaching a refreshed (debian/changelog…) patch. I don't get it. The netboot image isn't supposed to have SCSI support, it's supposed to download the SCSI module packages if needed. As it happens, it does include usb-storage-modules and that depends on scsi-core-modules, which now includes some of the traditional SCSI transports. But that's an implementation detail. Is anything broken in downloading of SCSI module packages? Or was this just another case where the PXE files weren't updated at a point release? The netboot image for Debian 7.8 amd64 works for me with QEMU's SCSI HD emulation. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Re: Uploading linux (3.16.7-ckt9-1)
On 2015-04-06 23:11, Ben Hutchings wrote:
> I intend to upload linux version 3.16.7-ckt9-1 to unstable tomorrow
> evening (Tuesday 7th April).
>
> The currently pending changes are:
> - Many fixes from stable release 3.16.7-ckt{8,9}
> - New hardware support: early console support on various systems,
> Xen MCE log, power control on some Allwinner (sunxi) systems,
> FocalTech PS/2 touchpads
> - Security fixes: CVE-2014-8159, CVE-2014-9710, CVE-2015-0275,
> CVE-2015-2666, CVE-2015-2922
> - Fix for data corruption on some Marvell Armada SoCs
> - Require upgraded flash-kernel on Kirkwood systems to avoid boot
> failure
> - Use the right fan control drivers on G5 PowerMac
> - Fix two instances of boot console noise on x86 (#781953, #781418)
> - Fix WARNING when attaching some display devices to i915 GPU
> - Fix race condition in thingm driver
> - Hide eMMC RPMB partitions which userland doesn't need to see and
> which often cause hangs
>
> I'm hoping this will be the one that goes into Debian 8.0, but there is
> probably a window of a few days after this to fix any showstoppers.
>
> Ben.
>
Hi Ben,
Thanks for the update.
Could I perhaps convince you to comment on the RC bug #780858. It is
tagged pending, but I do not see it listed above?
Thanks,
~Niels
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5522f9af.5060...@thykier.net
Processed: reassign 781193 to src:linux, found 781193 in 3.16.7-ckt4-3
Processing commands for cont...@bugs.debian.org: > reassign 781193 src:linux 3.16.7-ckt4-3~bpo70+1 Bug #781193 [linux-image-3.16.0-0.bpo.4-kirkwood] linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug Bug reassigned from package 'linux-image-3.16.0-0.bpo.4-kirkwood' to 'src:linux'. No longer marked as found in versions linux/3.16.7-ckt4-3~bpo70+1. Ignoring request to alter fixed versions of bug #781193 to the same values previously set Bug #781193 [src:linux] linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug Marked as found in versions linux/3.16.7-ckt4-3~bpo70+1. > found 781193 3.16.7-ckt4-3 Bug #781193 [src:linux] linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug Marked as found in versions linux/3.16.7-ckt4-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 781193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781193 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: https://lists.debian.org/handler.s.c.142835476014311.transcr...@bugs.debian.org
Processed: tagging 781193
Processing commands for cont...@bugs.debian.org: > tags 781193 + pending Bug #781193 [src:linux] linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 781193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781193 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: https://lists.debian.org/handler.s.c.142835477514343.transcr...@bugs.debian.org
Processed: limit source to linux, tagging 781953, tagging 775217, tagging 780055, tagging 780971, tagging 781418 ...
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 781953 + pending Bug #781953 [src:linux] linux-image-3.16.0-4-amd64: Verbose messages at boot time Added tag(s) pending. > tags 775217 + pending Bug #775217 [src:linux] drm/i915: Add limited color range readout for HDMI/DP ports on g4x/vlv/chv Added tag(s) pending. > tags 780055 + pending Bug #780055 [src:linux] linux: Kernel crash with ThingM blink(1) mk2 device Added tag(s) pending. > tags 780971 + pending Bug #780971 [src:linux] Touchpad detected as mouse on Asus ux303ln laptop Added tag(s) pending. > tags 781418 + pending Bug #781418 [src:linux] intel_rapl: RAPL domain dram detection failed Added tag(s) pending. > tags 781934 + pending Bug #781934 [src:linux] linux: XServe G5 all fans run full speed Bug #778787 [src:linux] linux-image-3.19.0: fails to handle fans with windfarm-pm72 on powermac7, 3 (Powermac G5) Added tag(s) pending. Added tag(s) pending. > tags 782038 + pending Bug #782038 [src:linux] Access to RPMB may fail with long timeout Bug #759656 [src:linux] linux-image-3.14-2-amd64: mmcblk0rpmb time-out and I/O errors Bug #780818 [src:linux] lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs) Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 759656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759656 775217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775217 778787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778787 780055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780055 780818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780818 780971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780971 781418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781418 781934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781934 781953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781953 782038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782038 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: https://lists.debian.org/handler.s.c.142835471414142.transcr...@bugs.debian.org
Uploading linux (3.16.7-ckt9-1)
I intend to upload linux version 3.16.7-ckt9-1 to unstable tomorrow
evening (Tuesday 7th April).
The currently pending changes are:
- Many fixes from stable release 3.16.7-ckt{8,9}
- New hardware support: early console support on various systems,
Xen MCE log, power control on some Allwinner (sunxi) systems,
FocalTech PS/2 touchpads
- Security fixes: CVE-2014-8159, CVE-2014-9710, CVE-2015-0275,
CVE-2015-2666, CVE-2015-2922
- Fix for data corruption on some Marvell Armada SoCs
- Require upgraded flash-kernel on Kirkwood systems to avoid boot
failure
- Use the right fan control drivers on G5 PowerMac
- Fix two instances of boot console noise on x86 (#781953, #781418)
- Fix WARNING when attaching some display devices to i915 GPU
- Fix race condition in thingm driver
- Hide eMMC RPMB partitions which userland doesn't need to see and
which often cause hangs
I'm hoping this will be the one that goes into Debian 8.0, but there is
probably a window of a few days after this to fix any showstoppers.
Ben.
--
Ben Hutchings
Power corrupts. Absolute power is kind of neat.
- John Lehman, Secretary of the US Navy 1981-1987
signature.asc
Description: This is a digitally signed message part
Processed: affects 780818
Processing commands for cont...@bugs.debian.org: > affects 780818 partman-base lvm2 Bug #780818 [src:linux] lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs) Bug #759656 [src:linux] linux-image-3.14-2-amd64: mmcblk0rpmb time-out and I/O errors Bug #782038 [src:linux] Access to RPMB may fail with long timeout Added indication that 780818 affects partman-base and lvm2 Added indication that 759656 affects partman-base and lvm2 Added indication that 782038 affects partman-base and lvm2 > thanks Stopping processing here. Please contact me if you need assistance. -- 759656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759656 780818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780818 782038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782038 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: https://lists.debian.org/handler.s.c.14283533786913.transcr...@bugs.debian.org
Processed: forcibly merging 759656 780818 782038
Processing commands for cont...@bugs.debian.org: > # oops, why did I add another of these > forcemerge 759656 780818 782038 Bug #759656 [src:linux] linux-image-3.14-2-amd64: mmcblk0rpmb time-out and I/O errors Bug #780818 [src:linux] lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs) Severity set to 'important' from 'normal' Removed indication that 780818 affects partman-base and lvm2 Marked as found in versions linux/3.14.15-2 and linux/3.16.7-ckt7-1. Added tag(s) upstream. Bug #782038 [src:linux] Access to RPMB may fail with long timeout Removed indication that 782038 affects partman-base and lvm2 Marked as found in versions linux/3.14.15-2. Added tag(s) upstream. Bug #759656 [src:linux] linux-image-3.14-2-amd64: mmcblk0rpmb time-out and I/O errors Marked as found in versions linux/3.16.7-ckt7-1. Merged 759656 780818 782038 > thanks Stopping processing here. Please contact me if you need assistance. -- 759656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759656 780818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780818 782038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782038 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: https://lists.debian.org/handler.s.c.14283529514965.transcr...@bugs.debian.org
Bug#780686: linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell
Control: tag -1 moreinfo On Tue, 2015-03-17 at 19:59 +, Chris Bainbridge wrote: > Package: src:linux > Version: 3.16.7-ckt7-1 > Severity: normal > > Dear Maintainer, > > As documented at > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384342 a > GPU hang will regularly occur on Intel IvyBridge and Haswell GPUs. > > This was fixed upstream in patches 48bf5b2 and 2a92d5b which were > included in Linux 3.19. > > Author: Chris Wilson > Date: Sat Dec 27 09:48:28 2014 + > > drm/i915: Ban Haswell from using RCS flips > > Like Ivybridge, we have reports that we get random hangs when > flipping > with multiple pipes. Extend > > commit 2a92d5bca1999b69c78f3c3e97b5484985b094b9 > Author: Chris Wilson > Date: Tue Jul 8 10:40:29 2014 +0100 > > drm/i915: Disable RCS flips on Ivybridge > > to also apply to Haswell. Both of those fixes are included in 3.16.7-ckt7-1, the version you reported this against. Are you still seeing a similar problem? Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#780686: linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell
Processing control commands: > tag -1 moreinfo Bug #780686 [src:linux] linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell Added tag(s) moreinfo. -- 780686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780686 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: https://lists.debian.org/handler.s.b780686.14283526113323.transcr...@bugs.debian.org
Processed: severity of 780862 is important, tagging 780862
Processing commands for cont...@bugs.debian.org: > # missing hardware support > severity 780862 important Bug #780862 [src:linux] linux-image-3.16.0-4-amd64: please backport 2015 ThinkPad Trackpoint/Touchpad support patches Severity set to 'important' from 'normal' > tags 780862 + upstream fixed-upstream Bug #780862 [src:linux] linux-image-3.16.0-4-amd64: please backport 2015 ThinkPad Trackpoint/Touchpad support patches Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 780862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780862 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: https://lists.debian.org/handler.s.c.142835178630804.transcr...@bugs.debian.org
Processed: severity of 781418 is important
Processing commands for cont...@bugs.debian.org: > # regression; spurious warning message on screen > severity 781418 important Bug #781418 [src:linux] intel_rapl: RAPL domain dram detection failed Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 781418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781418 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: https://lists.debian.org/handler.s.c.142835149128836.transcr...@bugs.debian.org
Bug#781845: linux-image-3.16.0-4-powerpc: kernel crash on powerpc
Control: tag -1 moreinfo On Fri, 2015-04-03 at 14:23 -0400, Pranith Kumar wrote: > > Package: src:linux > Version: 3.16.7-ckt7-1 > Severity: important > > Dear Maintainer, > > The kernel crashed on my ppc32 machine. It crashes pretty reliably. I can try > to > help debug and triage this bug. I see several warnings in the kernel log included in your report. Do those consistently appear? Do you see any more messages on the screen when it crashes? If so, please send them as an attachment. Is this system stable if you use the kernel from Debian 7 'wheezy' instead? Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#781845: linux-image-3.16.0-4-powerpc: kernel crash on powerpc
Processing control commands: > tag -1 moreinfo Bug #781845 [src:linux] linux-image-3.16.0-4-powerpc: kernel crash on powerpc Added tag(s) moreinfo. -- 781845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781845 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: https://lists.debian.org/handler.s.b781845.142835131127637.transcr...@bugs.debian.org
Bug#776192: Linux null-pointer deref in 3.16.7-ctk2-1 (was: Bug#776192: upgrade-reports wheezy to jessie boot problem)
Control: tag -1 patch
On Mon, 2015-04-06 at 20:50 +0100, Ben Hutchings wrote:
> Control: tag -1 moreinfo upstream
> Control: forwarded -1
> http://thread.gmane.org/gmane.linux.ubuntu.devel.kernel.general/39123/
>
> On Thu, 2015-04-02 at 01:01 -0700, Bill MacAllister wrote:
> >
> > --On Sunday, January 25, 2015 11:25:34 AM +0100 Niels Thykier
> > wrote:
> >
> > > I have CC'ed the Debian linux maintainers as I noticed your kernel
> > > reports a null pointer deference in the kernel (see below for the
> > > trace). I have taken the liberty of reassigning it to the linux package
> > > as well.
> > > @linux maintainers: if you suspect that the null pointer issue is
> > > unrelated to Bills boot problem, please clone the bug and throw the bug
> > > back to upgrade-reports for further analysis.
> > >
> > > Bug link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776192
> > >
> > > Thanks,
> > > ~Niels
> >
> > Any news on this problem? I am still seeing this problem even though
> > we have moved on to 3.16.7-ckt7-1.
> >
> > I had the thought to look at the kernel modules that support the
> > PERC controller on these Dell systems. Explicitly specifying the
> > mpt* modules and updating initramfs does not fix the problem.
> >
> > We have plenty of these 1950s. I really need to come up with a
> > work around or a solution to this problem. Any ideas about what
> > I should try next?
>
> It looks the same as this problem:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705
> http://thread.gmane.org/gmane.linux.ubuntu.devel.kernel.general/39123/
>
> Can you confirm that the LSI controller (mptsas driver) takes more than
> 30 seconds to scan for devices at boot time when running the wheezy
> (Linux 3.2) kernel?
>
> If so then we need a change to the udev rules to increase the timeout
> for this driver module. We also need to fix the driver so that it fails
> cleanly if it still hits the timeout.
Also, does this patch work around the problem?
(Instructions for rebuilding the Debian kernel package:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
)
Ben.
--
Ben Hutchings
Power corrupts. Absolute power is kind of neat.
- John Lehman, Secretary of the US Navy 1981-1987
From: Oleg Nesterov
Subject: Re: please fix FUSION (Was: [v3.13][v3.14][Regression]
kthread:makekthread_create()killable)
Date: Fri, 21 Mar 2014 19:34:43 +0100
Origin: http://permalink.gmane.org/gmane.linux.kernel/1671312
Bug-Debian: https://bugs.debian.org/776192
On 03/20, Oleg Nesterov wrote:
>
> On 03/20, Joseph Salisbury wrote:
> >
> > There was some testing done with your test kernel. The data collected
> > while running your kernel is available in the bug report:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/comments/58
>
> Joseph, thanks a lot.
>
> I'll try to read the logs tomorrow, but at first glance Tetsuo was right,
> I do not see a "long" sleep in that log.
Yes, it seems that it actually needs > 30 secs. It spends most of the time
(30.13286 seconds) in
msleep+0x20/0x30
WaitForDoorbellInt+0x103/0x130 [mptbase]
WaitForDoorbellReply+0x42/0x220 [mptbase]
mpt_handshake_req_reply_wait+0x1dc/0x2c0 [mptbase]
SendPortEnable.constprop.23+0x94/0xc0 [mptbase]
WaitForDoorbellInt() does msleep(1) in a loop. This trace starts at the line
6001, and it is repeated 3792 times, till the line 176686 which apparently
shows the trace of the 2nd WaitForDoorbellInt() in WaitForDoorbellReply().
SendPortEnable:
if (ioc->ir_firmware || ioc->bus_type == SAS) {
rc = mpt_handshake_req_reply_wait(ioc, req_sz,
(u32*)&port_enable, reply_sz, (u16*)&reply_buf,
300 /*seconds*/, sleepFlag);
} else {
rc = mpt_handshake_req_reply_wait(ioc, req_sz,
(u32*)&port_enable, reply_sz, (u16*)&reply_buf,
30 /*seconds*/, sleepFlag);
}
I am wondering which branch calls mpt_handshake_req_reply_wait(), the
else's timeout=30 (passed to the 1st WaitForDoorbellInt) suspiciously
matches the time WaitForDoorbellInt() actually runs... But everything
works fine and at first glance the potential timeout error should be
propogated correctly. So "timeout" is probably 300. And probably this
all is fine.
All I can suggest is the dirty hack for now. User-space should be
changed too, I think, but this is another story.
Tetsuo, what do you think?
Oleg.
---
--- a/drivers/message/fusion/mptsas.c
+++ b/drivers/message/fusion/mptsas.c
@@ -5393,6 +5393,8 @@ static struct pci_driver mptsas_driver = {
#endif
};
+#include
+
static int __init
mptsas_init(void)
{
@@ -5422,7 +5424,31 @@ mptsas_init(void)
mpt_event_register(mptsasDoneCtx, mptsas_event_process);
mpt_reset_register(mptsasDoneCtx, mptsas_ioc_reset);
- error = pci_register_driver(&mptsas_driver);
+ {
+ sigset_t full, save;
+ /*
+ * KILL ME. THIS IS THE DIRTY AND WRONG HACK WAITING FOR THE
+ * FIX FROM MAINTAINERS.
+ *
+ * - This driver needs a lot of time to complete SendPortEnable()
+ *
Processed: Re: Linux null-pointer deref in 3.16.7-ctk2-1 (was: Bug#776192: upgrade-reports wheezy to jessie boot problem)
Processing control commands: > tag -1 patch Bug #776192 [src:linux] mptsas probe failure and crash, probably related to udev timeout Added tag(s) patch. -- 776192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776192 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: https://lists.debian.org/handler.s.b776192.142835106226139.transcr...@bugs.debian.org
Processed: retitle 776192 to mptsas probe failure and crash, probably related to udev timeout
Processing commands for cont...@bugs.debian.org: > retitle 776192 mptsas probe failure and crash, probably related to udev > timeout Bug #776192 [src:linux] linux: null pointer deref in 3.16.7-ctk2-1 Changed Bug title to 'mptsas probe failure and crash, probably related to udev timeout' from 'linux: null pointer deref in 3.16.7-ctk2-1' > thanks Stopping processing here. Please contact me if you need assistance. -- 776192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776192 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: https://lists.debian.org/handler.s.c.142834953315367.transcr...@bugs.debian.org
linux_3.2.68-1_multi.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 31 Mar 2015 09:30:16 +0100 Source: linux Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4 linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha linux-headers-3.2.0-4-common linux-image-3.2.0-4-alpha-generic linux-headers-3.2.0-4-alpha-generic linux-image-3.2.0-4-alpha-smp linux-headers-3.2.0-4-alpha-smp linux-image-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-all-amd64 kernel-image-3.2.0-4-amd64-di nic-modules-3.2.0-4-amd64-di nic-extra-modules-3.2.0-4-amd64-di nic-wireless-modules-3.2.0-4-amd64-di nic-shared-modules-3.2.0-4-amd64-di serial-modules-3.2.0-4-amd64-di usb-serial-modules-3.2.0-4-amd64-di ppp-modules-3.2.0-4-amd64-di pata-modules-3.2.0-4-amd64-di cdrom-core-modules-3.2.0-4-amd64-di firewire-core-modules-3.2.0-4-amd64-di scsi-core-modules-3.2.0-4-amd64-di scsi-modules-3.2.0-4-amd64-di scsi-common-modules-3.2.0-4-amd64-di scsi-extra-modules-3.2.0-4-amd64-di plip-modules-3.2.0-4-amd64-di floppy-modules-3.2.0-4-amd64-di loop-modules-3.2.0-4-amd64-di btrfs-modules-3.2.0-4-amd64-di ext2-modules-3.2.0-4-amd64-di ext3-modules-3.2.0-4-amd64-di ext4-modules-3.2.0-4-amd64-di isofs-modules-3.2.0-4-amd64-di jfs-modules-3.2.0-4-amd64-di ntfs-modules-3.2.0-4-amd64-di reiserfs-modules-3.2.0-4-amd64-di xfs-modules-3.2.0-4-amd64-di fat-modules-3.2.0-4-amd64-di ufs-modules-3.2.0-4-amd64-di qnx4-modules-3.2.0-4-amd64-di md-modules-3.2.0-4-amd64-di multipath-modules-3.2.0-4-amd64-di usb-modules-3.2.0-4-amd64-di usb-storage-modules-3.2.0-4-amd64-di pcmcia-storage-modules-3.2.0-4-amd64-di fb-modules-3.2.0-4-amd64-di input-modules-3.2.0-4-amd64-di event-modules-3.2.0-4-amd64-di mouse-modules-3.2.0-4-amd64-di irda-modules-3.2.0-4-amd64-di parport-modules-3.2.0-4-amd64-di nic-pcmcia-modules-3.2.0-4-amd64-di pcmcia-modules-3.2.0-4-amd64-di nic-usb-modules-3.2.0-4-amd64-di sata-modules-3.2.0-4-amd64-di core-modules-3.2.0-4-amd64-di acpi-modules-3.2.0-4-amd64-di i2c-modules-3.2.0-4-amd64-di crc-modules-3.2.0-4-amd64-di crypto-modules-3.2.0-4-amd64-di crypto-dm-modules-3.2.0-4-amd64-di efi-modules-3.2.0-4-amd64-di ata-modules-3.2.0-4-amd64-di mmc-core-modules-3.2.0-4-amd64-di mmc-modules-3.2.0-4-amd64-di nbd-modules-3.2.0-4-amd64-di squashfs-modules-3.2.0-4-amd64-di speakup-modules-3.2.0-4-amd64-di virtio-modules-3.2.0-4-amd64-di uinput-modules-3.2.0-4-amd64-di sound-modules-3.2.0-4-amd64-di zlib-modules-3.2.0-4-amd64-di hyperv-modules-3.2.0-4-amd64-di udf-modules-3.2.0-4-amd64-di fuse-modules-3.2.0-4-amd64-di linux-image-3.2.0-4-amd64 linux-headers-3.2.0-4-amd64 linux-image-3.2.0-4-amd64-dbg xen-linux-system-3.2.0-4-amd64 linux-headers-3.2.0-4-common-rt linux-image-3.2.0-4-rt-amd64 linux-headers-3.2.0-4-rt-amd64 linux-image-3.2.0-4-rt-amd64-dbg linux-headers-3.2.0-4-all-armel kernel-image-3.2.0-4-iop32x-di nic-modules-3.2.0-4-iop32x-di nic-shared-modules-3.2.0-4-iop32x-di usb-serial-modules-3.2.0-4-iop32x-di ppp-modules-3.2.0-4-iop32x-di pata-modules-3.2.0-4-iop32x-di cdrom-core-modules-3.2.0-4-iop32x-di scsi-core-modules-3.2.0-4-iop32x-di loop-modules-3.2.0-4-iop32x-di ipv6-modules-3.2.0-4-iop32x-di btrfs-modules-3.2.0-4-iop32x-di ext2-modules-3.2.0-4-iop32x-di ext3-modules-3.2.0-4-iop32x-di ext4-modules-3.2.0-4-iop32x-di isofs-modules-3.2.0-4-iop32x-di jffs2-modules-3.2.0-4-iop32x-di jfs-modules-3.2.0-4-iop32x-di reiserfs-modules-3.2.0-4-iop32x-di fat-modules-3.2.0-4-iop32x-di md-modules-3.2.0-4-iop32x-di multipath-modules-3.2.0-4-iop32x-di usb-modules-3.2.0-4-iop32x-di usb-storage-modules-3.2.0-4-iop32x-di event-modules-3.2.0-4-iop32x-di nic-usb-modules-3.2.0-4-iop32x-di sata-modules-3.2.0-4-iop32x-di core-modules-3.2.0-4-iop32x-di crc-modules-3.2.0-4-iop32x-di crypto-modules-3.2.0-4-iop32x-di crypto-dm-modules-3.2.0-4-iop32x-di ata-modules-3.2.0-4-iop32x-di nbd-modules-3.2.0-4-iop32x-di squashfs-modules-3.2.0-4-iop32x-di zlib-modules-3.2.0-4-iop32x-di udf-modules-3.2.0-4-iop32x-di fuse-modules-3.2.0-4-iop32x-di kernel-image-3.2.0-4-kirkwood-di nic-modules-3.2.0-4-kirkwood-di nic-shared-modules-3.2.0-4-kirkwood-di usb-serial-modules-3.2.0-4-kirkwood-di ppp-modules-3.2.0-4-kirkwood-di cdrom-core-modules-3.2.0-4-kirkwood-di scsi-core-modules-3.2.0-4-kirkwood-di loop-modules-3.2.0-4-kirkwood-di ipv6-modules-3.2.0-4-kirkwood-di btrfs-modules-3.2.0-4-kirkwood-di ext2-modules-3.2.0-4-kirkwood-di ext3-modules-3.2.0-4-kirkwood-di ext4-modules-3.2.0-4-kirkwood-di isofs-modules-3.2.0-4-kirkwood-di jfs-modules-3.2.0-4-kirkwood-di reiserfs-modules-3.2.0-4-kirkwood-di fat-modules-3.2.0-4-kirkwood-di minix-modules-3.2.0-4-kirkwood-di md-modules-3.2.0-4-kirkwood-di multipath-modules-3.2.0-4-kirkwood-di usb-modules-3.2.0-4-kirkwood-di usb-storage-modules-3.2.0-4-kirkwood-di fb-modules-3.2.0-4-kirkwood-di input-modules-3.2.0-4-kirkwood-di event-modules-3.2.0-4-kirkwood-di mouse-modules-3.2.0-4-kirkwo
Bug#780818: lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs)
On Mon 2015-04-06 15:29:23 -0400, Ben Hutchings wrote: > Ideally the driver would avoid doing whatever it is that results in a > hang, or would expose the RPMB only if it's really accessible. I > suspect that where access to the RPMB hangs this is because the system > firmware (BIOS/EFI) has intentionally disabled access before handing > over to the OS. That seems like a plausible explanation of the situation to me, but i don't know enough to tell if that's the case on the machinery i've tested with. > Hiding RPMBs seems to be a popular workaround, and I doubt that it will > be useful to access them under a Debian system or other free operating > system, so that's what I intend to do. If we need to change that later > we can add a module parameter to override this. Thanks, this seems like a sensible workaround for the moment. --dkg -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87vbh958o7@alice.fifthhorseman.net
Processed: Re: Linux null-pointer deref in 3.16.7-ctk2-1 (was: Bug#776192: upgrade-reports wheezy to jessie boot problem)
Processing control commands: > tag -1 moreinfo upstream Bug #776192 [src:linux] mptsas probe failure and crash, probably related to udev timeout Added tag(s) upstream and moreinfo. > forwarded -1 > http://thread.gmane.org/gmane.linux.ubuntu.devel.kernel.general/39123/ Bug #776192 [src:linux] mptsas probe failure and crash, probably related to udev timeout Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.ubuntu.devel.kernel.general/39123/'. -- 776192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776192 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: https://lists.debian.org/handler.s.b776192.142834988217640.transcr...@bugs.debian.org
Bug#781548: marked as done (Support for HP SmartArray Gen9 Cards)
Your message dated Mon, 06 Apr 2015 19:47:11 +
with message-id
and subject line Bug#781548: fixed in linux 3.2.68-1
has caused the Debian Bug report #781548,
regarding Support for HP SmartArray Gen9 Cards
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.)
--
781548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.2.0-4-amd64
Version: 3.2.65-1+deb7u2
Hi,
nowadays wheezy kernel cant boot on Gen9 HP Servers because of the new PCI
ids of Smart Array Cards, the patch attached solves the problem
supporting the new Gen9 Cards
HTH
diff -uNr a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
--- a/drivers/scsi/hpsa.c 2014-12-14 16:24:02.0 +
+++ b/drivers/scsi/hpsa.c 2015-03-26 22:19:29.907717557 +
@@ -107,6 +107,19 @@
{PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSH, 0x103C, 0x1926},
{PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSH, 0x103C, 0x1928},
{PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSF, 0x103C, 0x334d},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSH, 0x103C, 0x1929},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21BD},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21BE},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21BF},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C0},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C1},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C2},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C3},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C4},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C5},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C7},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C8},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C9},
{PCI_VENDOR_ID_HP, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
PCI_CLASS_STORAGE_RAID << 8, 0x << 8, 0},
{0,}
@@ -142,6 +155,18 @@
{0x1926103C, "Smart Array", &SA5_access},
{0x1928103C, "Smart Array", &SA5_access},
{0x334d103C, "Smart Array P822se", &SA5_access},
+{0x21BD103C, "Smart Array", &SA5_access},
+{0x21BE103C, "Smart Array", &SA5_access},
+{0x21BF103C, "Smart Array", &SA5_access},
+{0x21C0103C, "Smart Array", &SA5_access},
+{0x21C1103C, "Smart Array", &SA5_access},
+{0x21C2103C, "Smart Array", &SA5_access},
+{0x21C3103C, "Smart Array", &SA5_access},
+{0x21C4103C, "Smart Array", &SA5_access},
+{0x21C5103C, "Smart Array", &SA5_access},
+{0x21C7103C, "Smart Array", &SA5_access},
+{0x21C8103C, "Smart Array", &SA5_access},
+{0x21C9103C, "Smart Array", &SA5_access},
{0x103C, "Unknown Smart Array", &SA5_access},
};
diff -uNr a/include/linux/pci_ids.h b/include/linux/pci_ids.h
--- a/include/linux/pci_ids.h 2014-12-14 16:24:02.0 +
+++ b/include/linux/pci_ids.h 2015-03-26 22:19:01.498077026 +
@@ -753,6 +753,7 @@
#define PCI_DEVICE_ID_HP_CISSE 0x323a
#define PCI_DEVICE_ID_HP_CISSF 0x323b
#define PCI_DEVICE_ID_HP_CISSH 0x323c
+#define PCI_DEVICE_ID_HP_CISSI 0x3239
#define PCI_DEVICE_ID_HP_ZX2_IOC 0x4031
#define PCI_VENDOR_ID_PCTECH 0x1042
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.2.68-1
We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 781...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings (supplier of updated linux package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 31 Mar 2015 09:30:16 +0100
Source: linux
Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4
linux-libc-dev linux-headers-3.2.0-4-all linux
Bug#732689: marked as done (ipset: kernel panic when adding ip to bitmap:ip)
Your message dated Mon, 06 Apr 2015 19:47:11 + with message-id and subject line Bug#732689: fixed in linux 3.2.68-1 has caused the Debian Bug report #732689, regarding ipset: kernel panic when adding ip to bitmap:ip 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.) -- 732689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ipset Version: 6.12.1-1 Severity: important # ipset create ipv4_ch bitmap:ip range 0.0.0.0/0 # ipset list [ another previously defined hash:net set. No problem with that. ] Name: ipv4_ch Type: bitmap:ip Header: range 0.0.0.0-255.255.255.255 Size in memory: 120 References: 0 Members: # ipset add ipv4_ch 5.1.96.0/21 Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.395819] Oops: 0002 [#1] SMP Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] Stack: Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] Call Trace: Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] Code: 31 c0 48 85 ff 74 19 48 81 ff ff ff ff 7f b0 01 74 0e 48 8b 05 e7 af 1e e1 48 29 f8 48 c1 e8 3f c3 48 8b 47 40 0f b7 16 48 8b 00 0f ab 10 19 d2 83 fa 01 19 c0 f7 d0 25 f9 ef ff ff c3 48 8b Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.398495] CR2: 0c10 Message from syslogd@pe1 at Dec 20 12:14:53 ... kernel:[3088568.428341] Kernel panic - not syncing: Fatal exception in interrupt That's all. The machine hung completely and needed a hard reset. -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ipset depends on: ii iptables 1.4.14-3.1 ii libc6 2.13-38 ii libipset2 6.12.1-1 ipset recommends no packages. ipset suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: linux Source-Version: 3.2.68-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 732...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 31 Mar 2015 09:30:16 +0100 Source: linux Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4 linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha linux-headers-3.2.0-4-common linux-image-3.2.0-4-alpha-generic linux-headers-3.2.0-4-alpha-generic linux-image-3.2.0-4-alpha-smp linux-headers-3.2.0-4-alpha-smp linux-image-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-all-amd64 kernel-image-3.2.0-4-amd64-di nic-modules-3.2.0-4-amd64-di nic-extra-modules-3.2.0-4-amd64-di nic-wireless-modules-3.2.0-4-amd64-di nic-shared-modules-3.2.0-4-amd64-di serial-modules-3.2.0-4-amd64-di usb-serial-modules-3.2.0-4-amd64-di ppp-modules-3.2.0-4-amd64-di pata-modules-3.2.0-4-amd64-di cdrom-core-modules-3.2.0-4-amd64-di firewire-core-modules-3.2.0-4-amd64-di scsi-core-modules-3.2.0-4-amd64-di scsi-modules-3.2.0-4-amd64-di scsi-common-modules-3.2.0-4-amd64-di scsi-extra-modules-3.2.0-4-amd64-di plip-modules-3.2.0-4-amd64-di floppy-modules-3.2.0-4-amd64-di loop-modules-3.2.0-4-amd64-di btrfs-modules-3.2.0-4-amd64-di ext2-modules-3.2.0-4-amd64-di ext3-modules-3.2.0-4-amd64-di ext4-modules-3.2.0-4-amd64-di isofs-modules-3.2.0-4-amd64-di jfs-modules-3.2.0-4-amd64-di ntfs-modules-3.2.0-4-amd64-di reiserfs-modules-3.2.0-4-amd64-di xfs-modules-3.2.0-4-amd64-di fat-modules-3.2.0-4-amd64-di ufs-modules-3.2.0-4-amd64-di qnx4-modules-3.2.0-4-amd64-di md-modules-3.2.0-4-amd64-di multipath-modules-3.2.0-4-amd64-di usb-modules-3.2.0-4-amd64-di usb-storage-modules-3.2.0-4-amd64-di pcmcia-storage-modules-3.2.0-4-amd64-di fb-modules-3.2.0-4-amd64-d
Bug#731439: marked as done ("BUG: unable to handle kernel paging request at ffffffffffffffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage)
Your message dated Mon, 06 Apr 2015 19:47:11 + with message-id and subject line Bug#731439: fixed in linux 3.2.68-1 has caused the Debian Bug report #731439, regarding "BUG: unable to handle kernel paging request at ffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage 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.) -- 731439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.51-1 Severity: normal Hi We found the following by chance: We are mounting a NFSv4 export from a EMC VNx storage. There are checkpoints, which are read-only, wereas the remaining part of the volume is read-write. When by accident trying to remove a file in such a checkpoint tree, we see the kernel oops (in our regular setup we also set kernel.panic_on_oops = 1 and kernel.panic = 60, so that the machine reboots): cut-cut-cut-cut-cut-cut- [592812.122561] BUG: unable to handle kernel paging request at ffb8 [592812.126500] IP: [] nfs_mark_delegation_referenced+0x6/0x6 [nfs] [592812.126500] PGD 1607067 PUD 1608067 PMD 0 [592812.126500] Oops: [#1] SMP [592812.126500] CPU 1 [592812.126500] Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables autofs4 binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop powernow_k8 psmouse nv_tco mperf pcspkr evdev serio_raw amd64_edac_mod edac_mce_amd i2c_nforce2 k8temp shpchp i2c_core edac_core processor button thermal_sys ext4 crc16 jbd2 mbcache raid1 md_mod microcode sg sd_mod crc_t10dif usbhid sr_mod cdrom hid ata_generic pata_amd ohci_hcd sata_nv libata tg3 ehci_hcd libphy scsi_mod usbcore forcedeth usb_common [last unloaded: scsi_wait_scan] [592812.126500] [592812.126500] Pid: 25914, comm: rm Not tainted 3.2.0-4-amd64 #1 Debian 3.2.51-1 Sun Microsystems Sun Fire X2100 M2/S40 [592812.126500] RIP: 0010:[] [] nfs_mark_delegation_referenced+0x6/0x6 [nfs] [592812.126500] RSP: 0018:880197979dc0 EFLAGS: 00010246 [592812.126500] RAX: d8ca RBX: d8ca RCX: [592812.126500] RDX: 880197979e08 RSI: 0001 RDI: [592812.126500] RBP: 880197979e08 R08: R09: dead00200200 [592812.126500] R10: 8801988e4000 R11: 8801988e4000 R12: 88019759c800 [592812.126500] R13: 880197a7d400 R14: R15: [592812.126500] FS: 7f879debb700() GS:88019fd0() knlGS: [592812.126500] CS: 0010 DS: ES: CR0: 8005003b [592813.924021] CR2: ffb8 CR3: 0001969a1000 CR4: 06e0 [592813.924021] DR0: DR1: DR2: [592813.924021] DR3: DR6: 0ff0 DR7: 0400 [592813.924021] Process rm (pid: 25914, threadinfo 880197978000, task 88019531c280) [592813.924021] Stack: [592813.924021] a02c5d05 dead00200200 880123a669d0 880123a79e20 [592813.924021] 8801444689d0 880123a669d0 0001 [592813.924021] a02c6b77 [592813.924021] Call Trace: [592813.924021] [] ? nfs4_handle_exception+0x147/0x2c2 [nfs] [592813.924021] [] ? nfs4_proc_remove+0x38/0x46 [nfs] [592813.924021] [] ? nfs_unlink+0xef/0x18a [nfs] [592813.924021] [] ? vfs_unlink+0x68/0xbb [592813.924021] [] ? do_unlinkat+0xd0/0x156 [592813.924021] [] ? __call_rcu+0x21/0x12c [592813.924021] [] ? sys_faccessat+0x145/0x155 [592813.924021] [] ? system_call_fastpath+0x16/0x1b [592813.924021] Code: df e8 78 4b ff ff 48 89 ef 89 44 24 08 e8 d8 fc ff ff 8b 44 24 08 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e 41 5f c3 f0 80 4f 48 04 c3 <48> 8b 7f b8 31 c0 48 85 ff 74 16 8b 57 30 83 e6 03 21 f2 39 f2 [592813.924021] RIP [] nfs_mark_delegation_referenced+0x6/0x6 [nfs] [592813.924021] RSP [592813.924021] CR2: ffb8 [592813.924021] ---[ end trace 6e2186ee7d0814e0 ]--- cut-cut-cut-cut-cut-cut- This does not seem to happen with a 3.10.11-1~bpo70+1 kernel from wheezy-backports, where we "correctly" get: rm: cannot remove `foo': Input/output error [I unfortunately cannot easily reproduce otherwise and was not able to identify a commit which changed this.] Regards, Salvatore --- End Message --- --- Begin Message --- Source: linux Source-Version: 3.2.68-1 We
Re: Linux null-pointer deref in 3.16.7-ctk2-1 (was: Bug#776192: upgrade-reports wheezy to jessie boot problem)
Control: tag -1 moreinfo upstream Control: forwarded -1 http://thread.gmane.org/gmane.linux.ubuntu.devel.kernel.general/39123/ On Thu, 2015-04-02 at 01:01 -0700, Bill MacAllister wrote: > > --On Sunday, January 25, 2015 11:25:34 AM +0100 Niels Thykier > wrote: > > > I have CC'ed the Debian linux maintainers as I noticed your kernel > > reports a null pointer deference in the kernel (see below for the > > trace). I have taken the liberty of reassigning it to the linux package > > as well. > > @linux maintainers: if you suspect that the null pointer issue is > > unrelated to Bills boot problem, please clone the bug and throw the bug > > back to upgrade-reports for further analysis. > > > > Bug link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776192 > > > > Thanks, > > ~Niels > > Any news on this problem? I am still seeing this problem even though > we have moved on to 3.16.7-ckt7-1. > > I had the thought to look at the kernel modules that support the > PERC controller on these Dell systems. Explicitly specifying the > mpt* modules and updating initramfs does not fix the problem. > > We have plenty of these 1950s. I really need to come up with a > work around or a solution to this problem. Any ideas about what > I should try next? It looks the same as this problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705 http://thread.gmane.org/gmane.linux.ubuntu.devel.kernel.general/39123/ Can you confirm that the LSI controller (mptsas driver) takes more than 30 seconds to scan for devices at boot time when running the wheezy (Linux 3.2) kernel? If so then we need a change to the udev rules to increase the timeout for this driver module. We also need to fix the driver so that it fails cleanly if it still hits the timeout. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processed: cloning 780818, reassign -1 to src:linux, retitle -1 to Access to RPMB may fail with long timeout ...
Processing commands for cont...@bugs.debian.org: > clone 780818 -1 Bug #780818 [src:linux] lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs) Bug 780818 cloned as bug 782038 > reassign -1 src:linux 3.16.7-ckt7-1 Bug #782038 [src:linux] lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs) Ignoring request to reassign bug #782038 to the same package Bug #782038 [src:linux] lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs) Marked as found in versions linux/3.16.7-ckt7-1. > retitle -1 Access to RPMB may fail with long timeout Bug #782038 [src:linux] lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs) Changed Bug title to 'Access to RPMB may fail with long timeout' from 'lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs)' > severity -1 important Bug #782038 [src:linux] Access to RPMB may fail with long timeout Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 780818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780818 782038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782038 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: https://lists.debian.org/handler.s.c.142834867510752.transcr...@bugs.debian.org
Bug#780818: lvm2 should never try to access /dev/mmcblk0rpmb (avoid hangs)
On Sat, 2015-04-04 at 17:26 -0400, Daniel Kahn Gillmor wrote: > Control: affects 780818 lvm2 partman-base > > On Sat 2015-03-21 07:26:46 -0400, Bastian Blank wrote: > > I don't think it is a bug in lvm to try reading a device. > > > >> lvm is a prime culprit of trying to scan this device, which is just not > >> going to be helpful to users, since it won't contain a PV. > > > > How does it know that as a fact? > > > > Re-assigning to linux, as it allowes read request on devices not > > supporting it. > > I understand that the issue might be caused by the kernel itself. I'm > noting here that this bug affects both lvm2 (because it causes vgscan to > hang for quite a while, at least) as well as causing the partition > manager during d-i to take ages on any system that has this kind of > device. Ideally the driver would avoid doing whatever it is that results in a hang, or would expose the RPMB only if it's really accessible. I suspect that where access to the RPMB hangs this is because the system firmware (BIOS/EFI) has intentionally disabled access before handing over to the OS. Hiding RPMBs seems to be a popular workaround, and I doubt that it will be useful to access them under a Debian system or other free operating system, so that's what I intend to do. If we need to change that later we can add a module parameter to override this. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processed: severity of 781953 is important
Processing commands for cont...@bugs.debian.org: > # regression from wheezy > severity 781953 important Bug #781953 [src:linux] linux-image-3.16.0-4-amd64: Verbose messages at boot time Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 781953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781953 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: https://lists.debian.org/handler.s.c.142834694332334.transcr...@bugs.debian.org
Processed: fixed 731439 in linux-2.6/3.4.1-1~experimental.1
Processing commands for cont...@bugs.debian.org: > fixed 731439 linux-2.6/3.4.1-1~experimental.1 Bug #731439 [src:linux] "BUG: unable to handle kernel paging request at ffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage Marked as fixed in versions linux-2.6/3.4.1-1~experimental.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 731439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731439 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: https://lists.debian.org/handler.s.c.142834655229237.transcr...@bugs.debian.org
Processed: tagging 778742
Processing commands for cont...@bugs.debian.org: > tags 778742 - fixed Bug #778742 [src:linux] linux-image-3.16.0-4-586: Oops with 586 and pae kernel Removed tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 778742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778742 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: https://lists.debian.org/handler.s.c.142834633928466.transcr...@bugs.debian.org
Bug#770479: linux-image-3.16.0-4-amd64: nbd timeout option is not working
Control: tag -1 upstream Control: severity -1 important On Fri, 21 Nov 2014 16:50:03 +0100 Hermann Lauer wrote: > Package: src:linux > Version: 3.16.7-2 > Severity: normal > Tags: patch > > Dear Maintainer, > > the nbd timeout settings from nbd-client to the kernel is broken inside the > jessie kernel. > This renders raid1 on top of nbd devices useless, as that device will simply > hang > when the network connection or the nbd-server fails until the connection to > the nbd-server is brought back to live - clearly not what is intended with > using a raid1. > > This worked in lenny and was broken since wheezy. > > Appended is the patch obtained from the nbd subsystem maintainers list, which > allows > me to rebuild the jessie kernel package and made it work again. > > If you need futher information or references please let me know. Unfortunately this change has still not been committed by the nbd maintainers (at least, not anywhere that I can see) and we will not apply it until that happens. Perhaps you can remind them that this problem is still unfixed? I'm increasing severity since this is a regression. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processed: Re: linux-image-3.16.0-4-amd64: nbd timeout option is not working
Processing control commands: > tag -1 upstream Bug #770479 [src:linux] linux-image-3.16.0-4-amd64: nbd timeout option is not working Added tag(s) upstream. > severity -1 important Bug #770479 [src:linux] linux-image-3.16.0-4-amd64: nbd timeout option is not working Severity set to 'important' from 'normal' -- 770479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770479 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: https://lists.debian.org/handler.s.b770479.142834576025172.transcr...@bugs.debian.org
Processed: Re: linux-image-3.14-1-amd64: Headset Plantronics GameCom 780 doesn't work
Processing control commands: > tag -1 upstream Bug #746638 [src:linux] linux-image-3.14-1-amd64: Headset Plantronics GameCom 780 doesn't work Added tag(s) upstream. > tag -1 - patch Bug #746638 [src:linux] linux-image-3.14-1-amd64: Headset Plantronics GameCom 780 doesn't work Removed tag(s) patch. -- 746638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746638 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: https://lists.debian.org/handler.s.b746638.142834552223638.transcr...@bugs.debian.org
Bug#746638: linux-image-3.14-1-amd64: Headset Plantronics GameCom 780 doesn't work
Control: tag -1 upstream Control: tag -1 - patch On Tue, 11 Nov 2014 12:08:45 +0100 =?UTF-8?B?TWF0ZXVzeiDFgXVrYXNpaw==?= wrote: > Hi again, > > This bug easy to fix, I don't know why did not I think of that before. > > I made patch, it's working fine on src:linux from sid and experimental. > Can you add it to jessie? Removing this control was a deliberate change: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19570d747795f0ecff79403698b868dc5ad7fa86 Please discuss this upstream rather than asking us to undo it. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processed: reassign 778787 to src:linux, forcibly merging 781934 778787
Processing commands for cont...@bugs.debian.org: > reassign 778787 src:linux Bug #778787 [linux-image-3.16.0-4-powerpc64] linux-image-3.19.0: fails to handle fans with windfarm-pm72 on powermac7, 3 (Powermac G5) Bug reassigned from package 'linux-image-3.16.0-4-powerpc64' to 'src:linux'. Ignoring request to alter found versions of bug #778787 to the same values previously set Ignoring request to alter fixed versions of bug #778787 to the same values previously set > forcemerge 781934 778787 Bug #781934 [src:linux] linux: XServe G5 all fans run full speed Bug #778787 [src:linux] linux-image-3.19.0: fails to handle fans with windfarm-pm72 on powermac7, 3 (Powermac G5) 781935 was blocked by: 781934 781935 was blocking: 781936 Added blocking bug(s) of 781935: 778787 781936 was blocked by: 781935 781934 781936 was not blocking any bugs. Added blocking bug(s) of 781936: 778787 Marked as found in versions linux/3.16.7-ckt7-1. Added tag(s) d-i and jessie. Merged 778787 781934 > thanks Stopping processing here. Please contact me if you need assistance. -- 778787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778787 781934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781934 781935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781935 781936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781936 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: https://lists.debian.org/handler.s.c.142834335010641.transcr...@bugs.debian.org
Bug#781999: Please install device-tree blobs in /boot
Package: linux Severity: wishlist Hey, The ARM linux image packages install DTB files in /usr/lib//, as a DTB is required to boot most modern arm systems typically the right file has to be copied to a bootloader accessible filesystem before usage (e.g. /boot). On current Debian systems this tends to be done by flash-kernel. This ofcourse works fine for device-specific images, however for generic ARM images that's pretty nasty. I've recently started using the newish u-boot generic distro support on my boards[0], which among other things allows one to simply specify a directory containing the DTB files and u-boot will pick the right one based on the board it's booting on.. Allowing generic images to be booted on boards where u-boot is in e.g. flash. Ofcourse, this means all potentially used dtb files should be on a boot-loader accessible partition, not just one specific board. As such the request to install dtb files in /boot, which also follows the convention in the upstream build system. For reference when using linux-image-3.19.0-trunk-armmp this would add ~8 mbyte of dtb files to /boot, current linux-next's multi_v7 configuration generates around ~11 mbyte of dtb files. 0: http://git.denx.de/?p=u-boot.git;a=blob_plain;f=doc/README.distro;hb=HEAD -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, armel Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150406100845.10859.68883.reportbug@dusk
