Bug#670492: linux-image-2.6.32-5-amd64: RTL8111/8168B Wake on LAN does not work
Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: normal The title says it all. I already tried the ethtool setting from the debian wiki. No success. I found one solution by using the r8168 driver from realtek. With this driver WOL works. The r8168 driver has an other problem. Sometimes the pc does not wake up from Suspend to Ram. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Mar 22 17:26:33 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=bc115a2e-a23d-4c00-9b7e-b30b2040006e ro quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [ 554.552019] SMP alternatives: switching to UP code [ 554.562694] PM: Creating hibernation image: [ 554.564006] PM: Need to copy 100351 pages [ 554.564006] PM: Normal pages needed: 100351 + 1024, available pages: 685633 [ 554.564006] PM: Restoring platform NVS memory [ 554.564006] CPU0: Thermal monitoring handled by SMI [ 554.564006] Force enabled HPET at resume [ 554.564006] Enabling non-boot CPUs ... [ 554.564006] SMP alternatives: switching to SMP code [ 554.572812] Booting processor 1 APIC 0x1 ip 0x6000 [ 554.564006] Initializing CPU#1 [ 554.564006] CPU: Trace cache: 12K uops, L1 D cache: 16K [ 554.564006] CPU: L2 cache: 1024K [ 554.564006] CPU 1/0x1 - Node 0 [ 554.564006] CPU: Physical Processor ID: 0 [ 554.564006] CPU: Processor Core ID: 1 [ 554.564006] CPU1: Thermal monitoring handled by SMI [ 554.660124] CPU1: Intel(R) Pentium(R) D CPU 3.20GHz stepping 04 [ 554.660265] CPU0 attaching NULL sched-domain. [ 554.688046] CPU0 attaching sched-domain: [ 554.688051] domain 0: span 0-1 level CPU [ 554.688054] groups: group 88000180fd00 cpus 0 group 88000190fd00 cpus 1 [ 554.688064] CPU1 attaching sched-domain: [ 554.688067] domain 0: span 0-1 level CPU [ 554.688070] groups: group 88000190fd00 cpus 1 group 88000180fd00 cpus 0 [ 554.688446] CPU1 is up [ 554.689087] ACPI: Waking up from system sleep state S4 [ 554.690227] Intel ICH :00:1e.2: restoring config space at offset 0x1 (was 0x297, writing 0x293) [ 554.690294] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 0x2880001, writing 0x2880005) [ 554.690324] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407) [ 554.690402] radeon :01:00.0: restoring config space at offset 0x1 (was 0x100107, writing 0x100507) [ 554.690493] tg3 :03:00.0: restoring config space at offset 0xc (was 0x0, writing 0x7823) [ 554.690581] r8168 :04:00.0: restoring config space at offset 0x3 (was 0x8, writing 0x20) [ 554.690590] r8168 :04:00.0: restoring config space at offset 0x1 (was 0x100147, writing 0x100547) [ 554.704035] firewire_ohci :0a:09.0: restoring config space at offset 0xf (was 0x4020100, writing 0x4020105) [ 554.704056] firewire_ohci :0a:09.0: restoring config space at offset 0x3 (was 0x0, writing 0x4008) [ 554.704063] firewire_ohci :0a:09.0: restoring config space at offset 0x1 (was 0x210, writing 0x2100156) [ 554.767951] uhci_hcd :00:1d.0: setting latency timer to 64 [ 554.767988] usb usb2: root hub lost power or was reset [ 554.768038] uhci_hcd :00:1d.1: setting latency timer to 64 [ 554.768072] usb usb3: root hub lost power or was reset [ 554.768089] uhci_hcd :00:1d.2: setting latency timer to 64 [ 554.768121] usb usb4: root hub lost power or was reset [ 554.768139] uhci_hcd :00:1d.3: setting latency timer to 64 [ 554.768171] usb usb5: root hub lost power or was reset [ 554.768189] ehci_hcd :00:1d.7: setting latency timer to 64 [ 554.768194] usb usb1: root hub lost power or was reset [ 554.772068] ehci_hcd :00:1d.7: cache line size of 128 is not supported [ 554.772084] pci :00:1e.0: setting latency timer to 64 [ 554.772099] Intel ICH :00:1e.2: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 554.772105] Intel ICH :00:1e.2: setting latency timer to 64 [ 554.781906] ata_piix :00:1f.1: PCI INT A - GSI 18 (level, low) - IRQ 18 [ 554.781912] ata_piix :00:1f.1: setting latency timer to 64 [ 554.782030] ahci :00:1f.2: setting latency timer to 64 [ 554.782110] radeon :01:00.0: setting latency timer to 64 [ 554.793759] [drm] Clocks initialized ! [ 554.840950] [drm] ring test succeeded in 1 usecs [ 554.840966] [drm] ib test succeeded in 0 usecs [ 554.840969] [drm] Enabling audio support [ 554.856092] tg3 :03:00.0: wake-up capability disabled by ACPI [ 554.856099] tg3 :03:00.0: PME# disabled [ 554.928044] firewire_core: skipped bus generations, destroying all nodes [ 554.929136] parport_pc 00:08: activated [ 554.929812] serial 00:09: activated [ 554.930477] serial 00:0a: activated [ 554.930582] i8042 aux 00:0b: activated [ 554.952268] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered
Bug#670496: initramfs-tools: [patch] fixes missing/ignored $tmpfs_size in the init script
Package: initramfs-tools Version: 0.102 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? The mouted size of /dev is larger then 10M (which is default, in the init script itself). * What exactly did you do (or not do) that was effective (or ineffective)? On examining the /usr/share/initramfs-tools/init I found a skipp over or typo. * What was the outcome of this action? I patched the init script, rebuild/updated /boot/initrd-whatever using update-initramfs -u; rebooted the system and report size now is 10M :) * What outcome did you expect instead? The udevfs/tmfs size for the /dev should be 10M (default) or as per /etc/udev/udev.conf -- Package-specific info: -- initramfs sizes -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=6f57d8ea-bb70-4e9e-9cba-21b3e9fa75ab ro nomodeset splash quiet -- resume RESUME=UUID=63e8707b-45be-4bfe-a203-c73223653920 -- /proc/filesystems ext3 fuseblk ufs vfat iso9660 -- lsmod Module Size Used by pci_stub 12429 1 vboxpci19066 0 vboxnetadp 13155 0 vboxnetflt 23571 0 vboxdrv 190057 3 vboxnetflt,vboxnetadp,vboxpci microcode 25793 0 ppdev 12763 0 lp 17149 0 binfmt_misc12957 1 nfnetlink_log 17212 0 nfnetlink 12906 1 nfnetlink_log uinput 17440 1 deflate12551 0 zlib_deflate 25638 1 deflate ctr12979 0 twofish_generic16569 0 twofish_x86_64_3way25167 0 twofish_x86_64 12501 1 twofish_x86_64_3way twofish_common 20544 3 twofish_x86_64,twofish_x86_64_3way,twofish_generic camellia 29068 0 serpent29015 0 blowfish_generic 12464 0 blowfish_x86_6421201 0 blowfish_common16447 2 blowfish_x86_64,blowfish_generic cast5 24829 0 des_generic20851 0 cbc12754 0 cryptd 14517 0 aes_x86_64 16796 0 aes_generic33026 1 aes_x86_64 xcbc 12709 0 rmd160 16640 0 sha512_generic 12625 0 sha256_generic 16797 0 sha1_ssse3 16983 0 sha1_generic 12539 1 sha1_ssse3 hmac 12835 0 crypto_null12732 0 af_key 31759 2 acpi_cpufreq 12935 0 mperf 12453 1 acpi_cpufreq cpufreq_powersave 12454 0 cpufreq_conservative13147 0 cpufreq_userspace 12576 0 cpufreq_stats 12866 0 nfsd 211858 13 nfs 312191 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 1 nfs lockd 67328 2 nfs,nfsd sunrpc173671 19 lockd,auth_rpcgss,nfs_acl,nfs,nfsd sit17561 0 tunnel412629 1 sit ip6t_LOG 12609 3 ip6t_REJECT12512 23 nf_conntrack_ipv6 13316 34 nf_defrag_ipv6 12788 1 nf_conntrack_ipv6 ip6table_mangle12540 1 ip6table_filter12540 1 ip6_tables 22175 3 ip6table_filter,ip6table_mangle,ip6t_LOG ipt_LOG12605 3 ipt_REJECT 12502 23 xt_recent 13188 10 xt_limit 12638 18 xt_state 12503 66 xt_connlimit 12622 2 iptable_nat12928 1 nf_nat 18242 1 iptable_nat nf_conntrack_ipv4 14078 37 nf_nat,iptable_nat nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 nf_conntrack 52720 6 nf_conntrack_ipv4,nf_nat,iptable_nat,xt_connlimit,xt_state,nf_conntrack_ipv6 xt_TCPMSS 12670 2 xt_tcpudp 12570 130 iptable_mangle 12536 1 iptable_filter 12536 1 ip_tables 22042 3 iptable_filter,iptable_mangle,iptable_nat x_tables 19073 17 ip_tables,iptable_filter,iptable_mangle,xt_tcpudp,xt_TCPMSS,iptable_nat,xt_connlimit,xt_state,xt_limit,xt_recent,ipt_REJECT,ipt_LOG,ip6_tables,ip6table_filter,ip6table_mangle,ip6t_REJECT,ip6t_LOG nls_utf8 12456 2 isofs 35171 2 loop 22641 4 nls_cp437 16553 2 vfat 17316 1 fat45642 1 vfat ufs58774 4 fuse 61981 3 usbhid 36379 0 hid81288 1 usbhid pl2303 17262 0 usbserial 32061 1 pl2303 usb_storage43870 0 uvcvideo 57744 0 videodev 70889 1 uvcvideo v4l2_compat_ioctl3216655 1 videodev media 18148 2 videodev,uvcvideo i2c_core 23876 1 videodev uas13296 0
Bug#670398: linux-image-2.6.32-5-amd64: SSH logins hang while hpet interrupts multiply on Intel Nehalem CPUs
On Thu, Apr 26, 2012 at 04:49:56AM +0100, Ben Hutchings wrote: On Wed, 2012-04-25 at 10:36 +0200, Sven Hoexter wrote: Hi, Searching through munin graphs we could narrow down the starting point of this issue to the point when the hpet interrupts for one CPU core multiplied. Sometimes they multiplied by six. Looking further we've found the Kernel [events/$x] in state D where $x is the number of the CPU core which has the high number of hpet interrupts. When we started strace -f on the sshd master process everything works until you logout. Then you'll again see the forked sshd process hanging in state D. This is strange, because D state means uninterruptible sleep (not handling signals). But perhaps the sshd process was repeatedly changing between uninterruptible and interruptible state. Is it possible to gather such data? I guess grep'ing through ps output is not the right tool here. From a system currently suffering from this issue: ps aux|grep D USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root15 0.0 0.0 0 0 ?DApr25 0:53 [events/0] root 4162 0.0 0.0 0 0 ?Ds 08:33 0:00 [bash] 480 7875 0.0 0.0 0 0 ?Ds 09:28 0:00 [bash] root 9407 0.0 0.0 76644 3392 ?Ds 09:49 0:00 sshd: root@pts/79 480 11310 0.0 0.0 8940 884 ?S09:59 0:00 grep D 480 11765 0.0 0.0 0 0 ?Ds Apr25 0:00 [bash] root 12803 0.0 0.0 76644 3392 ?Ds Apr25 0:00 sshd: root@pts/12 root 13762 0.0 0.0 76644 3392 ?Ds Apr25 0:00 sshd: root@pts/73 root 15111 0.0 0.0 0 0 ?Ds Apr25 0:00 [bash] root 19361 0.0 0.0 0 0 ?Ds Apr25 0:00 [bash] root 20966 0.0 0.0 0 0 ?Ds Apr25 0:00 [bash] root 29323 0.0 0.0 0 0 ?Ds Apr25 0:00 [bash] Sven -- 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/20120426080254.ga4...@sho.bk.hosteurope.de
Bug#670398: linux-image-2.6.32-5-amd64: SSH logins hang while hpet interrupts multiply on Intel Nehalem CPUs
On Wed, Apr 25, 2012 at 09:33:44PM -0700, John Stultz wrote: Hi, When you can connect to the system that is having problems, do you see any problems with the time? ie: does date show the correct time, and does it increment normally? I don't see any jumps in time here: while true; do /sbin/hwclock --show; date; done Thu 26 Apr 2012 09:50:19 AM CEST -0.781566 seconds Thu Apr 26 09:50:18 CEST 2012 Thu 26 Apr 2012 09:50:20 AM CEST -1.000351 seconds Thu Apr 26 09:50:19 CEST 2012 Thu 26 Apr 2012 09:50:21 AM CEST -1.000321 seconds Thu Apr 26 09:50:20 CEST 2012 Thu 26 Apr 2012 09:50:22 AM CEST -1.000299 seconds Thu Apr 26 09:50:21 CEST 2012 Thu 26 Apr 2012 09:50:23 AM CEST -1.000342 seconds Thu Apr 26 09:50:22 CEST 2012 Thu 26 Apr 2012 09:50:24 AM CEST -1.000315 seconds Thu Apr 26 09:50:23 CEST 2012 Thu 26 Apr 2012 09:50:25 AM CEST -0.984703 seconds Thu Apr 26 09:50:24 CEST 2012 Thu 26 Apr 2012 09:50:26 AM CEST -1.000319 seconds Thu Apr 26 09:50:25 CEST 2012 Thu 26 Apr 2012 09:50:27 AM CEST -1.000324 seconds Thu Apr 26 09:50:26 CEST 2012 Thu 26 Apr 2012 09:50:28 AM CEST -1.000320 seconds Thu Apr 26 09:50:27 CEST 2012 Thu 26 Apr 2012 09:50:29 AM CEST -1.000326 seconds Thu Apr 26 09:50:28 CEST 2012 Thu 26 Apr 2012 09:50:30 AM CEST -1.000307 seconds Thu Apr 26 09:50:29 CEST 2012 Thu 26 Apr 2012 09:50:31 AM CEST -1.000337 seconds Thu Apr 26 09:50:30 CEST 2012 Thu 26 Apr 2012 09:50:32 AM CEST -1.004597 seconds Thu Apr 26 09:50:32 CEST 2012 Thu 26 Apr 2012 09:50:33 AM CEST -0.984694 seconds Thu Apr 26 09:50:32 CEST 2012 Thu 26 Apr 2012 09:50:34 AM CEST -1.000320 seconds Thu Apr 26 09:50:33 CEST 2012 Thu 26 Apr 2012 09:50:35 AM CEST -1.000321 seconds Thu Apr 26 09:50:34 CEST 2012 Thu 26 Apr 2012 09:50:36 AM CEST -1.000320 seconds Thu Apr 26 09:50:35 CEST 2012 Thu 26 Apr 2012 09:50:37 AM CEST -1.000321 seconds Thu Apr 26 09:50:36 CEST 2012 Thu 26 Apr 2012 09:50:38 AM CEST -1.004611 seconds Thu Apr 26 09:50:38 CEST 2012 Thu 26 Apr 2012 09:50:39 AM CEST -0.984718 seconds Thu Apr 26 09:50:38 CEST 2012 Thu 26 Apr 2012 09:50:40 AM CEST -1.000274 seconds Thu Apr 26 09:50:39 CEST 2012 Thu 26 Apr 2012 09:50:41 AM CEST -1.000315 seconds It sounds like if there is some HPET irq issue, it would likely be due to some sort of global wakeup to handle local apics that halt in deep sleep modes. Its likely that getting /proc/timer_list output would help (both before and after the problem). I've attached /proc/timer_list from a system that is currently suffering from this problem. Unfortunately I've not the state before. I can only grab it from a system that is currently not effected but suffered in the past if it helps? Regards, Sven Timer List Version: v0.5 HRTIMER_MAX_CLOCK_BASES: 2 now at 83615781793881 nsecs cpu: 0 clock 0: .base: 880008a100c8 .index: 0 .resolution: 1 nsecs .get_time: ktime_get_real .offset: 1335342613769994271 nsecs active timers: #0: 8801a0967d08, hrtimer_wakeup, S:01, futex_wait_queue_me, java/18099 # expires at 1335426229557084000-1335426229557134000 nsecs [in 1335342613775290119 to 1335342613775340119 nsecs] #1: 88023deb7d08, hrtimer_wakeup, S:01, futex_wait_queue_me, java/18106 # expires at 1335426254026767000-1335426254026817000 nsecs [in 1335342638244973119 to 1335342638245023119 nsecs] #2: 8801f184dd08, hrtimer_wakeup, S:01, futex_wait_queue_me, java/18105 # expires at 1335426270572844000-1335426270572894000 nsecs [in 1335342654791050119 to 1335342654791100119 nsecs] #3: 8801f3d9bd08, hrtimer_wakeup, S:01, futex_wait_queue_me, java/18110 # expires at 1335426275040889000-1335426275040939000 nsecs [in 1335342659259095119 to 1335342659259145119 nsecs] #4: 8801a097fd08, hrtimer_wakeup, S:01, futex_wait_queue_me, java/18111 # expires at 133542628422666-133542628422671 nsecs [in 1335342668444866119 to 1335342668444916119 nsecs] clock 1: .base: 880008a10108 .index: 1 .resolution: 1 nsecs .get_time: ktime_get .offset: 0 nsecs active timers: #0: 880008a101b0, tick_sched_timer, S:01, tick_nohz_restart_sched_tick, swapper/0 # expires at 8361578400-8361578400 nsecs [in 2206119 to 2206119 nsecs] #1: 88021ebbb968, hrtimer_wakeup, S:01, schedule_hrtimeout_range, init/5900 # expires at 83616008255524-83616013255522 nsecs [in 226461643 to 231461641 nsecs] #2: 8802181f1968, hrtimer_wakeup, S:01, schedule_hrtimeout_range, init/6795 # expires at 83616584188235-83616589188233 nsecs [in 802394354 to 807394352 nsecs] #3: 88021d9af968, hrtimer_wakeup, S:01, schedule_hrtimeout_range, init/6032 # expires at 83616708138883-83616713138881 nsecs [in 926345002 to 931345000 nsecs] #4: 88023030d968, hrtimer_wakeup, S:01, schedule_hrtimeout_range, mysqld/4211 # expires at 83616968110539-83616973110538 nsecs [in 1186316658 to 1191316657 nsecs] #5: 880215f7b968, hrtimer_wakeup, S:01, schedule_hrtimeout_range, init/7172 # expires at
Bug#670505: linux-image-3.2.0-0.bpo.2-amd64: 3.2.{14, 15} regression: NFS delegation problems
Package: linux-2.6 Version: 3.2.15-1~bpo60+1 Severity: important Hi, It seems stable update 3.2.14 or 3.2.15 introduced a regression regarding NFS4 delegations. It seems to be the same issue as reported here[1] against the 3.3 kernel. It was also intruduced there between 3.3.0 and 3.3.1. [1] https://bugzilla.redhat.com/show_bug.cgi?id=811138 The following BUG is triggered when logging into gnome, but seems to be easily reproduceable by using flock (see Fedora bug report). Apr 25 14:06:02 bach gdm-simple-greeter[2320]: WARNING: Failed to send buffer Apr 25 14:06:05 bach kernel: [ 78.797185] BUG: unable to handle kernel paging request at ffb8 Apr 25 14:06:05 bach kernel: [ 78.797233] IP: [a048f016] nfs_mark_delegation_referenced+0x6/0x6 [nfs] Apr 25 14:06:05 bach kernel: [ 78.797289] PGD 1607067 PUD 1608067 PMD 0 Apr 25 14:06:05 bach kernel: [ 78.797319] Oops: [#1] SMP Apr 25 14:06:05 bach kernel: [ 78.797344] CPU 3 Apr 25 14:06:05 bach kernel: [ 78.797357] Modules linked in: autofs4 acpi_cpufreq mperf cpufreq_stats cpufreq_userspace cpufreq_powersave cpufreq_conservative ip6_tables ppdev lp bridge stp bnep rfcomm bluetooth rfkill tun binfmt_misc uinput kvm_intel kvm fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables ext3 jbd loop snd_hda_codec_analog ses enclosure snd_hda_intel snd_hda_codec snd_hwdep i915 snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device joydev snd drm_kms_helper usbhid usb_storage hid evdev dell_wmi soundcore parport_pc i2c_i801 drm i2c_algo_bit i2c_core processor uas button video snd_page_alloc pcspkr sparse_keymap parport tpm_tis tpm tpm_bios wmi dcdbas psmouse serio_raw thermal_sys ext4 mbcache jbd2 crc16 dm_mod sg sr_mod sd_mod cdrom crc_t10dif uhci_hcd ahci libahci ata_generic ehci_hcd lib ata e1000e usbcore scsi_mod usb_com Apr 25 14:06:05 bach kernel: mon [last unloaded: scsi_wait_scan] Apr 25 14:06:05 bach kernel: [ 78.798038] Apr 25 14:06:05 bach kernel: [ 78.798050] Pid: 3095, comm: gnome-keyring-d Not tainted 3.2.0-0.bpo.2-amd64 #1 Dell Inc. OptiPlex 760 /0M858N Apr 25 14:06:05 bach kernel: [ 78.798114] RIP: 0010:[a048f016] [a048f016] nfs_mark_delegation_referenced+0x6/0x6 [nfs] Apr 25 14:06:05 bach kernel: [ 78.798177] RSP: 0018:88021eca9e40 EFLAGS: 00010246 Apr 25 14:06:05 bach kernel: [ 78.798206] RAX: 88021eca5000 RBX: d8ca RCX: d8ca Apr 25 14:06:05 bach kernel: [ 78.798244] RDX: 88021eca9eb8 RSI: 0001 RDI: Apr 25 14:06:05 bach kernel: [ 78.798281] RBP: 88021eca9eb8 R08: d8ca R09: a0499a60 Apr 25 14:06:05 bach kernel: [ 78.798318] R10: R11: 88022e7c8b00 R12: 88022ddfb000 Apr 25 14:06:05 bach kernel: [ 78.798356] R13: 88022da7fc00 R14: 88022e7c8b00 R15: Apr 25 14:06:05 bach kernel: [ 78.798394] FS: 7f09050907a0() GS:880237cc() knlGS: Apr 25 14:06:05 bach kernel: [ 78.798436] CS: 0010 DS: ES: CR0: 80050033 Apr 25 14:06:05 bach kernel: [ 78.798467] CR2: ffb8 CR3: 00021eda7000 CR4: 000406e0 Apr 25 14:06:05 bach kernel: [ 78.798504] DR0: DR1: DR2: Apr 25 14:06:05 bach kernel: [ 78.798541] DR3: DR6: 0ff0 DR7: 0400 Apr 25 14:06:05 bach kernel: [ 78.798579] Process gnome-keyring-d (pid: 3095, threadinfo 88021eca8000, task 88021ec841c0) Apr 25 14:06:05 bach kernel: [ 78.798625] Stack: Apr 25 14:06:05 bach kernel: [ 78.798637] a047d657 88022e7c8b00 88022da93600 88022e7c8b00 Apr 25 14:06:05 bach kernel: [ 78.798685] 00fa 0006 0002 88022e7c8b40 Apr 25 14:06:05 bach kernel: [ 78.798732] a04813f2 88022ddfb048 88021eca9eb8 Apr 25 14:06:05 bach kernel: [ 78.798779] Call Trace: Apr 25 14:06:05 bach kernel: [ 78.798804] [a047d657] ? nfs4_handle_exception+0x149/0x2b8 [nfs] Apr 25 14:06:05 bach kernel: [ 78.798851] [a04813f2] ? nfs4_proc_lock+0x2d9/0x348 [nfs] Apr 25 14:06:05 bach kernel: [ 78.798892] [a046a48f] ? do_setlk+0x59/0xcc [nfs] Apr 25 14:06:05 bach kernel: [ 78.798926] [8113c83b] ? sys_flock+0x10c/0x137 Apr 25 14:06:05 bach kernel: [ 78.798958] [81369812] ? system_call_fastpath+0x16/0x1b Apr 25 14:06:05 bach kernel: [ 78.798991] Code: 5d 41 5c 41 5d 48 c7 c6 d0 ad 49 a0 48 c7 c7 19 07 4a a0 31 c0 e9 33 35 ed e0 59 5b 5d 41 5c 41 5d c3 90 90 90 f0 80 4f 48 04 c3 48 8b 47 b8 48 85 c0 74 17 8b 50 30 83 e6 03 21 f2 39 f2 75 0b Apr 25 14:06:05 bach kernel: [ 78.799224] RIP [a048f016]
Bug#655387: [PATCH net] cdc_ether: Ignore bogus union descriptor for RNDIS devices
Some RNDIS devices include a bogus CDC Union descriptor pointing
to non-existing interfaces. The RNDIS code is already prepared
to handle devices without a CDC Union descriptor by hardwiring
the driver to use interfaces 0 and 1, which is correct for the
devices with the bogus descriptor as well. So we can reuse the
existing workaround.
Cc: Markus Kolb linux-201...@tower-net.de
Cc: Iker Salmón San Millán sha...@esdebian.org
Cc: Jonathan Nieder jrnie...@gmail.com
Cc: Oliver Neukum oli...@neukum.org
Cc: 655...@bugs.debian.org
Cc: sta...@vger.kernel.org
Signed-off-by: Bjørn Mork bj...@mork.no
---
Something like this, then?
This has only been build tested by me as I don't have any of the affected
devices. It would be great if any of the reporters could verify that it
solves the problem. I can provide prebuilt modules for Debian 3.2 based
kernels to simplify the testing (just rmmod and insmod - no need to build
or boot). Send me an email if you want the module.
Sorry for the long delay in following up this. I totally forgot about it.
Bjørn
drivers/net/usb/cdc_ether.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c
index 90a3002..4ed5a38 100644
--- a/drivers/net/usb/cdc_ether.c
+++ b/drivers/net/usb/cdc_ether.c
@@ -83,6 +83,7 @@ int usbnet_generic_cdc_bind(struct usbnet *dev, struct
usb_interface *intf)
struct cdc_state*info = (void *) dev-data;
int status;
int rndis;
+ boolandroid_rndis_quirk = false;
struct usb_driver *driver = driver_of(intf);
struct usb_cdc_mdlm_desc*desc = NULL;
struct usb_cdc_mdlm_detail_desc *detail = NULL;
@@ -195,6 +196,11 @@ int usbnet_generic_cdc_bind(struct usbnet *dev, struct
usb_interface *intf)
info-control,
info-u-bSlaveInterface0,
info-data);
+ /* fall back to hard-wiring for RNDIS */
+ if (rndis) {
+ android_rndis_quirk = true;
+ goto next_desc;
+ }
goto bad_desc;
}
if (info-control != intf) {
@@ -271,8 +277,12 @@ next_desc:
/* Microsoft ActiveSync based and some regular RNDIS devices lack the
* CDC descriptors, so we'll hard-wire the interfaces and not check
* for descriptors.
+*
+* Some Android RNDIS devices have a CDC Union descriptor pointing
+* to non-existing interfaces. Ignore that and attempt the same
+* hard-wired 0 and 1 interfaces.
*/
- if (rndis !info-u) {
+ if (rndis (!info-u || android_rndis_quirk)) {
info-control = usb_ifnum_to_if(dev-udev, 0);
info-data = usb_ifnum_to_if(dev-udev, 1);
if (!info-control || !info-data) {
--
1.7.10
--
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/1335437703-6800-1-git-send-email-bj...@mork.no
Re: Squeeze point release (6.0.5)
On Wed, 25, Apr, 2012 at 09:32:51PM +0100, Steve McIntyre spoke thus.. That will help, but then the issue is more a problem with downloading the images. I've got a full mirror at home, which helps immensely with jigdo downloads. I can try and arrange to have a full local mirror at the BSP which I can sync at work on the Friday beforehand if that'll help. Mark -- Mark Hymers mhy at debian dot org I've had people claim that they actually make the sun rise rise every morning. I've offered to test them by shooting them. So far all these people have not responded to my endeavours. James Randi on BBCi Live Chat -- 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/20120426112218.ga30...@hymers.org.uk
Re: Squeeze point release (6.0.5)
On Thu, Apr 26, 2012 at 12:22:18PM +0100, Mark Hymers wrote: On Wed, 25, Apr, 2012 at 09:32:51PM +0100, Steve McIntyre spoke thus.. That will help, but then the issue is more a problem with downloading the images. I've got a full mirror at home, which helps immensely with jigdo downloads. I can try and arrange to have a full local mirror at the BSP which I can sync at work on the Friday beforehand if that'll help. Cool, that would be good. -- Steve McIntyre, Cambridge, UK.st...@einval.com We don't need no education. We don't need no thought control. -- 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/20120426113523.gn21...@einval.com
Bug#655387: [PATCH net] cdc_ether: Ignore bogus union descriptor for RNDIS devices
Am Donnerstag, 26. April 2012, 12:55:03 schrieb Bjørn Mork: Some RNDIS devices include a bogus CDC Union descriptor pointing to non-existing interfaces. The RNDIS code is already prepared to handle devices without a CDC Union descriptor by hardwiring the driver to use interfaces 0 and 1, which is correct for the devices with the bogus descriptor as well. So we can reuse the existing workaround. Very good, except that this is a bit risky, because we may use interface 0 without checking that it belongs to us. Could you add a sanity check that the interface for which probe() is called is really the control interface in case a workaround is used? Regards Oliver -- 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/201204261356.03000.oli...@neukum.org
Processed: Re: [Pkg-acpi-devel] Bug#670512: acpi: wrong battery state returned
Processing commands for cont...@bugs.debian.org: reassign 670512 linux-image-3.3.0-trunk-amd64 Bug #670512 [acpi] acpi: wrong battery state returned Bug reassigned from package 'acpi' to 'linux-image-3.3.0-trunk-amd64'. No longer marked as found in versions acpi/1.6-1. Ignoring request to alter fixed versions of bug #670512 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 670512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670512 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.133544294317715.transcr...@bugs.debian.org
Bug#655387: [PATCH net v2] cdc_ether: Ignore bogus union descriptor for RNDIS devices
Some RNDIS devices include a bogus CDC Union descriptor pointing
to non-existing interfaces. The RNDIS code is already prepared
to handle devices without a CDC Union descriptor by hardwiring
the driver to use interfaces 0 and 1, which is correct for the
devices with the bogus descriptor as well. So we can reuse the
existing workaround.
Cc: Markus Kolb linux-201...@tower-net.de
Cc: Iker Salmón San Millán sha...@esdebian.org
Cc: Jonathan Nieder jrnie...@gmail.com
Cc: Oliver Neukum oli...@neukum.org
Cc: 655...@bugs.debian.org
Cc: sta...@vger.kernel.org
Signed-off-by: Bjørn Mork bj...@mork.no
---
v2: adding a test to verify that the resulting control interface is the
probed interface, as suggested by Oliver Neukum
The same comments as for v1 regarding testing applies. This is build
tested only. Should go through some functional testing before being
applied.
Bjørn
drivers/net/usb/cdc_ether.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c
index 90a3002..00880ed 100644
--- a/drivers/net/usb/cdc_ether.c
+++ b/drivers/net/usb/cdc_ether.c
@@ -83,6 +83,7 @@ int usbnet_generic_cdc_bind(struct usbnet *dev, struct
usb_interface *intf)
struct cdc_state*info = (void *) dev-data;
int status;
int rndis;
+ boolandroid_rndis_quirk = false;
struct usb_driver *driver = driver_of(intf);
struct usb_cdc_mdlm_desc*desc = NULL;
struct usb_cdc_mdlm_detail_desc *detail = NULL;
@@ -195,6 +196,11 @@ int usbnet_generic_cdc_bind(struct usbnet *dev, struct
usb_interface *intf)
info-control,
info-u-bSlaveInterface0,
info-data);
+ /* fall back to hard-wiring for RNDIS */
+ if (rndis) {
+ android_rndis_quirk = true;
+ goto next_desc;
+ }
goto bad_desc;
}
if (info-control != intf) {
@@ -271,11 +277,15 @@ next_desc:
/* Microsoft ActiveSync based and some regular RNDIS devices lack the
* CDC descriptors, so we'll hard-wire the interfaces and not check
* for descriptors.
+*
+* Some Android RNDIS devices have a CDC Union descriptor pointing
+* to non-existing interfaces. Ignore that and attempt the same
+* hard-wired 0 and 1 interfaces.
*/
- if (rndis !info-u) {
+ if (rndis (!info-u || android_rndis_quirk)) {
info-control = usb_ifnum_to_if(dev-udev, 0);
info-data = usb_ifnum_to_if(dev-udev, 1);
- if (!info-control || !info-data) {
+ if (!info-control || !info-data || info-control != intf) {
dev_dbg(intf-dev,
rndis: master #0/%p slave #1/%p\n,
info-control,
--
1.7.10
--
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/1335443710-2627-1-git-send-email-bj...@mork.no
Bug#670398: linux-image-2.6.32-5-amd64: SSH logins hang while hpet interrupts multiply on Intel Nehalem CPUs
On Thu, 2012-04-26 at 10:02 +0200, Sven Hoexter wrote: On Thu, Apr 26, 2012 at 04:49:56AM +0100, Ben Hutchings wrote: On Wed, 2012-04-25 at 10:36 +0200, Sven Hoexter wrote: Hi, Searching through munin graphs we could narrow down the starting point of this issue to the point when the hpet interrupts for one CPU core multiplied. Sometimes they multiplied by six. Looking further we've found the Kernel [events/$x] in state D where $x is the number of the CPU core which has the high number of hpet interrupts. When we started strace -f on the sshd master process everything works until you logout. Then you'll again see the forked sshd process hanging in state D. This is strange, because D state means uninterruptible sleep (not handling signals). But perhaps the sshd process was repeatedly changing between uninterruptible and interruptible state. Is it possible to gather such data? I guess grep'ing through ps output is not the right tool here. From a system currently suffering from this issue: [...] You can use 'echo w /proc/sysrq-trigger' to get a traceback for all the tasks in D state, which might provide some clues. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#638863: linux-image-3.0.0-1-amd64: Errors/warnings show during startup - forward to upstream?
Hi, from what I understood, it is acknowledged that this is actually a bug in the upstream kernel, so I'd like to report it at the kernel bugzilla. However I do not know which bugzilla category to use - could someone give me a hint please? Kind regards, Ralf -- 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/201204261619.11456.ralfjun...@gmx.de
Bug#670398: linux-image-2.6.32-5-amd64: SSH logins hang while hpet interrupts multiply on Intel Nehalem CPUs
On Thu, Apr 26, 2012 at 01:45:30PM +0100, Ben Hutchings wrote: Hi, You can use 'echo w /proc/sysrq-trigger' to get a traceback for all the tasks in D state, which might provide some clues. ok, see the attached file. Regards, Sven Apr 26 16:08:34 vdf1 kernel: [6726714.281854] SysRq : Show Blocked State Apr 26 16:08:34 vdf1 kernel: [6726714.281883] taskPC stack pid father Apr 26 16:08:34 vdf1 kernel: [6726714.281912] events/0 D 015 2 0x Apr 26 16:08:34 vdf1 kernel: [6726714.281946] 814891f0 0046 88043e4e5c0c Apr 26 16:08:34 vdf1 kernel: [6726714.281997] 88000fa15780 f9e0 88043e4e5fd8 Apr 26 16:08:34 vdf1 kernel: [6726714.282048] 00015780 00015780 88043e4e8000 88043e4e82f8 Apr 26 16:08:34 vdf1 kernel: [6726714.282099] Call Trace: Apr 26 16:08:34 vdf1 kernel: [6726714.282127] [8105af0e] ? __mod_timer+0x141/0x153 Apr 26 16:08:34 vdf1 kernel: [6726714.287558] [8105a9f4] ? try_to_del_timer_sync+0x63/0x6c Apr 26 16:08:34 vdf1 kernel: [6726714.287589] [812fbd24] ? schedule_timeout+0xa5/0xdd Apr 26 16:08:34 vdf1 kernel: [6726714.287617] [8105aa88] ? process_timeout+0x0/0x5 Apr 26 16:08:34 vdf1 kernel: [6726714.287651] [a00fc8f7] ? ehci_endpoint_disable+0xa4/0x141 [ehci_hcd] Apr 26 16:08:34 vdf1 kernel: [6726714.287699] [a00b8f0d] ? usb_ep0_reinit+0x13/0x34 [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287731] [a00b970a] ? usb_reset_and_verify_device+0x87/0x3d6 [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287779] [a00be1c7] ? usb_kill_urb+0x10/0xbb [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287811] [a00be1c7] ? usb_kill_urb+0x10/0xbb [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287842] [a00b9aed] ? usb_reset_device+0x94/0x124 [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287873] [a00d96a0] ? hid_reset+0x91/0x122 [usbhid] Apr 26 16:08:34 vdf1 kernel: [6726714.287903] [810619f7] ? worker_thread+0x188/0x21d Apr 26 16:08:34 vdf1 kernel: [6726714.287932] [a00d960f] ? hid_reset+0x0/0x122 [usbhid] Apr 26 16:08:34 vdf1 kernel: [6726714.287961] [8106502a] ? autoremove_wake_function+0x0/0x2e Apr 26 16:08:34 vdf1 kernel: [6726714.287990] [8106186f] ? worker_thread+0x0/0x21d Apr 26 16:08:34 vdf1 kernel: [6726714.288018] [81064d5d] ? kthread+0x79/0x81 Apr 26 16:08:34 vdf1 kernel: [6726714.288046] [81011baa] ? child_rip+0xa/0x20 Apr 26 16:08:34 vdf1 kernel: [6726714.288072] [81064ce4] ? kthread+0x0/0x81 Apr 26 16:08:34 vdf1 kernel: [6726714.288098] [81011ba0] ? child_rip+0x0/0x20 Apr 26 16:08:34 vdf1 kernel: [6726714.288131] sshd D 0 17858 17854 0x Apr 26 16:08:34 vdf1 kernel: [6726714.288164] 88043e473880 0086 0ffc Apr 26 16:08:34 vdf1 kernel: [6726714.288215] f9e0 880270a55fd8 Apr 26 16:08:34 vdf1 kernel: [6726714.288266] 00015780 00015780 88043c100710 88043c100a08 Apr 26 16:08:34 vdf1 kernel: [6726714.288316] Call Trace: Apr 26 16:08:34 vdf1 kernel: [6726714.288340] [8100f6c4] ? __switch_to+0x1ad/0x297 Apr 26 16:08:34 vdf1 kernel: [6726714.288367] [812fbcad] ? schedule_timeout+0x2e/0xdd Apr 26 16:08:34 vdf1 kernel: [6726714.288397] [810482ed] ? finish_task_switch+0x3a/0xaf Apr 26 16:08:34 vdf1 kernel: [6726714.288426] [812fb8f0] ? thread_return+0x79/0xe0 Apr 26 16:08:34 vdf1 kernel: [6726714.288453] [812fbb64] ? wait_for_common+0xde/0x15b Apr 26 16:08:34 vdf1 kernel: [6726714.288482] [8104a4cc] ? default_wake_function+0x0/0x9 Apr 26 16:08:34 vdf1 kernel: [6726714.288510] [81062326] ? flush_work+0x75/0x87 Apr 26 16:08:34 vdf1 kernel: [6726714.288538] [81061d00] ? wq_barrier_func+0x0/0x9 Apr 26 16:08:34 vdf1 kernel: [6726714.288567] [811fbd44] ? n_tty_poll+0x5e/0x138 Apr 26 16:08:34 vdf1 kernel: [6726714.288594] [811f8732] ? tty_poll+0x56/0x6d Apr 26 16:08:34 vdf1 kernel: [6726714.288622] [810fc782] ? do_select+0x37b/0x57a Apr 26 16:08:34 vdf1 kernel: [6726714.288650] [810fcdfb] ? __pollwait+0x0/0xd6 Apr 26 16:08:34 vdf1 kernel: [6726714.288677] [810fced1] ? pollwake+0x0/0x5b Apr 26 16:08:34 vdf1 kernel: [6726714.288704] [810fced1] ? pollwake+0x0/0x5b Apr 26 16:08:34 vdf1 kernel: [6726714.288731] [810fced1] ? pollwake+0x0/0x5b Apr 26 16:08:34 vdf1 kernel: [6726714.288757] [810fced1] ? pollwake+0x0/0x5b Apr 26 16:08:34 vdf1 kernel: [6726714.288785] [8127f29b] ? tcp_recvmsg+0x98b/0xa9e Apr 26 16:08:34 vdf1 kernel: [6726714.288813] [8103fc9e] ? update_curr+0xa6/0x147 Apr 26 16:08:34 vdf1 kernel:
Bug#638863: linux-image-3.0.0-1-amd64: Errors/warnings show during startup - forward to upstream?
On Thu, 2012-04-26 at 16:19 +0200, Ralf Jung wrote: Hi, from what I understood, it is acknowledged that this is actually a bug in the upstream kernel, so I'd like to report it at the kernel bugzilla. However I do not know which bugzilla category to use - could someone give me a hint please? I think it's: Product: Platform Specific/Hardware Component: x86-64 Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#669270: Evolution triggers NFS4 problem
Hi again, Russel Winder wrote: I tried with the other kernel I have installed, 3.2.7 but it failed with both the nouveau driver and the NVIDIA driver. Do you mean you get the BUG in nfs_mark_delegation_referenced in 3.2.7-1 or some other kind of failure? Jonathan -- 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/20120426161657.GA3564@burratino
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #514833 (http://bugs.debian.org/514833) # Bug title: linux-image-2.6.18-6-686: sundance network driver get timeout on a DFE-580TX when this kernel is installed # * http://bugzilla.kernel.org/show_bug.cgi?id=43152 # * remote status changed: (?) - NEW usertags 514833 + status-NEW Bug#514833: linux-image-2.6.18-6-686: sundance network driver get timeout on a DFE-580TX when this kernel is installed There were no usertags set. Usertags are now: status-NEW. # remote status report for #656476 (http://bugs.debian.org/656476) # Bug title: linux-image-2.6.32-5-686: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable # * http://bugzilla.kernel.org/show_bug.cgi?id=43152 # * remote status changed: (?) - NEW usertags 656476 + status-NEW Bug#656476: linux-image-2.6.32-5-686: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable There were no usertags set. Usertags are now: status-NEW. # remote status report for #627372 (http://bugs.debian.org/627372) # Bug title: linux-image-2.6.38-2-686: Console turns black during boot # * https://bugs.freedesktop.org/show_bug.cgi?id=44156 # * remote status changed: REOPENED - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 627372 + fixed-upstream Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Added tag(s) fixed-upstream. usertags 627372 - status-REOPENED Bug#627372: linux-image-2.6.38-2-686: Console turns black during boot Usertags were: status-REOPENED. Usertags are now: . usertags 627372 + status-RESOLVED resolution-FIXED Bug#627372: linux-image-2.6.38-2-686: Console turns black during boot There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 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.13354583185142.transcr...@bugs.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #514833 (http://bugs.debian.org/514833) # Bug title: linux-image-2.6.18-6-686: sundance network driver get timeout on a DFE-580TX when this kernel is installed # * http://bugzilla.kernel.org/show_bug.cgi?id=43152 # * remote status changed: (?) - NEW usertags 514833 + status-NEW # remote status report for #656476 (http://bugs.debian.org/656476) # Bug title: linux-image-2.6.32-5-686: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable # * http://bugzilla.kernel.org/show_bug.cgi?id=43152 # * remote status changed: (?) - NEW usertags 656476 + status-NEW # remote status report for #627372 (http://bugs.debian.org/627372) # Bug title: linux-image-2.6.38-2-686: Console turns black during boot # * https://bugs.freedesktop.org/show_bug.cgi?id=44156 # * remote status changed: REOPENED - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 627372 + fixed-upstream usertags 627372 - status-REOPENED usertags 627372 + status-RESOLVED resolution-FIXED thanks -- 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/20120426163837.26227.59624.btsl...@busoni.debian.org
Bug#670505: [3.2.12 - 3.2.14 regression] BUG: unable to handle kernel paging request in nfs_mark_delegation_referenced
notfound 669270 linux-2.6/3.2.7-1
merge 670505 669270
tags 670505 + upstream patch moreinfo
quit
Hi Rik,
Rik Theys wrote:
It seems stable update 3.2.14 or 3.2.15 introduced a regression regarding
NFS4 delegations.
It seems to be the same issue as reported here[1] against the 3.3 kernel. It
was also intruduced
there between 3.3.0 and 3.3.1.
[...]
BUG: unable to handle kernel paging request at ffb8
IP: [a048f016] nfs_mark_delegation_referenced+0x6/0x6 [nfs]
In [1], Jeff Layton says it looks like a regression introduced by
3114ea7a24d3 NFSv4: Return the delegation if the server returns
NFS4ERR_OPENMODE
and suggests a fix. Does this patch help?
-- 8 --
From: Trond Myklebust trond.mykleb...@netapp.com
Date: Tue, 27 Mar 2012 18:31:25 -0400
Subject: NFSv4: Minor cleanups for nfs4_handle_exception and
nfs4_async_handle_error
commit 14977489ffdb80d4caf5a184ba41b23b02fbacd9 upstream.
Signed-off-by: Trond Myklebust trond.mykleb...@netapp.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
Thanks,
Jonathan
fs/nfs/nfs4proc.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 757293b66dbb..626945f23afb 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -265,7 +265,7 @@ static int nfs4_handle_exception(struct nfs_server *server,
int errorcode, struc
case 0:
return 0;
case -NFS4ERR_OPENMODE:
- if (nfs_have_delegation(inode, FMODE_READ)) {
+ if (inode nfs_have_delegation(inode, FMODE_READ)) {
nfs_inode_return_delegation(inode);
exception-retry = 1;
return 0;
@@ -277,10 +277,9 @@ static int nfs4_handle_exception(struct nfs_server
*server, int errorcode, struc
case -NFS4ERR_DELEG_REVOKED:
case -NFS4ERR_ADMIN_REVOKED:
case -NFS4ERR_BAD_STATEID:
- if (state != NULL)
- nfs_remove_bad_delegation(state-inode);
if (state == NULL)
break;
+ nfs_remove_bad_delegation(state-inode);
nfs4_schedule_stateid_recovery(server, state);
goto wait_on_recovery;
case -NFS4ERR_EXPIRED:
@@ -3730,8 +3729,9 @@ nfs4_async_handle_error(struct rpc_task *task, const
struct nfs_server *server,
case -NFS4ERR_DELEG_REVOKED:
case -NFS4ERR_ADMIN_REVOKED:
case -NFS4ERR_BAD_STATEID:
- if (state != NULL)
- nfs_remove_bad_delegation(state-inode);
+ if (state == NULL)
+ break;
+ nfs_remove_bad_delegation(state-inode);
case -NFS4ERR_OPENMODE:
if (state == NULL)
break;
--
1.7.10
--
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/20120426165127.GA3639@burratino
Processed: Re: [3.2.12 - 3.2.14 regression] BUG: unable to handle kernel paging request in nfs_mark_delegation_referenced
Processing commands for cont...@bugs.debian.org:
notfound 669270 linux-2.6/3.2.7-1
Bug #669270 [linux-2.6] linux-image-3.2.0-2-amd64: Evolution triggers NFS4
problem
No longer marked as found in versions linux-2.6/3.2.7-1.
merge 670505 669270
Bug #670505 [linux-2.6] linux-image-3.2.0-0.bpo.2-amd64: 3.2.{14, 15}
regression: NFS delegation problems
Bug #669270 [linux-2.6] linux-image-3.2.0-2-amd64: Evolution triggers NFS4
problem
There is no source info for the package 'linux-2.6' at version '3.2.15-1' with
architecture ''
Unable to make a source version for version '3.2.15-1'
There is no source info for the package 'linux-2.6' at version
'3.2.15-1~bpo60+1' with architecture ''
Unable to make a source version for version '3.2.15-1~bpo60+1'
Marked as found in versions 3.2.15-1~bpo60+1.
Bug #670505 [linux-2.6] linux-image-3.2.0-0.bpo.2-amd64: 3.2.{14, 15}
regression: NFS delegation problems
There is no source info for the package 'linux-2.6' at version '3.2.15-1' with
architecture ''
Unable to make a source version for version '3.2.15-1'
There is no source info for the package 'linux-2.6' at version
'3.2.15-1~bpo60+1' with architecture ''
Unable to make a source version for version '3.2.15-1~bpo60+1'
Marked as found in versions 3.2.15-1.
Merged 669270 670505
tags 670505 + upstream patch moreinfo
Bug #670505 [linux-2.6] linux-image-3.2.0-0.bpo.2-amd64: 3.2.{14, 15}
regression: NFS delegation problems
Bug #669270 [linux-2.6] linux-image-3.2.0-2-amd64: Evolution triggers NFS4
problem
Added tag(s) upstream, moreinfo, and patch.
Added tag(s) upstream, moreinfo, and patch.
quit
Stopping processing here.
Please contact me if you need assistance.
--
669270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669270
670505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670505
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.13354591029977.transcr...@bugs.debian.org
Processed: Re: [PATCH net v2] cdc_ether: Ignore bogus union descriptor for RNDIS devices
Processing commands for cont...@bugs.debian.org: tags 655387 + upstream patch moreinfo Bug #655387 [linux-2.6] Samsung galaxy S won't tether trough usb due to bad CDC descriptors Added tag(s) moreinfo and patch. End of message, stopping processing here. Please contact me if you need assistance. -- 655387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655387 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.133546017614160.transcr...@bugs.debian.org
Bug#627372: [2.6.32 - 2.6.38 regression] GM45: Console turns black during boot
tags 627372 + upstream patch moreinfo quit Hi Alan, Alan Zimmerman wrote: Console turns black during boot, roughly at the point where normally the console font changes. Thanks again. At last there is a patch to test (attached). Could you try it? Possible instructions: 0. Prerequisites apt-get install git build-essential 1. Get the kernel history if you don't already have it git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2. Add point releases cd linux git remote add stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git git fetch stable 3. Configure, build, and test git checkout stable/linux-3.2.y cp /boot/config-$(uname -r) .config; # current configuration make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root reboot Hopefully it reproduces the black screen at boot. 4. Try the patch cd linux git am -3sc /path/to/the/patch make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root reboot An alternative set of instructions is at [1]. If it works, we can try applying the patch and pass this information upstream to help them decide when to roll it out. Hope that helps, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official or the corresponding page in the debian-kernel-handbook package From: Chris Wilson ch...@chris-wilson.co.uk Date: Tue, 24 Apr 2012 16:36:50 +0100 Subject: drm/i915: Remove too early plane enable on pre-PCH hardware commit 969d380a39d33f7533b6dcee35e834109d23f9e9 upstream. Enabling the plane before we have assigned valid address means that it will access random PTE (often with conflicting memory types) and cause GPU lockups. However, enabling the plane too early appears to workaround a number of bugs in our modesetting code. Cc: Franz Melchior melchior.fr...@gmail.com References: https://bugs.freedesktop.org/show_bug.cgi?id=39947 References: https://bugs.freedesktop.org/show_bug.cgi?id=41091 References: https://bugs.freedesktop.org/show_bug.cgi?id=49041 Signed-off-by: Chris Wilson ch...@chris-wilson.co.uk Acked-by: Jesse Barnes jbar...@virtuousgeek.org Signed-off-by: Daniel Vetter daniel.vet...@ffwll.ch Signed-off-by: Jonathan Nieder jrnie...@gmail.com --- drivers/gpu/drm/i915/intel_display.c |1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c index 390768fce597..fe9b5fca9755 100644 --- a/drivers/gpu/drm/i915/intel_display.c +++ b/drivers/gpu/drm/i915/intel_display.c @@ -5195,7 +5195,6 @@ static int i9xx_crtc_mode_set(struct drm_crtc *crtc, I915_WRITE(DSPCNTR(plane), dspcntr); POSTING_READ(DSPCNTR(plane)); - intel_enable_plane(dev_priv, plane, pipe); ret = intel_pipe_set_base(crtc, x, y, old_fb); -- 1.7.10
Processed: Re: [2.6.32 - 2.6.38 regression] GM45: Console turns black during boot
Processing commands for cont...@bugs.debian.org: tags 627372 + upstream patch moreinfo Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Added tag(s) upstream, moreinfo, and patch. quit Stopping processing here. Please contact me if you need assistance. -- 627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 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.133546099418510.transcr...@bugs.debian.org
Bug#625727: [2.6.35 - 2.6.36 regression] G35: Console turns black during boot, backlight turns off
forcemerge 627372 625727 quit Hi Andreas, Andreas Horter wrote: linux-image-2.6.38-2-amd64_2.6.38-3_amd64.deb. Now when I boot up the system the screen turns black after the initial 6 lines [...] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G35 Express Integrated Graphics Controller [8086:2982] (rev 03) (prog-if 00 [VGA controller]) [...] [0.391371] agpgart-intel :00:00.0: Intel G35 Chipset Thanks for a pleasant report. There's a patch to test at [1] if you have time for it. Hope that helps, Jonathan [1] http://bugs.debian.org/627372#121 -- 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/20120426175110.GA4259@burratino
Processed: Re: [2.6.35 - 2.6.36 regression] G35: Console turns black during boot, backlight turns off
Processing commands for cont...@bugs.debian.org: forcemerge 627372 625727 Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot There is no source info for the package 'linux-2.6' at version '2.6.38-3' with architecture '' Unable to make a source version for version '2.6.38-3' There is no source info for the package 'linux-2.6' at version '2.6.38-5' with architecture '' Unable to make a source version for version '2.6.38-5' There is no source info for the package 'linux-2.6' at version '2.6.39-1' with architecture '' Unable to make a source version for version '2.6.39-1' Marked as found in versions 2.6.38-3. Bug #625727 [linux-2.6] linux-image-2.6.38-2-amd64: Console turns black during boot, backlight turns off Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=44156'. There is no source info for the package 'linux-2.6' at version '2.6.38-3' with architecture '' Unable to make a source version for version '2.6.38-3' There is no source info for the package 'linux-2.6' at version '2.6.38-5' with architecture '' Unable to make a source version for version '2.6.38-5' There is no source info for the package 'linux-2.6' at version '2.6.39-1' with architecture '' Unable to make a source version for version '2.6.39-1' Marked as found in versions 2.6.38-5, linux-2.6/3.1.5-1, 2.6.39-1, linux-2.6/2.6.38-3, and linux-2.6/3.2~rc7-1~experimental.1. Added tag(s) upstream, moreinfo, fixed-upstream, and patch. Merged 625727 627372 quit Stopping processing here. Please contact me if you need assistance. -- 625727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625727 627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 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.133546268928778.transcr...@bugs.debian.org
Bug#638863: Errors/warnings show during startup - forward to upstream?
Ralf Jung wrote: from what I understood, it is acknowledged that this is actually a bug in the upstream kernel, so I'd like to report it at the kernel bugzilla. Sounds like a good idea. Please let us know the bug number if doing so so we can track it. Thanks, Jonathan -- 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/20120426180506.GC3639@burratino
Bug#670505: [3.2.12 - 3.2.14 regression] BUG: unable to handle kernel paging request in nfs_mark_delegation_referenced
Hi Jonathan, On Thu, 26 Apr 2012, Jonathan Nieder wrote: Rik Theys wrote: It seems stable update 3.2.14 or 3.2.15 introduced a regression regarding NFS4 delegations. It seems to be the same issue as reported here[1] against the 3.3 kernel. It was also intruduced there between 3.3.0 and 3.3.1. [...] BUG: unable to handle kernel paging request at ffb8 IP: [a048f016] nfs_mark_delegation_referenced+0x6/0x6 [nfs] In [1], Jeff Layton says it looks like a regression introduced by 3114ea7a24d3 NFSv4: Return the delegation if the server returns NFS4ERR_OPENMODE and suggests a fix. Does this patch help? -- 8 -- From: Trond Myklebust trond.mykleb...@netapp.com Date: Tue, 27 Mar 2012 18:31:25 -0400 Subject: NFSv4: Minor cleanups for nfs4_handle_exception and nfs4_async_handle_error commit 14977489ffdb80d4caf5a184ba41b23b02fbacd9 upstream. If I read [1] correctly this patch was pushed in a Fedora update, and results in the following message being spewed at syslog by the thousands (filling the disk): NFS: nfs4_reclaim_open_state: Lock reclaim failed! I will try applying the patch to the Debian kernel next week, but I assume it will have the same result. If so, I believe it would be better to revert the bad commit for now, and apply a complete fix later when it becomes available. Regards, Rik -- 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/alpine.lrh.2.00.1204262107540.28...@helium.esat.kuleuven.be
Bug#670505: [3.2.12 - 3.2.14 regression] BUG: unable to handle kernel paging request in nfs_mark_delegation_referenced
Rik Theys wrote:
If I read [1] correctly this patch was pushed in a Fedora update,
and results in the following message being spewed at syslog by the
thousands (filling the disk):
NFS: nfs4_reclaim_open_state: Lock reclaim failed!
Mm, sounds unpleasant. Here's a workaround, though it doesn't
leave me thrilled.
-- 8 --
From: William Dauchy wdau...@gmail.com
Date: Wed, 14 Mar 2012 12:32:04 +0100
Subject: NFSv4: Rate limit the state manager for lock reclaim warning messages
commit 96dcadc2fdd111dca90d559f189a30c65394451a upstream.
Adding rate limit on `Lock reclaim failed` messages since it could fill
up system logs
Signed-off-by: William Dauchy wdau...@gmail.com
Signed-off-by: Trond Myklebust trond.mykleb...@netapp.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
fs/nfs/nfs4state.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
index 66020acf2ecd..9464a349f833 100644
--- a/fs/nfs/nfs4state.c
+++ b/fs/nfs/nfs4state.c
@@ -1186,7 +1186,8 @@ restart:
spin_lock(state-state_lock);
list_for_each_entry(lock, state-lock_states,
ls_locks) {
if (!(lock-ls_flags
NFS_LOCK_INITIALIZED))
- printk(%s: Lock reclaim
failed!\n,
+ pr_warn_ratelimited(
+ %s: Lock reclaim
failed!\n,
__func__);
}
spin_unlock(state-state_lock);
--
1.7.10
--
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/20120426192415.GF3639@burratino
Bug#669052: [regression 3.2.12 - 3.2.14] r8169 driver not automatically loaded
Hello Jonathan, here it comes, Regards Jean-Louis Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Jean-Louis Mounier jean-louis.moun...@laposte.net To: Debian Bug Tracking System sub...@bugs.debian.org Subject: initramfs-tools: none Package: initramfs-tools Version: 0.101 Severity: wishlist -- Package-specific info: -- initramfs sizes -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/sys-root ro quiet -- resume RESUME=/dev/hda5 -- /proc/filesystems ext4 ext2 fuseblk -- lsmod Module Size Used by xt_tcpudp 12570 2 ipt_MASQUERADE 12594 2 iptable_nat12928 1 nf_nat 18242 2 iptable_nat,ipt_MASQUERADE nf_conntrack_ipv4 14078 3 nf_nat,iptable_nat nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 nf_conntrack 52720 4 nf_conntrack_ipv4,nf_nat,iptable_nat,ipt_MASQUERADE iptable_filter 12536 1 ip_tables 22042 2 iptable_filter,iptable_nat x_tables 19073 5 ip_tables,iptable_filter,iptable_nat,ipt_MASQUERADE,xt_tcpudp autofs427635 1 powernow_k817574 0 mperf 12453 1 powernow_k8 cpufreq_userspace 12576 0 cpufreq_stats 12866 0 cpufreq_conservative13147 0 ppdev 12763 0 lp 17149 0 cpufreq_powersave 12454 0 bnep 17567 2 bluetooth 119406 7 bnep tun18337 4 fuse 61981 3 nfsd 211858 13 nfs 312191 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 1 nfs lockd 67328 2 nfs,nfsd sunrpc173671 19 lockd,auth_rpcgss,nfs_acl,nfs,nfsd ext2 59231 1 r8169 46980 0 w83627hf 26486 0 hwmon_vid 12430 1 w83627hf loop 22641 0 snd_via82xx23093 3 snd_ac97_codec106899 1 snd_via82xx snd_mpu401_uart13507 1 snd_via82xx snd_pcm_oss36985 0 snd_mixer_oss 17916 1 snd_pcm_oss snd_pcm63900 3 snd_pcm_oss,snd_ac97_codec,snd_via82xx nouveau 545197 2 mxm_wmi12473 1 nouveau snd_page_alloc 13003 2 snd_pcm,snd_via82xx arc4 12458 2 wmi13243 1 mxm_wmi snd_seq_midi 12848 0 snd_seq_midi_event 13316 1 snd_seq_midi snd_rawmidi23060 2 snd_seq_midi,snd_mpu401_uart ath5k 129406 0 video 17628 1 nouveau ttm48725 1 nouveau ath21370 1 ath5k drm_kms_helper 27227 1 nouveau snd_seq45093 2 snd_seq_midi_event,snd_seq_midi mac80211 192768 1 ath5k snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 22917 2 snd_seq,snd_pcm cfg80211 137140 3 mac80211,ath,ath5k snd52850 16 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_mpu401_uart,snd_ac97_codec,snd_via82xx drm 167670 4 drm_kms_helper,ttm,nouveau parport_pc 22364 1 usblp 17343 0 soundcore 13065 1 snd parport31858 3 parport_pc,lp,ppdev rfkill 19012 3 cfg80211,bluetooth ac97_bus 12510 1 snd_ac97_codec pcspkr 12579 0 evdev 17562 9 i2c_algo_bit 12841 1 nouveau i2c_viapro 12499 0 gameport 13612 1 snd_via82xx i2c_core 19780 5 i2c_viapro,i2c_algo_bit,drm,drm_kms_helper,nouveau psmouse64455 0 serio_raw 12931 0 amd64_edac_mod 22334 0 edac_mce_amd 17103 1 amd64_edac_mod edac_core 35258 3 amd64_edac_mod k8temp 12647 0 shpchp 31293 0 processor 28106 1 powernow_k8 thermal_sys18040 2 processor,video button 12937 1 nouveau ext4 350507 10 crc16 12343 2 ext4,bluetooth jbd2 62015 1 ext4 mbcache13065 2 ext4,ext2 dm_mod 63545 33 sd_mod 36136 2 sr_mod 21899 0 crc_t10dif 12348 1 sd_mod cdrom 35401 1 sr_mod ata_generic12479 0 pata_via 12847 0 sata_promise 13540 2 sata_via 12971 0 uhci_hcd 26865 0 ehci_hcd 40215 0 libata140589 4 sata_via,sata_promise,pata_via,ata_generic floppy 53129 0 usbcore 128498 4 ehci_hcd,uhci_hcd,usblp scsi_mod 162458 3
Processed: Re: regression: CPU fan fast after resume: won't climb back down (patch from upstream)
Processing commands for cont...@bugs.debian.org:
tags 596741 = upstream patch moreinfo
Bug #596741 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6]
regression: CPU fan fast after resume: won't climb back down
Added tag(s) moreinfo; removed tag(s) pending.
quit
Stopping processing here.
Please contact me if you need assistance.
--
596741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596741
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.1335470381428.transcr...@bugs.debian.org
Bug#596741: regression: CPU fan fast after resume: won't climb back down (patch from upstream)
tags 596741 = upstream patch moreinfo
quit
Hi Jon,
Jon Dowland wrote:
I'm happy to: but after a few hours I've totally failed to build the squeeze
kernel for various reasons, the last attempt (in a pbuilder) without any clear
idea why it failed.
Sorry for the trouble. Building the full kernel package is generally not a
great idea, since it is enormous. Building just one variant of the kernel
works better, as described at [1].
Even easier is testing using the upstream source. It works like this:
0. Prerequisites:
apt-get install git build-essential
1. Get a copy of the kernel history if you don't already have it:
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
2. Fetch point release (KMS variant):
cd linux
git remote add squeeze-drm \
git://git.kernel.org/pub/scm/linux/kernel/git/smb/linux-2.6.32.y-drm33.z.git
git fetch squeeze-drm
3. Configure, build, and test:
git checkout squeeze-drm/master
cp /boot/config-2.6.32-5-* .config; # stock configuration
scripts/config --disable DEBUG_INFO
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -jnum for parallel build
dpkg -i ../name of package; # as root
Hopefully it reproduces the problem. So:
4. Test the patch:
cd linux
git am -3sc /path/to/the/patch
make deb-pkg; # maybe with -j4
dpkg -i ../name of package
reboot
Patch attached.
Hope that helps,
Jonathan
[1]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
or the corresponding page in the debian-kernel-handbook package
From: Alex Deucher alexander.deuc...@amd.com
Date: Thu, 29 Mar 2012 19:04:08 -0400
Subject: drm/radeon/kms: fix fans after resume
commit 402976fe51b2d1a58a29ba06fa1ca5ace3a4cdcd upstream.
On pre-R600 asics, the SpeedFanControl table is not
executed as part of ASIC_Init as it is on newer asics.
Fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=29412
Signed-off-by: Alex Deucher alexander.deuc...@amd.com
Reviewed-by: Michel Dänzer michel.daen...@amd.com
Signed-off-by: Dave Airlie airl...@redhat.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
drivers/gpu/drm/radeon/atom.c |9 +
drivers/gpu/drm/radeon/atom.h |1 +
2 files changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/radeon/atom.c b/drivers/gpu/drm/radeon/atom.c
index 052312f5ff97..0272ea8bd6cf 100644
--- a/drivers/gpu/drm/radeon/atom.c
+++ b/drivers/gpu/drm/radeon/atom.c
@@ -31,6 +31,7 @@
#include atom.h
#include atom-names.h
#include atom-bits.h
+#include radeon.h
#define ATOM_COND_ABOVE0
#define ATOM_COND_ABOVEOREQUAL 1
@@ -1247,8 +1248,10 @@ struct atom_context *atom_parse(struct card_info *card,
void *bios)
int atom_asic_init(struct atom_context *ctx)
{
+ struct radeon_device *rdev = ctx-card-dev-dev_private;
int hwi = CU16(ctx-data_table + ATOM_DATA_FWI_PTR);
uint32_t ps[16];
+
memset(ps, 0, 64);
ps[0] = cpu_to_le32(CU32(hwi + ATOM_FWI_DEFSCLK_PTR));
@@ -1260,6 +1263,12 @@ int atom_asic_init(struct atom_context *ctx)
return 1;
atom_execute_table(ctx, ATOM_CMD_INIT, ps);
+ memset(ps, 0, 64);
+
+ if (rdev-family CHIP_R600) {
+ if (CU16(ctx-cmd_table + 4 + 2 * ATOM_CMD_SPDFANCNTL))
+ atom_execute_table(ctx, ATOM_CMD_SPDFANCNTL, ps);
+ }
return 0;
}
diff --git a/drivers/gpu/drm/radeon/atom.h b/drivers/gpu/drm/radeon/atom.h
index bc73781423a1..d3b7c967e44e 100644
--- a/drivers/gpu/drm/radeon/atom.h
+++ b/drivers/gpu/drm/radeon/atom.h
@@ -44,6 +44,7 @@
#define ATOM_CMD_SETSCLK 0x0A
#define ATOM_CMD_SETMCLK 0x0B
#define ATOM_CMD_SETPCLK 0x0C
+#define ATOM_CMD_SPDFANCNTL0x39
#define ATOM_DATA_FWI_PTR 0xC
#define ATOM_DATA_IIO_PTR 0x32
--
1.7.10
Processed: tagging 669270
Processing commands for cont...@bugs.debian.org:
tags 669270 + pending
Bug #669270 [linux-2.6] linux-image-3.2.0-2-amd64: Evolution triggers NFS4
problem
Bug #670505 [linux-2.6] linux-image-3.2.0-0.bpo.2-amd64: 3.2.{14, 15}
regression: NFS delegation problems
Added tag(s) pending.
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
669270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669270
670505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670505
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.133549470119657.transcr...@bugs.debian.org
Bug#670398: linux-image-2.6.32-5-amd64: SSH logins hang while hpet interrupts multiply on Intel Nehalem CPUs
On Thu, 2012-04-26 at 16:17 +0200, Sven Hoexter wrote: On Thu, Apr 26, 2012 at 01:45:30PM +0100, Ben Hutchings wrote: Hi, You can use 'echo w /proc/sysrq-trigger' to get a traceback for all the tasks in D state, which might provide some clues. ok, see the attached file. Apr 26 16:08:34 vdf1 kernel: [6726714.281854] SysRq : Show Blocked State Apr 26 16:08:34 vdf1 kernel: [6726714.281883] task PC stack pid father Apr 26 16:08:34 vdf1 kernel: [6726714.281912] events/0 D 015 2 0x Apr 26 16:08:34 vdf1 kernel: [6726714.281946] 814891f0 0046 88043e4e5c0c Apr 26 16:08:34 vdf1 kernel: [6726714.281997] 88000fa15780 f9e0 88043e4e5fd8 Apr 26 16:08:34 vdf1 kernel: [6726714.282048] 00015780 00015780 88043e4e8000 88043e4e82f8 Apr 26 16:08:34 vdf1 kernel: [6726714.282099] Call Trace: Apr 26 16:08:34 vdf1 kernel: [6726714.282127] [8105af0e] ? __mod_timer+0x141/0x153 Apr 26 16:08:34 vdf1 kernel: [6726714.287558] [8105a9f4] ? try_to_del_timer_sync+0x63/0x6c Apr 26 16:08:34 vdf1 kernel: [6726714.287589] [812fbd24] ? schedule_timeout+0xa5/0xdd Apr 26 16:08:34 vdf1 kernel: [6726714.287617] [8105aa88] ? process_timeout+0x0/0x5 Apr 26 16:08:34 vdf1 kernel: [6726714.287651] [a00fc8f7] ? ehci_endpoint_disable+0xa4/0x141 [ehci_hcd] Apr 26 16:08:34 vdf1 kernel: [6726714.287699] [a00b8f0d] ? usb_ep0_reinit+0x13/0x34 [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287731] [a00b970a] ? usb_reset_and_verify_device+0x87/0x3d6 [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287779] [a00be1c7] ? usb_kill_urb+0x10/0xbb [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287811] [a00be1c7] ? usb_kill_urb+0x10/0xbb [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287842] [a00b9aed] ? usb_reset_device+0x94/0x124 [usbcore] Apr 26 16:08:34 vdf1 kernel: [6726714.287873] [a00d96a0] ? hid_reset+0x91/0x122 [usbhid] Apr 26 16:08:34 vdf1 kernel: [6726714.287903] [810619f7] ? worker_thread+0x188/0x21d Apr 26 16:08:34 vdf1 kernel: [6726714.287932] [a00d960f] ? hid_reset+0x0/0x122 [usbhid] This is a global workqueue task, and it's running a work item that does error handling for a USB HID (keyboard or mouse, or possibly a UPS). Presumably this is taking a long time for some reason. [...] Apr 26 16:08:34 vdf1 kernel: [6726714.288131] sshd D 0 17858 17854 0x Apr 26 16:08:34 vdf1 kernel: [6726714.288164] 88043e473880 0086 0ffc Apr 26 16:08:34 vdf1 kernel: [6726714.288215] f9e0 880270a55fd8 Apr 26 16:08:34 vdf1 kernel: [6726714.288266] 00015780 00015780 88043c100710 88043c100a08 Apr 26 16:08:34 vdf1 kernel: [6726714.288316] Call Trace: Apr 26 16:08:34 vdf1 kernel: [6726714.288340] [8100f6c4] ? __switch_to+0x1ad/0x297 Apr 26 16:08:34 vdf1 kernel: [6726714.288367] [812fbcad] ? schedule_timeout+0x2e/0xdd Apr 26 16:08:34 vdf1 kernel: [6726714.288397] [810482ed] ? finish_task_switch+0x3a/0xaf Apr 26 16:08:34 vdf1 kernel: [6726714.288426] [812fb8f0] ? thread_return+0x79/0xe0 Apr 26 16:08:34 vdf1 kernel: [6726714.288453] [812fbb64] ? wait_for_common+0xde/0x15b Apr 26 16:08:34 vdf1 kernel: [6726714.288482] [8104a4cc] ? default_wake_function+0x0/0x9 Apr 26 16:08:34 vdf1 kernel: [6726714.288510] [81062326] ? flush_work+0x75/0x87 Apr 26 16:08:34 vdf1 kernel: [6726714.288538] [81061d00] ? wq_barrier_func+0x0/0x9 Apr 26 16:08:34 vdf1 kernel: [6726714.288567] [811fbd44] ? n_tty_poll+0x5e/0x138 [...] This is the sshd task, and it's waiting for a terminal-related work item to finish. Presumably this is queued behind the work item for the USB HID cleanup. So it looks like in this case at least you're seeing a bug in USB error recovery and not anything to do with timing using the TSC vs HPET. Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
Processed: tagging 670492
Processing commands for cont...@bugs.debian.org: tags 670492 + moreinfo Bug #670492 [linux-2.6] linux-image-2.6.32-5-amd64: RTL8111/8168B Wake on LAN does not work Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 670492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670492 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.13354989227716.transcr...@bugs.debian.org
Bug#670492: linux-image-2.6.32-5-amd64: RTL8111/8168B Wake on LAN does not work
On Thu, 2012-04-26 at 08:51 +0200, Andreas Wirooks wrote: Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: normal The title says it all. I already tried the ethtool setting from the debian wiki. No success. [...] It works on my own system with one of these chips, but only from soft-off (S5) and not suspend-to-disk (S4). Which are you testing? Does this work in Linux 3.2 from testing/unstable or squeeze-backports? Also, there are many variants of the chip and this might be a relevant detail. Can you provide the initial kernel log messages from the r8169 driver (try running 'grep r8169 /var/log/dmesg')? Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
Uploading linux-2.6 (3.2.16-1)
I intend to upload linux-2.6 to unstable this weekend. This includes various important fixes from upstream stable version 3.2.16, a few more bug fixes, and the addition of 'EFI stub' support on x86 (cherry-picked from 3.3). There should be no ABI bump. Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
