Bug#819390: marked as done (linux-image-4.5.0-trunk-armmp-lpae: Ethernet on Firefly-RK3288)

2017-12-07 Thread Debian Bug Tracking System 
Your message dated Thu, 07 Dec 2017 14:48:46 -0800
with message-id <877etyupbl@aikidev.net>
and subject line Re: linux-image-4.5.0-trunk-armmp-lpae: Ethernet on 
Firefly-RK3288
has caused the Debian Bug report #819390,
regarding linux-image-4.5.0-trunk-armmp-lpae: Ethernet on Firefly-RK3288
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.)


-- 
819390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5-1~exp1
Severity: normal

When upgrading to linux 4.5-1~exp1, the ethernet no longer responds
correctly.  Downgrading back to 4.4.6-1 from sid/stretch fixes the issue.

I see these messages in syslog:

Mar 27 21:25:37 ff2a systemd[1]: Reached target System Time Synchronized.
Mar 27 21:25:37 ff2a networking[311]: Configuring network interfaces...[ERROR] 
Could not read permanent MAC: Device or resource busy
Mar 27 21:25:37 ff2a networking[311]: Current MAC:   00:00:00:00:00:00 (XEROX 
CORPORATION)
Mar 27 21:25:37 ff2a networking[311]: Permanent MAC: 00:00:00:00:00:00 (XEROX 
CORPORATION)
Mar 27 21:25:37 ff2a networking[311]: New MAC:   4e:e3:67:92:21:0e (unknown)
Mar 27 21:25:37 ff2a networking[311]: RTNETLINK answers: No such device
Mar 27 21:25:37 ff2a networking[311]: Failed to bring up eth0.
Mar 27 21:25:37 ff2a networking[311]: done.
Mar 27 21:25:37 ff2a systemd[1]: Started LSB: Raise network interfaces..
Mar 27 21:25:37 ff2a systemd[1]: Starting Network.
--
Mar 27 21:25:37 ff2a kernel: [   10.182806]  mmcblk1: p1 p2
Mar 27 21:25:37 ff2a kernel: [   10.552168] Adding 5242876k swap on 
/dev/mapper/ff2a-swap.  Priority:-1 extents:1 across:5242876k FS
Mar 27 21:25:37 ff2a kernel: [   10.705565] EXT4-fs (dm-2): mounted filesystem 
with ordered data mode. Opts: (null)
Mar 27 21:25:37 ff2a atd[494]: File a1017285b2 is in wrong format - aborting
Mar 27 21:25:37 ff2a kernel: [   11.637423] EXT4-fs (mmcblk1p2): mounted 
filesystem with ordered data mode. Opts: (null)
Mar 27 21:25:37 ff2a kernel: [   12.169292] libphy: PHY stmmac-0: not 
found
Mar 27 21:25:37 ff2a kernel: [   12.174209] eth0: Could not attach to PHY
Mar 27 21:25:37 ff2a kernel: [   12.178246] stmmac_open: Cannot attach to PHY 
(error: -19)
Mar 27 21:25:37 ff2a systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Mar 27 21:25:37 ff2a kernel: [   13.051128] ip6_tables: (C) 2000-2006 Netfilter 
Core Team

Full syslog from boot attached.

live well,
  vagrant


-- Package-specific info:
** Kernel log: syslog attached

** Model information
Hardware: Rockchip (Device Tree)
Revision: 
Device Tree model: Firefly-RK3288

** PCI devices:

** USB devices:
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 152d:1561 JMicron Technology Corp. / JMicron USA 
Technology Corp. 
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental'), 
(1, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.4.0-1-armmp-lpae (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)

Versions of packages linux-image-4.5.0-trunk-armmp-lpae depends on:
ii  debconf [debconf-2.0]   1.5.56
ii  initramfs-tools [linux-initramfs-tool]  0.120
ii  kmod18-3
ii  linux-base  3.5

Versions of packages linux-image-4.5.0-trunk-armmp-lpae recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.0.6-3

Versions of packages linux-image-4.5.0-trunk-armmp-lpae suggests:
pn  debian-kernel-handbook  
pn  fdutils 
pn  linux-doc-4.5   

Versions of packages linux-image-4.5.0-trunk-armmp-lpae is related to:
pn  firmware-atheros
pn  firmware-bnx2   
pn  firmware-bnx2x  
pn  firmware-brcm80211  
pn  firmware-intelwimax 
pn  firmware-ipw2x00
pn  firmware-ivtv   
pn  firmware-iwlwifi
pn  firmware-libertas   
pn  firmware-linux  
pn  firmware-linux-nonfree  
pn  firmware-myricom
pn  firmware-netxen 
pn  firmware-qlogic 
pn  firmware-ralink 
pn  firmware-realtek
pn  xen-hypervisor  

-- debconf information:
  
linux-image-4.5.0-trunk-armmp-lpae/prerm/removing-running-kernel-4.5.0-trunk-armmp-lpae:

Re: Disable intel management engine

2017-12-07 Thread Yves-Alexis Perez 
On Fri, 2017-12-01 at 09:22 -0800, piruthiviraj natarajan wrote:
> I see that system 76 disables intel management engine for a potential
> security breach. 
> Does Debian has any plans similar to this?
> 
> http://blog.system76.com/post/168050597573/system76-me-firmware-updates-plan

System76 manages the hardware and firmware of their machines. Debian is a
distribution, we have no control over what machine our users uses. Disabling
the management using (using the HAP bit) is not something which can be
attempted  without deep knowledge of the machine it runs on.

So the short answer would be no, because we can't.

Regards,
-- 
Yves-Alexis

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

Processed: Re: Bug#864562: u-boot: broken ethernet support on Olimex A20-Olinuxino-Micro Rev. J

2017-12-07 Thread Debian Bug Tracking System 
Processing control commands:

> reassign 864562 u-boot-sunxi
Bug #864562 [src:linux] No ethernet link on Olimex A20-Olinuxino Micro Rev. J, 
possibly PHY driver problem.
Bug reassigned from package 'src:linux' to 'u-boot-sunxi'.
No longer marked as found in versions linux/4.9.30-1.
Ignoring request to alter fixed versions of bug #864562 to the same values 
previously set
> retitle 864562 u-boot: broken ethernet support on Olimex A20-Olinuxino-Micro 
> Rev. J
Bug #864562 [u-boot-sunxi] No ethernet link on Olimex A20-Olinuxino Micro Rev. 
J, possibly PHY driver problem.
Changed Bug title to 'u-boot: broken ethernet support on Olimex 
A20-Olinuxino-Micro Rev. J' from 'No ethernet link on Olimex A20-Olinuxino 
Micro Rev. J, possibly PHY driver problem.'.
> tags 864562 patch
Bug #864562 [u-boot-sunxi] u-boot: broken ethernet support on Olimex 
A20-Olinuxino-Micro Rev. J
Added tag(s) patch.

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

Bug#864562: u-boot: broken ethernet support on Olimex A20-Olinuxino-Micro Rev. J

2017-12-07 Thread Karsten Merker 
control: reassign 864562 u-boot-sunxi
control: retitle 864562 u-boot: broken ethernet support on Olimex 
A20-Olinuxino-Micro Rev. J
control: tags 864562 patch

On Mon, Oct 16, 2017 at 10:45:57PM +0200, Karsten Merker wrote:
> On Mon, Oct 16, 2017 at 09:39:36PM +0200, Jean-Louis Mounier wrote:

[Ethernet not working on Olimex A20-Olinuxino Micro Rev. J]
> > I discovered a new installer release but the bug is still
> > present.
> > 
> > Now the test :
> > 
> > => gpio clear PA17
> > gpio: pin PA17 (gpio 17) value is 0
> > =>run bootcmd
> > 
> > after that, the installer got IPV4 and IPV6 addresses wwith DHCP and then
> > ran fine.
> > 
> > Hope it helps
> 
> Yes, that helps as it confirms that a change in u-boot alone is
> enough to work around the issue in Linux as well (although it is
> debateable whether the kernel should rely on the bootloader in
> this case or not).  There has recently been an attempt to address
> the issue in mainline u-boot, but that didn't work out as planned
> and the patch got rejected:
> 
> https://lists.denx.de/pipermail/u-boot/2017-September/307778.html

Hello,

a patch to address this issue has finally been accepted today by
the upstream u-boot custodian for the sunxi platform, targeting
u-boot v2018.01:

https://patchwork.ozlabs.org/patch/833763/

Vagrant, could you include the patch in the next u-boot package
upload?

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.