Bug#808889: linux-image-4.3.0-1-amd64: The bug may lay on the firmware side.

2016-01-28 Thread Tianming Xie 
Package: src:linux
Version: 4.3.3-7
Followup-For: Bug #808889

Dear Maintainer,

According to http://permalink.gmane.org/gmane.comp.bios.libreboot/453 , I
applied the patch https://review.coreboot.org/#/c/11853/  (attached) atop the
last stable version. of libreboot's source code, rebuilt and reflashed the
firmware on my X200, and the system time was set successfully from hwclock by
the kernel.

This patch is committed after the last release, thus not included in the last
stable version.



-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19)

** Command line:
BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 
root=UUID=a994a1c5-a911-48bd-a468-4aa6a9728001 ro quiet

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

** Kernel log:
[2.612225] option 8-4:1.3: GSM modem (1-port) converter detected
[2.612293] usb 8-4: GSM modem (1-port) converter now attached to ttyUSB2
[2.612954] qmi_wwan 8-4:1.8: cdc-wdm0: USB WDM device
[2.613121] qmi_wwan 8-4:1.8 wwan0: register 'qmi_wwan' at 
usb-:00:1d.7-4, WWAN/QMI device, b2:71:3a:12:1c:d1
[2.613441] qmi_wwan 8-4:1.10: cdc-wdm1: USB WDM device
[2.613579] qmi_wwan 8-4:1.10 wwan1: register 'qmi_wwan' at 
usb-:00:1d.7-4, WWAN/QMI device, b2:71:3a:12:1c:d1
[2.613612] usbcore: registered new interface driver qmi_wwan
[2.652785] ath: EEPROM regdomain: 0x64
[2.652789] ath: EEPROM indicates we should expect a direct regpair map
[2.652791] ath: Country alpha2 being used: 00
[2.652793] ath: Regpair used: 0x64
[2.672641] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[2.672963] ieee80211 phy0: Atheros AR9300 Rev:3 mem=0xc9fc, 
irq=17
[2.731183] [drm] Initialized i915 1.6.0 20150731 for :00:02.0 on minor 0
[2.731300] ACPI Warning: SystemIO range 
0x0628-0x062F conflicts with OpRegion 
0x0600-0x067F (\PMIO) (20150818/utaddress-254)
[2.731306] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[2.731310] ACPI Warning: SystemIO range 
0x05B0-0x05BF conflicts with OpRegion 
0x0580-0x05BB (\GPIO) (20150818/utaddress-254)
[2.731313] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[2.731315] ACPI Warning: SystemIO range 
0x0580-0x05AF conflicts with OpRegion 
0x0580-0x05BB (\GPIO) (20150818/utaddress-254)
[2.731319] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[2.731320] lpc_ich: Resource conflict(s) found affecting gpio_ich
[2.731553] ACPI Warning: SystemIO range 
0x0400-0x041F conflicts with OpRegion 
0x0400-0x041F (\_SB_.PCI0.SBUS.SMBI) 
(20150818/utaddress-254)
[2.731559] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[2.846592] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: 
discard
[2.891419] EXT4-fs (sda3): mounting ext2 file system using the ext4 
subsystem
[2.896896] EXT4-fs (sda3): mounted filesystem without journal. Opts: discard
[2.901818] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: 
discard
[2.907642] fbcon: inteldrmfb (fb0) is primary device
[2.907883] cfg80211: World regulatory domain updated:
[2.907885] cfg80211:  DFS Master region: unset
[2.907885] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[2.907886] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[2.907888] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[2.907889] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 
mBm), (N/A)
[2.907891] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (N/A)
[2.907892] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (0 s)
[2.907894] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 
mBm), (0 s)
[2.907895] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[2.907896] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 
mBm), (N/A)
[2.932219] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT 
filesystems, filesystem will be case sensitive!
[2.939298] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: 
discard
[2.943538] EXT4-fs (sda10): mounted filesystem with ordered data mode. 
Opts: discard
[2.958358] iTCO_vendor_support: vendor-support=0
[2.959097] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[2.959145] iTCO_wdt: Found a ICH9M-E T

Bug#812928: udev: cdrom_id terminated by signal BUS

2016-01-28 Thread John Paul Adrian Glaubitz 
Control: reassign -1 src:systemd
Control: found -1 228-4
Control: retitle -1 initialize_srand provokes unaligned access

On 01/28/2016 07:37 AM, Anatoly Pugachev wrote:
> restored original cdrom_id.c (with initialize_srand() function call) and
> recompiled with memcpy() and run:
> 
> mator@deb4g:~/systemd$ sudo ./cdrom_id -l /dev/vdiskb
> ID_CDROM=1
> 
> there's no SIGBUS. And I don't know what it should output. Probably fixed.
> Thanks.

This is clearly a bug in udev/src:systemd then. I'll re-assign this and
also report this upstream.

Thanks for debugging this!

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: Re: Bug#812928: udev: cdrom_id terminated by signal BUS

2016-01-28 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 src:systemd
Bug #812928 [src:linux] getauxval(AT_RANDOM) broken on sparc64
Bug reassigned from package 'src:linux' to 'src:systemd'.
No longer marked as found in versions linux/4.3.0-1.
Ignoring request to alter fixed versions of bug #812928 to the same values 
previously set
> found -1 228-4
Bug #812928 [src:systemd] getauxval(AT_RANDOM) broken on sparc64
Marked as found in versions systemd/228-4.
> retitle -1 initialize_srand provokes unaligned access
Bug #812928 [src:systemd] getauxval(AT_RANDOM) broken on sparc64
Changed Bug title to 'initialize_srand provokes unaligned access' from 
'getauxval(AT_RANDOM) broken on sparc64'

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

Bug#808364: lxc: lxc-start fails to mount proc (Operation not permitted)

2016-01-28 Thread Tomassino Ferrauto 
I confirm that the problem exists and that downgrading to kernel
version 3.16.7-ckt11-1+deb8u6 makes (unprivileged) container work
again. I also found this bugreport in Ubuntu which may be related:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519106

Tomassino

Re: Kernel version for stretch

2016-01-28 Thread Moritz Mühlenhoff 
Ben Hutchings  wrote:
> For stretch, I would very much like to choose a kernel version for
> stretch that gets longterm maintenance by Greg Kroah-Hartman. That
> lasts 2 years from release, after which someone else (maybe me) can
> take over.

Luis Henriques and Kamal Mostafa maintain the ckt stable kernels
for Ubuntu-non-LTS releases for two years.

We could base the stretch kernel on the underlying ckt kernel
series used for Ubuntu 16.04 or 16.10?

Cheers,
Moritz

Re: Kernel version for stretch

2016-01-28 Thread Ben Hutchings 
On Thu, 2016-01-28 at 20:01 +0100, Moritz Mühlenhoff wrote:
> Ben Hutchings  wrote:
> > For stretch, I would very much like to choose a kernel version for
> > stretch that gets longterm maintenance by Greg Kroah-Hartman. That
> > lasts 2 years from release, after which someone else (maybe me) can
> > take over.
> 
> Luis Henriques and Kamal Mostafa maintain the ckt stable kernels
> for Ubuntu-non-LTS releases for two years.

Not in general; it can be as little as 12 months (e.g. 3.11-ckt).

> We could base the stretch kernel on the underlying ckt kernel
> series used for Ubuntu 16.04 or 16.10?

Given the politics involved, I would rather not do that twice in a row.

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

Re: Kernel version for stretch

2016-01-28 Thread maximilian attems 
On Thu, Jan 28, 2016 at 08:01:13PM +0100, Moritz Mühlenhoff wrote:
> Ben Hutchings  wrote:
> > For stretch, I would very much like to choose a kernel version for
> > stretch that gets longterm maintenance by Greg Kroah-Hartman. That
> > lasts 2 years from release, after which someone else (maybe me) can
> > take over.
> 
> Luis Henriques and Kamal Mostafa maintain the ckt stable kernels
> for Ubuntu-non-LTS releases for two years.
> 

Well, those efforts have not a good track record, afais Ben is maintaining
their lts Linus.

-- 
maks