Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)

[Ian Campbell]

On Thu, 2016-11-24 at 23:24 -0800, Ryan Tandy wrote:
> whereas the new orion5x-linkstation.dtsi contains this code:
> 
>  {
> status = "okay";
> nr-ports = <1>;
> };

A .dtsi is an include file, not the final thing for any given device,
for that you need a .dts (which is compiled into a .dtb).

Assuming orion5x-linkstation.dtsi is correctly relating to your
platform you would appear to want one of:
$ git grep orion5x-linkstation.dtsi arch/arm/boot/dts/*.dts
arch/arm/boot/dts/orion5x-kuroboxpro.dts:#include "orion5x-linkstation.dtsi"
arch/arm/boot/dts/orion5x-linkstation-lsgl.dts:#include 
"orion5x-linkstation.dtsi"
arch/arm/boot/dts/orion5x-linkstation-lswtgl.dts:#include 
"orion5x-linkstation.dtsi"

(Or something else not yet present in the kernel tree.)

Of the three above orion5x-kuroboxpro.dts and orion5x-linkstation-
lswtgl both set ports to 2 using:

 {
nr-ports = <2>;
};

which overrides the defaults from the dtsi. You mentioned kurobox_pro-
setup.c so perhaps orion5x-kuroboxpro.dts is the one you want?

Ian.

Processed: found 845611 in 4.6.2-2

[Debian Bug Tracking System]

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

> found 845611 4.6.2-2
Bug #845611 [linux-image-4.8.0-1-marvell] linux-image-4.8.0-1-marvell: hard 
drive not detected on LinkStation Pro (LS-GL)
There is no source info for the package 'linux-image-4.8.0-1-marvell' at 
version '4.6.2-2' with architecture ''
Unable to make a source version for version '4.6.2-2'
Marked as found in versions 4.6.2-2.
> thanks
Stopping processing here.

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

Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)

[Ryan Tandy]

Package: linux-image-4.8.0-1-marvell
Version: 4.8.7-1
Severity: normal
Tags: upstream

I found that on recent d-i images, the kernel does not detect the hard 
drive on my LinkStation. I tried some older images and found that kernel 
4.3.3-5 worked and kernel 4.6.2-2 did not.

I suspect the problem is with the device tree file, therefore CCing 
Roger Shimizu who contributed that file.

The old kurobox_pro-setup.c contains this code:

static struct mv_sata_platform_data kurobox_pro_sata_data = {
.n_ports= 2,
};

whereas the new orion5x-linkstation.dtsi contains this code:

 {
status = "okay";
nr-ports = <1>;
};

The dmesg output seems to reinforce this conclusion.

dmesg from 4.3.0-1:

[  611.914912] sata_mv sata_mv.0: version 1.28
[  611.915107] sata_mv sata_mv.0: cannot get optional clkdev
[  611.916086] sata_mv sata_mv.0: slots 32 ports 2
[  611.971107] scsi host0: sata_mv
[  611.984111] scsi host1: sata_mv
[  611.984881] ata1: SATA max UDMA/133 irq 30
[  611.984916] ata2: SATA max UDMA/133 irq 30
[  612.302763] ata1: SATA link down (SStatus 0 SControl 300)
[  612.778697] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  612.787074] ata2.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7
[  612.787118] ata2.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[  612.819082] ata2.00: configured for UDMA/133
[  612.820339] scsi 1:0:0:0: Direct-Access ATA  SAMSUNG SP2504C  0-41 
PQ: 0 ANSI: 5
[  612.899766] sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 
GiB)
[  612.900971] sd 1:0:0:0: [sda] Write Protect is off
[  612.901031] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[  612.901533] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[  612.924886] sd 1:0:0:0: [sda] Attached SCSI disk

dmesg from 4.8.7-1:

[   11.140091] sata_mv sata_mv.0: version 1.28
[   11.140252] sata_mv sata_mv.0: cannot get optional clkdev
[   11.170717] sata_mv sata_mv.0: slots 32 ports 1
[   11.226581] scsi host0: sata_mv
[   11.236985] ata1: SATA max UDMA/133 irq 28
[   11.554565] ata1: SATA link down (SStatus 0 SControl 300)

In this extract, ata2 is apparently never scanned.

I expect changing nr-ports to 2 will fix this. I have not tested the 
change yet, but will try to do so this weekend.

thanks
Ryan

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Am 25.11.2016 um 05:18 schrieb K.Ohta:
> Dear Michel,
> Sorry for very later.
> I test your patch of initramfs-tools, but, don't mount /usr with auto at 
> entry of fstab.
> 
> I tested below:
> 1.debuild initramfs after applying that patch and install packages.

>> W: initramfs-tools-core: script-not-executable
usr/share/initramfs-tools/hooks/mount

How did you apply the patch? If you do it via "patch < $patch", you'll
need to chmod +x hooks/mounts. The lintian warning should have been a clue.

If you use "git am $patch", then this will be done automatically:

diff --git a/hooks/mount b/hooks/mount
new file mode 100755
index 000..1464533
--- /dev/null
+++ b/hooks/mount

The patch was supposed to be applied using git am.

>> E: initramfs-tools-core: depends-on-essential-package-without-using-version 
>> depends: mount

That's a fair point. I'm not sure if we need a specific version, so this
explicit dependency can likely be dropped.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: #844605 already in linux 4.8.5

[Debian Bug Tracking System]

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

> found 844605 linux/4.8.5-1
Bug #844605 [linux] X11 segfault with AMD GPU since 4.8.x / Firmware issue
Marked as found in versions linux/4.8.5-1.
> # Due to comment
> # "with linux 4.8.x (tested 4.8.5 and 4.8.7-1) X segfaults with this device"
> # in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844605#5
> # => testing='Linux pivert 4.8.0-1-amd64 #1 SMP Debian 4.8.5-1 (2016-10-28) 
> x86_64 GNU/Linux'
> # should already be affected too => no need to delay unstable->testing.
> # Thanks, Franck
>
End of message, stopping processing here.

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

Bug#845609: linux-image-4.8.0-1-amd64-unsigned: Please enable compile option "CONFIG_MEMCG_SWAP_ENABLED"

[Zhang Jingqiang]

Package: src:linux
Version: 4.8.7-1
Severity: normal

Hello,
Please enable "CONFIG_MEMCG_SWAP_ENABLED", so we can use
"memory.memsw.limit_in_bytes" in memory cgroups.

Thanks

-- Package-specific info:
** Version:
Linux version 4.8.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 
20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13)

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

Sorry, I forgot to attach logs.
They are tar-xz ed.
Regards,
Otha.

On Wed, 23 Nov 2016 15:58:26 +0100
Michael Biebl  wrote:

> Am 23.11.2016 um 14:30 schrieb Michael Biebl:
> 
> > I'm going to reassign this to initramfs-tools as it uses mount
> > implementations from either klibc-utils or busybox which are both
> > incomplete and as a result, fail to mount /usr.
> > 
> > I decided against reassigning this to busybox and klibc-utils.
> > I think it's preferable, if initramfs-tools simply uses the mount
> > implementation from the real systemd, i.e. util-linux. This
> > guarantees that we won't run into such problems again in the future.
> > 
> > The mount utility is tiny, all its library dependencies are already
> > in the initramfs. Rebuilding the initramfs with mount from u-l
> > increases the size by 17K.
> > 
> > We would also have to make sure to use mount --move in
> > /usr/share/initramfs-tools/init for /run, /sys and /proc
> > 
> > Ben, what's your take on this?  
> 
> Something like the attached patch should do the trick.
> I wonder though, if we should use the other tools from mount as well,
> like umount, swapon/off
> 
> Feedback welcome.
> 
> 



mount_try_to_usr_with_auto_logs_20161125-1.tar.xz
Description: application/xz


pgpRi_zMATJXj.pgp
Description: OpenPGP digital signature

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

Dear Michel,
Sorry for very later.
I test your patch of initramfs-tools, but, don't mount /usr with auto at entry 
of fstab.

I tested below:
1.debuild initramfs after applying that patch and install packages.
2.Boot *without* auto and nouser with /usr entry at /etc/fstab.-> Success
3.Boot *with* auto and nouser with /usr entry at /etc/fstab.-> Fail
4.Remade initramfs (via update-initramfs -u -k `uname -r`) *without* auto and 
nouser with /usr entry at /etc/fstab .
5.Boot *without* auto and nouser with /usr entry at /etc/fstab. -> Fail.

I looked at log of debuild, found a error at litian checking:
>E: initramfs-tools-core: depends-on-essential-package-without-using-version 
>depends: mount
>W: initramfs-tools-core: script-not-executable 
>usr/share/initramfs-tools/hooks/mount

Regards,
Ohta.


On Wed, 23 Nov 2016 15:58:26 +0100
Michael Biebl  wrote:

> Am 23.11.2016 um 14:30 schrieb Michael Biebl:
> 
> > I'm going to reassign this to initramfs-tools as it uses mount
> > implementations from either klibc-utils or busybox which are both
> > incomplete and as a result, fail to mount /usr.
> > 
> > I decided against reassigning this to busybox and klibc-utils.
> > I think it's preferable, if initramfs-tools simply uses the mount
> > implementation from the real systemd, i.e. util-linux. This
> > guarantees that we won't run into such problems again in the future.
> > 
> > The mount utility is tiny, all its library dependencies are already
> > in the initramfs. Rebuilding the initramfs with mount from u-l
> > increases the size by 17K.
> > 
> > We would also have to make sure to use mount --move in
> > /usr/share/initramfs-tools/init for /run, /sys and /proc
> > 
> > Ben, what's your take on this?  
> 
> Something like the attached patch should do the trick.
> I wonder though, if we should use the other tools from mount as well,
> like umount, swapon/off
> 
> Feedback welcome.
> 
> 



pgpfVpYnwBgxD.pgp
Description: OpenPGP digital signature

Bug#838858: firmware-amd-graphics: missing SI/CI smc firmware files

[Mika Pflüger]

Hi,

I can confirm that James' patch fixes the issue for me as well, on
4.9.0-rc5. Without the patch, X can't start for me neither on 4.8 nor
on 4.9.0-rc5, but works fine on 4.7. I'm using a pitcairn graphic card.

Would be nice to get the files included soon, as it is effectively
making testing/stretch systems with radeon SI/CI cards unbootable right
now.

Cheers + thanks,

Mika


-- 



pgpDkFTgOmcXP.pgp
Description: Digitale Signatur von OpenPGP

Bug#845581: initramfs built in a chroot may lack /etc/mtab

[Ben Hutchings]

Package: initramfs-tools-core
Version: 0.125
Severity: important

mkinitramfs does:

# Remove any looping or broken symbolic links, since they break cpio.
[ "${verbose}" = y ] && xargs_verbose="-t"
(cd "${DESTDIR}" && find . -type l -printf '%p %Y\n' | sed -n 's/ [LN]$//p' 
\
| xargs ${xargs_verbose:-} -rL1 rm -f)

The comment used to be true when we used the cpio --dereference option,
but we have not done so since version 0.99.

vmdebootstrap installs packages in a chroot without /proc mounted, thus
${DESTDIR}/etc/mtab is a broken link and this command deletes it.  We
should remove this code.

Ben.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools-core depends on:
ii  cpio 2.11+dfsg-5
ii  klibc-utils  2.0.4-9
ii  kmod 23-1
ii  udev 232-6

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.1-4.4

-- no debconf information

Bug#845500: nftables: notrack target fails with No such file or directory

[Peter Colberg]

On Thu, Nov 24, 2016 at 06:58:46PM +, Ben Hutchings wrote:
> > IIRC Ben said that the next upstream kernel being tagged as LTS will be 
> > the one included in Debian strech, so we’ll probably have 4.9… unless 
> > Greg KH changes his mind again. :D
> 
> Yes, exactly.

Thanks for clarifying.

There are worse things than 3 more years of iptables–ip6tables duality ;-).

Peter

Bug#845500: nftables: notrack target fails with No such file or directory

[Ben Hutchings]

On Thu, 2016-11-24 at 13:44 +0100, Vincent Blut wrote:
> On Thu, Nov 24, 2016 at 08:46:27AM +0100, Arturo Borrero Gonzalez wrote:
> > > > On 24 November 2016 at 01:34, Peter Colberg  wrote:
> > > 
> > > While the nftables package in Debian stretch will support notrack, the
> > > corresponding kernel support was committed after the 4.9 merge window:
> > > 
> > > https://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git/commit/net/netfilter/nft_ct.c?id=254432613c588640f8b8b5c3641a3c27bbe14688
> > > 
> > > Assuming 4.9 becomes the stretch kernel, could you backport the patch?
> > 
> > 
> > Debian stretch will include linux 4.10 [0], so no problem.
> > 
> > 
> > [0] https://lists.debian.org/debian-devel-announce/2016/03/msg0.html
> 
> Hi,
> 
> IIRC Ben said that the next upstream kernel being tagged as LTS will be 
> the one included in Debian strech, so we’ll probably have 4.9… unless 
> Greg KH changes his mind again. :D

Yes, exactly.

Ben.

-- 
Ben Hutchings
[W]e found...that it wasn't as easy to get programs right as we had
thought.
... I realized that a large part of my life from then on was going to
be spent
in finding mistakes in my own programs. - Maurice Wilkes, 1949



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

Bug#845500: nftables: notrack target fails with No such file or directory

[Vincent Blut]

On Thu, Nov 24, 2016 at 08:46:27AM +0100, Arturo Borrero Gonzalez wrote:

On 24 November 2016 at 01:34, Peter Colberg  wrote:


While the nftables package in Debian stretch will support notrack, the
corresponding kernel support was committed after the 4.9 merge window:

https://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git/commit/net/netfilter/nft_ct.c?id=254432613c588640f8b8b5c3641a3c27bbe14688

Assuming 4.9 becomes the stretch kernel, could you backport the patch?



Debian stretch will include linux 4.10 [0], so no problem.


[0] https://lists.debian.org/debian-devel-announce/2016/03/msg0.html


Hi,

IIRC Ben said that the next upstream kernel being tagged as LTS will be 
the one included in Debian strech, so we’ll probably have 4.9… unless 
Greg KH changes his mind again. :D


Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#838887: please dont bomb out on nofail option

[Michael Biebl]

On Mon, 26 Sep 2016 07:02:01 +0200 Marc Haber
 wrote:
> when I looked for the last time (a few months ago), fstab entries
> parsed by initramfs-tools or in initramfs MUST NOT contain the
> "nofail" option. This is kind of surprising since some other fstab
> entries MUST contain the "nofail" option to avoid systemd from bombing
> out on boot.

Fwiw, the relevant fstab entries for the initramfs are / and /usr. And
those should not contain "nofail".



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?





signature.asc
Description: OpenPGP digital signature