Bug#805710: nfs-common: NFS mounts don't work because nfs-common starts before rpcbind.service

[Alex]

Hi,

I have the same issue. The problem for me is that the rpcbind listen socket is 
created _after_ the attempt to mount the NFS  filesystems.

After adding these 2 lines to the [Unit] section in 
/lib/systemdsystem/rpcbind.socket the problem was gone.

DefaultDependencies=no
Before=sockets.target

-- 
Alex

Bug#808051: xfs-modules for s390x fail to load because of missing crc32_generic

[alkl]

Package: xfs-modules-4.2.0-1-s390x-di
Version: 4.2.6-3
Severity: normal
Tags: d-i

Dear maintainers,

The xfs modules for s390x can not be loaded during the debian installation.
It fails because the required libcrc32c won't load. Which seems to be  
the case because crc32_generic is missing.


Many thanks in advance.

Alexander Klein

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

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 [powerpc] Modules fail to load following toolchain upgrade
Bug #808043 [src:linux] linux-image-4.3.0-1-powerpc64: Fail to load md_mod with 
unknow symbol error
Changed Bug title to '[powerpc] Modules fail to load following toolchain 
upgrade' from 'linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow 
symbol error'
> found -1 4.2.6-2
Bug #808043 [src:linux] [powerpc] Modules fail to load following toolchain 
upgrade
Marked as found in versions linux/4.2.6-2.
> tag -1 - moreinfo
Bug #808043 [src:linux] [powerpc] Modules fail to load following toolchain 
upgrade
Removed tag(s) moreinfo.

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

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

[Ben Hutchings]

Control: retitle -1 [powerpc] Modules fail to load following toolchain upgrade
Control: found -1 4.2.6-2
Control: tag -1 - moreinfo

On Tue, 2015-12-15 at 18:07 +0100, Christian Marillat wrote:
> On 15 déc. 2015 15:55, Ben Hutchings  wrote:
> 
> > Control: tag -1 moreinfo
> > 
> > On Tue, 2015-12-15 at 15:26 +0100, Christian Marillat wrote:
> > > Package: src:linux
> > > Version: 4.3.1-1
> > > Severity: serious
> > > 
> > > Dear Maintainer,
> > > 
> > > Since 4.2.6-2 the Powerpc G5 doesn't start with an error 'unknow symbol 
> > > in md_mod'
> > > 
> > > 4.2.6-1 work fine.
> > > 
> > > / is a RAID0 partition and kernels are in a normal partition in /boot
> > [...]
> > 
> > I don't see any differences between 4.2.6-1 and 4.2.6-2 that relate to
> > the md driver.
> 
> Me too, but the problem come from maybe the compiler or linker.

Right.

For 4.2.6-1: binutils 2.25.1-7           gcc-4.9 4.9.3-5
For 4.2.6-2: binutils 2.25.90.20151125-2 gcc-4.9 4.9.3-8

> > Assuming you get a rescue shell in the initramfs:
> > - The kernel log will show what the symbol is; please send that line
> >   (or lines)
> > - Send the output of 'modinfo -Fvermagic md_mod'
> 
> I don't have access to the rescue shell. CPUs go to 100% and
> the keyboard doesn't work. I attached two photos.
> 
> In the bottom screenshot you'll see that other module fail to load with
> an 'unknow symbol in module".

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.

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky

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

Bug#807624: armhf: Please enable support for DRA7XX systems (Beagle-x15)

[Vagrant Cascadian]

On 2015-12-10, Ben Hutchings wrote:
> On Thu, 2015-12-10 at 16:09 -0800, Vagrant Cascadian wrote:
>> Please enable support for DRA7XX systems, such as the Beagle-x15.
>> 
>> I was able to boot a Beagle-x15 system by applying the following
>> patch
>> to the debian packaging for linux 4.3-1~exp1:
>> 
>> diff --git a/debian/config/armhf/config.armmp
>> b/debian/config/armhf/config.armmp
>> index 285f9c3..457ca53 100644
>> --- a/debian/config/armhf/config.armmp
>> +++ b/debian/config/armhf/config.armmp
>> @@ -69,6 +69,7 @@ CONFIG_ARCH_OMAP3=y
>>  CONFIG_ARCH_OMAP4=y
>>  CONFIG_SOC_OMAP5=y
>>  CONFIG_SOC_AM33XX=y
>> +CONFIG_SOC_DRA7XX=y
>>  CONFIG_ARCH_OMAP2PLUS_TYPICAL=y
>>  CONFIG_SOC_OMAP3430=y
>>  CONFIG_SOC_TI81XX=y
>
> How about additional device drivers?  I found these which seem to be
> useful for DRA7xx chips but aren't enabled yet:
>
> CONFIG_SND_DAVINCI_SOC_MCASP
> CONFIG_VIDEO_TI_VPE
> CONFIG_SPI_TI_QSPI
> CONFIG_PCI_DRA7XX

With those enabled, there were no additional modules automatically
loaded and no PCI devices listed. So it doesn't seem to change anything
for the beagle-x15.

USB didn't work for me; all I saw were the USB3 and USB2 hub devices,
nothing plugged into them.

I haven't yet tested eSATA or video/framebuffer output yet. Hope to try
that later today. I'll also test a build with the 4.4.x kernel, to see
if updates to any of the drivers improve the situation.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#791868: closed by Milan Kupcevic <mi...@physics.harvard.edu> (Bug#741642: fixed in mkvmlinuz 37+deb8u1)

[Holger Levsen]

Hi Milan,

thanks for fixing this bug in stable! It's great to see this bug seeing fixed, 
even despite I finally gave the hardware away a very few weeks ago… :)


cheers,
Holger


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

linux_4.3.3-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Dec 2015 21:25:26 +
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#807624: armhf: Please enable support for DRA7XX systems (Beagle-x15)

[Vagrant Cascadian]

Control: tags 807624 -moreinfo

On 2015-12-15, Vagrant Cascadian wrote:
> On 2015-12-10, Ben Hutchings wrote:
>> On Thu, 2015-12-10 at 16:09 -0800, Vagrant Cascadian wrote:
>>> Please enable support for DRA7XX systems, such as the Beagle-x15.
...
>> How about additional device drivers?  I found these which seem to be
>> useful for DRA7xx chips but aren't enabled yet:
>>
>> CONFIG_SND_DAVINCI_SOC_MCASP
>> CONFIG_VIDEO_TI_VPE
>> CONFIG_SPI_TI_QSPI
>> CONFIG_PCI_DRA7XX
>
> With those enabled, there were no additional modules automatically
> loaded and no PCI devices listed. So it doesn't seem to change anything
> for the beagle-x15.
>
> USB didn't work for me; all I saw were the USB3 and USB2 hub devices,
> nothing plugged into them.
>
> I haven't yet tested eSATA or video/framebuffer output yet. Hope to try
> that later today. I'll also test a build with the 4.4.x kernel, to see
> if updates to any of the drivers improve the situation.

With 4.4.x and with CONFIG_SOC_DRA7XX=y added, I get:

Works:
frambuffer video
serial console
both CPUs detected
all RAM detected
eMMC works
microSD works

Doesn't work:
eSATA
USB

Haven't tested:
audio

dmesg and lsmod output attached if that would be helpful.


Would you consider enabling it even though there are some notable
features not yet working?


live well,
  vagrant



dmesg
Description: Binary data


lsmod
Description: Binary data


signature.asc
Description: PGP signature

Processed: Re: Bug#807624: armhf: Please enable support for DRA7XX systems (Beagle-x15)

[Debian Bug Tracking System]

Processing control commands:

> tags 807624 -moreinfo
Bug #807624 [src:linux] armhf: Please enable support for DRA7XX systems 
(Beagle-x15)
Removed tag(s) moreinfo.

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

Processing of linux_4.3.3-1_source.changes

[Debian FTP Masters]

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

Greetings,

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

Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4

[Alexandre]

Package: linux-image-4.4.0-rc4-amd64
Version: 4.4~rc4-1~exp1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Actually, i'm usging linux-image-4.3.0-trunk-amd64 on Dell XPS 13 9350. In
order to fix WiFi problem i would install linux-image-4.4.0rc4 but it makes it
impossible to boot my laptop.

I have this message before Luks ask passphrase :

Loading, please wait...
modprobe: module microcode not found in modules.dep
lvmetad is not active yet, using direct activation during sysinit
volume group "vg" not found
Cannot process volume group vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.




-- System Information:
Debian Release: stretch/sid
  APT prefers stable
  APT policy: (1001, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Bug#808035: [src:linux] Local Modules Fail to Load

[David Baron]

Package: src:linux
Version: linux-image-4.3.0-1
Severity: grave

--- Please enter the report below this line. ---
Today's upgrades, nvidia-legacy drivers, dkms, and linux-image, headers 
4.3.0-1

On reboot to 4.3.0-1 kernel, get two messages "Local modules fail to load"
Everything else seems to play OK, no other messages on boot.
Kde GUI fails to start.

This may be a post-install problem, relating the nvidia-legacy-304xx  dkms, 
why I mention them.
Kernel objects were built, in their similar places to 4.2.0-1.
But, indeed, xorg log reports failure to load module>

Notes:

Despite the tiny / partition given by the installer, one does, indeed need 
space to have more than one kernel around. For just this type of eventuality!!

Got that good old "Failed to mount /usr" on 4.2.0-1 bootup. /proc/mounts shows 
/usr is, in fact, mounted rw.



--- System information. ---
Architecture: amd64
Kernel:   Linux 4.2.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
1 experimentalftp.us.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Processed: reassign 808038 to src:linux

[Debian Bug Tracking System]

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

> reassign 808038 src:linux 4.4~rc4-1~exp1
Bug #808038 [linux-image-4.4.0-rc4-amd64] linux-image-4.4.0-rc4-amd64: Fails to 
boot on kernel 4.4rc4
Bug reassigned from package 'linux-image-4.4.0-rc4-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.4~rc4-1~exp1.
Ignoring request to alter fixed versions of bug #808038 to the same values 
previously set
Bug #808038 [src:linux] linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 
4.4rc4
Marked as found in versions linux/4.4~rc4-1~exp1.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #808043 [src:linux] linux-image-4.3.0-1-powerpc64: Fail to load md_mod with 
unknow symbol error
Added tag(s) moreinfo.

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

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

[Christian Marillat]

Package: src:linux
Version: 4.3.1-1
Severity: serious

Dear Maintainer,

Since 4.2.6-2 the Powerpc G5 doesn't start with an error 'unknow symbol in 
md_mod'

4.2.6-1 work fine.

/ is a RAID0 partition and kernels are in a normal partition in /boot

Christian

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
revision: 1.1 (pvr 0044 0101)
revision: 1.1 (pvr 0044 0101)
revision: 1.1 (pvr 0044 0101)
revision: 1.1 (pvr 0044 0101)
platform: PowerMac
model   : PowerMac11,2
machine : PowerMac11,2
motherboard : PowerMac11,2 MacRISC4 Power Macintosh 

** PCI devices:
:00:0b.0 PCI bridge [0604]: Apple Inc. CPC945 PCIe Bridge [106b:005b] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

:0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV43 [GeForce 
6600] [10de:0141] (rev a2) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device [10de:0010]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

0001:00:00.0 Host bridge [0600]: Apple Inc. U4 HT Bridge [106b:0074]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

0001:00:01.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge 
[1166:0130] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:02.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-X bridge 
[1166:0130] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:03.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:04.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:05.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:06.0 PCI bridge [0604]: Broadcom BCM5780 [HT2000] PCI-Express Bridge 
[1166:0132] (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:07.0 PCI bridge [0604]: Apple Inc. Shasta PCI Bridge [106b:0053] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

0001:00:08.0 PCI bridge [0604]: Apple Inc. Shasta PCI Bridge [106b:0054] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast 

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

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 2015-12-15 at 15:26 +0100, Christian Marillat wrote:
> Package: src:linux
> Version: 4.3.1-1
> Severity: serious
> 
> Dear Maintainer,
> 
> Since 4.2.6-2 the Powerpc G5 doesn't start with an error 'unknow symbol in 
> md_mod'
> 
> 4.2.6-1 work fine.
> 
> / is a RAID0 partition and kernels are in a normal partition in /boot
[...]

I don't see any differences between 4.2.6-1 and 4.2.6-2 that relate to
the md driver.

Assuming you get a rescue shell in the initramfs:
- The kernel log will show what the symbol is; please send that line
  (or lines)
- Send the output of 'modinfo -Fvermagic md_mod'

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky

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

Bug#808044: linux-image-4.3.0-1-amd64: Braswell NUC SD card reader needs Cherryview PINCTRL module

[bugreporter]

Package: src:linux
Version: 4.3.1-1Severity: important
Dear Maintainer,
The built-in SD card reader of the Intel Braswell NUC5PPYHdoesn't work under 
Debian Unstable running the latestLinux 4.3 kernel.  The card reader, 
however, works withUbuntu 15.10, which runs an older Linux 4.2 kernel.
Below is a comparison between the relevant portions of theDebian Unstable and 
Ubuntu 15.10 (Wily Werewolf) kernelconfiguration files. The key difference is 
the presenceof the CONFIG_PINCTRL_CHERRYVIEW=m option in the Ubuntukernel 
config.
$ grep -i pinctrl /boot/config-4.3.0-1-amd64 #Debian Unstable# 
CONFIG_I2C_MUX_PINCTRL is not setCONFIG_PINCTRL=y# CONFIG_DEBUG_PINCTRL is 
not set# CONFIG_PINCTRL_AMD is not setCONFIG_PINCTRL_BAYTRAIL=y# 
CONFIG_PINCTRL_CHERRYVIEW is not set# CONFIG_PINCTRL_SUNRISEPOINT is not set
$ grep -i pinctrl /boot/config-4.2.0-16-generic #Ubuntu 
15.10CONFIG_I2C_MUX_PINCTRL=mCONFIG_PINCTRL=y# CONFIG_DEBUG_PINCTRL is not 
setCONFIG_PINCTRL_AMD=yCONFIG_PINCTRL_BAYTRAIL=yCONFIG_PINCTRL_CHERRYVIEW=mCONFIG_PINCTRL_INTEL=mCONFIG_PINCTRL_SUNRISEPOINT=m
A comparison between the dmesg output for Debian Unstableand Ubuntu (15.10) 
shows the problem clearly ("failed tosetup card detect gpio").
$ dmesg | grep -i sdhci #Debian Unstable[    1.288201] sdhci: Secure Digital 
Host Controller Interface driver[    1.288208] sdhci: Copyright(c) Pierre 
Ossman[    1.317111] sdhci-pci :00:12.0: SDHCI controller found 
[8086:2296] (rev 21)[    1.317295] sdhci-pci :00:12.0: failed to setup 
card detect gpio[    1.318814] sdhci-pci :00:12.0: No vmmc regulator 
found[    1.318823] sdhci-pci :00:12.0: No vqmmc regulator found[   
 1.324453] mmc0: SDHCI controller on PCI [:00:12.0] using ADMA
$ dmesg | grep -i sdhci #Ubuntu 15.10[   11.433662] sdhci: Secure Digital 
Host Controller Interface driver[   11.433666] sdhci: Copyright(c) Pierre 
Ossman[   11.472483] sdhci-pci :00:12.0: SDHCI controller found 
[8086:2296] (rev 21)[   11.473841] sdhci-pci :00:12.0: No vmmc regulator 
found[   11.473845] sdhci-pci :00:12.0: No vqmmc regulator found[   
11.477273] mmc0: SDHCI controller on PCI [:00:12.0] using ADMA
Under Ubuntu 15.10, the pinctrl_cherryview module is loadedautomatically 
during system startup:
$ lsmod | grep -Ei 'sdhci|pinctrl' #Debian Unstablesdhci_pci             
 24576  0sdhci_acpi             16384  0sdhci                  40960  2 
sdhci_acpi,sdhci_pci
$ lsmod | grep -Ei 'sdhci|pinctrl' #Ubuntu 15.10sdhci_pci              24576 
 0sdhci_acpi             16384  0sdhci                  45056  2 
sdhci_acpi,sdhci_pcipinctrl_cherryview     32768  2
$ lspci #Debian Unstable00:00.0 Host bridge: Intel Corporation Device 2280 
(rev 21)00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 
21)00:12.0 SD Host controller: Intel Corporation Device 2296 (rev 21)00:13.0 
SATA controller: Intel Corporation Device 22a3 (rev 21)00:14.0 USB 
controller: Intel Corporation Device 22b5 (rev 21)00:18.0 DMA controller: 
Intel Corporation Device 22c0 (rev 21)00:18.6 Serial bus controller [0c80]: 
Intel Corporation Device 22c6 (rev 21)00:18.7 Serial bus controller [0c80]: 
Intel Corporation Device 22c7 (rev 21)00:1a.0 Encryption controller: Intel 
Corporation Device 2298 (rev 21)00:1b.0 Audio device: Intel Corporation 
Device 2284 (rev 21)00:1c.0 PCI bridge: Intel Corporation Device 22c8 (rev 
21)00:1c.1 PCI bridge: Intel Corporation Device 22ca (rev 21)00:1c.2 PCI 
bridge: Intel Corporation Device 22cc (rev 21)00:1f.0 ISA bridge: Intel 
Corporation Device 229c (rev 21)00:1f.3 SMBus: Intel Corporation Device 2292 
(rev 21)02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 
81)03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
-- System Information:Debian Release: stretch/sid  APT prefers testing  APT 
policy: (900, 'testing'), (90, 'unstable')Architecture: amd64 (x86_64)Foreign 
Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)Shell: /bin/sh linked to 
/bin/dashInit: sysvinit (via /sbin/init)
Versions of packages linux-image-4.3.0-1-amd64 depends on:ii  debconf 
[debconf-2.0]                   1.5.58ii  initramfs-tools 
[linux-initramfs-tool]  0.120ii  kmod                                   
 21-1ii  linux-base                              4.0
Versions of packages linux-image-4.3.0-1-amd64 recommends:ii 
 firmware-linux-free  3.4
Versions of packages linux-image-4.3.0-1-amd64 is related to:ii 
 firmware-iwlwifi                         20151207-1ii  firmware-linux       
                    20151207-1ii  firmware-linux-nonfree                   
20151207-1ii  firmware-misc-nonfree [firmware-ralink]  20151207-1ii 
 firmware-realtek                         20151207-1
-- debconf information:  
linux-image-4.3.0-1-amd64/postinst/depmod-error-initrd-4.3.0-1-amd64: false  
linux-image-4.3.0-1-amd64/prerm/removing-running-kernel-4.3.0-1-amd64: true  

Processed: notfound 808044 in 4.3.1-1Severity, found 808044 in 4.3.1-1, severity of 808044 is important

[Debian Bug Tracking System]

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

> notfound 808044 4.3.1-1Severity
Bug #808044 [src:linux] linux-image-4.3.0-1-amd64: Braswell NUC SD card reader 
needs Cherryview PINCTRL module
The source 'linux' and version '4.3.1-1Severity' do not appear to match any 
binary packages
Ignoring request to alter found versions of bug #808044 to the same values 
previously set
> found 808044 4.3.1-1
Bug #808044 [src:linux] linux-image-4.3.0-1-amd64: Braswell NUC SD card reader 
needs Cherryview PINCTRL module
Marked as found in versions linux/4.3.1-1.
> severity 808044 important
Bug #808044 [src:linux] linux-image-4.3.0-1-amd64: Braswell NUC SD card reader 
needs Cherryview PINCTRL module
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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