Bug#808043: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error

[Gianluca GP Renzi]

Nope. It does not work. Compiling 4.3.3 using  the latest binutils leads to the 
same problem. Why?

Christian Marillat  ha scritto:

>On 15 déc. 2015 19:12, Ben Hutchings  wrote:
>
>[...]
>
>> OK, so everything is failing because the 'mcount' symbol (used for
>> function tracing) is not found.  It is supposed to be exported from
>> vmlinux.  Comparing the two versions, there's no difference (aside from
>> addresses) in the symbols related to mcount, so I think there's a
>> deeper problem in the module loader.
>
>Thanks for the precise analysis of the bug report.
>
>Christian
>

Processing of linux_4.3.3-5_source.changes

[Debian FTP Masters]

linux_4.3.3-5_source.changes uploaded successfully to localhost
along with the files:
  linux_4.3.3-5.dsc
  linux_4.3.3-5.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Processed: notfound 809722 in 4.3.0-1, forcibly merging 809082 809722

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 809722 4.3.0-1
Bug #809722 [src:linux] linux-headers-4.3.0-1-all: Causes read/write errors on 
ata1.00 -- known issue patched in kernel
The source 'linux' and version '4.3.0-1' do not appear to match any binary 
packages
No longer marked as found in versions linux/4.3.0-1.
> forcemerge 809082 809722
Bug #809082 {Done: Ben Hutchings } [src:linux] Linux 
kernel 4.3.3 PAE causes disk errors
Bug #808563 {Done: Ben Hutchings } [src:linux] Boot with 
4.3: SATA errors. Returning to 4.2: no errors
Bug #809350 {Done: Ben Hutchings } [src:linux] 
linux-image-4.3.0-1-686-pae: SSDs report disk errors
Bug #809722 [src:linux] linux-headers-4.3.0-1-all: Causes read/write errors on 
ata1.00 -- known issue patched in kernel
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=109661'.
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions linux/4.3.3-3.
Marked as found in versions linux/4.3.3-2.
Added tag(s) upstream, fixed-upstream, and patch.
Bug #808563 {Done: Ben Hutchings } [src:linux] Boot with 
4.3: SATA errors. Returning to 4.2: no errors
Bug #809350 {Done: Ben Hutchings } [src:linux] 
linux-image-4.3.0-1-686-pae: SSDs report disk errors
Merged 808563 809082 809350 809722
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
808563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808563
809082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809082
809350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809350
809722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#809206: so can I delete them by hand?

[Ben Hutchings]

On Mon, 2016-01-04 at 10:14 +0800, 積丹尼 Dan Jacobson wrote:
> So can I delete them anyway?

You should not delete them.

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


signature.asc
Description: This is a digitally signed message part

Bug#808043: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error

[Gianluca Renzi]

As for today, the binutils and the kernel (4.3.0-1ppc) upgrade did not fix
the issue.
Right now I am compiling by myself the 4.3-source package and try to see if
it shows some differences...


On Wed, Dec 16, 2015 at 10:38 AM, Christian Marillat 
wrote:

> On 15 déc. 2015 19:12, Ben Hutchings  wrote:
>
> [...]
>
> > OK, so everything is failing because the 'mcount' symbol (used for
> > function tracing) is not found.  It is supposed to be exported from
> > vmlinux.  Comparing the two versions, there's no difference (aside from
> > addresses) in the symbols related to mcount, so I think there's a
> > deeper problem in the module loader.
>
> Thanks for the precise analysis of the bug report.
>
> Christian
>
>


-- 
Ciao e buona giornata.

"GP! In mezzo al campo stai proprio schifoso!"
Coach M.Russo

Processed: Re: Bug#809740: initramfs-tools: Completely ignores rootdelay

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 udev 220-4
Bug #809740 [initramfs-tools] initramfs-tools: Completely ignores rootdelay
Bug reassigned from package 'initramfs-tools' to 'udev'.
No longer marked as found in versions initramfs-tools/0.120.
Ignoring request to alter fixed versions of bug #809740 to the same values 
previously set
Bug #809740 [udev] initramfs-tools: Completely ignores rootdelay
Marked as found in versions systemd/220-4.

-- 
809740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#809740: initramfs-tools: Completely ignores rootdelay

[Ben Hutchings]

Control: reassign -1 udev 220-4

On Sun, 2016-01-03 at 16:21 +0100, Christoph Egger wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: important
> 
> Hi!
> 
> the initramfs totally ignores the rootdelay / rootwait parameters and
> just instantly boots up.
[...]

It has never implemented 'rootwait' as it will always wait for devices
to appear.

The 'rootdelay=' parameter used to be implemented in udev's script, but
this was wrongly removed recently for spurious reasons.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#809206: so can I delete them by hand?

[積丹尼 Dan Jacobson]

So can I delete them anyway?

linux_4.3.3-5_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jan 2016 00:45:27 +
Source: linux
Binary: linux-source-4.3 linux-support-4.3.0-1 linux-doc-4.3 linux-manual-4.3 
linux-libc-dev linux-headers-4.3.0-1-all linux-headers-4.3.0-1-all-alpha 
kernel-image-4.3.0-1-alpha-generic-di nic-modules-4.3.0-1-alpha-generic-di 
nic-wireless-modules-4.3.0-1-alpha-generic-di 
nic-shared-modules-4.3.0-1-alpha-generic-di 
serial-modules-4.3.0-1-alpha-generic-di 
usb-serial-modules-4.3.0-1-alpha-generic-di 
ppp-modules-4.3.0-1-alpha-generic-di pata-modules-4.3.0-1-alpha-generic-di 
cdrom-core-modules-4.3.0-1-alpha-generic-di 
scsi-core-modules-4.3.0-1-alpha-generic-di 
scsi-modules-4.3.0-1-alpha-generic-di 
scsi-common-modules-4.3.0-1-alpha-generic-di 
scsi-extra-modules-4.3.0-1-alpha-generic-di 
loop-modules-4.3.0-1-alpha-generic-di btrfs-modules-4.3.0-1-alpha-generic-di 
ext4-modules-4.3.0-1-alpha-generic-di isofs-modules-4.3.0-1-alpha-generic-di 
jfs-modules-4.3.0-1-alpha-generic-di xfs-modules-4.3.0-1-alpha-generic-di 
fat-modules-4.3.0-1-alpha-generic-di
 md-modules-4.3.0-1-alpha-generic-di multipath-modules-4.3.0-1-alpha-generic-di 
usb-modules-4.3.0-1-alpha-generic-di 
usb-storage-modules-4.3.0-1-alpha-generic-di 
fb-modules-4.3.0-1-alpha-generic-di input-modules-4.3.0-1-alpha-generic-di 
event-modules-4.3.0-1-alpha-generic-di mouse-modules-4.3.0-1-alpha-generic-di 
nic-pcmcia-modules-4.3.0-1-alpha-generic-di 
pcmcia-modules-4.3.0-1-alpha-generic-di 
nic-usb-modules-4.3.0-1-alpha-generic-di sata-modules-4.3.0-1-alpha-generic-di 
core-modules-4.3.0-1-alpha-generic-di crc-modules-4.3.0-1-alpha-generic-di 
crypto-modules-4.3.0-1-alpha-generic-di 
crypto-dm-modules-4.3.0-1-alpha-generic-di ata-modules-4.3.0-1-alpha-generic-di 
nbd-modules-4.3.0-1-alpha-generic-di squashfs-modules-4.3.0-1-alpha-generic-di 
virtio-modules-4.3.0-1-alpha-generic-di zlib-modules-4.3.0-1-alpha-generic-di 
fuse-modules-4.3.0-1-alpha-generic-di srm-modules-4.3.0-1-alpha-generic-di 
linux-headers-4.3.0-1-common linux-image-4.3.0-1-alpha-generic
 linux-headers-4.3.0-1-alpha-generic linux-image-4.3.0-1-alpha-smp 
linux-headers-4.3.0-1-alpha-smp linux-headers-4.3.0-1-all-amd64 
kernel-image-4.3.0-1-amd64-di nic-modules-4.3.0-1-amd64-di 
nic-wireless-modules-4.3.0-1-amd64-di nic-shared-modules-4.3.0-1-amd64-di 
serial-modules-4.3.0-1-amd64-di usb-serial-modules-4.3.0-1-amd64-di 
ppp-modules-4.3.0-1-amd64-di pata-modules-4.3.0-1-amd64-di 
cdrom-core-modules-4.3.0-1-amd64-di firewire-core-modules-4.3.0-1-amd64-di 
scsi-core-modules-4.3.0-1-amd64-di scsi-modules-4.3.0-1-amd64-di 
scsi-common-modules-4.3.0-1-amd64-di scsi-extra-modules-4.3.0-1-amd64-di 
loop-modules-4.3.0-1-amd64-di btrfs-modules-4.3.0-1-amd64-di 
ext4-modules-4.3.0-1-amd64-di isofs-modules-4.3.0-1-amd64-di 
jfs-modules-4.3.0-1-amd64-di ntfs-modules-4.3.0-1-amd64-di 
xfs-modules-4.3.0-1-amd64-di fat-modules-4.3.0-1-amd64-di 
md-modules-4.3.0-1-amd64-di multipath-modules-4.3.0-1-amd64-di 
usb-modules-4.3.0-1-amd64-di usb-storage-modules-4.3.0-1-amd64-di
 pcmcia-storage-modules-4.3.0-1-amd64-di fb-modules-4.3.0-1-amd64-di 
input-modules-4.3.0-1-amd64-di event-modules-4.3.0-1-amd64-di 
mouse-modules-4.3.0-1-amd64-di nic-pcmcia-modules-4.3.0-1-amd64-di 
pcmcia-modules-4.3.0-1-amd64-di nic-usb-modules-4.3.0-1-amd64-di 
sata-modules-4.3.0-1-amd64-di core-modules-4.3.0-1-amd64-di 
acpi-modules-4.3.0-1-amd64-di i2c-modules-4.3.0-1-amd64-di 
crc-modules-4.3.0-1-amd64-di crypto-modules-4.3.0-1-amd64-di 
crypto-dm-modules-4.3.0-1-amd64-di efi-modules-4.3.0-1-amd64-di 
ata-modules-4.3.0-1-amd64-di mmc-core-modules-4.3.0-1-amd64-di 
mmc-modules-4.3.0-1-amd64-di nbd-modules-4.3.0-1-amd64-di 
squashfs-modules-4.3.0-1-amd64-di speakup-modules-4.3.0-1-amd64-di 
virtio-modules-4.3.0-1-amd64-di uinput-modules-4.3.0-1-amd64-di 
sound-modules-4.3.0-1-amd64-di hyperv-modules-4.3.0-1-amd64-di 
udf-modules-4.3.0-1-amd64-di fuse-modules-4.3.0-1-amd64-di 
linux-image-4.3.0-1-amd64 linux-headers-4.3.0-1-amd64 
linux-image-4.3.0-1-amd64-dbg
 xen-linux-system-4.3.0-1-amd64 linux-headers-4.3.0-1-all-arm64 
kernel-image-4.3.0-1-arm64-di nic-modules-4.3.0-1-arm64-di 
nic-wireless-modules-4.3.0-1-arm64-di nic-shared-modules-4.3.0-1-arm64-di 
ppp-modules-4.3.0-1-arm64-di cdrom-core-modules-4.3.0-1-arm64-di 
scsi-core-modules-4.3.0-1-arm64-di scsi-modules-4.3.0-1-arm64-di 
loop-modules-4.3.0-1-arm64-di btrfs-modules-4.3.0-1-arm64-di 
ext4-modules-4.3.0-1-arm64-di isofs-modules-4.3.0-1-arm64-di 
jfs-modules-4.3.0-1-arm64-di xfs-modules-4.3.0-1-arm64-di 
fat-modules-4.3.0-1-arm64-di md-modules-4.3.0-1-arm64-di 
multipath-modules-4.3.0-1-arm64-di usb-modules-4.3.0-1-arm64-di 
usb-storage-modules-4.3.0-1-arm64-di input-modules-4.3.0-1-arm64-di 
event-modules-4.3.0-1-arm64-di nic-usb-modules-4.3.0-1-arm64-di 
sata-modules-4.3.0-1-arm64-di core-modules-4.3.0-1-arm64-di 
crc-modules-4.3.0-1-arm64-di crypto-modules-4.3.0-1-arm64-di 
crypto-dm-modules-4.3.0-1-arm64-di 

Bug#809740: initramfs-tools: Completely ignores rootdelay

[Christoph Egger]

Package: initramfs-tools
Version: 0.120
Severity: important

Hi!

the initramfs totally ignores the rootdelay / rootwait parameters and
just instantly boots up. As a result I always get a degraded array
activated as the second disk is not yet available. The second disk
just shows up a few blinks later.

  Christoph

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 5.5M Sep 23  2013 /boot/initrd.img-3.10-2-amd64
-rw-r--r-- 1 root root 5.6M Nov 15  2013 /boot/initrd.img-3.10-3-amd64
-rw-r--r-- 1 root root 6.7M Dec 19 21:02 /boot/initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 6.8M Sep 25 13:58 /boot/initrd.img-4.1.0-2-amd64
-rw-r--r-- 1 root root 6.8M Dec 19 21:06 /boot/initrd.img-4.2.0-1-amd64
-rw-r--r-- 1 root root 6.8M Jan  3 01:50 /boot/initrd.img-4.3.0-1-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 root=/dev/mapper/ssd-root ro quiet 
rootdelay=30 rootwait=30 systemd.log_target=kmsg systemd.debug-shell

-- resume
RESUME=UUID=160f4b55-b95a-416c-aec0-a20b510e40ee
-- /proc/filesystems
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
fuse   94208  3
ebtable_filter 16384  0
ebtables   36864  1 ebtable_filter
ip6table_filter16384  0
ip6_tables 28672  1 ip6table_filter
iptable_filter 16384  0
ip_tables  28672  1 iptable_filter
x_tables   36864  5 
ip6table_filter,ip_tables,iptable_filter,ebtables,ip6_tables
nfnetlink_queue20480  0
nfnetlink_log  20480  0
nfnetlink  16384  2 nfnetlink_log,nfnetlink_queue
bluetooth 512000  0
rfkill 24576  2 bluetooth
tun28672  2
sit24576  0
tunnel416384  1 sit
ip_tunnel  28672  1 sit
nfsd  286720  11
auth_rpcgss61440  1 nfsd
oid_registry   16384  1 auth_rpcgss
nfs_acl16384  1 nfsd
lockd  90112  1 nfsd
grace  16384  2 nfsd,lockd
sunrpc327680  17 nfsd,auth_rpcgss,lockd,nfs_acl
pci_stub   16384  1
vboxpci24576  0
vboxnetadp 28672  0
vboxnetflt 28672  0
vboxdrv   450560  3 vboxnetadp,vboxnetflt,vboxpci
binfmt_misc20480  1
bridge114688  0
stp16384  1 bridge
llc16384  2 stp,bridge
joydev 20480  0
snd_usb_audio 176128  0
snd_usbmidi_lib32768  1 snd_usb_audio
snd_hwdep  16384  1 snd_usb_audio
hid_generic16384  0
usbhid 49152  0
hid   118784  2 hid_generic,usbhid
sr_mod 24576  0
cdrom  57344  1 sr_mod
evdev  20480  13
amdkfd122880  1
kvm_amd65536  0
ohci_pci   16384  0
kvm   507904  1 kvm_amd
radeon   1490944  2
snd_ca0106 45056  0
psmouse   126976  0
snd_rawmidi32768  2 snd_usbmidi_lib,snd_ca0106
snd_seq_device 16384  1 snd_rawmidi
ehci_pci   16384  0
snd_ac97_codec126976  1 snd_ca0106
serio_raw  16384  0
xhci_pci   16384  0
ttm94208  1 radeon
r8169  81920  0
pcspkr 16384  0
snd_pcm_oss49152  0
xhci_hcd  172032  1 xhci_pci
drm_kms_helper131072  1 radeon
ohci_hcd   49152  1 ohci_pci
mii16384  1 r8169
snd_mixer_oss  24576  1 snd_pcm_oss
ehci_hcd   77824  1 ehci_pci
drm   348160  5 ttm,drm_kms_helper,radeon
snd_pcm   102400  4 
snd_pcm_oss,snd_usb_audio,snd_ac97_codec,snd_ca0106
pata_via   16384  0
firewire_ohci  40960  0
i2c_algo_bit   16384  1 radeon
snd_timer  32768  1 snd_pcm
snd81920  11 
snd_pcm_oss,snd_usb_audio,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_usbmidi_lib,snd_seq_device,snd_mixer_oss,snd_ca0106
edac_mce_amd   24576  0
usbcore   233472  9 
snd_usb_audio,ohci_hcd,ohci_pci,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,xhci_hcd,xhci_pci
sp5100_tco 16384  0
soundcore  16384  1 snd
ahci   36864  1
ac97_bus   16384  1 snd_ac97_codec
k10temp16384  0
edac_core  57344  0
sg 32768  0
i2c_piix4  24576  0
shpchp 36864  0
libahci32768  1 ahci
usb_common 16384  1 usbcore
wmi20480  0
8250_fintek16384  0
asus_atk0110   20480  0
acpi_cpufreq   20480  1
button 16384  0
processor  36864  1 acpi_cpufreq
hwmon_vid  16384  0
loop   28672  0
firewire_sbp2  24576  0

Bug#797949: CONFIG_PINCTRL_CHERRYVIEW is also needed for NUC5PPYH

[Baptiste Jonglez]

Hi,

With the 4.3.3 kernel (recently landed in stretch and jessie-backports),
enabling CONFIG_PINCTRL_CHERRYVIEW is still needed to get the SD reader to
work on a NUC 5PPYH.

Thanks,
Baptiste

On Sat, Dec 19, 2015 at 02:27:27PM +0100, Baptiste Jonglez wrote:
> Hi,
> 
> On a NUC5PPYH, enabling CONFIG_PINCTRL_BAYTRAIL is not enough.
> CONFIG_PINCTRL_CHERRYVIEW is also needed for the SD reader to work.
> 
> Using 4.2.6-3~bpo8+2 from jessie-backports, the SD reader does not work,
> with the (already reported) error about GPIO:
> 
> dmesg | grep -i sdhci
> [1.193414] sdhci: Secure Digital Host Controller Interface driver
> [1.193419] sdhci: Copyright(c) Pierre Ossman
> [1.210009] sdhci-pci :00:12.0: SDHCI controller found [8086:2296] 
> (rev 21)
> [1.210373] sdhci-pci :00:12.0: failed to setup card detect gpio
> [1.211394] sdhci-pci :00:12.0: No vmmc regulator found
> [1.211397] sdhci-pci :00:12.0: No vqmmc regulator found
> 
> Kernel version: Linux Togepi 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 
> (2015-12-14) x86_64 GNU/Linux
> 
> 
> When enabling CONFIG_PINCTRL_CHERRYVIEW, the SD reader works, and there is
> no more GPIO error message:
> 
> dmesg | grep -i sdhci
> [1.191143] sdhci: Secure Digital Host Controller Interface driver
> [1.191148] sdhci: Copyright(c) Pierre Ossman
> [1.227530] sdhci-pci :00:12.0: SDHCI controller found [8086:2296] 
> (rev 21)
> [1.228949] sdhci-pci :00:12.0: No vmmc regulator found
> [1.228953] sdhci-pci :00:12.0: No vqmmc regulator found
> [1.234878] mmc0: SDHCI controller on PCI [:00:12.0] using ADMA
> 
> The kernel is built from 4.2.6-3~bpo8+2 with the PINCTRL_CHERRYVIEW option 
> enabled: Linux Togepi 4.2.6-cherryview #1 SMP Sat Dec 19 13:52:07 CET 2015 
> x86_64 GNU/Linux
> 
> Thanks,
> Baptiste




pgp12daOuOOUO.pgp
Description: PGP signature

Bug#809722: linux-headers-4.3.0-1-all: Causes read/write errors on ata1.00 -- known issue patched in kernel

[Barkın Çelebican]

Package: linux-headers-4.3.0-1-all
Severity: important

Dear Maintainer,

I have removed the problem kernel package and reverted to the older 4.2.0 
package as there were no errors prior to the upgrade. While searching for a 
solution before I came across this bug report: 
https://bugzilla.kernel.org/show_bug.cgi?id=109661

   * What led up to the situation?
upgrade to linux-image-4.3.0-1-686-pae and booting into new kernel
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
booting into new kernel
   * What was the outcome of this action?
errors writing to disk in dmesg and stdout/console
   * What outcome did you expect instead?
no errors


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.2.0-1-686-pae (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
Init: systemd (via /run/systemd/system)

Bug#809722: linux-headers-4.3.0-1-all: Causes read/write errors on ata1.00 -- known issue patched in kernel

[Barkın Çelebican]

I don't know how I managed to mess up such an easy process, but the bug
report is about linux-image-4.3.0-1-686-pae and not the headers. Is there
anyway I can rectify this?

On Sun, Jan 3, 2016 at 2:29 PM, Barkın Çelebican 
wrote:

> Package: linux-headers-4.3.0-1-all
> Severity: important
>
> Dear Maintainer,
>
> I have removed the problem kernel package and reverted to the older 4.2.0
> package as there were no errors prior to the upgrade. While searching for a
> solution before I came across this bug report:
> https://bugzilla.kernel.org/show_bug.cgi?id=109661
>
>* What led up to the situation?
> upgrade to linux-image-4.3.0-1-686-pae and booting into new kernel
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> booting into new kernel
>* What was the outcome of this action?
> errors writing to disk in dmesg and stdout/console
>* What outcome did you expect instead?
> no errors
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 4.2.0-1-686-pae (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
> Init: systemd (via /run/systemd/system)
>

Processed: Re: Bug#809722: linux-headers-4.3.0-1-all: Causes read/write errors on ata1.00 -- known issue patched in kernel

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 4.3.0-1
Bug #809722 [linux-headers-4.3.0-1-all] linux-headers-4.3.0-1-all: Causes 
read/write errors on ata1.00 -- known issue patched in kernel
Bug reassigned from package 'linux-headers-4.3.0-1-all' to 'src:linux'.
Ignoring request to alter found versions of bug #809722 to the same values 
previously set
Ignoring request to alter fixed versions of bug #809722 to the same values 
previously set
Bug #809722 [src:linux] linux-headers-4.3.0-1-all: Causes read/write errors on 
ata1.00 -- known issue patched in kernel
The source 'linux' and version '4.3.0-1' do not appear to match any binary 
packages
Marked as found in versions linux/4.3.0-1.

-- 
809722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#809722: linux-headers-4.3.0-1-all: Causes read/write errors on ata1.00 -- known issue patched in kernel

[Roger Shimizu]

Control: reassign -1 src:linux 4.3.0-1
thanks

On Sun, Jan 3, 2016 at 9:41 PM, Barkın Çelebican  wrote:
> I don't know how I managed to mess up such an easy process, but the bug
> report is about linux-image-4.3.0-1-686-pae and not the headers. Is there
> anyway I can rectify this?

Bug report can be changed by "Control" command [0]
I already did that you.

BTW. The bug you report seems the same as Bug#808563 which is already
fixed in 4.3.3-3. [1]

[0]: https://www.debian.org/Bugs/server-control
[1]: https://bugs.debian.org/808563

Cheers,
Roger

docbook-xsl: manpages: Misuse of "no-break space" causes overlong lines

[Bjarni Ingi Gislason]

This is a multi-part MIME message sent by reportbug.


--===0054729797023488166==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: docbook-xsl
Version: 1.78.1+dfsg-1
Severity: normal
Tags: patch

  This is related to Debian bug #569828, which is number 1120 upstream.

Dear Maintainer,

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

  For example "man usb_copy_descriptors".  Manual is from the
"linux-manual" package.

  Environment was:

MANWIDTH=80
MANOPT=--no-hyphenation --warnings=w 
MAN_KEEP_STDERR=yes

   * What was the outcome of this action?

  For example

:34: warning [p 1, 1.5i]: can't break line

###

  There are many error detected by "lintian" in the package
"linux-manual" caused by the use of a "no-break space".  I don't know
the markup language used, but I experimented and did the following
changes in the directory
/usr/share/xml/docbook/stylesheet/docbook-xsl/manpages:

  What is missing in the patch is the idea in Debian bug #569828.


  Patch: (also in the attachment, if it should get mangled here)

--- param.xsl.jessie2012-01-09 14:09:15.0 +
+++ param.xsl   2016-01-02 21:43:50.0 +
@@ -90,10 +90,15 @@ or
 
 
 
-   
+  
   
-  
-  
+  
+  
+  
+
 
   
 
@@ -101,9 +106,9 @@ or
   
   
   
-  
-  
   
+  
+  
   
   
   



--- synop.xsl.jessie2012-01-09 14:08:12.0 +
+++ synop.xsl   2016-01-02 18:08:55.0 +
@@ -163,19 +163,24 @@
 .hy 0
   
   
-  .HP 
+  
+  
+  .nr hP 
   \w'
   
 
   
+  
   \ 'u
   
-  
+  
+  .HP \n(hPu
   
   
   
@@ -271,7 +276,8 @@
 
   
   
-  .HP 
+  
+  .nr hP 
   \w'
   
 
@@ -283,6 +289,8 @@
   
   ('u
   
+  .HP \n(hPu
+  
   .
   



  I have not yet seen the reason for this excessive use of the "no-break
space", but it is not acceptable.

  These patches should be applied as soon as possible by the
maintainers of the package "linux-manual" to their version of the
package "docbook-xsl", as there can be a longer wait for an official
update of it.

  After applying the patches I get 14 errors caused by long lines
(MANWIDTH=80).  "Lintian" reports about 300
"manpage-has-errors-from-man".


-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt20-u1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages docbook-xsl depends on:
ii  xml-core  0.13+nmu2

Versions of packages docbook-xsl recommends:
pn  docbook-xml  

Versions of packages docbook-xsl suggests:
pn  dbtoepub 
pn  docbook-xsl-doc-html | docbook-xsl-doc-pdf | docbook-xsl-doc-text |  
pn  docbook-xsl-saxon
pn  fop  
pn  libsaxon-java
pn  libxalan2-java   
pn  libxslthl-java   
pn  xalan

-- no debconf information

--===0054729797023488166==
Content-Type: text/x-diff; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="docbook-xsl.patch"

--- param.xsl.jessie2012-01-09 14:09:15.0 +
+++ param.xsl   2016-01-02 21:43:50.0 +
@@ -90,10 +90,15 @@ or
 
 
 
-   
+  
   
-  
-  
+  
+  
+  
+
 
   
 
@@ -101,9 +106,9 @@ or
   
   
   
-  
-  
   
+  
+  
   
   
   



--- synop.xsl.jessie2012-01-09 14:08:12.0 +
+++ synop.xsl   2016-01-02 18:08:55.0 +
@@ -163,19 +163,24 @@
 .hy 0
   
   
-  .HP 
+  
+  
+  .nr hP 
   \w'
   
 
   
+  
   \ 'u
   
-  
+  
+  .HP \n(hPu
   
   
   
@@ -271,7 +276,8 @@
 
   
   
-  .HP 
+  
+  .nr hP 
   \w'
   
 
@@ -283,6 +289,8 @@
   
   ('u
   
+  .HP \n(hPu
+  
   .
   


--===0054729797023488166==--

-- 
Bjarni I. Gislason

Re: linux-image-4.3.0-1-686-pae unstable after 60 minutes

[Torben Schou Jensen]

> On Sat, 2016-01-02 at 18:55 +0100, Torben Schou Jensen wrote:
>> > Since upgrade to linux-image-4.3.0-1-686-pae I experience unstable
>> system
>> > after 60 minutes.
>> > I am using XFCE desktop and primary Iceweasel.
>> > After about 60 minutes, oom-killer suddenly start to kill system,
>> first
>> > Iceweasel, then Xorg etc., taking down tasks so fast only solution is
>> a
>> > hard reboot.
>> > If I boot up in linux-image-4.2.0-1-686-pae, all is stable again.
linux-image-4.2.0-1-686-pae 4.2.6-3 i386
>> > linux-image-4.3.0-1-686-pae 4.3.3-2 i386
>> > I have tried to setup atop to log memory every 10 seconds, but until
>> now
>> > not possible to identify what is causing oom-killer.
>> > Brgds
>> > Torben Schou Jensen
>> Wifi has something to do with this.
>> With linux-image-4.3.0-1-686-pae I see a few error messages from
wpa_supplicant, always within a minute before oom-killer start.
> [...]
> Which driver is used for wifi on this computer?
> Ben.

Driver rtl8192cu

Wifi is not connected when I see problem.
I use this USB wifi as emergency if other net connection fail.

Here a few lines from logs

---
Dec 29 21:43:58 asrock kernel: [0.00] Linux version
4.3.0-1-686-pae (debian-kernel@lists.debian.org) (gcc version 5.3.1
20151207 (Debian 5.3.1-3) ) #1 SMP Debian 4.3.3-2 (2015-12-17)

Dec 29 21:44:02 asrock NetworkManager[772]:   NetworkManager
(version 1.0.10) is starting...

Dec 29 21:44:05 asrock NetworkManager[772]:   (wlan0): using nl80211
for WiFi device control
Dec 29 21:44:05 asrock NetworkManager[772]:   (wlan0): driver
supports Access Point (AP) mode
Dec 29 21:44:05 asrock NetworkManager[772]:   (wlan0): new 802.11
WiFi device (carrier: UNKNOWN, driver: 'rtl8192cu', ifindex: 3)
Dec 29 21:44:05 asrock NetworkManager[772]:   (wlan0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]

Dec 29 21:44:05 asrock NetworkManager[772]:   wpa_supplicant running
Dec 29 21:44:06 asrock NetworkManager[772]:   (wlan0) supports 4
scan SSIDs
Dec 29 21:44:06 asrock NetworkManager[772]:   (wlan0): supplicant
interface state: starting -> ready
Dec 29 21:44:06 asrock NetworkManager[772]:   startup complete Dec
29 21:44:06 asrock NetworkManager[772]:   (wlan0): device state
change: unavailable -> disconnected (reason 'supplicant-available') [20 30
42]

Dec 29 22:57:04 asrock wpa_supplicant[941]: nl80211:
send_and_recv->nl_recvmsgs failed: -33
Dec 29 22:58:07 asrock wpa_supplicant[941]: nl80211:
send_and_recv->nl_recvmsgs failed: -33
Dec 29 23:01:28 asrock kernel: [ 4676.355953] smbd invoked oom-killer:
gfp_mask=0x2000d0, order=1, oom_score_adj=0

---
Jan  1 15:42:48 asrock kernel: [0.00] Linux version
4.2.0-1-686-pae (debian-kernel@lists.debian.org) (gcc version 4.9.3
(Debian 4.9.3-8) ) #1 SMP Debian 4.2.6-3 (2015-12-06)

Jan  1 15:42:57 asrock NetworkManager[853]:   NetworkManager
(version 1.0.10) is starting...

Jan  1 15:42:58 asrock NetworkManager[853]:   (wlan0): using nl80211
for WiFi device control
Jan  1 15:42:59 asrock NetworkManager[853]:   (wlan0): driver
supports Access Point (AP) mode
Jan  1 15:42:59 asrock NetworkManager[853]:   (wlan0): new 802.11
WiFi device (carrier: UNKNOWN, driver: 'rtl8192cu', ifindex: 3)
Jan  1 15:42:59 asrock NetworkManager[853]:   (wlan0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]

Jan  1 15:43:00 asrock NetworkManager[853]:   wpa_supplicant running
Jan  1 15:43:00 asrock NetworkManager[853]:   (wlan0) supports 4
scan SSIDs
Jan  1 15:43:00 asrock NetworkManager[853]:   (wlan0): supplicant
interface state: starting -> ready
Jan  1 15:43:00 asrock NetworkManager[853]:   startup complete Jan 
1 15:43:00 asrock NetworkManager[853]:   (wlan0): device state
change: unavailable -> disconnected (reason 'supplicant-available') [20 30
42]