date:20140929

Bug#712115: marked as done (linux-source-3.2: Kernel from proposed-updates fails to build without removing [drivers/staging/rts5139/rts5139.ko] from configuration)

2014-09-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Sep 2014 07:52:25 +0200
with message-id 20140929075225.04fa5f52@s5.lokal
and subject line close
has caused the Debian Bug report #712115,
regarding linux-source-3.2: Kernel from proposed-updates fails to build without 
removing [drivers/staging/rts5139/rts5139.ko] from configuration
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.)


-- 
712115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: linux-source-3.2
Version: 3.2.46-1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

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

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

I had to remove this: drivers/staging/rts5139 from my kernel-configuration in 
order to be
able to build correctly, before that I saw this:
.
.
..
  CC [M]  drivers/video/via/accel.o
  CC [M]  drivers/video/via/via_utility.o
  CC [M]  drivers/video/via/vt1636.o
  CC [M]  drivers/video/via/global.o
  CC [M]  drivers/usb/serial/ti_usb_3410_5052.o
  CC [M]  drivers/video/via/tblDPASetting.o
  CC [M]  drivers/video/via/viamode.o
  CC [M]  drivers/video/via/via-core.o
  CC [M]  drivers/video/via/via-gpio.o
  CC [M]  drivers/video/via/via_modesetting.o
  CC [M]  drivers/video/via/via_clock.o
  CC [M]  drivers/usb/serial/visor.o
  CC [M]  drivers/usb/serial/whiteheat.o
  LD [M]  drivers/video/sis/sisfb.o
  CC [M]  drivers/usb/serial/vivopay-serial.o
  LD [M]  drivers/video/via/viafb.o
  CC [M]  drivers/usb/serial/zio.o
  LD [M]  drivers/usb/serial/usbserial.o
  Building modules, stage 2.
  MODPOST 2796 modules
ERROR: __modver_version_show [drivers/staging/rts5139/rts5139.ko] undefined!
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/andreas/src/linux-source-3.2'
make: *** [debian/stamp/build/kernel] Error 2

See my attached k-configuration.
The second problem is, that the AMD-legacy blob failed to be rebuilt by dkms 
for the
newly built kernel-image, when setting it up. I have no idea, wether this is 
the fault of
the dkms-mechanism or if it is the blob's fault, but this used to work very 
well on
Squeeze, now there was no hint at all about dkms, only update-grub was done 
when setting
up the new kernel-package. So as it looks like now, I have to reinstall the 
blob manually
every time a new kernel-version is installed. This is quite bad, another 
regression,
that makes me want to buy new hardware.

- -- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.46cak (SMP w/3 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-source-3.2 depends on:
ii  binutils  2.22-8
ii  bzip2 1.0.6-4

Versions of packages linux-source-3.2 recommends:
ii  gcc   4:4.7.2-1
ii  libc6-dev [libc-dev]  2.13-38
ii  make  3.81-8.2

Versions of packages linux-source-3.2 suggests:
pn  libncurses-dev | ncurses-dev  none
pn  libqt4-devnone
ii  pkg-config0.26-1

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlG5YhAACgkQ5+rBHyUt5wvd9gCfTv/PhXbckX4tISN7OGpqZi1Y
RZEAnAjXJMlB+YT9qZ4Yt0UvXILlPrcP
=GKKx
-END PGP SIGNATURE-


config-3.2.46cak.bz2
Description: application/bzip
---End Message---
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


No idea, why this episode has been left open.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlQo85kACgkQ5+rBHyUt5wu/4QCeN3p/aAO93hs/MDzidURNpL1T
bLcAoKD3FrLxyMIu3FAOVG9PdOth2zmz
=ddLh
-END PGP SIGNATURE-
---End Message---

Re: [PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80

2014-09-29 Thread Rafał Miłecki

On 29 September 2014 00:21, Brian Norris computersforpe...@gmail.com wrote:
+ Rafal

Rafal has been looking at the same area of code. I'd really like to get
this patch into 3.18 if possible, so the more eyes the better.

Thanks Brian.

I took me a while to follow this issue, too bad I wasn't subscribed to
the ML earlier. Let me try to sum it up.

1) The main urgent issue: broken auto-loading
Tracked in the thread: http://www.spinics.net/lists/linux-spi/msg01726.html
Problem: m25p80.c references spi_nor_ids (from external file)
Short-term solution: duplicate IDs in the m25p80.c

Ben: just like Brian, I think the patch like this one (
[PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80
) is the way to go. However few comments:

a) I don't see why you modify m25p_probe in it.

b) I don't think the described clean solution (you described it in the
commit message):
A clean solution to this will involve defining the list of device
IDs in spi-nor.h and removing struct spi_device_id from the spi-nor
API, but this is quite a large change.
is the correct one. I think there should be a single string to trigger
m25p80 load and the rest should be handled using JEDEC, with some
workarounds for incompatible devices only.

One thing I wonder about is sense of pushing this patch to the Linus's
tree. Do you think we could prepare a real fix for Linus and leave
this patch for stable@ only? I'm far from being an expert on such
things, just asking.

2) On going cleanups
It seems there are at least 2 ppl (me, Ben) working on some cleanups
independently.

a) There is (l2-mtd pushed) patch moving flash_platform_data into m25p80:
https://patchwork.ozlabs.org/patch/394219/

b) Removing spi_nor::read_id
https://patchwork.ozlabs.org/patch/389073/
Ben: I think this one has a NACK from me, because I'm going to use
custom read_id in the bcm53xxspiflash driver.
See following thread for bcm53xxspiflash description:
http://comments.gmane.org/gmane.linux.drivers.mtd/54578
Initial commit (it uses read_id): https://patchwork.ozlabs.org/patch/381902/

c) Obsoleting spi_device_id
It seems we both were working on the same thing, me slightly slower however ;)
https://patchwork.ozlabs.org/patch/377917/
https://patchwork.ozlabs.org/patch/389074/
https://patchwork.ozlabs.org/patch/389075/
I still have to review calmly your changes, but they need to be rebased anyway.

d) Cleaning m25p80
https://patchwork.ozlabs.org/patch/389076/
Ben: As said before, I think we should do smarter in the m25p80. We
should get rid of all that duplicated strings.

--
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/CACna6rx=GyZ-4JpDix==wkszabseqxk6qcckfikcm9-wzbm...@mail.gmail.com

Bug#759323: linux-image-3.16-trunk-amd64 : Xorg freezes or the system reboots under glxgears

2014-09-29 Thread Alain Rpnpif

This bug is resolved with the package: linux-image-3.16-0.bpo.2-amd64.

Thank you.

-- 
Alain Rpnpif


-- 
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/20140929080107.7b5115a1...@chro.home

Re: [PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80

2014-09-29 Thread Rafał Miłecki

On 29 September 2014 00:21, Brian Norris computersforpe...@gmail.com wrote:
 (Honestly, some of this name-matching / ID-matching stuff confuses me;
 there is at least one too many ways to choose a flash device for this
 driver.)

It's not that complex once you track it. It's just ugly to tracks
because of different structs, function calls and code locations.

1) All m25p80 users (arch code, SPI drivers, etc.) register
struct spi_board_info
that contains modalias. It it used to match a driver to load.
In most (?) cases modalias is set to m25p80

2) Some m25p80 users decided to put a flash device name (e.g.
at25fs010, mx25l2005a, m25p05, w25x10) as modalias of the
struct spi_board_info. I think they are affected by the recent m25p80
change to use spi-not framework.

3) Other m25p80 users provide flash device name (e.g. at25fs010,
mx25l2005a, m25p05, w25x10) using platform_data in the struct
spi_board_info. It points to the struct flash_platform_data with
name and type properties. It seems to me that name is never
used.


My idea for fixing this:

1) Always use m25p80 modalias (for m25p80 compatible hw).
This will make m25p80 driver work without this huge id_table

2) Do not use name nor type in the struct flash_platform_data if
the flash supports JEDEC

3) If the flash is m25p80 compatible, but doesn't support JEDEC, let's
use type to let m25p80 work.


-- 
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/CACna6rwxK61zVPNf2ACYj_NfNtkq=fnqde4xjjnpb8tvp1h...@mail.gmail.com

Re: [PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80

2014-09-29 Thread Rafał Miłecki

On 29 September 2014 08:36, Rafał Miłecki zaj...@gmail.com wrote:
 1) The main urgent issue: broken auto-loading
 Tracked in the thread: http://www.spinics.net/lists/linux-spi/msg01726.html
 Problem: m25p80.c references spi_nor_ids (from external file)
 Short-term solution: duplicate IDs in the m25p80.c

 Ben: just like Brian, I think the patch like this one (
 [PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80
 ) is the way to go. However few comments:

I started wondering... would this be possible to fix all m25p80 users
instead? Make them always specify modalias as m25p80 and then
provide platform_data if needed?

Has anyone checked in how many places we use wrong (or should I say
weird) modaliases? I guess some would need to grep kernel for all
possible names.


--
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/cacna6ry91b3wchsg4c-td+stpuiah7oaacqukikdhud+jct...@mail.gmail.com

Bug#763320: linux-image-3.16-2-amd64: intel_idle enabled for Intel Atom S1260, causes high CPU temperature when idle

2014-09-29 Thread Christophe Thil

Package: src:linux
Version: 3.16.3-2
Severity: normal

Dear Maintainer,

with Kernel 3.16, intel_idle is enabled for the Intel Atom S1260 CPU
(Centerton SoC). This leads to a +20°C temperature increase when the CPU
is idle, exceeding the 100°C alarm threshold for passive cooled systems
like the Supermicro X9SBAA-F.

With 3.14, intel_idle was blacklisted for this CPU, which runs fine. If
3.16 is booted with intel_idle.max_cstate=0 processor.max_cstate=0,
which disables the intel_idle, the CPU also stays cool.

-- Package-specific info:
** Version:
Linux version 3.16-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 
(Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16-2-amd64 
root=UUID=7b7b22dd-1baa-4772-a734-03ffc40db914 ro quiet console=ttyS1,115200n8 
console=tty0 intel_idle.max_cstate=0 processor.max_cstate=0

** Not tainted

** Kernel log:
[2.983325] ata8.00: configured for UDMA/66
[2.983820] ata3.00: ATA-8: ST2000DL003-9VT166, CC3C, max UDMA/133
[2.983825] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[2.984577] ata3.00: configured for UDMA/133
[3.011761] usb 1-4: New USB device found, idVendor=0557, idProduct=2221
[3.011767] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[3.011771] usb 1-4: Product: Hermon USB hidmouse Device
[3.011776] usb 1-4: Manufacturer: Winbond Electronics Corp
[3.012035] usb 1-4: ep 0x82 - rounding interval to 64 microframes, ep desc 
says 80 microframes
[3.012046] usb 1-4: ep 0x81 - rounding interval to 64 microframes, ep desc 
says 80 microframes
[3.019168] hidraw: raw HID events driver (C) Jiri Kosina
[3.030160] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[3.030313] ata1.00: ATA-7: MARVELL Raid VD, MV.R00-0, max UDMA7
[3.030321] ata1.00: 3906865280 sectors, multi 0: LBA48 NCQ (depth 31/32)
[3.030471] ata1.00: configured for UDMA/133
[3.030722] scsi 0:0:0:0: Direct-Access ATA  MARVELL Raid VD  00-0 
PQ: 0 ANSI: 5
[3.031345] usbcore: registered new interface driver usbhid
[3.031351] usbhid: USB HID core driver
[3.031737] scsi 2:0:0:0: Direct-Access ATA  ST2000DL003-9VT1 CC3C 
PQ: 0 ANSI: 5
[3.032928] scsi 7:0:0:0: Processor Marvell  Console  1.01 
PQ: 0 ANSI: 5
[3.033670] input: Winbond Electronics Corp Hermon USB hidmouse Device as 
/devices/pci:00/:00:02.0/:02:00.0/usb1/1-4/1-4:1.0/0003:0557:2221.0001/input/input0
[3.033959] hid-generic 0003:0557:2221.0001: input,hidraw0: USB HID v1.00 
Mouse [Winbond Electronics Corp Hermon USB hidmouse Device] on 
usb-:02:00.0-4/input0
[3.034460] input: Winbond Electronics Corp Hermon USB hidmouse Device as 
/devices/pci:00/:00:02.0/:02:00.0/usb1/1-4/1-4:1.1/0003:0557:2221.0002/input/input1
[3.034625] hid-generic 0003:0557:2221.0002: input,hidraw1: USB HID v1.00 
Keyboard [Winbond Electronics Corp Hermon USB hidmouse Device] on 
usb-:02:00.0-4/input1
[3.046153] ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[3.053518] ata8.00: irq_stat 0x4001
[3.057990] scsi 7:0:0:0: CDB: 
[3.057994] Inquiry: 12 01 00 00 ff 00
[3.058012] ata8.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 3 dma 16640 
in
[3.058012]  res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM 
violation)
[3.075126] ata8: hard resetting link
[3.401934] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[3.402158] ata8.00: configured for UDMA/66
[3.402241] ata8: EH complete
[3.410424] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[3.410654] scsi 2:0:0:0: Attached scsi generic sg1 type 0
[3.410830] scsi 7:0:0:0: Attached scsi generic sg2 type 3
[3.415232] sd 0:0:0:0: [sda] 3906865280 512-byte logical blocks: (2.00 
TB/1.81 TiB)
[3.415438] sd 0:0:0:0: [sda] Write Protect is off
[3.415446] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[3.415527] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[3.415633] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 
TB/1.81 TiB)
[3.415642] sd 2:0:0:0: [sdb] 4096-byte physical blocks
[3.415805] sd 2:0:0:0: [sdb] Write Protect is off
[3.415813] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[3.415884] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[3.460487]  sdb: sdb1 sdb2
[3.461418] sd 2:0:0:0: [sdb] Attached SCSI disk
[3.478857]  sda: sda1 sda2
[3.479827] sd 0:0:0:0: [sda] Attached SCSI disk
[3.726640] PM: Starting manual resume from disk
[3.726652] PM: Hibernation image partition 8:17 present
[3.726655] PM: Looking for hibernation image.
[3.727413] PM: Image not found (code -22)
[3.727417] PM: Hibernation image not present or could not be loaded.
[3.838801] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: 
(null)
[4.548055]

Re: [PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80

2014-09-29 Thread Rafał Miłecki

On 29 September 2014 11:53, Rafał Miłecki zaj...@gmail.com wrote:
 On 29 September 2014 08:36, Rafał Miłecki zaj...@gmail.com wrote:
 1) The main urgent issue: broken auto-loading
 Tracked in the thread: http://www.spinics.net/lists/linux-spi/msg01726.html
 Problem: m25p80.c references spi_nor_ids (from external file)
 Short-term solution: duplicate IDs in the m25p80.c

 Ben: just like Brian, I think the patch like this one (
 [PATCH 1/5] m25p80,spi-nor: Fix module aliases for m25p80
 ) is the way to go. However few comments:

 I started wondering... would this be possible to fix all m25p80 users
 instead? Make them always specify modalias as m25p80 and then
 provide platform_data if needed?

 Has anyone checked in how many places we use wrong (or should I say
 weird) modaliases? I guess some would need to grep kernel for all
 possible names.

I did some (e)grepping, it seems we have:
1) Only 6 references (modalias) in arch/mips/ath79/
2) About 57 references (compatible) in arch/arm/boot/dts/
3) About 32 references (compatible) in arch/powerpc/boot/dts/

However it seems there is no way to provide platform_data in Device
Tree files. So we have to support compatible (modalias) for now I
guess.

The list (if someone would like to check) of used names in archs:
m25p128 m25p16 m25p32 m25p40 m25p64
mx25l12805d mx25l1606e mx25l25635e mx25l4005a mx25l6405d mx66l51235l
n25q128a11 n25q128a13 n25q512a
s25fl008k s25fl256s1 s25fl512s s25sl064a s25sl12801
sst25vf016b sst25vf032b sst25vf040b sst25wf040
w25q128 w25q256 w25q32 w25q32dw w25q80bl w25x80

-- 
Rafał


--
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/cacna6rwz6e0hc_ho+drbtzwnu6_j0xn9b_76fh0ywdosv-m...@mail.gmail.com

Bug#763325: linux-image-3.16-2-amd64: Kernel oops 3.16.2-amd64

2014-09-29 Thread ael

Package: src:linux
Version: 3.16.3-2
Severity: normal

Noticed several oddities while booting this laptop after recent upgrade:
Keyboard was flakey (the 1 did not work unless first on line), then
ok. Fan running continuously which was not happening before.  Of course,
these things may have no connection with the oops, which I have only
just noticed.

The oops (shown again in context later):
-
Sep 29 11:08:39 shelf kernel: [  262.924810] WARNING: CPU: 0 PID: 0 at
/build/linux-P15SNz/linux-3.16.3/net/sched/sch_g
eneric.c:264 dev_watchdog+0x236/0x240()
Sep 29 11:08:39 shelf kernel: [  262.924812] NETDEV WATCHDOG: eth0
(r8169): transmit queue 0 timed out
Sep 29 11:08:39 shelf kernel: [  262.924813] Modules linked in: bnep
uvcvideo videobuf2_vmalloc ecb videobuf2_memops vi
deobuf2_core v4l2_common btusb videodev media bluetooth 6lowpan_iphc
snd_hrtimer snd_seq snd_seq_device snd_hda_codec_h
dmi joydev nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache
sunrpc arc4 rtsx_pci_ms rtsx_pci_sdmmc iTCO_wdt mems
tick iTCO_vendor_support mmc_core snd_hda_codec_realtek
snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp int
el_rapl coretemp kvm_intel kvm crc32_pclmul iwlmvm crc32c_intel mac80211
ghash_clmulni_intel aesni_intel aes_x86_64 lrw
 gf128mul glue_helper ablk_helper cryptd evdev psmouse iwlwifi i915
 serio_raw pcspkr snd_hda_intel cfg80211 i2c_i801 sn
 d_hda_controller sg r8169 sr_mod cdrom mii rfkill rtsx_pci wmi ehci_pci
 xhci_hcd snd_hda_codec snd_hwdep ehci_hcd drm_k
 ms_helper snd_pcm battery snd_timer drm tpm_infineon mei_me tpm_tis
 i2c_algo_bit tpm snd i2c_core soundcore lpc_ich usb
 core ac mei shpchp mfd_core video usb_common button processor fuse
 parport_pc ppdev lp parport autofs4 ext4 crc16 mbcac
 he jbd2 sd_mod crc_t10dif crct10dif_generic ahci libahci
 crct10dif_pclmul crct10dif_common libata scsi_mod thermal ther
 mal_sys
 Sep 29 11:08:39 shelf kernel: [  262.924877] CPU: 0 PID: 0 Comm:
 swapper/0 Not tainted 3.16-2-amd64 #1 Debian 3.16.3-2
 Sep 29 11:08:39 shelf kernel: [  262.924878] Hardware name:
 Notebook W54_55SU1,SUW/W54_55SU1,SU
 W, BIOS 4.6.5 05/29/2014
 Sep 29 11:08:39 shelf kernel: [  262.924879]  0009
 81506188 88041fa03e28 81065707
 Sep 29 11:08:39 shelf kernel: [  262.924881]  
 88041fa03e78 0001 
 Sep 29 11:08:39 shelf kernel: [  262.924883]  88040b1b4000
 8106576c 81775ca0 88040030
 Sep 29 11:08:39 shelf kernel: [  262.924886] Call Trace:
 Sep 29 11:08:39 shelf kernel: [  262.924887]  IRQ
 [81506188] ? dump_stack+0x41/0x51
 Sep 29 11:08:39 shelf kernel: [  262.924896]  [81065707] ?
 warn_slowpath_common+0x77/0x90
 Sep 29 11:08:39 shelf kernel: [  262.924898]  [8106576c] ?
 warn_slowpath_fmt+0x4c/0x50
 Sep 29 11:08:39 shelf kernel: [  262.924902]  [81439af6] ?
 dev_watchdog+0x236/0x240
 Sep 29 11:08:39 shelf kernel: [  262.924904]  [814398c0] ?
 dev_graft_qdisc+0x70/0x70
 Sep 29 11:08:39 shelf kernel: [  262.924908]  [810709c1] ?
 call_timer_fn+0x31/0x100
 Sep 29 11:08:39 shelf kernel: [  262.924910]  [814398c0] ?
 dev_graft_qdisc+0x70/0x70
 Sep 29 11:08:39 shelf kernel: [  262.924913]  [81071ff9] ?
 run_timer_softirq+0x209/0x2f0
 ep 29 11:08:39 shelf kernel: [  262.924887]  IRQ
 [81506188] ? dump_stack+0x41/0x51
 Sep 29 11:08:39 shelf kernel: [  262.924896]  [81065707] ?
 warn_slowpath_common+0x77/0x90
 Sep 29 11:08:39 shelf kernel: [  262.924898]  [8106576c] ?
 warn_slowpath_fmt+0x4c/0x50
 Sep 29 11:08:39 shelf kernel: [  262.924902]  [81439af6] ?
 dev_watchdog+0x236/0x240
 Sep 29 11:08:39 shelf kernel: [  262.924904]  [814398c0] ?
 dev_graft_qdisc+0x70/0x70
 Sep 29 11:08:39 shelf kernel: [  262.924908]  [810709c1] ?
 call_timer_fn+0x31/0x100
 Sep 29 11:08:39 shelf kernel: [  262.924910]  [814398c0] ?
 dev_graft_qdisc+0x70/0x70
 Sep 29 11:08:39 shelf kernel: [  262.924913]  [81071ff9] ?
 run_timer_softirq+0x209/0x2f0
 Sep 29 11:08:39 shelf kernel: [  262.924916]  [8106a5a1] ?
 __do_softirq+0xf1/0x290
 Sep 29 11:08:39 shelf kernel: [  262.924918]  [8106a975] ?
 irq_exit+0x95/0xa0
 Sep 29 11:08:39 shelf kernel: [  262.924922]  [8150f155] ?
 smp_apic_timer_interrupt+0x45/0x60
 Sep 29 11:08:39 shelf kernel: [  262.924924]  [8150d25d] ?
 apic_timer_interrupt+0x6d/0x80
 Sep 29 11:08:39 shelf kernel: [  262.924925]  EOI
 [81072906] ? get_next_timer_interrupt+0x1d6/0x250
 Sep 29 11:08:39 shelf kernel: [  262.924931]  [813d96e2] ?
 cpuidle_enter_state+0x52/0xc0
 Sep 29 11:08:39 shelf kernel: [  262.924934]  [813d96d8] ?
 cpuidle_enter_state+0x48/0xc0
 Sep 29 11:08:39 shelf kernel: [  262.924937]  [810a5d28] ?
 cpu_startup_entry+0x2f8/0x400
 Sep 29 11:08:39 shelf kernel: [  262.924940]  [8190305a] ?

Bug#763325: Solid

2014-09-29 Thread ael

I just had a repeat of this dump with the same details and
Call Trace. It seemed to happen when the machine was (probably)
idle which I suppose fits with a watchdog bug.

The other symptoms that I mentioned did not occur this time.

ael


-- 
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/20140929133205.GA10203@shelf.conquest

Processed: severity of 763320 is important

2014-09-29 Thread Debian Bug Tracking System

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

 severity 763320 important
Bug #763320 [src:linux] linux-image-3.16-2-amd64: intel_idle enabled for Intel 
Atom S1260, causes high CPU temperature when idle
Severity set to 'important' from 'normal'
 thanks
Stopping processing here.

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

Bug#759323: marked as done (linux-image-3.16-trunk-amd64 : Xorg freezes or the system reboots under glxgears)

2014-09-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Sep 2014 16:04:28 +0100
with message-id 1412003068.9388.43.ca...@decadent.org.uk
and subject line Re: Bug#759323: linux-image-3.16-trunk-amd64 : Xorg freezes or 
the system reboots under glxgears
has caused the Debian Bug report #759323,
regarding linux-image-3.16-trunk-amd64 : Xorg freezes or the system reboots 
under glxgears
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.)


-- 
759323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:linux
Version: 3.16-1~exp1
Severity: normal

Dear Maintainer,

Booting with linux-image-3.16-trunk-amd64.
In Xfce, run vblank_mode=1 glxgears.
After some seconds, Xorg freezes or the system reboots.

I will send you the config files.

With the 3.16.1 kernel from upstream, no such issue. Rarely, one reboot after 
two weeks occurs.

CPU :
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 21
model   : 16
model name  : AMD A4-5300 APU with Radeon(tm) HD Graphics
stepping: 1
microcode   : 0x6001119


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

** Model information
sys_vendor: MSI
product_name: MS-7721
product_version: 6.0
chassis_vendor: MSI
chassis_version: 6.0
bios_vendor: American Megatrends Inc.
bios_version: V30.3
board_vendor: MSI
board_name: A78M-E35 (MS-7721)
board_version: 6.0

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 15h (Models 
10h-1fh) Processor Root Complex [1022:1410]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7721]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0

00:00.2 IOMMU [0806]: Advanced Micro Devices [AMD] Family 15h (Models 10h-1fh) 
I/O Memory Management Unit [1022:1419]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7721]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 40
Capabilities: access denied

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI 
Device [1002:9993] (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. Device [1462:7721]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 49
Region 0: Memory at c000 (32-bit, prefetchable) [size=256M]
Region 1: I/O ports at f000 [size=256]
Region 2: Memory at feb0 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: radeon

00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Trinity HDMI 
Audio Controller [1002:9902]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7721]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 50
Region 0: Memory at feb44000 (32-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 15h (Models 
10h-1fh) Processor Root Port [1022:1414] (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- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: fea0-feaf
Prefetchable memory behind bridge: d000-d00f
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR-

Bug#763354: Enable support for RTS5129 card reader

2014-09-29 Thread jidanni

Package: src:linux
Version: 3.16.3-2

Please enable support for the RTS5129 card reader.

Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller

# journalctl

 9月 30 00:04:35 jidanni5 systemd-udevd[168]: Network interface NamePolicy= 
disabled on kernel commandline, ignoring.
 9月 30 00:04:35 jidanni5 kernel: mmc0: new high speed SD card at address 0007
 9月 30 00:04:35 jidanni5 kernel: mmcblk0: mmc0:0007 SD02G 1.84 GiB 
 9月 30 00:04:35 jidanni5 kernel: mmcblk0: p1

http://thelastmaimou.wordpress.com/2013/05/16/the-card-reader-bluff-call-it/comment-page-1/


--
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/87fvfajt44@jidanni.org

56 matches

Mail list logo