Error! Bad return status for module build on kernel

2015-07-05 Thread mudongliang
Today I compiled linux-kernel 4.1.1 and 4.0.7 in Debian Jessie!
The procedure is the following:
1. make menuconfig
2. do nothing change or patch 
3. save the default selection to .config
4. make -j4
5. make modules_install install

Both kernel encounter the following error in the fifth step:
Error! Bad return status for module build on kernel: 4.1.1/4.0.7

However, with kernel 4.1.1 the system can't boot , and 4.0.7 can!

What's the problem?

My final destination is to get kernel with only corresponding pax patched!
Is there any easy method?
- mudongliang


0x6BF5DC28.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Processed: Re: Bug#791489: /sbin/reiserfsck is not included in initrd image

2015-07-05 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 reiserfsprogs
Bug #791489 [initramfs-tools] /sbin/reiserfsck is not included in initrd image
Bug reassigned from package 'initramfs-tools' to 'reiserfsprogs'.
No longer marked as found in versions initramfs-tools/0.120.
Ignoring request to alter fixed versions of bug #791489 to the same values 
previously set
 tag -1 jessie sid
Bug #791489 [reiserfsprogs] /sbin/reiserfsck is not included in initrd image
Added tag(s) jessie and sid.

-- 
791489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791489
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.b791489.143611487318056.transcr...@bugs.debian.org



Bug#791489: /sbin/reiserfsck is not included in initrd image

2015-07-05 Thread dimas
Package: initramfs-tools
Version: 0.120
Severity: grave

after recent upgrades, which triggered update-initramfs, i've got my system
unbootable, compalining that /sbin/reiserfsck can not be run.
i've dug into the problem, and found that binary isn't copied
by /usr/share/initramfs-tools/hooks/fsck. the latter has the following lines:

for type in $(get_fstypes | sort | uniq); do
if [ $type = 'auto' ] ; then
echo Warning: couldn't identify filesystem type for fsck hook, 
ignoring.
continue
fi
+++[ $type = reiserfs ]  copy_exec /sbin/reiserfsck

prog=/sbin/fsck.${type}
if [ -h $prog ]; then
link=$(readlink -f $prog)
copy_exec $link
ln -s $link ${DESTDIR}/$prog
elif [ -x $prog ] ; then
copy_exec $prog
else
echo Warning: /sbin/fsck.${type} doesn't exist, can't install 
to initramfs, ignoring.
fi
done

(line marked with +++ is added by me as a fix).
the behaviour is that if fsck.$type is binary, it copies it. if it's a link, it
copies linked file too. but fsck.reiserfs is not a binary, neither a symlink.
it's a wrapper script:

#! /bin/sh
# Treat the -y flag the same way other fsck.* instances do
ADD_OPTS=
for opt
do
case $opt in
--)
break
;;
-y)
ADD_OPTS=-a
;;
esac
done
# Be sure to invoke reiserfsck quitely for booting over slow consoles
exec /sbin/reiserfsck -q $ADD_OPTS $@

so we need to modify hook script like i did to fix this. maybe we also need to
check, whether other fs utils have such wrapper scripts, so their users won't
get stuck with the similar problem.


-- 
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/20150705191200.75c2e...@ulf.tvoe.tv



Bug#791489: /sbin/reiserfsck is not included in initrd image

2015-07-05 Thread Ben Hutchings
Control: reassign -1 reiserfsprogs
Control: tag -1 jessie sid

reiserfs is deprecated in Debian and I don't think it makes sense to
give it special treatment in initramfs-tools.  If it needs special
treatment then reiserfsprogs can do that with a hook script.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug



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


Processed: mkvmlinuz

2015-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 286303 + wontfix
Bug #286303 [mkvmlinuz] mkvmlinuz: Add detection of NuBuS pmacs ...
Added tag(s) wontfix.
 tags 414839 + moreinfo
Bug #414839 [mkvmlinuz] mkvmlinuz fails with undefined reference to 
zlib_inflate_blocks* against 2.6.18-4-powerpc
Added tag(s) moreinfo.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
286303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286303
414839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414839
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.143614123520359.transcr...@bugs.debian.org



Bug#790694: linux-image-3.16.0-4-powerpc64: nouveau driver and msi interrupts

2015-07-05 Thread Ben Hutchings
Actually this much simpler patch should do the trick; please test this
instead.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

From: Ben Hutchings b...@decadent.org.uk
Date: Mon, 06 Jul 2015 01:24:37 +0100
Subject: nouveau: Disable MSI on G70 (NV47)
Bug-Debian: https://bugs.debian.org/790694

Peter Saisanas reported that MSI did not work properly on his Quadro
FX 4500 in a PowerMac.  Assuming this is a general problem with this
GPU type, disable MSI.

References: https://bugs.debian.org/790694
Reported-by: Peter Saisanas psaisa...@gmail.com
---
--- a/drivers/gpu/drm/nouveau/core/engine/device/nv40.c
+++ b/drivers/gpu/drm/nouveau/core/engine/device/nv40.c
@@ -173,7 +173,7 @@ nv40_identify(struct nouveau_device *dev
 		device-oclass[NVDEV_SUBDEV_CLOCK  ] = nv40_clock_oclass;
 		device-oclass[NVDEV_SUBDEV_THERM  ] = nv40_therm_oclass;
 		device-oclass[NVDEV_SUBDEV_DEVINIT] =  nv1a_devinit_oclass;
-		device-oclass[NVDEV_SUBDEV_MC ] =  nv40_mc_oclass;
+		device-oclass[NVDEV_SUBDEV_MC ] =  nv04_mc_oclass;
 		device-oclass[NVDEV_SUBDEV_BUS] =  nv31_bus_oclass;
 		device-oclass[NVDEV_SUBDEV_TIMER  ] = nv04_timer_oclass;
 		device-oclass[NVDEV_SUBDEV_FB ] =  nv47_fb_oclass;


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


Processed: Re: Bug#790944: networking CRASHES when using WAKEONLAN

2015-07-05 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #790944 [src:linux] networking CRASHES when using WAKEONLAN
Added tag(s) moreinfo.

-- 
790944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790944
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.b790944.143613877810225.transcr...@bugs.debian.org



Bug#790944: networking CRASHES when using WAKEONLAN

2015-07-05 Thread Ben Hutchings
Control: tag -1 moreinfo

On Fri, 2015-07-03 at 11:05 +0200, Thomas Schmidt wrote:
 Package: src:linux
 Version: 4.0.5-1
 Severity: important
 
 Dear Maintainer,
 
 *** Reporter, please consider answering these questions, where 
 appropriate ***
 
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
  ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
 
 *** End of the template - remove these template lines ***

You didn't answer the questions.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.



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


Processed: retitle 789070 to CONFIG_HIBERNATION broken on POWER7+ and causes build failure on ppc64el ...

2015-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 retitle 789070 CONFIG_HIBERNATION broken on POWER7+ and causes build failure 
 on ppc64el
Bug #789070 [src:linux] gas incorrectly expects an operand for PPC tlbia 
instructions
Changed Bug title to 'CONFIG_HIBERNATION broken on POWER7+ and causes build 
failure on ppc64el' from 'gas incorrectly expects an operand for PPC tlbia 
instructions'
 found 789070 4.0.5-1
Bug #789070 [src:linux] CONFIG_HIBERNATION broken on POWER7+ and causes build 
failure on ppc64el
Marked as found in versions linux/4.0.5-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
789070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789070
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.143613632031514.transcr...@bugs.debian.org



Bug#790838: marked as done ((no subject))

2015-07-05 Thread Debian Bug Tracking System
Your message dated Mon, 06 Jul 2015 00:27:16 +0100
with message-id 1436138836.7337.38.ca...@decadent.org.uk
and subject line Re: Bug#790838: (no subject)
has caused the Debian Bug report #790838,
regarding (no subject)
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.)


-- 
790838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:linux
Version: 4.0.5-1
Severity: minor
File: linux-image-4.0.0.2-686-pae

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.0.0-2-686-pae (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-21) ) #1 SMP Debian 4.0.5-1 (2015-06-16)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.0.0-2-686-pae 
root=UUID=51052b81-aa31-419e-8bb0-8a6ca7f0b466 ro vga=0x11a quiet 
init=/lib/sysvinit/init

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   19.696746] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   20.316204] [drm] Initialized drm 1.1.0 20060810
[   20.744029] floppy0: no floppy controllers found
[   20.755732] [drm] Memory usable by graphics device = 512M
[   20.755735] [drm] Replacing VGA console driver
[   20.756336] Console: switching to colour dummy device 80x25
[   20.780035] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   20.780038] [drm] Driver supports precise vblank timestamp query.
[   20.780093] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   20.781167] [drm] initialized overlay support
[   20.781213] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD 
(20150204/video-1257)
[   20.781216] ACPI: Video Device [GFX0] (multi-head: no  rom: yes  post: no)
[   20.781295] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
[   20.781347] [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0
[   20.800834] fbcon: inteldrmfb (fb0) is primary device
[   20.830537] Console: switching to colour frame buffer device 128x48
[   20.843142] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   20.843144] i915 :00:02.0: registered panic notifier
[   22.176370] input: A4Tech USB Mouse as 
/devices/pci:00/:00:1d.2/usb3/3-1/3-1:1.0/0003:09DA:000A.0001/input/input10
[   22.176833] a4tech 0003:09DA:000A.0001: input,hidraw0: USB HID v1.10 Mouse 
[A4Tech USB Mouse] on usb-:00:1d.2-1/input0
[   28.193828] Adding 979928k swap on /dev/sda5.  Priority:-1 extents:1 
across:979928k FS
[   28.236676] EXT4-fs (sda1): re-mounted. Opts: (null)
[   77.056307] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   77.268900] lp: driver loaded but no devices found
[   77.274114] ppdev: user-space parallel port driver
[   77.288182] loop: module loaded
[   80.855184] EXT4-fs (sda2): mounting ext3 file system using the ext4 
subsystem
[   80.892495] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: 
(null)
[   80.918973] EXT4-fs (sda6): mounting ext3 file system using the ext4 
subsystem
[   80.929943] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: 
(null)
[   80.943836] EXT4-fs (sda7): mounting ext3 file system using the ext4 
subsystem
[   80.956608] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: 
(null)
[   80.970449] EXT4-fs (sda8): mounting ext3 file system using the ext4 
subsystem
[   80.998096] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: 
(null)
[   81.015903] EXT4-fs (sdb1): mounting ext3 file system using the ext4 
subsystem
[   81.041080] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: 
(null)
[   81.063360] EXT4-fs (sdb10): mounting ext3 file system using the ext4 
subsystem
[   81.087308] EXT4-fs (sdb10): mounted filesystem with ordered data mode. 
Opts: (null)
[   81.099346] EXT4-fs (sdb11): mounting ext3 file system using the ext4 
subsystem
[   81.169432] EXT4-fs (sdb11): mounted filesystem with ordered data mode. 
Opts: (null)
[   81.186146] EXT4-fs (sdb2): mounting ext3 file system using the ext4 
subsystem
[   81.212094] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: 
(null)
[   81.216840] EXT4-fs (sdb5): mounting ext3 file system using the ext4 
subsystem
[   81.262717] 

Processed: Re: Bug#790694: linux-image-3.16.0-4-powerpc64: nouveau driver and msi interrupts

2015-07-05 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #790694 [src:linux] linux-image-3.16.0-4-powerpc64: nouveau driver and msi 
interrupts
Added tag(s) moreinfo.

-- 
790694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790694
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.b790694.143614273526589.transcr...@bugs.debian.org



Bug#790694: linux-image-3.16.0-4-powerpc64: nouveau driver and msi interrupts

2015-07-05 Thread Ben Hutchings
Control: tag -1 moreinfo

On Wed, 2015-07-01 at 07:49 +1000, Peter Saisanas wrote:
 Package: src:linux
 Version: 3.16.7-ckt11-1
 Severity: important
 
 Dear Maintainer,
 
 The nouveau driver defaults to using MSI interrupts should it see the msi
 interrupt pci flag supported on the supported target nVidia GPU.
 However, in some cases, the MSI address or vector is not configured correctly
 in the VGA bios or in this case the OpenFirmware FCODE ROM.

That is not its responsibility.

 When running linux-image-3.16.0-4-powerpc64 on a Powermac G5 11.2 machine (G5
 Quad to be precise) with a Quadro FX4500 (nv47 class gpu),the newer nouveau
 drivers in more recent kernels default to using MSI interrupts, however with
 the PPC G5, when using  MSI interrupts, the powerpc FCODE rom on Nvidia cards
 does not correctly set up the MSI address (or vector). This is a bug of the
 FCODE rom i believe.
 
 The detailed output of lspci -vvv attached.
 Note, i have disabled msi interrupts for now, but by default, it will be used.
 
 By my understanding, the msi address is :   Data: .
 
 This is an invalid configuration? Correct?

 If possible, can the nouveau driver do a sanity check for invalid msi address
 configurations before enabling msi interrupts?
[...]

The kernel will set the MSI address and data before enabling MSI.  So
looking at them while MSI is disabled tells us nothing.

What is going wrong when MSI is enabled?

The attached patch would blacklist this GPU for MSI; does it fix the pr
oblem for you?  (Instructions for testing this are at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.)

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

From: Ben Hutchings b...@decadent.org.uk
Date: Mon, 06 Jul 2015 01:24:37 +0100
Subject: nouveau: Disable MSI on G70 (NV47)
Bug-Debian: https://bugs.debian.org/790694

Peter Saisanas reported that MSI did not work properly on his Quadro
FX 4500 in a PowerMac.  Assuming this is a general problem with this
GPU type, disable MSI.

References: https://bugs.debian.org/790694
Reported-by: Peter Saisanas psaisa...@gmail.com
---
--- a/drivers/gpu/drm/nouveau/Makefile
+++ b/drivers/gpu/drm/nouveau/Makefile
@@ -155,6 +155,7 @@ nouveau-y += core/subdev/mc/base.o
 nouveau-y += core/subdev/mc/nv04.o
 nouveau-y += core/subdev/mc/nv40.o
 nouveau-y += core/subdev/mc/nv44.o
+nouveau-y += core/subdev/mc/nv47.o
 nouveau-y += core/subdev/mc/nv4c.o
 nouveau-y += core/subdev/mc/nv50.o
 nouveau-y += core/subdev/mc/nv94.o
--- a/drivers/gpu/drm/nouveau/core/engine/device/nv40.c
+++ b/drivers/gpu/drm/nouveau/core/engine/device/nv40.c
@@ -173,7 +173,7 @@ nv40_identify(struct nouveau_device *dev
 		device-oclass[NVDEV_SUBDEV_CLOCK  ] = nv40_clock_oclass;
 		device-oclass[NVDEV_SUBDEV_THERM  ] = nv40_therm_oclass;
 		device-oclass[NVDEV_SUBDEV_DEVINIT] =  nv1a_devinit_oclass;
-		device-oclass[NVDEV_SUBDEV_MC ] =  nv40_mc_oclass;
+		device-oclass[NVDEV_SUBDEV_MC ] =  nv47_mc_oclass;
 		device-oclass[NVDEV_SUBDEV_BUS] =  nv31_bus_oclass;
 		device-oclass[NVDEV_SUBDEV_TIMER  ] = nv04_timer_oclass;
 		device-oclass[NVDEV_SUBDEV_FB ] =  nv47_fb_oclass;
--- a/drivers/gpu/drm/nouveau/core/include/subdev/mc.h
+++ b/drivers/gpu/drm/nouveau/core/include/subdev/mc.h
@@ -48,6 +48,7 @@ struct nouveau_mc_oclass {
 extern struct nouveau_oclass *nv04_mc_oclass;
 extern struct nouveau_oclass *nv40_mc_oclass;
 extern struct nouveau_oclass *nv44_mc_oclass;
+extern struct nouveau_oclass *nv47_mc_oclass;
 extern struct nouveau_oclass *nv4c_mc_oclass;
 extern struct nouveau_oclass *nv50_mc_oclass;
 extern struct nouveau_oclass *nv94_mc_oclass;
--- /dev/null
+++ b/drivers/gpu/drm/nouveau/core/subdev/mc/nv47.c
@@ -0,0 +1,38 @@
+/*
+ * Copyright 2012 Red Hat Inc.
+ * Copyright 2015 Ben Hutchings
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a
+ * copy of this software and associated documentation files (the Software),
+ * to deal in the Software without restriction, including without limitation
+ * the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ * and/or sell copies of the Software, and to permit persons to whom the
+ * Software is furnished to do so, subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice shall be included in
+ * all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
+ * THE COPYRIGHT HOLDER(S) OR AUTHOR(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR
+ * OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
+ * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+ * OTHER DEALINGS IN THE SOFTWARE.
+ *
+ * Authors: Ben Skeggs, Ben Hutchings
+ */
+

Bug#790694: linux-image-3.16.0-4-powerpc64: nouveau driver and msi interrupts

2015-07-05 Thread Peter Saisanas
Hi Ben,
Thanks for this, ill give it a go as soon as i get a chance.
I'd say msi interrupts are fine on x86 with this class of gpu, but with
powerpc or this particular config it may be a problem.
I can give you the output of lspci -vvv when running with msi enabled on
this particular GPU.
It would just hang when starting xorg.
When running /cat/proc/interrupts with msi enabled, it would show only one
interrupt triggered on whatever cpu and hang the gpu if i recall.
Strangely enough, msi interrupts on powerpc seem to work fine just with the
nouveau console framebuffer...
If i recall, even with msi enabled, the msi address was still 0x0. But i
will send you a log for your reference.

Yes, and i am configuring kernel with 4kb kernel pagesize as there still
seems to be an issue with 64kb kernel pagesizes and nouveau.

Thanks Ben,

Best Regards,
Peter

On Mon, Jul 6, 2015 at 10:39 AM, Ben Hutchings b...@decadent.org.uk wrote:

 Actually this much simpler patch should do the trick; please test this
 instead.

 Ben.

 --
 Ben Hutchings
 If you seem to know what you are doing, you'll be given more to do.




Bug#748577: marked as done (arch/x86/tools/relocs.c per_cpu_load_addr missing static)

2015-07-05 Thread Debian Bug Tracking System
Your message dated Mon, 06 Jul 2015 02:51:22 +0100
with message-id 1436147482.7337.73.ca...@decadent.org.uk
and subject line Re: arch/x86/tools/relocs.c per_cpu_load_addr missing static
has caused the Debian Bug report #748577,
regarding arch/x86/tools/relocs.c per_cpu_load_addr missing static
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.)


-- 
748577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux
Version: 3.14.4-1
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error. Please note that we
use our research compiler tool-chain (using tools from the cbmc package), which
permits extended reporting on type inconsistencies at link time.

[...]
  HOSTCC  arch/x86/tools/relocs_32.o
  HOSTCC  arch/x86/tools/relocs_64.o
  HOSTCC  arch/x86/tools/relocs_common.o
  HOSTLD  arch/x86/tools/relocs

file 
/srv/jenkins-slave/workspace/sid-goto-cc-linux/linux-3.14.4/arch/x86/tools/relocs.c
 line 698: error: conflicting types for variable per_cpu_load_addr
old definition in module relocs_32 file 
/srv/jenkins-slave/workspace/sid-goto-cc-linux/linux-3.14.4/arch/x86/tools/relocs.c
 line 698
unsigned int
new definition in module relocs_64 file 
/srv/jenkins-slave/workspace/sid-goto-cc-linux/linux-3.14.4/arch/x86/tools/relocs.c
 line 698
unsigned long int
scripts/Makefile.host:127: recipe for target 'arch/x86/tools/relocs' failed
make[6]: *** [arch/x86/tools/relocs] Error 64
/srv/jenkins-slave/workspace/sid-goto-cc-linux/linux-3.14.4/arch/x86/Makefile:179:
 recipe for target 'archscripts' failed
make[5]: *** [archscripts] Error 2

Unlike other variables in relocs.c, per_cpu_load_addr is not marked static:

http://sources.debian.net/src/linux/3.11.8-1/arch/x86/tools/relocs.c?hl=698#L698

As, however, the type used in its declaration is different for
relocs_32/relocs_64, a type conflict (of the thus duplicate definition) arises.
The standard linker will pick either of the two definitions, possibly resulting
in the 32 bit (unsigned int) version being used, which would cause arbitrary
values to be overwritten when assigning to per_cpu_load_addr in a 64 bit
context.

Best,
Michael



pgpmnfmvj3O_Z.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Version: 3.18-1~exp1

My patch was applied upstream in 3.18.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.



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


Bug#790694: linux-image-3.16.0-4-powerpc64: nouveau driver and msi interrupts

2015-07-05 Thread Ben Hutchings
On Mon, 2015-07-06 at 10:57 +1000, Peter Saisanas wrote:
 Hi Ben,
 Thanks for this, ill give it a go as soon as i get a chance.
 I'd say msi interrupts are fine on x86 with this class of gpu, but 
 with powerpc or this particular config it may be a problem.

I asked upstream and was told MSIs should work on this PowerMac.

 I can give you the output of lspci -vvv when running with msi enabled 
 on this particular GPU.
 It would just hang when starting xorg.
 When running /cat/proc/interrupts with msi enabled, it would show 
 only one interrupt triggered on whatever cpu and hang the gpu if i 
 recall.
 Strangely enough, msi interrupts on powerpc seem to work fine just 
 with the nouveau console framebuffer...

The driver possibly doesn't ever need to wait for interrupts when writi
ng text to the console.

 If i recall, even with msi enabled, the msi address was still 0x0. 
 But i will send you a log for your reference.

 Yes, and i am configuring kernel with 4kb kernel pagesize as there 
 still seems to be an issue with 64kb kernel pagesizes and nouveau.

I saw that bug report as well.  I'm not sure what to do about it -
other distributions were also using 64K pages for 64-bit PowerPC the
last time I looked, and there may be good reasons to do that.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.



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