Bug#714137: be2net Driver update to 3.9.4 (Jessie)
Package: src:linux Version: 3.9.4 Severity: important X-Debbugs-CC: debian-kernel@lists.debian.org Opening bug to submit net-next patches for debian 3.9.4 kernel. Patches are primarily bug fixes some of which are critical fixes for new hardware support. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/9d1f9fe58f08ed47aa451abb038550e936d32...@cmexmb1.ad.emulex.com
Re: gcc 4.8
Ben Hutchings b...@decadent.org.uk writes: Hi, On Mon, Jun 24, 2013 at 07:27:24PM +0200, Bastian Blank wrote: Hi I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, however I found a weird not longer reproducible bug in s390. I think about using it as default pretty fast for all architectures. I think Arnaud said it was generating unbootable kernels for some ARM configurations. I don't remember any details, though. Yeah. The day we talked about switching to 4.8 for arm*, this mail got sent to linux-arm-kernel: http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/176334.html But no answer so far. Arnaud -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k3lh8few@lebrac.rtp-net.org
Re: Dropping support for the smallest armel machines
+1 for maintaining iop32xx support. I bought and use one for debian development and offer it as a service to open-source developers. Keeping it running with standard stable and sid is essential to this. I also remember nslu2 being the whizzo machine for hackers On 25 June 2013 04:05, Chris Wilkinson kins...@verizon.net wrote: I increased the kernel zimage flash available to 4mb on an Intel SS4000E (iop32x) by reconfiguring the flash with fconfig, deleting the unused parts used by the stock firmware. This enabled me to upgrade the kernel to v3.2. This does need serial console access as Ben says but that is true whatever kernel you want to flash. On the N2100, dpkg automatically flashes new kernels without need for serial console. Is -Os used in the kernel for armel? Or at least when compiling the small-flavour kernels? M -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cal4-wqrwzeqp5jei+_eav+xmve7stf6aklpo-nkqkpyrp3z...@mail.gmail.com
Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
I am exclusively seeing this on the same two servers so far. Is anyone experiencing on this server with more than one VM? Drew Hastings On 06/23/2013 03:41 PM, Drew Hastings wrote: I'm seeing these issues as well, for the first time today. I had two VM's fail. The unique thing about these dom0's was that they both only had one VM. As an example, the xm info on one of them is: root@phx-1006:~# cat /etc/debian_version 6.0.7 root@phx-1006:~# xm info host : phx-1006 release: 2.6.32-5-xen-amd64 version: #1 SMP Mon Feb 25 02:51:39 UTC 2013 machine: x86_64 nr_cpus: 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 3100 hw_caps: bfebfbff:28100800::1f40:13bae3ff::0001: virt_caps : hvm total_memory : 8164 free_memory: 50 node_to_cpu: node0:0-3 node_to_memory : node0:50 node_to_dma32_mem : node0:50 max_node_id: 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: placeholder dom0_mem=1024M cc_compiler: gcc version 4.4.5 (Debian 4.4.5-8) cc_compile_by : ijc cc_compile_domain : hellion.org.uk cc_compile_date: Wed Apr 17 18:59:41 UTC 2013 xend_config_format : 4 I am also only a small mention of it in /var/logmessages: Jun 23 12:13:58 phx-1006 kernel: [3863294.436187] pub: port 2(vif4.0) entering disabled state I have active-backup bonding setup between two NICs, which might be unrelated to the bug. I then create a bridge using that bonding device in /etc/network/interfaces -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51caace3.3050...@crucialwebhost.com
Bug#714137: be2net Driver update to 3.9.4 (Jessie)
Please find attached patches to apply to 3.9. These patches have been accepted upstream. The patches also contain the upstream commit id (using ' git-format-patch-for-backport script ). Please apply. Thanks, Sarvesh be2net_driver_update-3.9.tgz Description: be2net_driver_update-3.9.tgz
Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with entry failed, hardware error 0x80000021
On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
On 24.06.2013 14:30, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
As soon as I remove kvmvapic.bin the virtual machine boots with
qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
emulate_invalid_guest_state=0 or emulate_invalid_guest_state=1 make
no difference.
Please send your patches.
Here it is, run with it and kvmvapic.bin present. See what is printed in
dmesg after the failure.
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index f4a5b3f..65488a4 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -3385,6 +3385,7 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
u32 ar;
+ unsigned long rip;
if (vmx-rmode.vm86_active seg != VCPU_SREG_LDTR) {
*var = vmx-rmode.segs[seg];
@@ -3408,6 +3409,9 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
var-db = (ar 14) 1;
var-g = (ar 15) 1;
var-unusable = (ar 16) 1;
+ rip = kvm_rip_read(vcpu);
+ if ((rip == 0xc101611c || rip == 0xc101611a) seg == VCPU_SREG_FS)
+ printk(base=%p limit=%p selector=%x ar=%x\n, var-base,
var-limit, var-selector, ar);
}
static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)
Booting kernel Linux 3.10-rc5 with your patch applied produces these
messages in dmesg when starting a virtual machine:
emulate_invalid_guest_state=0
[ 118.732151] base= limit= (null) selector=ffff ar=0
[ 118.732341] base= limit= (null) selector=ffff ar=0
I've butchered printk format, but it gives me the idea of what is going
on anyway. Can you try the patch below with
emulate_invalid_guest_state=0|1?
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index f4a5b3f..eb062ce 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -3395,19 +3395,20 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
var-selector = vmx_read_guest_seg_selector(vmx, seg);
return;
}
+
var-base = vmx_read_guest_seg_base(vmx, seg);
var-limit = vmx_read_guest_seg_limit(vmx, seg);
var-selector = vmx_read_guest_seg_selector(vmx, seg);
ar = vmx_read_guest_seg_ar(vmx, seg);
+ var-unusable = (ar 16) 1;
var-type = ar 15;
var-s = (ar 4) 1;
var-dpl = (ar 5) 3;
- var-present = (ar 7) 1;
+ var-present = !var-unusable;
var-avl = (ar 12) 1;
var-l = (ar 13) 1;
var-db = (ar 14) 1;
var-g = (ar 15) 1;
- var-unusable = (ar 16) 1;
}
static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)
--
Gleb.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130626104703.gw18...@redhat.com
Bug#710938: Packard Bell EasyNote LV need i915.invert_brightness on Linux
user cont...@itopie.ch usertags 710938 + itopie.ch-installation thanks Hi there, On Mon, 03 Jun 2013 20:07:47 +0200, Petter Reinholdtsen wrote: The fix is to either set the kernel option i915.invert_brightness=1 during boot, or to create a file in /etc/ like this (as root): echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf update-initramfs -u -k all The above was enough to solve the same problem on an Acer Aspire V3-771G (model VA70): http://bugs.debian.org/714154 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: Acer Incorporated [ALI] Device [1025:0686] 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 41 Region 0: Memory at d400 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 Please change the i915 module for the hardware in question, to get this laptop working out of the box with Debian Wheezy (and future versions). Fully agree, thanks to Petter for the blog post, which directed me to the correct fix: http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html Thx, bye, Gismo / Luca signature.asc Description: PGP signature
Processed: Re: Processed (with 2 errors): installation-reports: Linux black screen of death with Intel HD video on Acer Aspire V3-771G
Processing commands for cont...@bugs.debian.org: block 714154 by 710938 Bug #714154 [installation-reports] installation-reports: Linux black screen of death with Intel HD video on Acer Aspire V3-771G 714154 was not blocked by any bugs. 714154 was not blocking any bugs. Added blocking bug(s) of 714154: 710938 block 714154 by 711586 Bug #714154 [installation-reports] installation-reports: Linux black screen of death with Intel HD video on Acer Aspire V3-771G 714154 was blocked by: 710938 714154 was not blocking any bugs. Added blocking bug(s) of 714154: 711586 thanks Stopping processing here. Please contact me if you need assistance. -- 714154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714154 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: http://lists.debian.org/handler.s.c.137225046828280.transcr...@bugs.debian.org
Bug#714155: initramfs-tools: mdadm starts up before all needed devices are available
Package: initramfs-tools Version: 0.113 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Dear Maintainer, bminton@bminton:~$ dmesg|grep sde [3.114799] sd 8:0:0:0: [sde] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [3.115888] sd 8:0:0:0: [sde] Write Protect is off [3.119758] sd 8:0:0:0: [sde] Mode Sense: 00 3a 00 00 [3.119808] sd 8:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.134660] sde: unknown partition table [3.135237] sd 8:0:0:0: [sde] Attached SCSI disk [45018.662644] md: export_rdev(sde) [45018.748222] md: bindsde [45018.772292] disk 2, o:1, dev:sde bminton@bminton:~$ dmesg|grep md1 [2.164616] md: md1 stopped. [2.171754] md/raid:md1: device sdc operational as raid disk 0 [2.172104] md/raid:md1: device sda2 operational as raid disk 1 [2.173021] md/raid:md1: allocated 3282kB [2.173416] md/raid:md1: raid level 5 active with 2 out of 3 devices, algorithm 5 [2.174093] md1: detected capacity change from 0 to 3000603639808 [2.177433] md1: unknown partition table [45018.773937] md: recovery of RAID array md1 Here's some info about my RAID setup: Personalities : [raid6] [raid5] [raid4] md1 : active raid5 sde[3] sdc[0] sda2[1] 2930276992 blocks level 5, 64k chunk, algorithm 5 [3/2] [UU_] [===.] recovery = 19.4% (285554336/1465138496) finish=684.0min speed=28741K/sec unused devices: none /dev/md1: Version : 0.90 Creation Time : Wed Jun 3 09:16:22 2009 Raid Level : raid5 Array Size : 2930276992 (2794.53 GiB 3000.60 GB) Used Dev Size : 1465138496 (1397.26 GiB 1500.30 GB) Raid Devices : 3 Total Devices : 3 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Wed Jun 19 11:22:09 2013 State : clean, degraded, recovering Active Devices : 2 Working Devices : 3 Failed Devices : 0 Spare Devices : 1 Layout : parity-last Chunk Size : 64K Rebuild Status : 19% complete UUID : bfa46bf0:67d6e997:e473ac2a:9f2b3a7b Events : 0.2609536 Number Major Minor RaidDevice State 0 8 320 active sync /dev/sdc 1 821 active sync /dev/sda2 3 8 642 spare rebuilding /dev/sde - -- Package-specific info: - -- initramfs sizes - -rw--- 1 root root 12M Nov 3 2009 /boot/initrd.img-2.6.31-trunk-amd64 - -rw--- 1 root root 13M Sep 10 2010 /boot/initrd.img-2.6.31.5 - -rw--- 1 root root 15M Feb 16 2010 /boot/initrd.img-2.6.31.5.bak - -rw--- 1 root root 4.7M Oct 27 2011 /boot/initrd.img-2.6.35.5 - -rw--- 1 root root 12M Jun 6 2012 /boot/initrd.img-3.1.6 - -rw-r--r-- 1 root root 9.6M Jun 25 2012 /boot/initrd.img-3.4.3 - -rw--- 1 root root 11M May 2 13:28 /boot/initrd.img-3.7.0 - -rw--- 1 root root0 Dec 13 2012 /boot/initrd.img-3.7.new - -rw--- 1 root root 13M Jun 21 09:21 /boot/initrd.img-3.9.0 - -rw-r--r-- 1 root root 8.0M Sep 30 2009 /boot/initrd.img-evms - -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.9.0 root=/dev/mapper/root-root_vol ro root=/dev/mapper/root-root_vol ro - -- /proc/filesystems reiserfs ext3 ext2 ext4 squashfs vfat iso9660 ntfs fuseblk udf jfs xfs btrfs - -- lsmod Module Size Used by xt_limit1860 5 nf_conntrack_ipv4 9048 2 nf_defrag_ipv4 1473 1 nf_conntrack_ipv4 xt_recent 8255 2 xt_conntrack2920 2 nf_conntrack 66471 2 xt_conntrack,nf_conntrack_ipv4 cpufreq_powersave 1370 0 cpufreq_conservative 4268 0 cpufreq_ondemand5212 1 cpufreq_stats 4638 0 ppdev 7256 0 lp 9272 0 bnep 14388 2 rfcomm 56820 0 bluetooth 296970 10 bnep,rfcomm rfkill 16291 2 bluetooth nfnetlink_queue 7688 0 nfnetlink_log 7629 0 nfnetlink 4265 2 nfnetlink_log,nfnetlink_queue uinput 7173 3 nfsd 197243 13 decnet 77683 0 dummy 2368 0 bridge 82616 0 stp 1900 1 bridge llc 4546 2 stp,bridge hwmon_vid 2442 0 dm_crypt 13410 0 ch 11769 0 st 30706 0 osst 45284 0 nouveau 764359 2 mxm_wmi 1713 1 nouveau wmi 8657 2 mxm_wmi,nouveau video 12263 1 nouveau i2c_algo_bit5003 1 nouveau ttm63471 1 nouveau drm_kms_helper 29285 1 nouveau drm 237454 4 ttm,drm_kms_helper,nouveau powernow_k818511 1 i2c_core
Bug#710938: Packard Bell EasyNote LV need i915.invert_brightness on Linux
[Luca Capello] The above was enough to solve the same problem on an Acer Aspire V3-771G (model VA70): Great. I checked the upstream source, and your video card ID is not in the quirk list yet. Can you submit a patch to dri-devel@ to make sure a permanent fix is included upstream and solve the problem for every distribution? See URL: http://lists.freedesktop.org/archives/dri-devel/2013-June/039763.html and the thread that followed for my success story. :) -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130626130155.ga9...@diskless.uio.no
Re: Dropping support for the smallest armel machines
Ben Hutchings b...@decadent.org.uk writes: We have a recurring problem with building kernels for armel: three flavours (iop32x, ixp4xx, orion5x) require the kernel image size to be less than 1.4-1.5 MB in order to fit into a fixed flash partition. As more features continue to be added to Linux and cannot always configurable as a module, it is necessary to override and disable them on these three configurations[1]. I don't think this is sustainable unless someone who particularly cares about these older platforms steps up to take on this task. The iop32x and ixp4xx hardware appears to been discontinued in 2008. If we remove these flavours now, they will still be supported in Debian 7 until 2016. I think 8 years of support is pretty good. btw, iop32x is used on n2100 which are used on buildd/porter boxes. If we stop supporting it, I'm not sure how the DSA people will react about that. According to comments in the current configuration, the current size limit of 1.5 MB for orion5x is due to the DNS-323, while other models have a ~2 MB flash partition for the kernel. Dropping support for the DNS-323 would make it possible to raise this limit. However, this model was only discontinued in 2012[2]. Perhaps it could be supported by putting a second stage uboot in flash which would load the kernel and initramfs from disk, as suggested in [3]? afaik, there's work upstream to get the same binary kernel running on armel Marvell SoCs (with DT) so if we merge the corresponding flavours, it may result in bigger kernels (it may result in smallers kernels but it's unlikely). We'll know that when it'll be working/available. Arnaud -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bo6t816b@lebrac.rtp-net.org
Bug#714166: linux-image-3.2.0-4-amd64: no rx packets on vlan on e1000e / 82574L
Package: linux-image-3.2.0-4-amd64 Version: 3.2.46-1 Hi, the machine on a trunk with 2 vlans sees no RX packets on VLANs. Configuring a native vlan on the switch and an ip address on the interface works. We also see no packets with 802.1q tags on the interface in tcpdump. Other machines running with squeeze work fine. I tried disabling vlan accelaration as described in #690956 ethtool -K eth0 rxvlan off without success. eth0 Link encap:Ethernet HWaddr 00:25:90:a1:fb:67 inet addr:172.30.24.20 Bcast:172.30.24.31 Mask:255.255.255.224 inet6 addr: fe80::225:90ff:fea1:fb67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15433 errors:0 dropped:0 overruns:0 frame:0 TX packets:7988 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6058505 (5.7 MiB) TX bytes:1462857 (1.3 MiB) Interrupt:20 Memory:dfb0-dfb2 eth0.10 Link encap:Ethernet HWaddr 00:25:90:a1:fb:67 inet6 addr: fe80::225:90ff:fea1:fb67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:468 (468.0 B) eth0.20 Link encap:Ethernet HWaddr 00:25:90:a1:fb:67 inet6 addr: fe80::225:90ff:fea1:fb67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:1174 (1.1 KiB) 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection Subsystem: Super Micro Computer Inc Device 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 16 Region 0: Memory at df90 (32-bit, non-prefetchable) [size=128K] Region 2: I/O ports at d000 [size=32] Region 3: Memory at df92 (32-bit, non-prefetchable) [size=16K] Capabilities: [c8] 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=1 PME- Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Capabilities: [e0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s 512ns, L1 64us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 128ns, L1 64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [a0] MSI-X: Enable+ Count=5 Masked- Vector table: BAR=3 offset= PBA: BAR=3 offset=2000 Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [140 v1] Device Serial Number 00-25-90-ff-ff-a1-fb-66 Kernel driver in use: e1000e [ 2301.255744] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k [ 2301.325643] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. [ 2301.396611] e1000e :00:19.0: setting latency timer to 64 [ 2301.396714] e1000e :00:19.0: irq 42 for MSI/MSI-X [ 2301.709914] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:25:90:a1:fb:67 [ 2301.805786] e1000e :00:19.0: eth0:
Bug#712174: Not support in upstream
On Wed, Jun 26, 2013 at 07:25:27AM +0200, Philipp Marek wrote: On Tue, Jun 25, 2013 at 08:18:48PM +0200, Philipp Marek wrote: I guess I found the reason: this device is not support by the default kernel, but needs the broadcom-sta module built. Trying with m-a a-i now, but I guess this bug can be closed. Right, the device listing in your report shows you had the 'wl' driver loaded on 3.2. Although this doesn't seem to be a regression, it is a bug (of a sort) that the free b43 driver doesn't support this WLAN controller. On second thought, the bug might be that installing/booting a new kernel doesn't immediately causes m-a to run. [...] The linux-headers packages do support postinst hooks. The problem is that dpkg installation does not recurse. So calling 'm-a a-i' in the postinst of a linux-headers package would fail. This is one reason why we now recommend using DKMS instead of m-a. DKMS doesn't require the compiled modules to be built into a package, so it can auto-install in the way that you want. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130626154508.gh4...@decadent.org.uk
Re: Dropping support for the smallest armel machines
On Wed, Jun 26, 2013 at 03:13:48PM +0200, Arnaud Patard wrote: Ben Hutchings b...@decadent.org.uk writes: We have a recurring problem with building kernels for armel: three flavours (iop32x, ixp4xx, orion5x) require the kernel image size to be less than 1.4-1.5 MB in order to fit into a fixed flash partition. As more features continue to be added to Linux and cannot always configurable as a module, it is necessary to override and disable them on these three configurations[1]. I don't think this is sustainable unless someone who particularly cares about these older platforms steps up to take on this task. The iop32x and ixp4xx hardware appears to been discontinued in 2008. If we remove these flavours now, they will still be supported in Debian 7 until 2016. I think 8 years of support is pretty good. btw, iop32x is used on n2100 which are used on buildd/porter boxes. If we stop supporting it, I'm not sure how the DSA people will react about that. [...] Bet they're slower than QEMU versatile emulation on an x86. And DSA loves virtual machines. :-) Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130626153915.gf4...@decadent.org.uk
Bug#710938: Packard Bell EasyNote LV need i915.invert_brightness on Linux
Btw, I have tried to fix my KDE problem (#711237), and the solution to this problem seem to be to disable the acpi backlight support (boot with acpi_backlight=vendor), causing the intel_backlight kernel module to take effect instead and allowing KDE to find a device it understand. But using acpi_backlight=vendor and i915.invert_brightness=1 together have the sad effect of cancelling out each other, leaving me with a black screen again. So you can only use one or the other, but not both. Does this work for your Acer Aspire V3-771G too? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130626164426.gr28...@ulrik.uio.no
Bug report on nfs-common: nfsidmap crashes with exit status 139
Hi, We found a crash in nfsidmap contained in the nfs-common package. You are being contacted because your are listed as one of the maintainer of nfs-common. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will be submitted to the bug tracker is available at the following url: http://www.forallsecure.com/bug-reports/557e857e10afad31f118e3534f57d3cf7645d9fd/ This email is part of a mass bug reporting campain comprising 1,182 bugs. You might have received multiple emails from us concerning different programs. More information about the mass bug reporting is available on the debian-devel mailing list: http://lists.debian.org/debian-devel/2013/06/msg00720.html Regards, The Mayhem Team Cylab, Carnegie Mellon University -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201306261746.r5qhkicl015...@smtp.andrew.cmu.edu
Bug#714217: linux-image-3.9-1-686-pae: hda-intel 0000:00:1b.0: azx_get_response timeout
Package: src:linux Version: 3.9.6-1 Severity: normal Dear Maintainer, I went from a kernel linux-image-3.2.0-4-686-pae to kernel linux-image-3.9-1-686-pae. Since the X display is shifted upwards and reveals a piece of the linux console at the bottom of screen. These three lines from the dmesg may have a bearing on the problem : [ 54.972133] hda-intel :00:1b.0: azx_get_response timeout, switching to polling mode: last cmd=0x106a [ 56.004116] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x106a [ 56.073605] hda-intel: Invalid position buffer, using LPIB read method instead. I can not attach a screenshot, because utility capture buffer X server but are not offset on the screen. Regards, -- Package-specific info: ** Version: Linux version 3.9-1-686-pae (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-4) ) #1 SMP Debian 3.9.6-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.9-1-686-pae root=UUID=fea5336a-726d-4e2c-a0cc-61b633ddcbaa ro drm.debug=0x86 ** Not tainted ** Kernel log: [ 22.140843] input: HDA Intel MID Line Out Side as /devices/pci:00/:00:1b.0/sound/card0/input13 [ 22.142454] input: HDA Intel MID Line Out CLFE as /devices/pci:00/:00:1b.0/sound/card0/input14 [ 22.144125] input: HDA Intel MID Line Out Surround as /devices/pci:00/:00:1b.0/sound/card0/input15 [ 22.145807] input: HDA Intel MID Line Out Front as /devices/pci:00/:00:1b.0/sound/card0/input16 [ 26.673971] Adding 2650688k swap on /dev/sda5. Priority:-1 extents:1 across:2650688k [ 29.070351] EXT3-fs (sda1): using internal journal [ 29.671240] device-mapper: uevent: version 1.0.3 [ 29.698741] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-de...@redhat.com [ 30.291837] fuse init (API version 7.21) [ 30.428813] loop: module loaded [ 34.893524] r8169 :01:00.0 eth0: link down [ 34.893563] r8169 :01:00.0 eth0: link down [ 34.956480] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 36.596713] r8169 :01:00.0 eth0: link up [ 36.652893] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 54.972133] hda-intel :00:1b.0: azx_get_response timeout, switching to polling mode: last cmd=0x106a [ 56.004116] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x106a [ 56.073605] hda-intel: Invalid position buffer, using LPIB read method instead. [ 174.823437] [drm:psb_intel_sdvo_debug_write], SDVOB: W: 05 00 00 (SDVO_CMD_SET_ACTIVE_OUTPUTS) [ 174.831875] [drm:psb_intel_sdvo_read_response], SDVOB: R: (Success) [ 174.832681] [drm:asle_set_backlight], asle set backlight 80ff [ 174.833006] [drm:asle_set_backlight], asle set backlight 80ff [ 177.207573] [drm:psb_intel_sdvo_debug_write], SDVOB: W: 03 (SDVO_CMD_GET_TRAINED_INPUTS) [ 177.215072] [drm:psb_intel_sdvo_read_response], SDVOB: R: (Success) 01 [ 177.215087] [drm:psb_intel_sdvo_debug_write], SDVOB: W: 05 02 00 (SDVO_CMD_SET_ACTIVE_OUTPUTS) [ 177.223310] [drm:psb_intel_sdvo_read_response], SDVOB: R: (Success) [ 177.223702] [drm:asle_set_backlight], asle set backlight 80ff [ 177.224024] [drm:asle_set_backlight], asle set backlight 80ff [ 197.804463] [drm:asle_set_backlight], asle set backlight 80ff [ 197.804773] [drm:asle_set_backlight], asle set backlight 80ff [ 362.511756] [drm:drm_crtc_helper_set_config], [ 362.511765] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:56] #connectors=1 (x y) (0 0) [ 362.511795] [drm:drm_crtc_helper_set_config], [CONNECTOR:42:VGA-1] to [CRTC:3] [ 362.511801] [drm:drm_crtc_helper_set_config], [ 362.511805] [drm:drm_crtc_helper_set_config], [CRTC:4] [NOFB] [ 391.018502] [drm:asle_set_backlight], asle set backlight 80ff [ 391.019011] [drm:asle_set_backlight], asle set backlight 80ff [ 454.224707] [drm:drm_crtc_helper_set_config], [ 454.224718] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:56] #connectors=1 (x y) (0 0) [ 454.224762] [drm:drm_crtc_helper_set_config], [CONNECTOR:42:VGA-1] to [CRTC:3] [ 454.224770] [drm:drm_crtc_helper_set_config], [ 454.224776] [drm:drm_crtc_helper_set_config], [CRTC:4] [NOFB] [ 458.668746] [drm:asle_set_backlight], asle set backlight 80ff [ 458.669146] [drm:asle_set_backlight], asle set backlight 80ff [ 551.741760] [drm:drm_crtc_helper_set_config], [ 551.741769] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:56] #connectors=1 (x y) (0 0) [ 551.741800] [drm:drm_crtc_helper_set_config], [CONNECTOR:42:VGA-1] to [CRTC:3] [ 551.741806] [drm:drm_crtc_helper_set_config], [ 551.741810] [drm:drm_crtc_helper_set_config], [CRTC:4] [NOFB] [ 586.299937] [drm:asle_set_backlight], asle set backlight 80ff [ 586.300518] [drm:asle_set_backlight], asle set backlight 80ff [ 739.421786] [drm:drm_crtc_helper_set_config], [ 739.421796] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:56]
Bug#714218: linux-image-3.10-rc5-amd64: Compile new intel-pstate driver
Package: src:linux Version: 3.10~rc5-1~exp1 Severity: wishlist Dear Maintainer, It'd be great if you could, in a future version of the kernel package, compile in the new intel-pstate driver. See: http://lkml.indiana.edu/hypermail/linux/kernel/1302.0/02669.html This is supposed to have landed in 3.9 (I believe). Thanks, Andreas -- Package-specific info: ** Version: Linux version 3.10-rc5-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.10~rc5-1~exp1 (2013-06-11) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.10-rc5-amd64 root=UUID=7a99e2e7-d94c-4a8d-bbde-18b48c4dfa67 ro quiet splash i915.i915_enable_rc6=1 i915.lvds_downclock=1 pcie_aspm=force init=/bin/systemd ** Not tainted ** Kernel log: [31407.125328] [ 2235] 1000 2235 242884 2054 610 0 gnome-keyring-d [31407.125330] [ 2254] 1000 2254 140365 979 1050 0 gnome-session [31407.125331] [ 2295] 1000 2295 3148 85 90 0 ssh-agent [31407.125333] [ 2296] 1000 2296 5174 54 120 0 gpg-agent [31407.125335] [ 2299] 1000 2299 6084 62 150 0 dbus-launch [31407.125336] [ 2300] 1000 2300 8725 639 230 0 dbus-daemon [31407.125338] [ 2307] 1000 230784319 133 320 0 at-spi-bus-laun [31407.125340] [ 2311] 1000 2311 8097 126 210 0 dbus-daemon [31407.125341] [ 2314] 1000 231431695 135 310 0 at-spi2-registr [31407.125343] [ 2321] 1000 2321 331770 2603 2020 0 gnome-settings- [31407.125345] [ 2336] 1000 2336 115346 1269 1020 0 pulseaudio [31407.125346] [ 2338] 1000 233849302 198 320 0 gvfsd [31407.125348] [ 2345] 1000 234529279 186 590 0 gconf-helper [31407.125350] [ 2347] 1000 234714084 420 320 0 gconfd-2 [31407.125351] [ 2352] 1000 235255253 389 430 0 gvfs-udisks2-vo [31407.125353] [ 2354] 0 235489985 368 410 0 udisksd [31407.125354] [ 2362] 1000 236271444 165 400 0 gvfs-afc-volume [31407.125356] [ 2367] 1000 236746850 132 290 0 gvfs-mtp-volume [31407.125358] [ 2371] 1000 237149919 190 330 0 gvfs-gphoto2-vo [31407.125360] [ 2375] 1000 237545852 127 260 0 gvfs-goa-volume [31407.125362] [ 2378] 1000 2378 135679 1683 1380 0 goa-daemon [31407.125363] [ 2383] 1000 2383 65137479177 7160 0 gnome-shell [31407.125365] [ 2386] 1000 2386 6351 58 170 0 syndaemon [31407.125366] [ 2395] 1000 239594946 282 810 0 gsd-printer [31407.125368] [ 2401] 1000 240144666 448 230 0 dconf-service [31407.125430] [ 2416] 1000 2416 125159 464 750 0 gnome-shell-cal [31407.125431] [ 2422] 1000 2422 269493 727 1410 0 evolution-sourc [31407.125433] [ 2437] 1000 243776893 834 520 0 mission-control [31407.125434] [ 2442] 1000 244231033 938 300 0 gvfsd-metadata [31407.125436] [ 2450] 1000 2450 219819 1448 1760 0 nm-applet [31407.125438] [ 2451] 1000 245162260 6729 910 0 applet.py [31407.125439] [ 2453] 1000 2453 186540 1797 1990 0 evolution-alarm [31407.125441] [ 2457] 1000 2457 413030 187547 4410 0 tracker-miner-f [31407.125443] [ 2459] 1000 2459 13981430778 1100 0 tracker-store [31407.125444] [ 2483] 1000 2483 227747 1347 1380 0 evolution-calen [31407.125446] [ 2546] 1000 254672455 243 420 0 telepathy-logge [31407.125447] [ 2554] 1000 2554 294538 2203 2190 0 evolution-addre [31407.125449] [ 2597] 1000 2597 12752610957 670 0 synoptic [31407.125451] [ 2598] 1000 2598 117253273600 3780 0 java [31407.125452] [ 2599] 1000 2599 133440 2872 1090 0 python [31407.125454] [ 2600] 1000 260051018 3625 1020 0 python2 [31407.125455] [ 2614] 1000 261415804 107 350 0 redshift [31407.125457] [ 3155] 1000 315569360 211 380 0 gvfsd-trash [31407.125458] [ 3570] 0 357019627
Processed: Re: Bug#714218: linux-image-3.10-rc5-amd64: Compile new intel-pstate driver
Processing commands for cont...@bugs.debian.org: close 714218 Bug #714218 [src:linux] linux-image-3.10-rc5-amd64: Compile new intel-pstate driver Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 714218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714218 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: http://lists.debian.org/handler.s.c.137228446212537.transcr...@bugs.debian.org
Bug#714218: linux-image-3.10-rc5-amd64: Compile new intel-pstate driver
close 714218 thanks Le 26/06/2013 23:12, Andreas Kloeckner a écrit : Package: src:linux Version: 3.10~rc5-1~exp1 Severity: wishlist Dear Maintainer, It'd be great if you could, in a future version of the kernel package, compile in the new intel-pstate driver. See: http://lkml.indiana.edu/hypermail/linux/kernel/1302.0/02669.html This is supposed to have landed in 3.9 (I believe). Hi, Please update to 3.10~rc7-1~exp1, you'll find your happiness ;-) Thanks, Andreas Cheers, Vincent -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51cb67a9.8010...@free.fr
Processed: fixed 714218 in 3.10~rc7-1~exp1
Processing commands for cont...@bugs.debian.org:
fixed 714218 3.10~rc7-1~exp1
Bug #714218 {Done: Vincent Blut vincent.deb...@free.fr} [src:linux]
linux-image-3.10-rc5-amd64: Compile new intel-pstate driver
Marked as fixed in versions linux/3.10~rc7-1~exp1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
714218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714218
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:
http://lists.debian.org/handler.s.c.13722887065898.transcr...@bugs.debian.org
Re: Bug report on nfs-common: nfsidmap crashes with exit status 139
On Wed, 2013-06-26 at 13:46 -0400, Alexandre Rebert wrote: Hi, We found a crash in nfsidmap contained in the nfs-common package. You are being contacted because your are listed as one of the maintainer of nfs-common. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. [...] It's a bit late for that, as you sent mail to a public mailing list. nfsidmap is intended to be invoked by request-key, which itself is invoked by the kernel using an upcall. The arguments are generated according to the configuration in /etc/request-key.d/id_resolver.conf where the default is '/usr/sbin/nfsidmap -t 600 %k %d'. %k expands to the key ID, an integer generated by the kernel's 'keys' subsystem. %d expands to a description of the key, a string generated by the kernel's NFS client. This is partly controlled by the remote server, but the client always uses one of four prefixes: 'uid:', 'gid:', 'user:' or 'group:'. There does not seem to be any way to make the kernel invoke nfsidmap with an invalid option as used in the test case, and I don't see any reason for a user to invoke it directly with untrusted input. So I don't think there is any security issue here. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Bug#714217: linux-image-3.9-1-686-pae: hda-intel 0000:00:1b.0: azx_get_response timeout
Control: retitle -1 X display is shifted upwards on GMA500 On Wed, 2013-06-26 at 23:26 +0200, Stéphane Aulery wrote: Package: src:linux Version: 3.9.6-1 Severity: normal Dear Maintainer, I went from a kernel linux-image-3.2.0-4-686-pae to kernel linux-image-3.9-1-686-pae. Since the X display is shifted upwards and reveals a piece of the linux console at the bottom of screen. These three lines from the dmesg may have a bearing on the problem : [ 54.972133] hda-intel :00:1b.0: azx_get_response timeout, switching to polling mode: last cmd=0x106a [ 56.004116] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x106a [ 56.073605] hda-intel: Invalid position buffer, using LPIB read method instead. Those error messages are from the sound driver (snd-hda-intel), not the graphics driver (gma500). I can not attach a screenshot, because utility capture buffer X server but are not offset on the screen. [...] Please report this bug at https://bugs.freedesktop.org/ under product DRI, component DRM/other. Let us know the URL of that bug report so we can track it. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#714217: linux-image-3.9-1-686-pae: hda-intel 0000:00:1b.0: azx_get_response timeout
Processing control commands: retitle -1 X display is shifted upwards on GMA500 Bug #714217 [src:linux] linux-image-3.9-1-686-pae: hda-intel :00:1b.0: azx_get_response timeout Changed Bug title to 'X display is shifted upwards on GMA500' from 'linux-image-3.9-1-686-pae: hda-intel :00:1b.0: azx_get_response timeout' -- 714217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714217 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: http://lists.debian.org/handler.s.b714217.13723064166989.transcr...@bugs.debian.org
