Bug#747364: linux: [armhf/armmp] Enable support for BeagleBone Black

2014-05-08 Thread Vagrant Cascadian 
On Fri, May 09, 2014 at 03:17:28AM +0100, Ben Hutchings wrote:
> On Wed, 2014-05-07 at 18:10 -0700, Vagrant Cascadian wrote:
> > On Wed, May 07, 2014 at 01:46:53PM -0700, Vagrant Cascadian wrote:
> > USB support seems flaky, at best... not sure if there are other options that
> > could improve that.
> 
> I think that's because the MUSB driver can only be built with support
> for one type of DMA controller, and so doesn't support DMA at all in
> multiplatform kernels.

hrm. That doesn't sound promising...


> >  CONFIG_DMA_OMAP=y
> > +CONFIG_TI_CPPI41=y
> 
> Why not =m?

Updated to use =m.


> > +CONFIG_I2C_CHARDEV=y
> 
> This symbol seems to be enabled in most configurations that have I2C,
> but often as a module. 

Updated to use =m.


> > +CONFIG_SERIAL_OF_PLATFORM=y

Removed.

Also removed the various DEVFREQ entries; there were no enabled drivers, just
governors...


diff --git a/config/armhf/config.armmp b/config/armhf/config.armmp
index c43f74e..d9b2308 100644
--- a/config/armhf/config.armmp
+++ b/config/armhf/config.armmp
@@ -136,6 +136,12 @@ CONFIG_OMAP_OCP2SCP=m
 CONFIG_OMAP_INTERCONNECT=m
 
 ##
+## file: drivers/char/hw_random/Kconfig
+##
+CONFIG_HW_RANDOM=m
+CONFIG_HW_RANDOM_OMAP=m
+
+##
 ## file: drivers/clk/Kconfig
 ##
 CONFIG_CLK_TWL6040=m
@@ -170,6 +176,8 @@ CONFIG_IMX_SDMA=y
 CONFIG_IMX_DMA=y
 CONFIG_MXS_DMA=y
 CONFIG_DMA_OMAP=y
+CONFIG_TI_CPPI41=m
+CONFIG_TI_EDMA=y
 
 ##
 ## file: drivers/gpio/Kconfig
@@ -178,6 +186,22 @@ CONFIG_GPIO_SYSFS=y
 CONFIG_GPIO_DA9052=m
 CONFIG_GPIO_TWL4030=y
 CONFIG_GPIO_TWL6040=y
+CONFIG_GPIO_GENERIC_PLATFORM=m
+
+##
+## file: drivers/gpu/drm/Kconfig
+##
+CONFIG_DRM=m
+
+##
+## file: drivers/gpu/drm/i2c/Kconfig
+##
+CONFIG_DRM_I2C_NXP_TDA998X=m
+
+##
+## file: drivers/gpu/drm/tilcdc/Kconfig
+##
+CONFIG_DRM_TILCDC=m
 
 ##
 ## file: drivers/hwspinlock/Kconfig
@@ -185,6 +209,11 @@ CONFIG_GPIO_TWL6040=y
 CONFIG_HWSPINLOCK_OMAP=m
 
 ##
+## file: drivers/i2c/Kconfig
+##
+CONFIG_I2C_CHARDEV=m
+
+##
 ## file: drivers/i2c/busses/Kconfig
 ##
 CONFIG_I2C_GPIO=y
@@ -199,6 +228,11 @@ CONFIG_I2C_VERSATILE=m
 CONFIG_IIO=m
 
 ##
+## file: drivers/iio/adc/Kconfig
+##
+CONFIG_TI_AM335X_ADC=m
+
+##
 ## file: drivers/iio/light/Kconfig
 ##
 CONFIG_SENSORS_TSL2563=m
@@ -229,6 +263,7 @@ CONFIG_SERIO_AMBAKMI=m
 ##
 CONFIG_INPUT_TOUCHSCREEN=y
 CONFIG_TOUCHSCREEN_TSC2005=m
+CONFIG_TOUCHSCREEN_TI_AM335X_TSC=m
 
 ##
 ## file: drivers/iommu/Kconfig
@@ -491,6 +526,11 @@ CONFIG_WLCORE_SDIO=m
 CONFIG_PHY_SUN4I_USB=m
 
 ##
+## file: drivers/pinctrl/Kconfig
+##
+CONFIG_PINCTRL_SINGLE=y
+
+##
 ## file: drivers/pinctrl/vt8500/Kconfig
 ##
 CONFIG_PINCTRL_WM8850=y
@@ -592,6 +632,8 @@ CONFIG_SERIAL_VT8500_CONSOLE=y
 CONFIG_SERIAL_ARC=y
 CONFIG_SERIAL_ARC_CONSOLE=y
 CONFIG_SERIAL_ARC_NR_PORTS=1
+CONFIG_SERIAL_OMAP=y
+CONFIG_SERIAL_OMAP_CONSOLE=y
 
 ##
 ## file: drivers/tty/serial/8250/Kconfig
@@ -663,6 +705,8 @@ CONFIG_OMAP_USB3=m
 CONFIG_TWL4030_USB=m
 CONFIG_TWL6030_USB=m
 CONFIG_USB_MXS_PHY=m
+CONFIG_AM335X_CONTROL_USB=m
+CONFIG_AM335X_PHY_USB=m
 
 ##
 ## file: drivers/video/Kconfig


live well,
  vagrant


signature.asc
Description: Digital signature

Bug#747467: linux-image-3.14-1-amd64: backlight control broken on dell xps13

2014-05-08 Thread Jan De Luyck 
Package: src:linux
Version: 3.14.2-1
Severity: normal
Tags: patch

Dear Maintainer,

Hello,

Kernel 3.14 contains a regression wrt backlight control on the Dell XPS13
laptops.
Details can be found on http://bugs.freedesktop.org/show_bug.cgi?id=76276

That bugzilla link also contains fixes: either revert a change or apply
another patch on top.

Would it be possible to consider either for 3.14?

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

** Model information
sys_vendor: Dell Inc.
product_name: XPS L322X
product_version:
chassis_vendor: Dell Inc.
chassis_version: 0.1
bios_vendor: Dell Inc.
bios_version: A10
board_vendor: Dell Inc.
board_name: 0WW7PG
board_version: A00

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM
Controller [8086:0154] (rev 09)
Subsystem: Dell Device [1028:058b]
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 3rd Gen Core
processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA
controller])
Subsystem: Dell Device [1028:058b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915

00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30
[XHCI])
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: xhci_hcd

00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210
Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
(prog-if 20 [EHCI])
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: ehci-pci

00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset
Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset
Family PCI Express Root Port 1 [8086:1e10] (rev c4) (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: 
Kernel driver in use: pcieport

00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
(prog-if 20 [EHCI])
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: ehci-pci

00:1f.0 ISA bridge [0601]: Intel Corporation QS77 Express Chipset LPC
Controller [8086:1e56] (rev 04)
Subsystem: Dell Device [1028:058b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: lpc_ich

00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family
6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) (prog-if 01 [AHCI
1.0])
Subsystem: Dell Device [1028:058b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family
SMBus Controller [8086:1e22] (rev 04)
Subsystem: Dell Device [1028:058b]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisIN

Bug#734003: linux-image-3.13-rc6-amd64: Display manager fails to start, Intel graphics driver not loaded/used, brightness conrtols reversed

2014-05-08 Thread Matteo Cypriani 
On Thu, 08 May 2014 23:00:51 -0400, Alex Vanderpol 
wrote:
> I had been running the 3.14-trunk from experimental for a while before 
> the 3.14 image in sid was available, neither version had any issues.

OK, if you don't know which one exactly, let's leave it that way.


pgpNDRfDl4GGQ.pgp
Description: PGP signature

Bug#734003: marked as done (linux-image-3.13-rc6-amd64: Display manager fails to start, Intel graphics driver not loaded/used, brightness conrtols reversed)

2014-05-08 Thread Debian Bug Tracking System 
Your message dated Thu, 8 May 2014 22:58:23 -0400
with message-id <20140508225823.8cc8eed175be6495e76f3...@lm7.fr>
and subject line Re: linux-image-3.13-rc6-amd64: Display manager fails to 
start, Intel graphics driver not loaded/used, brightness conrtols reversed
has caused the Debian Bug report #734003,
regarding linux-image-3.13-rc6-amd64: Display manager fails to start, Intel 
graphics driver not loaded/used, brightness conrtols reversed
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.)


-- 
734003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.13~rc6-1~exp1
Severity: important

Dear Maintainer,

This package (version 3.13~rc6-1~exp1) is exhibiting some symptoms that lead me
to believe it's buggy, namely:

1: My display manager (GDM) fails to start when the system finishes booting.
2: The Intel graphics driver does not appear to be loaded/used (possibly the
reason for #1). Instead, the driver "Gallium 0.4 on llvmpipe (LLVM 3.3, 128
bits)" is used.
3: For some reason, the brightness controls end up reversed (trying to lower
the brightness raises it, and vice-versa), causing my display to be turned off
rather than turned up to full brightness when the system finishes booting
(possibly also related to #2).

If you could please look into these matters, I would be ever so grateful. For
the time being, I shall continue to run the 3.12 kernel, which does not
experience these issues.



-- Package-specific info:
** Version:
Linux version 3.13-rc6-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.2 (Debian 4.8.2-10) ) #1 SMP Debian 3.13~rc6-1~exp1 (2013-12-30)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.13-rc6-amd64 
root=UUID=376d5c13-85a6-476a-aa9e-1be9dc19d808 ro quiet splash

** Tainted: I (2048)
 * Working around severe firmware bug.

** Kernel log:
[   10.182746] systemd[1]: Starting udev Control Socket.
[   10.182842] systemd[1]: Listening on udev Control Socket.
[   10.182930] systemd[1]: Starting udev Coldplug all Devices...
[   10.183809] systemd[1]: Starting Arbitrary Executable File Formats File 
System Automount Point.
[   10.184038] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[   10.184637] systemd[1]: Started Set Up Additional Binary Formats.
[   10.184655] systemd[1]: Starting Encrypted Volumes.
[   10.184722] systemd[1]: Reached target Encrypted Volumes.
[   10.225326] systemd[1]: Starting Apply Kernel Variables...
[   10.226160] systemd[1]: Expecting device 
dev-disk-by\x2duuid-360e320b\x2d691a\x2d4e31\x2dbcfb\x2d47b1059d7864.device...
[   10.226255] systemd[1]: Starting File System Check on Root Device...
[   10.227037] systemd[1]: Expecting device 
dev-disk-by\x2duuid-5405f114\x2de615\x2d4140\x2d8331\x2d6428d0b806d2.device...
[   10.227118] systemd[1]: Expecting device 
dev-disk-by\x2duuid-62eef65d\x2d32c0\x2d4c66\x2d81eb\x2dbcc97262b00a.device...
[   10.574194] fuse init (API version 7.22)
[   11.362490] loop: module loaded
[   11.475392] systemd-udevd[259]: starting version 204
[   13.684148] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   14.206514] cfg80211: Calling CRDA to update world regulatory domain
[   14.221595] ACPI: AC Adapter [ACAD] (off-line)
[   14.231365] ACPI: Battery Slot [BAT1] (battery present)
[   14.403692] ACPI Warning: 0x0428-0x042f SystemIO 
conflicts with Region \PMBA 1 (20131115/utaddress-251)
[   14.403703] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.403710] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \GPIO 1 (20131115/utaddress-251)
[   14.403716] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \_SB_.PCI0.LPC_.GPIO 2 (20131115/utaddress-251)
[   14.403722] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.403725] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \_SB_.PCI0.LPC_.GPIO 1 (20131115/utaddress-251)
[   14.403731] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.403733] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   14.502991] Monitor-Mwait will be used to enter C-1 state
[   14.503003] Monitor-Mwait will be used to enter C-2 state
[   14.503008] tsc: Marking TSC unstable due to TSC halts in idle
[   14.503017] ACPI: acpi_idle registered with cpuidle
[   14.503254]

Bug#734003: marked as done (linux-image-3.13-rc6-amd64: Display manager fails to start, Intel graphics driver not loaded/used, brightness conrtols reversed)

2014-05-08 Thread Debian Bug Tracking System 
Your message dated Thu, 08 May 2014 23:00:51 -0400
with message-id <536c44e3.9040...@gmail.com>
and subject line Re: linux-image-3.13-rc6-amd64: Display manager fails to 
start, Intel graphics driver not loaded/used, brightness conrtols reversed
has caused the Debian Bug report #734003,
regarding linux-image-3.13-rc6-amd64: Display manager fails to start, Intel 
graphics driver not loaded/used, brightness conrtols reversed
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.)


-- 
734003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.13~rc6-1~exp1
Severity: important

Dear Maintainer,

This package (version 3.13~rc6-1~exp1) is exhibiting some symptoms that lead me
to believe it's buggy, namely:

1: My display manager (GDM) fails to start when the system finishes booting.
2: The Intel graphics driver does not appear to be loaded/used (possibly the
reason for #1). Instead, the driver "Gallium 0.4 on llvmpipe (LLVM 3.3, 128
bits)" is used.
3: For some reason, the brightness controls end up reversed (trying to lower
the brightness raises it, and vice-versa), causing my display to be turned off
rather than turned up to full brightness when the system finishes booting
(possibly also related to #2).

If you could please look into these matters, I would be ever so grateful. For
the time being, I shall continue to run the 3.12 kernel, which does not
experience these issues.



-- Package-specific info:
** Version:
Linux version 3.13-rc6-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.2 (Debian 4.8.2-10) ) #1 SMP Debian 3.13~rc6-1~exp1 (2013-12-30)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.13-rc6-amd64 
root=UUID=376d5c13-85a6-476a-aa9e-1be9dc19d808 ro quiet splash

** Tainted: I (2048)
 * Working around severe firmware bug.

** Kernel log:
[   10.182746] systemd[1]: Starting udev Control Socket.
[   10.182842] systemd[1]: Listening on udev Control Socket.
[   10.182930] systemd[1]: Starting udev Coldplug all Devices...
[   10.183809] systemd[1]: Starting Arbitrary Executable File Formats File 
System Automount Point.
[   10.184038] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[   10.184637] systemd[1]: Started Set Up Additional Binary Formats.
[   10.184655] systemd[1]: Starting Encrypted Volumes.
[   10.184722] systemd[1]: Reached target Encrypted Volumes.
[   10.225326] systemd[1]: Starting Apply Kernel Variables...
[   10.226160] systemd[1]: Expecting device 
dev-disk-by\x2duuid-360e320b\x2d691a\x2d4e31\x2dbcfb\x2d47b1059d7864.device...
[   10.226255] systemd[1]: Starting File System Check on Root Device...
[   10.227037] systemd[1]: Expecting device 
dev-disk-by\x2duuid-5405f114\x2de615\x2d4140\x2d8331\x2d6428d0b806d2.device...
[   10.227118] systemd[1]: Expecting device 
dev-disk-by\x2duuid-62eef65d\x2d32c0\x2d4c66\x2d81eb\x2dbcc97262b00a.device...
[   10.574194] fuse init (API version 7.22)
[   11.362490] loop: module loaded
[   11.475392] systemd-udevd[259]: starting version 204
[   13.684148] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   14.206514] cfg80211: Calling CRDA to update world regulatory domain
[   14.221595] ACPI: AC Adapter [ACAD] (off-line)
[   14.231365] ACPI: Battery Slot [BAT1] (battery present)
[   14.403692] ACPI Warning: 0x0428-0x042f SystemIO 
conflicts with Region \PMBA 1 (20131115/utaddress-251)
[   14.403703] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.403710] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \GPIO 1 (20131115/utaddress-251)
[   14.403716] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \_SB_.PCI0.LPC_.GPIO 2 (20131115/utaddress-251)
[   14.403722] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.403725] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \_SB_.PCI0.LPC_.GPIO 1 (20131115/utaddress-251)
[   14.403731] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.403733] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   14.502991] Monitor-Mwait will be used to enter C-1 state
[   14.503003] Monitor-Mwait will be used to enter C-2 state
[   14.503008] tsc: Marking TSC unstable due to TSC halts in idle
[   14.503017] ACPI: acpi_idle registered with cpuidle
[   14.503254] Switched to clocks

Bug#734003: linux-image-3.13-rc6-amd64: Display manager fails to start, Intel graphics driver not loaded/used, brightness conrtols reversed

2014-05-08 Thread Alex Vanderpol 
I have not experienced either of these issues with the 3.14 kernel 
image. Brightness controls work as they should and the display manager 
loads just fine.


Thank you for your reply though.

On 2014-05-08 9:24 PM, Matteo Cypriani wrote:

Hi Alex,

On Thu, 02 Jan 2014 19:33:04 -0500, Alex Vanderpol 
wrote:

Package: src:linux
Version: 3.13~rc6-1~exp1
Severity: important

Dear Maintainer,

This package (version 3.13~rc6-1~exp1) is exhibiting some symptoms that
lead me to believe it's buggy, namely:

1: My display manager (GDM) fails to start when the system finishes booting.
2: The Intel graphics driver does not appear to be loaded/used (possibly the
reason for #1). Instead, the driver "Gallium 0.4 on llvmpipe (LLVM 3.3, 128
bits)" is used.
3: For some reason, the brightness controls end up reversed (trying to lower
the brightness raises it, and vice-versa), causing my display to be turned
off rather than turned up to full brightness when the system finishes
booting (possibly also related to #2).

Did you try reproducing this with Linux 3.14?

For your #3, you should try passing i915.invert_brightness=1 to the kernel
when booting (press E in Grub and add this at the end of the "linux" line),
it should solve the problem. I've read somewhere that if your machine requires
this you should report it, but I don't remember where so.

Hope this helps,
   Matteo



---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com


--
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/536c42a9.4020...@gmail.com

Bug#747464: linux-image-3.14-1-amd64: general protection fault when efibootmgr runs, RIP: 0010:[] [] efi_call5+0x6f/0xf0

2014-05-08 Thread James McCoy 
Package: src:linux
Version: 3.14.2-1
Severity: important

Dear Maintainer,

In the process of doing an update, a new version of grub was installed
which caused efibootmgr to run.  When that ran, the below general
protection fault occurred which eventually led to my computer completely
locking up.

May  8 21:01:54 freya kernel: [612184.434511] general protection fault:  
[#1] SMP 
May  8 21:01:54 freya kernel: [612184.434578] Modules linked in: cpuid aufs(C) 
ctr ccm rfcomm bnep uinput binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl 
nfs lockd fscache sunrpc snd_hda_codec_hdmi joydev arc4 nls_utf8 nls_cp437 vfat 
fat x86_pkg_temp_thermal intel_powerclamp iTCO_wdt iTCO_vendor_support iwlmvm 
uvcvideo intel_rapl mac80211 videobuf2_vmalloc coretemp videobuf2_memops 
psmouse efi_pstore kvm videobuf2_core iwlwifi efivars evdev 
snd_hda_codec_realtek serio_raw pcspkr videodev snd_hda_codec_generic btusb 
i2c_i801 bluetooth media 6lowpan_iphc lpc_ich mfd_core cfg80211 i915 wmi 
thinkpad_acpi nvram rfkill drm_kms_helper tpm_tis battery ac tpm drm 
snd_hda_intel i2c_algo_bit i2c_designware_platform snd_hda_codec 
i2c_designware_core snd_hwdep video snd_pcm snd_timer i2c_core mei_me snd 
button mei soundcore processor autofs4 ext4 crc16 mbcache jbd2 dm_crypt dm_mod 
sd_mod crc_t10dif crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel 
ghash_clmulni_intel ahci libahci ehci
 _pci ehci_hcd xhci_hcd aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd libata scsi_mod e1000e ptp usbcore pps_core thermal 
usb_common thermal_sys
May  8 21:01:54 freya kernel: [612184.435840] CPU: 1 PID: 13841 Comm: 
efibootmgr Tainted: GWC   3.14-1-amd64 #1 Debian 3.14.2-1
May  8 21:01:54 freya kernel: [612184.435926] Hardware name: LENOVO 
20A7CTO1WW/20A7CTO1WW, BIOS GRET30WW (1.07 ) 01/13/2014
May  8 21:01:54 freya kernel: [612184.436004] task: 880207788ca0 ti: 
88020e698000 task.ti: 88020e698000
May  8 21:01:54 freya kernel: [612184.436073] RIP: 0010:[]  
[] efi_call5+0x6f/0xf0
May  8 21:01:54 freya kernel: [612184.436158] RSP: 0018:88020e699d80  
EFLAGS: 00010002
May  8 21:01:54 freya kernel: [612184.436209] RAX: 80050033 RBX: 
8802143f9000 RCX: 8802143f9000
May  8 21:01:54 freya kernel: [612184.436276] RDX: 8802143f9400 RSI: 
8802143f9000 RDI: 211b59d57061fa5e
May  8 21:01:54 freya kernel: [612184.436342] RBP: 8802143f9400 R08: 
8802143f9820 R09: 8802143f9410
May  8 21:01:54 freya kernel: [612184.436408] R10: 7fff36e62c70 R11: 
0246 R12: 8802143f9820
May  8 21:01:54 freya kernel: [612184.436475] R13: 8802143f9410 R14: 
8802143f9418 R15: 00099000
May  8 21:01:54 freya kernel: [612184.436542] FS:  7fe9ae0c4700() 
GS:88021e24() knlGS:
May  8 21:01:54 freya kernel: [612184.436617] CS:  0010 DS:  ES:  CR0: 
80050033
May  8 21:01:54 freya kernel: [612184.436671] CR2: 7fe9ad7341a9 CR3: 
00099000 CR4: 001407e0
May  8 21:01:54 freya kernel: [612184.436738] DR0:  DR1: 
 DR2: 
May  8 21:01:54 freya kernel: [612184.436804] DR3:  DR6: 
fffe0ff0 DR7: 0400
May  8 21:01:54 freya kernel: [612184.436870] Stack:
May  8 21:01:54 freya kernel: [612184.436891]  88021d77b020 
880213223b40 88020e699e60 88021d7ef890
May  8 21:01:54 freya kernel: [612184.436973]  8802143f9418 
880213223b40 88020e699e28 80050033
May  8 21:01:54 freya kernel: [612184.437054]   
  
May  8 21:01:54 freya kernel: [612184.437134] Call Trace:
May  8 21:01:54 freya kernel: [612184.437168]  [] ? 
virt_efi_get_variable+0x3f/0x50
May  8 21:01:54 freya kernel: [612184.437245]  [] ? 
efivar_entry_get+0x3a/0x60
May  8 21:01:54 freya kernel: [612184.437308]  [] ? 
efivar_show_raw+0x3d/0x120 [efivars]
May  8 21:01:54 freya kernel: [612184.437378]  [] ? 
sysfs_kf_seq_show+0x67/0xe0
May  8 21:01:54 freya kernel: [612184.437439]  [] ? 
seq_read+0x134/0x390
May  8 21:01:54 freya kernel: [612184.437495]  [] ? 
vfs_read+0x91/0x160
May  8 21:01:54 freya kernel: [612184.437549]  [] ? 
SyS_read+0x3d/0xa0
May  8 21:01:54 freya kernel: [612184.437602]  [] ? 
system_call_fastpath+0x16/0x1b
May  8 21:01:54 freya kernel: [612184.437659] Code: 89 c8 48 89 f1 80 3d d8 b6 
7d 00 00 74 1d 4c 89 3d b7 b6 7d 00 41 0f 20 df 4c 89 3d b4 b6 7d 00 4c 8b 3d 
b5 b6 7d 00 41 0f 22 df  d7 80 3d b0 b6 7d 00 00 74 41 4c 8b 3d 97 b6 7d 00 
41 0f 22 
May  8 21:01:54 freya kernel: [612184.438011] RIP  [] 
efi_call5+0x6f/0xf0
May  8 21:01:54 freya kernel: [612184.438069]  RSP 
May  8 21:01:54 freya kernel: [612184.454587] ---[ end trace f2f3c521acb12d3c 
]---
May  8 21:01:54 freya kernel: [612205.464298] INFO: rcu_sched detected stalls 
on CPUs/tasks: { 1} (detected by 0, t=5252 jiffies, g=2467570, c=2467569, 
q=1551)
May  8 21:01:54 freya kernel: [6122

Bug#747364: linux: [armhf/armmp] Enable support for BeagleBone Black

2014-05-08 Thread Ben Hutchings 
Control: tag -1 moreinfo

On Wed, 2014-05-07 at 18:10 -0700, Vagrant Cascadian wrote:
> On Wed, May 07, 2014 at 01:46:53PM -0700, Vagrant Cascadian wrote:
> > The following patch enables configuration options needed for use with
> > BeagleBone Black.
> > 
> > Ethernet, serial console, MMC support work. Video may require some 
> > additional
> > patches from upstream...
> 
> Updated patch with support for video output as modules:
>   CONFIG_DRM_I2C_NXP_TDA998X=m
>   CONFIG_DRM_TILCDC=m
> 
> Thanks to Robert C. Nelson for the additional options!
> 
> USB support seems flaky, at best... not sure if there are other options that
> could improve that.

I think that's because the MUSB driver can only be built with support
for one type of DMA controller, and so doesn't support DMA at all in
multiplatform kernels.

> live well,
>   vagrant
> 
> diff --git a/config/armhf/config.armmp b/config/armhf/config.armmp
> index c43f74e..0ab26fc 100644
> --- a/config/armhf/config.armmp
> +++ b/config/armhf/config.armmp
[...]
> @@ -170,6 +185,8 @@ CONFIG_IMX_SDMA=y
>  CONFIG_IMX_DMA=y
>  CONFIG_MXS_DMA=y
>  CONFIG_DMA_OMAP=y
> +CONFIG_TI_CPPI41=y

Why not =m?  (It looks like this is only needed for USB anyway, which
means it's not used at all yet.)

[...]
> +## file: drivers/i2c/Kconfig
> +##
> +CONFIG_I2C_CHARDEV=y

This symbol seems to be enabled in most configurations that have I2C,
but often as a module.  When built as a module, it won't be auto-loaded,
though userland could explicitly load it if needed.

What userland programs need this, and do they try to load the module
(which will be needed in some configurations)?

[...]
> +CONFIG_SERIAL_OF_PLATFORM=y
[...]

This seems to select some glue code for 8250-like serial ports, and the
following symbols don't depend on it.

And in am33xx.dtsi, all the UARTs have compatible = "ti,omap3-uart".

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein


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

Processed: Re: Bug#747364: linux: [armhf/armmp] Enable support for BeagleBone Black

2014-05-08 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #747364 [src:linux] linux: [armhf/armmp] Enable support for BeagleBone Black
Added tag(s) moreinfo.

-- 
747364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747364
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.b747364.139960186115871.transcr...@bugs.debian.org

Bug#726463: marked as done (linux-image-3.10-3-amd64: System randomly freezes completely, needs hard reboot)

2014-05-08 Thread Debian Bug Tracking System 
Your message dated Thu, 8 May 2014 22:02:31 -0400
with message-id <20140508220231.04a5fdbb4803cf28c4bd9...@lm7.fr>
and subject line Re: linux-image-3.10-3-amd64: System randomly freezes 
completely, needs hard reboot
has caused the Debian Bug report #726463,
regarding linux-image-3.10-3-amd64: System randomly freezes completely, needs 
hard reboot
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.)


-- 
726463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.10.11-1
Severity: important

Hello kernel maintainers,

I'm experiencing random freezes on my laptop running sid with recent
kernels (3.10+, see below). It happens a couple of minutes to several
hours after booting, under no particular charge, and blocks completely
the screen, the mouse and the keyboard (no tty switching possible, no
magic keys).  It leaves no information in /var/log/{messages,syslog}.
I experienced the problem both under X11 or in text console (with xdm
stopped), although the freeze seems to take longer to appear in text
mode (?). At first I suspected the network, but I had the machine freeze
when connected to the wired network, to a Wi-Fi network, or even
completely disconnected with the interfaces down.

This machine was freshly reinstalled on wheezy in early September and
upgraded to sid right after. I still have the 3.2 kernel from wheezy
installed (linux-image-3.2.0-4-amd64 3.2.46-1+deb7u1), and the machine
is perfectly stable when I run it. When I upgraded to sid, the most
recent kernel was linux-image-3.10-2-amd64, with wich I had the problem,
and it was later upgraded to linux-image-3.10-3-amd64 (3.10.11-1) with
no improvement. I also tried the 3.11 version from experimental
(linux-image-3.11-trunk-amd64 3.11-1~exp1) and the problem is still
present. However, a 3.11.4 kernel compiled from the official sources
works perfectly, so the problem might be caused by a Debian patch.

Note that this problem is likely unrelated to #711453, since the machine
has never rebooted by itself after a freeze.

In case that matters, this system is installed on LUKS + LVM + ext4 with
an unencrypted /boot (ext3).

I'd be happy to help diagnosing this bug but don't really know where to
start, so if you have any advice or request, feel free to tell me.

Cheers,
  Matteo


-- Package-specific info:
** Version:
Linux version 3.10-3-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 
(Debian 4.7.3-7) ) #1 SMP Debian 3.10.11-1 (2013-09-10)

** Command line:
BOOT_IMAGE=/vmlinuz-3.10-3-amd64 root=/dev/mapper/sysvg-rootlv ro quiet

** Not tainted

** Kernel log:
[   16.950740] cfg80211: Calling CRDA to update world regulatory domain
[   16.998729] [drm] Memory usable by graphics device = 2048M
[   16.998737] i915 :00:02.0: setting latency timer to 64
[   17.024422] i915 :00:02.0: irq 46 for MSI/MSI-X
[   17.024434] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   17.024436] [drm] Driver supports precise vblank timestamp query.
[   17.024503] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   17.044717] Non-volatile memory driver v1.3
[   17.127837] ACPI: Battery Slot [BAT0] (battery present)
[   17.130217] microcode: CPU0 sig=0x10676, pf=0x80, revision=0x60c
[   17.228335] ath5k :03:00.0: registered as 'phy0'
[   17.236019] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
[   17.276797] psmouse serio1: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 
00 64
[   17.277689] thinkpad_acpi: ThinkPad ACPI Extras v0.24
[   17.277691] thinkpad_acpi: http://ibm-acpi.sf.net/
[   17.277693] thinkpad_acpi: ThinkPad BIOS 6DET28WW (1.05 ), EC 7XHT21WW-1.03
[   17.277694] thinkpad_acpi: Lenovo ThinkPad X200, model 7459WKU
[   17.297754] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[   17.297910] thinkpad_acpi: radio switch found; radios are disabled
[   17.298001] thinkpad_acpi: This ThinkPad has standard ACPI backlight 
brightness control, supported by the ACPI video driver
[   17.298003] thinkpad_acpi: Disabling thinkpad-acpi brightness events by 
default...
[   17.300484] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
blocked
[   17.303039] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[   17.303162] thinkpad_acpi: Console audio control enabled, mode: monitor 
(read only)
[   17.304836] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input9
[   17.343554] iTCO_vendor_suppo

Bug#719277: marked as done (linux-image-3.11-rc4-amd64: Display manager fails to start after system boots, cannot switch VTs)

2014-05-08 Thread Debian Bug Tracking System 
Your message dated Thu, 8 May 2014 21:54:41 -0400
with message-id <20140508215441.08c0e74d72afa139cb534...@lm7.fr>
and subject line Re: Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes 
when running Folding@Home as a system service
has caused the Debian Bug report #719277,
regarding linux-image-3.11-rc4-amd64: Display manager fails to start after 
system boots, cannot switch VTs
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.)


-- 
719277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.11~rc4-1~exp1
Severity: important

Dear Maintainer,

It would seem that with the current RC of kernel 3.11 my display manager (GDM)
fails to start after the system finishes booting, and I am unable to switch to
any of the virtual consoles. It seems the system freezes up when trying to
start the display manager, and all I am able to do is power off the system by
holding down the power button.

In order to file this bug with reportbug I had to boot into recovery mode and
launch an X session from there, thus the Linux command line. Allowing the boot
process to continue results in the same issue as a normal boot.

I am fairly certain this is somehow related to the 3.11 RC kernel image because
the display manager starts properly using the other available kernel images.

I should probably also mention I am using Systemd for init due to it
essentially being required by GNOME, however I do not believe this should be an
issue.



-- Package-specific info:
** Version:
Linux version 3.11-rc4-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.7.3 (Debian 4.7.3-6) ) #1 SMP Debian 3.11~rc4-1~exp1 (2013-08-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.11-rc4-amd64 
root=UUID=376d5c13-85a6-476a-aa9e-1be9dc19d808 ro single

** Tainted: I (2048)
 * Working around severe firmware bug.

** Kernel log:
[   14.130112] ACPI: Battery Slot [BAT1] (battery present)
[   14.190657] i801_smbus :00:1f.3: SMBus using PCI Interrupt
[   14.275159] input: PC Speaker as /devices/platform/pcspkr/input/input7
[   14.455183] microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa07
[   14.540446] acerhdf: Acer Aspire One Fan driver, v.0.5.26
[   14.692474] ACPI Warning: 0x0428-0x042f SystemIO 
conflicts with Region \PMBA 1 (20130517/utaddress-251)
[   14.694610] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.700046] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \GPIO 1 (20130517/utaddress-251)
[   14.702561] ACPI Warning: 0x0530-0x053f SystemIO 
conflicts with Region \_SB_.PCI0.LPC_.GPIO 2 (20130517/utaddress-251)
[   14.704747] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.706975] ACPI Warning: 0x0500-0x052f SystemIO 
conflicts with Region \_SB_.PCI0.LPC_.GPIO 1 (20130517/utaddress-251)
[   14.709223] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.711437] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   14.853933] cfg80211: Calling CRDA to update world regulatory domain
[   14.908380] systemd-udevd[321]: renamed network interface eth0 to eth1
[   14.984879] acer_wmi: Acer Laptop ACPI-WMI Extras
[   14.991839] acer_wmi: Function bitmap for Communication Device: 0x10
[   14.994159] acer_wmi: Brightness must be controlled by acpi video driver
[   14.996841] input: Acer BMA150 accelerometer as /devices/virtual/input/input8
[   15.028740] platform microcode: firmware: agent aborted loading 
intel-ucode/06-17-0a (not found?)
[   15.031262] microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa07
[   15.059332] iTCO_vendor_support: vendor-support=0
[   15.068956] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[   15.071390] iTCO_wdt: Found a ICH9M-E TCO device (Version=2, TCOBASE=0x0460)
[   15.074114] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   15.081653] platform microcode: firmware: agent aborted loading 
intel-ucode/06-17-0a (not found?)
[   15.084506] microcode: Microcode Update Driver: v2.00 
, Peter Oruba
[   15.159526] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id: 
0x1c0b1, caps: 0xd04733/0xa4/0xa, board id: 3655, fw id: 568746
[   15.208288] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio2/input/input9
[   15.229355] Intel(R) Wireless WiFi driver for Linux, in-tree:
[   15.232072] Copyright(c) 20

Bug#734003: linux-image-3.13-rc6-amd64: Display manager fails to start, Intel graphics driver not loaded/used, brightness conrtols reversed

2014-05-08 Thread Matteo Cypriani 
Hi Alex,

On Thu, 02 Jan 2014 19:33:04 -0500, Alex Vanderpol 
wrote:
> Package: src:linux
> Version: 3.13~rc6-1~exp1
> Severity: important
> 
> Dear Maintainer,
> 
> This package (version 3.13~rc6-1~exp1) is exhibiting some symptoms that
> lead me to believe it's buggy, namely:
> 
> 1: My display manager (GDM) fails to start when the system finishes booting.
> 2: The Intel graphics driver does not appear to be loaded/used (possibly the
> reason for #1). Instead, the driver "Gallium 0.4 on llvmpipe (LLVM 3.3, 128
> bits)" is used.
> 3: For some reason, the brightness controls end up reversed (trying to lower
> the brightness raises it, and vice-versa), causing my display to be turned
> off rather than turned up to full brightness when the system finishes
> booting (possibly also related to #2).

Did you try reproducing this with Linux 3.14?

For your #3, you should try passing i915.invert_brightness=1 to the kernel
when booting (press E in Grub and add this at the end of the "linux" line),
it should solve the problem. I've read somewhere that if your machine requires
this you should report it, but I don't remember where so.

Hope this helps,
  Matteo


pgp3ILjBRgYG9.pgp
Description: PGP signature

Processed: found 747166 in 3.2.41-2

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

> # first common ancestor for stable and unstable
> # kernels back to 2.6.31 are also affected, but that was linux-2.6, not linux
> found 747166 3.2.41-2
Bug #747166 [linux] CVE-2014-0196: pty layer race condition memory corruption
There is no source info for the package 'linux' at version '3.2.41-2' with 
architecture ''
Unable to make a source version for version '3.2.41-2'
Marked as found in versions 3.2.41-2.
> thanks
Stopping processing here.

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

Processed: merge 743181 742670

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

> fixed 742670 3.14~rc7-1~exp1
Bug #742670 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Ignoring request to alter fixed versions of bug #742670 to the same values 
previously set
> merge 743181 742670
Bug #743181 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Bug #743181 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Marked as fixed in versions linux/3.14~rc7-1~exp1; no longer marked as fixed in 
versions 3.14~rc7-1~exp1.
Bug #742670 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Merged 742670 743181
>
End of message, stopping processing here.

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

Processed (with 1 errors): Re: Critical bug fixes to be2net driver

2014-05-08 Thread Debian Bug Tracking System 
Processing control commands:

> forcemerge 743181 742670
Bug #743181 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Bug #742670 [src:linux] Critical bug fixes to be2net driver
Marked Bug as done
Marked as fixed in versions linux/3.14~rc7-1~exp1.
Bug #742670 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Ignoring request to alter fixed versions of bug #742670 to the same values 
previously set
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #742670 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Ignoring request to alter fixed versions of bug #742670 to the same values 
previously set
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #742670 {Done: Ben Hutchings } [src:linux] Critical 
bug fixes to be2net driver
Ignoring request to alter fixed versions of bug #742670 to the same values 
previously set
After four attempts, the following changes were unable to be made:
fixed_versions of #742670 is 'linux/3.14~rc7-1~exp1' not '3.14~rc7-1~exp1'
Failed to forcibly merge 743181: Unable to modify bugs so they could be merged.


-- 
742670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742670
743181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743181
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.b742670.13995868304482.transcr...@bugs.debian.org

Bug#742670: Critical bug fixes to be2net driver

2014-05-08 Thread Matteo Cypriani 
Control: forcemerge 743181 742670

On Wed, 26 Mar 2014 05:28:25 +, Suresh Kumar Reddy Reddygari
 wrote:
> Package: src:linux
> Version: 3.13.6-1 4
> Severity: important
> X-Debbugs-CC: debian-kernel@lists.debian.org
> 
> Opening Bug to submit certain 17 critical fixes to be2net driver.
> 
> These patches have been accepted upstream.
> These fixes required in driver for Skyhawk-R.

#742670 is a duplicate of #742670, which was already closed. Merging and
closing.

Cheers,
  Matteo


pgpxtmoJHs9bJ.pgp
Description: PGP signature

Bug#746726: Acknowledgement (linux-image-3.2.0-4-486: Sporadic freezes after updating from 3.2.54-2 to 3.2.57-3)

2014-05-08 Thread Erik Schanze 
Hi,

the reinstalled kernel 3.2.54-2 freezed also several times. I also tried
some older kernel like 3.2.41-2+deb7u2 that freezed also.

The strange thing is, that my installation CD (running 3.2.51) work fine
during installation of a new system or as rescue system.
Perhaps there are some problematic modules not loaded?

Currently I installed kernel 2.6.32-5-686 from Debian 6 that works fine
for some days now.

Do you have any suggestion to debug the problem?
Should I reduce the used modules in 3.2 kernel to check for
any problematic one?

Here some info of the system ATM:
-
-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-48squeeze5) (da...@debian.org)
(gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Apr 9 19:23:16 UTC 2014

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686
root=UUID=4d42bd7e-3df7-40fb-a825-ff02a5f2ac64 ro i915.modeset=1
enableapic quiet

** Not tainted

** Kernel log:
[6.884475] input: PS/2 Mouse as
/devices/platform/i8042/serio4/input/input6
[6.905337] input: AlpsPS/2 ALPS GlidePoint as
/devices/platform/i8042/serio4/input/input7
[6.950690] ACPI: WMI: Mapper loaded
[7.117363] [Firmware Bug]: ACPI: ACPI brightness control misses _BQC
function
[7.118167] acpi device:04: registered as cooling_device1
[7.118644] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input8
[7.118765] ACPI: Video Device [GFX0] (multi-head: yes  rom: yes
post: no)
[7.466080] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[7.526068] intel_rng: Firmware space is locked read-only. If you
can't or
[7.526071] intel_rng: don't want to disable this in firmware setup,
and if
[7.526074] intel_rng: you are certain that your system has a functional
[7.526076] intel_rng: RNG, try using the 'no_fwh_detect' option.
[7.568624] acer-wmi: Acer Laptop ACPI-WMI Extras
[7.568652] acer-wmi: No or unsupported WMI interface, unable to load
[7.587145] i801_smbus :00:1f.3: PCI INT B -> Link[LNKB] -> GSI
10 (level, low) -> IRQ 10
[8.097990] [drm] Initialized drm 1.1.0 20060810
[8.382486] parport_pc 00:08: reported by Plug and Play ACPI
[8.382512] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
[8.403959] iTCO_vendor_support: vendor-support=0
[8.455091] lib80211: common routines for IEEE802.11 drivers
[8.455097] lib80211_crypt: registered algorithm 'NULL'
[8.518975] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
[8.522819] iTCO_wdt: Found a ICH4-M TCO device (Version=1,
TCOBASE=0x1060)
[8.523347] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[8.538515] ieee80211: 802.11 data/management/control stack, git-1.1.13
[8.538519] ieee80211: Copyright (C) 2004-2005 Intel Corporation

[8.608541] i915 :00:02.0: PCI INT A -> Link[LNKA] -> GSI 10
(level, low) -> IRQ 10
[8.608549] i915 :00:02.0: setting latency timer to 64
[8.613875] [drm] set up 15M of stolen space
[8.743943] yenta_cardbus :01:04.0: CardBus bridge found [1025:003d]
[8.743963] yenta_cardbus :01:04.0: Using CSCINT to route CSC
interrupts to PCI
[8.743967] yenta_cardbus :01:04.0: Routing CardBus interrupts to PCI
[8.743973] yenta_cardbus :01:04.0: TI: mfunc 0x00111c12, devctl 0x46
[8.744471] [drm] initialized overlay support
[9.003615] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
[9.003619] ipw2100: Copyright(c) 2003-2006 Intel Corporation
[9.128922] yenta_cardbus :01:04.0: ISA IRQ mask 0x0818, PCI irq 10
[9.128928] yenta_cardbus :01:04.0: Socket status: 3006
[9.128934] pci_bus :01: Raising subordinate bus# of parent bus
(#01) from #01 to #05
[9.128946] yenta_cardbus :01:04.0: pcmcia: parent PCI bridge I/O
window: 0xc000 - 0xdfff
[9.128951] pcmcia_socket pcmcia_socket0: cs: IO port probe
0xc000-0xdfff: clean.
[9.129562] yenta_cardbus :01:04.0: pcmcia: parent PCI bridge
Memory window: 0xe000 - 0xefff
[9.129567] yenta_cardbus :01:04.0: pcmcia: parent PCI bridge
Memory window: 0xa000 - 0xafff
[9.133614] ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10
[9.133622] ipw2100 :01:02.0: PCI INT A -> Link[LNKG] -> GSI 10
(level, low) -> IRQ 10
[9.134242] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
[9.134264] ipw2100 :01:02.0: firmware: requesting ipw2100-1.3.fw
[9.603568] pcmcia_socket pcmcia_socket0: cs: IO port probe
0x100-0x3af: clean.
[9.605166] pcmcia_socket pcmcia_socket0: cs: IO port probe
0x3e0-0x4ff: clean.
[9.605848] pcmcia_socket pcmcia_socket0: cs: IO port probe
0x820-0x8ff: clean.
[9.606411] pcmcia_socket pcmcia_socket0: cs: IO port probe
0xc00-0xcf7: clean.
[9.607080] pcmcia_socket pcmcia_socket0: cs: IO port probe
0xa00-0xaff: clean.
[9.668363] eth1: Radio is disabled by RF switch.
[9.686607] Conso

Bug#746411: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update

2014-05-08 Thread Jens Thiele 
if i revert the commit:

commit e07518e9ce84547ef7a81478dbd3fed1539726da
Author: Robert Richter 
Date:   Wed Jan 15 15:57:29 2014 +0100

perf/x86/amd/ibs: Fix waking up from S3 for AMD family 10h

suspend/resume works for me again

$ git branch -v
* linux-3.2.y f453538 Linux 3.2.58
$ git diff-tree -R -p e07518e9ce84547ef7a81478dbd3fed1539726da
(patch attached)

diff --git a/arch/x86/kernel/cpu/perf_event_amd_ibs.c b/arch/x86/kernel/cpu/perf_event_amd_ibs.c
index ea34253..3b8a2d3 100644
--- a/arch/x86/kernel/cpu/perf_event_amd_ibs.c
+++ b/arch/x86/kernel/cpu/perf_event_amd_ibs.c
@@ -9,7 +9,6 @@
 #include 
 #include 
 #include 
-#include 
 
 #include 
 
@@ -210,18 +209,6 @@ out:
 	return ret;
 }
 
-static void ibs_eilvt_setup(void)
-{
-	/*
-	 * Force LVT offset assignment for family 10h: The offsets are
-	 * not assigned by the BIOS for this family, so the OS is
-	 * responsible for doing it. If the OS assignment fails, fall
-	 * back to BIOS settings and try to setup this.
-	 */
-	if (boot_cpu_data.x86 == 0x10)
-		force_ibs_eilvt_setup();
-}
-
 static inline int get_ibs_lvt_offset(void)
 {
 	u64 val;
@@ -257,36 +244,6 @@ static void clear_APIC_ibs(void *dummy)
 		setup_APIC_eilvt(offset, 0, APIC_EILVT_MSG_FIX, 1);
 }
 
-#ifdef CONFIG_PM
-
-static int perf_ibs_suspend(void)
-{
-	clear_APIC_ibs(NULL);
-	return 0;
-}
-
-static void perf_ibs_resume(void)
-{
-	ibs_eilvt_setup();
-	setup_APIC_ibs(NULL);
-}
-
-static struct syscore_ops perf_ibs_syscore_ops = {
-	.resume		= perf_ibs_resume,
-	.suspend	= perf_ibs_suspend,
-};
-
-static void perf_ibs_pm_init(void)
-{
-	register_syscore_ops(&perf_ibs_syscore_ops);
-}
-
-#else
-
-static inline void perf_ibs_pm_init(void) { }
-
-#endif
-
 static int __cpuinit
 perf_ibs_cpu_notifier(struct notifier_block *self, unsigned long action, void *hcpu)
 {
@@ -313,12 +270,18 @@ static __init int amd_ibs_init(void)
 	if (!caps)
 		return -ENODEV;	/* ibs not supported by the cpu */
 
-	ibs_eilvt_setup();
+	/*
+	 * Force LVT offset assignment for family 10h: The offsets are
+	 * not assigned by the BIOS for this family, so the OS is
+	 * responsible for doing it. If the OS assignment fails, fall
+	 * back to BIOS settings and try to setup this.
+	 */
+	if (boot_cpu_data.x86 == 0x10)
+		force_ibs_eilvt_setup();
 
 	if (!ibs_eilvt_valid())
 		goto out;
 
-	perf_ibs_pm_init();
 	get_online_cpus();
 	ibs_caps = caps;
 	/* make ibs_caps visible to other cpus: */


pgpW03HeRGKNp.pgp
Description: PGP signature

sculpture art

2014-05-08 Thread chinamarblestatue 

Hello Dear Friend:

This is Lee Who run my family sculpture business- Yuan Lee Sculpture
Plant. Who participate China latest

three Dynasty's Empire's BeiJing Forfidden Palace Building.
Last year just back from Numberg Stone Fair, Just because Germany is My
Childhood's Dream Land -

Deutscher; Switzerland.

I sincerely cherish the opptunity to communicate with the great germany
scluptors on the Fair. Especailly

thanks for Prasident Joachim Gruter From Deutscher
naturwerkstein-verbande V.
Our carving factory will cost price to support our partner.

We sincerely wish you could pay visitation to our factory in your free
time. Wish you Healthy, Happiness

and Prosperous all the whole year.

Yuan Lee Sculpture Plant
fount...@marblef.com
www.bronzefountain.net

SKYPE : StatueLee
ADD: the carving corridor development zone, Dangcheng QuYang
county(SJZ) HeBei province China.
Telephone: 86 0311 85803934 MOB: 86 150 3211 1017


我已邀请您填写表单 未命名的表单。 要填写此表单，请访问：
https://docs.google.com/forms/d/1XfLrPjUsxMfqiwGKMeTIhMnlIzgwZdDILDBlvvtxCy4/viewform?sid&c=0&w=1&token&usp=mail_form_link

Bug#746411: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update

2014-05-08 Thread Jens Thiele 
Jens Thiele  writes:

> Ben Hutchings  writes:
>
>> How is it 'not working'?
>
> didn't have time to inspect the details yet

did some more tests

- it doesn't matter wether i am on power or battery
- I have a reproducible crash on every second resume
  (first resume works / second crashes without any output :( )
- tried to debug using netconsole, but unfortunately i don't get any
  netconsole output on the second resume
- unfortunately i didn't find a linux-image-3.2.0-4-amd64_3.2.54-2.deb
  anymore, but using linux-image-3.2.0-4-amd64_3.2.46-1+deb7u1_amd64.deb
  from debian security suspend/resume works

jens


pgp5tYvZswoPT.pgp
Description: PGP signature

Bug#747395: Repeated oops on S4 resume with i915 drm on 3.2.54-2 and 3.2.57-3

2014-05-08 Thread Nick & John 
Package: linux-image-3.2.0-4-686-pae
Version: 3.2.57-3
Severity: important

Hello to the debian team again, this is Nick Barkas & John Barkas.
Our second bug report is about 3.2 drm again but this one is on
a 32 bit intel based system.The system is based on an ASRock
P4i945GC mainboard (945GC chipset, socket 478) with Pentium 4
Northwood CPU. Every time the system resumes from S4 it complains
about a "pipe B" which is supposed to be off but it is not. After
the oops, the machine works but we cannot tell if it works at 100%.
 This old (by now) board was never really 100% compatible with Linux.
The i915drm had serious i2c problems on older kernels (2.6.32) which
resulted in corrupted DDC EDID and dmesg flooding... Every kernel we
used nagged about the onboard VIA IDE PCIe ACPI DSDT code, but it
worked fine despite the ACPI errors.
 The crappy/beta i915 is finally usable with GMA950 when running a 3.13.10
kernel. Please backport a newer i915 drm (from 3.13 for example) to 3.2.

Mainboard DMI info:
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: P1.30
Release Date: 11/18/2009

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASRock
Product Name: P4i945GC

Mainboard pci info:

00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory
Controller Hub [8086:2770] (rev 02)
Subsystem: ASRock Incorporation Device [1849:2770]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
SERR- 
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ
Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA
controller])
Subsystem: ASRock Incorporation Device [1849:2772]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
SERR-  [disabled]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [d0] 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: i915

02:00.0 IDE interface [0101]: VIA Technologies, Inc. VT6415 PATA IDE
Host Controller [1106:0415] (prog-if 85 [Master SecO PriO])
Subsystem: ASRock Incorporation Device [1849:0415]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- ] ? warn_slowpath_common+0x68/0x79
[  149.468806]  [] ? assert_pipe+0x62/0x69 [i915]
[  149.468812]  [] ? warn_slowpath_fmt+0x29/0x2d
[  149.468831]  [] ? assert_pipe+0x62/0x69 [i915]
[  149.468849]  [] ? intel_crtc_disable+0x39/0x60 [i915]
[  149.468857]  [] ?
drm_helper_disable_unused_functions+0xb0/0xd3 [drm_kms_helper]
[  149.468864]  [] ? drm_helper_resume_force_mode+0xd5/0xdf
[drm_kms_helper]
[  149.468874]  [] ? i915_drm_thaw+0xb8/0xf7 [i915]
[  149.468885]  [] ? i915_resume+0x35/0x47 [i915]
[  149.468891]  [] ? pci_pm_restore+0x6b/0x7a
[  149.468896]  [] ? pm_op+0xe4/0x108
[  149.468900]  [] ? device_resume+0x78/0xc1
[  149.468904]  [] ? async_resume+0x13/0x33
[  149.468908]  [] ? async_run_entry_fn+0x8d/0x125
[  149.468913]  [] ? process_one_work+0x12a/0x209
[  149.468917]  [] ? worker_thread+0xa9/0x122
[  149.468921]  [] ? manage_workers.isra.25+0x13d/0x13d
[  149.468925]  [] ? kthread+0x63/0x68
[  149.468929]  [] ? kthread_worker_fn+0x101/0x101
[  149.468934]  [] ? kernel_thread_helper+0x6/0x10
[  149.468937] ---[ end trace 6f38b2687002c058 ]---

onboard VIA PATA errors to whom it may concern :
[1.116151] libata version 3.00 loaded.
[1.116959] pata_via :02:00.0: version 0.3.4
[1.117298] ACPI Error: [IDEP] Namespace lookup failure,
AE_NOT_FOUND (20131115/psargs-359)
[1.117311] ACPI Error: Method parse/execution failed
[\_SB_.PCI0.P0P6.VT00.GTM_] (Node f744e6e0), AE_NOT_FOUND
(20131115/psparse-536)
[1.117329] ACPI Error: Method parse/execution failed
[\_SB_.PCI0.P0P6.VT00.CHN0._GTM] (Node f744dda0), AE_NOT_FOUND
(20131115/psparse-536)
[1.124520] scsi0 : pata_via
[1.134252] scsi1 : pata_via
[1.134406] ata1: PATA max UDMA/133 cmd 0xec00 ctl 0xe880 bmdma 0xe400 irq 18
[1.134414] ata2: PATA max UDMA/133 cmd 0xe800 ctl 0xe480 bmdma 0xe408 irq 18


-- 
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/CANxHX8_VSJtRunWAeFpPmFhULE3Xrp=hheh+ptpbr4zj5ck...@mail.gmail.com