[PATCH] [arm64] including missing headers

[Ricardo Salveti]

Including missing arm header references from the arm64 headers:
asm/opcodes.h:#include <../../arm/include/asm/opcodes.h>
asm/xen/hypervisor.h:#include <../../arm/include/asm/xen/hypervisor.h>
asm/xen/page.h:#include <../../arm/include/asm/xen/page.h>
asm/xen/page-coherent.h:#include <../../arm/include/asm/xen/page-coherent.h>
asm/xen/hypercall.h:#include <../../arm/include/asm/xen/hypercall.h>
asm/xen/interface.h:#include <../../arm/include/asm/xen/interface.h>

Signed-off-by: Ricardo Salveti 
---
 debian/rules.real | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/debian/rules.real b/debian/rules.real
index c9b44a2..e6d3ace 100644
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -269,6 +269,17 @@ install-headers_$(ARCH)_$(FEATURESET): 
$(STAMPS_DIR)/source_$(FEATURESET)
) \
| \
cpio -pd --preserve-modification-time '$(CURDIR)/$(DIR)'
+# arm64 headers references arch/arm
+ifneq ($(filter arm64,$(ARCH)),)
+   set -o pipefail; \
+   cd $(SOURCE_DIR); \
+   ( \
+ find arch/arm/include -name 'opcodes.h' -print; \
+ find $$(find arch/arm/include -name xen -type d -print) -print; \
+   ) \
+   | \
+   cpio -pd --preserve-modification-time '$(CURDIR)/$(DIR)'
+endif
 
dh_link /usr/lib/$(PACKAGE_NAME_KBUILD)/scripts $(BASE_DIR)/scripts
 
-- 
2.7.4

Bug#821761: linux-image-4.5.0-1-amd64: [regression] switching from gdm Xorg vt to normal virtual console corrupts display until reboot

[Paul Wise]

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

When I upgraded to linux 4.5.1 I found that switching from a gdm Xorg
vt to normal virtual console corrupts the display until I reboot. The
display corruption is not static and is mostly black with some fuzz
around the sides and sometimes pixels from the gdm vt are in the top of
the display. This happens both with and without an external display
plugged into the VGA port on the laptop. This does not happen with 4.4
but it does happen with 4.6 from experimental. I couldn't find any way
to work around this issue other than a reboot.

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

** Model information
sys_vendor: LENOVO
product_name: 0831CTO
product_version: ThinkPad X201 Tablet
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: 6QET62WW (1.32 )
board_vendor: LENOVO
board_name: 0831CTO
board_version: Not Available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller 
[8086:0044] (rev 02)
Subsystem: Lenovo Core Processor DRAM Controller [17aa:2193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor 
Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA 
controller])
Subsystem: Lenovo Core Processor Integrated Graphics Controller 
[17aa:215a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF 
Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Lenovo 5 Series/3400 Series Chipset PCI 
Express Root Port 1 [17aa:2164]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 5 [8086:3b4a] (rev 06) (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-

Re: Bug#821442: schroot: operation not permitted (only with 4.5 kernel)

[Barry Warsaw]

On Apr 18, 2016, at 09:40 PM, James McCoy wrote:

>I've been seeing something similar.  Am I right to assume that these are
>union-type=overlay?  If so, this seems to be a change in the kernel.

Yep, union-type=overlay.


pgpyziTxZW8nO.pgp
Description: OpenPGP digital signature

Re: Bug#821442: schroot: operation not permitted (only with 4.5 kernel)

[James McCoy]

On Mon, Apr 18, 2016 at 02:14:58PM -0400, Barry Warsaw wrote:
> With today's dist-upgrade, I am unable to enter an existing or newly
> created chroot, nor am I able to sbuild or adt-run with the chroot.
> 
> I had an existing sid-amd64 chroot which I could not enter.  I then
> removed the chroot and recreated it with mk-sbuild.  Now I get:
> 
> % schroot -u root -c sid-amd64
> E: 15binfmt: update-binfmts: unable to open
> /var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/bin/sh:
> Operation not permitted
> E: 20copyfiles: cp: cannot create regular file
> '/var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/etc/resolv.conf':
> Operation not permitted
> E: 15binfmt: update-binfmts: unable to open
> /var/run/schroot/mount/sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9/bin/sh:
> Operation not permitted
> E: sid-amd64-98db94f4-3bc6-4948-95a6-57a8e986bba9: Chroot setup
> failed: stage=setup-start

I've been seeing something similar.  Am I right to assume that these are
union-type=overlay?  If so, this seems to be a change in the kernel.

Running linux-image-4.5.0-1-amd64, I see various failures using overlay
but rebooting into linux-image-4.4.0-1-amd64 I am again able to use
schroot/sbuild.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Bug#821741: linux-perf-4.6: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/perf-tip/tips.txt

[Andreas Beckmann]

Package: linux-perf-4.6
Version: 4.6~rc3-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package linux-perf-4.6.
  Preparing to unpack .../linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb ...
  Unpacking linux-perf-4.6 (4.6~rc3-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/doc/perf-tip/tips.txt', which is also in 
package linux-perf-4.5 4.5.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb


cheers,

Andreas


linux-perf-4.5=4.5.1-1_linux-perf-4.6=4.6~rc3-1~exp1.log.gz
Description: application/gzip

Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied

[Ben Hutchings]

On Mon, 2016-04-18 at 14:57 -0400, Daniel Kahn Gillmor wrote:
> Version: 20160110-1
> 
> Thanks for the quick response, Ben.
> 
> On Mon 2016-04-18 09:49:27 -0400, Ben Hutchings wrote:
> > 
> > > 
> > > It looks to me like the brcmfmac_sdio kernel module is expecting this
> > > .txt file is supposed to be shipped alongside the .bin, but it isn't
> > > present.
> > That's board-specific configuration, not really firmware.  I don't know
> > where you're supposed to get it from.
> hm, https://wiki.debian.org/InstallingDebianOn/Asus/X205TA#WiFi
> suggests:
> 
>    cp /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 
> /lib/firmware/brcm/brcmfmac43340-sdio.txt
> 
> and indeed, after doing that, and then removing and re-loading the
> kernel module with:
> 
>  modprobe -v -r brcmfmac
>  modprobe -v brcmfmac
> 
> then the device is found correctly.

Ah, I dimly remembered that this information could be stashed in the
system firmware somewhere.  It seems like the driver ought to look
there first if EFI support is enabled (there is an in-kernel API for
reading EFI variables).  That will have to be developed upstream
though.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

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

Bug#821400: marked as done (firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied)

[Debian Bug Tracking System]

Your message dated Mon, 18 Apr 2016 14:57:57 -0400
with message-id <87fuui68y2@alice.fifthhorseman.net>
and subject line Re: Bug#821400: firmware-brcm80211: brcmfmac_sdio wants 
brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied
has caused the Debian Bug report #821400,
regarding firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin 
and .txt, only .bin supplied
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.)


-- 
821400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-brcm80211
Version: 20160110-1
Severity: normal

On an Asus X205T, dmesg says:

brcmfmac_sdio mmc1:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43340-sdio.bin
brcmfmac_sdio mmc1:0001:1: firmware: failed to load brcm/brcmfmac43340-sdio.txt 
(-2)
brcmfmac_sdio mmc1:0001:1: firmware: Direct firmware load for 
brcm/brcmfmac43340-sdio.txt failed with error -2
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50

and no network interface appears for the device.

It looks to me like the brcmfmac_sdio kernel module is expecting this
.txt file is supposed to be shipped alongside the .bin, but it isn't
present.

--dkg


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

Kernel: Linux 4.4.0-1-amd64 (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)
--- End Message ---
--- Begin Message ---
Version: 20160110-1

Thanks for the quick response, Ben.

On Mon 2016-04-18 09:49:27 -0400, Ben Hutchings wrote:
>> It looks to me like the brcmfmac_sdio kernel module is expecting this
>> .txt file is supposed to be shipped alongside the .bin, but it isn't
>> present.
>
> That's board-specific configuration, not really firmware.  I don't know
> where you're supposed to get it from.

hm, https://wiki.debian.org/InstallingDebianOn/Asus/X205TA#WiFi
suggests:

   cp /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 
/lib/firmware/brcm/brcmfmac43340-sdio.txt

and indeed, after doing that, and then removing and re-loading the
kernel module with:

 modprobe -v -r brcmfmac
 modprobe -v brcmfmac

then the device is found correctly.

 --dkg--- End Message ---

Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied

[Daniel Kahn Gillmor]

Version: 20160110-1

Thanks for the quick response, Ben.

On Mon 2016-04-18 09:49:27 -0400, Ben Hutchings wrote:
>> It looks to me like the brcmfmac_sdio kernel module is expecting this
>> .txt file is supposed to be shipped alongside the .bin, but it isn't
>> present.
>
> That's board-specific configuration, not really firmware.  I don't know
> where you're supposed to get it from.

hm, https://wiki.debian.org/InstallingDebianOn/Asus/X205TA#WiFi
suggests:

   cp /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 
/lib/firmware/brcm/brcmfmac43340-sdio.txt

and indeed, after doing that, and then removing and re-loading the
kernel module with:

 modprobe -v -r brcmfmac
 modprobe -v brcmfmac

then the device is found correctly.

 --dkg

Processed: Re: Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wontfix
Bug #821400 [firmware-brcm80211] firmware-brcm80211: brcmfmac_sdio wants 
brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied
Added tag(s) wontfix.

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

Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied

[Ben Hutchings]

Control: tag -1 wontfix

On Mon, 2016-04-18 at 09:22 -0400, Daniel Kahn Gillmor wrote:
> Package: firmware-brcm80211
> Version: 20160110-1
> Severity: normal
> 
> On an Asus X205T, dmesg says:
> 
> brcmfmac_sdio mmc1:0001:1: firmware: direct-loading firmware 
> brcm/brcmfmac43340-sdio.bin
> brcmfmac_sdio mmc1:0001:1: firmware: failed to load 
> brcm/brcmfmac43340-sdio.txt (-2)
> brcmfmac_sdio mmc1:0001:1: firmware: Direct firmware load for 
> brcm/brcmfmac43340-sdio.txt failed with error -2
> brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
> brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
> 
> and no network interface appears for the device.
> 
> It looks to me like the brcmfmac_sdio kernel module is expecting this
> .txt file is supposed to be shipped alongside the .bin, but it isn't
> present.

That's board-specific configuration, not really firmware.  I don't know
where you're supposed to get it from.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

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

Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied

[Daniel Kahn Gillmor]

Package: firmware-brcm80211
Version: 20160110-1
Severity: normal

On an Asus X205T, dmesg says:

brcmfmac_sdio mmc1:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac43340-sdio.bin
brcmfmac_sdio mmc1:0001:1: firmware: failed to load brcm/brcmfmac43340-sdio.txt 
(-2)
brcmfmac_sdio mmc1:0001:1: firmware: Direct firmware load for 
brcm/brcmfmac43340-sdio.txt failed with error -2
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50

and no network interface appears for the device.

It looks to me like the brcmfmac_sdio kernel module is expecting this
.txt file is supposed to be shipped alongside the .bin, but it isn't
present.

--dkg


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

Kernel: Linux 4.4.0-1-amd64 (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#821371: linux-image-4.4.0-0.bpo.1-686-pae: Intel i915 : xrandr -s does hang the kernel

[rpnpif]

Package: src:linux
Version: 4.4.6-1~bpo8+1
Severity: normal

Dear Maintainer,

Each time that I run "xrandr -s 800x600" or "xrandr -s 1024x600", syslog logs
debug messages saying about issues of the kernel (see below).
No other effects out of this log.
xrandr seems to work fine.

$ xrandr
Screen 0: minimum 8 x 8, current 1024 x 600, maximum 32767 x 32767
LVDS1 connected 1024x600+0+0 (normal left inverted right x axis y axis) 195mm x 
113mm
   1024x600  60.00*+
   800x600   60.3256.25  
   640x480   59.94  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


-- Package-specific info:
** Version:
Linux version 4.4.0-0.bpo.1-686-pae (debian-kernel@lists.debian.org) (gcc 
version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.4.0-0.bpo.1-686-pae 
root=UUID=2ed3bc82-5cc0-4529-a13c-2e6f80b5b588 ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[ 2022.347925]  [] ? intel_atomic_commit+0xae1/0x12d0 [i915]
[ 2022.347971]  [] ? drm_atomic_check_only+0x2b5/0x650 [drm]
[ 2022.348012]  [] ? drm_modeset_lock+0x33/0xf0 [drm]
[ 2022.348052]  [] ? drm_atomic_set_crtc_for_connector+0x1d/0xa0 [drm]
[ 2022.348094]  [] ? drm_atomic_commit+0x32/0x60 [drm]
[ 2022.348118]  [] ? drm_atomic_helper_set_config+0x62/0xa0 
[drm_kms_helper]
[ 2022.348161]  [] ? drm_mode_set_config_internal+0x4e/0xc0 [drm]
[ 2022.348203]  [] ? drm_mode_setcrtc+0x1a4/0x570 [drm]
[ 2022.348247]  [] ? drm_mode_setplane+0x1d0/0x1d0 [drm]
[ 2022.348285]  [] ? drm_ioctl+0x14c/0x510 [drm]
[ 2022.348302]  [] ? fsnotify_destroy_event+0x27/0x50
[ 2022.348316]  [] ? fsnotify_destroy_event+0x27/0x50
[ 2022.348358]  [] ? drm_mode_setplane+0x1d0/0x1d0 [drm]
[ 2022.348401]  [] ? drm_getmap+0xc0/0xc0 [drm]
[ 2022.348415]  [] ? do_vfs_ioctl+0x322/0x550
[ 2022.348427]  [] ? dput+0xb7/0x210
[ 2022.348441]  [] ? __fsnotify_parent+0x96/0x100
[ 2022.348456]  [] ? vfs_write+0x150/0x1b0
[ 2022.348470]  [] ? SyS_ioctl+0x60/0x90
[ 2022.348485]  [] ? do_fast_syscall_32+0x93/0x220
[ 2022.348501]  [] ? sysenter_past_esp+0x3d/0x61
[ 2022.348545] ---[ end trace 10505acfd6e5984f ]---
[ 2029.524389] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
gmch_pfit.lvds_border_bits (expected 0x8000, found 0x)
[ 2029.524408] [ cut here ]
[ 2029.524519] WARNING: CPU: 0 PID: 641 at 
/home/zumbi/linux-4.4.6/drivers/gpu/drm/i915/intel_display.c:12812 
intel_atomic_commit+0xae1/0x12d0 [i915]()
[ 2029.524527] pipe state doesn't match!
[ 2029.524534] Modules linked in: sha256_generic hmac drbg ansi_cprng ctr ccm 
binfmt_misc iTCO_wdt iTCO_vendor_support arc4 uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media 
rt2800pci rt2800mmio rt2800lib rt2x00pci rt2x00mmio rt2x00lib eeprom_93cx6 
mac80211 coretemp evdev joydev i915 pcspkr cfg80211 serio_raw lpc_ich mfd_core 
eeepc_laptop crc_ccitt sparse_keymap i2c_i801 rfkill snd_hda_codec_realtek 
snd_hda_codec_generic rng_core snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep drm_kms_helper snd_pcm acpi_cpufreq tpm_tis snd_timer snd soundcore 
drm video i2c_algo_bit tpm battery ac shpchp button processor loop fuse 
parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 sg sd_mod 
ata_generic psmouse ata_piix libata scsi_mod ehci_pci uhci_hcd ehci_hcd
[ 2029.524782]  usbcore usb_common thermal atl1e
[ 2029.524808] CPU: 0 PID: 641 Comm: Xorg Tainted: GW   
4.4.0-0.bpo.1-686-pae #1 Debian 4.4.6-1~bpo8+1
[ 2029.524816] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 2103
06/11/2009
[ 2029.524826]  00203286 af31f475 f4a01c98 c12ba29c f4a01ca8  c106b5c1 
f8a5dbca
[ 2029.524851]  f4a01cc8 0281 f8a4f190 320c f89ef9f1 0009 320c 
f89ef9f1
[ 2029.524875]  f4a1a800 f51e5c00 f3d0 f4a01cb4 c106b62e 0009 f4a01ca8 
f8a5dbca
[ 2029.524898] Call Trace:
[ 2029.524921]  [] ? dump_stack+0x55/0x79
[ 2029.524938]  [] ? warn_slowpath_common+0x91/0xc0
[ 2029.525047]  [] ? intel_atomic_commit+0xae1/0x12d0 [i915]
[ 2029.525153]  [] ? intel_atomic_commit+0xae1/0x12d0 [i915]
[ 2029.525167]  [] ? warn_slowpath_fmt+0x3e/0x60
[ 2029.525274]  [] ? intel_atomic_commit+0xae1/0x12d0 [i915]
[ 2029.525320]  [] ? drm_atomic_check_only+0x2b5/0x650 [drm]
[ 2029.525361]  [] ? drm_modeset_lock+0x33/0xf0 [drm]
[ 2029.525402]  [] ? drm_atomic_set_crtc_for_connector+0x1d/0xa0 [drm]
[ 2029.525443]  [] ? drm_atomic_commit+0x32/0x60 [drm]
[ 2029.525468]  [] ? drm_atomic_helper_set_config+0x62/0xa0 
[drm_kms_helper]
[ 2029.525511]  [] ? drm_mode_set_config_internal+0x4e/0xc0 [drm]
[ 2029.525553]  [] ? drm_mode_setcrtc+0x1a4/0x570 [drm]
[ 2029.525598]  [] ? drm_mode_setplane+0x1d0/0x1d0 [drm]
[ 2029.525636]  [] ? drm_ioctl+0x14c/0x510 [drm]
[ 2029.525652]  [] ? fsnotify_destroy_event+0x27/0x50
[ 2029.525666]  [] ? fsnotify_destroy_event+0x27/0x50
[ 2029.525709]  [] ? 

Processed: Re: Suspend on iBook G3 (A1007) no longer works

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #697606 [src:linux] linux-image-3.2.0-4-powerpc: Suspend on iBook G3 
(A1007) no longer works
Bug #715546 [src:linux] linux-image-3.9-1-powerpc: Suspend fails on iBook G3 
Dual USB PowerPC
Added tag(s) confirmed.
Added tag(s) confirmed.

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

Bug#697606: Suspend on iBook G3 (A1007) no longer works

[Mathieu Malaterre]

Control: tags -1 confirmed

On Mon, Apr 18, 2016 at 7:49 AM, Kristen  wrote:
> On 4/12/16 4:10 AM, Mathieu Malaterre wrote:
>> Hi,
>>
>> Since the OP of #697606 does not have the hardware anymore, I am
>> thinking of closing the bug report.
>>
>> Does anyone have access to an iBook G3 and wants to update the bug ?
>>
>> thx
>>
>
> I just preformed an install of Jessie with the 3.16.7-ckt25-1 kernel. I
> find that suspend gives indications of working.

ok, taggind as confirmed.

> However very little else appears to work. I do not have networking, I do
> not receive a login screen (lightDM), and I can not start X. I am not
> sure if anything works other then a virtual terminal. Perhaps this
> taints the results some.

Could you run some comparison with ubuntu ppc:

https://wiki.ubuntu.com/PowerPCDownloads

The only way to solve this situation is to solve the issue one by one
(network and X at least).

Once you are confident with one issue (say network), please do a open
a new bug report (CC me).

Thanks.

Bug#697606: Suspend on iBook G3 (A1007) no longer works

[Kristen]

On 4/12/16 4:10 AM, Mathieu Malaterre wrote:
> Hi,
> 
> Since the OP of #697606 does not have the hardware anymore, I am
> thinking of closing the bug report.
> 
> Does anyone have access to an iBook G3 and wants to update the bug ?
> 
> thx
> 

I just preformed an install of Jessie with the 3.16.7-ckt25-1 kernel. I
find that suspend gives indications of working.

However very little else appears to work. I do not have networking, I do
not receive a login screen (lightDM), and I can not start X. I am not
sure if anything works other then a virtual terminal. Perhaps this
taints the results some.

Kristen




signature.asc
Description: OpenPGP digital signature