Bug#734976: fail to flush all tx fifo queues Q 2
Applied the patch to a 3.16 kernel. I had to edit line by line the source file because the diff wouldn't behave nicely, and then compiled the kernel with make-kpkg. Running for about 12 hours. Gone into sleep mode and out of it. All seems nice up to now. I'll you keep posted if anything breaks. -- signature name Gerasimos Melissaratos /name title Systems Administrator /title tel+30 6 979 045 121 /tel email gme...@mikroskosmos.gr /email /signature
Bug#765112: linux-image-3.17-rc5-amd64: Kernel hangs for 5 minutes after resume: libgcrypt version: 1.5.4
On Thu, 2014-10-16 at 19:57 -0700, Ralf-Peter Rohbeck wrote: This happens with all the kernels I have, including 3.14-2 and back to 3.2.0-4. If anybody has an idea how to fix or troubleshoot this I'm all ears. Are there flags to increase verbosity or turn on debug messages for the swap code? Add 'debug' to the kernel command line. Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Bug#765685: linux-image-3.16-2-amd64: Kernel lockups with r8723au
Package: src:linux Version: 3.16.3-2 Severity: serious The staging driver r8723au is enabled in the kernel but there appear to be very good reasons why it's in staging - when it loads it routinely locks up my system (hard with no output unfortunately). It seems to make sense to disable the driver. -- 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=1c8b372e-5478-46fe-84d9-efc496b4a0ce ro init=/bin/systemd quiet ** Tainted: WC (1536) * Taint on warning. * Module from drivers/staging has been loaded. ** Kernel log: [ 557.489458] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 557.489463] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 557.494527] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 557.494530] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 558.501325] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 558.501338] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 558.506380] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 558.506383] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 559.515171] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 559.515183] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 559.520204] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 559.520206] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 560.527936] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 560.527939] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 560.532991] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 560.532994] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 561.543521] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 561.543525] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 561.548556] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 561.548560] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 562.557183] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 562.557188] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 562.562215] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 562.562220] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 563.571309] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 563.571314] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 563.576374] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 563.576377] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 564.585412] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 564.585424] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 564.590447] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 564.590450] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 565.599700] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 565.599703] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 565.604736] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 565.604740] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 566.613028] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 566.613033] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 566.618109] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 566.618116] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 567.627585] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 567.627588] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 567.632636] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 567.632640] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 568.640977] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 568.640981] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 568.646030] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 568.646034] atkbd serio0: Use 'setkeycodes e03e keycode' to make it known. [ 569.656338] atkbd
Processed: severity of 765685 is important
Processing commands for cont...@bugs.debian.org: severity 765685 important Bug #765685 [src:linux] linux-image-3.16-2-amd64: Kernel lockups with r8723au Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 765685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765685 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.141354325714912.transcr...@bugs.debian.org
Bug#765690: packagename: type_problemheading_here
Package: linux-image-3.17-rc5-amd64 Version: 3.17~rc5-1~exp1 Severity: normal hi, can the following be a kernel problem? I'll explain a bit, it's got to do with the iptables command.. (fwiw, there's a bug with the lsb-functions, 40-systemd which is instead this can be used to test rules.v4 iptables-restore /etc/iptables/rules.v4 ) output, iptables-restore v1.4.21: iptables-restore: unable to initialize table 'nat' Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information all basic nat modules I can come up with modprobe are loaded, but iptables continues to fail, I checked if NAT is compiled /boot/config-3.17-rc5-amd64 lsmod |grep nat act_nat12501 0 nft_chain_nat_ipv4 12552 0 nft_nat12507 0 nf_tables 54396 2 nft_chain_nat_ipv4,nft_nat nf_nat_ipv412912 1 nft_chain_nat_ipv4 nf_nat_ipv612920 0 nf_nat 18241 4 nft_chain_nat_ipv4,nft_nat,nf_nat_ipv4,nf_nat_ipv6 nf_conntrack 87476 5 nf_nat,nf_nat_ipv4,nf_nat_ipv6,nf_conntrack_ipv4,nf_conntrack_ipv6 so it looks like everything is compiled and loads, but iptables fails for v4. fwiw, the ip6tables loads properly for rules.v6.. If I recall the previous kernel in testing(vmlinuz-3.16-2-amd64) can have the iptables load ipv4 rules timely without issue -- 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/5440f998.9080...@videotron.ca
Bug#765691: linux-image-3.17-rc5-amd64: nat failure with iptables
Package: linux-image-3.17-rc5-amd64 Version: 3.17~rc5-1~exp1 Severity: normal hi, can the following be a kernel problem? I'll explain a bit, it's got to do with the iptables command.. (fwiw, there's a bug with the lsb-functions, 40-systemd which is instead this can be used to test rules.v4 iptables-restore /etc/iptables/rules.v4 ) output, iptables-restore v1.4.21: iptables-restore: unable to initialize table 'nat' Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information all basic nat modules I can come up with modprobe are loaded, but iptables continues to fail, I checked if NAT is compiled /boot/config-3.17-rc5-amd64 lsmod |grep nat act_nat12501 0 nft_chain_nat_ipv4 12552 0 nft_nat12507 0 nf_tables 54396 2 nft_chain_nat_ipv4,nft_nat nf_nat_ipv412912 1 nft_chain_nat_ipv4 nf_nat_ipv612920 0 nf_nat 18241 4 nft_chain_nat_ipv4,nft_nat,nf_nat_ipv4,nf_nat_ipv6 nf_conntrack 87476 5 nf_nat,nf_nat_ipv4,nf_nat_ipv6,nf_conntrack_ipv4,nf_conntrack_ipv6 so it looks like everything is compiled and loads, but iptables fails for v4. fwiw, the ip6tables loads properly for rules.v6.. If I recall the previous kernel in testing(vmlinuz-3.16-2-amd64) can have the iptables load ipv4 rules timely without issue -- 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/5440f9f1.7010...@videotron.ca
Bug#765690: packagename: type_problemheading_here
On Fri, 2014-10-17 at 07:12 -0400, westlake wrote: hi, can the following be a kernel problem? Please can you start to make use of the user support forums (e.g. the debian-user mailing list) in the first instance rather than filing things as bugs which are not yet clearly (or even vaguely) identifiable as such. Ian. -- 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/1413545906.2012.45.ca...@hellion.org.uk
Bug#765690: packagename: type_problemheading_here
There's a bug in multiple places. 1) netfilter-persistent/systemd fails https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764950 2) Emailed J.Wiltshire, he never responded. He's responsible for the netfilter package 3) There is a systemd bug related to the netfilter-persistent package, filed over here, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765683 linux (3.17-1~exp1) experimental; urgency=medium * New upstream release: http://kernelnewbies.org/Linux_3.17 * armel: Drop ixp4xx image. * topconfig: Reenable renamed IP_NF_NAT. (closes #762458) * udeb: refix renamed i2c-core. -- maximilian attems m...@debian.org Tue, 14 Oct 2014 23:01:39 +0200 linux (3.17~rc5-1~exp1) experimental; urgency=medium * New upstream release candidate [ Ben Hutchings ] * aufs: Update to aufs3.x-rcN-20140908 [ maximilian attems ] * udeb: fix renamed i2ccore. -- maximilian attems m...@debian.org Thu, 18 Sep 2014 23:50:00 +0200 http://metadata.ftp-master.debian.org/changelogs//main/l/linux/linux_3.17-1~exp1_changelog I think it's very clear there was indeed a change with nat in this kernel. This is not a configuration issue, otherwise iptables would be loading successfully without crashing with a NAT message. fwiw, iptables relies on the kernel for the NAT modules, so it appears quite clearly what the problem is, and that is this kernel has something new with NAT causing iptables to fail. Not rocket science. -- 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/544113ed.3000...@videotron.ca
Bug#765717: linux-image-3.16-2-amd64: High CPU load with linux-image-3.16-2-amd64
Package: src:linux Version: 3.16.3-2 Severity: normal Dear Maintainer, From the Debian linux kernel 3.16 (all versions in Jessie and Sid), I have a high CPU load. With a fresh install of Debian Jessie (testing), this load is still present. With a non Debian kernel, this issue is not present. Also tested with the new version of the Linux Kernel, linux-image-3.17-1-amd64 (in Experimental), and I have the same problem. Tested on several machines (Zotac ZBOX IQ01, Dell Latitude E6520). CPU model : Intel(R) Core(TM) i7-4770T CPU @ 2.50GHz top : top - 15:03:26 up 1:44, 2 users, load average: 1.00, 1.00, 0.96 Tasks: 146 total, 1 running, 145 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 16165792 total, 338108 used, 15827684 free,19292 buffers KiB Swap: 4395004 total,0 used, 4395004 free. 143788 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 28632 5064 3192 S 0.0 0.0 0:00.54 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.02 ksoftirqd/0 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H 7 root 20 0 0 0 0 S 0.0 0.0 0:00.18 rcu_sched 8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh 9 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0 10 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/0 11 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/1 12 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/1 13 root 20 0 0 0 0 S 0.0 0.0 0:00.09 ksoftirqd/1 15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:0H 16 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/2 17 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/2 18 root 20 0 0 0 0 S 0.0 0.0 0:00.02 ksoftirqd/2 20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/2:0H 21 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/3 22 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/3 23 root 20 0 0 0 0 S 0.0 0.0 0:00.01 ksoftirqd/3 25 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/3:0H
Processing of linux-tools_3.17-1~exp1_source.changes
linux-tools_3.17-1~exp1_source.changes uploaded successfully to localhost along with the files: linux-tools_3.17-1~exp1.dsc linux-tools_3.17.orig.tar.xz linux-tools_3.17-1~exp1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1xf80b-00069v...@franck.debian.org
Bug#765717: linux-image-3.16-2-amd64: High CPU load with linux-image-3.16-2-amd64
Control: tag -1 moreinfo On Fri, Oct 17, 2014 at 03:16:59PM +0200, Gregory Fardel wrote: Package: src:linux Version: 3.16.3-2 Severity: normal Dear Maintainer, From the Debian linux kernel 3.16 (all versions in Jessie and Sid), I have a high CPU load. [...] But CPU *usage* shown by top is 0. That implies there is a task in D state (uninterruptible sleep). That may or may not be a real problem. What does this command print: ps -e -o state,pid,cmd | grep ^D Ben. -- Ben Hutchings Humour is the best antidote to reality. -- 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/20141017141327.gc5...@decadent.org.uk
Bug#765690: packagename: type_problemheading_here
this report is for package maintainers, not clueless idiots. thank you -- 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/5441201a.2070...@videotron.ca
Bug#765690: marked as done (packagename: type_problemheading_here)
Your message dated Fri, 17 Oct 2014 15:04:26 +0100 with message-id 20141017140426.ga5...@decadent.org.uk and subject line Re: Bug#765690: packagename: type_problemheading_here has caused the Debian Bug report #765690, regarding packagename: type_problemheading_here 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.) -- 765690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-3.17-rc5-amd64 Version: 3.17~rc5-1~exp1 Severity: normal hi, can the following be a kernel problem? I'll explain a bit, it's got to do with the iptables command.. (fwiw, there's a bug with the lsb-functions, 40-systemd which is instead this can be used to test rules.v4 iptables-restore /etc/iptables/rules.v4 ) output, iptables-restore v1.4.21: iptables-restore: unable to initialize table 'nat' Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information all basic nat modules I can come up with modprobe are loaded, but iptables continues to fail, I checked if NAT is compiled /boot/config-3.17-rc5-amd64 lsmod |grep nat act_nat12501 0 nft_chain_nat_ipv4 12552 0 nft_nat12507 0 nf_tables 54396 2 nft_chain_nat_ipv4,nft_nat nf_nat_ipv412912 1 nft_chain_nat_ipv4 nf_nat_ipv612920 0 nf_nat 18241 4 nft_chain_nat_ipv4,nft_nat,nf_nat_ipv4,nf_nat_ipv6 nf_conntrack 87476 5 nf_nat,nf_nat_ipv4,nf_nat_ipv6,nf_conntrack_ipv4,nf_conntrack_ipv6 so it looks like everything is compiled and loads, but iptables fails for v4. fwiw, the ip6tables loads properly for rules.v6.. If I recall the previous kernel in testing(vmlinuz-3.16-2-amd64) can have the iptables load ipv4 rules timely without issue ---End Message--- ---BeginMessage--- Closing as this is a duplicate of #765691 and it doesn't have a proper subject. Ben. -- Ben Hutchings Humour is the best antidote to reality.---End Message---
Bug#765691: marked as done (linux-image-3.17-rc5-amd64: nat failure with iptables)
Your message dated Fri, 17 Oct 2014 15:09:14 +0100 with message-id 20141017140914.gb5...@decadent.org.uk and subject line CONFIG_IP_NF_NAT has been enabled has caused the Debian Bug report #762458, regarding linux-image-3.17-rc5-amd64: nat failure with iptables 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.) -- 762458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-3.17-rc5-amd64 Version: 3.17~rc5-1~exp1 Severity: normal hi, can the following be a kernel problem? I'll explain a bit, it's got to do with the iptables command.. (fwiw, there's a bug with the lsb-functions, 40-systemd which is instead this can be used to test rules.v4 iptables-restore /etc/iptables/rules.v4 ) output, iptables-restore v1.4.21: iptables-restore: unable to initialize table 'nat' Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information all basic nat modules I can come up with modprobe are loaded, but iptables continues to fail, I checked if NAT is compiled /boot/config-3.17-rc5-amd64 lsmod |grep nat act_nat12501 0 nft_chain_nat_ipv4 12552 0 nft_nat12507 0 nf_tables 54396 2 nft_chain_nat_ipv4,nft_nat nf_nat_ipv412912 1 nft_chain_nat_ipv4 nf_nat_ipv612920 0 nf_nat 18241 4 nft_chain_nat_ipv4,nft_nat,nf_nat_ipv4,nf_nat_ipv6 nf_conntrack 87476 5 nf_nat,nf_nat_ipv4,nf_nat_ipv6,nf_conntrack_ipv4,nf_conntrack_ipv6 so it looks like everything is compiled and loads, but iptables fails for v4. fwiw, the ip6tables loads properly for rules.v6.. If I recall the previous kernel in testing(vmlinuz-3.16-2-amd64) can have the iptables load ipv4 rules timely without issue ---End Message--- ---BeginMessage--- Version: 3.17-1~exp1 In Linux 3.17, CONFIG_NF_NAT_IPV4 was renamed to CONFIG_IP_NF_NAT. The new config option was enabled in the above Debian version. Ben. -- Ben Hutchings Humour is the best antidote to reality.---End Message---
Bug#762921: marked as done (linux-image-3.17-rc5-amd64: Kernel netfilter modules lack NAT support)
Your message dated Fri, 17 Oct 2014 15:09:14 +0100 with message-id 20141017140914.gb5...@decadent.org.uk and subject line CONFIG_IP_NF_NAT has been enabled has caused the Debian Bug report #762458, regarding linux-image-3.17-rc5-amd64: Kernel netfilter modules lack NAT support 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.) -- 762458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.17~rc5-1~exp1 Severity: important Dear Maintainer, This kernel does not have IP NAT support configured, making it useles for most home router setups. # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE iptables v1.4.21: can't initialize iptables table `nat': Table does not exist # grep CONFIG_IP_NF_NAT /boot/config-3.17-rc5-amd64 # CONFIG_IP_NF_NAT is not set This enables the `nat' table in iptables. This allows masquerading, port forwarding and other forms of full Network Address Port Translation. It seems that the required .config options for NAT have shifted around recently in the kernel. -- Package-specific info: ** Version: Linux version 3.17-rc5-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.17~rc5-1~exp1 (2014-09-18) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.17-rc5-amd64 root=UUID=cb97baf6-acb1-4535-b2d8-dc9d3eb47f64 ro quiet ** Not tainted ** Kernel log: [2.943586] usb 3-10: reset high-speed USB device number 5 using xhci_hcd [2.943634] xhci_hcd :00:14.0: Setup ERROR: setup context command for slot 5. [2.943635] usb 3-10: hub failed to enable device, error -22 [2.948205] sdb: sdb1 [2.959479] sd 4:0:0:0: [sdb] Attached SCSI disk [3.01] usb 3-10: reset high-speed USB device number 5 using xhci_hcd [3.071949] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880214bb7300 [3.071950] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880214bb7348 [3.071951] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880214bb7390 [3.075607] r8152 3-10:1.0 eth1: v1.06.0 (2014/03/03) [3.075677] usbcore: registered new interface driver r8152 [3.078218] usbcore: registered new interface driver cdc_ether [3.081795] random: nonblocking pool is initialized [3.143784] usb 3-9.2: new full-speed USB device number 7 using xhci_hcd [3.231717] Console: switching to colour frame buffer device 240x67 [3.235252] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.235253] i915 :00:02.0: registered panic notifier [3.243430] usb 3-9.2: New USB device found, idVendor=05f3, idProduct=0007 [3.243433] usb 3-9.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [3.247368] input: HID 05f3:0007 as /devices/pci:00/:00:14.0/usb3/3-9/3-9.2/3-9.2:1.0/0003:05F3:0007.0002/input/input8 [3.247421] hid-generic 0003:05F3:0007.0002: input,hidraw1: USB HID v1.00 Keyboard [HID 05f3:0007] on usb-:00:14.0-9.2/input0 [3.253294] input: HID 05f3:0007 as /devices/pci:00/:00:14.0/usb3/3-9/3-9.2/3-9.2:1.1/0003:05F3:0007.0003/input/input9 [3.253348] hid-generic 0003:05F3:0007.0003: input,hidraw2: USB HID v1.00 Device [HID 05f3:0007] on usb-:00:14.0-9.2/input1 [3.261173] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [3.261232] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 [3.261282] [drm] Initialized i915 1.6.0 20140725 for :00:02.0 on minor 0 [3.261306] snd_hda_intel :00:03.0: enabling device ( - 0002) [3.261396] snd_hda_intel :00:1b.0: enabling device ( - 0002) [3.261722] snd_hda_intel :00:03.0: irq 31 for MSI/MSI-X [3.261772] snd_hda_intel :00:1b.0: irq 32 for MSI/MSI-X [3.274888] sound hdaudioC1D0: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [3.274891] sound hdaudioC1D0:speaker_outs=1 (0x1a/0x0/0x0/0x0/0x0) [3.274892] sound hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [3.274893] sound hdaudioC1D0:mono: mono_out=0x0 [3.274894] sound hdaudioC1D0:inputs: [3.274895] sound hdaudioC1D0: Rear Mic=0x18 [3.274896] sound hdaudioC1D0: Front Mic=0x19 [3.274898] sound hdaudioC1D0: Internal Mic=0x12 [3.282002] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input11 [3.282077] input: HDA Intel HDMI HDMI/DP,pcm=7 as
Bug#765685: linux-image-3.16-2-amd64: Kernel lockups with r8723au
Control: tag -1 moreinfo On Fri, 17 Oct 2014 12:14:42 +0200 Mark Brown broo...@debian.org wrote: Package: src:linux Version: 3.16.3-2 Severity: serious The staging driver r8723au is enabled in the kernel but there appear to be very good reasons why it's in staging - when it loads it routinely locks up my system (hard with no output unfortunately). It seems to make sense to disable the driver. [...] We discussed this in person and agreed Mark should test this driver in 3.17 and then we can decide whether to disable it or backport the changes. Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon -- 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/1413555776.23022.1.ca...@decadent.org.uk
Processed: reassign 765691 to src:linux, forcibly merging 762458 762921 765691
Processing commands for cont...@bugs.debian.org: reassign 765691 src:linux 3.17~rc5-1~exp1 Bug #765691 [linux-image-3.17-rc5-amd64] linux-image-3.17-rc5-amd64: nat failure with iptables Bug reassigned from package 'linux-image-3.17-rc5-amd64' to 'src:linux'. No longer marked as found in versions linux/3.17~rc5-1~exp1. Ignoring request to alter fixed versions of bug #765691 to the same values previously set Bug #765691 [src:linux] linux-image-3.17-rc5-amd64: nat failure with iptables Marked as found in versions linux/3.17~rc5-1~exp1. forcemerge 762458 762921 765691 Bug #762458 [src:linux] [src:linux] Please enable CONFIG_IP_NF_NAT Bug #762921 [src:linux] linux-image-3.17-rc5-amd64: Kernel netfilter modules lack NAT support Severity set to 'normal' from 'important' Bug #765691 [src:linux] linux-image-3.17-rc5-amd64: nat failure with iptables Merged 762458 762921 765691 thanks Stopping processing here. Please contact me if you need assistance. -- 762458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762458 762921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762921 765691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765691 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.1413554853687.transcr...@bugs.debian.org
Bug#762458: marked as done ([src:linux] Please enable CONFIG_IP_NF_NAT)
Your message dated Fri, 17 Oct 2014 15:09:14 +0100 with message-id 20141017140914.gb5...@decadent.org.uk and subject line CONFIG_IP_NF_NAT has been enabled has caused the Debian Bug report #762458, regarding [src:linux] Please enable CONFIG_IP_NF_NAT 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.) -- 762458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: linux-image-3.17-rc5-amd64 Severity: normal Between linux version 3.16 and 3.17 the option CONFIG_NF_NAT_IPV4 changed the name to CONFIG_IP_NF_NAT. This option is not enabled in linux-image-3.17-rc5-amd64 Therefore I can't reach the internet from my KVM guest. Please enable this option and the suboptions CONFIG_IP_NF_TARGET_MASQUERADE CONFIG_IP_NF_TARGET_NETMAP CONFIG_IP_NF_TARGET_REDIRECT as modules. Generating a kernel with this options enabled, I can again access the internet. Reinhard --- System information. --- Architecture: amd64 Kernel: Linux 3.17-rc5-amd64 Debian Release: jessie/sid 500 unstabledebian 500 testing debian 500 stable deb.opera.com 101 experimentaldebian --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. ---End Message--- ---BeginMessage--- Version: 3.17-1~exp1 In Linux 3.17, CONFIG_NF_NAT_IPV4 was renamed to CONFIG_IP_NF_NAT. The new config option was enabled in the above Debian version. Ben. -- Ben Hutchings Humour is the best antidote to reality.---End Message---
Processed: Re: Bug#765717: linux-image-3.16-2-amd64: High CPU load with linux-image-3.16-2-amd64
Processing control commands: tag -1 moreinfo Bug #765717 [src:linux] linux-image-3.16-2-amd64: High CPU load with linux-image-3.16-2-amd64 Added tag(s) moreinfo. -- 765717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765717 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.b765717.14135552113415.transcr...@bugs.debian.org
Processed: Re: linux-image-3.16-2-amd64: Kernel lockups with r8723au
Processing control commands: tag -1 moreinfo Bug #765685 [src:linux] linux-image-3.16-2-amd64: Kernel lockups with r8723au Added tag(s) moreinfo. -- 765685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765685 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.b765685.14135557857642.transcr...@bugs.debian.org
Bug#764901: linux-image-3.16-2-amd64: Suspend results in shutdown
Control: severity -1 important Control: tag -1 moreinfo On Sat, 11 Oct 2014 21:44:53 -0600 David Zundel davidzun...@gmail.com wrote: Package: src:linux Version: 3.16.3-2 Severity: critical Justification: causes serious data loss Not unless this causes disk corruption. Dear Maintainer, Following installation of linux-image-3.16-2-amd64 and related, attempts at suspend most often (but not always) result in an unwanted shutdown. Reverting to linux-image-3.14-2-amd64 resolves the problem. Attempted re-installation of linux-image-3.16-2-amd64 generates an error report: Error! Bad return status for module build on kernel: 3.16-2-amd64 (x86_64) Consult /var/lib/dkms/open-vm-tools/2012.05.21/build/make.log for more information. That is a bug in open-vm-tools, not the kernel. -- 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=/vmlinuz-3.16-2-amd64 root=UUID=5051f67f-ea68-41c3-ba22-bb2c1210b21b ro initrd=/install/initrd.gz quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. [...] Please test whether suspend works properly without the Broadcom wireless driver (wl) installed. Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Bug#765717: linux-image-3.16-2-amd64: High CPU load with linux-image-3.16-2-amd64
Hi, Thank you for your message. Look the output of this command : root@zozo:~# ps -e -o state,pid,cmd | grep ^D D 1025 [rtsx_usb_ms_2] root@zozo:~# Le 17.10.2014 15:16, Gregory Fardel a écrit : Package: src:linux Version: 3.16.3-2 Severity: normal Dear Maintainer, From the Debian linux kernel 3.16 (all versions in Jessie and Sid), I have a high CPU load. With a fresh install of Debian Jessie (testing), this load is still present. With a non Debian kernel, this issue is not present. Also tested with the new version of the Linux Kernel, linux-image-3.17-1-amd64 (in Experimental), and I have the same problem. Tested on several machines (Zotac ZBOX IQ01, Dell Latitude E6520). CPU model : Intel(R) Core(TM) i7-4770T CPU @ 2.50GHz top : top - 15:03:26 up 1:44, 2 users, load average: 1.00, 1.00, 0.96 Tasks: 146 total, 1 running, 145 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 16165792 total, 338108 used, 15827684 free,19292 buffers KiB Swap: 4395004 total,0 used, 4395004 free. 143788 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 28632 5064 3192 S 0.0 0.0 0:00.54 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.02 ksoftirqd/0 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H 7 root 20 0 0 0 0 S 0.0 0.0 0:00.18 rcu_sched 8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh 9 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0 10 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/0 11 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/1 12 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/1 13 root 20 0 0 0 0 S 0.0 0.0 0:00.09 ksoftirqd/1 15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:0H 16 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/2 17 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/2 18 root 20 0 0 0 0 S 0.0 0.0 0:00.02 ksoftirqd/2 20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/2:0H 21 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/3 22 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/3 23 root 20 0 0 0 0 S 0.0 0.0 0:00.01 ksoftirqd/3 25 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/3:0H 26 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/4 27 root rt 0 0 0 0 S 0.0 0.0 0:00.04 migration/4 28 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/4 29 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/4:0 30 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/4:0H 31 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/5 32 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/5 33 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/5 35 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/5:0H 36 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/6 37 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/6 38 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/6 40 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/6:0H 41 root rt 0 0 0 0 S 0.0 0.0 0:00.01 watchdog/7 42 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/7 43 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/7 45 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/7:0H 46 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper 47 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs 48 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns 49 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khungtaskd 50 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback 51 root 25 5 0 0 0 S 0.0 0.0 0:00.00 ksmd 52 root 39 19 0 0 0 S 0.0 0.0 0:00.00 khugepaged 53 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto 54 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd 55 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 56 root 0 -20 0
Processed: Re: linux-image-3.16-2-amd64: Suspend results in shutdown
Processing control commands: severity -1 important Bug #764901 [src:linux] linux-image-3.16-2-amd64: Suspend results in shutdown Severity set to 'important' from 'critical' tag -1 moreinfo Bug #764901 [src:linux] linux-image-3.16-2-amd64: Suspend results in shutdown Added tag(s) moreinfo. -- 764901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764901 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.b764901.141355728318658.transcr...@bugs.debian.org
Bug#765731: nfs-kernel-server: Service ordering cycle under systemd
Package: nfs-kernel-server Version: 1:1.2.8-9 Severity: normal Every time I boot, systemd complains about ordering cycles involving nfs-kernel-server: systemd[1]: Found ordering cycle on nfs-kernel-server.service/stop systemd[1]: Breaking ordering cycle by deleting job saned.service/stop systemd[1]: Job saned.service/stop deleted to break ordering cycle starting with nfs-kernel-server.service/stop systemd[1]: Found ordering cycle on nfs-kernel-server.service/stop systemd[1]: Breaking ordering cycle by deleting job fwbuilder.service/stop systemd[1]: Job fwbuilder.service/stop deleted to break ordering cycle starting with nfs-kernel-server.service/stop systemd[1]: Found ordering cycle on nfs-kernel-server.service/stop systemd[1]: Breaking ordering cycle by deleting job openvpn.service/stop systemd[1]: Job openvpn.service/stop deleted to break ordering cycle starting with nfs-kernel-server.service/stop systemd[1]: Found ordering cycle on nfs-kernel-server.service/stop systemd[1]: Breaking ordering cycle by deleting job vmware-workstation-server.service/stop systemd[1]: Job vmware-workstation-server.service/stop deleted to break ordering cycle starting with nfs-kernel-server.service/stop I'm assuming this is a problem with nfs-kernel-server since it is the common thread here, but I don't know if that is a valid assumption. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 41435 status 1000241 tcp 60482 status 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 1002272 tcp 2049 1002273 tcp 2049 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 1002272 udp 2049 1002273 udp 2049 1000211 udp 40131 nlockmgr 1000213 udp 40131 nlockmgr 1000214 udp 40131 nlockmgr 1000211 tcp 48655 nlockmgr 1000213 tcp 48655 nlockmgr 1000214 tcp 48655 nlockmgr 151 udp 36503 mountd 151 tcp 58760 mountd 152 udp 33164 mountd 152 tcp 32793 mountd 153 udp 42392 mountd 153 tcp 47614 mountd -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS=--manage-gids NEED_SVCGSSD=no RPCSVCGSSDOPTS= -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-kernel-server depends on: ii libblkid1 2.20.1-5.11 ii libc6 2.19-11 ii libcap2 1:2.24-6 ii libsqlite3-0 3.8.6-1 ii libtirpc1 0.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13 ii nfs-common1:1.2.8-9 ii ucf 3.0030 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information -- 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/20141017155712.7729.65289.report...@harkonnen.beechwoods.com
Processing of linux-tools_3.17-1~exp1_multi.changes
linux-tools_3.17-1~exp1_multi.changes uploaded successfully to localhost along with the files: linux-tools_3.17-1~exp1.dsc linux-tools_3.17.orig.tar.xz linux-tools_3.17-1~exp1.debian.tar.xz linux-kbuild-3.17_3.17-1~exp1_i386.deb libusbip-dev_2.0+3.17-1~exp1_i386.deb usbip_2.0+3.17-1~exp1_i386.deb linux-tools-3.17_3.17-1~exp1_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1xfa84-0006hc...@franck.debian.org
Re: [PATCH v2 1/5] m25p80,spi-nor: Fix module aliases for m25p80
On Thu, Oct 09, 2014 at 09:51:26PM -0700, Brian Norris wrote: On Tue, Sep 30, 2014 at 03:14:55AM +0100, Ben Hutchings wrote: m25p80's device ID table is now spi_nor_ids, defined in spi-nor. The MODULE_DEVICE_TABLE() macro doesn't work with extern definitions, but its use was also removed at the same time. Now if m25p80 is built as a module it doesn't get the necessary aliases to be loaded automatically. 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. As a quick fix suitable for stable, copy the device IDs back into m25p80. Fixes: 03e296f613af (mtd: m25p80: use the SPI nor framework) Cc: stable sta...@vger.kernel.org # 3.16.x: 32f1b7c8352f: mtd: move support for struct flash_platform_data into m25p80 Cc: stable sta...@vger.kernel.org # 3.16.x Signed-off-by: Ben Hutchings b...@decadent.org.uk Can I get any acks/tested-by's? I'll try to test this out when I get back to the office, but I'd like to be able to send this in the 3.18 cycle still. Applied this patch to l2-mtd/master. Thanks! Acks/tested-by's are still welcome. I plan to send this out in 3.18 (maybe for -rc2) if things look good. Brian -- 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/20141017162335.GG22169@norris-Latitude-E6410
linux-tools_3.17-1~exp1_multi.changes is NEW
binary:linux-kbuild-3.17 is NEW. binary:linux-tools-3.17 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html -- 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/e1xfaju-0001ck...@franck.debian.org
Re: [PATCH v2 1/5] m25p80,spi-nor: Fix module aliases for m25p80
On Fri, 2014-10-17 at 09:35 -0700, Brian Norris wrote: On Fri, Oct 17, 2014 at 09:23:35AM -0700, Brian Norris wrote: On Thu, Oct 09, 2014 at 09:51:26PM -0700, Brian Norris wrote: On Tue, Sep 30, 2014 at 03:14:55AM +0100, Ben Hutchings wrote: m25p80's device ID table is now spi_nor_ids, defined in spi-nor. The MODULE_DEVICE_TABLE() macro doesn't work with extern definitions, but its use was also removed at the same time. Now if m25p80 is built as a module it doesn't get the necessary aliases to be loaded automatically. 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. As a quick fix suitable for stable, copy the device IDs back into m25p80. Fixes: 03e296f613af (mtd: m25p80: use the SPI nor framework) Cc: stable sta...@vger.kernel.org # 3.16.x: 32f1b7c8352f: mtd: move support for struct flash_platform_data into m25p80 Cc: stable sta...@vger.kernel.org # 3.16.x Signed-off-by: Ben Hutchings b...@decadent.org.uk Can I get any acks/tested-by's? I'll try to test this out when I get back to the office, but I'd like to be able to send this in the 3.18 cycle still. Applied this patch to l2-mtd/master. Thanks! Scratch that; I took Rafal's rebased version found at: git://git.infradead.org/users/rafal/mtd.git Thanks! Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Re: [PATCH 2/2] mtd: spi-nor: make spi_nor_scan() take a chip type name, not spi_device_id
On Mon, Sep 29, 2014 at 11:47:54AM +0200, Rafał Miłecki wrote: From: Ben Hutchings b...@decadent.org.uk Drivers currently call spi_nor_match_id() and then spi_nor_scan(). This adds a dependency on struct spi_device_id which we want to avoid. Make spi_nor_scan() do it for them. Signed-off-by: Ben Hutchings b...@decadent.org.uk Signed-off-by: Rafał Miłecki zaj...@gmail.com Pushed to l2-mtd.git/master. Brian -- 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/20141017163109.GI22169@norris-Latitude-E6410
Re: [PATCH 1/2] mtd: m25p80: get rid of spi_get_device_id
On Mon, Sep 29, 2014 at 11:47:53AM +0200, Rafał Miłecki wrote: This simplifies the way we use spi_nor framework and will allow us to drop spi_nor_match_id. Signed-off-by: Rafał Miłecki zaj...@gmail.com Applied to l2-mtd.git/master. Brian -- 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/20141017163023.GH22169@norris-Latitude-E6410
Re: [PATCH v2 1/5] m25p80,spi-nor: Fix module aliases for m25p80
On Fri, Oct 17, 2014 at 09:23:35AM -0700, Brian Norris wrote: On Thu, Oct 09, 2014 at 09:51:26PM -0700, Brian Norris wrote: On Tue, Sep 30, 2014 at 03:14:55AM +0100, Ben Hutchings wrote: m25p80's device ID table is now spi_nor_ids, defined in spi-nor. The MODULE_DEVICE_TABLE() macro doesn't work with extern definitions, but its use was also removed at the same time. Now if m25p80 is built as a module it doesn't get the necessary aliases to be loaded automatically. 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. As a quick fix suitable for stable, copy the device IDs back into m25p80. Fixes: 03e296f613af (mtd: m25p80: use the SPI nor framework) Cc: stable sta...@vger.kernel.org # 3.16.x: 32f1b7c8352f: mtd: move support for struct flash_platform_data into m25p80 Cc: stable sta...@vger.kernel.org # 3.16.x Signed-off-by: Ben Hutchings b...@decadent.org.uk Can I get any acks/tested-by's? I'll try to test this out when I get back to the office, but I'd like to be able to send this in the 3.18 cycle still. Applied this patch to l2-mtd/master. Thanks! Scratch that; I took Rafal's rebased version found at: git://git.infradead.org/users/rafal/mtd.git Brian -- 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/20141017163500.GJ22169@norris-Latitude-E6410
Processed: reassign 754354 to src:linux, found 754354 in 3.2.60-1+deb7u3, severity of 754354 is important
Processing commands for cont...@bugs.debian.org: reassign 754354 src:linux 3.2.60-1+deb7u1 Bug #754354 [nfs-kernel-server] nfs-kernel-server: hangs after hours or days, no login to server possible Bug reassigned from package 'nfs-kernel-server' to 'src:linux'. No longer marked as found in versions nfs-utils/1:1.2.6-4. Ignoring request to alter fixed versions of bug #754354 to the same values previously set Bug #754354 [src:linux] nfs-kernel-server: hangs after hours or days, no login to server possible Marked as found in versions linux/3.2.60-1+deb7u1. found 754354 3.2.60-1+deb7u3 Bug #754354 [src:linux] nfs-kernel-server: hangs after hours or days, no login to server possible Marked as found in versions linux/3.2.60-1+deb7u3. severity 754354 important Bug #754354 [src:linux] nfs-kernel-server: hangs after hours or days, no login to server possible Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 754354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754354 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.14135638651932.transcr...@bugs.debian.org
Re: Bug#765380: don't ship gcc-4.8 with jessie
On Tue, Oct 14, 2014 at 05:25:13PM +0200, Matthias Klose wrote: Package: src:gcc-4.8 Version: 4.8.3-11 Severity: serious Tags: sid jessie The current default for GCC (4.9) is good enough for jessie. Don't ship legacy compilers with jessie. Hi Matthias, Removing GCC 4.8 will need Linux kernel ABI transitions. I haven't seen any discussion on the debian-kernel list, and the latest of the Linux package (uploaded to sid this week) still has it generating linux-compiler-* packages depending on gcc-4.8, so I think the Linux maintainers are expecting GCC 4.8 to be in Jessie. (CC'ing the debian-kernel list for comments) Regards, Steve -- 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/2014101717.ga2...@s.cotton.clara.co.uk
Re: Bug#765380: don't ship gcc-4.8 with jessie
Am 17.10.2014 um 19:44 schrieb Steve Cotton: On Tue, Oct 14, 2014 at 05:25:13PM +0200, Matthias Klose wrote: Package: src:gcc-4.8 Version: 4.8.3-11 Severity: serious Tags: sid jessie The current default for GCC (4.9) is good enough for jessie. Don't ship legacy compilers with jessie. Hi Matthias, Removing GCC 4.8 will need Linux kernel ABI transitions. I haven't seen any discussion on the debian-kernel list, and the latest of the Linux package (uploaded to sid this week) still has it generating linux-compiler-* packages depending on gcc-4.8, so I think the Linux maintainers are expecting GCC 4.8 to be in Jessie. This was communicated to Ben Hutching at DebConf, so plenty of time to prepare the change. Are there known showstoppers? Matthias -- 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/54415eca.6030...@debian.org
linux-tools_3.17-1~exp1_multi.changes ACCEPTED into experimental, experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Oct 2014 14:58:51 +0200 Source: linux-tools Binary: linux-kbuild-3.17 linux-tools-3.17 libusbip-dev usbip Architecture: i386 source Version: 3.17-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Description: libusbip-dev - USB device sharing system over IP network (development files) linux-kbuild-3.17 - Kbuild infrastructure for Linux 3.17 linux-tools-3.17 - Performance analysis tools for Linux 3.17 usbip - USB device sharing system over IP network Changes: linux-tools (3.17-1~exp1) experimental; urgency=medium . * New upstream release - usbip userspace moved to tools/usb/usbip Checksums-Sha1: 4d01befcc32a38540267dd043cecb577ba2034c2 2566 linux-tools_3.17-1~exp1.dsc ceee5c946912eeddaff5e00654537b152e7929b2 7919696 linux-tools_3.17.orig.tar.xz 298b4c6f491f183a0d458c857e8aae2ec992952d 22988 linux-tools_3.17-1~exp1.debian.tar.xz cdba716a195f2ccc4e65830bb90738c6f2abada2 176028 linux-kbuild-3.17_3.17-1~exp1_i386.deb f36a2940abe030c3556f2dd9a71752812c6945ef 23294 libusbip-dev_2.0+3.17-1~exp1_i386.deb fe9e4f3137f5118226d23c885bb6419e9453be7e 37242 usbip_2.0+3.17-1~exp1_i386.deb 0d25cb8d6f7221d5995b6c8244258a33f1ec642b 574832 linux-tools-3.17_3.17-1~exp1_i386.deb Checksums-Sha256: 11f1566f1a536fa8cf084168f13d2d51d75bf28ad7d9f21ae2ab0041e72f159f 2566 linux-tools_3.17-1~exp1.dsc 51162320841053fcf06070b6d5a6d984fb4c429e3ba3dc6d4eec021d374b926f 7919696 linux-tools_3.17.orig.tar.xz ab971d5026b33cf041ea7525b57731176ca828f9df3caf7efb36297e7282ee2a 22988 linux-tools_3.17-1~exp1.debian.tar.xz c6b3e9419b145cb1e0eb45bcc90a7454450b5e23e2c2371fcc340c0faeaf7ffb 176028 linux-kbuild-3.17_3.17-1~exp1_i386.deb 94c42b8e22b19b07f38dfe1860ab0a81200db33c7ddd516a4e80ca68f9d8a68e 23294 libusbip-dev_2.0+3.17-1~exp1_i386.deb 4cc8c7ea83fd25cca3cd3fba15ac168698dbd1e8192248e98fdd29e6972e2aa9 37242 usbip_2.0+3.17-1~exp1_i386.deb 77c7c08d07f25e2e00300e0531784fe4b396264795bd904f4546e6772486b449 574832 linux-tools-3.17_3.17-1~exp1_i386.deb Files: e4e0763f8451256633704cdb7e56728c 2566 kernel optional linux-tools_3.17-1~exp1.dsc 6c78f25c86761a60b89235e12bc109a8 7919696 kernel optional linux-tools_3.17.orig.tar.xz fa1ba1ed2fdf7fa79d8b5e2b36da0829 22988 kernel optional linux-tools_3.17-1~exp1.debian.tar.xz a10040830fab8d5c61dc4d326bbe5387 176028 kernel optional linux-kbuild-3.17_3.17-1~exp1_i386.deb aff4beb8497023f408d7d0fa6f95f556 23294 libdevel optional libusbip-dev_2.0+3.17-1~exp1_i386.deb 8074b53c454407397158792fd04feea3 37242 admin optional usbip_2.0+3.17-1~exp1_i386.deb ea2e60c334a859c556011f015a757ad4 574832 devel optional linux-tools-3.17_3.17-1~exp1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVEE+xee/yOyVhhEJAQoGYBAAxcK3j98BZbBRY2lzELp2ps9kxAMYHRJy vn/r2mIKuHmUDuUfOd/nhxVEy33aNGNkVBEC73003etGHj2vhOARROTe2LOV3kO6 c9eaG/cM74AaBjTuV8/9h8Bta6VGBStQQ0+1fm/mdI1do1DfI+MOFnfqbNZLOm1/ fetIeZQUhmQCEZocTZEQG3uOSDAdRrGtV2bIf9B4/RNkL/JIUDKGokIAjst8GXCb PoCAbSJPwjC5+j1DkC7AdZ+Az3jTrYi+ilpUhBC07jEp7p/y3cZ+SO0Th/NtUdMw XsuxnYT5YFd1GWdTULtgFLlIyCagq/kN7FK5NSZJCYaPcwnSHNdPwgHsEA2/fHuX DrN/gQsIgEDsVdE+SdLtaLjUkWG6ZTy+bwANcJDOM3bl/+99Zfk8YWHKEJ7MoKKo kABPFfEVGQrlXlA+A/mr8vwNiU7EZS80Q8v8Ld2MAfcJpb39afZAkizGt1WOiXTX ywVcBHGr0XulipCL6lV/5gABBR3hYhcM3ecPvdqP/aFHeumZtvdsHXtxHCM5OQgw mv32+PxTI3poK+yv28YYp8IU8JQiNlXwGY9o4fG3xyozLxNFd0eXKiEXIc07oTCo 8Snmn/7Qk1VEhXOd08b8b4av6w6zSgxRSOpNjWc+/a21+RVDMryGVuVWRf6Q+K42 PeR4i4VAHE0= =Nq9E -END PGP SIGNATURE- Thank you for your contribution to Debian. -- 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/e1xfckw-0005fi...@franck.debian.org
Bug#765750: initramfs-tools: should probably recreate initrd after installing
Package: initramfs-tools Version: 0.116 When I install dracut, a new initrd is generated automatically using dracut. If I install initramfs-tools again, dracut is removed but this time a new initrd (generated by initramfs-tools) is not generated. I see a lot of danger here. Either initrds are generated automatically or they are not. If they are, installing dracut and then reinstalling initramfs-tools should leave the system in the same state as before. This is particularly important because initrds generated by dracut are not always suitable for everybody so the user might reasonably expect that reinstalling initramfs-tools should create a safe initrd again. Not sure avout the severity of this bug, but it seems that more and more people are using dracut, so this might eventually become a real serious problem and will bite us. Thanks. -- 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/alpine.deb.2.11.1410172053010.31...@cantor.unex.es
