[4.15-rc4][regression][e1000e] - Device initialization appears broken/inconsistent
Hello kernel devs, I'm encountering an issue with the e1000e driver. I can reproduce this by booting to Windows 10, reboot to Fedora and notice the device won't initialize. If I reboot to Windows 10, then reboot to Linux the device initializes properly. With a kernel.org rpm build of 4.15-rc1 I didn't encounter issues. Fedora kernel is: 4.15.0-0.rc4.git1.2.fc28.x86_64 Any debug from the device I can provide which might show why initialization isn't being complete? Thanks, Shawn
[4.15-rc4][regression][e1000e] - Device initialization appears broken/inconsistent
Hello kernel devs, I'm encountering an issue with the e1000e driver. I can reproduce this by booting to Windows 10, reboot to Fedora and notice the device won't initialize. If I reboot to Windows 10, then reboot to Linux the device initializes properly. With a kernel.org rpm build of 4.15-rc1 I didn't encounter issues. Fedora kernel is: 4.15.0-0.rc4.git1.2.fc28.x86_64 Any debug from the device I can provide which might show why initialization isn't being complete? Thanks, Shawn
[4.12-rc3][smp] smp_call_function_many() - CPU soft lockup
Hello Kernel devs, I was just about to open a VM with virt-manager and then kernel locked up CPUs. Will try -rc4 and see if this got fixed in the churn. Thanks, Shawn Stack below: [33970.295966] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [libvirtd:1043] [33970.295969] Modules linked in: vhost_net vhost tap tun ebtable_filterebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev sunrpc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvmarc4 uvcvideo videobuf2_vmalloc irqbypass iwlmvm snd_usb_audio videobuf2_memops videobuf2_v4l2 crct10dif_pclmul videobuf2_core crc32_pclmul snd_soc_rt5640 ghash_clmulni_intel snd_soc_rl6231 snd_usbmidi_lib videodev snd_hda_codec_realtek intel_cstate snd_rawmidi snd_soc_core snd_compress media iTCO_wdt mei_wdt mac80211 snd_pcm_dmaengine intel_uncore snd_hda_codec_generic ppdev dell_laptop ac97_bus iTCO_vendor_support snd_hda_codec_hdmi dell_wmi snd_hda_intel intel_rapl_perf snd_hda_codec vfat snd_hda_core dell_smbios dcdbas snd_hwdep [33970.295992] sparse_keymap dell_smm_hwmon snd_seq fat snd_seq_device snd_pcm snd_timer iwlwifi joydev cfg80211 pcspkr parport_pc mei_me snd elan_i2c snd_soc_sst_acpi i2c_designware_platform dw_dmac spi_pxa2xx_platform parport video snd_soc_sst_match lpc_ich shpchp mei dell_rbtn rfkill i2c_i801 i2c_designware_core ie31200_edac soundcore 8250_pci tpm_tis tpm_tis_core tpm dell_smo8800 wmi binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel mmc_core serio_raw i2c_hid e1000e ptp pps_core [33970.296013] CPU: 0 PID: 1043 Comm: libvirtd Not tainted 4.12.0-rc3+ #1 [33970.296014] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A19 05/14/2017 [33970.296015] task: 96c6f7c8ac80 task.stack: b16c4815c000 [33970.296017] RIP: 0010:smp_call_function_many+0x1c9/0x220 [33970.296018] RSP: 0018:b16c4815fc20 EFLAGS: 0202 ORIG_RAX:ff10 [33970.296019] RAX: 0003 RBX: 0008 RCX:0007 [33970.296020] RDX: 96c72dddcd38 RSI: RDI:96c70d021ae0 [33970.296021] RBP: b16c4815fc58 R08: ff80 R09:00fe [33970.296021] R10: eee51fdd7880 R11: 96c70cc02dc8 R12:ae025b90 [33970.296022] R13: R14: 96c72dc19dc0 R15:00019d80 [33970.296023] FS: 7f6a70200700() GS:96c72dc0() knlGS: [33970.296024] CS: 0010 DS: ES: CR0: 80050033 [33970.296024] CR2: 55e31fbbcb60 CR3: 0007f7c3 CR4:001406b0 [33970.296025] Call Trace: [33970.296029] ? ___slab_alloc+0x34b/0x4e0 [33970.296031] ? setup_data_read+0xa0/0xa0 [33970.296032] ? ___slab_alloc+0x34c/0x4e0 [33970.296033] on_each_cpu+0x28/0x60 [33970.296035] ? ___slab_alloc+0x34b/0x4e0 [33970.296036] text_poke_bp+0x8f/0xe0 [33970.296037] ? ___slab_alloc+0x34b/0x4e0 [33970.296039] arch_jump_label_transform+0x96/0x110 [33970.296041] __jump_label_update+0x72/0x80 [33970.296042] jump_label_update+0x54/0xb0 [33970.296044] static_key_slow_inc+0x86/0x90 [33970.296045] cpuset_css_online+0x62/0x450 [33970.296046] online_css+0x1a/0x60 [33970.296048] cgroup_apply_control_enable+0x212/0x350 [33970.296049] cgroup_mkdir+0x2da/0x310 [33970.296052] kernfs_iop_mkdir+0x55/0x90 [33970.296053] vfs_mkdir+0x10a/0x1b0 [33970.296055] SyS_mkdir+0x75/0xf0 [33970.296057] entry_SYSCALL_64_fastpath+0x1a/0xa5 [33970.296058] RIP: 0033:0x7f6a7eab0947 [33970.296059] RSP: 002b:7f6a701ff4c8 EFLAGS: 0202 ORIG_RAX:0053 [33970.296060] RAX: ffda RBX: 7f6a44012d20 RCX:7f6a7eab0947 [33970.296060] RDX: 7f6a701ff3e0 RSI: 01ed RDI:7f6a44012cd0 [33970.296061] RBP: 7f6a7ed763c0 R08: 7f6a828ae270 R09:7f6a828acc25 [33970.296062] R10: 7f6a44012cd0 R11: 0202 R12: [33970.296062] R13: 000b R14: 7f6a701ff092 R15: [33970.296063] Code: ae 55 28 00 3b 05 6c aa ca 00 89 c1 0f 8d bb fe ff ff 48 98 49 8b 16 48 03 14 c5 e0 33 ac ae 8b 42 18 a8 01 74 09 f3 90 8b 42 18 01 75 f7 eb be 0f b6 4d d0 4c 89 ea 4c 89 e6 44 89 f7 e8 7f [spstarr@segfault ~]$ Message from syslogd@segfault at Jun 6 12:34:57 ... kernel:[33974.355754] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [chrome:12357] Message from syslogd@segfault at Jun 6 12:35:21 ... kernel:[33998.294502] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [libvirtd:1043] Message from syslogd@segfault at Jun 6 12:35:25 ... kernel:[34002.354290] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [chrome:12357] Message from syslogd@segfault at Jun 6 12:35:53 ... kernel:[34030.292830] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [libvirtd:1043] Message from syslogd@segfault at Jun 6 12:35:53 ... kernel:[34030.352826] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [chrome:12357]
[4.12-rc3][smp] smp_call_function_many() - CPU soft lockup
Hello Kernel devs, I was just about to open a VM with virt-manager and then kernel locked up CPUs. Will try -rc4 and see if this got fixed in the churn. Thanks, Shawn Stack below: [33970.295966] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [libvirtd:1043] [33970.295969] Modules linked in: vhost_net vhost tap tun ebtable_filterebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev sunrpc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvmarc4 uvcvideo videobuf2_vmalloc irqbypass iwlmvm snd_usb_audio videobuf2_memops videobuf2_v4l2 crct10dif_pclmul videobuf2_core crc32_pclmul snd_soc_rt5640 ghash_clmulni_intel snd_soc_rl6231 snd_usbmidi_lib videodev snd_hda_codec_realtek intel_cstate snd_rawmidi snd_soc_core snd_compress media iTCO_wdt mei_wdt mac80211 snd_pcm_dmaengine intel_uncore snd_hda_codec_generic ppdev dell_laptop ac97_bus iTCO_vendor_support snd_hda_codec_hdmi dell_wmi snd_hda_intel intel_rapl_perf snd_hda_codec vfat snd_hda_core dell_smbios dcdbas snd_hwdep [33970.295992] sparse_keymap dell_smm_hwmon snd_seq fat snd_seq_device snd_pcm snd_timer iwlwifi joydev cfg80211 pcspkr parport_pc mei_me snd elan_i2c snd_soc_sst_acpi i2c_designware_platform dw_dmac spi_pxa2xx_platform parport video snd_soc_sst_match lpc_ich shpchp mei dell_rbtn rfkill i2c_i801 i2c_designware_core ie31200_edac soundcore 8250_pci tpm_tis tpm_tis_core tpm dell_smo8800 wmi binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel mmc_core serio_raw i2c_hid e1000e ptp pps_core [33970.296013] CPU: 0 PID: 1043 Comm: libvirtd Not tainted 4.12.0-rc3+ #1 [33970.296014] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A19 05/14/2017 [33970.296015] task: 96c6f7c8ac80 task.stack: b16c4815c000 [33970.296017] RIP: 0010:smp_call_function_many+0x1c9/0x220 [33970.296018] RSP: 0018:b16c4815fc20 EFLAGS: 0202 ORIG_RAX:ff10 [33970.296019] RAX: 0003 RBX: 0008 RCX:0007 [33970.296020] RDX: 96c72dddcd38 RSI: RDI:96c70d021ae0 [33970.296021] RBP: b16c4815fc58 R08: ff80 R09:00fe [33970.296021] R10: eee51fdd7880 R11: 96c70cc02dc8 R12:ae025b90 [33970.296022] R13: R14: 96c72dc19dc0 R15:00019d80 [33970.296023] FS: 7f6a70200700() GS:96c72dc0() knlGS: [33970.296024] CS: 0010 DS: ES: CR0: 80050033 [33970.296024] CR2: 55e31fbbcb60 CR3: 0007f7c3 CR4:001406b0 [33970.296025] Call Trace: [33970.296029] ? ___slab_alloc+0x34b/0x4e0 [33970.296031] ? setup_data_read+0xa0/0xa0 [33970.296032] ? ___slab_alloc+0x34c/0x4e0 [33970.296033] on_each_cpu+0x28/0x60 [33970.296035] ? ___slab_alloc+0x34b/0x4e0 [33970.296036] text_poke_bp+0x8f/0xe0 [33970.296037] ? ___slab_alloc+0x34b/0x4e0 [33970.296039] arch_jump_label_transform+0x96/0x110 [33970.296041] __jump_label_update+0x72/0x80 [33970.296042] jump_label_update+0x54/0xb0 [33970.296044] static_key_slow_inc+0x86/0x90 [33970.296045] cpuset_css_online+0x62/0x450 [33970.296046] online_css+0x1a/0x60 [33970.296048] cgroup_apply_control_enable+0x212/0x350 [33970.296049] cgroup_mkdir+0x2da/0x310 [33970.296052] kernfs_iop_mkdir+0x55/0x90 [33970.296053] vfs_mkdir+0x10a/0x1b0 [33970.296055] SyS_mkdir+0x75/0xf0 [33970.296057] entry_SYSCALL_64_fastpath+0x1a/0xa5 [33970.296058] RIP: 0033:0x7f6a7eab0947 [33970.296059] RSP: 002b:7f6a701ff4c8 EFLAGS: 0202 ORIG_RAX:0053 [33970.296060] RAX: ffda RBX: 7f6a44012d20 RCX:7f6a7eab0947 [33970.296060] RDX: 7f6a701ff3e0 RSI: 01ed RDI:7f6a44012cd0 [33970.296061] RBP: 7f6a7ed763c0 R08: 7f6a828ae270 R09:7f6a828acc25 [33970.296062] R10: 7f6a44012cd0 R11: 0202 R12: [33970.296062] R13: 000b R14: 7f6a701ff092 R15: [33970.296063] Code: ae 55 28 00 3b 05 6c aa ca 00 89 c1 0f 8d bb fe ff ff 48 98 49 8b 16 48 03 14 c5 e0 33 ac ae 8b 42 18 a8 01 74 09 f3 90 8b 42 18 01 75 f7 eb be 0f b6 4d d0 4c 89 ea 4c 89 e6 44 89 f7 e8 7f [spstarr@segfault ~]$ Message from syslogd@segfault at Jun 6 12:34:57 ... kernel:[33974.355754] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [chrome:12357] Message from syslogd@segfault at Jun 6 12:35:21 ... kernel:[33998.294502] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [libvirtd:1043] Message from syslogd@segfault at Jun 6 12:35:25 ... kernel:[34002.354290] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [chrome:12357] Message from syslogd@segfault at Jun 6 12:35:53 ... kernel:[34030.292830] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [libvirtd:1043] Message from syslogd@segfault at Jun 6 12:35:53 ... kernel:[34030.352826] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [chrome:12357]
Re: [4.10][regression][PM] Oops pci_restore_msi_state() e1000e? (Re: [BUG] 4.11.0-rc1 panic on shutdown X61s)
This isn't just Lenovo, My Dell laptop experiences same problem, there is bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=194801 Thanks, Shawn On 02/25/2017 04:53 AM, Shawn Starr wrote: Hello kernel devs, Hibernation appears broken for me in 4.10, I notice the e1000e does not resume on boot, and kernel shows why.. This kernel contains agd5f's 4.11/4.12-drm-next branches merged in. I am unsure if this is a result of the AMDGPU performing a bad hibernation (since it hangs when it finishes dumping pages to disk and doesn't reboot system when /sys/power/disk is set for 'reboot' mode.) otherwise this bug has been persistent in 4.10-rcX. Thanks, Shawn [ 912.256010] BUG: unable to handle kernel NULL pointer dereference at 003c [ 912.257227] IP: pci_restore_msi_state+0x1bd/0x270 [ 912.258218] PGD 0 [ 912.260182] Oops: [#1] SMP [ 912.261168] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev intel_rapl arc4 iwlmvm x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp iTCO_wdt vfat dell_laptop sparse_keymap kvm_intel fat mac80211 iTCO_vendor_support dell_smbios mei_wdt dcdbas dell_smm_hwmon ppdev kvm uvcvideo videobuf2_vmalloc snd_hda_codec_realtek snd_hda_codec_generic snd_usb_audio videobuf2_memops videobuf2_v4l2 irqbypass videobuf2_core snd_hda_codec_hdmi crct10dif_pclmul snd_soc_rt5640 crc32_pclmul snd_soc_rl6231 ghash_clmulni_intel snd_hda_intel snd_soc_core snd_hda_codec snd_usbmidi_lib snd_hda_core snd_compress snd_pcm_dmaengine ac97_bus iwlwifi intel_cstate intel_uncore videodev snd_hwdep intel_rapl_perf snd_seq [ 912.265654] media snd_rawmidi snd_seq_device cfg80211 snd_pcm snd_timer pcspkr ie31200_edac joydev snd video snd_soc_sst_acpi soundcore mei_me parport_pc edac_core elan_i2c mei parport snd_soc_sst_match i2c_designware_platform shpchp spi_pxa2xx_platform tpm_tis dw_dmac lpc_ich i2c_designware_core tpm_tis_core i2c_i801 tpm dell_smo8800 dell_rbtn rfkill wmi nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel mmc_core serio_raw fjes i2c_hid e1000e ptp pps_core [ 912.269609] CPU: 2 PID: 867 Comm: NetworkManager Tainted: GW 4.10.0+ #1 [ 912.270919] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 [ 912.272242] task: 8f3fb7629d80 task.stack: b79243cec000 [ 912.273576] RIP: 0010:pci_restore_msi_state+0x1bd/0x270 [ 912.274916] RSP: 0018:b79243cef540 EFLAGS: 00010286 [ 912.276262] RAX: RBX: 8f3fe97f9000 RCX: [ 912.277623] RDX: 0080 RSI: 0246 RDI: 0246 [ 912.278990] RBP: b79243cef560 R08: 0002 R09: b79243cef50c [ 912.280359] R10: 00c8 R11: 8f3fecc00028 R12: [ 912.281735] R13: fffc R14: 8f3fe97f97e0 R15: 8f3fe97f90a0 [ 912.283114] FS: 7fb468d04940() GS:8f3fedc8() knlGS: [ 912.284506] CS: 0010 DS: ES: CR0: 80050033 [ 912.286248] CR2: 003c CR3: 0007f5881000 CR4: 001406a0 [ 912.287652] Call Trace: [ 912.289049] pci_restore_state.part.35+0x119/0x240 [ 912.290449] ? pci_restore_standard_config+0x40/0x40 [ 912.291840] pci_restore_state+0x18/0x20 [ 912.293224] pci_restore_standard_config+0x37/0x40 [ 912.294599] pci_pm_runtime_resume+0x46/0xa0 [ 912.295969] __rpm_callback+0xc2/0x200 [ 912.297337] ? ipv6_mc_down+0x6d/0x80 [ 912.298703] rpm_callback+0x5f/0x80 [ 912.300063] ? pci_restore_standard_config+0x40/0x40 [ 912.301423] rpm_resume+0x4a4/0x6b0 [ 912.302778] ? inetdev_event+0x3d/0x4e0 [ 912.304133] ? skb_dequeue+0x59/0x70 [ 912.305487] __pm_runtime_resume+0x4e/0x80 [ 912.306839] e1000e_open+0x59/0x450 [e1000e] [ 912.308175] __dev_open+0xc6/0x140 [ 912.309494] ? _raw_spin_unlock_bh+0x1a/0x20 [ 912.310801] __dev_change_flags+0x9d/0x160 [ 912.312103] dev_change_flags+0x29/0x60 [ 912.313391] do_setlink+0x338/0xc90 [ 912.314643] ? __nla_reserve+0x41/0x50 [ 912.315876] ? __nla_put+0x20/0x30 [ 912.317094] ? _raw_read_unlock_bh+0x20/0x30 [ 912.318296] ? inet6_fill_ifla6_attrs+0x494/0x4b0 [ 912.319481] ? inet6_fill_link_af+0x1a/0x30 [ 912.320651] ? rtnl_fill_ifinfo+0xb62/0x10c0 [ 912.321817] ? nla_parse+0x31/0x110 [ 912.323566] rtnl_newlink+0x7ac/0x8e0 [ 912.325432] ? security_capset+0x60/0x80 [ 912.327301] ? ns_capable_common+0x68/0x80 [ 912.329151] ? ns_capable+0x13/0x20 [ 912.330949] rtnetlink_rcv_msg+0xe6/0x210 [ 912.332712] ? __d_lookup+0x116/0x130 [ 912.334455] ? __kmalloc_node_track_caller+0x1f6/0x2b0 [ 912.336182] ? __alloc_skb+0x87/0x1c0 [ 912.337858] ? rtnl_newlink+0x8e0/0x8e0 [ 912.339504] netlink_rcv_skb+0xa4/0xc0 [ 912.341130] rtnetlink_rcv+0x28/0x30 [ 912.342719
Re: [4.10][regression][PM] Oops pci_restore_msi_state() e1000e? (Re: [BUG] 4.11.0-rc1 panic on shutdown X61s)
This isn't just Lenovo, My Dell laptop experiences same problem, there is bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=194801 Thanks, Shawn On 02/25/2017 04:53 AM, Shawn Starr wrote: Hello kernel devs, Hibernation appears broken for me in 4.10, I notice the e1000e does not resume on boot, and kernel shows why.. This kernel contains agd5f's 4.11/4.12-drm-next branches merged in. I am unsure if this is a result of the AMDGPU performing a bad hibernation (since it hangs when it finishes dumping pages to disk and doesn't reboot system when /sys/power/disk is set for 'reboot' mode.) otherwise this bug has been persistent in 4.10-rcX. Thanks, Shawn [ 912.256010] BUG: unable to handle kernel NULL pointer dereference at 003c [ 912.257227] IP: pci_restore_msi_state+0x1bd/0x270 [ 912.258218] PGD 0 [ 912.260182] Oops: [#1] SMP [ 912.261168] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev intel_rapl arc4 iwlmvm x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp iTCO_wdt vfat dell_laptop sparse_keymap kvm_intel fat mac80211 iTCO_vendor_support dell_smbios mei_wdt dcdbas dell_smm_hwmon ppdev kvm uvcvideo videobuf2_vmalloc snd_hda_codec_realtek snd_hda_codec_generic snd_usb_audio videobuf2_memops videobuf2_v4l2 irqbypass videobuf2_core snd_hda_codec_hdmi crct10dif_pclmul snd_soc_rt5640 crc32_pclmul snd_soc_rl6231 ghash_clmulni_intel snd_hda_intel snd_soc_core snd_hda_codec snd_usbmidi_lib snd_hda_core snd_compress snd_pcm_dmaengine ac97_bus iwlwifi intel_cstate intel_uncore videodev snd_hwdep intel_rapl_perf snd_seq [ 912.265654] media snd_rawmidi snd_seq_device cfg80211 snd_pcm snd_timer pcspkr ie31200_edac joydev snd video snd_soc_sst_acpi soundcore mei_me parport_pc edac_core elan_i2c mei parport snd_soc_sst_match i2c_designware_platform shpchp spi_pxa2xx_platform tpm_tis dw_dmac lpc_ich i2c_designware_core tpm_tis_core i2c_i801 tpm dell_smo8800 dell_rbtn rfkill wmi nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel mmc_core serio_raw fjes i2c_hid e1000e ptp pps_core [ 912.269609] CPU: 2 PID: 867 Comm: NetworkManager Tainted: GW 4.10.0+ #1 [ 912.270919] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 [ 912.272242] task: 8f3fb7629d80 task.stack: b79243cec000 [ 912.273576] RIP: 0010:pci_restore_msi_state+0x1bd/0x270 [ 912.274916] RSP: 0018:b79243cef540 EFLAGS: 00010286 [ 912.276262] RAX: RBX: 8f3fe97f9000 RCX: [ 912.277623] RDX: 0080 RSI: 0246 RDI: 0246 [ 912.278990] RBP: b79243cef560 R08: 0002 R09: b79243cef50c [ 912.280359] R10: 00c8 R11: 8f3fecc00028 R12: [ 912.281735] R13: fffc R14: 8f3fe97f97e0 R15: 8f3fe97f90a0 [ 912.283114] FS: 7fb468d04940() GS:8f3fedc8() knlGS: [ 912.284506] CS: 0010 DS: ES: CR0: 80050033 [ 912.286248] CR2: 003c CR3: 0007f5881000 CR4: 001406a0 [ 912.287652] Call Trace: [ 912.289049] pci_restore_state.part.35+0x119/0x240 [ 912.290449] ? pci_restore_standard_config+0x40/0x40 [ 912.291840] pci_restore_state+0x18/0x20 [ 912.293224] pci_restore_standard_config+0x37/0x40 [ 912.294599] pci_pm_runtime_resume+0x46/0xa0 [ 912.295969] __rpm_callback+0xc2/0x200 [ 912.297337] ? ipv6_mc_down+0x6d/0x80 [ 912.298703] rpm_callback+0x5f/0x80 [ 912.300063] ? pci_restore_standard_config+0x40/0x40 [ 912.301423] rpm_resume+0x4a4/0x6b0 [ 912.302778] ? inetdev_event+0x3d/0x4e0 [ 912.304133] ? skb_dequeue+0x59/0x70 [ 912.305487] __pm_runtime_resume+0x4e/0x80 [ 912.306839] e1000e_open+0x59/0x450 [e1000e] [ 912.308175] __dev_open+0xc6/0x140 [ 912.309494] ? _raw_spin_unlock_bh+0x1a/0x20 [ 912.310801] __dev_change_flags+0x9d/0x160 [ 912.312103] dev_change_flags+0x29/0x60 [ 912.313391] do_setlink+0x338/0xc90 [ 912.314643] ? __nla_reserve+0x41/0x50 [ 912.315876] ? __nla_put+0x20/0x30 [ 912.317094] ? _raw_read_unlock_bh+0x20/0x30 [ 912.318296] ? inet6_fill_ifla6_attrs+0x494/0x4b0 [ 912.319481] ? inet6_fill_link_af+0x1a/0x30 [ 912.320651] ? rtnl_fill_ifinfo+0xb62/0x10c0 [ 912.321817] ? nla_parse+0x31/0x110 [ 912.323566] rtnl_newlink+0x7ac/0x8e0 [ 912.325432] ? security_capset+0x60/0x80 [ 912.327301] ? ns_capable_common+0x68/0x80 [ 912.329151] ? ns_capable+0x13/0x20 [ 912.330949] rtnetlink_rcv_msg+0xe6/0x210 [ 912.332712] ? __d_lookup+0x116/0x130 [ 912.334455] ? __kmalloc_node_track_caller+0x1f6/0x2b0 [ 912.336182] ? __alloc_skb+0x87/0x1c0 [ 912.337858] ? rtnl_newlink+0x8e0/0x8e0 [ 912.339504] netlink_rcv_skb+0xa4/0xc0 [ 912.341130] rtnetlink_rcv+0x28/0x30 [ 912.342719
[4.10][regression][PM] Oops pci_restore_msi_state() e1000e?
Hello kernel devs, Hibernation appears broken for me in 4.10, I notice the e1000e does not resume on boot, and kernel shows why.. This kernel contains agd5f's 4.11/4.12-drm-next branches merged in. I am unsure if this is a result of the AMDGPU performing a bad hibernation (since it hangs when it finishes dumping pages to disk and doesn't reboot system when /sys/power/disk is set for 'reboot' mode.) otherwise this bug has been persistent in 4.10-rcX. Thanks, Shawn [ 912.256010] BUG: unable to handle kernel NULL pointer dereference at 003c [ 912.257227] IP: pci_restore_msi_state+0x1bd/0x270 [ 912.258218] PGD 0 [ 912.260182] Oops: [#1] SMP [ 912.261168] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev intel_rapl arc4 iwlmvm x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp iTCO_wdt vfat dell_laptop sparse_keymap kvm_intel fat mac80211 iTCO_vendor_support dell_smbios mei_wdt dcdbas dell_smm_hwmon ppdev kvm uvcvideo videobuf2_vmalloc snd_hda_codec_realtek snd_hda_codec_generic snd_usb_audio videobuf2_memops videobuf2_v4l2 irqbypass videobuf2_core snd_hda_codec_hdmi crct10dif_pclmul snd_soc_rt5640 crc32_pclmul snd_soc_rl6231 ghash_clmulni_intel snd_hda_intel snd_soc_core snd_hda_codec snd_usbmidi_lib snd_hda_core snd_compress snd_pcm_dmaengine ac97_bus iwlwifi intel_cstate intel_uncore videodev snd_hwdep intel_rapl_perf snd_seq [ 912.265654] media snd_rawmidi snd_seq_device cfg80211 snd_pcm snd_timer pcspkr ie31200_edac joydev snd video snd_soc_sst_acpi soundcore mei_me parport_pc edac_core elan_i2c mei parport snd_soc_sst_match i2c_designware_platform shpchp spi_pxa2xx_platform tpm_tis dw_dmac lpc_ich i2c_designware_core tpm_tis_core i2c_i801 tpm dell_smo8800 dell_rbtn rfkill wmi nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel mmc_core serio_raw fjes i2c_hid e1000e ptp pps_core [ 912.269609] CPU: 2 PID: 867 Comm: NetworkManager Tainted: GW 4.10.0+ #1 [ 912.270919] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 [ 912.272242] task: 8f3fb7629d80 task.stack: b79243cec000 [ 912.273576] RIP: 0010:pci_restore_msi_state+0x1bd/0x270 [ 912.274916] RSP: 0018:b79243cef540 EFLAGS: 00010286 [ 912.276262] RAX: RBX: 8f3fe97f9000 RCX: [ 912.277623] RDX: 0080 RSI: 0246 RDI: 0246 [ 912.278990] RBP: b79243cef560 R08: 0002 R09: b79243cef50c [ 912.280359] R10: 00c8 R11: 8f3fecc00028 R12: [ 912.281735] R13: fffc R14: 8f3fe97f97e0 R15: 8f3fe97f90a0 [ 912.283114] FS: 7fb468d04940() GS:8f3fedc8() knlGS: [ 912.284506] CS: 0010 DS: ES: CR0: 80050033 [ 912.286248] CR2: 003c CR3: 0007f5881000 CR4: 001406a0 [ 912.287652] Call Trace: [ 912.289049] pci_restore_state.part.35+0x119/0x240 [ 912.290449] ? pci_restore_standard_config+0x40/0x40 [ 912.291840] pci_restore_state+0x18/0x20 [ 912.293224] pci_restore_standard_config+0x37/0x40 [ 912.294599] pci_pm_runtime_resume+0x46/0xa0 [ 912.295969] __rpm_callback+0xc2/0x200 [ 912.297337] ? ipv6_mc_down+0x6d/0x80 [ 912.298703] rpm_callback+0x5f/0x80 [ 912.300063] ? pci_restore_standard_config+0x40/0x40 [ 912.301423] rpm_resume+0x4a4/0x6b0 [ 912.302778] ? inetdev_event+0x3d/0x4e0 [ 912.304133] ? skb_dequeue+0x59/0x70 [ 912.305487] __pm_runtime_resume+0x4e/0x80 [ 912.306839] e1000e_open+0x59/0x450 [e1000e] [ 912.308175] __dev_open+0xc6/0x140 [ 912.309494] ? _raw_spin_unlock_bh+0x1a/0x20 [ 912.310801] __dev_change_flags+0x9d/0x160 [ 912.312103] dev_change_flags+0x29/0x60 [ 912.313391] do_setlink+0x338/0xc90 [ 912.314643] ? __nla_reserve+0x41/0x50 [ 912.315876] ? __nla_put+0x20/0x30 [ 912.317094] ? _raw_read_unlock_bh+0x20/0x30 [ 912.318296] ? inet6_fill_ifla6_attrs+0x494/0x4b0 [ 912.319481] ? inet6_fill_link_af+0x1a/0x30 [ 912.320651] ? rtnl_fill_ifinfo+0xb62/0x10c0 [ 912.321817] ? nla_parse+0x31/0x110 [ 912.323566] rtnl_newlink+0x7ac/0x8e0 [ 912.325432] ? security_capset+0x60/0x80 [ 912.327301] ? ns_capable_common+0x68/0x80 [ 912.329151] ? ns_capable+0x13/0x20 [ 912.330949] rtnetlink_rcv_msg+0xe6/0x210 [ 912.332712] ? __d_lookup+0x116/0x130 [ 912.334455] ? __kmalloc_node_track_caller+0x1f6/0x2b0 [ 912.336182] ? __alloc_skb+0x87/0x1c0 [ 912.337858] ? rtnl_newlink+0x8e0/0x8e0 [ 912.339504] netlink_rcv_skb+0xa4/0xc0 [ 912.341130] rtnetlink_rcv+0x28/0x30 [ 912.342719] netlink_unicast+0x18c/0x220 [ 912.344262] netlink_sendmsg+0x2f7/0x3b0 [ 912.345800] sock_sendmsg+0x38/0x50 [ 912.347304] ___sys_sendmsg+0x29d/0x2b0 [ 912.348765] ?
[4.10][regression][PM] Oops pci_restore_msi_state() e1000e?
Hello kernel devs, Hibernation appears broken for me in 4.10, I notice the e1000e does not resume on boot, and kernel shows why.. This kernel contains agd5f's 4.11/4.12-drm-next branches merged in. I am unsure if this is a result of the AMDGPU performing a bad hibernation (since it hangs when it finishes dumping pages to disk and doesn't reboot system when /sys/power/disk is set for 'reboot' mode.) otherwise this bug has been persistent in 4.10-rcX. Thanks, Shawn [ 912.256010] BUG: unable to handle kernel NULL pointer dereference at 003c [ 912.257227] IP: pci_restore_msi_state+0x1bd/0x270 [ 912.258218] PGD 0 [ 912.260182] Oops: [#1] SMP [ 912.261168] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev intel_rapl arc4 iwlmvm x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp iTCO_wdt vfat dell_laptop sparse_keymap kvm_intel fat mac80211 iTCO_vendor_support dell_smbios mei_wdt dcdbas dell_smm_hwmon ppdev kvm uvcvideo videobuf2_vmalloc snd_hda_codec_realtek snd_hda_codec_generic snd_usb_audio videobuf2_memops videobuf2_v4l2 irqbypass videobuf2_core snd_hda_codec_hdmi crct10dif_pclmul snd_soc_rt5640 crc32_pclmul snd_soc_rl6231 ghash_clmulni_intel snd_hda_intel snd_soc_core snd_hda_codec snd_usbmidi_lib snd_hda_core snd_compress snd_pcm_dmaengine ac97_bus iwlwifi intel_cstate intel_uncore videodev snd_hwdep intel_rapl_perf snd_seq [ 912.265654] media snd_rawmidi snd_seq_device cfg80211 snd_pcm snd_timer pcspkr ie31200_edac joydev snd video snd_soc_sst_acpi soundcore mei_me parport_pc edac_core elan_i2c mei parport snd_soc_sst_match i2c_designware_platform shpchp spi_pxa2xx_platform tpm_tis dw_dmac lpc_ich i2c_designware_core tpm_tis_core i2c_i801 tpm dell_smo8800 dell_rbtn rfkill wmi nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel mmc_core serio_raw fjes i2c_hid e1000e ptp pps_core [ 912.269609] CPU: 2 PID: 867 Comm: NetworkManager Tainted: GW 4.10.0+ #1 [ 912.270919] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 [ 912.272242] task: 8f3fb7629d80 task.stack: b79243cec000 [ 912.273576] RIP: 0010:pci_restore_msi_state+0x1bd/0x270 [ 912.274916] RSP: 0018:b79243cef540 EFLAGS: 00010286 [ 912.276262] RAX: RBX: 8f3fe97f9000 RCX: [ 912.277623] RDX: 0080 RSI: 0246 RDI: 0246 [ 912.278990] RBP: b79243cef560 R08: 0002 R09: b79243cef50c [ 912.280359] R10: 00c8 R11: 8f3fecc00028 R12: [ 912.281735] R13: fffc R14: 8f3fe97f97e0 R15: 8f3fe97f90a0 [ 912.283114] FS: 7fb468d04940() GS:8f3fedc8() knlGS: [ 912.284506] CS: 0010 DS: ES: CR0: 80050033 [ 912.286248] CR2: 003c CR3: 0007f5881000 CR4: 001406a0 [ 912.287652] Call Trace: [ 912.289049] pci_restore_state.part.35+0x119/0x240 [ 912.290449] ? pci_restore_standard_config+0x40/0x40 [ 912.291840] pci_restore_state+0x18/0x20 [ 912.293224] pci_restore_standard_config+0x37/0x40 [ 912.294599] pci_pm_runtime_resume+0x46/0xa0 [ 912.295969] __rpm_callback+0xc2/0x200 [ 912.297337] ? ipv6_mc_down+0x6d/0x80 [ 912.298703] rpm_callback+0x5f/0x80 [ 912.300063] ? pci_restore_standard_config+0x40/0x40 [ 912.301423] rpm_resume+0x4a4/0x6b0 [ 912.302778] ? inetdev_event+0x3d/0x4e0 [ 912.304133] ? skb_dequeue+0x59/0x70 [ 912.305487] __pm_runtime_resume+0x4e/0x80 [ 912.306839] e1000e_open+0x59/0x450 [e1000e] [ 912.308175] __dev_open+0xc6/0x140 [ 912.309494] ? _raw_spin_unlock_bh+0x1a/0x20 [ 912.310801] __dev_change_flags+0x9d/0x160 [ 912.312103] dev_change_flags+0x29/0x60 [ 912.313391] do_setlink+0x338/0xc90 [ 912.314643] ? __nla_reserve+0x41/0x50 [ 912.315876] ? __nla_put+0x20/0x30 [ 912.317094] ? _raw_read_unlock_bh+0x20/0x30 [ 912.318296] ? inet6_fill_ifla6_attrs+0x494/0x4b0 [ 912.319481] ? inet6_fill_link_af+0x1a/0x30 [ 912.320651] ? rtnl_fill_ifinfo+0xb62/0x10c0 [ 912.321817] ? nla_parse+0x31/0x110 [ 912.323566] rtnl_newlink+0x7ac/0x8e0 [ 912.325432] ? security_capset+0x60/0x80 [ 912.327301] ? ns_capable_common+0x68/0x80 [ 912.329151] ? ns_capable+0x13/0x20 [ 912.330949] rtnetlink_rcv_msg+0xe6/0x210 [ 912.332712] ? __d_lookup+0x116/0x130 [ 912.334455] ? __kmalloc_node_track_caller+0x1f6/0x2b0 [ 912.336182] ? __alloc_skb+0x87/0x1c0 [ 912.337858] ? rtnl_newlink+0x8e0/0x8e0 [ 912.339504] netlink_rcv_skb+0xa4/0xc0 [ 912.341130] rtnetlink_rcv+0x28/0x30 [ 912.342719] netlink_unicast+0x18c/0x220 [ 912.344262] netlink_sendmsg+0x2f7/0x3b0 [ 912.345800] sock_sendmsg+0x38/0x50 [ 912.347304] ___sys_sendmsg+0x29d/0x2b0 [ 912.348765] ?
[4.10-rc6][regression][tty] Crash in n_tty_receive_buf_common()
Hello kernel devs, Triggered an interesting kernel panic while in KVM in a old Windows 2008R2 VM to connect to some legacy server, X froze, manages to capture oops with magic emergency key sync. Feb 3 03:03:27 segfault kernel: [ 2785.908618] BUG: unable to handle kernel paging request at 2260 Feb 3 03:03:27 segfault kernel: [ 2785.908706] IP: n_tty_receive_buf_common+0x70/0xd80 Feb 3 03:03:27 segfault kernel: [ 2785.908741] PGD 0 Feb 3 03:03:27 segfault kernel: [ 2785.908742] Feb 3 03:03:27 segfault kernel: [ 2785.908774] Oops: [#1] SMP Feb 3 03:03:27 segfault kernel: [ 2785.908799] Modules linked in: tun ebtable_filter ebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev arc4 iwlmvm intel_rapl x86_pkg_temp_thermal mac80211 intel_powerclamp coretemp snd_usb_audio kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_codec_hdmi uvcvideo videobuf2_vmalloc snd_hda_intel videobuf2_memops videobuf2_v4l2 snd_usbmidi_lib snd_rawmidi vfat snd_soc_rt5640 videobuf2_core snd_hda_codec videodev irqbypass dell_wmi dell_laptop snd_soc_rl6231 sparse_keymap snd_soc_core dell_smbios dcdbas media dell_smm_hwmon iTCO_wdt mei_wdt ppdev iTCO_vendor_support crct10dif_pclmul fat snd_hda_core crc32_pclmul ghash_clmulni_intel intel_cstate snd_compress intel_uncore snd_pcm_dmaengine snd_hwdep ac97_bus pcspkr Feb 3 03:03:27 segfault kernel: [ 2785.909272] intel_rapl_perf iwlwifi snd_seq snd_seq_device snd_pcm i2c_i801 cfg80211 ie31200_edac joydev edac_core snd_soc_sst_acpi snd_timer snd elan_i2c wmi i2c_designware_platform i2c_designware_core snd_soc_sst_match mei_me tpm_tis tpm_tis_core dell_rbtn rfkill video parport_pc dw_dmac soundcore mei tpm parport dell_smo8800 shpchp lpc_ich spi_pxa2xx_platform nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel serio_raw mmc_core fjes i2c_hid e1000e ptp pps_core Feb 3 03:03:27 segfault kernel: [ 2785.909654] CPU: 0 PID: 159 Comm: kworker/u16:2 Not tainted 4.10.0-rc6+ #1 Feb 3 03:03:27 segfault kernel: [ 2785.909659] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 Feb 3 03:03:27 segfault kernel: [ 2785.909664] Workqueue: events_unbound flush_to_ldisc Feb 3 03:03:27 segfault kernel: [ 2785.909668] task: 9fc3496b3b00 task.stack: c3a8c3c8c000 Feb 3 03:03:27 segfault kernel: [ 2785.909673] RIP: 0010:n_tty_receive_buf_common+0x70/0xd80 Feb 3 03:03:27 segfault kernel: [ 2785.909675] RSP: 0018:c3a8c3c8fd48 EFLAGS: 00010297 Feb 3 03:03:27 segfault kernel: [ 2785.909678] RAX: RBX: 9fc252b33000 RCX: 0010 Feb 3 03:03:27 segfault kernel: [ 2785.909681] RDX: 8000 RSI: 9fc252b33020 RDI: 9fc1c839f8c0 Feb 3 03:03:27 segfault kernel: [ 2785.909683] RBP: c3a8c3c8fde8 R08: 0001 R09: Feb 3 03:03:27 segfault kernel: [ 2785.909685] R10: R11: 0aac R12: 9fc1a7be5808 Feb 3 03:03:27 segfault kernel: [ 2785.909687] R13: 9fc3379535d0 R14: 9fc1a7be5828 R15: 9fc1c839f800 Feb 3 03:03:27 segfault kernel: [ 2785.909691] FS: () GS:9fc36dc0() knlGS: Feb 3 03:03:27 segfault kernel: [ 2785.909693] CS: 0010 DS: ES: CR0: 80050033 Feb 3 03:03:27 segfault kernel: [ 2785.909695] CR2: 2260 CR3: 00067ce09000 CR4: 001426b0 Feb 3 03:03:27 segfault kernel: [ 2785.909697] Call Trace: Feb 3 03:03:27 segfault kernel: [ 2785.909705] n_tty_receive_buf2+0x14/0x20 Feb 3 03:03:27 segfault kernel: [ 2785.909709] tty_ldisc_receive_buf+0x22/0x50 Feb 3 03:03:27 segfault kernel: [ 2785.909713] flush_to_ldisc+0xc6/0xe0 Feb 3 03:03:27 segfault kernel: [ 2785.909719] process_one_work+0x197/0x450 Feb 3 03:03:27 segfault kernel: [ 2785.909723] worker_thread+0x4e/0x4a0 Feb 3 03:03:27 segfault kernel: [ 2785.909728] kthread+0x101/0x140 Feb 3 03:03:27 segfault kernel: [ 2785.909732] ? process_one_work+0x450/0x450 Feb 3 03:03:27 segfault kernel: [ 2785.909737] ? kthread_park+0x90/0x90 Feb 3 03:03:27 segfault kernel: [ 2785.909760] ret_from_fork+0x2c/0x40 Feb 3 03:03:27 segfault kernel: [ 2785.909761] Code: ff ff e8 d4 3d 33 00 49 8d 87 00 02 00 00 c7 45 b4 00 00 00 00 48 89 45 80 49 8d 87 28 02 00 00 48 89 85 78 ff ff ff 48 8b 45 b8 <48> 8b b8 60 22 00 00 48 8b 30 41 8b 8f 10 01 00 00 8d 97 00 10 Feb 3 03:03:27 segfault kernel: [ 2785.909800] RIP: n_tty_receive_buf_common+0x70/0xd80 RSP: c3a8c3c8fd48 Feb 3 03:03:27 segfault kernel: [ 2785.909801] CR2: 2260 Feb 3 03:03:27 segfault kernel: [ 2785.909803] ---[ end trace e8b859cad4b16c5b ]--- Thanks, Shawn
[4.10-rc6][regression][tty] Crash in n_tty_receive_buf_common()
Hello kernel devs, Triggered an interesting kernel panic while in KVM in a old Windows 2008R2 VM to connect to some legacy server, X froze, manages to capture oops with magic emergency key sync. Feb 3 03:03:27 segfault kernel: [ 2785.908618] BUG: unable to handle kernel paging request at 2260 Feb 3 03:03:27 segfault kernel: [ 2785.908706] IP: n_tty_receive_buf_common+0x70/0xd80 Feb 3 03:03:27 segfault kernel: [ 2785.908741] PGD 0 Feb 3 03:03:27 segfault kernel: [ 2785.908742] Feb 3 03:03:27 segfault kernel: [ 2785.908774] Oops: [#1] SMP Feb 3 03:03:27 segfault kernel: [ 2785.908799] Modules linked in: tun ebtable_filter ebtables ip6table_filter ip6_tables bridge stp llc toshiba_acpi industrialio toshiba_haps hp_accel lis3lv02d input_polldev arc4 iwlmvm intel_rapl x86_pkg_temp_thermal mac80211 intel_powerclamp coretemp snd_usb_audio kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_codec_hdmi uvcvideo videobuf2_vmalloc snd_hda_intel videobuf2_memops videobuf2_v4l2 snd_usbmidi_lib snd_rawmidi vfat snd_soc_rt5640 videobuf2_core snd_hda_codec videodev irqbypass dell_wmi dell_laptop snd_soc_rl6231 sparse_keymap snd_soc_core dell_smbios dcdbas media dell_smm_hwmon iTCO_wdt mei_wdt ppdev iTCO_vendor_support crct10dif_pclmul fat snd_hda_core crc32_pclmul ghash_clmulni_intel intel_cstate snd_compress intel_uncore snd_pcm_dmaengine snd_hwdep ac97_bus pcspkr Feb 3 03:03:27 segfault kernel: [ 2785.909272] intel_rapl_perf iwlwifi snd_seq snd_seq_device snd_pcm i2c_i801 cfg80211 ie31200_edac joydev edac_core snd_soc_sst_acpi snd_timer snd elan_i2c wmi i2c_designware_platform i2c_designware_core snd_soc_sst_match mei_me tpm_tis tpm_tis_core dell_rbtn rfkill video parport_pc dw_dmac soundcore mei tpm parport dell_smo8800 shpchp lpc_ich spi_pxa2xx_platform nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc amdkfd amd_iommu_v2 amdgpu i2c_algo_bit drm_kms_helper ttm drm netconsole sdhci_pci sdhci_acpi sdhci crc32c_intel serio_raw mmc_core fjes i2c_hid e1000e ptp pps_core Feb 3 03:03:27 segfault kernel: [ 2785.909654] CPU: 0 PID: 159 Comm: kworker/u16:2 Not tainted 4.10.0-rc6+ #1 Feb 3 03:03:27 segfault kernel: [ 2785.909659] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 Feb 3 03:03:27 segfault kernel: [ 2785.909664] Workqueue: events_unbound flush_to_ldisc Feb 3 03:03:27 segfault kernel: [ 2785.909668] task: 9fc3496b3b00 task.stack: c3a8c3c8c000 Feb 3 03:03:27 segfault kernel: [ 2785.909673] RIP: 0010:n_tty_receive_buf_common+0x70/0xd80 Feb 3 03:03:27 segfault kernel: [ 2785.909675] RSP: 0018:c3a8c3c8fd48 EFLAGS: 00010297 Feb 3 03:03:27 segfault kernel: [ 2785.909678] RAX: RBX: 9fc252b33000 RCX: 0010 Feb 3 03:03:27 segfault kernel: [ 2785.909681] RDX: 8000 RSI: 9fc252b33020 RDI: 9fc1c839f8c0 Feb 3 03:03:27 segfault kernel: [ 2785.909683] RBP: c3a8c3c8fde8 R08: 0001 R09: Feb 3 03:03:27 segfault kernel: [ 2785.909685] R10: R11: 0aac R12: 9fc1a7be5808 Feb 3 03:03:27 segfault kernel: [ 2785.909687] R13: 9fc3379535d0 R14: 9fc1a7be5828 R15: 9fc1c839f800 Feb 3 03:03:27 segfault kernel: [ 2785.909691] FS: () GS:9fc36dc0() knlGS: Feb 3 03:03:27 segfault kernel: [ 2785.909693] CS: 0010 DS: ES: CR0: 80050033 Feb 3 03:03:27 segfault kernel: [ 2785.909695] CR2: 2260 CR3: 00067ce09000 CR4: 001426b0 Feb 3 03:03:27 segfault kernel: [ 2785.909697] Call Trace: Feb 3 03:03:27 segfault kernel: [ 2785.909705] n_tty_receive_buf2+0x14/0x20 Feb 3 03:03:27 segfault kernel: [ 2785.909709] tty_ldisc_receive_buf+0x22/0x50 Feb 3 03:03:27 segfault kernel: [ 2785.909713] flush_to_ldisc+0xc6/0xe0 Feb 3 03:03:27 segfault kernel: [ 2785.909719] process_one_work+0x197/0x450 Feb 3 03:03:27 segfault kernel: [ 2785.909723] worker_thread+0x4e/0x4a0 Feb 3 03:03:27 segfault kernel: [ 2785.909728] kthread+0x101/0x140 Feb 3 03:03:27 segfault kernel: [ 2785.909732] ? process_one_work+0x450/0x450 Feb 3 03:03:27 segfault kernel: [ 2785.909737] ? kthread_park+0x90/0x90 Feb 3 03:03:27 segfault kernel: [ 2785.909760] ret_from_fork+0x2c/0x40 Feb 3 03:03:27 segfault kernel: [ 2785.909761] Code: ff ff e8 d4 3d 33 00 49 8d 87 00 02 00 00 c7 45 b4 00 00 00 00 48 89 45 80 49 8d 87 28 02 00 00 48 89 85 78 ff ff ff 48 8b 45 b8 <48> 8b b8 60 22 00 00 48 8b 30 41 8b 8f 10 01 00 00 8d 97 00 10 Feb 3 03:03:27 segfault kernel: [ 2785.909800] RIP: n_tty_receive_buf_common+0x70/0xd80 RSP: c3a8c3c8fd48 Feb 3 03:03:27 segfault kernel: [ 2785.909801] CR2: 2260 Feb 3 03:03:27 segfault kernel: [ 2785.909803] ---[ end trace e8b859cad4b16c5b ]--- Thanks, Shawn
[4.7-rc3 June 16th code][EXT4] Rename file corruption?
Hello Kernel devs, I built a snapshot of Linus's kernel (master) Triggered fault in EXT4 compiling LLVM/clang/Mesa: Jun 15 12:36:41 segfault kernel: [34407.966896] Modules linked in: bnep bluetooth cpufreq_stats ebtable_filter ebtables ip6table_filter ip6_tables bridge amdkfd amd_iommu_v2 amdgpu intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel arc4 iwlmvm kvm coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mac80211 uvcvideo snd_hda_intel snd_hda_codec videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 vfat snd_usb_audio irqbypass crct10dif_pclmul videobuf2_core snd_soc_rt5640 snd_soc_rl6231 i2c_algo_bit snd_soc_core snd_usbmidi_lib snd_compress crc32_pclmul videodev ghash_clmulni_intel fat ttm snd_hda_core snd_pcm_dmaengine ac97_bus snd_rawmidi snd_hwdep snd_seq intel_cstate drm_kms_helper intel_uncore drm dell_wmi mei_wdt sparse_keymap iwlwifi snd_seq_device media snd_pcm iTCO_wdt dell_laptop dell_smbios iTCO_vendor_support snd_timer dcdbas ppdev dell_smm_hwmon cfg80211 snd pcspkr joydev elan_i2c ie31200_edac wmi i2c_designware_platform edac_core mei_me shpchp dw_dmac parport_pc parport mei i2c_designware_core lpc_ich video snd_soc_sst_acpi snd_soc_sst_match soundcore dw_dmac_core i2c_i801 tpm_tis spi_pxa2xx_platform tpm dell_rbtn rfkill dell_smo8800 nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc 8021q garp stp llc netconsole mrp sdhci_pci crc32c_intel sdhci_acpi sdhci serio_raw mmc_core fjes i2c_hid e1000e ptp pps_core Jun 15 12:36:41 segfault kernel: [34407.973782] CPU: 3 PID: 12388 Comm: gcc Not tainted 4.7.0-rc3+ #1 Jun 15 12:36:41 segfault kernel: [34407.974026] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 Jun 15 12:36:41 segfault kernel: [34407.974289] 0286 40a52c61 88073fe9bc90 813d07af Jun 15 12:36:41 segfault kernel: [34407.974576] 88073fe9bcd0 8109f53b Jun 15 12:36:41 segfault kernel: [34407.974864] 01183fe9bcf8 880487740928 880487740928 Jun 15 12:36:41 segfault kernel: [34407.975150] Call Trace: Jun 15 12:36:41 segfault kernel: [34407.975246] [] dump_stack+0x63/0x84 Jun 15 12:36:41 segfault kernel: [34407.975432] [] __warn+0xcb/0xf0 Jun 15 12:36:41 segfault kernel: [34407.975605] [] warn_slowpath_null+0x1d/0x20 Jun 15 12:36:41 segfault kernel: [34407.975817] [] drop_nlink+0x3e/0x50 Jun 15 12:36:41 segfault kernel: [34407.976068] [] ext4_rename+0x530/0x910 Jun 15 12:36:41 segfault kernel: [34407.976332] [] ? terminate_walk+0x8e/0xf0 Jun 15 12:36:41 segfault kernel: [34407.976607] [] ext4_rename2+0x1d/0x30 Jun 15 12:36:41 segfault kernel: [34407.976866] [] vfs_rename+0x5a3/0x900 Jun 15 12:36:41 segfault kernel: [34407.977125] [] ? trailing_symlink+0x181/0x220 Jun 15 12:36:41 segfault kernel: [34407.977416] [] SyS_rename+0x3a7/0x3d0 Jun 15 12:36:41 segfault kernel: [34407.977679] [] entry_SYSCALL_64_fastpath+0x1a/0xa4 Jun 15 12:36:41 segfault kernel: [34407.978014] ---[ end trace 812bc2d188b90844 ]--- Jun 15 12:36:45 segfault kernel: [34412.076658] [ cut here ] Jun 15 12:36:45 segfault kernel: [34412.076897] WARNING: CPU: 2 PID: 13368 at fs/inode.c:280 drop_nlink+0x3e/0x50 On shutdown, had inode corruption, rebooted had to fsck to repair. Thanks, Shawn
[4.7-rc3 June 16th code][EXT4] Rename file corruption?
Hello Kernel devs, I built a snapshot of Linus's kernel (master) Triggered fault in EXT4 compiling LLVM/clang/Mesa: Jun 15 12:36:41 segfault kernel: [34407.966896] Modules linked in: bnep bluetooth cpufreq_stats ebtable_filter ebtables ip6table_filter ip6_tables bridge amdkfd amd_iommu_v2 amdgpu intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel arc4 iwlmvm kvm coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mac80211 uvcvideo snd_hda_intel snd_hda_codec videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 vfat snd_usb_audio irqbypass crct10dif_pclmul videobuf2_core snd_soc_rt5640 snd_soc_rl6231 i2c_algo_bit snd_soc_core snd_usbmidi_lib snd_compress crc32_pclmul videodev ghash_clmulni_intel fat ttm snd_hda_core snd_pcm_dmaengine ac97_bus snd_rawmidi snd_hwdep snd_seq intel_cstate drm_kms_helper intel_uncore drm dell_wmi mei_wdt sparse_keymap iwlwifi snd_seq_device media snd_pcm iTCO_wdt dell_laptop dell_smbios iTCO_vendor_support snd_timer dcdbas ppdev dell_smm_hwmon cfg80211 snd pcspkr joydev elan_i2c ie31200_edac wmi i2c_designware_platform edac_core mei_me shpchp dw_dmac parport_pc parport mei i2c_designware_core lpc_ich video snd_soc_sst_acpi snd_soc_sst_match soundcore dw_dmac_core i2c_i801 tpm_tis spi_pxa2xx_platform tpm dell_rbtn rfkill dell_smo8800 nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc 8021q garp stp llc netconsole mrp sdhci_pci crc32c_intel sdhci_acpi sdhci serio_raw mmc_core fjes i2c_hid e1000e ptp pps_core Jun 15 12:36:41 segfault kernel: [34407.973782] CPU: 3 PID: 12388 Comm: gcc Not tainted 4.7.0-rc3+ #1 Jun 15 12:36:41 segfault kernel: [34407.974026] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015 Jun 15 12:36:41 segfault kernel: [34407.974289] 0286 40a52c61 88073fe9bc90 813d07af Jun 15 12:36:41 segfault kernel: [34407.974576] 88073fe9bcd0 8109f53b Jun 15 12:36:41 segfault kernel: [34407.974864] 01183fe9bcf8 880487740928 880487740928 Jun 15 12:36:41 segfault kernel: [34407.975150] Call Trace: Jun 15 12:36:41 segfault kernel: [34407.975246] [] dump_stack+0x63/0x84 Jun 15 12:36:41 segfault kernel: [34407.975432] [] __warn+0xcb/0xf0 Jun 15 12:36:41 segfault kernel: [34407.975605] [] warn_slowpath_null+0x1d/0x20 Jun 15 12:36:41 segfault kernel: [34407.975817] [] drop_nlink+0x3e/0x50 Jun 15 12:36:41 segfault kernel: [34407.976068] [] ext4_rename+0x530/0x910 Jun 15 12:36:41 segfault kernel: [34407.976332] [] ? terminate_walk+0x8e/0xf0 Jun 15 12:36:41 segfault kernel: [34407.976607] [] ext4_rename2+0x1d/0x30 Jun 15 12:36:41 segfault kernel: [34407.976866] [] vfs_rename+0x5a3/0x900 Jun 15 12:36:41 segfault kernel: [34407.977125] [] ? trailing_symlink+0x181/0x220 Jun 15 12:36:41 segfault kernel: [34407.977416] [] SyS_rename+0x3a7/0x3d0 Jun 15 12:36:41 segfault kernel: [34407.977679] [] entry_SYSCALL_64_fastpath+0x1a/0xa4 Jun 15 12:36:41 segfault kernel: [34407.978014] ---[ end trace 812bc2d188b90844 ]--- Jun 15 12:36:45 segfault kernel: [34412.076658] [ cut here ] Jun 15 12:36:45 segfault kernel: [34412.076897] WARNING: CPU: 2 PID: 13368 at fs/inode.c:280 drop_nlink+0x3e/0x50 On shutdown, had inode corruption, rebooted had to fsck to repair. Thanks, Shawn
[4.6-rc1/rc2][snd_usb_audio] regression: BUG usb_audio_probe+0x2ca/0x9a0
Hello kernel devs, USB audio devices broke: [ 13.873279] BUG: unable to handle kernel NULL pointer dereference at 0014 [ 13.874701] IP: [] usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio] [ 13.876050] *PGD 0 * [ 13.876942] Oops*: [#1] SMP * [ 13.877896] Modules linked in*: snd_usb_audio(+) mac80211 videobuf2_vmalloc vfat irqbypass videobuf2_memops fat crct10dif_pclmul videob* [ 13.884695] * tpm soundcore i2c_designware_core i2c_i801 wmi dell_rbtn rfkill dell_smo8800 nfsd auth_rpcgss nfs_acl lockd grace sunrpc * [ 13.888261] CPU*: 7 PID: 628 Comm: systemd-udevd Not tainted 4.6.0-rc2 #1* [ 13.889507] Hardware name*: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015* [ 13.890794] task*: 8807fdc61d80 ti: 8808074d4000 task.ti: 8808074d4000* [ 13.892094] RIP*: 0010:[] [] usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio]* [ 13.893543] RSP*: 0018:8808074d7a80 EFLAGS: 00010246* [ 13.894769] RAX*: RBX: RCX: * [ 13.896051] RDX*: 8808082b2b80 RSI: RDI: 880807ec6880* [ 13.897347] RBP*: 8808074d7af8 R08: 0001a6c0 R09: 813cf33c* [ 13.898616] R10*: ea001ff91a00 R11: 8807fe2b7871 R12: 8807fdd3a900* [ 13.899907] R13*: 0002 R14: 8807fdd3a954 R15: 88080748fd12* [ 13.901205] FS*: 7fba7d6ae8c0() GS:88082ddc() knlGS:* [ 13.902827] CS*: 0010 DS: ES: CR0: 80050033* [ 13.904091] CR2*: 0014 CR3: 000807e7f000 CR4: 001406e0* [ 13.905398] *Stack:* [ 13.906448] * 8807fedaacc8 8807feecac00 8807fedaacc8* [ 13.907784] * 0246 8808074d7ab8 8807ff1d3000 3634304253550282* [ 13.909115] * ff00343461303a64 e52cf258 8807fecd5098 8807fecd5000* [ 13.910710] *Call Trace:* [ 13.912339] * [] usb_probe_interface+0x1bd/0x300* [ 13.913581] * [] driver_probe_device+0x22c/0x440* [ 13.914838] * [] __driver_attach+0xd1/0xf0* [ 13.916099] * [] ? driver_probe_device+0x440/0x440* [ 13.917396] * [] bus_for_each_dev+0x6c/0xc0* [ 13.918660] * [] driver_attach+0x1e/0x20* [ 13.919822] * [] bus_add_driver+0x1eb/0x280* [ 13.921074] * [] driver_register+0x60/0xe0* [ 13.921085] * [] usb_register_driver+0x84/0x140* [ 13.921086] * [] ? 0xc086d000* [ 13.921091] * [] usb_audio_driver_init+0x1e/0x1000 [snd_usb_audio]* [ 13.921095] * [] do_one_initcall+0xb3/0x200* [ 13.921096] * [] ? __vunmap+0x81/0xd0* [ 13.921098] * [] ? kmem_cache_alloc_trace+0x189/0x1f0* [ 13.921099] * [] ? kfree+0x15b/0x170* [ 13.921101] * [] ? do_init_module+0x27/0x1d7* [ 13.921102] * [] do_init_module+0x5f/0x1d7* [ 13.921104] * [] load_module+0x20c4/0x26f0* [ 13.921105] * [] ? __symbol_put+0x60/0x60* [ 13.921107] * [] ? vfs_read+0x114/0x130* [ 13.921108] * [] SYSC_finit_module+0xe6/0x120* [ 13.921109] * [] SyS_finit_module+0xe/0x10* [ 13.92] * [] entry_SYSCALL_64_fastpath+0x1a/0xa4* [ 13.921119] Code*: 02 00 8b 75 ac 4c 89 e7 e8 94 75 00 00 85 c0 89 c1 0f 88 ae 00 00 00 49 8b 7c 24 10 e8 00 6f c2 ff 85 c0 89 c1 0f 88* [ 13.921123] RIP [] usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio] [ 13.921124] * RSP * [ 13.921124] CR2*: 0014* [ 13.921132] *---[ end trace 29d92678e4d33f46 ]---* Thanks, Shawn
[4.6-rc1/rc2][snd_usb_audio] regression: BUG usb_audio_probe+0x2ca/0x9a0
Hello kernel devs, USB audio devices broke: [ 13.873279] BUG: unable to handle kernel NULL pointer dereference at 0014 [ 13.874701] IP: [] usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio] [ 13.876050] *PGD 0 * [ 13.876942] Oops*: [#1] SMP * [ 13.877896] Modules linked in*: snd_usb_audio(+) mac80211 videobuf2_vmalloc vfat irqbypass videobuf2_memops fat crct10dif_pclmul videob* [ 13.884695] * tpm soundcore i2c_designware_core i2c_i801 wmi dell_rbtn rfkill dell_smo8800 nfsd auth_rpcgss nfs_acl lockd grace sunrpc * [ 13.888261] CPU*: 7 PID: 628 Comm: systemd-udevd Not tainted 4.6.0-rc2 #1* [ 13.889507] Hardware name*: Dell Inc. Precision M6800/05NG6V, BIOS A16 12/01/2015* [ 13.890794] task*: 8807fdc61d80 ti: 8808074d4000 task.ti: 8808074d4000* [ 13.892094] RIP*: 0010:[] [] usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio]* [ 13.893543] RSP*: 0018:8808074d7a80 EFLAGS: 00010246* [ 13.894769] RAX*: RBX: RCX: * [ 13.896051] RDX*: 8808082b2b80 RSI: RDI: 880807ec6880* [ 13.897347] RBP*: 8808074d7af8 R08: 0001a6c0 R09: 813cf33c* [ 13.898616] R10*: ea001ff91a00 R11: 8807fe2b7871 R12: 8807fdd3a900* [ 13.899907] R13*: 0002 R14: 8807fdd3a954 R15: 88080748fd12* [ 13.901205] FS*: 7fba7d6ae8c0() GS:88082ddc() knlGS:* [ 13.902827] CS*: 0010 DS: ES: CR0: 80050033* [ 13.904091] CR2*: 0014 CR3: 000807e7f000 CR4: 001406e0* [ 13.905398] *Stack:* [ 13.906448] * 8807fedaacc8 8807feecac00 8807fedaacc8* [ 13.907784] * 0246 8808074d7ab8 8807ff1d3000 3634304253550282* [ 13.909115] * ff00343461303a64 e52cf258 8807fecd5098 8807fecd5000* [ 13.910710] *Call Trace:* [ 13.912339] * [] usb_probe_interface+0x1bd/0x300* [ 13.913581] * [] driver_probe_device+0x22c/0x440* [ 13.914838] * [] __driver_attach+0xd1/0xf0* [ 13.916099] * [] ? driver_probe_device+0x440/0x440* [ 13.917396] * [] bus_for_each_dev+0x6c/0xc0* [ 13.918660] * [] driver_attach+0x1e/0x20* [ 13.919822] * [] bus_add_driver+0x1eb/0x280* [ 13.921074] * [] driver_register+0x60/0xe0* [ 13.921085] * [] usb_register_driver+0x84/0x140* [ 13.921086] * [] ? 0xc086d000* [ 13.921091] * [] usb_audio_driver_init+0x1e/0x1000 [snd_usb_audio]* [ 13.921095] * [] do_one_initcall+0xb3/0x200* [ 13.921096] * [] ? __vunmap+0x81/0xd0* [ 13.921098] * [] ? kmem_cache_alloc_trace+0x189/0x1f0* [ 13.921099] * [] ? kfree+0x15b/0x170* [ 13.921101] * [] ? do_init_module+0x27/0x1d7* [ 13.921102] * [] do_init_module+0x5f/0x1d7* [ 13.921104] * [] load_module+0x20c4/0x26f0* [ 13.921105] * [] ? __symbol_put+0x60/0x60* [ 13.921107] * [] ? vfs_read+0x114/0x130* [ 13.921108] * [] SYSC_finit_module+0xe6/0x120* [ 13.921109] * [] SyS_finit_module+0xe/0x10* [ 13.92] * [] entry_SYSCALL_64_fastpath+0x1a/0xa4* [ 13.921119] Code*: 02 00 8b 75 ac 4c 89 e7 e8 94 75 00 00 85 c0 89 c1 0f 88 ae 00 00 00 49 8b 7c 24 10 e8 00 6f c2 ff 85 c0 89 c1 0f 88* [ 13.921123] RIP [] usb_audio_probe+0x2ca/0x9a0 [snd_usb_audio] [ 13.921124] * RSP * [ 13.921124] CR2*: 0014* [ 13.921132] *---[ end trace 29d92678e4d33f46 ]---* Thanks, Shawn
[Fedora][libata][4.4-rc0/rc1] Disk cache/write error? - FLUSH CACHE EXT / WRITE FPDMA QUEUED
Hello devs, Something unusual happened today, disk locked up, went into bad state, rebooted with sysctl magic key, BIOS reported disk showed no OS found, hard powered off machine then everything was normal. Any changes recently in libata that might have caused the disk to perform a bad operation? SMART reports no faults in tests (Will perform long test later), I don't suspect disk failure (231 days, not rollover counter) kernel: 4.4.0-0.rc0.git9.2.fc24.x86_64 Filesystem: EXT4, options: noatime,nodiratime Boot command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-0.rc0.git9.2.fc24.x86_64 root=UUID=f834b05c-55f3-407b-9a63-fc6b04d4c845 ro rhgb slub_debug=- cgroup_disable=memory console=tty0 console=ttyS0,115200n8 nmi_watchdog=0 video=LVDS-1:d video=VGA-0:e audit=0 radeon.gartsize=8192 intel_iommu=igfx_off radeon.lockup_timeout=0 radeon.vm_size=16 rd.driver.blacklist=dell_rbtn LANG=en_US.UTF-8 Laptop: Dell Precision M6800 BIOS: Version A15 Controller: 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) SMART Log: Error 1 occurred at disk power-on lifetime: 5559 hours (231 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 71 03 80 04 11 e0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ea 00 00 00 00 00 a0 00 02:59:36.641 FLUSH CACHE EXT 61 00 88 ff ff ff 4f 00 02:59:36.641 WRITE FPDMA QUEUED 61 00 30 ff ff ff 4f 00 02:59:36.640 WRITE FPDMA QUEUED 61 00 20 ff ff ff 4f 00 02:59:35.952 WRITE FPDMA QUEUED 61 00 90 ff ff ff 4f 00 02:59:35.952 WRITE FPDMA QUEUED Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Fedora][libata][4.4-rc0/rc1] Disk cache/write error? - FLUSH CACHE EXT / WRITE FPDMA QUEUED
Hello devs, Something unusual happened today, disk locked up, went into bad state, rebooted with sysctl magic key, BIOS reported disk showed no OS found, hard powered off machine then everything was normal. Any changes recently in libata that might have caused the disk to perform a bad operation? SMART reports no faults in tests (Will perform long test later), I don't suspect disk failure (231 days, not rollover counter) kernel: 4.4.0-0.rc0.git9.2.fc24.x86_64 Filesystem: EXT4, options: noatime,nodiratime Boot command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-0.rc0.git9.2.fc24.x86_64 root=UUID=f834b05c-55f3-407b-9a63-fc6b04d4c845 ro rhgb slub_debug=- cgroup_disable=memory console=tty0 console=ttyS0,115200n8 nmi_watchdog=0 video=LVDS-1:d video=VGA-0:e audit=0 radeon.gartsize=8192 intel_iommu=igfx_off radeon.lockup_timeout=0 radeon.vm_size=16 rd.driver.blacklist=dell_rbtn LANG=en_US.UTF-8 Laptop: Dell Precision M6800 BIOS: Version A15 Controller: 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) SMART Log: Error 1 occurred at disk power-on lifetime: 5559 hours (231 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 71 03 80 04 11 e0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ea 00 00 00 00 00 a0 00 02:59:36.641 FLUSH CACHE EXT 61 00 88 ff ff ff 4f 00 02:59:36.641 WRITE FPDMA QUEUED 61 00 30 ff ff ff 4f 00 02:59:36.640 WRITE FPDMA QUEUED 61 00 20 ff ff ff 4f 00 02:59:35.952 WRITE FPDMA QUEUED 61 00 90 ff ff ff 4f 00 02:59:35.952 WRITE FPDMA QUEUED Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[UVC][4.x][USB] Logitech QuickCam 9000 - Stability problems device disconnects/fails to reset
Hello kernel devs, I've been noticing stability problems with my USB webcam, it used to be just bogus volume warning notice but now I have to unplug/plugin, unplug and sometimes it works, sometimes not. It seems to work less now. It used to be lesser of a problem in eariler 4.x but now in 4.2/4.3 it's become very unstable in use. The device will sometimes be force disconnected by the USB bus Both USB 2.x/USB 3.x bus device ports. Below is kernel msgs of failure: Thanks, Shawn [ 107.510683] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [ 1558.485719] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [22996.495603] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [23015.964902] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [23017.886591] restoring control ----0101/10/5 [23023.282498] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [23035.010933] usb 1-1: USB disconnect, device number 2 [23046.412316] usb 1-1: new high-speed USB device number 5 using xhci_hcd [23046.711073] usb 1-1: New USB device found, idVendor=046d, idProduct=0990 [23046.711426] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23046.711780] usb 1-1: SerialNumber: B4261720 [23046.712415] uvcvideo: Found UVC 1.00 device (046d:0990) [23046.744959] input: UVC Camera (046d:0990) as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/input/input24 [23047.138076] usb 1-1: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. [23047.138504] usb 1-1: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 [23055.241577] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23074.561834] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23089.251001] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23089.544931] restoring control ----0101/10/5 [23094.823168] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). [23104.003182] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23104.297038] restoring control ----0101/10/5 [23115.198761] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23117.118523] restoring control ----0101/10/5 [23137.491620] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23139.411020] restoring control ----0101/10/5 [23146.809652] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23161.863901] usb 1-1: USB disconnect, device number 5 [23166.711888] usb 1-2: new high-speed USB device number 6 using xhci_hcd [23167.010096] usb 1-2: New USB device found, idVendor=046d, idProduct=0990 [23167.010432] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23167.010777] usb 1-2: SerialNumber: B4261720 [23167.011452] uvcvideo: Found UVC 1.00 device (046d:0990) [23167.044467] input: UVC Camera (046d:0990) as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input25 [23167.437046] usb 1-2: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. [23167.437468] usb 1-2: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 [23180.400229] usb 1-2: reset high-speed USB device number 6 using xhci_hcd [23182.319743] restoring control ----0101/10/5 [23189.733146] usb 1-2: reset high-speed USB device number 6 using xhci_hcd [23204.787522] usb 1-2: USB disconnect, device number 6 [23217.185055] usb 1-2: new high-speed USB device number 7 using xhci_hcd [23217.482873] usb 1-2: New USB device found, idVendor=046d, idProduct=0990 [23217.483215] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23217.483570] usb 1-2: SerialNumber: B4261720 [23217.484210] uvcvideo: Found UVC 1.00 device (046d:0990) [23217.516471] input: UVC Camera (046d:0990) as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input26 [23217.908525] usb 1-2: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. [23217.908948] usb 1-2: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 [23234.440066] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23240.010115] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). [23247.331979] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23247.627113] restoring control ----0101/10/5 [23262.752322] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23264.672678] restoring control ----0101/10/5 [23271.261131] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23281.899397] usb 1-2: USB disconnect, device number 7 [23309.462489] usb 1-2: new high-speed USB device number 8 using xhci_hcd [23309.760538] usb 1-2: New USB device found, idVendor=046d, idProduct=0990 [23309.760872] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23309.761220] usb 1-2: SerialNumber: B4261720
[UVC][4.x][USB] Logitech QuickCam 9000 - Stability problems device disconnects/fails to reset
Hello kernel devs, I've been noticing stability problems with my USB webcam, it used to be just bogus volume warning notice but now I have to unplug/plugin, unplug and sometimes it works, sometimes not. It seems to work less now. It used to be lesser of a problem in eariler 4.x but now in 4.2/4.3 it's become very unstable in use. The device will sometimes be force disconnected by the USB bus Both USB 2.x/USB 3.x bus device ports. Below is kernel msgs of failure: Thanks, Shawn [ 107.510683] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [ 1558.485719] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [22996.495603] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [23015.964902] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [23017.886591] restoring control ----0101/10/5 [23023.282498] usb 1-1: reset high-speed USB device number 2 using xhci_hcd [23035.010933] usb 1-1: USB disconnect, device number 2 [23046.412316] usb 1-1: new high-speed USB device number 5 using xhci_hcd [23046.711073] usb 1-1: New USB device found, idVendor=046d, idProduct=0990 [23046.711426] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23046.711780] usb 1-1: SerialNumber: B4261720 [23046.712415] uvcvideo: Found UVC 1.00 device (046d:0990) [23046.744959] input: UVC Camera (046d:0990) as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/input/input24 [23047.138076] usb 1-1: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. [23047.138504] usb 1-1: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 [23055.241577] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23074.561834] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23089.251001] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23089.544931] restoring control ----0101/10/5 [23094.823168] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). [23104.003182] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23104.297038] restoring control ----0101/10/5 [23115.198761] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23117.118523] restoring control ----0101/10/5 [23137.491620] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23139.411020] restoring control ----0101/10/5 [23146.809652] usb 1-1: reset high-speed USB device number 5 using xhci_hcd [23161.863901] usb 1-1: USB disconnect, device number 5 [23166.711888] usb 1-2: new high-speed USB device number 6 using xhci_hcd [23167.010096] usb 1-2: New USB device found, idVendor=046d, idProduct=0990 [23167.010432] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23167.010777] usb 1-2: SerialNumber: B4261720 [23167.011452] uvcvideo: Found UVC 1.00 device (046d:0990) [23167.044467] input: UVC Camera (046d:0990) as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input25 [23167.437046] usb 1-2: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. [23167.437468] usb 1-2: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 [23180.400229] usb 1-2: reset high-speed USB device number 6 using xhci_hcd [23182.319743] restoring control ----0101/10/5 [23189.733146] usb 1-2: reset high-speed USB device number 6 using xhci_hcd [23204.787522] usb 1-2: USB disconnect, device number 6 [23217.185055] usb 1-2: new high-speed USB device number 7 using xhci_hcd [23217.482873] usb 1-2: New USB device found, idVendor=046d, idProduct=0990 [23217.483215] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23217.483570] usb 1-2: SerialNumber: B4261720 [23217.484210] uvcvideo: Found UVC 1.00 device (046d:0990) [23217.516471] input: UVC Camera (046d:0990) as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input26 [23217.908525] usb 1-2: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. [23217.908948] usb 1-2: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 [23234.440066] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23240.010115] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). [23247.331979] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23247.627113] restoring control ----0101/10/5 [23262.752322] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23264.672678] restoring control ----0101/10/5 [23271.261131] usb 1-2: reset high-speed USB device number 7 using xhci_hcd [23281.899397] usb 1-2: USB disconnect, device number 7 [23309.462489] usb 1-2: new high-speed USB device number 8 using xhci_hcd [23309.760538] usb 1-2: New USB device found, idVendor=046d, idProduct=0990 [23309.760872] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [23309.761220] usb 1-2: SerialNumber: B4261720
[4.2-rc7][Haswell] NMI soft lockup - try_to_del_timer_sync
Hello folks, I was just using KVM and doing some VM work on my laptop when it locked up system fully, here is the kernel trace below (it repeats after the second dump) Since we're soon 'close' to 4.2 final, maybe someone can check if something regressed? Never saw this in eariler -rcX builds. Thanks, Shawn. [69399.505355] kvm: zapping shadow pages for mmio generation wraparound [69405.611747] kvm [24415]: vcpu0 unhandled rdmsr: 0x641 [69411.477997] Bridge: port 2(vnet0) entered forwarding state [70844.574880] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [swapper/3:0] [70844.575264] Modules linked in: vhost_net vhost macvtap macvlan tun ebtable_filter ebtables ip6table_filter ip6_tables bridge vfat fat intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_core videobuf2_memops arc4 iwlmvm v4l2_common mac80211 videodev snd_usb_audio snd_usbmidi_lib snd_rawmidi media iwlwifi dell_laptop cfg80211 snd_hda_codec_realtek dell_wmi snd_soc_rt5640 iTCO_wdt iTCO_vendor_support joydev lpc_ich dcdbas sparse_keymap ppdev dell_smm_hwmon mei_me snd_hda_codec_generic snd_soc_rl6231 snd_hda_codec_hdmi mei ie31200_edac edac_core dw_dmac snd_soc_core parport_pc parport snd_compress snd_pcm_dmaengine shpchp video ac97_bus dw_dmac_core i2c_i801 i2c_designware_platform i2c_designware_core [70844.579376] snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_soc_sst_acpi dell_rbtn rfkill wmi dell_smo8800 nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc 8021q garp stp llc mrp amdkfd amd_iommu_v2 radeon i2c_algo_bit drm_kms_helper ttm e1000e drm serio_raw sdhci_pci ptp sdhci_acpi pps_core sdhci mmc_core i2c_hid [70844.581351] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.2.0-0.rc7.git0.1.fc23.x86_64 #1 [70844.581804] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A14 05/24/2015 [70844.582198] task: 880809f6c4c0 ti: 88080990 task.ti: 88080990 [70844.582555] RIP: 0010:[] [] try_to_del_timer_sync+0xb/0x90 [70844.583042] RSP: 0018:88082dcc3da0 EFLAGS: 0286 [70844.583296] RAX: RBX: 0296 RCX: [70844.583637] RDX: 0001 RSI: 0296 RDI: 8800bc0612e0 [70844.584037] RBP: 88082dcc3da8 R08: 0101 R09: 0003 [70844.584373] R10: 0002 R11: 0004 R12: 88082dcc3d18 [70844.584771] R13: 8177818b R14: 88082dcc3da8 R15: 8800bc0612e0 [70844.585139] FS: () GS:88082dcc() knlGS: [70844.585524] CS: 0010 DS: ES: CR0: 80050033 [70844.585833] CR2: 140a84048000 CR3: 01c0b000 CR4: 001426e0 [70844.586200] Stack: [70844.586301] 8807650fe800 88082dcc3dc8 8110379c 88082dcc3dc8 [70844.586687] 8800bc061248 88082dcc3df8 816ac35c 000167c0 [70844.587187] 8800bc061248 8807650fe800 8807ec9c5000 88082dcc3e38 [70844.587631] Call Trace: [70844.587784] [70844.587884] [] del_timer_sync+0x4c/0x60 [70844.588188] [] inet_csk_reqsk_queue_drop+0x6c/0x1d0 [70844.588499] [] reqsk_timer_handler+0xd9/0x2a0 [70844.588817] [] ? inet_csk_reqsk_queue_drop+0x1d0/0x1d0 [70844.589158] [] call_timer_fn+0x39/0xf0 [70844.589432] [] ? inet_csk_reqsk_queue_drop+0x1d0/0x1d0 [70844.589774] [] run_timer_softirq+0x20f/0x2c0 [70844.590105] [] __do_softirq+0xfb/0x290 [70844.590365] [] irq_exit+0x119/0x120 [70844.590618] [] smp_apic_timer_interrupt+0x46/0x60 [70844.590929] [] apic_timer_interrupt+0x6b/0x70 [70844.591222] [70844.591322] [] ? hrtimer_start_range_ns+0x1bf/0x3b0 [70844.591656] [] ? cpuidle_enter_state+0x130/0x270 [70844.591961] [] ? cpuidle_enter_state+0x10b/0x270 [70844.592265] [] cpuidle_enter+0x17/0x20 [70844.592527] [] call_cpuidle+0x32/0x60 [70844.592787] [] ? cpuidle_select+0x13/0x20 [70844.593060] [] cpu_startup_entry+0x268/0x320 [70844.593347] [] start_secondary+0x186/0x1c0 [70844.593623] Code: 00 00 44 89 e0 75 0b 48 83 c4 18 5b 41 5c 41 5d 5d c3 e8 79 ab f9 ff 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 <53> 48 8d 75 e0 48 89 fb 48 83 c7 28 48 83 ec 10 65 48 8b 04 25 [70872.581083] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [swapper/3:0] [70872.581462] Modules linked in: vhost_net vhost macvtap macvlan tun ebtable_filter ebtables ip6table_filter ip6_tables bridge vfat fat intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_core videobuf2_memops arc4 iwlmvm v4l2_common mac80211 videodev snd_usb_audio snd_usbmidi_lib snd_rawmidi media iwlwifi dell_laptop cfg80211 snd_hda_codec_realtek dell_wmi snd_soc_rt5640 iTCO_wdt iTCO_vendor_support joydev lpc_ich dcdbas sparse_keymap ppdev
[4.2-rc7][Haswell] NMI soft lockup - try_to_del_timer_sync
Hello folks, I was just using KVM and doing some VM work on my laptop when it locked up system fully, here is the kernel trace below (it repeats after the second dump) Since we're soon 'close' to 4.2 final, maybe someone can check if something regressed? Never saw this in eariler -rcX builds. Thanks, Shawn. [69399.505355] kvm: zapping shadow pages for mmio generation wraparound [69405.611747] kvm [24415]: vcpu0 unhandled rdmsr: 0x641 [69411.477997] Bridge: port 2(vnet0) entered forwarding state [70844.574880] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [swapper/3:0] [70844.575264] Modules linked in: vhost_net vhost macvtap macvlan tun ebtable_filter ebtables ip6table_filter ip6_tables bridge vfat fat intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_core videobuf2_memops arc4 iwlmvm v4l2_common mac80211 videodev snd_usb_audio snd_usbmidi_lib snd_rawmidi media iwlwifi dell_laptop cfg80211 snd_hda_codec_realtek dell_wmi snd_soc_rt5640 iTCO_wdt iTCO_vendor_support joydev lpc_ich dcdbas sparse_keymap ppdev dell_smm_hwmon mei_me snd_hda_codec_generic snd_soc_rl6231 snd_hda_codec_hdmi mei ie31200_edac edac_core dw_dmac snd_soc_core parport_pc parport snd_compress snd_pcm_dmaengine shpchp video ac97_bus dw_dmac_core i2c_i801 i2c_designware_platform i2c_designware_core [70844.579376] snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_soc_sst_acpi dell_rbtn rfkill wmi dell_smo8800 nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc 8021q garp stp llc mrp amdkfd amd_iommu_v2 radeon i2c_algo_bit drm_kms_helper ttm e1000e drm serio_raw sdhci_pci ptp sdhci_acpi pps_core sdhci mmc_core i2c_hid [70844.581351] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.2.0-0.rc7.git0.1.fc23.x86_64 #1 [70844.581804] Hardware name: Dell Inc. Precision M6800/05NG6V, BIOS A14 05/24/2015 [70844.582198] task: 880809f6c4c0 ti: 88080990 task.ti: 88080990 [70844.582555] RIP: 0010:[811036cb] [811036cb] try_to_del_timer_sync+0xb/0x90 [70844.583042] RSP: 0018:88082dcc3da0 EFLAGS: 0286 [70844.583296] RAX: RBX: 0296 RCX: [70844.583637] RDX: 0001 RSI: 0296 RDI: 8800bc0612e0 [70844.584037] RBP: 88082dcc3da8 R08: 0101 R09: 0003 [70844.584373] R10: 0002 R11: 0004 R12: 88082dcc3d18 [70844.584771] R13: 8177818b R14: 88082dcc3da8 R15: 8800bc0612e0 [70844.585139] FS: () GS:88082dcc() knlGS: [70844.585524] CS: 0010 DS: ES: CR0: 80050033 [70844.585833] CR2: 140a84048000 CR3: 01c0b000 CR4: 001426e0 [70844.586200] Stack: [70844.586301] 8807650fe800 88082dcc3dc8 8110379c 88082dcc3dc8 [70844.586687] 8800bc061248 88082dcc3df8 816ac35c 000167c0 [70844.587187] 8800bc061248 8807650fe800 8807ec9c5000 88082dcc3e38 [70844.587631] Call Trace: [70844.587784] IRQ [70844.587884] [8110379c] del_timer_sync+0x4c/0x60 [70844.588188] [816ac35c] inet_csk_reqsk_queue_drop+0x6c/0x1d0 [70844.588499] [816ac599] reqsk_timer_handler+0xd9/0x2a0 [70844.588817] [816ac4c0] ? inet_csk_reqsk_queue_drop+0x1d0/0x1d0 [70844.589158] [811034f9] call_timer_fn+0x39/0xf0 [70844.589432] [816ac4c0] ? inet_csk_reqsk_queue_drop+0x1d0/0x1d0 [70844.589774] [81103b2f] run_timer_softirq+0x20f/0x2c0 [70844.590105] [810a280b] __do_softirq+0xfb/0x290 [70844.590365] [810a2bb9] irq_exit+0x119/0x120 [70844.590618] [81779ff6] smp_apic_timer_interrupt+0x46/0x60 [70844.590929] [8177818b] apic_timer_interrupt+0x6b/0x70 [70844.591222] EOI [70844.591322] [8110653f] ? hrtimer_start_range_ns+0x1bf/0x3b0 [70844.591656] [816136e0] ? cpuidle_enter_state+0x130/0x270 [70844.591961] [816136bb] ? cpuidle_enter_state+0x10b/0x270 [70844.592265] [81613857] cpuidle_enter+0x17/0x20 [70844.592527] [810df402] call_cpuidle+0x32/0x60 [70844.592787] [81613833] ? cpuidle_select+0x13/0x20 [70844.593060] [810df698] cpu_startup_entry+0x268/0x320 [70844.593347] [8104cbd6] start_secondary+0x186/0x1c0 [70844.593623] Code: 00 00 44 89 e0 75 0b 48 83 c4 18 5b 41 5c 41 5d 5d c3 e8 79 ab f9 ff 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 53 48 8d 75 e0 48 89 fb 48 83 c7 28 48 83 ec 10 65 48 8b 04 25 [70872.581083] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [swapper/3:0] [70872.581462] Modules linked in: vhost_net vhost macvtap macvlan tun ebtable_filter ebtables ip6table_filter ip6_tables bridge vfat fat intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul
[3.18][ACPI] and [drm] Dell Precision M6800 - bad ACPI sleep states / bogus BAR alignment
Hello Kernel devs, In my continuing use of this new laptop (Day 2), I'm encountering some other issues. I am using Dell's latest A11 BIOS that came out last month. I have switchable graphics currently turned on in the BIOS. Might be some bugs with this being active and other variables. Will test any patches you might have for me. Thanks, Shawn Below is full kernel message [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.18.0+ (r...@segfault.sh0n.net) (gcc version 4.9.2 20141101 (Red Hat 4.9.2-1) (GCC) ) #1 SMP Sat Dec 13 21:38:30 EST 2014 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.18.0+ root=UUID=4ca78ce8-7850-4f5e-9fab-3d675e5864af ro rhgb slub_debug=- cgroup_disable=memory console=tty0 console=ttyS0,115200n8 radeon.dpm=1 intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 zswap.zpool=zsmalloc zswap.enabled=1 zram=1 [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0004efff] usable [0.00] BIOS-e820: [mem 0x0004f000-0x0004] reserved [0.00] BIOS-e820: [mem 0x0005-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0xbffc5fff] usable [0.00] BIOS-e820: [mem 0xbffc6000-0xbffccfff] ACPI NVS [0.00] BIOS-e820: [mem 0xbffcd000-0xc0991fff] usable [0.00] BIOS-e820: [mem 0xc0992000-0xc0e67fff] reserved [0.00] BIOS-e820: [mem 0xc0e68000-0xc7db2fff] usable [0.00] BIOS-e820: [mem 0xc7db3000-0xc7ff] reserved [0.00] BIOS-e820: [mem 0xc800-0xc8758fff] usable [0.00] BIOS-e820: [mem 0xc8759000-0xc87f] reserved [0.00] BIOS-e820: [mem 0xc880-0xc8f92fff] usable [0.00] BIOS-e820: [mem 0xc8f93000-0xc8ff] ACPI data [0.00] BIOS-e820: [mem 0xc900-0xca6d3fff] usable [0.00] BIOS-e820: [mem 0xca6d4000-0xca7f] ACPI NVS [0.00] BIOS-e820: [mem 0xca80-0xcbcddfff] usable [0.00] BIOS-e820: [mem 0xcbcde000-0xcbff] reserved [0.00] BIOS-e820: [mem 0xcd00-0xcf1f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00082edf] usable [0.00] NX (Execute Disable) protection: active [0.00] e820: update [mem 0xc558e018-0xc55aa657] usable ==> usable [0.00] e820: update [mem 0xc557d018-0xc558d057] usable ==> usable [0.00] e820: update [mem 0xc556d018-0xc557cc57] usable ==> usable [0.00] e820: update [mem 0xc554f018-0xc556cc57] usable ==> usable [0.00] extended physical RAM map: [0.00] reserve setup_data: [mem 0x-0x0004efff] usable [0.00] reserve setup_data: [mem 0x0004f000-0x0004] reserved [0.00] reserve setup_data: [mem 0x0005-0x0009efff] usable [0.00] reserve setup_data: [mem 0x0009f000-0x0009] reserved [0.00] reserve setup_data: [mem 0x0010-0xbffc5fff] usable [0.00] reserve setup_data: [mem 0xbffc6000-0xbffccfff] ACPI NVS [0.00] reserve setup_data: [mem 0xbffcd000-0xc0991fff] usable [0.00] reserve setup_data: [mem 0xc0992000-0xc0e67fff] reserved [0.00] reserve setup_data: [mem 0xc0e68000-0xc554f017] usable [0.00] reserve setup_data: [mem 0xc554f018-0xc556cc57] usable [0.00] reserve setup_data: [mem 0xc556cc58-0xc556d017] usable [0.00] reserve setup_data: [mem 0xc556d018-0xc557cc57] usable [0.00] reserve setup_data: [mem 0xc557cc58-0xc557d017] usable [0.00] reserve setup_data: [mem 0xc557d018-0xc558d057] usable [0.00] reserve setup_data: [mem 0xc558d058-0xc558e017] usable [0.00] reserve setup_data: [mem 0xc558e018-0xc55aa657] usable [0.00] reserve setup_data: [mem 0xc55aa658-0xc7db2fff] usable [0.00] reserve setup_data: [mem
[alsa][intel-hda] Dell M6800 - Realtek ALC3226 - Headphone Microphone not detected/working
Hello ALSA/Kernel devs, I have a Dell Precision M6800 with latest BIOS here is output from the HDA driver [ 20.783635] snd_hda_intel :00:03.0: enabling device ( -> 0002) [ 20.783804] snd_hda_intel :00:1b.0: irq 34 for MSI/MSI-X [ 20.783911] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client [ 20.783914] snd_hda_intel :01:00.1: VGA controller is disabled [ 20.783914] snd_hda_intel :01:00.1: Delaying initialization [ 20.785722] snd_hda_intel :00:03.0: irq 35 for MSI/MSI-X [ 20.798841] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card1/input16 [ 20.798881] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card1/input17 [ 20.798914] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card1/input18 [ 20.800208] sound hdaudioC2D0: autoconfig: line_outs=1 (0x16/0x0/0x0/0x0/0x0) type:line [ 20.800209] sound hdaudioC2D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 20.800210] sound hdaudioC2D0:hp_outs=1 (0x15/0x0/0x0/0x0/0x0) [ 20.800210] sound hdaudioC2D0:mono: mono_out=0x0 [ 20.800211] sound hdaudioC2D0:inputs: [ 20.800212] sound hdaudioC2D0: Front Mic=0x18 [ 20.800212] sound hdaudioC2D0: Dock Mic=0x19 [ 20.800213] sound hdaudioC2D0: Headset Mic=0x1a [ 20.800213] sound hdaudioC2D0: Internal Mic=0x12 [ 20.805683] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card2/input19 [ 20.805724] input: HDA Intel PCH Dock Mic as /devices/pci:00/:00:1b.0/sound/card2/input20 [ 20.805756] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card2/input21 [ 20.805784] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card2/input22 [ 78.191344] snd_hda_intel :01:00.1: Start delayed initialization [ 78.195309] snd_hda_intel :01:00.1: irq 36 for MSI/MSI-X [ 78.298530] snd_hda_intel :01:00.1: CORB reset timeout#2, CORBRP = 65535 [ 78.300524] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.303813] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.306054] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.308797] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.311717] snd_hda_intel :01:00.1: no codecs initialized [ 78.314116] snd_hda_intel :01:00.1: initialization error [ 264.477548] snd_hda_intel :00:1b.0: Unstable LPIB (352800 >= 176400); disabling LPIB delay counting [ 381.091720] snd_hda_intel :01:00.1: enabling device ( -> 0002) [ 381.095346] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client [ 381.097754] snd_hda_intel :01:00.1: VGA controller is disabled [ 381.100294] snd_hda_intel :01:00.1: Delaying initialization When I have the analog headphones plugged in the headphone speakers work but microphone does not, interestingly in another OS, it also didn't show it functioning. If someone has had similar issues in Linux, let me know, I will also test patches. Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[alsa][intel-hda] Dell M6800 - Realtek ALC3226 - Headphone Microphone not detected/working
Hello ALSA/Kernel devs, I have a Dell Precision M6800 with latest BIOS here is output from the HDA driver [ 20.783635] snd_hda_intel :00:03.0: enabling device ( - 0002) [ 20.783804] snd_hda_intel :00:1b.0: irq 34 for MSI/MSI-X [ 20.783911] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client [ 20.783914] snd_hda_intel :01:00.1: VGA controller is disabled [ 20.783914] snd_hda_intel :01:00.1: Delaying initialization [ 20.785722] snd_hda_intel :00:03.0: irq 35 for MSI/MSI-X [ 20.798841] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card1/input16 [ 20.798881] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card1/input17 [ 20.798914] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card1/input18 [ 20.800208] sound hdaudioC2D0: autoconfig: line_outs=1 (0x16/0x0/0x0/0x0/0x0) type:line [ 20.800209] sound hdaudioC2D0:speaker_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 20.800210] sound hdaudioC2D0:hp_outs=1 (0x15/0x0/0x0/0x0/0x0) [ 20.800210] sound hdaudioC2D0:mono: mono_out=0x0 [ 20.800211] sound hdaudioC2D0:inputs: [ 20.800212] sound hdaudioC2D0: Front Mic=0x18 [ 20.800212] sound hdaudioC2D0: Dock Mic=0x19 [ 20.800213] sound hdaudioC2D0: Headset Mic=0x1a [ 20.800213] sound hdaudioC2D0: Internal Mic=0x12 [ 20.805683] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card2/input19 [ 20.805724] input: HDA Intel PCH Dock Mic as /devices/pci:00/:00:1b.0/sound/card2/input20 [ 20.805756] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card2/input21 [ 20.805784] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card2/input22 [ 78.191344] snd_hda_intel :01:00.1: Start delayed initialization [ 78.195309] snd_hda_intel :01:00.1: irq 36 for MSI/MSI-X [ 78.298530] snd_hda_intel :01:00.1: CORB reset timeout#2, CORBRP = 65535 [ 78.300524] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.303813] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.306054] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.308797] snd_hda_intel :01:00.1: no AFG or MFG node found [ 78.311717] snd_hda_intel :01:00.1: no codecs initialized [ 78.314116] snd_hda_intel :01:00.1: initialization error [ 264.477548] snd_hda_intel :00:1b.0: Unstable LPIB (352800 = 176400); disabling LPIB delay counting [ 381.091720] snd_hda_intel :01:00.1: enabling device ( - 0002) [ 381.095346] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client [ 381.097754] snd_hda_intel :01:00.1: VGA controller is disabled [ 381.100294] snd_hda_intel :01:00.1: Delaying initialization When I have the analog headphones plugged in the headphone speakers work but microphone does not, interestingly in another OS, it also didn't show it functioning. If someone has had similar issues in Linux, let me know, I will also test patches. Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[3.18][ACPI] and [drm] Dell Precision M6800 - bad ACPI sleep states / bogus BAR alignment
Hello Kernel devs, In my continuing use of this new laptop (Day 2), I'm encountering some other issues. I am using Dell's latest A11 BIOS that came out last month. I have switchable graphics currently turned on in the BIOS. Might be some bugs with this being active and other variables. Will test any patches you might have for me. Thanks, Shawn Below is full kernel message [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.18.0+ (r...@segfault.sh0n.net) (gcc version 4.9.2 20141101 (Red Hat 4.9.2-1) (GCC) ) #1 SMP Sat Dec 13 21:38:30 EST 2014 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.18.0+ root=UUID=4ca78ce8-7850-4f5e-9fab-3d675e5864af ro rhgb slub_debug=- cgroup_disable=memory console=tty0 console=ttyS0,115200n8 radeon.dpm=1 intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 zswap.zpool=zsmalloc zswap.enabled=1 zram=1 [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0004efff] usable [0.00] BIOS-e820: [mem 0x0004f000-0x0004] reserved [0.00] BIOS-e820: [mem 0x0005-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0xbffc5fff] usable [0.00] BIOS-e820: [mem 0xbffc6000-0xbffccfff] ACPI NVS [0.00] BIOS-e820: [mem 0xbffcd000-0xc0991fff] usable [0.00] BIOS-e820: [mem 0xc0992000-0xc0e67fff] reserved [0.00] BIOS-e820: [mem 0xc0e68000-0xc7db2fff] usable [0.00] BIOS-e820: [mem 0xc7db3000-0xc7ff] reserved [0.00] BIOS-e820: [mem 0xc800-0xc8758fff] usable [0.00] BIOS-e820: [mem 0xc8759000-0xc87f] reserved [0.00] BIOS-e820: [mem 0xc880-0xc8f92fff] usable [0.00] BIOS-e820: [mem 0xc8f93000-0xc8ff] ACPI data [0.00] BIOS-e820: [mem 0xc900-0xca6d3fff] usable [0.00] BIOS-e820: [mem 0xca6d4000-0xca7f] ACPI NVS [0.00] BIOS-e820: [mem 0xca80-0xcbcddfff] usable [0.00] BIOS-e820: [mem 0xcbcde000-0xcbff] reserved [0.00] BIOS-e820: [mem 0xcd00-0xcf1f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00082edf] usable [0.00] NX (Execute Disable) protection: active [0.00] e820: update [mem 0xc558e018-0xc55aa657] usable == usable [0.00] e820: update [mem 0xc557d018-0xc558d057] usable == usable [0.00] e820: update [mem 0xc556d018-0xc557cc57] usable == usable [0.00] e820: update [mem 0xc554f018-0xc556cc57] usable == usable [0.00] extended physical RAM map: [0.00] reserve setup_data: [mem 0x-0x0004efff] usable [0.00] reserve setup_data: [mem 0x0004f000-0x0004] reserved [0.00] reserve setup_data: [mem 0x0005-0x0009efff] usable [0.00] reserve setup_data: [mem 0x0009f000-0x0009] reserved [0.00] reserve setup_data: [mem 0x0010-0xbffc5fff] usable [0.00] reserve setup_data: [mem 0xbffc6000-0xbffccfff] ACPI NVS [0.00] reserve setup_data: [mem 0xbffcd000-0xc0991fff] usable [0.00] reserve setup_data: [mem 0xc0992000-0xc0e67fff] reserved [0.00] reserve setup_data: [mem 0xc0e68000-0xc554f017] usable [0.00] reserve setup_data: [mem 0xc554f018-0xc556cc57] usable [0.00] reserve setup_data: [mem 0xc556cc58-0xc556d017] usable [0.00] reserve setup_data: [mem 0xc556d018-0xc557cc57] usable [0.00] reserve setup_data: [mem 0xc557cc58-0xc557d017] usable [0.00] reserve setup_data: [mem 0xc557d018-0xc558d057] usable [0.00] reserve setup_data: [mem 0xc558d058-0xc558e017] usable [0.00] reserve setup_data: [mem 0xc558e018-0xc55aa657] usable [0.00] reserve setup_data: [mem 0xc55aa658-0xc7db2fff] usable [0.00] reserve setup_data: [mem
[3.18-rc1] Regression in userspace - Google Chrome
Hello kernel folks, In -rc1, I had problems running Google Chrome with sandbox enabled by default. Chrome would start once, sometimes not run at all, setuid binary would be stuck in 'D' state. Using my current kernel (kernel-3.17.1-303.fc21.x86_64) no such problems exist. I know 3.18 is early in it's -rc cycle but this is a heads up if nobody else noticed. Now that -rc2 is out and soon Fedora will have a -rc2 kernel for me to play with, I'll will see if this was just noise in the merge window. Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[3.18-rc1] Regression in userspace - Google Chrome
Hello kernel folks, In -rc1, I had problems running Google Chrome with sandbox enabled by default. Chrome would start once, sometimes not run at all, setuid binary would be stuck in 'D' state. Using my current kernel (kernel-3.17.1-303.fc21.x86_64) no such problems exist. I know 3.18 is early in it's -rc cycle but this is a heads up if nobody else noticed. Now that -rc2 is out and soon Fedora will have a -rc2 kernel for me to play with, I'll will see if this was just noise in the merge window. Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bulk] Re: [3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU
On September 11, 2014 04:26:21 PM Bjorn Helgaas wrote: > [+cc linux-pci] > > On Sat, Aug 2, 2014 at 10:02 AM, Shawn Starr wrote: > > Hello devs, > > > > There are two issues I am encountering with the PCIe Hotplug driver on my > > Lenovo Laptop (W500). I note this goes back further than 3.15. > > > > It is noted here: > > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id= > > f244d8b623dae7a7bc695b0336f67729b95a9736 > > https://bugzilla.kernel.org/show_bug.cgi?id=79701 > > > > And my open bug here: > > https://bugzilla.kernel.org/show_bug.cgi?id=77261 > > > > 1) If I enable the device to use both the integrated and discrete GPU, > > pciehp will decide to force unload radeon because it puts itself into a > > power saving state, fails back to the Intel integrated GPU in this case > > unless I tell radeon.ko to runpm=0 (no power management, then pciehp wont > > touch it). > > > > 2) If the Radeon GPU resets and you use pci_reset=1 for kernel module > > option, pciehp decides to force unload radeon even though the GPU is > > trying to setup after failing. > > > > Kernel I am using right now: 3.16.0-0.rc7.git3.1.fc21.x86_64 (about to > > boot into snapshot kernel-core-3.16.0-0.rc7.git4.1.fc21.x86_64) > Hi Shawn, > > Thanks for the report and sorry that it got dropped. But I see you're > cc'd on https://bugzilla.kernel.org/show_bug.cgi?id=79701, so you've > probably seen the work there. If you can try out the patches I just > posted, that would be great. > > Bjorn Hi Bjorn, For #1) This is fixed in linux-next (tracking 3.18.0-0.rc0.git1.2.fc22.1.x86_64 nondebug kernel for Fedora). PCIe HotPlug no longer unloads radeon. For this bugzilla report we can close it. #2) This still has weird results however, radeon.hard_reset=1 is experimental and while it attempts to reset GPU, PCIe HotPlug seems to interact in this. This can be tested by adding to grub command line radeon.hard_reset=1. When X has started up, trigger a reset by cat /sys/kernel/debug/dri/#/radeon_gpu_reset. It will output 0, cat it again will show 1. Attempt to drag a window. The this will trigger a GPU reset, but fail to recover, its unknown if PCIe HotPlug is preventing a proper reset or not but there is pciehp calls in the stack trace. Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Bulk] Re: [3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU
On September 11, 2014 04:26:21 PM Bjorn Helgaas wrote: [+cc linux-pci] On Sat, Aug 2, 2014 at 10:02 AM, Shawn Starr shawn.st...@rogers.com wrote: Hello devs, There are two issues I am encountering with the PCIe Hotplug driver on my Lenovo Laptop (W500). I note this goes back further than 3.15. It is noted here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id= f244d8b623dae7a7bc695b0336f67729b95a9736 https://bugzilla.kernel.org/show_bug.cgi?id=79701 And my open bug here: https://bugzilla.kernel.org/show_bug.cgi?id=77261 1) If I enable the device to use both the integrated and discrete GPU, pciehp will decide to force unload radeon because it puts itself into a power saving state, fails back to the Intel integrated GPU in this case unless I tell radeon.ko to runpm=0 (no power management, then pciehp wont touch it). 2) If the Radeon GPU resets and you use pci_reset=1 for kernel module option, pciehp decides to force unload radeon even though the GPU is trying to setup after failing. Kernel I am using right now: 3.16.0-0.rc7.git3.1.fc21.x86_64 (about to boot into snapshot kernel-core-3.16.0-0.rc7.git4.1.fc21.x86_64) Hi Shawn, Thanks for the report and sorry that it got dropped. But I see you're cc'd on https://bugzilla.kernel.org/show_bug.cgi?id=79701, so you've probably seen the work there. If you can try out the patches I just posted, that would be great. Bjorn Hi Bjorn, For #1) This is fixed in linux-next (tracking 3.18.0-0.rc0.git1.2.fc22.1.x86_64 nondebug kernel for Fedora). PCIe HotPlug no longer unloads radeon. For this bugzilla report we can close it. #2) This still has weird results however, radeon.hard_reset=1 is experimental and while it attempts to reset GPU, PCIe HotPlug seems to interact in this. This can be tested by adding to grub command line radeon.hard_reset=1. When X has started up, trigger a reset by cat /sys/kernel/debug/dri/#/radeon_gpu_reset. It will output 0, cat it again will show 1. Attempt to drag a window. The this will trigger a GPU reset, but fail to recover, its unknown if PCIe HotPlug is preventing a proper reset or not but there is pciehp calls in the stack trace. Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU
On September 11, 2014 04:26:21 PM Bjorn Helgaas wrote: > [+cc linux-pci] > > On Sat, Aug 2, 2014 at 10:02 AM, Shawn Starr wrote: > > Hello devs, > > > > There are two issues I am encountering with the PCIe Hotplug driver on my > > Lenovo Laptop (W500). I note this goes back further than 3.15. > > > > It is noted here: > > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id= > > f244d8b623dae7a7bc695b0336f67729b95a9736 > > https://bugzilla.kernel.org/show_bug.cgi?id=79701 > > > > And my open bug here: > > https://bugzilla.kernel.org/show_bug.cgi?id=77261 > > > > 1) If I enable the device to use both the integrated and discrete GPU, > > pciehp will decide to force unload radeon because it puts itself into a > > power saving state, fails back to the Intel integrated GPU in this case > > unless I tell radeon.ko to runpm=0 (no power management, then pciehp wont > > touch it). > > > > 2) If the Radeon GPU resets and you use pci_reset=1 for kernel module > > option, pciehp decides to force unload radeon even though the GPU is > > trying to setup after failing. > > > > Kernel I am using right now: 3.16.0-0.rc7.git3.1.fc21.x86_64 (about to > > boot into snapshot kernel-core-3.16.0-0.rc7.git4.1.fc21.x86_64) > Hi Shawn, > > Thanks for the report and sorry that it got dropped. But I see you're > cc'd on https://bugzilla.kernel.org/show_bug.cgi?id=79701, so you've > probably seen the work there. If you can try out the patches I just > posted, that would be great. > > Bjorn Hi Bjorn, I will be testing this in 3.17-rcX if it hits 3.17, otherwise manually patch it in. Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU
On September 11, 2014 04:26:21 PM Bjorn Helgaas wrote: [+cc linux-pci] On Sat, Aug 2, 2014 at 10:02 AM, Shawn Starr shawn.st...@rogers.com wrote: Hello devs, There are two issues I am encountering with the PCIe Hotplug driver on my Lenovo Laptop (W500). I note this goes back further than 3.15. It is noted here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id= f244d8b623dae7a7bc695b0336f67729b95a9736 https://bugzilla.kernel.org/show_bug.cgi?id=79701 And my open bug here: https://bugzilla.kernel.org/show_bug.cgi?id=77261 1) If I enable the device to use both the integrated and discrete GPU, pciehp will decide to force unload radeon because it puts itself into a power saving state, fails back to the Intel integrated GPU in this case unless I tell radeon.ko to runpm=0 (no power management, then pciehp wont touch it). 2) If the Radeon GPU resets and you use pci_reset=1 for kernel module option, pciehp decides to force unload radeon even though the GPU is trying to setup after failing. Kernel I am using right now: 3.16.0-0.rc7.git3.1.fc21.x86_64 (about to boot into snapshot kernel-core-3.16.0-0.rc7.git4.1.fc21.x86_64) Hi Shawn, Thanks for the report and sorry that it got dropped. But I see you're cc'd on https://bugzilla.kernel.org/show_bug.cgi?id=79701, so you've probably seen the work there. If you can try out the patches I just posted, that would be great. Bjorn Hi Bjorn, I will be testing this in 3.17-rcX if it hits 3.17, otherwise manually patch it in. Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU
Hello devs, There are two issues I am encountering with the PCIe Hotplug driver on my Lenovo Laptop (W500). I note this goes back further than 3.15. It is noted here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f244d8b623dae7a7bc695b0336f67729b95a9736 https://bugzilla.kernel.org/show_bug.cgi?id=79701 And my open bug here: https://bugzilla.kernel.org/show_bug.cgi?id=77261 1) If I enable the device to use both the integrated and discrete GPU, pciehp will decide to force unload radeon because it puts itself into a power saving state, fails back to the Intel integrated GPU in this case unless I tell radeon.ko to runpm=0 (no power management, then pciehp wont touch it). 2) If the Radeon GPU resets and you use pci_reset=1 for kernel module option, pciehp decides to force unload radeon even though the GPU is trying to setup after failing. Kernel I am using right now: 3.16.0-0.rc7.git3.1.fc21.x86_64 (about to boot into snapshot kernel-core-3.16.0-0.rc7.git4.1.fc21.x86_64) Here is kernel dump (from time GPU resets, and cascading failure with PCIe Hotplug fighting): Aug 2 11:31:24 segfault kernel: [ 515.525087] radeon :01:00.0: ring 0 stalled for more than 10158msec Aug 2 11:31:24 segfault kernel: [ 515.525280] radeon :01:00.0: GPU lockup (waiting for 0x000154b6 last fence id 0x000154b0 on ring 0) Aug 2 11:31:24 segfault kernel: [ 515.743497] radeon :01:00.0: Saved 185 dwords of commands on ring 0. Aug 2 11:31:24 segfault kernel: [ 515.743724] radeon :01:00.0: GPU softreset: 0x0008 Aug 2 11:31:24 segfault kernel: [ 515.743897] radeon :01:00.0: R_008010_GRBM_STATUS = 0xA0003030 Aug 2 11:31:24 segfault kernel: [ 515.744152] radeon :01:00.0: R_008014_GRBM_STATUS2 = 0x0003 Aug 2 11:31:24 segfault kernel: [ 515.744396] radeon :01:00.0: R_000E50_SRBM_STATUS = 0x20C0 Aug 2 11:31:24 segfault kernel: [ 515.744623] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 2 11:31:24 segfault kernel: [ 515.744820] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x Aug 2 11:31:24 segfault kernel: [ 515.745030] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x00028186 Aug 2 11:31:24 segfault kernel: [ 515.745251] radeon :01:00.0: R_008680_CP_STAT = 0x80028645 Aug 2 11:31:24 segfault kernel: [ 515.745456] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Aug 2 11:31:25 segfault kernel: [ 515.802395] radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x4001 Aug 2 11:31:25 segfault kernel: [ 515.802633] radeon :01:00.0: SRBM_SOFT_RESET=0x0100 Aug 2 11:31:25 segfault kernel: [ 515.804908] radeon :01:00.0: R_008010_GRBM_STATUS = 0xA0003030 Aug 2 11:31:25 segfault kernel: [ 515.805147] radeon :01:00.0: R_008014_GRBM_STATUS2 = 0x0003 Aug 2 11:31:25 segfault kernel: [ 515.805355] radeon :01:00.0: R_000E50_SRBM_STATUS = 0x200080C0 Aug 2 11:31:25 segfault kernel: [ 515.805560] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 2 11:31:25 segfault kernel: [ 515.805756] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x Aug 2 11:31:25 segfault kernel: [ 515.805957] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x Aug 2 11:31:25 segfault kernel: [ 515.806184] radeon :01:00.0: R_008680_CP_STAT = 0x8010 Aug 2 11:31:25 segfault kernel: [ 515.806384] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Aug 2 11:31:25 segfault kernel: [ 515.806583] radeon :01:00.0: GPU pci config reset Aug 2 11:31:25 segfault kernel: [ 515.887334] pciehp :00:01.0:pcie04: Card not present on Slot(1-1) Aug 2 11:31:25 segfault kernel: [ 515.889380] Console: switching to colour VGA+ 80x25 Aug 2 11:31:25 segfault kernel: [ 515.893123] pciehp :00:01.0:pcie04: Card present on Slot(1-1) Aug 2 11:31:25 segfault kernel: [ 515.902365] drm_kms_helper: drm: unregistered panic notifier Aug 2 11:31:25 segfault kernel: [ 516.046783] radeon :01:00.0: GPU reset succeeded, trying to resume Aug 2 11:31:25 segfault kernel: [ 516.175830] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed Aug 2 11:31:26 segfault kernel: [ 516.842282] radeon :01:00.0: Wait for MC idle timedout ! Aug 2 11:31:26 segfault kernel: [ 517.008275] radeon :01:00.0: Wait for MC idle timedout ! Aug 2 11:31:26 segfault kernel: [ 517.010332] [drm] PCIE GART of 512M enabled (table at 0x0004). Aug 2 11:31:26 segfault kernel: [ 517.010627] divide error: [#1] SMP Aug 2 11:31:26 segfault kernel: [ 517.010793] Modules linked in: vhost_net vhost macvtap macvlan tun bridge stp llc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media snd_usb_audio snd_usbmidi_lib mmc_block snd_rawmidi coretemp kvm_intel kvm iTCO_wdt sdhci_pci arc4 iwldvm mac80211 sdhci
[3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU
Hello devs, There are two issues I am encountering with the PCIe Hotplug driver on my Lenovo Laptop (W500). I note this goes back further than 3.15. It is noted here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f244d8b623dae7a7bc695b0336f67729b95a9736 https://bugzilla.kernel.org/show_bug.cgi?id=79701 And my open bug here: https://bugzilla.kernel.org/show_bug.cgi?id=77261 1) If I enable the device to use both the integrated and discrete GPU, pciehp will decide to force unload radeon because it puts itself into a power saving state, fails back to the Intel integrated GPU in this case unless I tell radeon.ko to runpm=0 (no power management, then pciehp wont touch it). 2) If the Radeon GPU resets and you use pci_reset=1 for kernel module option, pciehp decides to force unload radeon even though the GPU is trying to setup after failing. Kernel I am using right now: 3.16.0-0.rc7.git3.1.fc21.x86_64 (about to boot into snapshot kernel-core-3.16.0-0.rc7.git4.1.fc21.x86_64) Here is kernel dump (from time GPU resets, and cascading failure with PCIe Hotplug fighting): Aug 2 11:31:24 segfault kernel: [ 515.525087] radeon :01:00.0: ring 0 stalled for more than 10158msec Aug 2 11:31:24 segfault kernel: [ 515.525280] radeon :01:00.0: GPU lockup (waiting for 0x000154b6 last fence id 0x000154b0 on ring 0) Aug 2 11:31:24 segfault kernel: [ 515.743497] radeon :01:00.0: Saved 185 dwords of commands on ring 0. Aug 2 11:31:24 segfault kernel: [ 515.743724] radeon :01:00.0: GPU softreset: 0x0008 Aug 2 11:31:24 segfault kernel: [ 515.743897] radeon :01:00.0: R_008010_GRBM_STATUS = 0xA0003030 Aug 2 11:31:24 segfault kernel: [ 515.744152] radeon :01:00.0: R_008014_GRBM_STATUS2 = 0x0003 Aug 2 11:31:24 segfault kernel: [ 515.744396] radeon :01:00.0: R_000E50_SRBM_STATUS = 0x20C0 Aug 2 11:31:24 segfault kernel: [ 515.744623] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 2 11:31:24 segfault kernel: [ 515.744820] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x Aug 2 11:31:24 segfault kernel: [ 515.745030] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x00028186 Aug 2 11:31:24 segfault kernel: [ 515.745251] radeon :01:00.0: R_008680_CP_STAT = 0x80028645 Aug 2 11:31:24 segfault kernel: [ 515.745456] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Aug 2 11:31:25 segfault kernel: [ 515.802395] radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x4001 Aug 2 11:31:25 segfault kernel: [ 515.802633] radeon :01:00.0: SRBM_SOFT_RESET=0x0100 Aug 2 11:31:25 segfault kernel: [ 515.804908] radeon :01:00.0: R_008010_GRBM_STATUS = 0xA0003030 Aug 2 11:31:25 segfault kernel: [ 515.805147] radeon :01:00.0: R_008014_GRBM_STATUS2 = 0x0003 Aug 2 11:31:25 segfault kernel: [ 515.805355] radeon :01:00.0: R_000E50_SRBM_STATUS = 0x200080C0 Aug 2 11:31:25 segfault kernel: [ 515.805560] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 2 11:31:25 segfault kernel: [ 515.805756] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x Aug 2 11:31:25 segfault kernel: [ 515.805957] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x Aug 2 11:31:25 segfault kernel: [ 515.806184] radeon :01:00.0: R_008680_CP_STAT = 0x8010 Aug 2 11:31:25 segfault kernel: [ 515.806384] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Aug 2 11:31:25 segfault kernel: [ 515.806583] radeon :01:00.0: GPU pci config reset Aug 2 11:31:25 segfault kernel: [ 515.887334] pciehp :00:01.0:pcie04: Card not present on Slot(1-1) Aug 2 11:31:25 segfault kernel: [ 515.889380] Console: switching to colour VGA+ 80x25 Aug 2 11:31:25 segfault kernel: [ 515.893123] pciehp :00:01.0:pcie04: Card present on Slot(1-1) Aug 2 11:31:25 segfault kernel: [ 515.902365] drm_kms_helper: drm: unregistered panic notifier Aug 2 11:31:25 segfault kernel: [ 516.046783] radeon :01:00.0: GPU reset succeeded, trying to resume Aug 2 11:31:25 segfault kernel: [ 516.175830] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed Aug 2 11:31:26 segfault kernel: [ 516.842282] radeon :01:00.0: Wait for MC idle timedout ! Aug 2 11:31:26 segfault kernel: [ 517.008275] radeon :01:00.0: Wait for MC idle timedout ! Aug 2 11:31:26 segfault kernel: [ 517.010332] [drm] PCIE GART of 512M enabled (table at 0x0004). Aug 2 11:31:26 segfault kernel: [ 517.010627] divide error: [#1] SMP Aug 2 11:31:26 segfault kernel: [ 517.010793] Modules linked in: vhost_net vhost macvtap macvlan tun bridge stp llc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media snd_usb_audio snd_usbmidi_lib mmc_block snd_rawmidi coretemp kvm_intel kvm iTCO_wdt sdhci_pci arc4 iwldvm mac80211 sdhci
[3.13-rc/78] random SIGBUS errors + 3.14-rc0 - KVM/QEMU - CPU hang issues
Hello folks, After a couple days of uptime, with Google Chrome + Flash. This has happened twice, will crash with a SIGBUS and subsequent launches of Google Chrome will SIGBUS. In addition other programs may or may not SIGBUS but the whole system becomes unstable until a full reboot. I only see kaudit logs from kernel but nothing looks unusual and there are no other noticed messages indicating anything wrong. Anyone else noticed SIGBUS issues w/ 3.13-rcX (-rc8 or final?) For 3.14-rc0 in Fedora (rawhide non-debug repo), spinning up a VM w/ KVM causes kernel to report CPU hang by 'qemu' process, it's early in the 3.14 cycle so I expect things to be wild a bit but wanted to report that if anyone else hasn't noticed yet. Thanks, Shawn Starr Sr. Linux Administrator StatPro | Toronto Tel. +1 (416) 619-3972 | Fax. +1 (416) 598-9530 Twitter. @statprogroup www.statpro.com Looking for a bit of holiday cheer? Watch StatPro's latest video StatPro Canada Inc. registered Office: 33 Yonge Street, Suite 1101, Toronto ON, M5E 1G4. StatPro Canada Inc. is a member of StatPro Group plc. This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Any views or opinions presented in this email are solely those of the author and might not represent those of StatPro. Warning: Although StatPro has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[3.13-rc/78] random SIGBUS errors + 3.14-rc0 - KVM/QEMU - CPU hang issues
Hello folks, After a couple days of uptime, with Google Chrome + Flash. This has happened twice, will crash with a SIGBUS and subsequent launches of Google Chrome will SIGBUS. In addition other programs may or may not SIGBUS but the whole system becomes unstable until a full reboot. I only see kaudit logs from kernel but nothing looks unusual and there are no other noticed messages indicating anything wrong. Anyone else noticed SIGBUS issues w/ 3.13-rcX (-rc8 or final?) For 3.14-rc0 in Fedora (rawhide non-debug repo), spinning up a VM w/ KVM causes kernel to report CPU hang by 'qemu' process, it's early in the 3.14 cycle so I expect things to be wild a bit but wanted to report that if anyone else hasn't noticed yet. Thanks, Shawn Starr Sr. Linux Administrator StatPro | Toronto Tel. +1 (416) 619-3972 | Fax. +1 (416) 598-9530 Twitter. @statprogroup www.statpro.com Looking for a bit of holiday cheer? Watch StatPro's latest video StatPro Canada Inc. registered Office: 33 Yonge Street, Suite 1101, Toronto ON, M5E 1G4. StatPro Canada Inc. is a member of StatPro Group plc. This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Any views or opinions presented in this email are solely those of the author and might not represent those of StatPro. Warning: Although StatPro has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: No longer able to build kernel into RPM on Fedora
On Sunday, October 13, 2013 10:35:09 AM Chris Jones wrote: > As a temporary work around, can you revert to the older version of RPM? > Hi Chris, I was missing rpm-build, I have a patch submitted to force use of rpm-build. AFAIK, nobody uses legacy rpm anymore since falling back to just rpm will fail since it does not have --target or -ta options. Thanks, Shawn > > Regards > > On 10/13/2013 05:03 AM, Shawn Starr wrote: > > Hello folks, > > > > My usual approach to testing git snapshots of Linus's tree (with custom > > patches applied on top) is to make rpm and install this into my system for > > a clean add/remove of test kernels. > > > > However, the developers of rpm removed the --target and -ta options, so I > > can't take tarball and build into RPM anymore. > > > > Since I last built custom RPM builds of Linus's tree was likely Fedora 18, > > it seems the option target got removed by 19. > > > > Any ideas, fixes? > > > > Thanks, > > Shawn > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to majord...@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
resend [PATCH][BUILD] Force check for rpm-build where package is not installed
On Saturday, October 12, 2013 03:39:05 PM Shawn Starr wrote: > On Saturday, October 12, 2013 03:03:32 PM Shawn Starr wrote: > > Hello folks, > > > > My usual approach to testing git snapshots of Linus's tree (with custom > > patches applied on top) is to make rpm and install this into my system for > > a clean add/remove of test kernels. > > > > However, the developers of rpm removed the --target and -ta options, so I > > can't take tarball and build into RPM anymore. > > > > Since I last built custom RPM builds of Linus's tree was likely Fedora 18, > > it seems the option target got removed by 19. > > > > Any ideas, fixes? > > > > Thanks, > > Shawn > > Sorry for noise, I was missing rpm-build. That said, here's a patch to > force check for rpm-build as any modern RPM distribution should be be using > a newer rpm release. > > Thanks, > Shawn > Signed-off-by: Shawn Starr --- scripts/package/Makefile | 8 +++- 1 files changed, 7 insertions(+), 1 deletion(-) diff --git a/scripts/package/Makefile b/scripts/package/Makefile index a4f31c9..aac24de 100644 --- a/scripts/package/Makefile +++ b/scripts/package/Makefile @@ -23,7 +23,7 @@ # Do we have rpmbuild, otherwise fall back to the older rpm RPM := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \ - else echo rpm; fi) + else echo none; fi) # Remove hyphens since they have special meaning in RPM filenames KERNELPATH := kernel-$(subst -,_,$(KERNELRELEASE)) @@ -51,6 +51,12 @@ rpm-pkg rpm: FORCE rm -f $(objtree)/.scmversion $(CONFIG_SHELL) $(srctree)/scripts/mkversion > $(objtree)/.tmp_version mv -f $(objtree)/.tmp_version $(objtree)/.version + @if test "$(RPM)" != "rpmbuild"; then \ + echo "To build the kernel you must install the rpm-build package from your distribution" ;\ + echo "aborting package creation." ; \ + false; \ + fi + $(RPM) $(RPMOPTS) --target $(UTS_MACHINE) -ta $(KERNELPATH).tar.gz rm $(KERNELPATH).tar.gz kernel.spec -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH][BUILD] Force check for rpm-build where package is not installed
On Saturday, October 12, 2013 03:03:32 PM Shawn Starr wrote: > Hello folks, > > My usual approach to testing git snapshots of Linus's tree (with custom > patches applied on top) is to make rpm and install this into my system for a > clean add/remove of test kernels. > > However, the developers of rpm removed the --target and -ta options, so I > can't take tarball and build into RPM anymore. > > Since I last built custom RPM builds of Linus's tree was likely Fedora 18, > it seems the option target got removed by 19. > > Any ideas, fixes? > > Thanks, > Shawn Sorry for noise, I was missing rpm-build. That said, here's a patch to force check for rpm-build as any modern RPM distribution should be be using a newer rpm release. Thanks, Shawn Signed-off-by: Shawn Starr --- scripts/package/Makefile | 8 +++- 1 files changed, 7 insertions(+), 1 deletion(-) diff --git a/scripts/package/Makefile b/scripts/package/Makefile index a4f31c9..aac24de 100644 --- a/scripts/package/Makefile +++ b/scripts/package/Makefile @@ -23,7 +23,7 @@ # Do we have rpmbuild, otherwise fall back to the older rpm RPM := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \ - else echo rpm; fi) + else echo none; fi) # Remove hyphens since they have special meaning in RPM filenames KERNELPATH := kernel-$(subst -,_,$(KERNELRELEASE)) @@ -51,6 +51,12 @@ rpm-pkg rpm: FORCE rm -f $(objtree)/.scmversion $(CONFIG_SHELL) $(srctree)/scripts/mkversion > $(objtree)/.tmp_version mv -f $(objtree)/.tmp_version $(objtree)/.version + @if test "$(RPM)" != "rpmbuild"; then \ + echo "To build the kernel you must install the rpm-build package from your distri + echo "aborting package creation." ; \ + false; \ + fi + $(RPM) $(RPMOPTS) --target $(UTS_MACHINE) -ta $(KERNELPATH).tar.gz rm $(KERNELPATH).tar.gz kernel.spec -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
No longer able to build kernel into RPM on Fedora
Hello folks, My usual approach to testing git snapshots of Linus's tree (with custom patches applied on top) is to make rpm and install this into my system for a clean add/remove of test kernels. However, the developers of rpm removed the --target and -ta options, so I can't take tarball and build into RPM anymore. Since I last built custom RPM builds of Linus's tree was likely Fedora 18, it seems the option target got removed by 19. Any ideas, fixes? Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
No longer able to build kernel into RPM on Fedora
Hello folks, My usual approach to testing git snapshots of Linus's tree (with custom patches applied on top) is to make rpm and install this into my system for a clean add/remove of test kernels. However, the developers of rpm removed the --target and -ta options, so I can't take tarball and build into RPM anymore. Since I last built custom RPM builds of Linus's tree was likely Fedora 18, it seems the option target got removed by 19. Any ideas, fixes? Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH][BUILD] Force check for rpm-build where package is not installed
On Saturday, October 12, 2013 03:03:32 PM Shawn Starr wrote: Hello folks, My usual approach to testing git snapshots of Linus's tree (with custom patches applied on top) is to make rpm and install this into my system for a clean add/remove of test kernels. However, the developers of rpm removed the --target and -ta options, so I can't take tarball and build into RPM anymore. Since I last built custom RPM builds of Linus's tree was likely Fedora 18, it seems the option target got removed by 19. Any ideas, fixes? Thanks, Shawn Sorry for noise, I was missing rpm-build. That said, here's a patch to force check for rpm-build as any modern RPM distribution should be be using a newer rpm release. Thanks, Shawn Signed-off-by: Shawn Starr shawn.st...@rogers.com --- scripts/package/Makefile | 8 +++- 1 files changed, 7 insertions(+), 1 deletion(-) diff --git a/scripts/package/Makefile b/scripts/package/Makefile index a4f31c9..aac24de 100644 --- a/scripts/package/Makefile +++ b/scripts/package/Makefile @@ -23,7 +23,7 @@ # Do we have rpmbuild, otherwise fall back to the older rpm RPM := $(shell if [ -x /usr/bin/rpmbuild ]; then echo rpmbuild; \ - else echo rpm; fi) + else echo none; fi) # Remove hyphens since they have special meaning in RPM filenames KERNELPATH := kernel-$(subst -,_,$(KERNELRELEASE)) @@ -51,6 +51,12 @@ rpm-pkg rpm: FORCE rm -f $(objtree)/.scmversion $(CONFIG_SHELL) $(srctree)/scripts/mkversion $(objtree)/.tmp_version mv -f $(objtree)/.tmp_version $(objtree)/.version + @if test $(RPM) != rpmbuild; then \ + echo To build the kernel you must install the rpm-build package from your distri + echo aborting package creation. ; \ + false; \ + fi + $(RPM) $(RPMOPTS) --target $(UTS_MACHINE) -ta $(KERNELPATH).tar.gz rm $(KERNELPATH).tar.gz kernel.spec -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
resend [PATCH][BUILD] Force check for rpm-build where package is not installed
On Saturday, October 12, 2013 03:39:05 PM Shawn Starr wrote: On Saturday, October 12, 2013 03:03:32 PM Shawn Starr wrote: Hello folks, My usual approach to testing git snapshots of Linus's tree (with custom patches applied on top) is to make rpm and install this into my system for a clean add/remove of test kernels. However, the developers of rpm removed the --target and -ta options, so I can't take tarball and build into RPM anymore. Since I last built custom RPM builds of Linus's tree was likely Fedora 18, it seems the option target got removed by 19. Any ideas, fixes? Thanks, Shawn Sorry for noise, I was missing rpm-build. That said, here's a patch to force check for rpm-build as any modern RPM distribution should be be using a newer rpm release. Thanks, Shawn Signed-off-by: Shawn Starr shawn.st...@rogers.com --- scripts/package/Makefile | 8 +++- 1 files changed, 7 insertions(+), 1 deletion(-) diff --git a/scripts/package/Makefile b/scripts/package/Makefile index a4f31c9..aac24de 100644 --- a/scripts/package/Makefile +++ b/scripts/package/Makefile @@ -23,7 +23,7 @@ # Do we have rpmbuild, otherwise fall back to the older rpm RPM := $(shell if [ -x /usr/bin/rpmbuild ]; then echo rpmbuild; \ - else echo rpm; fi) + else echo none; fi) # Remove hyphens since they have special meaning in RPM filenames KERNELPATH := kernel-$(subst -,_,$(KERNELRELEASE)) @@ -51,6 +51,12 @@ rpm-pkg rpm: FORCE rm -f $(objtree)/.scmversion $(CONFIG_SHELL) $(srctree)/scripts/mkversion $(objtree)/.tmp_version mv -f $(objtree)/.tmp_version $(objtree)/.version + @if test $(RPM) != rpmbuild; then \ + echo To build the kernel you must install the rpm-build package from your distribution ;\ + echo aborting package creation. ; \ + false; \ + fi + $(RPM) $(RPMOPTS) --target $(UTS_MACHINE) -ta $(KERNELPATH).tar.gz rm $(KERNELPATH).tar.gz kernel.spec -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: No longer able to build kernel into RPM on Fedora
On Sunday, October 13, 2013 10:35:09 AM Chris Jones wrote: As a temporary work around, can you revert to the older version of RPM? Hi Chris, I was missing rpm-build, I have a patch submitted to force use of rpm-build. AFAIK, nobody uses legacy rpm anymore since falling back to just rpm will fail since it does not have --target or -ta options. Thanks, Shawn Regards On 10/13/2013 05:03 AM, Shawn Starr wrote: Hello folks, My usual approach to testing git snapshots of Linus's tree (with custom patches applied on top) is to make rpm and install this into my system for a clean add/remove of test kernels. However, the developers of rpm removed the --target and -ta options, so I can't take tarball and build into RPM anymore. Since I last built custom RPM builds of Linus's tree was likely Fedora 18, it seems the option target got removed by 19. Any ideas, fixes? Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo
On Tuesday, March 19, 2013 04:12:18 PM Daniel Vetter wrote:
> On Tue, Mar 19, 2013 at 10:03 AM, Chris Wilson
wrote:
> >> > How about just using:
> >> > if (!HAS_GMBUS_IRQ(dev_priv->dev)) gmbus4_irq_en = 0;
> >> >
> >> > and the existing wait loop?
> >>
> >> I explicitly wanted to avoid touching GMBUS4 register, as the real cause
> >> of the failure is not clear.
> >>
> >> But, as Yinghai Lu points out, the problem is most likely caused by
> >> interrupt disabling not working properly (see his very good point
> >> regarding DisINTx+ and INTx+ discrepancy), so zeroing the register out
> >> should work and it indeed does in my case, hence the (tested) patch
> >> below.
> >>
> >> I think it's a 3.9-rc material, and I am all open to debug this further
> >> for 3.10 so that the race is closed and gmbus irqs can be used on Gen4
> >> platform properly.
> >
> > Agreed. Using the IRQ for GMBUS is just a performance feature that can
> > be deferred until after we determine the root cause - and hope that the
> > failure is somehow peculiar to GMBUS.
>
> Ok, I've merged this patch. But some further investigation points at a
> much more severe dragon hiding here: The MSI interrupt for the intel
> gfx is commonly in the 40+ range, but the interrupt vector with the
> spurious interrupts is 16. Which is the irq of the intel gfx when MSI
> is disabled!
>
> So it looks like gmbus on the intel gfx is capable of generating
> non-MSI interrupts in parallel to the MSI interrupts (since apparently
> gmbus still works, so we get the interrupts we expect). I have no idea
> how that could happen. Hence adding a bunch of people with more clue
> than me.
>
Hello folks,
I am using Linus git master and built an rpm for 3.9.0-rc4 which has Jiri's
patch. I confirm this patch returns the GMA 4500 to working behavior as in
3.8.
Thanks everyone.
Shawn
> For reference below the updated commit message.
>
> Cheers, Daniel
>
> Author: Jiri Kosina
> Date: Tue Mar 19 09:56:57 2013 +0100
>
> drm/i915: stop using GMBUS IRQs on Gen4 chips
>
> Commit 28c70f162 ("drm/i915: use the gmbus irq for waits") switched to
> using GMBUS irqs instead of GPIO bit-banging for chipset generations 4
> and above.
>
> It turns out though that on many systems this leads to spurious
> interrupts being generated, long after the register write to disable the
> IRQs has been issued.
>
> Typically this results in the spurious interrupt source getting
> disabled:
>
> [9.636345] irq 16: nobody cared (try booting with the "irqpoll"
> option) [9.637915] Pid: 4157, comm: ifup Tainted: GF
> 3.9.0-rc2-00341-g0863702 #422
> [9.639484] Call Trace:
> [9.640731][] __report_bad_irq+0x1d/0xc7
> [9.640731] [] note_interrupt+0x15b/0x1e8
> [9.640731] [] handle_irq_event_percpu+0x1bf/0x214
> [9.640731] [] handle_irq_event+0x3c/0x5c [
> 9.640731] [] handle_fasteoi_irq+0x7a/0xb0 [9.640731]
> [] handle_irq+0x1a/0x24
> [9.640731] [] do_IRQ+0x48/0xaf
> [9.640731] [] common_interrupt+0x6a/0x6a
> [9.640731][] ?
> system_call_fastpath+0x16/0x1b [9.640731] handlers:
> [9.640731] [] usb_hcd_irq [usbcore]
> [9.640731] [] yenta_interrupt [yenta_socket]
> [9.640731] Disabling IRQ #16
>
> The really curious thing is now that irq 16 is _not_ the interrupt for
> the i915 driver when using MSI, but it _is_ the interrupt when not
> using MSI. So by all indications it seems like gmbus is able to
> generate a legacy (shared) interrupt in MSI mode on some
> configurations. I've tried to reproduce this and the differentiating
> thing seems to be that on unaffected systems no other device uses irq
> 16 (which seems to be the non-MSI intel gfx interrupt on all gm45).
>
> I have no idea how that even can happen.
>
> To avoid tempting this elephant into a rage, just disable gmbus
> interrupt support on gen 4.
>
> v2: Improve the commit message with exact details of what's going on.
> Also add a comment in the code to warn against this particular
> elephant in the room.
>
> Signed-off-by: Jiri Kosina (v1)
> Acked-by: Chris Wilson (v1)
> References: https://lkml.org/lkml/2013/3/8/325
> Signed-off-by: Daniel Vetter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo
On Tuesday, March 19, 2013 04:12:18 PM Daniel Vetter wrote: On Tue, Mar 19, 2013 at 10:03 AM, Chris Wilson ch...@chris-wilson.co.uk wrote: How about just using: if (!HAS_GMBUS_IRQ(dev_priv-dev)) gmbus4_irq_en = 0; and the existing wait loop? I explicitly wanted to avoid touching GMBUS4 register, as the real cause of the failure is not clear. But, as Yinghai Lu points out, the problem is most likely caused by interrupt disabling not working properly (see his very good point regarding DisINTx+ and INTx+ discrepancy), so zeroing the register out should work and it indeed does in my case, hence the (tested) patch below. I think it's a 3.9-rc material, and I am all open to debug this further for 3.10 so that the race is closed and gmbus irqs can be used on Gen4 platform properly. Agreed. Using the IRQ for GMBUS is just a performance feature that can be deferred until after we determine the root cause - and hope that the failure is somehow peculiar to GMBUS. Ok, I've merged this patch. But some further investigation points at a much more severe dragon hiding here: The MSI interrupt for the intel gfx is commonly in the 40+ range, but the interrupt vector with the spurious interrupts is 16. Which is the irq of the intel gfx when MSI is disabled! So it looks like gmbus on the intel gfx is capable of generating non-MSI interrupts in parallel to the MSI interrupts (since apparently gmbus still works, so we get the interrupts we expect). I have no idea how that could happen. Hence adding a bunch of people with more clue than me. Hello folks, I am using Linus git master and built an rpm for 3.9.0-rc4 which has Jiri's patch. I confirm this patch returns the GMA 4500 to working behavior as in 3.8. Thanks everyone. Shawn For reference below the updated commit message. Cheers, Daniel Author: Jiri Kosina jkos...@suse.cz Date: Tue Mar 19 09:56:57 2013 +0100 drm/i915: stop using GMBUS IRQs on Gen4 chips Commit 28c70f162 (drm/i915: use the gmbus irq for waits) switched to using GMBUS irqs instead of GPIO bit-banging for chipset generations 4 and above. It turns out though that on many systems this leads to spurious interrupts being generated, long after the register write to disable the IRQs has been issued. Typically this results in the spurious interrupt source getting disabled: [9.636345] irq 16: nobody cared (try booting with the irqpoll option) [9.637915] Pid: 4157, comm: ifup Tainted: GF 3.9.0-rc2-00341-g0863702 #422 [9.639484] Call Trace: [9.640731] IRQ [8109b40d] __report_bad_irq+0x1d/0xc7 [9.640731] [8109b7db] note_interrupt+0x15b/0x1e8 [9.640731] [810999f7] handle_irq_event_percpu+0x1bf/0x214 [9.640731] [81099a88] handle_irq_event+0x3c/0x5c [ 9.640731] [8109c139] handle_fasteoi_irq+0x7a/0xb0 [9.640731] [8100400e] handle_irq+0x1a/0x24 [9.640731] [81003d17] do_IRQ+0x48/0xaf [9.640731] [8142f1ea] common_interrupt+0x6a/0x6a [9.640731] EOI [8142f952] ? system_call_fastpath+0x16/0x1b [9.640731] handlers: [9.640731] [a000d771] usb_hcd_irq [usbcore] [9.640731] [a0306189] yenta_interrupt [yenta_socket] [9.640731] Disabling IRQ #16 The really curious thing is now that irq 16 is _not_ the interrupt for the i915 driver when using MSI, but it _is_ the interrupt when not using MSI. So by all indications it seems like gmbus is able to generate a legacy (shared) interrupt in MSI mode on some configurations. I've tried to reproduce this and the differentiating thing seems to be that on unaffected systems no other device uses irq 16 (which seems to be the non-MSI intel gfx interrupt on all gm45). I have no idea how that even can happen. To avoid tempting this elephant into a rage, just disable gmbus interrupt support on gen 4. v2: Improve the commit message with exact details of what's going on. Also add a comment in the code to warn against this particular elephant in the room. Signed-off-by: Jiri Kosina jkos...@suse.cz (v1) Acked-by: Chris Wilson ch...@chris-wilson.co.uk (v1) References: https://lkml.org/lkml/2013/3/8/325 Signed-off-by: Daniel Vetter daniel.vet...@ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Intel][RNG] PCI IDs commented out for 82801I (ICH9 Mobile and non-mobile)?
Hello folks,
I was looking at why I can't load the Intel RNG driver (or why it doesn't load
automatically) and
it just so happens I have both the mobile and non-mobile ICH9 chipset. Looking
at the driver I noticed:
/* BAM, CAM, DBM, FBM, GxM
{ PCI_DEVICE(0x8086, 0x2448) }, */
/* BA, CA, DB, Ex, 6300, Fx, 631x/632x, Gx
{ PCI_DEVICE(0x8086, 0x244e) }, */
IDs from both machines:
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev 93)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev
92)
I saw a thread from 2006 explaining the 50% chance there's no RNG (but these
days all modern chipsets should have an RNG) and I know
this chipset I have does have an RNG so I'd like to use the HW random generator
vs software.
Do we need to revisit this? Even if I try to force it to load it still fails:
# modprobe intel_rng no_fwh_detect=-1 or =1
modprobe: ERROR: could not insert 'intel_rng': No such device
Thanks,
Shawn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Intel][RNG] PCI IDs commented out for 82801I (ICH9 Mobile and non-mobile)?
Hello folks,
I was looking at why I can't load the Intel RNG driver (or why it doesn't load
automatically) and
it just so happens I have both the mobile and non-mobile ICH9 chipset. Looking
at the driver I noticed:
/* BAM, CAM, DBM, FBM, GxM
{ PCI_DEVICE(0x8086, 0x2448) }, */
/* BA, CA, DB, Ex, 6300, Fx, 631x/632x, Gx
{ PCI_DEVICE(0x8086, 0x244e) }, */
IDs from both machines:
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev 93)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev
92)
I saw a thread from 2006 explaining the 50% chance there's no RNG (but these
days all modern chipsets should have an RNG) and I know
this chipset I have does have an RNG so I'd like to use the HW random generator
vs software.
Do we need to revisit this? Even if I try to force it to load it still fails:
# modprobe intel_rng no_fwh_detect=-1 or =1
modprobe: ERROR: could not insert 'intel_rng': No such device
Thanks,
Shawn
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [Linux 3.8/3.9-rc1][alsa][hda] Problem with automute on HDA CX20561 (Hermosa) - Persistent even after power off
On Friday, March 08, 2013 03:06:12 PM Shawn Starr wrote: > Hello folks, > > All of a sudden, it worked fine in Linux kernel 3.8, I believe after booting > Linux kernel 3.9 (which has ALSA HDA changes). I can no longer hear audio > from speakers on laptop. If I plug in headphones audio works. > > [ 18.434846] hda_codec: CX20561 (Hermosa): BIOS auto-probing. > [ 18.434932] ALSA sound/pci/hda/hda_auto_parser.c:306 autoconfig: > line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker [ 18.434934] ALSA > sound/pci/hda/hda_auto_parser.c:310 speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ > 18.434936] ALSA sound/pci/hda/hda_auto_parser.c:314 hp_outs=2 > (0x19/0x16/0x0/0x0/0x0) [ 18.434937] ALSA > sound/pci/hda/hda_auto_parser.c:315 mono: mono_out=0x0 [ 18.434939] ALSA > sound/pci/hda/hda_auto_parser.c:318 dig-out=0x1c/0x0 [ 18.434940] ALSA > sound/pci/hda/hda_auto_parser.c:319 inputs: > [ 18.434942] ALSA sound/pci/hda/hda_auto_parser.c:323 Mic=0x18 > [ 18.434944] ALSA sound/pci/hda/hda_auto_parser.c:323 Internal Mic=0x1d > [ 18.434945] ALSA sound/pci/hda/hda_auto_parser.c:323 Dock Mic=0x17 > [ 18.435835] ALSA sound/pci/hda/patch_conexant.c:4587 hda_codec: Enable > sync_write for stable communication [ 18.443473] input: HDA Intel Dock Mic > as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 18.443563] input: > HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [ > 18.443614] input: HDA Intel Headphone as > /devices/pci:00/:00:1b.0/sound/card0/input11 [ 18.443674] input: > HDA Intel Dock Headphone as > /devices/pci:00/:00:1b.0/sound/card0/input12 > > I did a hard power off, even booted into a Windows OS to see the windows > kernel driver might reset the autio ports and it didn't fix this even, did > the kernel driver reprogram the hardware badly somewhere? How can I fix > this? > > Thanks, > Shawn Sorry for the noise, this is fixed, I found the cause. Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Linux 3.8/3.9-rc1][alsa][hda] Problem with automute on HDA CX20561 (Hermosa) - Persistent even after power off
Hello folks, All of a sudden, it worked fine in Linux kernel 3.8, I believe after booting Linux kernel 3.9 (which has ALSA HDA changes). I can no longer hear audio from speakers on laptop. If I plug in headphones audio works. [ 18.434846] hda_codec: CX20561 (Hermosa): BIOS auto-probing. [ 18.434932] ALSA sound/pci/hda/hda_auto_parser.c:306 autoconfig: line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker [ 18.434934] ALSA sound/pci/hda/hda_auto_parser.c:310 speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 18.434936] ALSA sound/pci/hda/hda_auto_parser.c:314 hp_outs=2 (0x19/0x16/0x0/0x0/0x0) [ 18.434937] ALSA sound/pci/hda/hda_auto_parser.c:315 mono: mono_out=0x0 [ 18.434939] ALSA sound/pci/hda/hda_auto_parser.c:318 dig-out=0x1c/0x0 [ 18.434940] ALSA sound/pci/hda/hda_auto_parser.c:319 inputs: [ 18.434942] ALSA sound/pci/hda/hda_auto_parser.c:323 Mic=0x18 [ 18.434944] ALSA sound/pci/hda/hda_auto_parser.c:323 Internal Mic=0x1d [ 18.434945] ALSA sound/pci/hda/hda_auto_parser.c:323 Dock Mic=0x17 [ 18.435835] ALSA sound/pci/hda/patch_conexant.c:4587 hda_codec: Enable sync_write for stable communication [ 18.443473] input: HDA Intel Dock Mic as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 18.443563] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [ 18.443614] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [ 18.443674] input: HDA Intel Dock Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 I did a hard power off, even booted into a Windows OS to see the windows kernel driver might reset the autio ports and it didn't fix this even, did the kernel driver reprogram the hardware badly somewhere? How can I fix this? Thanks, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Linux 3.8/3.9-rc1][alsa][hda] Problem with automute on HDA CX20561 (Hermosa) - Persistent even after power off
Hello folks, All of a sudden, it worked fine in Linux kernel 3.8, I believe after booting Linux kernel 3.9 (which has ALSA HDA changes). I can no longer hear audio from speakers on laptop. If I plug in headphones audio works. [ 18.434846] hda_codec: CX20561 (Hermosa): BIOS auto-probing. [ 18.434932] ALSA sound/pci/hda/hda_auto_parser.c:306 autoconfig: line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker [ 18.434934] ALSA sound/pci/hda/hda_auto_parser.c:310 speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 18.434936] ALSA sound/pci/hda/hda_auto_parser.c:314 hp_outs=2 (0x19/0x16/0x0/0x0/0x0) [ 18.434937] ALSA sound/pci/hda/hda_auto_parser.c:315 mono: mono_out=0x0 [ 18.434939] ALSA sound/pci/hda/hda_auto_parser.c:318 dig-out=0x1c/0x0 [ 18.434940] ALSA sound/pci/hda/hda_auto_parser.c:319 inputs: [ 18.434942] ALSA sound/pci/hda/hda_auto_parser.c:323 Mic=0x18 [ 18.434944] ALSA sound/pci/hda/hda_auto_parser.c:323 Internal Mic=0x1d [ 18.434945] ALSA sound/pci/hda/hda_auto_parser.c:323 Dock Mic=0x17 [ 18.435835] ALSA sound/pci/hda/patch_conexant.c:4587 hda_codec: Enable sync_write for stable communication [ 18.443473] input: HDA Intel Dock Mic as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 18.443563] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [ 18.443614] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [ 18.443674] input: HDA Intel Dock Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 I did a hard power off, even booted into a Windows OS to see the windows kernel driver might reset the autio ports and it didn't fix this even, did the kernel driver reprogram the hardware badly somewhere? How can I fix this? Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Linux 3.8/3.9-rc1][alsa][hda] Problem with automute on HDA CX20561 (Hermosa) - Persistent even after power off
On Friday, March 08, 2013 03:06:12 PM Shawn Starr wrote: Hello folks, All of a sudden, it worked fine in Linux kernel 3.8, I believe after booting Linux kernel 3.9 (which has ALSA HDA changes). I can no longer hear audio from speakers on laptop. If I plug in headphones audio works. [ 18.434846] hda_codec: CX20561 (Hermosa): BIOS auto-probing. [ 18.434932] ALSA sound/pci/hda/hda_auto_parser.c:306 autoconfig: line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker [ 18.434934] ALSA sound/pci/hda/hda_auto_parser.c:310 speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 18.434936] ALSA sound/pci/hda/hda_auto_parser.c:314 hp_outs=2 (0x19/0x16/0x0/0x0/0x0) [ 18.434937] ALSA sound/pci/hda/hda_auto_parser.c:315 mono: mono_out=0x0 [ 18.434939] ALSA sound/pci/hda/hda_auto_parser.c:318 dig-out=0x1c/0x0 [ 18.434940] ALSA sound/pci/hda/hda_auto_parser.c:319 inputs: [ 18.434942] ALSA sound/pci/hda/hda_auto_parser.c:323 Mic=0x18 [ 18.434944] ALSA sound/pci/hda/hda_auto_parser.c:323 Internal Mic=0x1d [ 18.434945] ALSA sound/pci/hda/hda_auto_parser.c:323 Dock Mic=0x17 [ 18.435835] ALSA sound/pci/hda/patch_conexant.c:4587 hda_codec: Enable sync_write for stable communication [ 18.443473] input: HDA Intel Dock Mic as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 18.443563] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [ 18.443614] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [ 18.443674] input: HDA Intel Dock Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 I did a hard power off, even booted into a Windows OS to see the windows kernel driver might reset the autio ports and it didn't fix this even, did the kernel driver reprogram the hardware badly somewhere? How can I fix this? Thanks, Shawn Sorry for the noise, this is fixed, I found the cause. Thanks, Shawn -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[3.8.0-0.rc3.git1.2] Processes hanging after unmounting mm0 device (not confirmed related)
Hello kernel folks, I am seeing problems with snapshot 3.8.0-0.rc3.git1.2 [fc19]. Processes hanging after it appears unmounting my mmc0 (SD) card, I will attempt to reproduce but, I am unclear if the two are related at this moment [ 9127.631555] mmc0: new high speed SDHC card at address 1234 [ 9127.665816] mmcblk0: mmc0:1234 SA08G 7.42 GiB [ 9127.667810] mmcblk0: p1 [ 9273.215847] mmc0: card 1234 removed [ 9273.219007] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.276972] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.336307] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.394115] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.453340] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.165082] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.226002] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.293369] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.360836] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. Live stack trace: [10336.859532] SysRq : Show Blocked State [10336.859538] taskPC stack pid father [10336.859546] khugepaged D 88023bc93d80 032 2 0x [10336.859551] 88022ff07c80 0046 88022fef1760 88022ff07fd8 [10336.859555] 88022ff07fd8 88022ff07fd8 880230149760 88022fef1760 [10336.859558] 81e8b500 88022fef1760 88022a5e9568 [10336.859562] Call Trace: [10336.859574] [] schedule+0x29/0x70 [10336.859578] [] rwsem_down_failed_common+0xb5/0x140 [10336.859581] [] rwsem_down_read_failed+0x15/0x17 [10336.859587] [] call_rwsem_down_read_failed+0x14/0x30 [10336.859591] [] ? down_read+0x24/0x2b [10336.859597] [] khugepaged+0x17d/0x15b0 [10336.859602] [] ? wake_up_bit+0x40/0x40 [10336.859606] [] ? maybe_pmd_mkwrite+0x20/0x20 [10336.859609] [] kthread+0xc0/0xd0 [10336.859614] [] ? ftrace_define_fields_xen_mc_entry+0x30/0xf0 [10336.859618] [] ? kthread_create_on_node+0x120/0x120 [10336.859622] [] ret_from_fork+0x7c/0xb0 [10336.859626] [] ? kthread_create_on_node+0x120/0x120 [10336.859678] qemu-kvmD 88023bc93d80 0 3697 1 0x0080 [10336.859682] 8801e0a77cb8 0086 880190751760 8801e0a77fd8 [10336.859686] 8801e0a77fd8 8801e0a77fd8 8801c3b2aec0 880190751760 [10336.859689] 8801e0a77cb8 880190751760 880212659c88 [10336.859692] Call Trace: [10336.859697] [] schedule+0x29/0x70 [10336.859700] [] rwsem_down_failed_common+0xb5/0x140 [10336.859704] [] rwsem_down_write_failed+0x13/0x20 [10336.859708] [] call_rwsem_down_write_failed+0x13/0x20 [10336.859712] [] ? down_write+0x32/0x40 [10336.859716] [] vma_adjust+0x10d/0x770 [10336.859720] [] vma_merge+0x267/0x320 [10336.859723] [] do_brk+0x1e2/0x370 [10336.859727] [] sys_brk+0x13e/0x150 [10336.859730] [] system_call_fastpath+0x16/0x1b [10336.859785] ps D 88023bc93d80 0 3709 3708 0x0080 [10336.859788] 88018a765c90 0086 8801c8161760 88018a765fd8 [10336.859791] 88018a765fd8 88018a765fd8 880230149760 8801c8161760 [10336.859795] 0001 8801c8161760 88022a5e9568 fffe [10336.859798] Call Trace: [10336.859802] [] schedule+0x29/0x70 [10336.859805] [] rwsem_down_failed_common+0xb5/0x140 [10336.859809] [] rwsem_down_read_failed+0x15/0x17 [10336.859813] [] call_rwsem_down_read_failed+0x14/0x30 [10336.859817] [] ? down_read+0x24/0x2b [10336.859820] [] __access_remote_vm+0x3f/0x1d0 [10336.859823] [] access_process_vm+0x5f/0x90 [10336.859828] [] proc_pid_cmdline+0x9a/0x130 [10336.859831] [] proc_info_read+0x9f/0xf0 [10336.859836] [] vfs_read+0xa9/0x180 [10336.859839] [] sys_read+0x52/0xa0 [10336.859843] [] ? __audit_syscall_exit+0x20c/0x2c0 [10336.859847] [] system_call_fastpath+0x16/0x1b There are more but they show same point in the stack per process. Active CPU backtrace: [10718.740248] SysRq : Show backtrace of all active CPUs [10718.740252] sending NMI to all CPUs: [10718.740258] NMI backtrace for cpu 0 [10718.740259] CPU 0 [10718.740262] Pid: 7864, comm: bash Not tainted 3.8.0-0.rc3.git1.2.fc19.x86_64 #1 LENOVO 4058CTO/4058CTO [10718.740264] RIP: 0010:[] [] __const_udelay+0x12/0x30 [10718.740271] RSP: 0018:88022a7dde08 EFLAGS: 0046 [10718.740272] RAX: 01062560 RBX: 2710 RCX: 0002 [10718.740274] RDX: 00268f12 RSI: 0080 RDI: 00418958 [10718.740275] RBP: 88022a7dde28 R08:
[3.8.0-0.rc3.git1.2] Processes hanging after unmounting mm0 device (not confirmed related)
Hello kernel folks, I am seeing problems with snapshot 3.8.0-0.rc3.git1.2 [fc19]. Processes hanging after it appears unmounting my mmc0 (SD) card, I will attempt to reproduce but, I am unclear if the two are related at this moment kernel conversation [ 9127.631555] mmc0: new high speed SDHC card at address 1234 [ 9127.665816] mmcblk0: mmc0:1234 SA08G 7.42 GiB [ 9127.667810] mmcblk0: p1 [ 9273.215847] mmc0: card 1234 removed [ 9273.219007] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.276972] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.336307] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.394115] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9273.453340] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.165082] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.226002] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.293369] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [ 9284.360836] sdhci-pci :15:00.2: Will use DMA mode even though HW doesn't fully claim to support it. Live stack trace: [10336.859532] SysRq : Show Blocked State [10336.859538] taskPC stack pid father [10336.859546] khugepaged D 88023bc93d80 032 2 0x [10336.859551] 88022ff07c80 0046 88022fef1760 88022ff07fd8 [10336.859555] 88022ff07fd8 88022ff07fd8 880230149760 88022fef1760 [10336.859558] 81e8b500 88022fef1760 88022a5e9568 [10336.859562] Call Trace: [10336.859574] [8164ba19] schedule+0x29/0x70 [10336.859578] [8164c7c5] rwsem_down_failed_common+0xb5/0x140 [10336.859581] [8164c885] rwsem_down_read_failed+0x15/0x17 [10336.859587] [81302594] call_rwsem_down_read_failed+0x14/0x30 [10336.859591] [8164acb4] ? down_read+0x24/0x2b [10336.859597] [8118bdcd] khugepaged+0x17d/0x15b0 [10336.859602] [81082670] ? wake_up_bit+0x40/0x40 [10336.859606] [8118bc50] ? maybe_pmd_mkwrite+0x20/0x20 [10336.859609] [81081d60] kthread+0xc0/0xd0 [10336.859614] [8101] ? ftrace_define_fields_xen_mc_entry+0x30/0xf0 [10336.859618] [81081ca0] ? kthread_create_on_node+0x120/0x120 [10336.859622] [816550ec] ret_from_fork+0x7c/0xb0 [10336.859626] [81081ca0] ? kthread_create_on_node+0x120/0x120 [10336.859678] qemu-kvmD 88023bc93d80 0 3697 1 0x0080 [10336.859682] 8801e0a77cb8 0086 880190751760 8801e0a77fd8 [10336.859686] 8801e0a77fd8 8801e0a77fd8 8801c3b2aec0 880190751760 [10336.859689] 8801e0a77cb8 880190751760 880212659c88 [10336.859692] Call Trace: [10336.859697] [8164ba19] schedule+0x29/0x70 [10336.859700] [8164c7c5] rwsem_down_failed_common+0xb5/0x140 [10336.859704] [8164c863] rwsem_down_write_failed+0x13/0x20 [10336.859708] [813025c3] call_rwsem_down_write_failed+0x13/0x20 [10336.859712] [8164ac82] ? down_write+0x32/0x40 [10336.859716] [81162d7d] vma_adjust+0x10d/0x770 [10336.859720] [81163867] vma_merge+0x267/0x320 [10336.859723] [811649a2] do_brk+0x1e2/0x370 [10336.859727] [81164cde] sys_brk+0x13e/0x150 [10336.859730] [81655199] system_call_fastpath+0x16/0x1b [10336.859785] ps D 88023bc93d80 0 3709 3708 0x0080 [10336.859788] 88018a765c90 0086 8801c8161760 88018a765fd8 [10336.859791] 88018a765fd8 88018a765fd8 880230149760 8801c8161760 [10336.859795] 0001 8801c8161760 88022a5e9568 fffe [10336.859798] Call Trace: [10336.859802] [8164ba19] schedule+0x29/0x70 [10336.859805] [8164c7c5] rwsem_down_failed_common+0xb5/0x140 [10336.859809] [8164c885] rwsem_down_read_failed+0x15/0x17 [10336.859813] [81302594] call_rwsem_down_read_failed+0x14/0x30 [10336.859817] [8164acb4] ? down_read+0x24/0x2b [10336.859820] [8115f8df] __access_remote_vm+0x3f/0x1d0 [10336.859823] [8116018f] access_process_vm+0x5f/0x90 [10336.859828] [8120320a] proc_pid_cmdline+0x9a/0x130 [10336.859831] [81203e7f] proc_info_read+0x9f/0xf0 [10336.859836] [8119d569] vfs_read+0xa9/0x180 [10336.859839] [8119d692] sys_read+0x52/0xa0 [10336.859843] [810dec8c] ? __audit_syscall_exit+0x20c/0x2c0 [10336.859847] [81655199] system_call_fastpath+0x16/0x1b There are more but they show same point in the stack per process. Active CPU backtrace:
Re: [3.5/6.x][e1000e] - Regression - Unable to receive packets if MTU == 1500
On Thursday, November 01, 2012 02:01:05 PM Shawn Starr wrote: > Hello network driver folks, To follow up, this is fixed now in 3.6.7-5.fc18.x86_64 [38936.525226] e1000e :00:19.0: eth0: changing MTU from 9000 to 1500 [38936.539510] e1000e :00:19.0: Interrupt Throttle Rate turned on [38939.352053] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx I don't remember which 3.6 -rc fixed it but I saw some adjustments in e1000e threshold changes in Linus's usual announce -rc emails. Thanks for fixing! Now onto Fedora 19 (3.7) kernel testing Shawn. > > I recently decided to reinstall my Lenovo W500 laptop and found I wasn't > able to get DHCP leases, I wasn't able to install over PXE (when getting > the IP a second time within the OS) > > Fedora is currently using kernel-3.6.2-2.fc18.x86_64 (Pre-beta) > > The only difference I noticed was in my old install of Fedora, I had added > MTU=9000 to the interface config while using a 3.5 kernel, not knowing 3.6.x > seems to break things. > > My Cisco DPC3825 Switch/Cable modem has an MTU setting but this is from > Cable provider <-> WAN interface only. I tried changing to 1500 but by > default it uses this anyway. > > I had noticed tx unit hang errors sometimes, but not when MTU is above 1500. > > PCI info: > > 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network > Connection (rev 03) > Subsystem: Lenovo Device 20ee > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- Latency: 0 > Interrupt: pin A routed to IRQ 46 > Region 0: Memory at fc00 (32-bit, non-prefetchable) [size=128K] > Region 1: Memory at fc025000 (32-bit, non-prefetchable) [size=4K] > Region 2: I/O ports at 1840 [size=32] > Capabilities: [c8] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Address: fee0100c Data: 41a2 > Capabilities: [e0] PCI Advanced Features > AFCap: TP+ FLR+ > AFCtrl: FLR- > AFStatus: TP- > Kernel driver in use: e1000e > > e1000e conversation log: > > [ 12.653816] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k > [ 12.653819] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. > [ 12.653855] e1000e :00:19.0: setting latency timer to 64 > [ 12.653938] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set > to dynamic conservative mode > [ 12.653980] e1000e :00:19.0: irq 46 for MSI/MSI-X > [ 12.844121] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) > 00:22:68:0c:96:e3 > [ 12.844124] e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network > Connection [ 12.844150] e1000e :00:19.0: eth0: MAC: 7, PHY: 8, PBA > No: 1008FF-0FF [ 17.459570] e1000e :00:19.0: eth0: changing MTU from > 1500 to 9000 [ 17.459577] e1000e :00:19.0: Interrupt Throttle Rate > turned off [ 17.948121] e1000e :00:19.0: irq 46 for MSI/MSI-X > [ 18.049164] e1000e :00:19.0: irq 46 for MSI/MSI-X > [ 20.442936] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow > Control: Rx/Tx > > When I set MTU = 1500 (2000 works), it will stop receiving packets, it also > disables Interrupt Throttling when MTU is set higher. > > After testing reasons why it wasn't get a DHCP lease, I decided to bump the > MTU to 9000 for Jumbo Frames and as soon as I did this, I was able to get a > lease and the network functioned resumes receiving packets. > > Can anyone else report regressions or might know whats going on? > > Thanks, > Shawn. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3.5/6.x][e1000e] - Regression - Unable to receive packets if MTU == 1500
On Thursday, November 01, 2012 02:01:05 PM Shawn Starr wrote: Hello network driver folks, To follow up, this is fixed now in 3.6.7-5.fc18.x86_64 [38936.525226] e1000e :00:19.0: eth0: changing MTU from 9000 to 1500 [38936.539510] e1000e :00:19.0: Interrupt Throttle Rate turned on [38939.352053] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx I don't remember which 3.6 -rc fixed it but I saw some adjustments in e1000e threshold changes in Linus's usual announce -rc emails. Thanks for fixing! Now onto Fedora 19 (3.7) kernel testing Shawn. I recently decided to reinstall my Lenovo W500 laptop and found I wasn't able to get DHCP leases, I wasn't able to install over PXE (when getting the IP a second time within the OS) Fedora is currently using kernel-3.6.2-2.fc18.x86_64 (Pre-beta) The only difference I noticed was in my old install of Fedora, I had added MTU=9000 to the interface config while using a 3.5 kernel, not knowing 3.6.x seems to break things. My Cisco DPC3825 Switch/Cable modem has an MTU setting but this is from Cable provider - WAN interface only. I tried changing to 1500 but by default it uses this anyway. I had noticed tx unit hang errors sometimes, but not when MTU is above 1500. PCI info: 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) Subsystem: Lenovo Device 20ee Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 46 Region 0: Memory at fc00 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at fc025000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 1840 [size=32] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0100c Data: 41a2 Capabilities: [e0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: e1000e e1000e conversation log: [ 12.653816] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k [ 12.653819] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. [ 12.653855] e1000e :00:19.0: setting latency timer to 64 [ 12.653938] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 12.653980] e1000e :00:19.0: irq 46 for MSI/MSI-X [ 12.844121] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:22:68:0c:96:e3 [ 12.844124] e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 12.844150] e1000e :00:19.0: eth0: MAC: 7, PHY: 8, PBA No: 1008FF-0FF [ 17.459570] e1000e :00:19.0: eth0: changing MTU from 1500 to 9000 [ 17.459577] e1000e :00:19.0: Interrupt Throttle Rate turned off [ 17.948121] e1000e :00:19.0: irq 46 for MSI/MSI-X [ 18.049164] e1000e :00:19.0: irq 46 for MSI/MSI-X [ 20.442936] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx When I set MTU = 1500 (2000 works), it will stop receiving packets, it also disables Interrupt Throttling when MTU is set higher. After testing reasons why it wasn't get a DHCP lease, I decided to bump the MTU to 9000 for Jumbo Frames and as soon as I did this, I was able to get a lease and the network functioned resumes receiving packets. Can anyone else report regressions or might know whats going on? Thanks, Shawn. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[usb_storage][mmc] - Genesys Logic / SilverStone 6-in-1 Card Reader/Writer - Can't mount storage
Hello kernel folks, I have an old 2.0 USB card reader, Linux detects the device but is not able to mount the storage device. I tried it in both a KVM Windows VM and in Linux to mount the storage but device hangs, if I take out card, it detects all 6 device storage capabilities, then it detects the mmc card if i re-insert the card but is unable to mount it. I am using a MMC adapter that can attach a micro-SD card inside it. This USB card reader/writer device comes with a 3.5" bay slot w/ a USB connector to motherboard and can detached for portable reading. Anyone seen this problem before? Does it need any quirks used? Thanks, Shawn. --- SNIP --- Kernel conversation: [523520.622075] usb 1-1: new high-speed USB device number 8 using ehci_hcd [523520.749731] usb 1-1: New USB device found, idVendor=05e3, idProduct=0760 [523520.749735] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4 [523520.749738] usb 1-1: Product: Flash Reader [523520.749739] usb 1-1: SerialNumber: 37 [523520.751674] scsi31 : usb-storage 1-1:1.0 [523521.753494] scsi 31:0:0:0: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523521.884032] usb 1-1: reset high-speed USB device number 8 using ehci_hcd [523522.020128] scsi 31:0:0:1: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523522.157055] usb 1-1: reset high-speed USB device number 8 using ehci_hcd [523522.292672] scsi 31:0:0:2: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523522.426047] usb 1-1: reset high-speed USB device number 8 using ehci_hcd [523522.561250] scsi 31:0:0:3: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523522.561828] sd 31:0:0:0: Attached scsi generic sg2 type 0 [523522.562020] sd 31:0:0:1: Attached scsi generic sg3 type 0 [523522.562158] sd 31:0:0:2: Attached scsi generic sg4 type 0 [523522.562294] sd 31:0:0:3: Attached scsi generic sg5 type 0 [523526.062174] usb 1-1: USB disconnect, device number 8 [523526.066148] sd 31:0:0:1: [sdc] READ CAPACITY failed [523526.066151] sd 31:0:0:1: [sdc] [523526.066153] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066154] sd 31:0:0:1: [sdc] Sense not available. [523526.066162] sd 31:0:0:3: [sde] READ CAPACITY failed [523526.066164] sd 31:0:0:3: [sde] [523526.066165] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066166] sd 31:0:0:3: [sde] Sense not available. [523526.066180] sd 31:0:0:3: [sde] Write Protect is off [523526.066181] sd 31:0:0:2: [sdd] READ CAPACITY failed [523526.066183] sd 31:0:0:2: [sdd] [523526.066184] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066185] sd 31:0:0:2: [sdd] Sense not available. [523526.066187] sd 31:0:0:3: [sde] Mode Sense: 00 00 00 00 [523526.066193] sd 31:0:0:1: [sdc] Write Protect is off [523526.066195] sd 31:0:0:1: [sdc] Mode Sense: 00 00 00 00 [523526.066201] sd 31:0:0:2: [sdd] Write Protect is on [523526.066203] sd 31:0:0:2: [sdd] Mode Sense: 90 67 cf b2 [523526.066205] sd 31:0:0:1: [sdc] Asking for cache data failed [523526.066208] sd 31:0:0:1: [sdc] Assuming drive cache: write through [523526.066213] sd 31:0:0:2: [sdd] Asking for cache data failed [523526.066215] sd 31:0:0:2: [sdd] Assuming drive cache: write through [523526.066261] sd 31:0:0:3: [sde] Asking for cache data failed [523526.066264] sd 31:0:0:3: [sde] Assuming drive cache: write through [523526.066411] sd 31:0:0:2: [sdd] READ CAPACITY failed [523526.066414] sd 31:0:0:2: [sdd] [523526.066415] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066416] sd 31:0:0:2: [sdd] Sense not available. [523526.066450] sd 31:0:0:3: [sde] Attached SCSI removable disk [523526.066452] sd 31:0:0:2: [sdd] Asking for cache data failed [523526.066454] sd 31:0:0:2: [sdd] Assuming drive cache: write through [523526.066456] sd 31:0:0:2: [sdd] Attached SCSI removable disk [523526.066457] sd 31:0:0:1: [sdc] Attached SCSI removable disk [523526.072084] sd 31:0:0:0: [sdb] READ CAPACITY failed [523526.072088] sd 31:0:0:0: [sdb] [523526.072089] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.072091] sd 31:0:0:0: [sdb] Sense not available. [523526.072102] sd 31:0:0:0: [sdb] Write Protect is off [523526.072104] sd 31:0:0:0: [sdb] Mode Sense: 00 00 00 00 [523526.072114] sd 31:0:0:0: [sdb] Asking for cache data failed [523526.072116] sd 31:0:0:0: [sdb] Assuming drive cache: write through [523526.072274] sd 31:0:0:0: [sdb] Attached SCSI removable disk [523526.410077] hub 1-0:1.0: unable to enumerate USB device on port 1 [523527.324054] usb 1-1: new high-speed USB device number 10 using ehci_hcd [523527.450935] usb 1-1: New USB device found, idVendor=05e3, idProduct=0760 [523527.450941] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4 [523527.450944] usb 1-1: Product: Flash Reader [523527.450947] usb 1-1: SerialNumber: 37 [523527.453972] scsi32 : usb-storage 1-1:1.0 [523528.458085] scsi 32:0:0:0: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0
[usb_storage][mmc] - Genesys Logic / SilverStone 6-in-1 Card Reader/Writer - Can't mount storage
Hello kernel folks, I have an old 2.0 USB card reader, Linux detects the device but is not able to mount the storage device. I tried it in both a KVM Windows VM and in Linux to mount the storage but device hangs, if I take out card, it detects all 6 device storage capabilities, then it detects the mmc card if i re-insert the card but is unable to mount it. I am using a MMC adapter that can attach a micro-SD card inside it. This USB card reader/writer device comes with a 3.5 bay slot w/ a USB connector to motherboard and can detached for portable reading. Anyone seen this problem before? Does it need any quirks used? Thanks, Shawn. --- SNIP --- Kernel conversation: [523520.622075] usb 1-1: new high-speed USB device number 8 using ehci_hcd [523520.749731] usb 1-1: New USB device found, idVendor=05e3, idProduct=0760 [523520.749735] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4 [523520.749738] usb 1-1: Product: Flash Reader [523520.749739] usb 1-1: SerialNumber: 37 [523520.751674] scsi31 : usb-storage 1-1:1.0 [523521.753494] scsi 31:0:0:0: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523521.884032] usb 1-1: reset high-speed USB device number 8 using ehci_hcd [523522.020128] scsi 31:0:0:1: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523522.157055] usb 1-1: reset high-speed USB device number 8 using ehci_hcd [523522.292672] scsi 31:0:0:2: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523522.426047] usb 1-1: reset high-speed USB device number 8 using ehci_hcd [523522.561250] scsi 31:0:0:3: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0 [523522.561828] sd 31:0:0:0: Attached scsi generic sg2 type 0 [523522.562020] sd 31:0:0:1: Attached scsi generic sg3 type 0 [523522.562158] sd 31:0:0:2: Attached scsi generic sg4 type 0 [523522.562294] sd 31:0:0:3: Attached scsi generic sg5 type 0 [523526.062174] usb 1-1: USB disconnect, device number 8 [523526.066148] sd 31:0:0:1: [sdc] READ CAPACITY failed [523526.066151] sd 31:0:0:1: [sdc] [523526.066153] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066154] sd 31:0:0:1: [sdc] Sense not available. [523526.066162] sd 31:0:0:3: [sde] READ CAPACITY failed [523526.066164] sd 31:0:0:3: [sde] [523526.066165] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066166] sd 31:0:0:3: [sde] Sense not available. [523526.066180] sd 31:0:0:3: [sde] Write Protect is off [523526.066181] sd 31:0:0:2: [sdd] READ CAPACITY failed [523526.066183] sd 31:0:0:2: [sdd] [523526.066184] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066185] sd 31:0:0:2: [sdd] Sense not available. [523526.066187] sd 31:0:0:3: [sde] Mode Sense: 00 00 00 00 [523526.066193] sd 31:0:0:1: [sdc] Write Protect is off [523526.066195] sd 31:0:0:1: [sdc] Mode Sense: 00 00 00 00 [523526.066201] sd 31:0:0:2: [sdd] Write Protect is on [523526.066203] sd 31:0:0:2: [sdd] Mode Sense: 90 67 cf b2 [523526.066205] sd 31:0:0:1: [sdc] Asking for cache data failed [523526.066208] sd 31:0:0:1: [sdc] Assuming drive cache: write through [523526.066213] sd 31:0:0:2: [sdd] Asking for cache data failed [523526.066215] sd 31:0:0:2: [sdd] Assuming drive cache: write through [523526.066261] sd 31:0:0:3: [sde] Asking for cache data failed [523526.066264] sd 31:0:0:3: [sde] Assuming drive cache: write through [523526.066411] sd 31:0:0:2: [sdd] READ CAPACITY failed [523526.066414] sd 31:0:0:2: [sdd] [523526.066415] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.066416] sd 31:0:0:2: [sdd] Sense not available. [523526.066450] sd 31:0:0:3: [sde] Attached SCSI removable disk [523526.066452] sd 31:0:0:2: [sdd] Asking for cache data failed [523526.066454] sd 31:0:0:2: [sdd] Assuming drive cache: write through [523526.066456] sd 31:0:0:2: [sdd] Attached SCSI removable disk [523526.066457] sd 31:0:0:1: [sdc] Attached SCSI removable disk [523526.072084] sd 31:0:0:0: [sdb] READ CAPACITY failed [523526.072088] sd 31:0:0:0: [sdb] [523526.072089] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [523526.072091] sd 31:0:0:0: [sdb] Sense not available. [523526.072102] sd 31:0:0:0: [sdb] Write Protect is off [523526.072104] sd 31:0:0:0: [sdb] Mode Sense: 00 00 00 00 [523526.072114] sd 31:0:0:0: [sdb] Asking for cache data failed [523526.072116] sd 31:0:0:0: [sdb] Assuming drive cache: write through [523526.072274] sd 31:0:0:0: [sdb] Attached SCSI removable disk [523526.410077] hub 1-0:1.0: unable to enumerate USB device on port 1 [523527.324054] usb 1-1: new high-speed USB device number 10 using ehci_hcd [523527.450935] usb 1-1: New USB device found, idVendor=05e3, idProduct=0760 [523527.450941] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4 [523527.450944] usb 1-1: Product: Flash Reader [523527.450947] usb 1-1: SerialNumber: 37 [523527.453972] scsi32 : usb-storage 1-1:1.0 [523528.458085] scsi 32:0:0:0: Direct-Access Generic STORAGE DEVICE 0113 PQ: 0 ANSI: 0
[3.6.x][e1000e] - Regression - Unable to receive packets if MTU == 1500
Hello kernel folks, I recently decided to reinstall my Lenovo W500 laptop and found I wasn't able to get DHCP leases, I wasn't able to install over PXE (when getting the IP a second time within the OS) Fedora is currently using kernel-3.6.2-2.fc18.x86_64 (Pre-beta) The only difference I noticed was in my old install of Fedora, I had added MTU=9000 to the interface config while using a 3.5 kernel, not knowing 3.6.x seems to break things. I have noticed tx unit hang errors sometimes, but not when MTU is above 1500. PCI info: 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) Subsystem: Lenovo Device 20ee Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[3.6.x][e1000e] - Regression - Unable to receive packets if MTU == 1500
Hello kernel folks, I recently decided to reinstall my Lenovo W500 laptop and found I wasn't able to get DHCP leases, I wasn't able to install over PXE (when getting the IP a second time within the OS) Fedora is currently using kernel-3.6.2-2.fc18.x86_64 (Pre-beta) The only difference I noticed was in my old install of Fedora, I had added MTU=9000 to the interface config while using a 3.5 kernel, not knowing 3.6.x seems to break things. I have noticed tx unit hang errors sometimes, but not when MTU is above 1500. PCI info: 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) Subsystem: Lenovo Device 20ee Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 46 Region 0: Memory at fc00 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at fc025000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 1840 [size=32] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0100c Data: 41a2 Capabilities: [e0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: e1000e e1000e conversation log: [ 12.653816] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k [ 12.653819] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. [ 12.653855] e1000e :00:19.0: setting latency timer to 64 [ 12.653938] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 12.653980] e1000e :00:19.0: irq 46 for MSI/MSI-X [ 12.844121] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:22:68:0c:96:e3 [ 12.844124] e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 12.844150] e1000e :00:19.0: eth0: MAC: 7, PHY: 8, PBA No: 1008FF-0FF [ 17.459570] e1000e :00:19.0: eth0: changing MTU from 1500 to 9000 [ 17.459577] e1000e :00:19.0: Interrupt Throttle Rate turned off [ 17.948121] e1000e :00:19.0: irq 46 for MSI/MSI-X [ 18.049164] e1000e :00:19.0: irq 46 for MSI/MSI-X [ 20.442936] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx When I set MTU = 1500 (2000 works), it will stop receiving packets, it also disables Interrupt Throttling when MTU is set higher. After testing reasons why it wasn't get a DHCP lease, I decided to bump the MTU to 9000 for Jumbo Frames and as soon as I did this, I was able to get a lease and the network functioned. Can anyone else report regressions? Thanks, Shawn. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANNOUNCE] RSDL completely fair starvation free interactive cpu scheduler
On Monday 05 March 2007 10:13, Willy Tarreau wrote: > Con, > > I've now given it a try with HZ=250 on my dual-athlon. It works > beautifully. I also quickly checked that playing mp3 doesn't skip during > make -j4, and that gears runs fairly smoothly, since those are the > references people often use. > > But with real work, it's excellent too. When I saturate my CPUs by > injecting HTTP traffic on haproxy, the load is stable and the command line > perfectly responsive, while in the past the load would oscillate and the > command line sometimes stopped to respond for a few seconds. > > I've also launched my scheddos program (you may remember, the one we did a > few experiments with). I could not cause any freeze at all. Plain 2.6.20 > had already improved a lot in this area, but above 4 processes/CPU, > occasional short freezes did still occur. This time, even at 100 processes, > the system was rather slow (of course!) but just as expected, and nothing > more. > > I also tried the good old "dd if=/dev/zero bs=1|...|dd bs=1 of=/dev/null" > and it did not cause any trouble. > > I will boot 2.6 slightly more often to test the code under various > conditions, and I will recommend it to a few people I know who tend to > switch back to 2.4 after one day full of 2.6 jerkiness. > > Overall, you have done a great job ! > > I hope that more people will give it a try, first to help find possible > remaining bugs, and to pronounce in favour of its inclusion in mainline. Hi Con/Willy, Just to chime on this thread, I've been testing Con's scheduler patches since he mentioned them to me. I have to say for desktop performance all processes running remain responsive (although with more resource hungry processes things get slower but remain responsive, but expected). I have also been testing his scheduler on my work power workstation running 4 VMs with 4GB of ram on a dual-core EM64T box, again RSDL performs rather well balancing VM resources even while I have xmms running, xchat, beryl and a bunch of other stuff. There is total response to each process. Thanks, Shawn. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANNOUNCE] RSDL completely fair starvation free interactive cpu scheduler
On Monday 05 March 2007 10:13, Willy Tarreau wrote: Con, I've now given it a try with HZ=250 on my dual-athlon. It works beautifully. I also quickly checked that playing mp3 doesn't skip during make -j4, and that gears runs fairly smoothly, since those are the references people often use. But with real work, it's excellent too. When I saturate my CPUs by injecting HTTP traffic on haproxy, the load is stable and the command line perfectly responsive, while in the past the load would oscillate and the command line sometimes stopped to respond for a few seconds. I've also launched my scheddos program (you may remember, the one we did a few experiments with). I could not cause any freeze at all. Plain 2.6.20 had already improved a lot in this area, but above 4 processes/CPU, occasional short freezes did still occur. This time, even at 100 processes, the system was rather slow (of course!) but just as expected, and nothing more. I also tried the good old dd if=/dev/zero bs=1|...|dd bs=1 of=/dev/null and it did not cause any trouble. I will boot 2.6 slightly more often to test the code under various conditions, and I will recommend it to a few people I know who tend to switch back to 2.4 after one day full of 2.6 jerkiness. Overall, you have done a great job ! I hope that more people will give it a try, first to help find possible remaining bugs, and to pronounce in favour of its inclusion in mainline. Hi Con/Willy, Just to chime on this thread, I've been testing Con's scheduler patches since he mentioned them to me. I have to say for desktop performance all processes running remain responsive (although with more resource hungry processes things get slower but remain responsive, but expected). I have also been testing his scheduler on my work power workstation running 4 VMs with 4GB of ram on a dual-core EM64T box, again RSDL performs rather well balancing VM resources even while I have xmms running, xchat, beryl and a bunch of other stuff. There is total response to each process. Thanks, Shawn. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.19] Scheduler starvation of audio?
Hello, If any of you have used a Commodore 64 emulator in Linux (such as vice) noticed when using audio there is severe starvation while other activities of the system are going on. i.e. moving a window in X or starting another application causing audio to chop (this goes away if you speed up the emulation to 200% then drop it back down to 100% The audio will resume chopping once you perform more activity on the desktop). Note, even increasing the audio buffer of the emulation app to its maximum does not help. Of note, the machine I ran this emulator on had a low load. There are times when I hit starvation and I wonder if there's any interesting scheduler patches in -mm that might address this? Thanks, -- Shawn Starr Software Developer, Open Source Grid Development Center (OSGDC) Platform Computing 3760 14th Avenue Markham, ON L3R3T7 direct: 905.948.4229 http://www.platform.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.19] Scheduler starvation of audio?
Hello, If any of you have used a Commodore 64 emulator in Linux (such as vice) noticed when using audio there is severe starvation while other activities of the system are going on. i.e. moving a window in X or starting another application causing audio to chop (this goes away if you speed up the emulation to 200% then drop it back down to 100% The audio will resume chopping once you perform more activity on the desktop). Note, even increasing the audio buffer of the emulation app to its maximum does not help. Of note, the machine I ran this emulator on had a low load. There are times when I hit starvation and I wonder if there's any interesting scheduler patches in -mm that might address this? Thanks, -- Shawn Starr Software Developer, Open Source Grid Development Center (OSGDC) Platform Computing 3760 14th Avenue Markham, ON L3R3T7 direct: 905.948.4229 http://www.platform.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ieee80211 & ipw2200 (ipw2100) issues
On Tuesday 14 November 2006 7:32 am, Alessandro Suardi wrote: > On 11/13/06, Mark Lord <[EMAIL PROTECTED]> wrote: > > Shawn Starr wrote: > > > With WPA2? I have to confirm if things are still broken with ipw2200 > > > 1.1.4. I wish this was sorted out. Really, the developers seem to have > > > vanished afaik. > > > > I'm using WPA2 CCMP+CCMP(AES) with 2.6.18. No problems. > > WPA1+TKIP in my case. > > --alessandro > > "...when I get it, I _get_ it" > > (Lara Eidemiller) Looks good, 2.6.19-rc6 seems ok. I dont need to download the tarballs now since the version is now 1.1.4 vs 1.1.2 in ipw2200.sf.net. Shawn. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ieee80211 ipw2200 (ipw2100) issues
On Tuesday 14 November 2006 7:32 am, Alessandro Suardi wrote: On 11/13/06, Mark Lord [EMAIL PROTECTED] wrote: Shawn Starr wrote: With WPA2? I have to confirm if things are still broken with ipw2200 1.1.4. I wish this was sorted out. Really, the developers seem to have vanished afaik. I'm using WPA2 CCMP+CCMP(AES) with 2.6.18. No problems. WPA1+TKIP in my case. --alessandro ...when I get it, I _get_ it (Lara Eidemiller) Looks good, 2.6.19-rc6 seems ok. I dont need to download the tarballs now since the version is now 1.1.4 vs 1.1.2 in ipw2200.sf.net. Shawn. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.13-rc6][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode
No, it just took longer to crash. Jeff, do you have any ideas as to why this occuring? If its the ASUS board then are there any workarounds I can do to stop this hanging? Logging a bug, It surely couldn't be the board :( Shawn. -Original Message- From: Shawn Starr Sent: Monday, August 22, 2005 15:53 To: Shawn Starr; 'linux-ide@vger.kernel.org' Cc: 'linux-kernel@vger.kernel.org'; '[EMAIL PROTECTED]' Subject: RE: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode - Resolved in 2.6.13-rc6 It appears 2.6.13-rc6 has enough SATA/libata fixes that stop the DMA read/write locks (the .ordered_flush ops seems to do it). I did also flash the BIOS to the latest release as well (but older 2.6.13-rcX releases had problems still). Thanks, Shawn. -Original Message- From: Shawn Starr Sent: Friday, July 15, 2005 18:09 To: 'linux-ide@vger.kernel.org' Cc: 'linux-kernel@vger.kernel.org'; '[EMAIL PROTECTED]' Subject: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode I just tried -rc3 today on the amd64 box which is a Asus K8N-E Deluxe motherboard. Is it possible the firmware for the controller is buggy? Anyone else reporting hangs? I can reproduce the sata controller with various writes: 1) If I connect the box and allow a remote machine to PXE and TFTP boot from it, the machine hangs. This is consistent each time I try this but only if the box is in 64bit mode. 2) Certain times when doing disk writes it will just hang, there doesn't appear to be any messages from the sil driver logged to console. It still seems to be released to DMA problems. I hope this info is helpful, thanks, Shawn. lspci info: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15) 02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:0c.0 Unknown mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Relevent dmesg: SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ata1: SATA max UDMA/100 cmd 0xFF004C80 ctl 0xFF004C8A bmdma 0xFF004C00 irq 11 ata2: SATA max UDMA/100 cmd 0xFF004CC0 ctl 0xFF004CCA bmdma 0xFF004C08 irq 11 ata3: SATA max UDMA/100 cmd 0xFF004E80 ctl 0xFF004E8A bmdma 0xFF004E00 irq 11 ata4: SATA max UDMA/100 cmd 0xFF004EC0 ctl 0xFF004ECA bmdma 0xFF004E08 irq 11 ata1: no device found (phy stat ) scsi0 : sata_sil ata2: no device found (phy stat ) scsi1 : sata_sil ata3: no device found (phy stat ) scsi2 : sata_sil ata4: no device found (phy stat ) scsi3 : sata_sil sata_nv version 0.6 PCI: Setting latency timer of device :00:0a.0 to 64 ata5: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 10 ata6: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 10 ata5: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:007f ata5: dev 0 ATA, max UDMA/133, 160086528 sectors: nv_sata: Primary device added nv_sata: Primary device removed nv_sata: Secondary device removed ata5: dev 0 configured for UDMA/133 scsi4 : sata_nv ata6: no device found (phy stat ) scsi5 : sata_nv Vendor: ATA Model: Maxtor 6Y080M0Rev: YAR5 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi4, channel 0, id 0, lun 0 Onboard IDE
[2.6.13-rc6][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode
No, it just took longer to crash. Jeff, do you have any ideas as to why this occuring? If its the ASUS board then are there any workarounds I can do to stop this hanging? Logging a bug, It surely couldn't be the board :( Shawn. -Original Message- From: Shawn Starr Sent: Monday, August 22, 2005 15:53 To: Shawn Starr; 'linux-ide@vger.kernel.org' Cc: 'linux-kernel@vger.kernel.org'; '[EMAIL PROTECTED]' Subject: RE: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode - Resolved in 2.6.13-rc6 It appears 2.6.13-rc6 has enough SATA/libata fixes that stop the DMA read/write locks (the .ordered_flush ops seems to do it). I did also flash the BIOS to the latest release as well (but older 2.6.13-rcX releases had problems still). Thanks, Shawn. -Original Message- From: Shawn Starr Sent: Friday, July 15, 2005 18:09 To: 'linux-ide@vger.kernel.org' Cc: 'linux-kernel@vger.kernel.org'; '[EMAIL PROTECTED]' Subject: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode I just tried -rc3 today on the amd64 box which is a Asus K8N-E Deluxe motherboard. Is it possible the firmware for the controller is buggy? Anyone else reporting hangs? I can reproduce the sata controller with various writes: 1) If I connect the box and allow a remote machine to PXE and TFTP boot from it, the machine hangs. This is consistent each time I try this but only if the box is in 64bit mode. 2) Certain times when doing disk writes it will just hang, there doesn't appear to be any messages from the sil driver logged to console. It still seems to be released to DMA problems. I hope this info is helpful, thanks, Shawn. lspci info: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15) 02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:0c.0 Unknown mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Relevent dmesg: SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ata1: SATA max UDMA/100 cmd 0xFF004C80 ctl 0xFF004C8A bmdma 0xFF004C00 irq 11 ata2: SATA max UDMA/100 cmd 0xFF004CC0 ctl 0xFF004CCA bmdma 0xFF004C08 irq 11 ata3: SATA max UDMA/100 cmd 0xFF004E80 ctl 0xFF004E8A bmdma 0xFF004E00 irq 11 ata4: SATA max UDMA/100 cmd 0xFF004EC0 ctl 0xFF004ECA bmdma 0xFF004E08 irq 11 ata1: no device found (phy stat ) scsi0 : sata_sil ata2: no device found (phy stat ) scsi1 : sata_sil ata3: no device found (phy stat ) scsi2 : sata_sil ata4: no device found (phy stat ) scsi3 : sata_sil sata_nv version 0.6 PCI: Setting latency timer of device :00:0a.0 to 64 ata5: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 10 ata6: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 10 ata5: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:007f ata5: dev 0 ATA, max UDMA/133, 160086528 sectors: nv_sata: Primary device added nv_sata: Primary device removed nv_sata: Secondary device removed ata5: dev 0 configured for UDMA/133 scsi4 : sata_nv ata6: no device found (phy stat ) scsi5 : sata_nv Vendor: ATA Model: Maxtor 6Y080M0Rev: YAR5 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi4, channel 0, id 0, lun 0 Onboard IDE
RE: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode - Resolved in 2.6.13-rc6
It appears 2.6.13-rc6 has enough SATA/libata fixes that stop the DMA read/write locks (the .ordered_flush ops seems to do it). I did also flash the BIOS to the latest release as well (but older 2.6.13-rcX releases had problems still). Thanks, Shawn. -Original Message- From: Shawn Starr Sent: Friday, July 15, 2005 18:09 To: 'linux-ide@vger.kernel.org' Cc: 'linux-kernel@vger.kernel.org'; '[EMAIL PROTECTED]' Subject: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode I just tried -rc3 today on the amd64 box which is a Asus K8N-E Deluxe motherboard. Is it possible the firmware for the controller is buggy? Anyone else reporting hangs? I can reproduce the sata controller with various writes: 1) If I connect the box and allow a remote machine to PXE and TFTP boot from it, the machine hangs. This is consistent each time I try this but only if the box is in 64bit mode. 2) Certain times when doing disk writes it will just hang, there doesn't appear to be any messages from the sil driver logged to console. It still seems to be released to DMA problems. I hope this info is helpful, thanks, Shawn. lspci info: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15) 02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:0c.0 Unknown mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Relevent dmesg: SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ata1: SATA max UDMA/100 cmd 0xFF004C80 ctl 0xFF004C8A bmdma 0xFF004C00 irq 11 ata2: SATA max UDMA/100 cmd 0xFF004CC0 ctl 0xFF004CCA bmdma 0xFF004C08 irq 11 ata3: SATA max UDMA/100 cmd 0xFF004E80 ctl 0xFF004E8A bmdma 0xFF004E00 irq 11 ata4: SATA max UDMA/100 cmd 0xFF004EC0 ctl 0xFF004ECA bmdma 0xFF004E08 irq 11 ata1: no device found (phy stat ) scsi0 : sata_sil ata2: no device found (phy stat ) scsi1 : sata_sil ata3: no device found (phy stat ) scsi2 : sata_sil ata4: no device found (phy stat ) scsi3 : sata_sil sata_nv version 0.6 PCI: Setting latency timer of device :00:0a.0 to 64 ata5: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 10 ata6: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 10 ata5: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:007f ata5: dev 0 ATA, max UDMA/133, 160086528 sectors: nv_sata: Primary device added nv_sata: Primary device removed nv_sata: Secondary device removed ata5: dev 0 configured for UDMA/133 scsi4 : sata_nv ata6: no device found (phy stat ) scsi5 : sata_nv Vendor: ATA Model: Maxtor 6Y080M0Rev: YAR5 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi4, channel 0, id 0, lun 0 Onboard IDE controller and devices information: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx NFORCE3-250: IDE controller at PCI slot :00:08.0 NFORCE3-250: chipset revision 162 NFORCE3-250: not 100% native mode: will probe irqs later NFORCE3-250: :00:08.0 (rev a2) UDMA133 controller ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: GCR-8523B, ATAPI
RE: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode - Resolved in 2.6.13-rc6
It appears 2.6.13-rc6 has enough SATA/libata fixes that stop the DMA read/write locks (the .ordered_flush ops seems to do it). I did also flash the BIOS to the latest release as well (but older 2.6.13-rcX releases had problems still). Thanks, Shawn. -Original Message- From: Shawn Starr Sent: Friday, July 15, 2005 18:09 To: 'linux-ide@vger.kernel.org' Cc: 'linux-kernel@vger.kernel.org'; '[EMAIL PROTECTED]' Subject: [2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode I just tried -rc3 today on the amd64 box which is a Asus K8N-E Deluxe motherboard. Is it possible the firmware for the controller is buggy? Anyone else reporting hangs? I can reproduce the sata controller with various writes: 1) If I connect the box and allow a remote machine to PXE and TFTP boot from it, the machine hangs. This is consistent each time I try this but only if the box is in 64bit mode. 2) Certain times when doing disk writes it will just hang, there doesn't appear to be any messages from the sil driver logged to console. It still seems to be released to DMA problems. I hope this info is helpful, thanks, Shawn. lspci info: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15) 02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:0c.0 Unknown mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Relevent dmesg: SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ata1: SATA max UDMA/100 cmd 0xFF004C80 ctl 0xFF004C8A bmdma 0xFF004C00 irq 11 ata2: SATA max UDMA/100 cmd 0xFF004CC0 ctl 0xFF004CCA bmdma 0xFF004C08 irq 11 ata3: SATA max UDMA/100 cmd 0xFF004E80 ctl 0xFF004E8A bmdma 0xFF004E00 irq 11 ata4: SATA max UDMA/100 cmd 0xFF004EC0 ctl 0xFF004ECA bmdma 0xFF004E08 irq 11 ata1: no device found (phy stat ) scsi0 : sata_sil ata2: no device found (phy stat ) scsi1 : sata_sil ata3: no device found (phy stat ) scsi2 : sata_sil ata4: no device found (phy stat ) scsi3 : sata_sil sata_nv version 0.6 PCI: Setting latency timer of device :00:0a.0 to 64 ata5: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 10 ata6: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 10 ata5: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:007f ata5: dev 0 ATA, max UDMA/133, 160086528 sectors: nv_sata: Primary device added nv_sata: Primary device removed nv_sata: Secondary device removed ata5: dev 0 configured for UDMA/133 scsi4 : sata_nv ata6: no device found (phy stat ) scsi5 : sata_nv Vendor: ATA Model: Maxtor 6Y080M0Rev: YAR5 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi4, channel 0, id 0, lun 0 Onboard IDE controller and devices information: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx NFORCE3-250: IDE controller at PCI slot :00:08.0 NFORCE3-250: chipset revision 162 NFORCE3-250: not 100% native mode: will probe irqs later NFORCE3-250: :00:08.0 (rev a2) UDMA133 controller ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: GCR-8523B, ATAPI
Re: [BUG][2.6.7+(or eariler)] Switching from LCD to external video w/ no external video connected causes deadlock - Regression
We're back to square one, in VT mode the system deadlocks once again when switching between LCD, External video modes. Kernel: 2.6.13-rc5 (merucurial build August 2nd snapshot). Looks like this bug needs to be reopened again :/ Shawn. On November 10, 2004 19:14, Shawn Starr wrote: > As of 2.6.9 in Linux console, it properly switches between modes, there is > a small delay when switching to external VGA (if you have sound playing it > will repeat for a moment then resume). There is no deadlocks. > > I cant test inside X just yet (w/ Xinerama extension) > > Shawn. > > On November 10, 2004 19:04, Andrew Morton wrote: > > Is this still happening in current kernels? > > > > Thanks. > > > > "Shawn Starr" <[EMAIL PROTECTED]> wrote: > > > I've noticed a few people with IBM Thinkpads running 2.6.7+ - different > > > models - have this problem. I don't know where in 2.6 this begin > > > happening though. > > > > > > When you use the function key and switch from LCD to External Video, > > > the system deadlocks. > > > While ssh'd into the laptop the system has deadlocked once I switched > > > video. Unfortunately, I don't have a USB <-> Serial dongle handy yet > > > ;-) > > > > > > The Video card is a ATI Radeon 9600 64MB RAM, kernel has no framebuffer > > > support enabled. > > > > > > Is this a known issue? > > > > > > Thanks. > > > > > > Shawn. > > > > > > - > > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" > > > in the body of a message to [EMAIL PROTECTED] > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG][2.6.7+(or eariler)] Switching from LCD to external video w/ no external video connected causes deadlock - Regression
We're back to square one, in VT mode the system deadlocks once again when switching between LCD, External video modes. Kernel: 2.6.13-rc5 (merucurial build August 2nd snapshot). Looks like this bug needs to be reopened again :/ Shawn. On November 10, 2004 19:14, Shawn Starr wrote: As of 2.6.9 in Linux console, it properly switches between modes, there is a small delay when switching to external VGA (if you have sound playing it will repeat for a moment then resume). There is no deadlocks. I cant test inside X just yet (w/ Xinerama extension) Shawn. On November 10, 2004 19:04, Andrew Morton wrote: Is this still happening in current kernels? Thanks. Shawn Starr [EMAIL PROTECTED] wrote: I've noticed a few people with IBM Thinkpads running 2.6.7+ - different models - have this problem. I don't know where in 2.6 this begin happening though. When you use the function key and switch from LCD to External Video, the system deadlocks. While ssh'd into the laptop the system has deadlocked once I switched video. Unfortunately, I don't have a USB - Serial dongle handy yet ;-) The Video card is a ATI Radeon 9600 64MB RAM, kernel has no framebuffer support enabled. Is this a known issue? Thanks. Shawn. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode
I just tried -rc3 today on the amd64 box which is a Asus K8N-E Deluxe motherboard. Is it possible the firmware for the controller is buggy? Anyone else reporting hangs? I can reproduce the sata controller with various writes: 1) If I connect the box and allow a remote machine to PXE and TFTP boot from it, the machine hangs. This is consistent each time I try this but only if the box is in 64bit mode. 2) Certain times when doing disk writes it will just hang, there doesn't appear to be any messages from the sil driver logged to console. It still seems to be released to DMA problems. I hope this info is helpful, thanks, Shawn. lspci info: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15) 02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:0c.0 Unknown mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Relevent dmesg: SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ata1: SATA max UDMA/100 cmd 0xFF004C80 ctl 0xFF004C8A bmdma 0xFF004C00 irq 11 ata2: SATA max UDMA/100 cmd 0xFF004CC0 ctl 0xFF004CCA bmdma 0xFF004C08 irq 11 ata3: SATA max UDMA/100 cmd 0xFF004E80 ctl 0xFF004E8A bmdma 0xFF004E00 irq 11 ata4: SATA max UDMA/100 cmd 0xFF004EC0 ctl 0xFF004ECA bmdma 0xFF004E08 irq 11 ata1: no device found (phy stat ) scsi0 : sata_sil ata2: no device found (phy stat ) scsi1 : sata_sil ata3: no device found (phy stat ) scsi2 : sata_sil ata4: no device found (phy stat ) scsi3 : sata_sil sata_nv version 0.6 PCI: Setting latency timer of device :00:0a.0 to 64 ata5: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 10 ata6: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 10 ata5: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:007f ata5: dev 0 ATA, max UDMA/133, 160086528 sectors: nv_sata: Primary device added nv_sata: Primary device removed nv_sata: Secondary device removed ata5: dev 0 configured for UDMA/133 scsi4 : sata_nv ata6: no device found (phy stat ) scsi5 : sata_nv Vendor: ATA Model: Maxtor 6Y080M0Rev: YAR5 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi4, channel 0, id 0, lun 0 Onboard IDE controller and devices information: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx NFORCE3-250: IDE controller at PCI slot :00:08.0 NFORCE3-250: chipset revision 162 NFORCE3-250: not 100% native mode: will probe irqs later NFORCE3-250: :00:08.0 (rev a2) UDMA133 controller ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: GCR-8523B, ATAPI CD/DVD-ROM drive hdb: LITE-ON DVD SOHD-16P9S, ATAPI CD/DVD-ROM drive - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.13-rc3][SATA] - SIL 3114 controller w/ firmware 5.0.39 - Hanging only in 64bit mode
I just tried -rc3 today on the amd64 box which is a Asus K8N-E Deluxe motherboard. Is it possible the firmware for the controller is buggy? Anyone else reporting hangs? I can reproduce the sata controller with various writes: 1) If I connect the box and allow a remote machine to PXE and TFTP boot from it, the machine hangs. This is consistent each time I try this but only if the box is in 64bit mode. 2) Certain times when doing disk writes it will just hang, there doesn't appear to be any messages from the sil driver logged to console. It still seems to be released to DMA problems. I hope this info is helpful, thanks, Shawn. lspci info: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15) 02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 02:0c.0 Unknown mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Relevent dmesg: SCSI subsystem initialized libata version 1.10 loaded. sata_sil version 0.8 ata1: SATA max UDMA/100 cmd 0xFF004C80 ctl 0xFF004C8A bmdma 0xFF004C00 irq 11 ata2: SATA max UDMA/100 cmd 0xFF004CC0 ctl 0xFF004CCA bmdma 0xFF004C08 irq 11 ata3: SATA max UDMA/100 cmd 0xFF004E80 ctl 0xFF004E8A bmdma 0xFF004E00 irq 11 ata4: SATA max UDMA/100 cmd 0xFF004EC0 ctl 0xFF004ECA bmdma 0xFF004E08 irq 11 ata1: no device found (phy stat ) scsi0 : sata_sil ata2: no device found (phy stat ) scsi1 : sata_sil ata3: no device found (phy stat ) scsi2 : sata_sil ata4: no device found (phy stat ) scsi3 : sata_sil sata_nv version 0.6 PCI: Setting latency timer of device :00:0a.0 to 64 ata5: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 10 ata6: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 10 ata5: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:007f ata5: dev 0 ATA, max UDMA/133, 160086528 sectors: nv_sata: Primary device added nv_sata: Primary device removed nv_sata: Secondary device removed ata5: dev 0 configured for UDMA/133 scsi4 : sata_nv ata6: no device found (phy stat ) scsi5 : sata_nv Vendor: ATA Model: Maxtor 6Y080M0Rev: YAR5 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi4, channel 0, id 0, lun 0 Onboard IDE controller and devices information: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx NFORCE3-250: IDE controller at PCI slot :00:08.0 NFORCE3-250: chipset revision 162 NFORCE3-250: not 100% native mode: will probe irqs later NFORCE3-250: :00:08.0 (rev a2) UDMA133 controller ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: GCR-8523B, ATAPI CD/DVD-ROM drive hdb: LITE-ON DVD SOHD-16P9S, ATAPI CD/DVD-ROM drive - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] Updating hard disk firmware & parking hard disk
Perhaps you also need to flash the BIOS and or Embedded Controller firmware? Shawn. On July 13, 2005 04:58, Gijs Hillenius wrote: > > Frank Sorenson writes: > > Martin Knoblauch wrote: > > > >> Download is simple, just don't use the "IBM Download > >> Manager". Main problem is that one needs a bootable floopy > >> drive and "the other OS" to create a bootable floppy. It would > >> be great if IBM could provide floppy images for use with "dd" > >> for the poor Linux users. > >> > > You may be able to use this process to avoid using either a > > floppy drive or "the other OS": > > > > 1) Download the appropriate firmware exe from > > http://www-306.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR- > >41008 (in my case, this looks like fwhd3313.exe) > > > > 2) Find a freedos disk image (I used one that came with > > biosdisk - http://linux.dell.com/biosdisk/) > > > > 3) Create a disk image for the firmware executable: cp > > /usr/share/biosdisk/dosdisk.img /tmp/fwdisk1.img mount -oloop > > /tmp/fwtemp.img /mnt/tmp cp fwhd3313.exe /mnt/tmp umount > > /mnt/tmp > > > > 4) Create a blank disk image for the extracted contents: dd > > if=/dev/zero of=/boot/fwdisk.img bs=1474560 count=1 > > > > 5) Run qemu to extract files and write the disk image: qemu > > -fda /tmp/fwtemp.img -fdb /boot/fwdisk.img A:\>fwhd3313 ... > > exit qemu > > > > 6) Set up grub to boot the new disk image (requires memdisk > > from syslinux - http://syslinux.zytor.com/): $EDITOR > > /boot/grub/grub.conf title IBM Hard Drive Firmware update > > kernel /memdisk initrd=/fwdisk.img floppy > > > > 7) Reboot and select the "IBM Hard Drive Firmware update" > > option > > > > > > It allowed me to run the firmware update program, however it > > didn't believe my drive needed updating, so I haven't even > > successfully tried the entire process. Please let me know if > > it works for you. > > > > DISCLAIMER: I also provide no guarantees. Hopefully your hard > > disk won't fly off the spindle or anything else bad. If it > > does, blame someone else. > > Hi Frank, > > FYI I succesfully used your above method to update the firmware > for the IC25N040ATMR04-0 hard disk that came with my Thinkpad R51. > > Before the update hdparm -i /dev/hda > Model=IC25N040ATMR04-0, FwRev=MO2OAD4A > > and after the update > Model=IC25N040ATMR04-0, FwRev=MO2OADEA > > So, thanks! > > however, the firmware update did not solve the 'head not park' > issue. :-( > > sudo ./park /dev/hda > head not parked 4c > > > Regards > > Gijs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] Updating hard disk firmware parking hard disk
Perhaps you also need to flash the BIOS and or Embedded Controller firmware? Shawn. On July 13, 2005 04:58, Gijs Hillenius wrote: Frank Sorenson writes: Martin Knoblauch wrote: Download is simple, just don't use the IBM Download Manager. Main problem is that one needs a bootable floopy drive and the other OS to create a bootable floppy. It would be great if IBM could provide floppy images for use with dd for the poor Linux users. You may be able to use this process to avoid using either a floppy drive or the other OS: 1) Download the appropriate firmware exe from http://www-306.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR- 41008 (in my case, this looks like fwhd3313.exe) 2) Find a freedos disk image (I used one that came with biosdisk - http://linux.dell.com/biosdisk/) 3) Create a disk image for the firmware executable: cp /usr/share/biosdisk/dosdisk.img /tmp/fwdisk1.img mount -oloop /tmp/fwtemp.img /mnt/tmp cp fwhd3313.exe /mnt/tmp umount /mnt/tmp 4) Create a blank disk image for the extracted contents: dd if=/dev/zero of=/boot/fwdisk.img bs=1474560 count=1 5) Run qemu to extract files and write the disk image: qemu -fda /tmp/fwtemp.img -fdb /boot/fwdisk.img A:\fwhd3313 ... exit qemu 6) Set up grub to boot the new disk image (requires memdisk from syslinux - http://syslinux.zytor.com/): $EDITOR /boot/grub/grub.conf title IBM Hard Drive Firmware update kernel /memdisk initrd=/fwdisk.img floppy 7) Reboot and select the IBM Hard Drive Firmware update option It allowed me to run the firmware update program, however it didn't believe my drive needed updating, so I haven't even successfully tried the entire process. Please let me know if it works for you. DISCLAIMER: I also provide no guarantees. Hopefully your hard disk won't fly off the spindle or anything else bad. If it does, blame someone else. Hi Frank, FYI I succesfully used your above method to update the firmware for the IC25N040ATMR04-0 hard disk that came with my Thinkpad R51. Before the update hdparm -i /dev/hda Model=IC25N040ATMR04-0, FwRev=MO2OAD4A and after the update Model=IC25N040ATMR04-0, FwRev=MO2OADEA So, thanks! however, the firmware update did not solve the 'head not park' issue. :-( sudo ./park /dev/hda head not parked 4c Regards Gijs - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
It should be noted im using linux-2.6.git. --- Jens Axboe <[EMAIL PROTECTED]> wrote: > On Fri, Jul 08 2005, Jon Escombe wrote: > > Jens Axboe wrote: > > > > >On Thu, Jul 07 2005, Shawn Starr wrote: > > > > > > > > >>Model: HTS548080M9AT00 (Hitachi) > > >>Laptop: T42. > > >> > > >>segfault:/home/spstarr# ./a /dev/hda > > >>head parked > > >> > > >>Seems to park, heard it click :) > > >> > > >> > > > > > >Note on that - if the util says it parked, you > can be very sure that it > > >actually did as the drive actually returns that > status outside of just > > >completing the command. > > > > > > > > It's worth noting that you'll need the libata > passthrough patch to make > > this work on a T43.. > > > > However, with this patch I'm getting the "head not > parked 4c" message, > > but I can hear the click from the drive.. It takes > around 350-400ms for > > the command to execute, but when repeated, it > drops to around 5ms for a > > short while (with no audible clicking), before > reverting to original > > behaviour after a few seconds. > > > > The clicking and the variation in execution time > lead me to think it is > > parking, but not being reported correctly? > > Sounds like a pass through bug, it should pass the > register output back > out again for a non-data command. > > Checking code... Yeah it does not. Since the 'we > parked successfully' is > stored in the lbal register, we need the full > register set copied back > into the buffer. That goes for all three HDIO_* > commands, there's still > some work to be done for the libata passthrough to > be compliant with the > ide one. > > -- > Jens Axboe > > > > --- > This SF.Net email is sponsored by the 'Do More With > Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to > explore the latest in dual > core and dual graphics technology at this free one > hour event hosted by HP, > AMD, and NVIDIA. To register visit > http://www.hp.com/go/dualwebinar > ___ > Hdaps-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hdaps-devel > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
It should be noted im using linux-2.6.git. --- Jens Axboe [EMAIL PROTECTED] wrote: On Fri, Jul 08 2005, Jon Escombe wrote: Jens Axboe wrote: On Thu, Jul 07 2005, Shawn Starr wrote: Model: HTS548080M9AT00 (Hitachi) Laptop: T42. segfault:/home/spstarr# ./a /dev/hda head parked Seems to park, heard it click :) Note on that - if the util says it parked, you can be very sure that it actually did as the drive actually returns that status outside of just completing the command. It's worth noting that you'll need the libata passthrough patch to make this work on a T43.. However, with this patch I'm getting the head not parked 4c message, but I can hear the click from the drive.. It takes around 350-400ms for the command to execute, but when repeated, it drops to around 5ms for a short while (with no audible clicking), before reverting to original behaviour after a few seconds. The clicking and the variation in execution time lead me to think it is parking, but not being reported correctly? Sounds like a pass through bug, it should pass the register output back out again for a non-data command. Checking code... Yeah it does not. Since the 'we parked successfully' is stored in the lbal register, we need the full register set copied back into the buffer. That goes for all three HDIO_* commands, there's still some work to be done for the libata passthrough to be compliant with the ide one. -- Jens Axboe --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Hdaps-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hdaps-devel - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] RE: Head parking (was: IBM HDAPS things are looking up)
You can take the .exe file and turn this into a bootable CD (using a RW CD) I forgot how I did it, but if I remember correctly, I took a floppy dos image and made that into the boot 'stub' and threw the exe into the CD (a la El-Torito). I flashed the disk firmware once since I got the laptop. Shawn. On July 7, 2005 14:51, Erik Mouw wrote: > On Thu, Jul 07, 2005 at 11:45:38AM -0700, Martin Knoblauch wrote: > > If IBM would provide a CD image (bootable ISO) containing FW for all > > supported drives - that would be great. No need for the "other OS" any > > more. > > I can imagine IBM doesn't do that because in that way you can't update > the firmware of the CD/DVD drive. Bootable FreeDOS floppy images would > be a nice idea, though. > > > Erik (not a ThinkPad owner) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] Re: Head parking (was: IBM HDAPS things are looking up)
Model: HTS548080M9AT00 (Hitachi) Laptop: T42. segfault:/home/spstarr# ./a /dev/hda head parked Seems to park, heard it click :) Shawn. On July 7, 2005 04:48, Jens Axboe wrote: > On Thu, Jul 07 2005, Lenz Grimmer wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hi, > > > > Jens Axboe wrote: > > > ATA7 defines a park maneuvre, I don't know how well supported it is > > > yet though. You can test with this little app, if it says 'head > > > parked' it works. If not, it has just idled the drive. > > > > Great! Thanks for digging this up - it works on my T42, using a Fujitsu > > MHT2080AH drive: > > > > [EMAIL PROTECTED]:~/work/ibm_hdaps> sudo ./headpark /dev/hda > > head parked > > > > Judging from the sound the drive makes, this is the same operation that > > the windows tool performs. > > Very cool, I wasn't sure if this was a 'new' feature waiting to be > implemented in drives or if ata7 just documented existing use in some > drives. > > How long did the park take? Spec states it can take up to 500ms. > > > However, the head does not remain parked for a very long time, > > especially if there is a lot of disk activity going on (I tested it by > > running a "find /" in parallel). The head parks, but leaves the park > > position immediately afterwards again. I guess now we need to find a way > > to "nail" the head into the parking position for some time - otherwise > > it may already be on its way back to the platter before the laptop hits > > the ground... > > The head just remains parked until the next command is issued. This > needs to be combined with some ide help, to freeze the queue. Perhaps > some sysfs file so you could do > > # echo park > /sys/block/hda/device/head_state > > Or whatever, at least just exposing this possibility so that the drive > internally can block future io until a 'resume' command is issued. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
Model: HTS548080M9AT00 (Hitachi)
Laptop: T42.
segfault:/home/spstarr# ./a /dev/hda
head parked
Seems to park, heard it click :)
Shawn.
On July 7, 2005 04:03, Jens Axboe wrote:
> On Mon, Jul 04 2005, Jens Axboe wrote:
> > On Mon, Jul 04 2005, Lenz Grimmer wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > Hi,
> > >
> > > Jens Axboe wrote:
> > > > It isn't too pretty to rely on such unreliable timing anyways. I'm
> > > > not too crazy about spinning the disk down either, it's useless wear
> > > > compared to just parking the head.
> > >
> > > Fully agreed, and that's the approach the IBM Windows driver seems to
> > > take - you just hear the disk park its head when the sensor kicks in
> > > (you can hear it) - the disk does not spin down when this happens.
> > >
> > > Could this be some reserved ATA command that only works with certain#
> > > drives?
> >
> > Perhaps the IDLE or IDLEIMMEDIATE commands imply a head parking, that
> > would make sense. As you say, you can hear a drive parking its head.
> > Here's a test case, it doesn't sound like it's parking the hard here.
>
> ATA7 defines a park maneuvre, I don't know how well supported it is yet
> though. You can test with this little app, if it says 'head parked' it
> works. If not, it has just idled the drive.
>
>
> #include
> #include
> #include
> #include
> #include
> #include
>
> int main(int argc, char *argv[])
> {
> unsigned char buf[8];
> int fd;
>
> if (argc < 2) {
> printf("%s \n", argv[0]);
> return 1;
> }
>
> fd = open(argv[1], O_RDONLY);
> if (fd == -1) {
> perror("open");
> return 1;
> }
>
> memset(buf, 0, sizeof(buf));
> buf[0] = 0xe1;
> buf[1] = 0x44;
> buf[3] = 0x4c;
> buf[4] = 0x4e;
> buf[5] = 0x55;
>
> if (ioctl(fd, HDIO_DRIVE_TASK, buf)) {
> perror("ioctl");
> return 1;
> }
>
> if (buf[3] == 0xc4)
> printf("head parked\n");
> else
> printf("head not parked %x\n", buf[3]);
>
> close(fd);
> return 0;
> }
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
Model: HTS548080M9AT00 (Hitachi)
Laptop: T42.
segfault:/home/spstarr# ./a /dev/hda
head parked
Seems to park, heard it click :)
Shawn.
On July 7, 2005 04:03, Jens Axboe wrote:
> On Mon, Jul 04 2005, Jens Axboe wrote:
> > On Mon, Jul 04 2005, Lenz Grimmer wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > Hi,
> > >
> > > Jens Axboe wrote:
> > > > It isn't too pretty to rely on such unreliable timing anyways. I'm
> > > > not too crazy about spinning the disk down either, it's useless wear
> > > > compared to just parking the head.
> > >
> > > Fully agreed, and that's the approach the IBM Windows driver seems to
> > > take - you just hear the disk park its head when the sensor kicks in
> > > (you can hear it) - the disk does not spin down when this happens.
> > >
> > > Could this be some reserved ATA command that only works with certain#
> > > drives?
> >
> > Perhaps the IDLE or IDLEIMMEDIATE commands imply a head parking, that
> > would make sense. As you say, you can hear a drive parking its head.
> > Here's a test case, it doesn't sound like it's parking the hard here.
>
> ATA7 defines a park maneuvre, I don't know how well supported it is yet
> though. You can test with this little app, if it says 'head parked' it
> works. If not, it has just idled the drive.
>
>
> #include
> #include
> #include
> #include
> #include
> #include
>
> int main(int argc, char *argv[])
> {
> unsigned char buf[8];
> int fd;
>
> if (argc < 2) {
> printf("%s \n", argv[0]);
> return 1;
> }
>
> fd = open(argv[1], O_RDONLY);
> if (fd == -1) {
> perror("open");
> return 1;
> }
>
> memset(buf, 0, sizeof(buf));
> buf[0] = 0xe1;
> buf[1] = 0x44;
> buf[3] = 0x4c;
> buf[4] = 0x4e;
> buf[5] = 0x55;
>
> if (ioctl(fd, HDIO_DRIVE_TASK, buf)) {
> perror("ioctl");
> return 1;
> }
>
> if (buf[3] == 0xc4)
> printf("head parked\n");
> else
> printf("head not parked %x\n", buf[3]);
>
> close(fd);
> return 0;
> }
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
Model: HTS548080M9AT00 (Hitachi)
Laptop: T42.
segfault:/home/spstarr# ./a /dev/hda
head parked
Seems to park, heard it click :)
Shawn.
On July 7, 2005 04:03, Jens Axboe wrote:
On Mon, Jul 04 2005, Jens Axboe wrote:
On Mon, Jul 04 2005, Lenz Grimmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Jens Axboe wrote:
It isn't too pretty to rely on such unreliable timing anyways. I'm
not too crazy about spinning the disk down either, it's useless wear
compared to just parking the head.
Fully agreed, and that's the approach the IBM Windows driver seems to
take - you just hear the disk park its head when the sensor kicks in
(you can hear it) - the disk does not spin down when this happens.
Could this be some reserved ATA command that only works with certain#
drives?
Perhaps the IDLE or IDLEIMMEDIATE commands imply a head parking, that
would make sense. As you say, you can hear a drive parking its head.
Here's a test case, it doesn't sound like it's parking the hard here.
ATA7 defines a park maneuvre, I don't know how well supported it is yet
though. You can test with this little app, if it says 'head parked' it
works. If not, it has just idled the drive.
#include stdio.h
#include unistd.h
#include fcntl.h
#include string.h
#include sys/ioctl.h
#include linux/hdreg.h
int main(int argc, char *argv[])
{
unsigned char buf[8];
int fd;
if (argc 2) {
printf(%s dev\n, argv[0]);
return 1;
}
fd = open(argv[1], O_RDONLY);
if (fd == -1) {
perror(open);
return 1;
}
memset(buf, 0, sizeof(buf));
buf[0] = 0xe1;
buf[1] = 0x44;
buf[3] = 0x4c;
buf[4] = 0x4e;
buf[5] = 0x55;
if (ioctl(fd, HDIO_DRIVE_TASK, buf)) {
perror(ioctl);
return 1;
}
if (buf[3] == 0xc4)
printf(head parked\n);
else
printf(head not parked %x\n, buf[3]);
close(fd);
return 0;
}
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
Model: HTS548080M9AT00 (Hitachi)
Laptop: T42.
segfault:/home/spstarr# ./a /dev/hda
head parked
Seems to park, heard it click :)
Shawn.
On July 7, 2005 04:03, Jens Axboe wrote:
On Mon, Jul 04 2005, Jens Axboe wrote:
On Mon, Jul 04 2005, Lenz Grimmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Jens Axboe wrote:
It isn't too pretty to rely on such unreliable timing anyways. I'm
not too crazy about spinning the disk down either, it's useless wear
compared to just parking the head.
Fully agreed, and that's the approach the IBM Windows driver seems to
take - you just hear the disk park its head when the sensor kicks in
(you can hear it) - the disk does not spin down when this happens.
Could this be some reserved ATA command that only works with certain#
drives?
Perhaps the IDLE or IDLEIMMEDIATE commands imply a head parking, that
would make sense. As you say, you can hear a drive parking its head.
Here's a test case, it doesn't sound like it's parking the hard here.
ATA7 defines a park maneuvre, I don't know how well supported it is yet
though. You can test with this little app, if it says 'head parked' it
works. If not, it has just idled the drive.
#include stdio.h
#include unistd.h
#include fcntl.h
#include string.h
#include sys/ioctl.h
#include linux/hdreg.h
int main(int argc, char *argv[])
{
unsigned char buf[8];
int fd;
if (argc 2) {
printf(%s dev\n, argv[0]);
return 1;
}
fd = open(argv[1], O_RDONLY);
if (fd == -1) {
perror(open);
return 1;
}
memset(buf, 0, sizeof(buf));
buf[0] = 0xe1;
buf[1] = 0x44;
buf[3] = 0x4c;
buf[4] = 0x4e;
buf[5] = 0x55;
if (ioctl(fd, HDIO_DRIVE_TASK, buf)) {
perror(ioctl);
return 1;
}
if (buf[3] == 0xc4)
printf(head parked\n);
else
printf(head not parked %x\n, buf[3]);
close(fd);
return 0;
}
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] Re: Head parking (was: IBM HDAPS things are looking up)
Model: HTS548080M9AT00 (Hitachi) Laptop: T42. segfault:/home/spstarr# ./a /dev/hda head parked Seems to park, heard it click :) Shawn. On July 7, 2005 04:48, Jens Axboe wrote: On Thu, Jul 07 2005, Lenz Grimmer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Jens Axboe wrote: ATA7 defines a park maneuvre, I don't know how well supported it is yet though. You can test with this little app, if it says 'head parked' it works. If not, it has just idled the drive. Great! Thanks for digging this up - it works on my T42, using a Fujitsu MHT2080AH drive: [EMAIL PROTECTED]:~/work/ibm_hdaps sudo ./headpark /dev/hda head parked Judging from the sound the drive makes, this is the same operation that the windows tool performs. Very cool, I wasn't sure if this was a 'new' feature waiting to be implemented in drives or if ata7 just documented existing use in some drives. How long did the park take? Spec states it can take up to 500ms. However, the head does not remain parked for a very long time, especially if there is a lot of disk activity going on (I tested it by running a find / in parallel). The head parks, but leaves the park position immediately afterwards again. I guess now we need to find a way to nail the head into the parking position for some time - otherwise it may already be on its way back to the platter before the laptop hits the ground... The head just remains parked until the next command is issued. This needs to be combined with some ide help, to freeze the queue. Perhaps some sysfs file so you could do # echo park /sys/block/hda/device/head_state Or whatever, at least just exposing this possibility so that the drive internally can block future io until a 'resume' command is issued. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] RE: Head parking (was: IBM HDAPS things are looking up)
You can take the .exe file and turn this into a bootable CD (using a RW CD) I forgot how I did it, but if I remember correctly, I took a floppy dos image and made that into the boot 'stub' and threw the exe into the CD (a la El-Torito). I flashed the disk firmware once since I got the laptop. Shawn. On July 7, 2005 14:51, Erik Mouw wrote: On Thu, Jul 07, 2005 at 11:45:38AM -0700, Martin Knoblauch wrote: If IBM would provide a CD image (bootable ISO) containing FW for all supported drives - that would be great. No need for the other OS any more. I can imagine IBM doesn't do that because in that way you can't update the firmware of the CD/DVD drive. Bootable FreeDOS floppy images would be a nice idea, though. Erik (not a ThinkPad owner) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] Re: IBM HDAPS things are looking up
>From what I'm told its not specific to hard disk, you
can put any laptop HD and it will work the same (?).
Shawn.
--- Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 04 2005, Lenz Grimmer wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi Jens!
> >
> > Thanks for the sample code. I've trimmed the
> recipient list a bit...
> >
> > Jens Axboe wrote:
> >
> > > Perhaps the IDLE or IDLEIMMEDIATE commands imply
> a head parking, that
> > > would make sense. As you say, you can hear a
> drive parking its head.
> > > Here's a test case, it doesn't sound like it's
> parking the hard here.
> >
> > Not here either, but let me check, if I understand
> this correctly:
> >
> > > #include
> > > #include
> > > #include
> > > #include
> > > #include
> > >
> > > int main(int argc, char *argv[])
> > > {
> > > char cmd[4] = { 0xe1, 0, 0, 0 };
> >
> > The "0xe1" in here is what is defined as
> "WIN_IDLEIMMEDIATE" in hdreg.h,
> > correct?
>
> Correct.
>
> > > int fd;
> > >
> > > if (argc < 2) {
> > > printf("%s \n", argv[0]);
> > > return 1;
> > > }
> > >
> > > fd = open(argv[1], O_RDONLY);
> >
> > Hmm, don't I need to actually have *write* access
> for sending an ioctl?
>
> No, but you need CAP_SYS_RAWIO capability. So run it
> as root.
>
> > > if (fd == -1) {
> > > perror("open");
> > > return 1;
> > > }
> > >
> > > if (ioctl(fd, HDIO_DRIVE_CMD, cmd))
> > > perror("ioctl");
> > >
> > > close(fd);
> > > return 0;
> > > }
> >
> > I will give it another try, after clarifying the
> above questions - maybe
> > there is a command that will perform the desired
> task. If not, I guess
> > we're back at snooping what the Windows driver
> does here...
>
> I'm not aware of a generally specificed command,
> it's likely that the
> ibm drive has a vendor specific one. Or that one of
> the idle commands
> can be configured to park the drive. Or... I'm not
> sure you'll find
> anything interesting in the windows driver, I would
> imagine that the
> user app is the one issuing the ide command (like
> the linux equiv would
> as well).
>
> --
> Jens Axboe
>
>
>
>
---
> SF.Net email is sponsored by: Discover Easy Linux
> Migration Strategies
> from IBM. Find simple to follow Roadmaps,
> straightforward articles,
> informative Webcasts and more! Get everything you
> need to get up to
> speed, fast.
>
http://ads.osdn.com/?ad_id=7477_id=16492=click
> ___
> Hdaps-devel mailing list
> [EMAIL PROTECTED]
>
https://lists.sourceforge.net/lists/listinfo/hdaps-devel
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
We could put it in userspace, but if the system is swapping like mad, can we still get a critical response if this remains in userspace fully? Someone mentioned we should use a kernel thread(s) to handle stopping all I/O so we can safely park heads. Shawn. --- Jens Axboe <[EMAIL PROTECTED]> wrote: > On Mon, Jul 04 2005, Lenz Grimmer wrote: > > > I'll be working on adding sysfs stuff to it > tomorrow so it's generally > > > useful (at least for monitoring things - not yet > for parking disk > > > heads). > > > > Maybe there is some kind of all-purpose ATA > command that instructs the > > disk drive to park the heads? Jens, could you give > us a hint on how a > > userspace application would do that? > > Dunno if there's something that explicitly only > parks the head, the best > option is probably to issue a STANDBY_NOW command. > You can test this > with hdparm -y. > > Generel observation on this driver - why isn't it > just contained in user > space? You need to do the monitoring and sending of > ide commands from > there anyways, I don't see the point of putting it > in the kernel. > > -- > Jens Axboe > > > > --- > SF.Net email is sponsored by: Discover Easy Linux > Migration Strategies > from IBM. Find simple to follow Roadmaps, > straightforward articles, > informative Webcasts and more! Get everything you > need to get up to > speed, fast. > http://ads.osdn.com/?ad_id=7477_id=16492=click > ___ > Hdaps-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hdaps-devel > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
We could put it in userspace, but if the system is swapping like mad, can we still get a critical response if this remains in userspace fully? Someone mentioned we should use a kernel thread(s) to handle stopping all I/O so we can safely park heads. Shawn. --- Jens Axboe [EMAIL PROTECTED] wrote: On Mon, Jul 04 2005, Lenz Grimmer wrote: I'll be working on adding sysfs stuff to it tomorrow so it's generally useful (at least for monitoring things - not yet for parking disk heads). Maybe there is some kind of all-purpose ATA command that instructs the disk drive to park the heads? Jens, could you give us a hint on how a userspace application would do that? Dunno if there's something that explicitly only parks the head, the best option is probably to issue a STANDBY_NOW command. You can test this with hdparm -y. Generel observation on this driver - why isn't it just contained in user space? You need to do the monitoring and sending of ide commands from there anyways, I don't see the point of putting it in the kernel. -- Jens Axboe --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Hdaps-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hdaps-devel - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Hdaps-devel] Re: IBM HDAPS things are looking up
From what I'm told its not specific to hard disk, you
can put any laptop HD and it will work the same (?).
Shawn.
--- Jens Axboe [EMAIL PROTECTED] wrote:
On Mon, Jul 04 2005, Lenz Grimmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jens!
Thanks for the sample code. I've trimmed the
recipient list a bit...
Jens Axboe wrote:
Perhaps the IDLE or IDLEIMMEDIATE commands imply
a head parking, that
would make sense. As you say, you can hear a
drive parking its head.
Here's a test case, it doesn't sound like it's
parking the hard here.
Not here either, but let me check, if I understand
this correctly:
#include stdio.h
#include unistd.h
#include fcntl.h
#include sys/ioctl.h
#include linux/hdreg.h
int main(int argc, char *argv[])
{
char cmd[4] = { 0xe1, 0, 0, 0 };
The 0xe1 in here is what is defined as
WIN_IDLEIMMEDIATE in hdreg.h,
correct?
Correct.
int fd;
if (argc 2) {
printf(%s dev\n, argv[0]);
return 1;
}
fd = open(argv[1], O_RDONLY);
Hmm, don't I need to actually have *write* access
for sending an ioctl?
No, but you need CAP_SYS_RAWIO capability. So run it
as root.
if (fd == -1) {
perror(open);
return 1;
}
if (ioctl(fd, HDIO_DRIVE_CMD, cmd))
perror(ioctl);
close(fd);
return 0;
}
I will give it another try, after clarifying the
above questions - maybe
there is a command that will perform the desired
task. If not, I guess
we're back at snooping what the Windows driver
does here...
I'm not aware of a generally specificed command,
it's likely that the
ibm drive has a vendor specific one. Or that one of
the idle commands
can be configured to park the drive. Or... I'm not
sure you'll find
anything interesting in the windows driver, I would
imagine that the
user app is the one issuing the ide command (like
the linux equiv would
as well).
--
Jens Axboe
---
SF.Net email is sponsored by: Discover Easy Linux
Migration Strategies
from IBM. Find simple to follow Roadmaps,
straightforward articles,
informative Webcasts and more! Get everything you
need to get up to
speed, fast.
http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click
___
Hdaps-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hdaps-devel
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Linux support for IBM ThinkPad Disk shock prevention update...
Has anyone started on such a project or would like to? We just need to figure out to get the specs from IBM I think such support would be good. Shawn. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.12-rc2][panic][NET] qdisc_restart - When loading ipw2200 driver - not mangled
Here's the dmesg/panic dump: Any problems with the Network scheduling in 2.6.12-rc2? [4294667.296000] Linux version 2.6.12-rc2 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050319 (prerelease)) #1 Wed Apr 13 11:38:19 EDT 2005 [4294667.296000] BIOS-provided physical RAM map: [4294667.296000] BIOS-e820: - 0009f000 (usable) [4294667.296000] BIOS-e820: 0009f000 - 000a (reserved) [4294667.296000] BIOS-e820: 000dc000 - 0010 (reserved) [4294667.296000] BIOS-e820: 0010 - 3ff6 (usable) [4294667.296000] BIOS-e820: 3ff6 - 3ff77000 (ACPI data) [4294667.296000] BIOS-e820: 3ff77000 - 3ff79000 (ACPI NVS) [4294667.296000] BIOS-e820: 3ff8 - 4000 (reserved) [4294667.296000] BIOS-e820: ff80 - 0001 (reserved) [4294667.296000] 127MB HIGHMEM available. [4294667.296000] 896MB LOWMEM available. [4294667.296000] DMI present. [4294667.296000] ACPI: PM-Timer IO Port: 0x1008 [4294667.296000] Allocating PCI resources starting at 4000 (gap: 4000:bf80) [4294667.296000] Built 1 zonelists [4294667.296000] Kernel command line: root=/dev/hda1 ro acpi_sleep=s3_bios hdc=ide-cd lapic [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/00:0D:60:3C:3A:3F [4294667.296000] ide_setup: hdc=ide-cd [4294667.296000] netconsole: local port 6665 [4294667.296000] netconsole: local IP 172.25.244.212 [4294667.296000] netconsole: interface eth0 [4294667.296000] netconsole: remote port 9353 [4294667.296000] netconsole: remote IP 172.25.244.222 [4294667.296000] netconsole: remote ethernet address 00:0d:60:3c:3a:3f [4294667.296000] Local APIC disabled by BIOS -- reenabling. [4294667.296000] Found and enabled local APIC! [4294667.296000] Initializing CPU#0 [4294667.296000] CPU 0 irqstacks, hard=c060a000 soft=c0609000 [4294667.296000] PID hash table entries: 4096 (order: 12, 65536 bytes) [4294667.296000] Detected 1798.930 MHz processor. [4294667.296000] Using pmtmr for high-res timesource [4294667.296000] Console: colour VGA+ 80x25 [4294670.127000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [4294670.127000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [4294670.16] Memory: 1032876k/1047936k available (3693k kernel code, 14480k reserved, 1200k data, 236k init, 130432k highmem) [4294670.16] Checking if this processor honours the WP bit even in supervisor mode... Ok. [4294670.183000] Mount-cache hash table entries: 512 [4294670.183000] CPU: L1 I cache: 32K, L1 D cache: 32K [4294670.183000] CPU: L2 cache: 2048K [4294670.183000] Intel machine check architecture supported. [4294670.183000] Intel machine check reporting enabled on CPU#0. [4294670.183000] CPU: Intel(R) Pentium(R) M processor 1.80GHz stepping 06 [4294670.183000] Enabling fast FPU save and restore... done. [4294670.183000] Enabling unmasked SIMD FPU exception support... done. [4294670.183000] Checking 'hlt' instruction... OK. [4294670.187000] tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired [4294670.399000] Parsing all Control Methods:.. .. ... [4294670.869000] Table [DSDT](id F005) - 1342 Objects with 64 Devices 403 Methods 19 Regions [4294670.869000] Parsing all Control Methods:. [4294670.87] Table [SSDT](id F003) - 1 Objects with 0 Devices 1 Methods 0 Regions [4294670.87] ACPI Namespace successfully loaded at root c0632620 [4294670.87] ACPI: setting ELCR to 0200 (from 0e28) [4294670.88] evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful [4294670.982000] NET: Registered protocol family 16 [4294670.983000] PCI: PCI BIOS revision 2.10 entry at 0xfd8d6, last bus=8 [4294670.983000] PCI: Using configuration type 1 [4294670.983000] mtrr: v2.0 (20020519) [4294670.991000] ACPI: Subsystem revision 20050309 [4294671.006000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9 [4294671.006000] evgpeblk-0987 [06] ev_create_gpe_block : Found 7 Wake, Enabled 0 Runtime GPEs in this block [4294671.007000] ACPI: Found ECDT [4294671.017000] Completing Region/Field/Buffer/Package initialization:.. .. [4294671.249000] Initialized 18/19 Regions 123/123 Fields 72/72 Buffers 39/46 Packages (1352 nodes) [4294671.249000] Executing all Device _STA and_INI
[2.6.12-rc2][panic][NET] qdisc_restart - When loading ipw2200 driver
Here's the dmesg/panic dump: Any problems with the Network scheduling in 2.6.12-rc2? [4294667.296000] Linux version 2.6.12-rc2 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050319 (prerelease)) #1 Wed Apr 13 11:38:19 EDT 2005 [4294667.296000] BIOS-provided physical RAM map: [4294667.296000] BIOS-e820: - 0009f000 (usable) [4294667.296000] BIOS-e820: 0009f000 - 000a (reserved) [4294667.296000] BIOS-e820: 000dc000 - 0010 (reserved) [4294667.296000] BIOS-e820: 0010 - 3ff6 (usable) [4294667.296000] BIOS-e820: 3ff6 - 3ff77000 (ACPI data) [4294667.296000] BIOS-e820: 3ff77000 - 3ff79000 (ACPI NVS) [4294667.296000] BIOS-e820: 3ff8 - 4000 (reserved) [4294667.296000] BIOS-e820: ff80 - 0001 (reserved) [4294667.296000] 127MB HIGHMEM available. [4294667.296000] 896MB LOWMEM available. [4294667.296000] DMI present. [4294667.296000] ACPI: PM-Timer IO Port: 0x1008 [4294667.296000] Allocating PCI resources starting at 4000 (gap: 4000:bf80) [4294667.296000] Built 1 zonelists [4294667.296000] Kernel command line: root=/dev/hda1 ro acpi_sleep=s3_bios hdc=ide-cd lapic [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/00:0D:60:3C:3A:3F [4294667.296000] ide_setup: hdc=ide-cd [4294667.296000] netconsole: local port 6665 [4294667.296000] netconsole: local IP 172.25.244.212 [4294667.296000] netconsole: interface eth0 [4294667.296000] netconsole: remote port 9353 [4294667.296000] netconsole: remote IP 172.25.244.222 [4294667.296000] netconsole: remote ethernet address 00:0d:60:3c:3a:3f [4294667.296000] Local APIC disabled by BIOS -- reenabling. [4294667.296000] Found and enabled local APIC! [4294667.296000] Initializing CPU#0 [4294667.296000] CPU 0 irqstacks, hard=c060a000 soft=c0609000 [4294667.296000] PID hash table entries: 4096 (order: 12, 65536 bytes) [4294667.296000] Detected 1798.930 MHz processor. [4294667.296000] Using pmtmr for high-res timesource [4294667.296000] Console: colour VGA+ 80x25 [4294670.127000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [4294670.127000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [4294670.16] Memory: 1032876k/1047936k available (3693k kernel code, 14480k reserved, 1200k data, 236k init, 130432k highmem) [4294670.16] Checking if this processor honours the WP bit even in supervisor mode... Ok. [4294670.183000] Mount-cache hash table entries: 512 [4294670.183000] CPU: L1 I cache: 32K, L1 D cache: 32K [4294670.183000] CPU: L2 cache: 2048K [4294670.183000] Intel machine check architecture supported. [4294670.183000] Intel machine check reporting enabled on CPU#0. [4294670.183000] CPU: Intel(R) Pentium(R) M processor 1.80GHz stepping 06 [4294670.183000] Enabling fast FPU save and restore... done. [4294670.183000] Enabling unmasked SIMD FPU exception support... done. [4294670.183000] Checking 'hlt' instruction... OK. [4294670.187000] tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired [4294670.399000] Parsing all Control Methods:... [4294670.869000] Table [DSDT](id F005) - 1342 Objects with 64 Devices 403 Methods 19 Regions [4294670.869000] Parsing all Control Methods:. [4294670.87] Table [SSDT](id F003) - 1 Objects with 0 Devices 1 Methods 0 Regions [4294670.87] ACPI Namespace successfully loaded at root c0632620 [4294670.87] ACPI: setting ELCR to 0200 (from 0e28) [4294670.88] evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful [4294670.982000] NET: Registered protocol family 16 [4294670.983000] PCI: PCI BIOS revision 2.10 entry at 0xfd8d6, last bus=8 [4294670.983000] PCI: Using configuration type 1 [4294670.983000] mtrr: v2.0 (20020519) [4294670.991000] ACPI: Subsystem revision 20050309 [4294671.006000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9 [4294671.006000] evgpeblk-0987 [06] ev_create_gpe_block : Found 7 Wake, Enabled 0 Runtime GPEs in this block [4294671.007000] ACPI: Found ECDT [4294671.017000] Completing Region/Field/Buffer/Package initialization: [4294671.249000] Initialized 18/19 Regions 123/123 Fields 72/72 Buffers 39/46 Packages (1352 nodes) [4294671.249000] Executing all Device _STA and_INI
[2.6.12-rc2][panic][NET] qdisc_restart - When loading ipw2200 driver
Here's the dmesg/panic dump: Any problems with the Network scheduling in 2.6.12-rc2? [4294667.296000] Linux version 2.6.12-rc2 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050319 (prerelease)) #1 Wed Apr 13 11:38:19 EDT 2005 [4294667.296000] BIOS-provided physical RAM map: [4294667.296000] BIOS-e820: - 0009f000 (usable) [4294667.296000] BIOS-e820: 0009f000 - 000a (reserved) [4294667.296000] BIOS-e820: 000dc000 - 0010 (reserved) [4294667.296000] BIOS-e820: 0010 - 3ff6 (usable) [4294667.296000] BIOS-e820: 3ff6 - 3ff77000 (ACPI data) [4294667.296000] BIOS-e820: 3ff77000 - 3ff79000 (ACPI NVS) [4294667.296000] BIOS-e820: 3ff8 - 4000 (reserved) [4294667.296000] BIOS-e820: ff80 - 0001 (reserved) [4294667.296000] 127MB HIGHMEM available. [4294667.296000] 896MB LOWMEM available. [4294667.296000] DMI present. [4294667.296000] ACPI: PM-Timer IO Port: 0x1008 [4294667.296000] Allocating PCI resources starting at 4000 (gap: 4000:bf80) [4294667.296000] Built 1 zonelists [4294667.296000] Kernel command line: root=/dev/hda1 ro acpi_sleep=s3_bios hdc=ide-cd lapic [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/00:0D:60:3C:3A:3F [4294667.296000] ide_setup: hdc=ide-cd [4294667.296000] netconsole: local port 6665 [4294667.296000] netconsole: local IP 172.25.244.212 [4294667.296000] netconsole: interface eth0 [4294667.296000] netconsole: remote port 9353 [4294667.296000] netconsole: remote IP 172.25.244.222 [4294667.296000] netconsole: remote ethernet address 00:0d:60:3c:3a:3f [4294667.296000] Local APIC disabled by BIOS -- reenabling. [4294667.296000] Found and enabled local APIC! [4294667.296000] Initializing CPU#0 [4294667.296000] CPU 0 irqstacks, hard=c060a000 soft=c0609000 [4294667.296000] PID hash table entries: 4096 (order: 12, 65536 bytes) [4294667.296000] Detected 1798.930 MHz processor. [4294667.296000] Using pmtmr for high-res timesource [4294667.296000] Console: colour VGA+ 80x25 [4294670.127000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [4294670.127000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [4294670.16] Memory: 1032876k/1047936k available (3693k kernel code, 14480k reserved, 1200k data, 236k init, 130432k highmem) [4294670.16] Checking if this processor honours the WP bit even in supervisor mode... Ok. [4294670.183000] Mount-cache hash table entries: 512 [4294670.183000] CPU: L1 I cache: 32K, L1 D cache: 32K [4294670.183000] CPU: L2 cache: 2048K [4294670.183000] Intel machine check architecture supported. [4294670.183000] Intel machine check reporting enabled on CPU#0. [4294670.183000] CPU: Intel(R) Pentium(R) M processor 1.80GHz stepping 06 [4294670.183000] Enabling fast FPU save and restore... done. [4294670.183000] Enabling unmasked SIMD FPU exception support... done. [4294670.183000] Checking 'hlt' instruction... OK. [4294670.187000] tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired [4294670.399000] Parsing all Control Methods:... [4294670.869000] Table [DSDT](id F005) - 1342 Objects with 64 Devices 403 Methods 19 Regions [4294670.869000] Parsing all Control Methods:. [4294670.87] Table [SSDT](id F003) - 1 Objects with 0 Devices 1 Methods 0 Regions [4294670.87] ACPI Namespace successfully loaded at root c0632620 [4294670.87] ACPI: setting ELCR to 0200 (from 0e28) [4294670.88] evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful [4294670.982000] NET: Registered protocol family 16 [4294670.983000] PCI: PCI BIOS revision 2.10 entry at 0xfd8d6, last bus=8 [4294670.983000] PCI: Using configuration type 1 [4294670.983000] mtrr: v2.0 (20020519) [4294670.991000] ACPI: Subsystem revision 20050309 [4294671.006000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9 [4294671.006000] evgpeblk-0987 [06] ev_create_gpe_block : Found 7 Wake, Enabled 0 Runtime GPEs in this block [4294671.007000] ACPI: Found ECDT [4294671.017000] Completing Region/Field/Buffer/Package initialization: [4294671.249000] Initialized 18/19 Regions 123/123 Fields 72/72 Buffers 39/46 Packages (1352 nodes) [4294671.249000] Executing all Device _STA and_INI
[2.6.12-rc2][panic][NET] qdisc_restart - When loading ipw2200 driver - not mangled
Here's the dmesg/panic dump: Any problems with the Network scheduling in 2.6.12-rc2? [4294667.296000] Linux version 2.6.12-rc2 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050319 (prerelease)) #1 Wed Apr 13 11:38:19 EDT 2005 [4294667.296000] BIOS-provided physical RAM map: [4294667.296000] BIOS-e820: - 0009f000 (usable) [4294667.296000] BIOS-e820: 0009f000 - 000a (reserved) [4294667.296000] BIOS-e820: 000dc000 - 0010 (reserved) [4294667.296000] BIOS-e820: 0010 - 3ff6 (usable) [4294667.296000] BIOS-e820: 3ff6 - 3ff77000 (ACPI data) [4294667.296000] BIOS-e820: 3ff77000 - 3ff79000 (ACPI NVS) [4294667.296000] BIOS-e820: 3ff8 - 4000 (reserved) [4294667.296000] BIOS-e820: ff80 - 0001 (reserved) [4294667.296000] 127MB HIGHMEM available. [4294667.296000] 896MB LOWMEM available. [4294667.296000] DMI present. [4294667.296000] ACPI: PM-Timer IO Port: 0x1008 [4294667.296000] Allocating PCI resources starting at 4000 (gap: 4000:bf80) [4294667.296000] Built 1 zonelists [4294667.296000] Kernel command line: root=/dev/hda1 ro acpi_sleep=s3_bios hdc=ide-cd lapic [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/00:0D:60:3C:3A:3F [4294667.296000] ide_setup: hdc=ide-cd [4294667.296000] netconsole: local port 6665 [4294667.296000] netconsole: local IP 172.25.244.212 [4294667.296000] netconsole: interface eth0 [4294667.296000] netconsole: remote port 9353 [4294667.296000] netconsole: remote IP 172.25.244.222 [4294667.296000] netconsole: remote ethernet address 00:0d:60:3c:3a:3f [4294667.296000] Local APIC disabled by BIOS -- reenabling. [4294667.296000] Found and enabled local APIC! [4294667.296000] Initializing CPU#0 [4294667.296000] CPU 0 irqstacks, hard=c060a000 soft=c0609000 [4294667.296000] PID hash table entries: 4096 (order: 12, 65536 bytes) [4294667.296000] Detected 1798.930 MHz processor. [4294667.296000] Using pmtmr for high-res timesource [4294667.296000] Console: colour VGA+ 80x25 [4294670.127000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [4294670.127000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [4294670.16] Memory: 1032876k/1047936k available (3693k kernel code, 14480k reserved, 1200k data, 236k init, 130432k highmem) [4294670.16] Checking if this processor honours the WP bit even in supervisor mode... Ok. [4294670.183000] Mount-cache hash table entries: 512 [4294670.183000] CPU: L1 I cache: 32K, L1 D cache: 32K [4294670.183000] CPU: L2 cache: 2048K [4294670.183000] Intel machine check architecture supported. [4294670.183000] Intel machine check reporting enabled on CPU#0. [4294670.183000] CPU: Intel(R) Pentium(R) M processor 1.80GHz stepping 06 [4294670.183000] Enabling fast FPU save and restore... done. [4294670.183000] Enabling unmasked SIMD FPU exception support... done. [4294670.183000] Checking 'hlt' instruction... OK. [4294670.187000] tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired [4294670.399000] Parsing all Control Methods:.. .. ... [4294670.869000] Table [DSDT](id F005) - 1342 Objects with 64 Devices 403 Methods 19 Regions [4294670.869000] Parsing all Control Methods:. [4294670.87] Table [SSDT](id F003) - 1 Objects with 0 Devices 1 Methods 0 Regions [4294670.87] ACPI Namespace successfully loaded at root c0632620 [4294670.87] ACPI: setting ELCR to 0200 (from 0e28) [4294670.88] evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful [4294670.982000] NET: Registered protocol family 16 [4294670.983000] PCI: PCI BIOS revision 2.10 entry at 0xfd8d6, last bus=8 [4294670.983000] PCI: Using configuration type 1 [4294670.983000] mtrr: v2.0 (20020519) [4294670.991000] ACPI: Subsystem revision 20050309 [4294671.006000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9 [4294671.006000] evgpeblk-0987 [06] ev_create_gpe_block : Found 7 Wake, Enabled 0 Runtime GPEs in this block [4294671.007000] ACPI: Found ECDT [4294671.017000] Completing Region/Field/Buffer/Package initialization:.. .. [4294671.249000] Initialized 18/19 Regions 123/123 Fields 72/72 Buffers 39/46 Packages (1352 nodes) [4294671.249000] Executing all Device _STA and_INI
Linux support for IBM ThinkPad Disk shock prevention update...
Has anyone started on such a project or would like to? We just need to figure out to get the specs from IBM I think such support would be good. Shawn. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Policy question (was Re: [2.6.12-rc1][ACPI][suspend] /proc/acpi/sleep vs /sys/power/state issue - 'standby' on a laptop)
Well, of course. When I get around to figuring out the best way to do this. Since I don't want to bloat up sysfs ACPI stuff just to check if the echoed value is a number or string. We can just gradually phase it out by just marking it DEPRECATED and keep it ON in the Kbuild file so nobody looses the functionality until then. I'm thinking 2 years but some say thats too long :) Now that I look at it, I don't need to put it into a CONFIG option as its already a module :-) even better. Shawn. On April 11, 2005 20:09, Rob Landley wrote: > On Wednesday 06 April 2005 05:22 pm, Shawn Starr wrote: > > --- Pavel Machek <[EMAIL PROTECTED]> wrote: > > > Hi! > > > > > > > So nobody minds if I make this into a CONFIG > > > > > > option marked as Deprecated? :) > > > > > > Actually it should probably go through > > > > > > Documentation/feature-removal-schedule.txt > > > > > > ...and give it *long* timeout, since it is API > > > change. > > > Pavel > > Shouldn't all deprecated features be in feature-removal-schedule.txt? > > There are four entries in feature-removal-schedule in 2.6.12-rc2, but > `find . -name "Kconfig" | xargs grep -i deprecated` finds eight entries. > (And there's more if the grep -i is for "obsolete" instead...) > > Just wondering... > > Rob - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] [2.6.12-rc2][suspend] Suspending Thinkpad: drive bay light in S3 mode stays on
Sure, I suppose you can, but most suspend tools just echo stuff to /sys (or still /proc/acpi/sleep) which makes it harder to script it. Besides, when a laptop goes into suspend to RAM there should be no extra power on except a Moon or some other icon. That said, the ACPI thinkpad extras was designed to do all of this so why shouldn't the driver do S3 suspend if it hooks into it already? Shawn. --- Matthew Garrett <[EMAIL PROTECTED]> wrote: > On Mon, 2005-04-11 at 16:03 -0400, Shawn Starr > wrote: > > I notice in Linux and in XP the drive bay light > > remains on while the laptop is in suspend-to-RAM. > I > > know the ACPI thinkpad extras added to the kernel > > recently can turn this off. I wonder if we can/or > need > > to write hooks to turn the light off so to > conserve > > power when we're in S3 > > Just disable it in your suspend script. There's no > reason to push that > sort of policy into the kernel. > > -- > Matthew Garrett | [EMAIL PROTECTED] > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.12-rc2][suspend] Suspending Thinkpad: drive bay light in S3 mode stays on
I notice in Linux and in XP the drive bay light remains on while the laptop is in suspend-to-RAM. I know the ACPI thinkpad extras added to the kernel recently can turn this off. I wonder if we can/or need to write hooks to turn the light off so to conserve power when we're in S3 Thoughts? Shawn. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.12-rc2][suspend] resume occuring twice before suspend to suspend-to-disk
I've noticed that when I do a suspend to disk. The machine suspends PCI devices once (I notice this because the ipw2200 wireless card shows its suspending, then it locks/parks the HD heads, but then all PCI devices are woken up and resume. The HD spins up and then dumps memory contents to swap partition, then it suspends all devices again? :) Is this the right behaviour? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.12-rc2][suspend] resume occuring twice before suspend to suspend-to-disk
I've noticed that when I do a suspend to disk. The machine suspends PCI devices once (I notice this because the ipw2200 wireless card shows its suspending, then it locks/parks the HD heads, but then all PCI devices are woken up and resume. The HD spins up and then dumps memory contents to swap partition, then it suspends all devices again? :) Is this the right behaviour? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.12-rc2][suspend] Suspending Thinkpad: drive bay light in S3 mode stays on
I notice in Linux and in XP the drive bay light remains on while the laptop is in suspend-to-RAM. I know the ACPI thinkpad extras added to the kernel recently can turn this off. I wonder if we can/or need to write hooks to turn the light off so to conserve power when we're in S3 Thoughts? Shawn. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
