Linus GIT 3.18.0-rc3: WARNING: CPU: 0 PID: 1063 at mm/vmalloc.c:1440 __vunmap+0x5c/0xc8()
Not sure if this is a kernel issue or a Linux distribution issue (Ubuntu 15.04 dev tree). [4.439057] WARNING: CPU: 0 PID: 1063 at mm/vmalloc.c:1440 __vunmap+0x5c/0xc8() [4.439059] Trying to vfree() bad address (c0109cf7) [4.439060] Modules linked in: cdrom [4.439066] CPU: 0 PID: 1063 Comm: systemd-udevd Not tainted 3.18.0-rc3 #29 [4.439068] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [4.439069] 0009 8800d561bcc8 81504679 81074b27 [4.439073] 8800d561bd18 8800d561bd08 81035306 880212f292e0 [4.439076] 810e4522 c0109cf7 c0109cf7 0001 [4.439080] Call Trace: [4.439085] [] dump_stack+0x4f/0x7c [4.439091] [] ? console_unlock+0x35a/0x389 [4.439094] [] warn_slowpath_common+0x77/0x91 [4.439098] [] ? __vunmap+0x5c/0xc8 [4.439101] [] warn_slowpath_fmt+0x41/0x43 [4.439104] [] ? trace_hardirqs_on+0xd/0xf [4.439108] [] __vunmap+0x5c/0xc8 [4.439112] [] vfree+0x80/0x85 [4.439117] [] module_free+0xc/0x14 [4.439120] [] load_module+0x1036/0x14b9 [4.439124] [] SyS_finit_module+0x59/0x66 [4.439129] [] tracesys_phase2+0xd4/0xd9 [4.439131] ---[ end trace 4dfcc2294de9043f ]--- [4.440765] WARNING: CPU: 0 PID: 1063 at mm/vmalloc.c:1440 __vunmap+0x5c/0xc8() [4.440768] Trying to vfree() bad address (c011530e) [4.440770] Modules linked in: sr_mod cdrom [4.440779] CPU: 0 PID: 1063 Comm: systemd-udevd Tainted: G W 3.18.0-rc3 #29 [4.440782] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [4.440785] 0009 8800d561bcc8 81504679 81074b27 [4.440791] 8800d561bd18 8800d561bd08 81035306 880212f292e0 [4.440797] 810e4522 c011530e c011530e 0001 [4.440804] Call Trace: [4.440811] [] dump_stack+0x4f/0x7c [4.440817] [] ? console_unlock+0x35a/0x389 [4.440823] [] warn_slowpath_common+0x77/0x91 [4.440829] [] ? __vunmap+0x5c/0xc8 [4.440835] [] warn_slowpath_fmt+0x41/0x43 [4.440840] [] ? trace_hardirqs_on+0xd/0xf [4.440845] [] __vunmap+0x5c/0xc8 [4.440852] [] vfree+0x80/0x85 [4.440858] [] module_free+0xc/0x14 [4.440864] [] load_module+0x1036/0x14b9 [4.440871] [] SyS_finit_module+0x59/0x66 [4.440877] [] tracesys_phase2+0xd4/0xd9 [4.440881] ---[ end trace 4dfcc2294de90440 ]--- Gnu C 4.9.1 Gnu make 4.0 binutils 2.24.90.20141023 util-linux 2.25.2 mount debug module-init-tools 18 e2fsprogs 1.42.12 pcmciautils018 PPP2.4.5 Linux C Library2.19 Dynamic linker (ldd) 2.19 Procps 3.3.9 Net-tools 1.60 Kbd1.15.5 Sh-utils 8.23 Modules Loaded bnep rfcomm ipv6 ecb hid_multitouch uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common usbhid videodev media ath3k btusb bluetooth ath9k ath9k_common ath9k_hw ath mac80211 r8169 mii snd_hda_codec_realtek snd_hda_codec_generic cfg80211 snd_hda_codec_hdmi dell_wmi dell_laptop rfkill intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp microcode snd_soc_rt5640 snd_hda_intel snd_hda_controller ehci_pci snd_hda_codec lpc_ich snd_soc_rl6231 snd_soc_core ehci_hcd snd_hwdep snd_compress snd_pcm_dmaengine shpchp snd_pcm_oss snd_mixer_oss wmi snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_seq_device snd_timer sdhci_acpi sdhci snd mmc_core mei_me snd_soc_sst_acpi soundcore ac mei i2c_hid xhci_pci xhci_hcd fuse sr_mod cdrom # # Automatically generated file; DO NOT EDIT. # Linux/x86 3.18.0-rc3 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_HAVE_INTEL_TXT=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9
Re: Linus GIT 3.18.0-rc2+: INFO: suspicious RCU usage - kernel/sched/core.c:7449 suspicious rcu_dereference_check() usage!
Hello,
I tested the patch and it appears to fix the problem.
Thanks!
Miles
On Sat, Nov 1, 2014 at 7:46 PM, Wanpeng Li wrote:
> How about try this patch, https://lkml.org/lkml/2014/10/28/41
> On 14/11/2 上午4:45, Miles Lane wrote:
>>
>> [0.763902] [ INFO: suspicious RCU usage. ]
>> [0.763904] 3.18.0-rc2+ #25 Not tainted
>> [0.763906] ---
>> [0.763907] kernel/sched/core.c:7449 suspicious
>> rcu_dereference_check() usage!
>> [0.763908]
>> other info that might help us debug this:
>>
>> [0.763911]
>> rcu_scheduler_active = 1, debug_locks = 1
>> [0.763913] 2 locks held by swapper/0/0:
>> [0.763914] #0: (>pi_lock){..}, at: []
>> task_rq_lock+0x30/0xaa
>> [0.763923] #1: (>lock){-.}, at: []
>> task_rq_lock+0x52/0xaa
>> [0.763928]
>> stack backtrace:
>> [0.763930] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.18.0-rc2+ #25
>> [0.763932] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07
>> 11/14/2013
>> [0.763934] 0001 81a03cf8 814fdde5
>> 810723dc
>> [0.763937] 81a16580 81a03d28 8106312e
>> 88021387
>> [0.763940] 88021ea12780 8802138a
>> 81a03d88
>> [0.763943] Call Trace:
>> [0.763948] [] dump_stack+0x4f/0x7c
>> [0.763952] [] ? console_unlock+0x35a/0x389
>> [0.763957] [] lockdep_rcu_suspicious+0xfa/0x103
>> [0.763960] [] sched_move_task+0xda/0x17b
>> [0.763963] [] ? _raw_write_unlock_irq+0x28/0x48
>> [0.763966] [] cpu_cgroup_fork+0x9/0xb
>> [0.763970] [] cgroup_post_fork+0x8a/0x99
>> [0.763974] [] copy_process+0x17ca/0x1835
>> [0.763977] [] ? rest_init+0x130/0x130
>> [0.763981] [] do_fork+0x87/0x23d
>> [0.763983] [] ? free_reserved_area+0xf4/0x106
>> [0.763987] [] kernel_thread+0x21/0x23
>> [0.763990] [] rest_init+0x1e/0x130
>> [0.763994] [] start_kernel+0x434/0x441
>> [0.763997] [] x86_64_start_reservations+0x2a/0x2c
>> [0.763999] [] x86_64_start_kernel+0xc8/0xcc
>>
>> Gnu C 4.9.1
>> Gnu make 4.0
>> binutils 2.24.90.20141023
>> util-linux 2.25.2
>> mount debug
>> module-init-tools 18
>> e2fsprogs 1.42.12
>> pcmciautils018
>> PPP2.4.5
>> Linux C Library2.19
>> Dynamic linker (ldd) 2.19
>> Procps 3.3.9
>> Net-tools 1.60
>> Kbd1.15.5
>> Sh-utils 8.23
>> Modules Loaded rfcomm bnep ipv6 ecb uvcvideo videobuf2_vmalloc
>> videobuf2_memops videobuf2_core v4l2_common hid_multitouch videodev
>> usbhid media ath3k btusb bluetooth snd_hda_codec_realtek
>> snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl
>> x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp ath9k
>> dell_laptop ath9k_common ath9k_hw microcode snd_soc_rt5640
>> snd_soc_rl6231 ath snd_hda_intel snd_soc_core snd_hda_controller
>> mac80211 snd_hda_codec snd_compress snd_hwdep snd_pcm_dmaengine
>> cfg80211 snd_pcm_oss rfkill snd_mixer_oss snd_pcm snd_seq_dummy
>> snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq
>> snd_seq_device snd_soc_sst_acpi snd_timer i2c_hid snd soundcore
>> xhci_pci mei_me ehci_pci xhci_hcd shpchp ehci_hcd ac mei lpc_ich wmi
>> fuse sr_mod cdrom r8169 mii sdhci_acpi sdhci mmc_core
>>
>> #
>> # Automatically generated file; DO NOT EDIT.
>> # Linux/x86 3.18.0-rc2 Kernel Configuration
>> #
>> CONFIG_64BIT=y
>> CONFIG_X86_64=y
>> CONFIG_X86=y
>> CONFIG_INSTRUCTION_DECODER=y
>> CONFIG_OUTPUT_FORMAT="elf64-x86-64"
>> CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
>> CONFIG_LOCKDEP_SUPPORT=y
>> CONFIG_STACKTRACE_SUPPORT=y
>> CONFIG_HAVE_LATENCYTOP_SUPPORT=y
>> CONFIG_MMU=y
>> CONFIG_NEED_DMA_MAP_STATE=y
>> CONFIG_NEED_SG_DMA_LENGTH=y
>> CONFIG_GENERIC_ISA_DMA=y
>> CONFIG_GENERIC_BUG=y
>> CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
>> CONFIG_GENERIC_HWEIGHT=y
>> CONFIG_ARCH_MAY_HAVE_PC_FDC=y
>> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
>> CONFIG_GENERIC_CALIBRATE_DELAY=y
>> CONFIG_ARCH_HAS_CPU_RELAX=y
>> CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
>> CONFIG_HAVE_SETUP_PER_CPU_AREA=y
>> CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
>> CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
>> CONFIG_ARCH_HI
Re: Linus GIT 3.18.0-rc2+: INFO: suspicious RCU usage - kernel/sched/core.c:7449 suspicious rcu_dereference_check() usage!
Hello,
I tested the patch and it appears to fix the problem.
Thanks!
Miles
On Sat, Nov 1, 2014 at 7:46 PM, Wanpeng Li kernel...@gmail.com wrote:
How about try this patch, https://lkml.org/lkml/2014/10/28/41
On 14/11/2 上午4:45, Miles Lane wrote:
[0.763902] [ INFO: suspicious RCU usage. ]
[0.763904] 3.18.0-rc2+ #25 Not tainted
[0.763906] ---
[0.763907] kernel/sched/core.c:7449 suspicious
rcu_dereference_check() usage!
[0.763908]
other info that might help us debug this:
[0.763911]
rcu_scheduler_active = 1, debug_locks = 1
[0.763913] 2 locks held by swapper/0/0:
[0.763914] #0: (p-pi_lock){..}, at: [8104fb23]
task_rq_lock+0x30/0xaa
[0.763923] #1: (rq-lock){-.}, at: [8104fb45]
task_rq_lock+0x52/0xaa
[0.763928]
stack backtrace:
[0.763930] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.18.0-rc2+ #25
[0.763932] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07
11/14/2013
[0.763934] 0001 81a03cf8 814fdde5
810723dc
[0.763937] 81a16580 81a03d28 8106312e
88021387
[0.763940] 88021ea12780 8802138a
81a03d88
[0.763943] Call Trace:
[0.763948] [814fdde5] dump_stack+0x4f/0x7c
[0.763952] [810723dc] ? console_unlock+0x35a/0x389
[0.763957] [8106312e] lockdep_rcu_suspicious+0xfa/0x103
[0.763960] [81055726] sched_move_task+0xda/0x17b
[0.763963] [815052c5] ? _raw_write_unlock_irq+0x28/0x48
[0.763966] [810557e4] cpu_cgroup_fork+0x9/0xb
[0.763970] [8109e8d7] cgroup_post_fork+0x8a/0x99
[0.763974] [81033625] copy_process+0x17ca/0x1835
[0.763977] [814f94bc] ? rest_init+0x130/0x130
[0.763981] [810337ea] do_fork+0x87/0x23d
[0.763983] [810b90fa] ? free_reserved_area+0xf4/0x106
[0.763987] [810339c1] kernel_thread+0x21/0x23
[0.763990] [814f93aa] rest_init+0x1e/0x130
[0.763994] [81aaae6c] start_kernel+0x434/0x441
[0.763997] [81aaa487] x86_64_start_reservations+0x2a/0x2c
[0.763999] [81aaa551] x86_64_start_kernel+0xc8/0xcc
Gnu C 4.9.1
Gnu make 4.0
binutils 2.24.90.20141023
util-linux 2.25.2
mount debug
module-init-tools 18
e2fsprogs 1.42.12
pcmciautils018
PPP2.4.5
Linux C Library2.19
Dynamic linker (ldd) 2.19
Procps 3.3.9
Net-tools 1.60
Kbd1.15.5
Sh-utils 8.23
Modules Loaded rfcomm bnep ipv6 ecb uvcvideo videobuf2_vmalloc
videobuf2_memops videobuf2_core v4l2_common hid_multitouch videodev
usbhid media ath3k btusb bluetooth snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl
x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp ath9k
dell_laptop ath9k_common ath9k_hw microcode snd_soc_rt5640
snd_soc_rl6231 ath snd_hda_intel snd_soc_core snd_hda_controller
mac80211 snd_hda_codec snd_compress snd_hwdep snd_pcm_dmaengine
cfg80211 snd_pcm_oss rfkill snd_mixer_oss snd_pcm snd_seq_dummy
snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq
snd_seq_device snd_soc_sst_acpi snd_timer i2c_hid snd soundcore
xhci_pci mei_me ehci_pci xhci_hcd shpchp ehci_hcd ac mei lpc_ich wmi
fuse sr_mod cdrom r8169 mii sdhci_acpi sdhci mmc_core
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 3.18.0-rc2 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT=elf64-x86-64
CONFIG_ARCH_DEFCONFIG=arch/x86/configs/x86_64_defconfig
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS=-fcall-saved-rdi -fcall-saved-rsi
-fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9
-fcall-saved-r10 -fcall-saved-r11
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DEFCONFIG_LIST=/lib/modules
Linus GIT 3.18.0-rc3: WARNING: CPU: 0 PID: 1063 at mm/vmalloc.c:1440 __vunmap+0x5c/0xc8()
Not sure if this is a kernel issue or a Linux distribution issue (Ubuntu 15.04 dev tree). [4.439057] WARNING: CPU: 0 PID: 1063 at mm/vmalloc.c:1440 __vunmap+0x5c/0xc8() [4.439059] Trying to vfree() bad address (c0109cf7) [4.439060] Modules linked in: cdrom [4.439066] CPU: 0 PID: 1063 Comm: systemd-udevd Not tainted 3.18.0-rc3 #29 [4.439068] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [4.439069] 0009 8800d561bcc8 81504679 81074b27 [4.439073] 8800d561bd18 8800d561bd08 81035306 880212f292e0 [4.439076] 810e4522 c0109cf7 c0109cf7 0001 [4.439080] Call Trace: [4.439085] [81504679] dump_stack+0x4f/0x7c [4.439091] [81074b27] ? console_unlock+0x35a/0x389 [4.439094] [81035306] warn_slowpath_common+0x77/0x91 [4.439098] [810e4522] ? __vunmap+0x5c/0xc8 [4.439101] [81035361] warn_slowpath_fmt+0x41/0x43 [4.439104] [810671ac] ? trace_hardirqs_on+0xd/0xf [4.439108] [810e4522] __vunmap+0x5c/0xc8 [4.439112] [810e4638] vfree+0x80/0x85 [4.439117] [810961b2] module_free+0xc/0x14 [4.439120] [81097e97] load_module+0x1036/0x14b9 [4.439124] [8109841e] SyS_finit_module+0x59/0x66 [4.439129] [8150c8e2] tracesys_phase2+0xd4/0xd9 [4.439131] ---[ end trace 4dfcc2294de9043f ]--- [4.440765] WARNING: CPU: 0 PID: 1063 at mm/vmalloc.c:1440 __vunmap+0x5c/0xc8() [4.440768] Trying to vfree() bad address (c011530e) [4.440770] Modules linked in: sr_mod cdrom [4.440779] CPU: 0 PID: 1063 Comm: systemd-udevd Tainted: G W 3.18.0-rc3 #29 [4.440782] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [4.440785] 0009 8800d561bcc8 81504679 81074b27 [4.440791] 8800d561bd18 8800d561bd08 81035306 880212f292e0 [4.440797] 810e4522 c011530e c011530e 0001 [4.440804] Call Trace: [4.440811] [81504679] dump_stack+0x4f/0x7c [4.440817] [81074b27] ? console_unlock+0x35a/0x389 [4.440823] [81035306] warn_slowpath_common+0x77/0x91 [4.440829] [810e4522] ? __vunmap+0x5c/0xc8 [4.440835] [81035361] warn_slowpath_fmt+0x41/0x43 [4.440840] [810671ac] ? trace_hardirqs_on+0xd/0xf [4.440845] [810e4522] __vunmap+0x5c/0xc8 [4.440852] [810e4638] vfree+0x80/0x85 [4.440858] [810961b2] module_free+0xc/0x14 [4.440864] [81097e97] load_module+0x1036/0x14b9 [4.440871] [8109841e] SyS_finit_module+0x59/0x66 [4.440877] [8150c8e2] tracesys_phase2+0xd4/0xd9 [4.440881] ---[ end trace 4dfcc2294de90440 ]--- Gnu C 4.9.1 Gnu make 4.0 binutils 2.24.90.20141023 util-linux 2.25.2 mount debug module-init-tools 18 e2fsprogs 1.42.12 pcmciautils018 PPP2.4.5 Linux C Library2.19 Dynamic linker (ldd) 2.19 Procps 3.3.9 Net-tools 1.60 Kbd1.15.5 Sh-utils 8.23 Modules Loaded bnep rfcomm ipv6 ecb hid_multitouch uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common usbhid videodev media ath3k btusb bluetooth ath9k ath9k_common ath9k_hw ath mac80211 r8169 mii snd_hda_codec_realtek snd_hda_codec_generic cfg80211 snd_hda_codec_hdmi dell_wmi dell_laptop rfkill intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp microcode snd_soc_rt5640 snd_hda_intel snd_hda_controller ehci_pci snd_hda_codec lpc_ich snd_soc_rl6231 snd_soc_core ehci_hcd snd_hwdep snd_compress snd_pcm_dmaengine shpchp snd_pcm_oss snd_mixer_oss wmi snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_seq_device snd_timer sdhci_acpi sdhci snd mmc_core mei_me snd_soc_sst_acpi soundcore ac mei i2c_hid xhci_pci xhci_hcd fuse sr_mod cdrom # # Automatically generated file; DO NOT EDIT. # Linux/x86 3.18.0-rc3 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT=elf64-x86-64 CONFIG_ARCH_DEFCONFIG=arch/x86/configs/x86_64_defconfig CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y
Linus GIT 3.18.0-rc2+ - BUG: unable to handle kernel paging request at ffff88021dc52000 - IP: [] scan_block+0x59/0x100
[ 69.271345] BUG: unable to handle kernel paging request at 88021dc52000 [ 69.271417] IP: [] scan_block+0x59/0x100 [ 69.271471] PGD 28d5067 PUD 28d8067 PMD 21fdf2067 PTE 80021dc52060 [ 69.271542] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 69.271597] Modules linked in: rfcomm ipv6 bnep ecb uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common hid_multitouch videodev media usbhid ath3k btusb bluetooth snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp dell_laptop microcode ath9k ath9k_common ath9k_hw ath mac80211 r8169 cfg80211 rfkill snd_soc_rt5640 snd_soc_rl6231 snd_hda_intel snd_soc_core snd_hda_controller snd_compress snd_hda_codec snd_pcm_dmaengine snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_soc_sst_acpi snd_seq_device snd_timer sdhci_acpi sdhci mmc_core xhci_pci snd i2c_hid mei_me soundcore ehci_pci lpc_ich mei xhci_hcd ehci_hcd shpchp wmi ac fuse sr_mod [ 69.272392] cdrom mii [ 69.272410] CPU: 0 PID: 1026 Comm: kmemleak Not tainted 3.18.0-rc2+ #26 [ 69.272471] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 69.272529] task: 880211d98000 ti: 8800d53b4000 task.ti: 8800d53b4000 [ 69.272588] RIP: 0010:[] [] scan_block+0x59/0x100 [ 69.272661] RSP: 0018:8800d53b7d78 EFLAGS: 00010046 [ 69.272704] RAX: RBX: 880214828000 RCX: [ 69.272769] RDX: 880214828000 RSI: 88021dc53000 RDI: 88021dc52000 [ 69.272832] RBP: 8800d53b7db8 R08: 0001 R09: 00406032 [ 69.272889] R10: R11: 0002 R12: 88021dc52000 [ 69.272945] R13: 88021dc52ff9 R14: 880214828000 R15: [ 69.273011] FS: () GS:88021da0() knlGS: [ 69.273075] CS: 0010 DS: ES: CR0: 80050033 [ 69.273122] CR2: 88021dc52000 CR3: 00020bcbe000 CR4: 001407f0 [ 69.273186] Stack: [ 69.273204] 8800d53b7db8 81507471 810f569d 880214828000 [ 69.273278] 88021ec0 880214828050 0292 88021dc53000 [ 69.273350] 8800d53b7df8 810f5672 880211d988b0 81a16580 [ 69.273425] Call Trace: [ 69.273452] [] ? _raw_spin_lock_irqsave+0x48/0x52 [ 69.273506] [] ? scan_gray_list+0xe2/0x15f [ 69.273561] [] scan_gray_list+0xb7/0x15f [ 69.273615] [] kmemleak_scan+0x294/0x45e [ 69.273662] [] ? kmemleak_write+0x354/0x354 [ 69.273711] [] kmemleak_scan_thread+0x82/0xa4 [ 69.273762] [] kthread+0xd6/0xde [ 69.273803] [] ? __kthread_parkme+0x62/0x62 [ 69.273856] [] ret_from_fork+0x7c/0xb0 [ 69.273901] [] ? __kthread_parkme+0x62/0x62 [ 69.273945] Code: 00 45 85 ff 74 18 31 d2 be 86 04 00 00 48 c7 c7 80 d5 7e 81 e8 34 bf f5 ff e8 ad e4 40 00 e8 b8 fb ff ff 85 c0 0f 85 98 00 00 00 <49> 8b 3c 24 be 01 00 00 00 e8 98 fc ff ff 48 85 c0 48 89 c3 74 [ 69.274266] RIP [] scan_block+0x59/0x100 [ 69.274317] RSP [ 69.274348] CR2: 88021dc52000 [ 69.281408] ---[ end trace 5cc9aa4cd3f6b3b6 ]--- [ 69.281412] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:41 [ 69.281414] in_atomic(): 1, irqs_disabled(): 1, pid: 1026, name: kmemleak [ 69.281415] INFO: lockdep is turned off. [ 69.281417] irq event stamp: 7294084 [ 69.281418] hardirqs last enabled at (7294083): [] _raw_spin_unlock_irqrestore+0x3a/0x5c [ 69.281424] hardirqs last disabled at (7294084): [] _raw_spin_lock_irqsave+0x1a/0x52 [ 69.281427] softirqs last enabled at (7294078): [] __do_softirq+0x221/0x27d [ 69.281431] softirqs last disabled at (7294059): [] irq_exit+0x59/0xdb [ 69.281434] Preemption disabled at:[] scan_gray_list+0xe2/0x15f [ 69.281441] CPU: 0 PID: 1026 Comm: kmemleak Tainted: G D 3.18.0-rc2+ #26 [ 69.281442] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 69.281444] 0402 8800d53b7988 81500656 8107339f [ 69.281447] 8800d53b79b8 8105164a 7000 [ 69.281451] 8802114aae78 0009 8800d53b7cc8 8800d53b79d8 [ 69.281454] Call Trace: [ 69.281458] [] dump_stack+0x4f/0x7c [ 69.281462] [] ? console_unlock+0x33d/0x389 [ 69.281466] [] __might_sleep+0x214/0x21c [ 69.281469] [] down_read+0x1c/0x4b [ 69.281473] [] exit_signals+0x21/0x115 [ 69.281475] [] ? kmsg_dump+0x1d/0x199 [ 69.281478] [] do_exit+0x108/0x980 [ 69.281481] [] ? kmsg_dump+0x173/0x199 [ 69.281484] [] ? kmsg_dump+0x190/0x199 [ 69.281487] [] oops_end+0x7c/0x81 [ 69.281491] [] no_context+0x2d6/0x338 [ 69.281495] [] __bad_area_nosemaphore+0x6f/0x1bf [ 69.281498] [] bad_area_nosemaphore+0xe/0x10 [ 69.281500] [] __do_page_fault+0x181/0x363 [ 69.281503] [] ? validate_chain.isra.19+0xe5/0x8b2
Linus GIT 3.18.0-rc2+: INFO: suspicious RCU usage - kernel/sched/core.c:7449 suspicious rcu_dereference_check() usage!
[0.763902] [ INFO: suspicious RCU usage. ]
[0.763904] 3.18.0-rc2+ #25 Not tainted
[0.763906] ---
[0.763907] kernel/sched/core.c:7449 suspicious
rcu_dereference_check() usage!
[0.763908]
other info that might help us debug this:
[0.763911]
rcu_scheduler_active = 1, debug_locks = 1
[0.763913] 2 locks held by swapper/0/0:
[0.763914] #0: (>pi_lock){..}, at: []
task_rq_lock+0x30/0xaa
[0.763923] #1: (>lock){-.}, at: []
task_rq_lock+0x52/0xaa
[0.763928]
stack backtrace:
[0.763930] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.18.0-rc2+ #25
[0.763932] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07
11/14/2013
[0.763934] 0001 81a03cf8 814fdde5
810723dc
[0.763937] 81a16580 81a03d28 8106312e
88021387
[0.763940] 88021ea12780 8802138a
81a03d88
[0.763943] Call Trace:
[0.763948] [] dump_stack+0x4f/0x7c
[0.763952] [] ? console_unlock+0x35a/0x389
[0.763957] [] lockdep_rcu_suspicious+0xfa/0x103
[0.763960] [] sched_move_task+0xda/0x17b
[0.763963] [] ? _raw_write_unlock_irq+0x28/0x48
[0.763966] [] cpu_cgroup_fork+0x9/0xb
[0.763970] [] cgroup_post_fork+0x8a/0x99
[0.763974] [] copy_process+0x17ca/0x1835
[0.763977] [] ? rest_init+0x130/0x130
[0.763981] [] do_fork+0x87/0x23d
[0.763983] [] ? free_reserved_area+0xf4/0x106
[0.763987] [] kernel_thread+0x21/0x23
[0.763990] [] rest_init+0x1e/0x130
[0.763994] [] start_kernel+0x434/0x441
[0.763997] [] x86_64_start_reservations+0x2a/0x2c
[0.763999] [] x86_64_start_kernel+0xc8/0xcc
Gnu C 4.9.1
Gnu make 4.0
binutils 2.24.90.20141023
util-linux 2.25.2
mount debug
module-init-tools 18
e2fsprogs 1.42.12
pcmciautils018
PPP2.4.5
Linux C Library2.19
Dynamic linker (ldd) 2.19
Procps 3.3.9
Net-tools 1.60
Kbd1.15.5
Sh-utils 8.23
Modules Loaded rfcomm bnep ipv6 ecb uvcvideo videobuf2_vmalloc
videobuf2_memops videobuf2_core v4l2_common hid_multitouch videodev
usbhid media ath3k btusb bluetooth snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl
x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp ath9k
dell_laptop ath9k_common ath9k_hw microcode snd_soc_rt5640
snd_soc_rl6231 ath snd_hda_intel snd_soc_core snd_hda_controller
mac80211 snd_hda_codec snd_compress snd_hwdep snd_pcm_dmaengine
cfg80211 snd_pcm_oss rfkill snd_mixer_oss snd_pcm snd_seq_dummy
snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq
snd_seq_device snd_soc_sst_acpi snd_timer i2c_hid snd soundcore
xhci_pci mei_me ehci_pci xhci_hcd shpchp ehci_hcd ac mei lpc_ich wmi
fuse sr_mod cdrom r8169 mii sdhci_acpi sdhci mmc_core
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 3.18.0-rc2 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi
-fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9
-fcall-saved-r10 -fcall-saved-r11"
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
CONFIG_KERNEL_BZIP2=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="Whirlwind"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
Linus GIT 3.18.0-rc2+: INFO: suspicious RCU usage - kernel/sched/core.c:7449 suspicious rcu_dereference_check() usage!
[0.763902] [ INFO: suspicious RCU usage. ]
[0.763904] 3.18.0-rc2+ #25 Not tainted
[0.763906] ---
[0.763907] kernel/sched/core.c:7449 suspicious
rcu_dereference_check() usage!
[0.763908]
other info that might help us debug this:
[0.763911]
rcu_scheduler_active = 1, debug_locks = 1
[0.763913] 2 locks held by swapper/0/0:
[0.763914] #0: (p-pi_lock){..}, at: [8104fb23]
task_rq_lock+0x30/0xaa
[0.763923] #1: (rq-lock){-.}, at: [8104fb45]
task_rq_lock+0x52/0xaa
[0.763928]
stack backtrace:
[0.763930] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.18.0-rc2+ #25
[0.763932] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07
11/14/2013
[0.763934] 0001 81a03cf8 814fdde5
810723dc
[0.763937] 81a16580 81a03d28 8106312e
88021387
[0.763940] 88021ea12780 8802138a
81a03d88
[0.763943] Call Trace:
[0.763948] [814fdde5] dump_stack+0x4f/0x7c
[0.763952] [810723dc] ? console_unlock+0x35a/0x389
[0.763957] [8106312e] lockdep_rcu_suspicious+0xfa/0x103
[0.763960] [81055726] sched_move_task+0xda/0x17b
[0.763963] [815052c5] ? _raw_write_unlock_irq+0x28/0x48
[0.763966] [810557e4] cpu_cgroup_fork+0x9/0xb
[0.763970] [8109e8d7] cgroup_post_fork+0x8a/0x99
[0.763974] [81033625] copy_process+0x17ca/0x1835
[0.763977] [814f94bc] ? rest_init+0x130/0x130
[0.763981] [810337ea] do_fork+0x87/0x23d
[0.763983] [810b90fa] ? free_reserved_area+0xf4/0x106
[0.763987] [810339c1] kernel_thread+0x21/0x23
[0.763990] [814f93aa] rest_init+0x1e/0x130
[0.763994] [81aaae6c] start_kernel+0x434/0x441
[0.763997] [81aaa487] x86_64_start_reservations+0x2a/0x2c
[0.763999] [81aaa551] x86_64_start_kernel+0xc8/0xcc
Gnu C 4.9.1
Gnu make 4.0
binutils 2.24.90.20141023
util-linux 2.25.2
mount debug
module-init-tools 18
e2fsprogs 1.42.12
pcmciautils018
PPP2.4.5
Linux C Library2.19
Dynamic linker (ldd) 2.19
Procps 3.3.9
Net-tools 1.60
Kbd1.15.5
Sh-utils 8.23
Modules Loaded rfcomm bnep ipv6 ecb uvcvideo videobuf2_vmalloc
videobuf2_memops videobuf2_core v4l2_common hid_multitouch videodev
usbhid media ath3k btusb bluetooth snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl
x86_pkg_temp_thermal intel_powerclamp dell_wmi coretemp ath9k
dell_laptop ath9k_common ath9k_hw microcode snd_soc_rt5640
snd_soc_rl6231 ath snd_hda_intel snd_soc_core snd_hda_controller
mac80211 snd_hda_codec snd_compress snd_hwdep snd_pcm_dmaengine
cfg80211 snd_pcm_oss rfkill snd_mixer_oss snd_pcm snd_seq_dummy
snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq
snd_seq_device snd_soc_sst_acpi snd_timer i2c_hid snd soundcore
xhci_pci mei_me ehci_pci xhci_hcd shpchp ehci_hcd ac mei lpc_ich wmi
fuse sr_mod cdrom r8169 mii sdhci_acpi sdhci mmc_core
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 3.18.0-rc2 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT=elf64-x86-64
CONFIG_ARCH_DEFCONFIG=arch/x86/configs/x86_64_defconfig
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS=-fcall-saved-rdi -fcall-saved-rsi
-fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9
-fcall-saved-r10 -fcall-saved-r11
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
Linus GIT 3.18.0-rc2+ - BUG: unable to handle kernel paging request at ffff88021dc52000 - IP: [ffffffff810f5514] scan_block+0x59/0x100
[ 69.271345] BUG: unable to handle kernel paging request at 88021dc52000 [ 69.271417] IP: [810f5514] scan_block+0x59/0x100 [ 69.271471] PGD 28d5067 PUD 28d8067 PMD 21fdf2067 PTE 80021dc52060 [ 69.271542] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 69.271597] Modules linked in: rfcomm ipv6 bnep ecb uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common hid_multitouch videodev media usbhid ath3k btusb bluetooth snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp dell_laptop microcode ath9k ath9k_common ath9k_hw ath mac80211 r8169 cfg80211 rfkill snd_soc_rt5640 snd_soc_rl6231 snd_hda_intel snd_soc_core snd_hda_controller snd_compress snd_hda_codec snd_pcm_dmaengine snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_soc_sst_acpi snd_seq_device snd_timer sdhci_acpi sdhci mmc_core xhci_pci snd i2c_hid mei_me soundcore ehci_pci lpc_ich mei xhci_hcd ehci_hcd shpchp wmi ac fuse sr_mod [ 69.272392] cdrom mii [ 69.272410] CPU: 0 PID: 1026 Comm: kmemleak Not tainted 3.18.0-rc2+ #26 [ 69.272471] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 69.272529] task: 880211d98000 ti: 8800d53b4000 task.ti: 8800d53b4000 [ 69.272588] RIP: 0010:[810f5514] [810f5514] scan_block+0x59/0x100 [ 69.272661] RSP: 0018:8800d53b7d78 EFLAGS: 00010046 [ 69.272704] RAX: RBX: 880214828000 RCX: [ 69.272769] RDX: 880214828000 RSI: 88021dc53000 RDI: 88021dc52000 [ 69.272832] RBP: 8800d53b7db8 R08: 0001 R09: 00406032 [ 69.272889] R10: R11: 0002 R12: 88021dc52000 [ 69.272945] R13: 88021dc52ff9 R14: 880214828000 R15: [ 69.273011] FS: () GS:88021da0() knlGS: [ 69.273075] CS: 0010 DS: ES: CR0: 80050033 [ 69.273122] CR2: 88021dc52000 CR3: 00020bcbe000 CR4: 001407f0 [ 69.273186] Stack: [ 69.273204] 8800d53b7db8 81507471 810f569d 880214828000 [ 69.273278] 88021ec0 880214828050 0292 88021dc53000 [ 69.273350] 8800d53b7df8 810f5672 880211d988b0 81a16580 [ 69.273425] Call Trace: [ 69.273452] [81507471] ? _raw_spin_lock_irqsave+0x48/0x52 [ 69.273506] [810f569d] ? scan_gray_list+0xe2/0x15f [ 69.273561] [810f5672] scan_gray_list+0xb7/0x15f [ 69.273615] [810f59ae] kmemleak_scan+0x294/0x45e [ 69.273662] [810f5ecc] ? kmemleak_write+0x354/0x354 [ 69.273711] [810f5f4e] kmemleak_scan_thread+0x82/0xa4 [ 69.273762] [8104cb4d] kthread+0xd6/0xde [ 69.273803] [8104ca77] ? __kthread_parkme+0x62/0x62 [ 69.273856] [81507eec] ret_from_fork+0x7c/0xb0 [ 69.273901] [8104ca77] ? __kthread_parkme+0x62/0x62 [ 69.273945] Code: 00 45 85 ff 74 18 31 d2 be 86 04 00 00 48 c7 c7 80 d5 7e 81 e8 34 bf f5 ff e8 ad e4 40 00 e8 b8 fb ff ff 85 c0 0f 85 98 00 00 00 49 8b 3c 24 be 01 00 00 00 e8 98 fc ff ff 48 85 c0 48 89 c3 74 [ 69.274266] RIP [810f5514] scan_block+0x59/0x100 [ 69.274317] RSP 8800d53b7d78 [ 69.274348] CR2: 88021dc52000 [ 69.281408] ---[ end trace 5cc9aa4cd3f6b3b6 ]--- [ 69.281412] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:41 [ 69.281414] in_atomic(): 1, irqs_disabled(): 1, pid: 1026, name: kmemleak [ 69.281415] INFO: lockdep is turned off. [ 69.281417] irq event stamp: 7294084 [ 69.281418] hardirqs last enabled at (7294083): [815075c7] _raw_spin_unlock_irqrestore+0x3a/0x5c [ 69.281424] hardirqs last disabled at (7294084): [81507443] _raw_spin_lock_irqsave+0x1a/0x52 [ 69.281427] softirqs last enabled at (7294078): [81037e74] __do_softirq+0x221/0x27d [ 69.281431] softirqs last disabled at (7294059): [810380f6] irq_exit+0x59/0xdb [ 69.281434] Preemption disabled at:[810f569d] scan_gray_list+0xe2/0x15f [ 69.281441] CPU: 0 PID: 1026 Comm: kmemleak Tainted: G D 3.18.0-rc2+ #26 [ 69.281442] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 69.281444] 0402 8800d53b7988 81500656 8107339f [ 69.281447] 8800d53b79b8 8105164a 7000 [ 69.281451] 8802114aae78 0009 8800d53b7cc8 8800d53b79d8 [ 69.281454] Call Trace: [ 69.281458] [81500656] dump_stack+0x4f/0x7c [ 69.281462] [8107339f] ? console_unlock+0x33d/0x389 [ 69.281466] [8105164a] __might_sleep+0x214/0x21c [ 69.281469] [8150649e] down_read+0x1c/0x4b [ 69.281473] [81040821] exit_signals+0x21/0x115 [ 69.281475] [810744b8] ?
Re: Linus GIT 3.17.0+ - BUG: unable to handle kernel paging request - IP: [] scan_block+0x59/0x100
On Thu, Oct 16, 2014 at 10:02 AM, Catalin Marinas wrote: > Hi Miles, > > On 15 October 2014 04:43, Miles Lane wrote: >> [ 68.164917] BUG: unable to handle kernel paging request at >> 88021dc52000 >> [ 68.164957] IP: [] scan_block+0x59/0x100 >> [ 68.164987] PGD 2902067 PUD 2905067 PMD 21fdf2067 PTE 80021dc52060 > > My reading of the x86 _PAGE_BIT_* macros show that this is not present. > >> [ 68.165020] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC > > And this could be caused by CONFIG_DEBUG_PAGEALLOC, though kmemleak > should not try to access such memory. > >> [ 68.165945] Call Trace: >> [ 68.165960] [] ? _raw_spin_lock_irqsave+0x48/0x52 >> [ 68.165988] [] ? scan_gray_list+0xe2/0x15f >> [ 68.166015] [] scan_gray_list+0xb7/0x15f >> [ 68.166040] [] kmemleak_scan+0x29c/0x466 >> [ 68.166066] [] ? kmemleak_write+0x354/0x354 >> [ 68.166092] [] kmemleak_scan_thread+0x82/0xa4 > > I have a couple of questions: > > 1. Are there any messages prior to the dump you posted, like kmemleak > getting disabled? There are no indications of problems with kmemleak before the BUG. This is all I see: [5.111054] kmemleak: Kernel memory leak detector initialized [5.111062] kmemleak: Automatic memory scanning thread started > 2. Can you still reproduce the problem with !CONFIG_DEBUG_PAGEALLOC? When I disable this option, the BUG does not occur. > Thanks, > > Catalin -- 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: Linus GIT 3.17.0+ - BUG: unable to handle kernel paging request - IP: [ffffffff81109e8d] scan_block+0x59/0x100
On Thu, Oct 16, 2014 at 10:02 AM, Catalin Marinas catalin.mari...@arm.com wrote: Hi Miles, On 15 October 2014 04:43, Miles Lane miles.l...@gmail.com wrote: [ 68.164917] BUG: unable to handle kernel paging request at 88021dc52000 [ 68.164957] IP: [81109e8d] scan_block+0x59/0x100 [ 68.164987] PGD 2902067 PUD 2905067 PMD 21fdf2067 PTE 80021dc52060 My reading of the x86 _PAGE_BIT_* macros show that this is not present. [ 68.165020] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC And this could be caused by CONFIG_DEBUG_PAGEALLOC, though kmemleak should not try to access such memory. [ 68.165945] Call Trace: [ 68.165960] [81528559] ? _raw_spin_lock_irqsave+0x48/0x52 [ 68.165988] [8110a016] ? scan_gray_list+0xe2/0x15f [ 68.166015] [81109feb] scan_gray_list+0xb7/0x15f [ 68.166040] [8110a32f] kmemleak_scan+0x29c/0x466 [ 68.166066] [8110a84d] ? kmemleak_write+0x354/0x354 [ 68.166092] [8110a8cf] kmemleak_scan_thread+0x82/0xa4 I have a couple of questions: 1. Are there any messages prior to the dump you posted, like kmemleak getting disabled? There are no indications of problems with kmemleak before the BUG. This is all I see: [5.111054] kmemleak: Kernel memory leak detector initialized [5.111062] kmemleak: Automatic memory scanning thread started 2. Can you still reproduce the problem with !CONFIG_DEBUG_PAGEALLOC? When I disable this option, the BUG does not occur. Thanks, Catalin -- 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/
Linus GIT 3.17.0+ - BUG: unable to handle kernel paging request - IP: [] scan_block+0x59/0x100
[ 68.164917] BUG: unable to handle kernel paging request at 88021dc52000 [ 68.164957] IP: [] scan_block+0x59/0x100 [ 68.164987] PGD 2902067 PUD 2905067 PMD 21fdf2067 PTE 80021dc52060 [ 68.165020] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 68.165048] Modules linked in: ecb uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev ath3k media btusb snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi dell_wmi ipv6 bnep rfcomm bluetooth dell_laptop snd_soc_rt5640 snd_soc_rl6231 intel_rapl x86_pkg_temp_thermal snd_soc_core intel_powerclamp snd_compress coretemp microcode snd_pcm_dmaengine ath9k snd_seq_dummy ath9k_common ath9k_hw ath mac80211 snd_seq_oss snd_hda_intel cfg80211 sr_mod snd_hda_controller cdrom snd_seq_midi rfkill r8169 ehci_pci snd_hda_codec mii snd_hwdep lpc_ich ehci_hcd snd_rawmidi snd_pcm_oss snd_mixer_oss wmi mei_me snd_pcm thermal xhci_pci snd_seq_midi_event shpchp mei xhci_hcd snd_seq battery snd_seq_device snd_timer sdhci_acpi snd sdhci soundcore snd_soc_sst_acpi mmc_core ac processor [ 68.165428] fuse [ 68.165434] CPU: 2 PID: 1017 Comm: kmemleak Not tainted 3.17.0+ #17 [ 68.165463] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 68.165494] task: 8802115a4dc0 ti: 8800d57ac000 task.ti: 8800d57ac000 [ 68.165527] RIP: 0010:[] [] scan_block+0x59/0x100 [ 68.165563] RSP: 0018:8800d57afd78 EFLAGS: 00010046 [ 68.165587] RAX: RBX: 880214828000 RCX: [ 68.165618] RDX: 880214828000 RSI: 88021dc53000 RDI: 88021dc52000 [ 68.165648] RBP: 8800d57afdb8 R08: 0001 R09: 003f6033 [ 68.165678] R10: R11: 0001 R12: 88021dc52000 [ 68.165708] R13: 88021dc52ff9 R14: 880214828000 R15: [ 68.165739] FS: () GS:88021db0() knlGS: [ 68.165775] CS: 0010 DS: ES: CR0: 80050033 [ 68.165800] CR2: 88021dc52000 CR3: 0001fd838000 CR4: 001407e0 [ 68.165830] Stack: [ 68.165839] 8800d57afdb8 81528559 8110a016 880214828000 [ 68.165874] 88021ec0 880214828050 0292 88021dc53000 [ 68.165910] 8800d57afdf8 81109feb 8802115a5678 81a16580 [ 68.165945] Call Trace: [ 68.165960] [] ? _raw_spin_lock_irqsave+0x48/0x52 [ 68.165988] [] ? scan_gray_list+0xe2/0x15f [ 68.166015] [] scan_gray_list+0xb7/0x15f [ 68.166040] [] kmemleak_scan+0x29c/0x466 [ 68.166066] [] ? kmemleak_write+0x354/0x354 [ 68.166092] [] kmemleak_scan_thread+0x82/0xa4 [ 68.166120] [] kthread+0xd6/0xde [ 68.166143] [] ? __kthread_parkme+0x62/0x62 [ 68.166170] [] ret_from_fork+0x7c/0xb0 [ 68.166195] [] ? __kthread_parkme+0x62/0x62 [ 68.166220] Code: 00 45 85 ff 74 18 31 d2 be 86 04 00 00 48 c7 c7 24 cf 7f 81 e8 c0 d8 f4 ff e8 a2 ab 41 00 e8 20 fc ff ff 85 c0 0f 85 98 00 00 00 <49> 8b 3c 24 be 01 00 00 00 e8 09 f9 ff ff 48 85 c0 48 89 c3 74 [ 68.166370] RIP [] scan_block+0x59/0x100 [ 68.166396] RSP [ 68.166411] CR2: 88021dc52000 [ 68.172682] ---[ end trace fe9bfcfd7e0c3b2d ]--- [ 68.172685] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:41 [ 68.172687] in_atomic(): 1, irqs_disabled(): 1, pid: 1017, name: kmemleak [ 68.172688] INFO: lockdep is turned off. [ 68.172689] irq event stamp: 11064396 [ 68.172690] hardirqs last enabled at (11064395): [] _raw_spin_unlock_irqrestore+0x3a/0x5c [ 68.172693] hardirqs last disabled at (11064396): [] _raw_spin_lock_irqsave+0x1a/0x52 [ 68.172697] softirqs last enabled at (10535470): [] __do_softirq+0x21b/0x277 [ 68.172700] softirqs last disabled at (10535465): [] irq_exit+0x59/0xd0 [ 68.172702] Preemption disabled at:[] scan_gray_list+0xe2/0x15f [ 68.172707] CPU: 2 PID: 1017 Comm: kmemleak Tainted: G D 3.17.0+ #17 [ 68.172708] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 68.172709] 03f9 8800d57af978 815221b2 810790d7 [ 68.172712] 8800d57af9a8 8105794f 7000 [ 68.172715] 880211fe8bf8 0009 0046 8800d57af9c8 [ 68.172718] Call Trace: [ 68.172722] [] dump_stack+0x4f/0x7c [ 68.172726] [] ? console_unlock+0x348/0x394 [ 68.172729] [] __might_sleep+0x214/0x21c [ 68.172733] [] down_read+0x1c/0x4b [ 68.172737] [] exit_signals+0x21/0x115 [ 68.172740] [] ? kmsg_dump+0x1d/0x199 [ 68.172744] [] do_exit+0x108/0x9a5 [ 68.172747] [] ? kmsg_dump+0x173/0x199 [ 68.172762] [] ? kmsg_dump+0x190/0x199 [ 68.172767] [] oops_end+0xa1/0xa9 [ 68.172774] [] no_context+0x2d6/0x338 [ 68.172780] [] ? find_usage_backwards+0x68/0x70 [ 68.172785] [] __bad_area_nosemaphore+0x6f/0x1bf [ 68.172791] [] bad_area_nosemaphore+0xe/0x10 [ 68.172796] [] __do_page_fault+0x181/0x363 [
Linus GIT 3.17.0+ - BUG: unable to handle kernel paging request - IP: [ffffffff81109e8d] scan_block+0x59/0x100
[ 68.164917] BUG: unable to handle kernel paging request at 88021dc52000 [ 68.164957] IP: [81109e8d] scan_block+0x59/0x100 [ 68.164987] PGD 2902067 PUD 2905067 PMD 21fdf2067 PTE 80021dc52060 [ 68.165020] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 68.165048] Modules linked in: ecb uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev ath3k media btusb snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi dell_wmi ipv6 bnep rfcomm bluetooth dell_laptop snd_soc_rt5640 snd_soc_rl6231 intel_rapl x86_pkg_temp_thermal snd_soc_core intel_powerclamp snd_compress coretemp microcode snd_pcm_dmaengine ath9k snd_seq_dummy ath9k_common ath9k_hw ath mac80211 snd_seq_oss snd_hda_intel cfg80211 sr_mod snd_hda_controller cdrom snd_seq_midi rfkill r8169 ehci_pci snd_hda_codec mii snd_hwdep lpc_ich ehci_hcd snd_rawmidi snd_pcm_oss snd_mixer_oss wmi mei_me snd_pcm thermal xhci_pci snd_seq_midi_event shpchp mei xhci_hcd snd_seq battery snd_seq_device snd_timer sdhci_acpi snd sdhci soundcore snd_soc_sst_acpi mmc_core ac processor [ 68.165428] fuse [ 68.165434] CPU: 2 PID: 1017 Comm: kmemleak Not tainted 3.17.0+ #17 [ 68.165463] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 68.165494] task: 8802115a4dc0 ti: 8800d57ac000 task.ti: 8800d57ac000 [ 68.165527] RIP: 0010:[81109e8d] [81109e8d] scan_block+0x59/0x100 [ 68.165563] RSP: 0018:8800d57afd78 EFLAGS: 00010046 [ 68.165587] RAX: RBX: 880214828000 RCX: [ 68.165618] RDX: 880214828000 RSI: 88021dc53000 RDI: 88021dc52000 [ 68.165648] RBP: 8800d57afdb8 R08: 0001 R09: 003f6033 [ 68.165678] R10: R11: 0001 R12: 88021dc52000 [ 68.165708] R13: 88021dc52ff9 R14: 880214828000 R15: [ 68.165739] FS: () GS:88021db0() knlGS: [ 68.165775] CS: 0010 DS: ES: CR0: 80050033 [ 68.165800] CR2: 88021dc52000 CR3: 0001fd838000 CR4: 001407e0 [ 68.165830] Stack: [ 68.165839] 8800d57afdb8 81528559 8110a016 880214828000 [ 68.165874] 88021ec0 880214828050 0292 88021dc53000 [ 68.165910] 8800d57afdf8 81109feb 8802115a5678 81a16580 [ 68.165945] Call Trace: [ 68.165960] [81528559] ? _raw_spin_lock_irqsave+0x48/0x52 [ 68.165988] [8110a016] ? scan_gray_list+0xe2/0x15f [ 68.166015] [81109feb] scan_gray_list+0xb7/0x15f [ 68.166040] [8110a32f] kmemleak_scan+0x29c/0x466 [ 68.166066] [8110a84d] ? kmemleak_write+0x354/0x354 [ 68.166092] [8110a8cf] kmemleak_scan_thread+0x82/0xa4 [ 68.166120] [810536ad] kthread+0xd6/0xde [ 68.166143] [810535d7] ? __kthread_parkme+0x62/0x62 [ 68.166170] [81528fec] ret_from_fork+0x7c/0xb0 [ 68.166195] [810535d7] ? __kthread_parkme+0x62/0x62 [ 68.166220] Code: 00 45 85 ff 74 18 31 d2 be 86 04 00 00 48 c7 c7 24 cf 7f 81 e8 c0 d8 f4 ff e8 a2 ab 41 00 e8 20 fc ff ff 85 c0 0f 85 98 00 00 00 49 8b 3c 24 be 01 00 00 00 e8 09 f9 ff ff 48 85 c0 48 89 c3 74 [ 68.166370] RIP [81109e8d] scan_block+0x59/0x100 [ 68.166396] RSP 8800d57afd78 [ 68.166411] CR2: 88021dc52000 [ 68.172682] ---[ end trace fe9bfcfd7e0c3b2d ]--- [ 68.172685] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:41 [ 68.172687] in_atomic(): 1, irqs_disabled(): 1, pid: 1017, name: kmemleak [ 68.172688] INFO: lockdep is turned off. [ 68.172689] irq event stamp: 11064396 [ 68.172690] hardirqs last enabled at (11064395): [815286af] _raw_spin_unlock_irqrestore+0x3a/0x5c [ 68.172693] hardirqs last disabled at (11064396): [8152852b] _raw_spin_lock_irqsave+0x1a/0x52 [ 68.172697] softirqs last enabled at (10535470): [8103e993] __do_softirq+0x21b/0x277 [ 68.172700] softirqs last disabled at (10535465): [8103ec15] irq_exit+0x59/0xd0 [ 68.172702] Preemption disabled at:[8110a016] scan_gray_list+0xe2/0x15f [ 68.172707] CPU: 2 PID: 1017 Comm: kmemleak Tainted: G D 3.17.0+ #17 [ 68.172708] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [ 68.172709] 03f9 8800d57af978 815221b2 810790d7 [ 68.172712] 8800d57af9a8 8105794f 7000 [ 68.172715] 880211fe8bf8 0009 0046 8800d57af9c8 [ 68.172718] Call Trace: [ 68.172722] [815221b2] dump_stack+0x4f/0x7c [ 68.172726] [810790d7] ? console_unlock+0x348/0x394 [ 68.172729] [8105794f] __might_sleep+0x214/0x21c [ 68.172733] [815274d9] down_read+0x1c/0x4b [ 68.172737] [810473fc] exit_signals+0x21/0x115 [ 68.172740] [8107a213] ? kmsg_dump+0x1d/0x199 [
Linus GIT - 3.17.0-rc6+ - BUG: unable to handle kernel NULL pointer dereference - IP: [] thermal_get_trip_type+0x17/0x84 [thermal]
This occurs during the boot process. It is not triggered by userspace as far as I can tell. There are other OOPS messages. I can send the full list if it will help. [2.364611] BUG: unable to handle kernel NULL pointer dereference at 0039 [2.364615] IP: [] thermal_get_trip_type+0x17/0x84 [thermal] [2.364616] PGD 374d6067 PUD 374d7067 PMD 0 [2.364618] Oops: [#1] PREEMPT SMP [2.364621] Modules linked in: thermal(+) mmc_core [2.364623] CPU: 0 PID: 971 Comm: systemd-udevd Not tainted 3.17.0-rc6+ #6 [2.364624] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [2.364625] task: 8802155f8cf0 ti: 8800374f4000 task.ti: 8800374f4000 [2.364628] RIP: 0010:[] [] thermal_get_trip_type+0x17/0x84 [thermal] [2.364629] RSP: 0018:8800374f7b50 EFLAGS: 00010202 [2.364629] RAX: 0001 RBX: 0001 RCX: [2.364630] RDX: 8800374f7b7c RSI: RDI: 880216a67800 [2.364631] RBP: 8800374f7b50 R08: R09: 0700 [2.364631] R10: 8802156c7300 R11: 0001 R12: [2.364632] R13: R14: R15: 880216a67800 [2.364633] FS: 7f85e4b55880() GS:88021fa0() knlGS: [2.364634] CS: 0010 DS: ES: CR0: 80050033 [2.364635] CR2: 0039 CR3: 374d5000 CR4: 001407f0 [2.364635] Stack: [2.364637] 8800374f7ba8 813cd140 880216a67804 [2.364638] 880216a67818 8800374f7bb8 880216a67000 8802168721e0 [2.364639] 88021630e860 88021630e890 88021630e830 8800374f7c10 [2.364640] Call Trace: [2.364645] [] thermal_zone_device_register+0x479/0x75a [2.364649] [] acpi_thermal_add+0x24d/0x427 [thermal] [2.364653] [] acpi_device_probe+0x4a/0xf0 [2.364655] [] driver_probe_device+0xb2/0x1e8 [2.364657] [] __driver_attach+0x58/0x7a [2.364659] [] ? __device_attach+0x38/0x38 [2.364662] [] bus_for_each_dev+0x68/0x80 [2.364663] [] driver_attach+0x19/0x1b [2.364664] [] bus_add_driver+0x103/0x1c2 [2.364666] [] driver_register+0x89/0xc5 [2.364669] [] acpi_bus_register_driver+0x38/0x3a [2.364671] [] acpi_thermal_init+0x67/0x81 [thermal] [2.364673] [] ? 0xc0159000 [2.364675] [] do_one_initcall+0x183/0x198 [2.364678] [] ? __vunmap+0xa4/0xac [2.364681] [] load_module+0x16d3/0x1c4e [2.364683] [] SyS_finit_module+0x59/0x66 [2.364685] [] ? SyS_finit_module+0x59/0x66 [2.364688] [] tracesys+0xdd/0xe2 [2.364705] Code: 74 10 31 c0 83 ba 48 05 00 00 00 0f 95 c0 89 06 31 c0 5d c3 89 f1 55 48 8b 87 e8 02 00 00 c1 e9 1f 48 89 e5 75 6b 48 85 c0 74 66 40 38 01 74 0e 85 f6 75 08 c7 02 03 00 00 00 eb 50 ff ce f6 [2.364708] RIP [] thermal_get_trip_type+0x17/0x84 [thermal] [2.364708] RSP [2.364709] CR2: 0039 [2.393720] BUG: unable to handle kernel NULL pointer dereference at 0030 [2.394613] IP: [] add_disk+0x88/0x3ff [2.395490] PGD 375b1067 PUD 375b2067 PMD 0 [2.396371] Oops: [#2] PREEMPT SMP [2.397150] Modules linked in: sr_mod(+) atkbd cdrom mii thermal(+) mmc_core [2.397935] CPU: 0 PID: 974 Comm: systemd-udevd Tainted: G D 3.17.0-rc6+ #6 [2.398738] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [2.399547] task: 8802155fcda0 ti: 88003749 task.ti: 88003749 [2.400336] RIP: 0010:[] [] add_disk+0x88/0x3ff [2.401142] RSP: 0018:880037493b60 EFLAGS: 00010202 [2.401987] RAX: RBX: 8800376ee800 RCX: 0009 [2.402793] RDX: 000b RSI: 880037493b64 RDI: 8800376ee848 [2.403591] RBP: 880037493ba8 R08: R09: [2.40] R10: 880037493b78 R11: 81672240 R12: 8800376ee800 [2.405248] R13: 8800376ee80c R14: R15: 88021629237c [2.406049] FS: 7f85e4b55880() GS:88021fa0() knlGS: [2.406909] CS: 0010 DS: ES: CR0: 80050033 [2.407726] CR2: 0030 CR3: 375b CR4: 001407f0 [2.408558] Stack: [2.409458] 00b0814e22e5 880037493b90 81352deb 88021552 [2.410372] 880216292300 8800376ee800 880216b00968 [2.411297] 88021629237c 880037493c30 c01a1d40 8808200e [2.412205] Call Trace: [2.413057] [] ? __pm_runtime_use_autosuspend+0x5e/0x65 [2.413935] [] sr_probe+0x480/0x4d2 [sr_mod] [2.414853] [] driver_probe_device+0xb2/0x1e8 [2.415732] [] __driver_attach+0x58/0x7a [2.416657] [] ? __device_attach+0x38/0x38 [2.417539] [] bus_for_each_dev+0x68/0x80 [2.418421] [] driver_attach+0x19/0x1b [2.419341] []
Linus GIT - 3.17.0-rc6+ - BUG: unable to handle kernel NULL pointer dereference - IP: [ffffffffc015503e] thermal_get_trip_type+0x17/0x84 [thermal]
This occurs during the boot process. It is not triggered by userspace as far as I can tell. There are other OOPS messages. I can send the full list if it will help. [2.364611] BUG: unable to handle kernel NULL pointer dereference at 0039 [2.364615] IP: [c015503e] thermal_get_trip_type+0x17/0x84 [thermal] [2.364616] PGD 374d6067 PUD 374d7067 PMD 0 [2.364618] Oops: [#1] PREEMPT SMP [2.364621] Modules linked in: thermal(+) mmc_core [2.364623] CPU: 0 PID: 971 Comm: systemd-udevd Not tainted 3.17.0-rc6+ #6 [2.364624] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [2.364625] task: 8802155f8cf0 ti: 8800374f4000 task.ti: 8800374f4000 [2.364628] RIP: 0010:[c015503e] [c015503e] thermal_get_trip_type+0x17/0x84 [thermal] [2.364629] RSP: 0018:8800374f7b50 EFLAGS: 00010202 [2.364629] RAX: 0001 RBX: 0001 RCX: [2.364630] RDX: 8800374f7b7c RSI: RDI: 880216a67800 [2.364631] RBP: 8800374f7b50 R08: R09: 0700 [2.364631] R10: 8802156c7300 R11: 0001 R12: [2.364632] R13: R14: R15: 880216a67800 [2.364633] FS: 7f85e4b55880() GS:88021fa0() knlGS: [2.364634] CS: 0010 DS: ES: CR0: 80050033 [2.364635] CR2: 0039 CR3: 374d5000 CR4: 001407f0 [2.364635] Stack: [2.364637] 8800374f7ba8 813cd140 880216a67804 [2.364638] 880216a67818 8800374f7bb8 880216a67000 8802168721e0 [2.364639] 88021630e860 88021630e890 88021630e830 8800374f7c10 [2.364640] Call Trace: [2.364645] [813cd140] thermal_zone_device_register+0x479/0x75a [2.364649] [c0156120] acpi_thermal_add+0x24d/0x427 [thermal] [2.364653] [8125652c] acpi_device_probe+0x4a/0xf0 [2.364655] [8134bd0b] driver_probe_device+0xb2/0x1e8 [2.364657] [8134bed1] __driver_attach+0x58/0x7a [2.364659] [8134be79] ? __device_attach+0x38/0x38 [2.364662] [8134a4a1] bus_for_each_dev+0x68/0x80 [2.364663] [8134b8a9] driver_attach+0x19/0x1b [2.364664] [8134b59b] bus_add_driver+0x103/0x1c2 [2.364666] [8134c42d] driver_register+0x89/0xc5 [2.364669] [81256d39] acpi_bus_register_driver+0x38/0x3a [2.364671] [c0159067] acpi_thermal_init+0x67/0x81 [thermal] [2.364673] [c0159000] ? 0xc0159000 [2.364675] [810003a6] do_one_initcall+0x183/0x198 [2.364678] [81109d47] ? __vunmap+0xa4/0xac [2.364681] [810b967e] load_module+0x16d3/0x1c4e [2.364683] [810b9cef] SyS_finit_module+0x59/0x66 [2.364685] [810b9cef] ? SyS_finit_module+0x59/0x66 [2.364688] [814e2c4b] tracesys+0xdd/0xe2 [2.364705] Code: 74 10 31 c0 83 ba 48 05 00 00 00 0f 95 c0 89 06 31 c0 5d c3 89 f1 55 48 8b 87 e8 02 00 00 c1 e9 1f 48 89 e5 75 6b 48 85 c0 74 66 f6 40 38 01 74 0e 85 f6 75 08 c7 02 03 00 00 00 eb 50 ff ce f6 [2.364708] RIP [c015503e] thermal_get_trip_type+0x17/0x84 [thermal] [2.364708] RSP 8800374f7b50 [2.364709] CR2: 0039 [2.393720] BUG: unable to handle kernel NULL pointer dereference at 0030 [2.394613] IP: [811f9834] add_disk+0x88/0x3ff [2.395490] PGD 375b1067 PUD 375b2067 PMD 0 [2.396371] Oops: [#2] PREEMPT SMP [2.397150] Modules linked in: sr_mod(+) atkbd cdrom mii thermal(+) mmc_core [2.397935] CPU: 0 PID: 974 Comm: systemd-udevd Tainted: G D 3.17.0-rc6+ #6 [2.398738] Hardware name: Dell Inc. Inspiron 5437/0DM6M9, BIOS A07 11/14/2013 [2.399547] task: 8802155fcda0 ti: 88003749 task.ti: 88003749 [2.400336] RIP: 0010:[811f9834] [811f9834] add_disk+0x88/0x3ff [2.401142] RSP: 0018:880037493b60 EFLAGS: 00010202 [2.401987] RAX: RBX: 8800376ee800 RCX: 0009 [2.402793] RDX: 000b RSI: 880037493b64 RDI: 8800376ee848 [2.403591] RBP: 880037493ba8 R08: R09: [2.40] R10: 880037493b78 R11: 81672240 R12: 8800376ee800 [2.405248] R13: 8800376ee80c R14: R15: 88021629237c [2.406049] FS: 7f85e4b55880() GS:88021fa0() knlGS: [2.406909] CS: 0010 DS: ES: CR0: 80050033 [2.407726] CR2: 0030 CR3: 375b CR4: 001407f0 [2.408558] Stack: [2.409458] 00b0814e22e5 880037493b90 81352deb 88021552 [2.410372] 880216292300 8800376ee800 880216b00968 [2.411297] 88021629237c
Linus GIT - kernel BUG at include/linux/scatterlist.h:115! CPU: 1 PID: 1203 Comm: apparmor_parser Not tainted 3.12.0-rc1+
[ 27.190017] kernel BUG at include/linux/scatterlist.h:115! [ 27.190017] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 27.190017] Modules linked in: mxm_wmi iwldvm mac80211 iwlwifi cfg80211 snd_hda_intel(+) snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss hwmon snd_pcm ttm snd_seq_dummy snd_page_alloc snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_timer i915(+) snd i2c_algo_bit drm_kms_helper wmi ac drm soundcore evdev mac_hid i2c_core battery acpi_cpufreq ehci_pci(+) ehci_hcd asus_laptop rfkill intel_agp intel_gtt agpgart processor sr_mod cdrom atl1c uhci_hcd thermal [ 27.190017] CPU: 1 PID: 1203 Comm: apparmor_parser Not tainted 3.12.0-rc1+ #8 [ 27.190017] Hardware name: ASUSTeK Computer Inc. UL50VT /UL50VT, BIOS 217 03/01/2010 [ 27.190017] task: 8800bd99ea80 ti: 8800baf5a000 task.ti: 8800baf5a000 [ 27.190017] RIP: 0010:[] [] sg_set_buf+0x20/0x7e [ 27.190017] RSP: 0018:8800baf5bcf8 EFLAGS: 00010246 [ 27.190017] RAX: RBX: 8800baf5bd70 RCX: 0024 [ 27.190017] RDX: 0410 RSI: c900108ca010 RDI: 4100108ca010 [ 27.190017] RBP: 8800baf5bd18 R08: 880138eec290 R09: [ 27.190017] R10: 880138ee2148 R11: 0e12 R12: c900108ca010 [ 27.190017] R13: 8649 R14: c900108ca010 R15: 880138ee [ 27.190017] FS: 7f96aaf6c740() GS:88013f30() knlGS: [ 27.190017] CS: 0010 DS: ES: CR0: 80050033 [ 27.190017] CR2: 7f96aaf5d00f CR3: b9e7a000 CR4: 000407e0 [ 27.190017] Stack: [ 27.190017] 8800b9d55520 8800baf5bd70 8649 c900108ca010 [ 27.190017] 8800baf5bdb8 811f9f50 811f3eef 000538ee8000 [ 27.190017] 880138c42000 8800 87654321 ea0002ebd6c0 [ 27.190017] Call Trace: [ 27.190017] [] aa_calc_profile_hash+0x75/0x11d [ 27.190017] [] ? __aa_kvmalloc+0x39/0x51 [ 27.190017] [] aa_unpack+0x929/0x969 [ 27.190017] [] aa_replace_profiles+0x38/0x57c [ 27.190017] [] profile_replace+0x35/0x4c [ 27.190017] [] vfs_write+0xad/0x113 [ 27.190017] [] SyS_write+0x44/0x7a [ 27.190017] [] system_call_fastpath+0x16/0x1b [ 27.190017] Code: 66 89 45 fc e8 6a fc ff ff c9 c3 55 48 89 e5 41 56 41 55 41 89 d5 41 54 49 89 f4 53 48 89 fb 48 89 f7 e8 1b 9e e3 ff 84 c0 75 02 <0f> 0b 4c 89 e7 45 89 e6 e8 96 9e e3 ff 48 8b 53 08 41 81 e6 ff [ 27.190017] RIP [] sg_set_buf+0x20/0x7e [ 27.190017] RSP -- 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/
Linus GIT - kernel BUG at include/linux/scatterlist.h:115! CPU: 1 PID: 1203 Comm: apparmor_parser Not tainted 3.12.0-rc1+
[ 27.190017] kernel BUG at include/linux/scatterlist.h:115! [ 27.190017] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 27.190017] Modules linked in: mxm_wmi iwldvm mac80211 iwlwifi cfg80211 snd_hda_intel(+) snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss hwmon snd_pcm ttm snd_seq_dummy snd_page_alloc snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_timer i915(+) snd i2c_algo_bit drm_kms_helper wmi ac drm soundcore evdev mac_hid i2c_core battery acpi_cpufreq ehci_pci(+) ehci_hcd asus_laptop rfkill intel_agp intel_gtt agpgart processor sr_mod cdrom atl1c uhci_hcd thermal [ 27.190017] CPU: 1 PID: 1203 Comm: apparmor_parser Not tainted 3.12.0-rc1+ #8 [ 27.190017] Hardware name: ASUSTeK Computer Inc. UL50VT /UL50VT, BIOS 217 03/01/2010 [ 27.190017] task: 8800bd99ea80 ti: 8800baf5a000 task.ti: 8800baf5a000 [ 27.190017] RIP: 0010:[811f9e71] [811f9e71] sg_set_buf+0x20/0x7e [ 27.190017] RSP: 0018:8800baf5bcf8 EFLAGS: 00010246 [ 27.190017] RAX: RBX: 8800baf5bd70 RCX: 0024 [ 27.190017] RDX: 0410 RSI: c900108ca010 RDI: 4100108ca010 [ 27.190017] RBP: 8800baf5bd18 R08: 880138eec290 R09: [ 27.190017] R10: 880138ee2148 R11: 0e12 R12: c900108ca010 [ 27.190017] R13: 8649 R14: c900108ca010 R15: 880138ee [ 27.190017] FS: 7f96aaf6c740() GS:88013f30() knlGS: [ 27.190017] CS: 0010 DS: ES: CR0: 80050033 [ 27.190017] CR2: 7f96aaf5d00f CR3: b9e7a000 CR4: 000407e0 [ 27.190017] Stack: [ 27.190017] 8800b9d55520 8800baf5bd70 8649 c900108ca010 [ 27.190017] 8800baf5bdb8 811f9f50 811f3eef 000538ee8000 [ 27.190017] 880138c42000 8800 87654321 ea0002ebd6c0 [ 27.190017] Call Trace: [ 27.190017] [811f9f50] aa_calc_profile_hash+0x75/0x11d [ 27.190017] [811f3eef] ? __aa_kvmalloc+0x39/0x51 [ 27.190017] [811f7e34] aa_unpack+0x929/0x969 [ 27.190017] [811f6a21] aa_replace_profiles+0x38/0x57c [ 27.190017] [811f249b] profile_replace+0x35/0x4c [ 27.190017] [81121477] vfs_write+0xad/0x113 [ 27.190017] [81121add] SyS_write+0x44/0x7a [ 27.190017] [8145f3e2] system_call_fastpath+0x16/0x1b [ 27.190017] Code: 66 89 45 fc e8 6a fc ff ff c9 c3 55 48 89 e5 41 56 41 55 41 89 d5 41 54 49 89 f4 53 48 89 fb 48 89 f7 e8 1b 9e e3 ff 84 c0 75 02 0f 0b 4c 89 e7 45 89 e6 e8 96 9e e3 ff 48 8b 53 08 41 81 e6 ff [ 27.190017] RIP [811f9e71] sg_set_buf+0x20/0x7e [ 27.190017] RSP 8800baf5bcf8 -- 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/
Linus Git (3.11.0+) - security/apparmor/include/policy.h:363 suspicious rcu_dereference_check() usage!
[ 29.804534] [ INFO: suspicious RCU usage. ]
[ 29.804539] 3.11.0+ #5 Not tainted
[ 29.804541] ---
[ 29.804545] security/apparmor/include/policy.h:363 suspicious
rcu_dereference_check() usage!
[ 29.804548]
[ 29.804548] other info that might help us debug this:
[ 29.804548]
[ 29.804553]
[ 29.804553] rcu_scheduler_active = 1, debug_locks = 1
[ 29.804558] 2 locks held by apparmor_parser/1268:
[ 29.804560] #0: (sb_writers#9){.+.+.+}, at: []
file_start_write+0x27/0x29
[ 29.804576] #1: (>lock){+.+.+.}, at: []
aa_replace_profiles+0x166/0x57c
[ 29.804589]
[ 29.804589] stack backtrace:
[ 29.804595] CPU: 0 PID: 1268 Comm: apparmor_parser Not tainted 3.11.0+ #5
[ 29.804599] Hardware name: ASUSTeK Computer Inc. UL50VT
/UL50VT, BIOS 217 03/01/2010
[ 29.804602] 8800b95a1d90 8144eb9b
8800b94db540
[ 29.804611] 8800b95a1dc0 81087439 880138cc3a18
880138cc3a18
[ 29.804619] 8800b9464a90 880138cc3a38 8800b95a1df0
811f5084
[ 29.804628] Call Trace:
[ 29.804636] [] dump_stack+0x4e/0x82
[ 29.804642] [] lockdep_rcu_suspicious+0xfc/0x105
[ 29.804649] [] __aa_update_replacedby+0x53/0x7f
[ 29.804655] [] __replace_profile+0x11f/0x1ed
[ 29.804661] [] aa_replace_profiles+0x410/0x57c
[ 29.804668] [] profile_replace+0x35/0x4c
[ 29.804674] [] vfs_write+0xad/0x113
[ 29.804680] [] SyS_write+0x44/0x7a
[ 29.804687] [] system_call_fastpath+0x16/0x1b
[ 29.804691]
[ 29.804694] ===
[ 29.804697] [ INFO: suspicious RCU usage. ]
[ 29.804700] 3.11.0+ #5 Not tainted
[ 29.804703] ---
[ 29.804706] security/apparmor/policy.c:566 suspicious
rcu_dereference_check() usage!
[ 29.804709]
[ 29.804709] other info that might help us debug this:
[ 29.804709]
[ 29.804714]
[ 29.804714] rcu_scheduler_active = 1, debug_locks = 1
[ 29.804718] 2 locks held by apparmor_parser/1268:
[ 29.804721] #0: (sb_writers#9){.+.+.+}, at: []
file_start_write+0x27/0x29
[ 29.804733] #1: (>lock){+.+.+.}, at: []
aa_replace_profiles+0x166/0x57c
[ 29.804744]
[ 29.804744] stack backtrace:
[ 29.804750] CPU: 0 PID: 1268 Comm: apparmor_parser Not tainted 3.11.0+ #5
[ 29.804753] Hardware name: ASUSTeK Computer Inc. UL50VT
/UL50VT, BIOS 217 03/01/2010
[ 29.804756] 8800b95a1d80 8144eb9b
8800b94db540
[ 29.804764] 8800b95a1db0 81087439 8800b95b02b0
[ 29.804772] 8800b9efba08 880138cc3a38 8800b95a1dd0
811f4f94
[ 29.804779] Call Trace:
[ 29.804786] [] dump_stack+0x4e/0x82
[ 29.804791] [] lockdep_rcu_suspicious+0xfc/0x105
[ 29.804798] [] aa_free_replacedby_kref+0x4d/0x62
[ 29.804804] [] ? aa_put_namespace+0x17/0x17
[ 29.804810] [] kref_put+0x36/0x40
[ 29.804816] [] __replace_profile+0x13a/0x1ed
[ 29.804822] [] aa_replace_profiles+0x410/0x57c
[ 29.804829] [] profile_replace+0x35/0x4c
[ 29.804835] [] vfs_write+0xad/0x113
[ 29.804840] [] SyS_write+0x44/0x7a
[ 29.804847] [] system_call_fastpath+0x16/0x1b
--
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/
Linus Git (3.11.0+) - security/apparmor/include/policy.h:363 suspicious rcu_dereference_check() usage!
[ 29.804534] [ INFO: suspicious RCU usage. ]
[ 29.804539] 3.11.0+ #5 Not tainted
[ 29.804541] ---
[ 29.804545] security/apparmor/include/policy.h:363 suspicious
rcu_dereference_check() usage!
[ 29.804548]
[ 29.804548] other info that might help us debug this:
[ 29.804548]
[ 29.804553]
[ 29.804553] rcu_scheduler_active = 1, debug_locks = 1
[ 29.804558] 2 locks held by apparmor_parser/1268:
[ 29.804560] #0: (sb_writers#9){.+.+.+}, at: [81120a4c]
file_start_write+0x27/0x29
[ 29.804576] #1: (ns-lock){+.+.+.}, at: [811f5d88]
aa_replace_profiles+0x166/0x57c
[ 29.804589]
[ 29.804589] stack backtrace:
[ 29.804595] CPU: 0 PID: 1268 Comm: apparmor_parser Not tainted 3.11.0+ #5
[ 29.804599] Hardware name: ASUSTeK Computer Inc. UL50VT
/UL50VT, BIOS 217 03/01/2010
[ 29.804602] 8800b95a1d90 8144eb9b
8800b94db540
[ 29.804611] 8800b95a1dc0 81087439 880138cc3a18
880138cc3a18
[ 29.804619] 8800b9464a90 880138cc3a38 8800b95a1df0
811f5084
[ 29.804628] Call Trace:
[ 29.804636] [8144eb9b] dump_stack+0x4e/0x82
[ 29.804642] [81087439] lockdep_rcu_suspicious+0xfc/0x105
[ 29.804649] [811f5084] __aa_update_replacedby+0x53/0x7f
[ 29.804655] [811f5408] __replace_profile+0x11f/0x1ed
[ 29.804661] [811f6032] aa_replace_profiles+0x410/0x57c
[ 29.804668] [811f16d4] profile_replace+0x35/0x4c
[ 29.804674] [81120fa3] vfs_write+0xad/0x113
[ 29.804680] [81121609] SyS_write+0x44/0x7a
[ 29.804687] [8145bfd2] system_call_fastpath+0x16/0x1b
[ 29.804691]
[ 29.804694] ===
[ 29.804697] [ INFO: suspicious RCU usage. ]
[ 29.804700] 3.11.0+ #5 Not tainted
[ 29.804703] ---
[ 29.804706] security/apparmor/policy.c:566 suspicious
rcu_dereference_check() usage!
[ 29.804709]
[ 29.804709] other info that might help us debug this:
[ 29.804709]
[ 29.804714]
[ 29.804714] rcu_scheduler_active = 1, debug_locks = 1
[ 29.804718] 2 locks held by apparmor_parser/1268:
[ 29.804721] #0: (sb_writers#9){.+.+.+}, at: [81120a4c]
file_start_write+0x27/0x29
[ 29.804733] #1: (ns-lock){+.+.+.}, at: [811f5d88]
aa_replace_profiles+0x166/0x57c
[ 29.804744]
[ 29.804744] stack backtrace:
[ 29.804750] CPU: 0 PID: 1268 Comm: apparmor_parser Not tainted 3.11.0+ #5
[ 29.804753] Hardware name: ASUSTeK Computer Inc. UL50VT
/UL50VT, BIOS 217 03/01/2010
[ 29.804756] 8800b95a1d80 8144eb9b
8800b94db540
[ 29.804764] 8800b95a1db0 81087439 8800b95b02b0
[ 29.804772] 8800b9efba08 880138cc3a38 8800b95a1dd0
811f4f94
[ 29.804779] Call Trace:
[ 29.804786] [8144eb9b] dump_stack+0x4e/0x82
[ 29.804791] [81087439] lockdep_rcu_suspicious+0xfc/0x105
[ 29.804798] [811f4f94] aa_free_replacedby_kref+0x4d/0x62
[ 29.804804] [811f4f47] ? aa_put_namespace+0x17/0x17
[ 29.804810] [811f4f0b] kref_put+0x36/0x40
[ 29.804816] [811f5423] __replace_profile+0x13a/0x1ed
[ 29.804822] [811f6032] aa_replace_profiles+0x410/0x57c
[ 29.804829] [811f16d4] profile_replace+0x35/0x4c
[ 29.804835] [81120fa3] vfs_write+0xad/0x113
[ 29.804840] [81121609] SyS_write+0x44/0x7a
[ 29.804847] [8145bfd2] system_call_fastpath+0x16/0x1b
--
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.11.0-rc6+: INFO: possible circular locking dependency detected
[ 24.990076] [ INFO: possible circular locking dependency detected ]
[ 24.990086] 3.11.0-rc6+ #154 Not tainted
[ 24.990094] ---
[ 24.990103] crda/1159 is trying to acquire lock:
[ 24.990111] (genl_mutex){+.+.+.}, at: []
genl_lock+0x12/0x14
[ 24.990134]
[ 24.990134] but task is already holding lock:
[ 24.990144] (nlk->cb_mutex){+.+.+.}, at: []
netlink_dump+0x1c/0x1da
[ 24.990163]
[ 24.990163] which lock already depends on the new lock.
[ 24.990163]
[ 24.990177]
[ 24.990177] the existing dependency chain (in reverse order) is:
[ 24.990188]
[ 24.990188] -> #1 (nlk->cb_mutex){+.+.+.}:
[ 24.990202][] lock_acquire+0x8f/0xa7
[ 24.990214][] mutex_lock_nested+0x72/0x42a
[ 24.990228][] __netlink_dump_start+0xb0/0x13b
[ 24.990240][] genl_family_rcv_msg+0x106/0x24f
[ 24.990253][] genl_rcv_msg+0x3b/0x5b
[ 24.990264][] netlink_rcv_skb+0x44/0x86
[ 24.990276][] genl_rcv+0x23/0x32
[ 24.990287][] netlink_unicast+0xe2/0x166
[ 24.990299][] netlink_sendmsg+0x304/0x34e
[ 24.990311][] __sock_sendmsg_nosec+0x25/0x27
[ 24.990324][] sock_sendmsg+0x54/0x70
[ 24.990336][] ___sys_sendmsg+0x1fe/0x28e
[ 24.990348][] __sys_sendmsg+0x3d/0x5b
[ 24.990359][] SyS_sendmsg+0xd/0x17
[ 24.990370][] tracesys+0xdd/0xe2
[ 24.990382]
[ 24.990382] -> #0 (genl_mutex){+.+.+.}:
[ 24.990394][] __lock_acquire+0xb5f/0xe49
[ 24.990406][] lock_acquire+0x8f/0xa7
[ 24.990417][] mutex_lock_nested+0x72/0x42a
[ 24.990429][] genl_lock+0x12/0x14
[ 24.990440][] ctrl_dumpfamily+0x42/0x117
[ 24.990452][] netlink_dump+0x88/0x1da
[ 24.990463][] netlink_recvmsg+0x16f/0x2f4
[ 24.990475][] __sock_recvmsg_nosec+0x29/0x2b
[ 24.990487][] sock_recvmsg+0x5f/0x7d
[ 24.990499][] ___sys_recvmsg+0x155/0x21f
[ 24.990510][] __sys_recvmsg+0x3d/0x5b
[ 24.990522][] SyS_recvmsg+0xd/0x17
[ 24.990532][] tracesys+0xdd/0xe2
[ 24.990544]
[ 24.990544] other info that might help us debug this:
[ 24.990544]
[ 24.990557] Possible unsafe locking scenario:
[ 24.990557]
[ 24.990567]CPU0CPU1
[ 24.990575]
[ 24.990582] lock(nlk->cb_mutex);
[ 24.990591]lock(genl_mutex);
[ 24.990602]lock(nlk->cb_mutex);
[ 24.990612] lock(genl_mutex);
[ 24.990620]
[ 24.990620] *** DEADLOCK ***
[ 24.990620]
[ 24.990633] 1 lock held by crda/1159:
[ 24.990640] #0: (nlk->cb_mutex){+.+.+.}, at: []
netlink_dump+0x1c/0x1da
[ 24.990660]
[ 24.990660] stack backtrace:
[ 24.990671] CPU: 1 PID: 1159 Comm: crda Not tainted 3.11.0-rc6+ #154
[ 24.990681] Hardware name: ASUSTeK Computer Inc. UL50VT
/UL50VT, BIOS 217 03/01/2010
[ 24.990695] 8801338bb920 81374ba4
81b842b0
[ 24.990711] 8801338bb960 81370581 8801339b4180
8801339b4180
[ 24.990728] 8801339b47a0 8801339b4778 0001
006520ee
[ 24.990744] Call Trace:
[ 24.990754] [] dump_stack+0x4e/0x82
[ 24.990766] [] print_circular_bug+0x1f6/0x204
[ 24.990778] [] __lock_acquire+0xb5f/0xe49
[ 24.990791] [] ? trace_hardirqs_on+0xd/0xf
[ 24.990803] [] ? genl_lock+0x12/0x14
[ 24.990814] [] lock_acquire+0x8f/0xa7
[ 24.990825] [] ? genl_lock+0x12/0x14
[ 24.990837] [] mutex_lock_nested+0x72/0x42a
[ 24.990849] [] ? genl_lock+0x12/0x14
[ 24.990860] [] ? genl_lock+0x12/0x14
[ 24.990873] [] ? __alloc_skb+0x76/0x19c
[ 24.990884] [] genl_lock+0x12/0x14
[ 24.990896] [] ctrl_dumpfamily+0x42/0x117
[ 24.990907] [] ? __alloc_skb+0xa2/0x19c
[ 24.990919] [] netlink_dump+0x88/0x1da
[ 24.990931] [] netlink_recvmsg+0x16f/0x2f4
[ 24.990943] [] __sock_recvmsg_nosec+0x29/0x2b
[ 24.990955] [] sock_recvmsg+0x5f/0x7d
[ 24.990967] [] ? lock_release_non_nested+0x123/0x21d
[ 24.990979] [] ? lock_release_non_nested+0x123/0x21d
[ 24.990993] [] ? verify_iovec+0x58/0xa6
[ 24.991005] [] ___sys_recvmsg+0x155/0x21f
[ 24.991018] [] ? up_read+0x22/0x25
[ 24.991030] [] ? __do_page_fault+0x321/0x3a5
[ 24.991043] [] ? fcheck_files+0x9f/0xe0
[ 24.991055] [] ? fget_light+0x30/0x90
[ 24.991066] [] __sys_recvmsg+0x3d/0x5b
[ 24.991077] [] SyS_recvmsg+0xd/0x17
[ 24.991089] [] tracesys+0xdd/0xe2
--
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.11.0-rc6+: INFO: possible circular locking dependency detected
[ 24.990076] [ INFO: possible circular locking dependency detected ]
[ 24.990086] 3.11.0-rc6+ #154 Not tainted
[ 24.990094] ---
[ 24.990103] crda/1159 is trying to acquire lock:
[ 24.990111] (genl_mutex){+.+.+.}, at: [812ff7e6]
genl_lock+0x12/0x14
[ 24.990134]
[ 24.990134] but task is already holding lock:
[ 24.990144] (nlk-cb_mutex){+.+.+.}, at: [812fdab8]
netlink_dump+0x1c/0x1da
[ 24.990163]
[ 24.990163] which lock already depends on the new lock.
[ 24.990163]
[ 24.990177]
[ 24.990177] the existing dependency chain (in reverse order) is:
[ 24.990188]
[ 24.990188] - #1 (nlk-cb_mutex){+.+.+.}:
[ 24.990202][8107d863] lock_acquire+0x8f/0xa7
[ 24.990214][813777ab] mutex_lock_nested+0x72/0x42a
[ 24.990228][812fdd26] __netlink_dump_start+0xb0/0x13b
[ 24.990240][81300b44] genl_family_rcv_msg+0x106/0x24f
[ 24.990253][81300cc8] genl_rcv_msg+0x3b/0x5b
[ 24.990264][812ff528] netlink_rcv_skb+0x44/0x86
[ 24.990276][812ff98b] genl_rcv+0x23/0x32
[ 24.990287][812ff033] netlink_unicast+0xe2/0x166
[ 24.990299][812ff3bb] netlink_sendmsg+0x304/0x34e
[ 24.990311][812cb91a] __sock_sendmsg_nosec+0x25/0x27
[ 24.990324][812cdf23] sock_sendmsg+0x54/0x70
[ 24.990336][812ce17b] ___sys_sendmsg+0x1fe/0x28e
[ 24.990348][812cf410] __sys_sendmsg+0x3d/0x5b
[ 24.990359][812cf43b] SyS_sendmsg+0xd/0x17
[ 24.990370][8137fc24] tracesys+0xdd/0xe2
[ 24.990382]
[ 24.990382] - #0 (genl_mutex){+.+.+.}:
[ 24.990394][8107d4ea] __lock_acquire+0xb5f/0xe49
[ 24.990406][8107d863] lock_acquire+0x8f/0xa7
[ 24.990417][813777ab] mutex_lock_nested+0x72/0x42a
[ 24.990429][812ff7e6] genl_lock+0x12/0x14
[ 24.990440][81300969] ctrl_dumpfamily+0x42/0x117
[ 24.990452][812fdb24] netlink_dump+0x88/0x1da
[ 24.990463][812fe03c] netlink_recvmsg+0x16f/0x2f4
[ 24.990475][812cb945] __sock_recvmsg_nosec+0x29/0x2b
[ 24.990487][812ce26a] sock_recvmsg+0x5f/0x7d
[ 24.990499][812ceae1] ___sys_recvmsg+0x155/0x21f
[ 24.990510][812cf5f4] __sys_recvmsg+0x3d/0x5b
[ 24.990522][812cf61f] SyS_recvmsg+0xd/0x17
[ 24.990532][8137fc24] tracesys+0xdd/0xe2
[ 24.990544]
[ 24.990544] other info that might help us debug this:
[ 24.990544]
[ 24.990557] Possible unsafe locking scenario:
[ 24.990557]
[ 24.990567]CPU0CPU1
[ 24.990575]
[ 24.990582] lock(nlk-cb_mutex);
[ 24.990591]lock(genl_mutex);
[ 24.990602]lock(nlk-cb_mutex);
[ 24.990612] lock(genl_mutex);
[ 24.990620]
[ 24.990620] *** DEADLOCK ***
[ 24.990620]
[ 24.990633] 1 lock held by crda/1159:
[ 24.990640] #0: (nlk-cb_mutex){+.+.+.}, at: [812fdab8]
netlink_dump+0x1c/0x1da
[ 24.990660]
[ 24.990660] stack backtrace:
[ 24.990671] CPU: 1 PID: 1159 Comm: crda Not tainted 3.11.0-rc6+ #154
[ 24.990681] Hardware name: ASUSTeK Computer Inc. UL50VT
/UL50VT, BIOS 217 03/01/2010
[ 24.990695] 8801338bb920 81374ba4
81b842b0
[ 24.990711] 8801338bb960 81370581 8801339b4180
8801339b4180
[ 24.990728] 8801339b47a0 8801339b4778 0001
006520ee
[ 24.990744] Call Trace:
[ 24.990754] [81374ba4] dump_stack+0x4e/0x82
[ 24.990766] [81370581] print_circular_bug+0x1f6/0x204
[ 24.990778] [8107d4ea] __lock_acquire+0xb5f/0xe49
[ 24.990791] [8107b7ea] ? trace_hardirqs_on+0xd/0xf
[ 24.990803] [812ff7e6] ? genl_lock+0x12/0x14
[ 24.990814] [8107d863] lock_acquire+0x8f/0xa7
[ 24.990825] [812ff7e6] ? genl_lock+0x12/0x14
[ 24.990837] [813777ab] mutex_lock_nested+0x72/0x42a
[ 24.990849] [812ff7e6] ? genl_lock+0x12/0x14
[ 24.990860] [812ff7e6] ? genl_lock+0x12/0x14
[ 24.990873] [812d594f] ? __alloc_skb+0x76/0x19c
[ 24.990884] [812ff7e6] genl_lock+0x12/0x14
[ 24.990896] [81300969] ctrl_dumpfamily+0x42/0x117
[ 24.990907] [812d597b] ? __alloc_skb+0xa2/0x19c
[ 24.990919] [812fdb24] netlink_dump+0x88/0x1da
[ 24.990931] [812fe03c] netlink_recvmsg+0x16f/0x2f4
[ 24.990943] [812cb945] __sock_recvmsg_nosec+0x29/0x2b
[ 24.990955] [812ce26a] sock_recvmsg+0x5f/0x7d
[ 24.990967] [8107dc4b] ? lock_release_non_nested+0x123/0x21d
[ 24.990979] [8107dc4b] ?
3.11.0-rc4 (Linus GIT) -- WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185 can_stop_full_tick+0x7e/0x89()
I am not seeing any problems in the behavior of the computer, but wonder if this indicates something that needs fixing. [1.969109] WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185 can_stop_full_tick+0x7e/0x89() [1.969121] NO_HZ FULL will not work with unstable sched clock [1.969129] Modules linked in: [1.969142] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc4 #150 [1.969152] Hardware name: ASUSTeK Computer Inc. UL50VT /UL50VT, BIOS 217 03/01/2010 [1.969166] 88013f303eb0 8138347b 88013f303ef8 [1.969183] 88013f303ee8 8103454f 81079bbf 88013f30d7b0 [1.969199] 0001 88013a801dc0 88013a802240 88013f303f48 [1.969216] Call Trace: [1.969222][] dump_stack+0x4e/0x82 [1.969241] [] warn_slowpath_common+0x75/0x8e [1.969253] [] ? can_stop_full_tick+0x7e/0x89 [1.969265] [] warn_slowpath_fmt+0x47/0x49 [1.969278] [] can_stop_full_tick+0x7e/0x89 [1.969290] [] tick_nohz_irq_exit+0x63/0x7f [1.969302] [] irq_exit+0xa4/0xac [1.969314] [] smp_apic_timer_interrupt+0x30/0x3c [1.969327] [] apic_timer_interrupt+0x6f/0x80 [1.969336][] ? save_stack_trace+0x26/0x41 [1.969355] [] ? _raw_spin_unlock_irqrestore+0x3c/0x69 [1.969369] [] __slab_free+0x53/0x317 [1.969382] [] ? debug_check_no_obj_freed+0x103/0x153 [1.969397] [] kfree+0x102/0x111 [1.969410] [] ? acpi_ns_get_node+0xb6/0xc6 [1.969422] [] acpi_ns_get_node+0xb6/0xc6 [1.969434] [] ? _raw_spin_unlock_irqrestore+0x5b/0x69 [1.969447] [] ? up+0x34/0x39 [1.969459] [] ? acpi_os_signal_semaphore+0x1c/0x28 [1.969472] [] acpi_get_handle+0x7e/0x92 [1.969486] [] pnpacpi_add_device_handler+0x57/0x217 [1.969499] [] acpi_ns_get_device_callback+0x135/0x14b [1.969511] [] ? up+0x34/0x39 [1.969523] [] acpi_ns_walk_namespace+0xc3/0x17a [1.969535] [] ? acpi_walk_namespace+0xc0/0xc0 [1.969547] [] acpi_get_devices+0x5d/0x72 [1.969560] [] ? ispnpidacpi+0x84/0x84 [1.969571] [] ? pnpacpi_add_device_handler+0x217/0x217 [1.969584] [] pnpacpi_init+0x5e/0x8c [1.969596] [] do_one_initcall+0x8e/0x12b [1.969608] [] ? parameq+0x1d/0x1f [1.969619] [] ? parse_args+0x18c/0x23f [1.969632] [] kernel_init_freeable+0x115/0x196 [1.969643] [] ? do_early_param+0x88/0x88 [1.969654] [] ? rest_init+0x131/0x131 [1.969665] [] kernel_init+0x9/0xd1 [1.969676] [] ret_from_fork+0x7c/0xb0 [1.969687] [] ? rest_init+0x131/0x131 -- 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.11.0-rc4 (Linus GIT) -- WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185 can_stop_full_tick+0x7e/0x89()
I am not seeing any problems in the behavior of the computer, but wonder if this indicates something that needs fixing. [1.969109] WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185 can_stop_full_tick+0x7e/0x89() [1.969121] NO_HZ FULL will not work with unstable sched clock [1.969129] Modules linked in: [1.969142] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc4 #150 [1.969152] Hardware name: ASUSTeK Computer Inc. UL50VT /UL50VT, BIOS 217 03/01/2010 [1.969166] 88013f303eb0 8138347b 88013f303ef8 [1.969183] 88013f303ee8 8103454f 81079bbf 88013f30d7b0 [1.969199] 0001 88013a801dc0 88013a802240 88013f303f48 [1.969216] Call Trace: [1.969222] IRQ [8138347b] dump_stack+0x4e/0x82 [1.969241] [8103454f] warn_slowpath_common+0x75/0x8e [1.969253] [81079bbf] ? can_stop_full_tick+0x7e/0x89 [1.969265] [810345af] warn_slowpath_fmt+0x47/0x49 [1.969278] [81079bbf] can_stop_full_tick+0x7e/0x89 [1.969290] [8107a046] tick_nohz_irq_exit+0x63/0x7f [1.969302] [810384ec] irq_exit+0xa4/0xac [1.969314] [810239e8] smp_apic_timer_interrupt+0x30/0x3c [1.969327] [8138ef6f] apic_timer_interrupt+0x6f/0x80 [1.969336] EOI [8100c676] ? save_stack_trace+0x26/0x41 [1.969355] [813893cd] ? _raw_spin_unlock_irqrestore+0x3c/0x69 [1.969369] [813810fb] __slab_free+0x53/0x317 [1.969382] [811f08c6] ? debug_check_no_obj_freed+0x103/0x153 [1.969397] [810eb271] kfree+0x102/0x111 [1.969410] [81237171] ? acpi_ns_get_node+0xb6/0xc6 [1.969422] [81237171] acpi_ns_get_node+0xb6/0xc6 [1.969434] [813893ec] ? _raw_spin_unlock_irqrestore+0x5b/0x69 [1.969447] [81053a3a] ? up+0x34/0x39 [1.969459] [812198d2] ? acpi_os_signal_semaphore+0x1c/0x28 [1.969472] [81237aa0] acpi_get_handle+0x7e/0x92 [1.969486] [816aa050] pnpacpi_add_device_handler+0x57/0x217 [1.969499] [812378ca] acpi_ns_get_device_callback+0x135/0x14b [1.969511] [81053a3a] ? up+0x34/0x39 [1.969523] [8123728f] acpi_ns_walk_namespace+0xc3/0x17a [1.969535] [81237795] ? acpi_walk_namespace+0xc0/0xc0 [1.969547] [812376c0] acpi_get_devices+0x5d/0x72 [1.969560] [816a9ff9] ? ispnpidacpi+0x84/0x84 [1.969571] [816aa210] ? pnpacpi_add_device_handler+0x217/0x217 [1.969584] [816aa26e] pnpacpi_init+0x5e/0x8c [1.969596] [81000276] do_one_initcall+0x8e/0x12b [1.969608] [8104d796] ? parameq+0x1d/0x1f [1.969619] [8104d924] ? parse_args+0x18c/0x23f [1.969632] [81684dd4] kernel_init_freeable+0x115/0x196 [1.969643] [816846b4] ? do_early_param+0x88/0x88 [1.969654] [81379a6d] ? rest_init+0x131/0x131 [1.969665] [81379a76] kernel_init+0x9/0xd1 [1.969676] [8138e26c] ret_from_fork+0x7c/0xb0 [1.969687] [81379a6d] ? rest_init+0x131/0x131 -- 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/
Linus GIT 3.8.0-rc5: INFO: possible circular locking dependency detected -- ((fb_notifier_list).rwsem){.+.+.+}, at: [] __blocking_notifier_call_chain+0x49/0x80
Hi Daniel,
At the bottom of this message you will find dmesg output showing this
problem from the current Linus GIT tree.
Here is the test of the message you wrote about this
(http://marc.info/?l=dri-devel=135905755124554=2):
--
Patches for the know issues around console_lock vs fbdev_notifier are in -mm:
http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover.patch
http://ozlabs.org/~akpm/mmots/broken-out/fb-yet-another-band-aid-for-fixing-lockdep-mess.patch
Unfortunately the patches seem to be stuck there for now despite quite
a few reports about this (including seemingly relevant background
noise about hangs in distro bugzillas).
-Daniel
--
[ 489.832113] [ INFO: possible circular locking dependency detected ]
[ 489.832115] 3.8.0-rc5 #99 Not tainted
[ 489.832116] ---
[ 489.832117] 99video/4306 is trying to acquire lock:
[ 489.832129] ((fb_notifier_list).rwsem){.+.+.+}, at:
[] __blocking_notifier_call_chain+0x49/0x80
[ 489.832130]
[ 489.832130] but task is already holding lock:
[ 489.832136] (console_lock){+.+.+.}, at: []
store_fbstate+0x43/0x71
[ 489.832137]
[ 489.832137] which lock already depends on the new lock.
[ 489.832137]
[ 489.832138]
[ 489.832138] the existing dependency chain (in reverse order) is:
[ 489.832141]
[ 489.832141] -> #1 (console_lock){+.+.+.}:
[ 489.832146][] lock_acquire+0xfe/0x14d
[ 489.832150][] console_lock+0x64/0x66
[ 489.832154][] register_con_driver+0x33/0x123
[ 489.832158][] take_over_console+0x21/0x266
[ 489.832161][] fbcon_takeover+0x56/0x98
[ 489.832165][] fbcon_event_notify+0x3b6/0x6e4
[ 489.832169][] notifier_call_chain+0x8c/0xc0
[ 489.832173][]
__blocking_notifier_call_chain+0x5f/0x80
[ 489.832176][] blocking_notifier_call_chain+0xf/0x11
[ 489.832181][] fb_notifier_call_chain+0x16/0x18
[ 489.832184][] register_framebuffer+0x216/0x27a
[ 489.832189][] vesafb_probe+0x6df/0x75f
[ 489.832193][] platform_drv_probe+0x34/0x5e
[ 489.832196][] driver_probe_device+0x90/0x19b
[ 489.832199][] __driver_attach+0x4e/0x6f
[ 489.832202][] bus_for_each_dev+0x52/0x85
[ 489.832205][] driver_attach+0x19/0x1b
[ 489.832208][] bus_add_driver+0xf7/0x21a
[ 489.832211][] driver_register+0x8c/0x110
[ 489.832214][] platform_driver_register+0x41/0x43
[ 489.832217][] platform_driver_probe+0x18/0x8a
[ 489.832220][] vesafb_init+0x215/0x258
[ 489.832224][] do_one_initcall+0x7a/0x130
[ 489.832228][] kernel_init_freeable+0x109/0x191
[ 489.832233][] kernel_init+0x9/0xd1
[ 489.832236][] ret_from_fork+0x7c/0xb0
[ 489.832240]
[ 489.832240] -> #0 ((fb_notifier_list).rwsem){.+.+.+}:
[ 489.832242][] __lock_acquire+0xacc/0xe0c
[ 489.832245][] lock_acquire+0xfe/0x14d
[ 489.832249][] down_read+0x3f/0x4b
[ 489.832253][]
__blocking_notifier_call_chain+0x49/0x80
[ 489.832257][] blocking_notifier_call_chain+0xf/0x11
[ 489.832260][] fb_notifier_call_chain+0x16/0x18
[ 489.832263][] fb_set_suspend+0x22/0x4b
[ 489.832266][] store_fbstate+0x4e/0x71
[ 489.832270][] dev_attr_store+0x13/0x1f
[ 489.832274][] sysfs_write_file+0xe9/0x121
[ 489.832278][] vfs_write+0x91/0xd0
[ 489.832281][] sys_write+0x5a/0x8b
[ 489.832284][] system_call_fastpath+0x16/0x1b
[ 489.832285]
[ 489.832285] other info that might help us debug this:
[ 489.832285]
[ 489.832286] Possible unsafe locking scenario:
[ 489.832286]
[ 489.832287]CPU0CPU1
[ 489.832288]
[ 489.832290] lock(console_lock);
[ 489.832292]lock((fb_notifier_list).rwsem);
[ 489.832294]lock(console_lock);
[ 489.832296] lock((fb_notifier_list).rwsem);
[ 489.832297]
[ 489.832297] *** DEADLOCK ***
[ 489.832297]
[ 489.832298] 4 locks held by 99video/4306:
[ 489.832304] #0: (>mutex){+.+.+.}, at:
[] sysfs_write_file+0x37/0x121
[ 489.832310] #1: (s_active#204){.+.+.+}, at: []
sysfs_write_file+0xd1/0x121
[ 489.832315] #2: (_info->lock){+.+.+.}, at:
[] lock_fb_info+0x18/0x37
[ 489.832321] #3: (console_lock){+.+.+.}, at: []
store_fbstate+0x43/0x71
[ 489.832321]
[ 489.832321] stack backtrace:
[ 489.832324] Pid: 4306, comm: 99video Not tainted 3.8.0-rc5 #99
[ 489.832325] Call Trace:
[ 489.832330] [] print_circular_bug+0x1f6/0x204
[ 489.832333] [] __lock_acquire+0xacc/0xe0c
[ 489.832337] [] lock_acquire+0xfe/0x14d
[ 489.832341] [] ? __blocking_notifier_call_chain+0x49/0x80
[ 489.832345] [] down_read+0x3f/0x4b
[ 489.832348] [] ? __blocking_notifier_call_chain+0x49/0x80
[ 489.832352] []
Linus GIT 3.8.0-rc5: INFO: possible circular locking dependency detected -- ((fb_notifier_list).rwsem){.+.+.+}, at: [ffffffff81052611] __blocking_notifier_call_chain+0x49/0x80
Hi Daniel,
At the bottom of this message you will find dmesg output showing this
problem from the current Linus GIT tree.
Here is the test of the message you wrote about this
(http://marc.info/?l=dri-develm=135905755124554w=2):
--
Patches for the know issues around console_lock vs fbdev_notifier are in -mm:
http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover.patch
http://ozlabs.org/~akpm/mmots/broken-out/fb-yet-another-band-aid-for-fixing-lockdep-mess.patch
Unfortunately the patches seem to be stuck there for now despite quite
a few reports about this (including seemingly relevant background
noise about hangs in distro bugzillas).
-Daniel
--
[ 489.832113] [ INFO: possible circular locking dependency detected ]
[ 489.832115] 3.8.0-rc5 #99 Not tainted
[ 489.832116] ---
[ 489.832117] 99video/4306 is trying to acquire lock:
[ 489.832129] ((fb_notifier_list).rwsem){.+.+.+}, at:
[81052611] __blocking_notifier_call_chain+0x49/0x80
[ 489.832130]
[ 489.832130] but task is already holding lock:
[ 489.832136] (console_lock){+.+.+.}, at: [8125d25e]
store_fbstate+0x43/0x71
[ 489.832137]
[ 489.832137] which lock already depends on the new lock.
[ 489.832137]
[ 489.832138]
[ 489.832138] the existing dependency chain (in reverse order) is:
[ 489.832141]
[ 489.832141] - #1 (console_lock){+.+.+.}:
[ 489.832146][81079aa8] lock_acquire+0xfe/0x14d
[ 489.832150][8102f680] console_lock+0x64/0x66
[ 489.832154][812b06ef] register_con_driver+0x33/0x123
[ 489.832158][812b0f13] take_over_console+0x21/0x266
[ 489.832161][812617e0] fbcon_takeover+0x56/0x98
[ 489.832165][812652f4] fbcon_event_notify+0x3b6/0x6e4
[ 489.832169][8147584a] notifier_call_chain+0x8c/0xc0
[ 489.832173][81052627]
__blocking_notifier_call_chain+0x5f/0x80
[ 489.832176][81052657] blocking_notifier_call_chain+0xf/0x11
[ 489.832181][812582f2] fb_notifier_call_chain+0x16/0x18
[ 489.832184][812595de] register_framebuffer+0x216/0x27a
[ 489.832189][81ac6e48] vesafb_probe+0x6df/0x75f
[ 489.832193][81333d70] platform_drv_probe+0x34/0x5e
[ 489.832196][8133254b] driver_probe_device+0x90/0x19b
[ 489.832199][813326a4] __driver_attach+0x4e/0x6f
[ 489.832202][81330d02] bus_for_each_dev+0x52/0x85
[ 489.832205][8133208a] driver_attach+0x19/0x1b
[ 489.832208][81331d49] bus_add_driver+0xf7/0x21a
[ 489.832211][81332bf3] driver_register+0x8c/0x110
[ 489.832214][81333805] platform_driver_register+0x41/0x43
[ 489.832217][8133381f] platform_driver_probe+0x18/0x8a
[ 489.832220][81ac6726] vesafb_init+0x215/0x258
[ 489.832224][81000232] do_one_initcall+0x7a/0x130
[ 489.832228][81aa4bfb] kernel_init_freeable+0x109/0x191
[ 489.832233][8145d421] kernel_init+0x9/0xd1
[ 489.832236][814786ec] ret_from_fork+0x7c/0xb0
[ 489.832240]
[ 489.832240] - #0 ((fb_notifier_list).rwsem){.+.+.+}:
[ 489.832242][8107925d] __lock_acquire+0xacc/0xe0c
[ 489.832245][81079aa8] lock_acquire+0xfe/0x14d
[ 489.832249][81470d7a] down_read+0x3f/0x4b
[ 489.832253][81052611]
__blocking_notifier_call_chain+0x49/0x80
[ 489.832257][81052657] blocking_notifier_call_chain+0xf/0x11
[ 489.832260][812582f2] fb_notifier_call_chain+0x16/0x18
[ 489.832263][812586d9] fb_set_suspend+0x22/0x4b
[ 489.832266][8125d269] store_fbstate+0x4e/0x71
[ 489.832270][8132e98f] dev_attr_store+0x13/0x1f
[ 489.832274][81163064] sysfs_write_file+0xe9/0x121
[ 489.832278][81106546] vfs_write+0x91/0xd0
[ 489.832281][81106738] sys_write+0x5a/0x8b
[ 489.832284][81478792] system_call_fastpath+0x16/0x1b
[ 489.832285]
[ 489.832285] other info that might help us debug this:
[ 489.832285]
[ 489.832286] Possible unsafe locking scenario:
[ 489.832286]
[ 489.832287]CPU0CPU1
[ 489.832288]
[ 489.832290] lock(console_lock);
[ 489.832292]lock((fb_notifier_list).rwsem);
[ 489.832294]lock(console_lock);
[ 489.832296] lock((fb_notifier_list).rwsem);
[ 489.832297]
[ 489.832297] *** DEADLOCK ***
[ 489.832297]
[ 489.832298] 4 locks held by 99video/4306:
[ 489.832304] #0: (buffer-mutex){+.+.+.}, at:
[81162fb2] sysfs_write_file+0x37/0x121
[ 489.832310] #1: (s_active#204){.+.+.+}, at:
3.6.0+ (GIT) -- BUG: sleeping function called from invalid context at kernel/mutex.c:269 in_atomic(): 0, irqs_disabled(): 1, pid: 3561, name: pm-suspend
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
numa_remove_cpu cpu 1 node 0: mask now 0
Broke affinity for irq 46
smpboot: CPU 1 is now offline
BUG: sleeping function called from invalid context at kernel/mutex.c:269
in_atomic(): 0, irqs_disabled(): 1, pid: 3561, name: pm-suspend
4 locks held by pm-suspend/3561:
#0: (>mutex){+.+.+.}, at: []
sysfs_write_file+0x37/0x121
#1: (s_active#98){.+.+.+}, at: []
sysfs_write_file+0xd1/0x121
#2: (autosleep_lock){+.+.+.}, at: []
pm_autosleep_lock+0x12/0x14
#3: (pm_mutex){+.+.+.}, at: [] pm_suspend+0x38/0x1b8
irq event stamp: 103458
hardirqs last enabled at (103457): []
__mutex_unlock_slowpath+0x101/0x125
hardirqs last disabled at (103458): []
arch_suspend_disable_irqs+0xa/0xc
softirqs last enabled at (103196): []
__do_softirq+0x12a/0x155
softirqs last disabled at (103171): [] call_softirq+0x1c/0x30
Pid: 3561, comm: pm-suspend Not tainted 3.6.0+ #26
Call Trace:
[] ? print_irqtrace_events+0x9d/0xa1
[] __might_sleep+0x19f/0x1a8
[] mutex_lock_nested+0x20/0x3b
[] ledtrig_cpu+0x3b/0x7b
[] ledtrig_cpu_syscore_suspend+0xe/0x15
[] syscore_suspend+0x78/0xfd
[] suspend_devices_and_enter+0x10f/0x201
[] pm_suspend+0xff/0x1b8
[] state_store+0x43/0x6c
[] kobj_attr_store+0xf/0x1b
[] sysfs_write_file+0xe9/0x121
[] vfs_write+0x9b/0xfd
[] ? trace_hardirqs_on+0xd/0xf
[] sys_write+0x4d/0x7a
[] tracesys+0xdd/0xe2
--
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.6.0+ (GIT) -- BUG: sleeping function called from invalid context at kernel/mutex.c:269 in_atomic(): 0, irqs_disabled(): 1, pid: 3561, name: pm-suspend
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
numa_remove_cpu cpu 1 node 0: mask now 0
Broke affinity for irq 46
smpboot: CPU 1 is now offline
BUG: sleeping function called from invalid context at kernel/mutex.c:269
in_atomic(): 0, irqs_disabled(): 1, pid: 3561, name: pm-suspend
4 locks held by pm-suspend/3561:
#0: (buffer-mutex){+.+.+.}, at: [8113cab6]
sysfs_write_file+0x37/0x121
#1: (s_active#98){.+.+.+}, at: [8113cb50]
sysfs_write_file+0xd1/0x121
#2: (autosleep_lock){+.+.+.}, at: [810616c2]
pm_autosleep_lock+0x12/0x14
#3: (pm_mutex){+.+.+.}, at: [8105c06c] pm_suspend+0x38/0x1b8
irq event stamp: 103458
hardirqs last enabled at (103457): [81460461]
__mutex_unlock_slowpath+0x101/0x125
hardirqs last disabled at (103458): [8105be25]
arch_suspend_disable_irqs+0xa/0xc
softirqs last enabled at (103196): [8103445d]
__do_softirq+0x12a/0x155
softirqs last disabled at (103171): [8146836c] call_softirq+0x1c/0x30
Pid: 3561, comm: pm-suspend Not tainted 3.6.0+ #26
Call Trace:
[8106b64e] ? print_irqtrace_events+0x9d/0xa1
[8104efcd] __might_sleep+0x19f/0x1a8
[81460345] mutex_lock_nested+0x20/0x3b
[81391cbb] ledtrig_cpu+0x3b/0x7b
[81391d29] ledtrig_cpu_syscore_suspend+0xe/0x15
[813329e9] syscore_suspend+0x78/0xfd
[8105bf42] suspend_devices_and_enter+0x10f/0x201
[8105c133] pm_suspend+0xff/0x1b8
[8105b4fa] state_store+0x43/0x6c
[811c5ba6] kobj_attr_store+0xf/0x1b
[8113cb68] sysfs_write_file+0xe9/0x121
[810e48a3] vfs_write+0x9b/0xfd
[8106bc63] ? trace_hardirqs_on+0xd/0xf
[810e4ac6] sys_write+0x4d/0x7a
[814672f4] tracesys+0xdd/0xe2
--
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/
Why is there no nouveau driver maintainer listed in MAINTAINERS?
I would like to report an issue in the nouveau driver, but don't know who to report it to. Thanks, Miles -- 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/
Why is there no nouveau driver maintainer listed in MAINTAINERS?
I would like to report an issue in the nouveau driver, but don't know who to report it to. Thanks, Miles -- 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: 2.6.24-git20 -- BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:449
I don't believe it is related to this patch, but while testing, I tried running "find /proc | xargs cat" and "find /proc | xargs head" and "find /proc | xargs tail" and "ls -aR /" all at once. Everything seemed to be running great. Firefox continued to be highly responsive. I did notice that one of the command line processes had stopped scrolling text. After sending my approval message just now, I killed all the command line processes. Then I noticed that the frequency scaling monitor remained pegged for both CPUs in my Duo 2 Core processor. I ran top, and everything looked okay. As far as I can tell, top thinks the CPU is mostly idling. However, as I write this my fan is going full speed. I looked in my dmesg output and see no sign of an OOPS, a BUG or and INFO message. top - 23:01:03 up 13 min, 2 users, load average: 0.13, 0.70, 0.58 Tasks: 128 total, 2 running, 126 sleeping, 0 stopped, 0 zombie Cpu(s): 1.5%us, 1.6%sy, 0.0%ni, 96.9%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 2060928k total, 855628k used, 1205300k free, 155704k buffers Swap: 570268k total,0k used, 570268k free, 259780k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 3879 root 20 0 356m 16m 8212 R2 0.8 1:58.43 Xorg 4377 miles 20 0 20948 8276 6992 S1 0.4 0:07.75 multiload-apple 5099 miles 20 0 75368 22m 12m S1 1.1 0:01.06 gnome-terminal 5176 miles 20 0 2304 1108 836 R1 0.1 0:00.47 top 9 root -2 -5 000 S0 0.0 0:00.25 group_balance 3344 messageb 20 0 3028 1212 732 S0 0.1 0:00.85 dbus-daemon 3406 haldaemo 20 0 6112 3764 3152 S0 0.2 0:00.81 hald 1 root 20 0 2972 1856 532 S0 0.1 0:00.77 init 2 root 15 -5 000 S0 0.0 0:00.00 kthreadd [ 868.025460] power_supply BAT1: uevent [ 868.025467] power_supply BAT1: POWER_SUPPLY_NAME=BAT1 [ 868.025475] power_supply BAT1: Static prop TYPE=Battery [ 868.025480] power_supply BAT1: 12 dynamic props [ 868.025486] power_supply BAT1: prop STATUS=Full [ 868.025491] power_supply BAT1: prop PRESENT=1 [ 868.025496] power_supply BAT1: prop TECHNOLOGY=Li-ion [ 868.025503] power_supply BAT1: prop VOLTAGE_MIN_DESIGN=1480 [ 868.025508] power_supply BAT1: prop VOLTAGE_NOW=16715000 [ 868.025515] power_supply BAT1: prop CURRENT_NOW=0 [ 868.025520] power_supply BAT1: prop CHARGE_FULL_DESIGN=480 [ 868.025526] power_supply BAT1: prop CHARGE_FULL=4164000 [ 868.025532] power_supply BAT1: prop CHARGE_NOW=416 [ 868.025539] power_supply BAT1: prop MODEL_NAME=MAL42b [ 868.025545] power_supply BAT1: prop MANUFACTURER=SMP-PAN24 [ 868.025552] power_supply BAT1: prop SERIAL_NUMBER= [ 738.719569] power_supply BAT1: uevent [ 738.719576] power_supply BAT1: POWER_SUPPLY_NAME=BAT1 [ 738.719583] power_supply BAT1: Static prop TYPE=Battery [ 738.719587] power_supply BAT1: 12 dynamic props [ 738.719592] power_supply BAT1: prop STATUS=Full [ 738.719597] power_supply BAT1: prop PRESENT=1 [ 738.719603] power_supply BAT1: prop TECHNOLOGY=Li-ion [ 738.719609] power_supply BAT1: prop VOLTAGE_MIN_DESIGN=1480 [ 738.719616] power_supply BAT1: prop VOLTAGE_NOW=16715000 [ 738.719622] power_supply BAT1: prop CURRENT_NOW=0 [ 738.719627] power_supply BAT1: prop CHARGE_FULL_DESIGN=480 [ 738.719633] power_supply BAT1: prop CHARGE_FULL=4164000 [ 738.719639] power_supply BAT1: prop CHARGE_NOW=416 [ 738.719646] power_supply BAT1: prop MODEL_NAME=MAL42b [ 738.719652] power_supply BAT1: prop MANUFACTURER=SMP-PAN24 [ 738.719658] power_supply BAT1: prop SERIAL_NUMBER= [ 738.722095] power_supply ACAD: uevent [ 738.722099] power_supply ACAD: POWER_SUPPLY_NAME=ACAD [ 738.722105] power_supply ACAD: Static prop TYPE=Mains [ 738.722110] power_supply ACAD: 1 dynamic props [ 738.722114] power_supply ACAD: prop ONLINE=1 I just ran: cpufreq-selector -c 0 -f 800 cpufreq-selector -c 1 -f 800 Now everything is quite and running normally, except that Gnome seems to no longer be increasing the frequency of the CPUs with the ondemand governor. top - 23:10:58 up 23 min, 2 users, load average: 0.09, 0.17, 0.34 Tasks: 132 total, 1 running, 131 sleeping, 0 stopped, 0 zombie Cpu(s): 6.4%us, 3.7%sy, 0.0%ni, 89.8%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 2060928k total, 948740k used, 1112188k free, 156636k buffers Swap: 570268k total,0k used, 570268k free, 260544k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 5240 miles 20 0 254m 106m 22m S 10 5.3 0:39.51 firefox-bin 3879 root 20 0 357m 16m 8664 S4 0.8 2:27.28 Xorg 4377 miles 20 0 20948 8276 6992 S2 0.4 0:15.21 multiload-apple 5099 miles 20 0 75552 23m 12m S1 1.1 0:02.31 gnome-terminal 5682 root 20 0 2304 1108 836 R1 0.1 0:00.52 top 7 root 15 -5 000 S0 0.0 0:00.37
Re: 2.6.24-git20 -- BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:449
Excellent. Your patch fixed it for me. Thanks, Miles -- 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: 2.6.24-git20 -- BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:449
Excellent. Your patch fixed it for me. Thanks, Miles -- 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.24-rc7 -- WARNING: at kernel/lockdep.c:2662 check_flags()
Is this an issue in the Totem code or in the kernel? Please, let me know if you need my .config file. [ 5446.835007] WARNING: at kernel/lockdep.c:2662 check_flags() [ 5446.835022] Pid: 6060, comm: totem-plugin-vi Not tainted 2.6.24-rc7 #1 [ 5446.835027] [] show_trace_log_lvl+0x1a/0x2f [ 5446.835041] [] show_trace+0x12/0x14 [ 5446.835047] [] dump_stack+0x6c/0x72 [ 5446.835052] [] check_flags+0xc5/0x194 [ 5446.835061] [] lock_acquire+0x49/0xac [ 5446.835066] [] _spin_lock+0x35/0x42 [ 5446.835074] [] do_futex+0x339/0x967 [ 5446.835080] [] sys_futex+0xc0/0xd3 [ 5446.835085] [] syscall_call+0x7/0xb [ 5446.835091] === [ 5446.835093] possible reason: unannotated irqs-on. [ 5446.835097] irq event stamp: 173320 [ 5446.835100] hardirqs last enabled at (173319): [] sysenter_past_esp+0xb2/0xc1 [ 5446.835106] hardirqs last disabled at (173320): [] ret_from_exception+0x15/0x18 [ 5446.835113] softirqs last enabled at (173298): [] __do_softirq+0xf7/0xff [ 5446.835123] softirqs last disabled at (173289): [] do_softirq+0x77/0xf8 -- 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.24-rc7 -- WARNING: at kernel/lockdep.c:2662 check_flags()
Is this an issue in the Totem code or in the kernel? Please, let me know if you need my .config file. [ 5446.835007] WARNING: at kernel/lockdep.c:2662 check_flags() [ 5446.835022] Pid: 6060, comm: totem-plugin-vi Not tainted 2.6.24-rc7 #1 [ 5446.835027] [c01052b3] show_trace_log_lvl+0x1a/0x2f [ 5446.835041] [c0105bca] show_trace+0x12/0x14 [ 5446.835047] [c0105f29] dump_stack+0x6c/0x72 [ 5446.835052] [c01409f7] check_flags+0xc5/0x194 [ 5446.835061] [c0143b9d] lock_acquire+0x49/0xac [ 5446.835066] [c031c5cb] _spin_lock+0x35/0x42 [ 5446.835074] [c01460f1] do_futex+0x339/0x967 [ 5446.835080] [c01467df] sys_futex+0xc0/0xd3 [ 5446.835085] [c0104202] syscall_call+0x7/0xb [ 5446.835091] === [ 5446.835093] possible reason: unannotated irqs-on. [ 5446.835097] irq event stamp: 173320 [ 5446.835100] hardirqs last enabled at (173319): [c01041b1] sysenter_past_esp+0xb2/0xc1 [ 5446.835106] hardirqs last disabled at (173320): [c0104071] ret_from_exception+0x15/0x18 [ 5446.835113] softirqs last enabled at (173298): [c012a44e] __do_softirq+0xf7/0xff [ 5446.835123] softirqs last disabled at (173289): [c0106642] do_softirq+0x77/0xf8 -- 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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem" AFTER suspend-to-disk/resume)
On Dec 21, 2007 3:00 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Fri, 21 Dec 2007 11:06:49 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote:
>
> > > >
> > > > How do I determine what comes next?
> > > >
> > >
> > > By comparing it with the /proc/iomem from prior to suspending the machine.
> > >
> >
> > The offending information seems to be "9000-9fff : Intel Flush Page"
>
> ah-hah. git-agpgart.patch
>
> > I hope this helps,
>
> It does, thanks.
>
> Dave, a `cat /proc/iomem' crashes after a suspend/resume cycle when it
> reaches the intel_private.ifp_resource record.
>
>
> intel_i915_configure() is called on each resume and it calls
> intel_i9xx_setup_flush() which zeroes out the already-registered `struct
> resource', causing core kernel to oops over a deref of
> parent/sibling/child.
>
> Probably this:
>
> --- a/drivers/char/agp/intel-agp.c~a
> +++ a/drivers/char/agp/intel-agp.c
> @@ -883,8 +883,6 @@ static void intel_i965_g33_setup_chipset
> static void intel_i9xx_setup_flush(void)
> {
> /* setup a resource for this object */
> - memset(_private.ifp_resource, 0,
> sizeof(intel_private.ifp_resource));
> -
> intel_private.ifp_resource.name = "Intel Flush Page";
> intel_private.ifp_resource.flags = IORESOURCE_MEM;
>
> _
>
>
> will be enough to prevent the crash, but I suspect a bit more than that
> will be needed.
>
I tested with the patch applied, and the stackdump did not occur.
However, I notice that the values listed for Intel Page Flush is
changed from the pre-suspend values:
Before the suspend:
9000-9fff : Intel Flush Page
After the resume:
-90001000 : Intel Flush Page
# patch -p1 < akpm.patch
patching file drivers/char/agp/intel-agp.c
Hunk #1 succeeded at 891 (offset 8 lines).
$ cat /proc/iomem
-0009f7ff : System RAM
0009f800-0009 : reserved
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-7f68 : System RAM
0010-0039e4a7 : Kernel code
0039e4a8-004f0983 : Kernel data
00553000-007ecdfb : Kernel bss
7f69-7f698fff : ACPI Tables
7f699000-7f6f : ACPI Non-volatile Storage
7f70-7fff : reserved
8800-8bff : PCI CardBus #05
8c00-8fff : PCI CardBus #05
-90001000 : Intel Flush Page
c000-cfff : :00:02.0
d000-d1ff : PCI Bus #02
d200-d3ff : PCI Bus #03
d400-d5ff : PCI Bus #02
d400-d4003fff : :02:00.0
d400-d4003fff : sky2
d600-d7ff : PCI Bus #03
d600-d6000fff : :03:00.0
d600-d6000fff : iwl3945
d800-d80f : PCI Bus #04
d800-d8003fff : :04:09.1
d8004000-d8004fff : :04:09.2
d8004000-d8004fff : tifm_7xx1
d8005000-d80057ff : :04:09.1
d8005000-d80057ff : ohci1394
d8006000-d8006fff : :04:09.0
d8006000-d8006fff : yenta_socket
d810-d817 : :00:02.0
d818-d81f : :00:02.1
d820-d823 : :00:02.0
d824-d8243fff : :00:1b.0
d824-d8243fff : ICH HD audio
d8444000-d84443ff : :00:1d.7
d8444000-d84443ff : ehci_hcd
d800-d84447ff : :00:1f.2
d800-d84447ff : ahci
e000-efff : PCI MMCONFIG 0
e000-efff : reserved
fec0-fec0 : reserved
fed0-fed003ff : HPET 0
fed0-fed003ff : reserved
fed14000-fed19fff : reserved
fed1c000-fed8 : reserved
fee0-fee00fff : reserved
ff00- : reserved
--
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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem" AFTER suspend-to-disk/resume)
On Dec 21, 2007 1:29 AM, Andrew Morton <[EMAIL PROTECTED]> wrote: > > On Fri, 21 Dec 2007 00:58:19 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote: > > > On Dec 20, 2007 12:32 PM, Andrew Morton <[EMAIL PROTECTED]> wrote: > > > > > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]> > > > wrote: > > > > > > > On further investigation, "cat /proc/iomem" does not trigger the stack > > > > trace until after a suspend-to-disk/resume cycle has occurred. > > > > > > I still can't reproduce this. > > > > > > Could you please try this? > > > > > > - cat /proc/iomem > > > - suspend/resume > > > - do > > > > > > while read i > > > do > > > echo $i > > > sleep 1 > > > done < /proc/iomem > > > > > > then, with luck, we'll be able to work out which /proc/iomem record > > > immediately precedes the corrupted one. > > > > > > > [EMAIL PROTECTED]:~$ cat > test.sh > > while read i > > do > > echo $i > > sleep 1 > > done < /proc/iomem > > ^C > > [EMAIL PROTECTED]:~$ sh test.sh > > -0009f7ff : System RAM > > 0009f800-0009 : reserved > > 000a-000b : Video RAM area > > 000c-000c7fff : Video ROM > > 000f-000f : System ROM > > 0010-7f68 : System RAM > > 0010-0039e4b7 : Kernel code > > 0039e4b8-004f0983 : Kernel data > > 00553000-007ecdfb : Kernel bss > > 7f69-7f698fff : ACPI Tables > > 7f699000-7f6f : ACPI Non-volatile Storage > > 7f70-7fff : reserved > > 8800-8bff : PCI CardBus #05 > > 8c00-8fff : PCI CardBus #05 > > Segmentation fault > > > > How do I determine what comes next? > > > > By comparing it with the /proc/iomem from prior to suspending the machine. > The offending information seems to be "9000-9fff : Intel Flush Page" [EMAIL PROTECTED]:~# cat /proc/iomem -0009f7ff : System RAM 0009f800-0009 : reserved 000a-000b : Video RAM area 000c-000c7fff : Video ROM 000f-000f : System ROM 0010-7f68 : System RAM 0010-0039e4b7 : Kernel code 0039e4b8-004f0983 : Kernel data 00553000-007ecdfb : Kernel bss 7f69-7f698fff : ACPI Tables 7f699000-7f6f : ACPI Non-volatile Storage 7f70-7fff : reserved 8800-8bff : PCI CardBus #05 8c00-8fff : PCI CardBus #05 9000-9fff : Intel Flush Page c000-cfff : :00:02.0 d000-d1ff : PCI Bus #02 d200-d3ff : PCI Bus #03 d400-d5ff : PCI Bus #02 d400-d4003fff : :02:00.0 d400-d4003fff : sky2 d600-d7ff : PCI Bus #03 d600-d6000fff : :03:00.0 d600-d6000fff : iwl3945 d800-d80f : PCI Bus #04 d800-d8003fff : :04:09.1 d8004000-d8004fff : :04:09.2 d8004000-d8004fff : tifm_7xx1 d8005000-d80057ff : :04:09.1 d8005000-d80057ff : ohci1394 d8006000-d8006fff : :04:09.0 d8006000-d8006fff : yenta_socket d810-d817 : :00:02.0 d818-d81f : :00:02.1 d820-d823 : :00:02.0 d824-d8243fff : :00:1b.0 d824-d8243fff : ICH HD audio d8444000-d84443ff : :00:1d.7 d8444000-d84443ff : ehci_hcd d800-d84447ff : :00:1f.2 d800-d84447ff : ahci e000-efff : PCI MMCONFIG 0 e000-efff : reserved fec0-fec0 : reserved fed0-fed003ff : HPET 0 fed0-fed003ff : reserved fed14000-fed19fff : reserved fed1c000-fed8 : reserved fee0-fee00fff : reserved ff00- : reserved ~# lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corpor
Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by cat /proc/iomem AFTER suspend-to-disk/resume)
On Dec 21, 2007 1:29 AM, Andrew Morton [EMAIL PROTECTED] wrote: On Fri, 21 Dec 2007 00:58:19 -0500 Miles Lane [EMAIL PROTECTED] wrote: On Dec 20, 2007 12:32 PM, Andrew Morton [EMAIL PROTECTED] wrote: On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane [EMAIL PROTECTED] wrote: On further investigation, cat /proc/iomem does not trigger the stack trace until after a suspend-to-disk/resume cycle has occurred. I still can't reproduce this. Could you please try this? - cat /proc/iomem - suspend/resume - do while read i do echo $i sleep 1 done /proc/iomem then, with luck, we'll be able to work out which /proc/iomem record immediately precedes the corrupted one. [EMAIL PROTECTED]:~$ cat test.sh while read i do echo $i sleep 1 done /proc/iomem ^C [EMAIL PROTECTED]:~$ sh test.sh -0009f7ff : System RAM 0009f800-0009 : reserved 000a-000b : Video RAM area 000c-000c7fff : Video ROM 000f-000f : System ROM 0010-7f68 : System RAM 0010-0039e4b7 : Kernel code 0039e4b8-004f0983 : Kernel data 00553000-007ecdfb : Kernel bss 7f69-7f698fff : ACPI Tables 7f699000-7f6f : ACPI Non-volatile Storage 7f70-7fff : reserved 8800-8bff : PCI CardBus #05 8c00-8fff : PCI CardBus #05 Segmentation fault How do I determine what comes next? By comparing it with the /proc/iomem from prior to suspending the machine. The offending information seems to be 9000-9fff : Intel Flush Page [EMAIL PROTECTED]:~# cat /proc/iomem -0009f7ff : System RAM 0009f800-0009 : reserved 000a-000b : Video RAM area 000c-000c7fff : Video ROM 000f-000f : System ROM 0010-7f68 : System RAM 0010-0039e4b7 : Kernel code 0039e4b8-004f0983 : Kernel data 00553000-007ecdfb : Kernel bss 7f69-7f698fff : ACPI Tables 7f699000-7f6f : ACPI Non-volatile Storage 7f70-7fff : reserved 8800-8bff : PCI CardBus #05 8c00-8fff : PCI CardBus #05 9000-9fff : Intel Flush Page c000-cfff : :00:02.0 d000-d1ff : PCI Bus #02 d200-d3ff : PCI Bus #03 d400-d5ff : PCI Bus #02 d400-d4003fff : :02:00.0 d400-d4003fff : sky2 d600-d7ff : PCI Bus #03 d600-d6000fff : :03:00.0 d600-d6000fff : iwl3945 d800-d80f : PCI Bus #04 d800-d8003fff : :04:09.1 d8004000-d8004fff : :04:09.2 d8004000-d8004fff : tifm_7xx1 d8005000-d80057ff : :04:09.1 d8005000-d80057ff : ohci1394 d8006000-d8006fff : :04:09.0 d8006000-d8006fff : yenta_socket d810-d817 : :00:02.0 d818-d81f : :00:02.1 d820-d823 : :00:02.0 d824-d8243fff : :00:1b.0 d824-d8243fff : ICH HD audio d8444000-d84443ff : :00:1d.7 d8444000-d84443ff : ehci_hcd d800-d84447ff : :00:1f.2 d800-d84447ff : ahci e000-efff : PCI MMCONFIG 0 e000-efff : reserved fec0-fec0 : reserved fed0-fed003ff : HPET 0 fed0-fed003ff : reserved fed14000-fed19fff : reserved fed1c000-fed8 : reserved fee0-fee00fff : reserved ff00- : reserved ~# lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14) 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) 04:09.0 CardBus bridge: Texas
Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by cat /proc/iomem AFTER suspend-to-disk/resume)
On Dec 21, 2007 3:00 PM, Andrew Morton [EMAIL PROTECTED] wrote:
On Fri, 21 Dec 2007 11:06:49 -0500 Miles Lane [EMAIL PROTECTED] wrote:
How do I determine what comes next?
By comparing it with the /proc/iomem from prior to suspending the machine.
The offending information seems to be 9000-9fff : Intel Flush Page
ah-hah. git-agpgart.patch
I hope this helps,
It does, thanks.
Dave, a `cat /proc/iomem' crashes after a suspend/resume cycle when it
reaches the intel_private.ifp_resource record.
intel_i915_configure() is called on each resume and it calls
intel_i9xx_setup_flush() which zeroes out the already-registered `struct
resource', causing core kernel to oops over a deref of
parent/sibling/child.
Probably this:
--- a/drivers/char/agp/intel-agp.c~a
+++ a/drivers/char/agp/intel-agp.c
@@ -883,8 +883,6 @@ static void intel_i965_g33_setup_chipset
static void intel_i9xx_setup_flush(void)
{
/* setup a resource for this object */
- memset(intel_private.ifp_resource, 0,
sizeof(intel_private.ifp_resource));
-
intel_private.ifp_resource.name = Intel Flush Page;
intel_private.ifp_resource.flags = IORESOURCE_MEM;
_
will be enough to prevent the crash, but I suspect a bit more than that
will be needed.
I tested with the patch applied, and the stackdump did not occur.
However, I notice that the values listed for Intel Page Flush is
changed from the pre-suspend values:
Before the suspend:
9000-9fff : Intel Flush Page
After the resume:
-90001000 : Intel Flush Page
# patch -p1 akpm.patch
patching file drivers/char/agp/intel-agp.c
Hunk #1 succeeded at 891 (offset 8 lines).
$ cat /proc/iomem
-0009f7ff : System RAM
0009f800-0009 : reserved
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-7f68 : System RAM
0010-0039e4a7 : Kernel code
0039e4a8-004f0983 : Kernel data
00553000-007ecdfb : Kernel bss
7f69-7f698fff : ACPI Tables
7f699000-7f6f : ACPI Non-volatile Storage
7f70-7fff : reserved
8800-8bff : PCI CardBus #05
8c00-8fff : PCI CardBus #05
-90001000 : Intel Flush Page
c000-cfff : :00:02.0
d000-d1ff : PCI Bus #02
d200-d3ff : PCI Bus #03
d400-d5ff : PCI Bus #02
d400-d4003fff : :02:00.0
d400-d4003fff : sky2
d600-d7ff : PCI Bus #03
d600-d6000fff : :03:00.0
d600-d6000fff : iwl3945
d800-d80f : PCI Bus #04
d800-d8003fff : :04:09.1
d8004000-d8004fff : :04:09.2
d8004000-d8004fff : tifm_7xx1
d8005000-d80057ff : :04:09.1
d8005000-d80057ff : ohci1394
d8006000-d8006fff : :04:09.0
d8006000-d8006fff : yenta_socket
d810-d817 : :00:02.0
d818-d81f : :00:02.1
d820-d823 : :00:02.0
d824-d8243fff : :00:1b.0
d824-d8243fff : ICH HD audio
d8444000-d84443ff : :00:1d.7
d8444000-d84443ff : ehci_hcd
d800-d84447ff : :00:1f.2
d800-d84447ff : ahci
e000-efff : PCI MMCONFIG 0
e000-efff : reserved
fec0-fec0 : reserved
fed0-fed003ff : HPET 0
fed0-fed003ff : reserved
fed14000-fed19fff : reserved
fed1c000-fed8 : reserved
fee0-fee00fff : reserved
ff00- : reserved
--
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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem" AFTER suspend-to-disk/resume)
Resending... Curse GMail's HTML messages! On Dec 21, 2007 12:58 AM, Miles Lane <[EMAIL PROTECTED]> wrote: > > On Dec 20, 2007 12:32 PM, Andrew Morton <[EMAIL PROTECTED]> wrote: > > > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]> wrote: > > > > > On further investigation, "cat /proc/iomem" does not trigger the stack > > > trace until after a suspend-to-disk/resume cycle has occurred. > > > > I still can't reproduce this. > > > > Could you please try this? > > > > - cat /proc/iomem > > - suspend/resume > > - do > > > > while read i > > do > > echo $i > > sleep 1 > > done < /proc/iomem > > > > then, with luck, we'll be able to work out which /proc/iomem record > > immediately precedes the corrupted one. > > > > [EMAIL PROTECTED]:~$ cat > test.sh > > while read i > do > echo $i > sleep 1 > done < /proc/iomem > ^C > [EMAIL PROTECTED]:~$ sh test.sh > -0009f7ff : System RAM > 0009f800-0009 : reserved > 000a-000b : Video RAM area > 000c-000c7fff : Video ROM > 000f-000f : System ROM > 0010-7f68 : System RAM > 0010-0039e4b7 : Kernel code > 0039e4b8-004f0983 : Kernel data > 00553000-007ecdfb : Kernel bss > 7f69-7f698fff : ACPI Tables > 7f699000-7f6f : ACPI Non-volatile Storage > 7f70-7fff : reserved > 8800-8bff : PCI CardBus #05 > 8c00-8fff : PCI CardBus #05 > Segmentation fault > > How do I determine what comes next? > > Thanks, > Miles > -- 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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem" AFTER suspend-to-disk/resume)
On further investigation, "cat /proc/iomem" does not trigger the stack trace until after a suspend-to-disk/resume cycle has occurred. I am removing Ingo and Russell from the TO list (as they are apparently the wrong people) and adding the suspend folks, as suspend is implicated. My .config file can be found here: http://marc.info/?l=linux-kernel=119812903001296=2 Miles Lane wrote: .config attached in order to not trip spam filters. Miles Lane wrote: [ 252.868386] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 252.868393] printing ip: c012d527 *pde = [ 252.868399] Oops: [#1] SMP [ 252.868403] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 252.868407] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi snd_hda_intel snd_pcm_oss snd_mixer_oss pcmcia snd_pcm iTCO_wdt iTCO_vendor_support snd_seq_dummy watchdog_core watchdog_dev snd_seq_oss snd_seq_midi tifm_7xx1 snd_rawmidi iwl3945 snd_seq_midi_event rng_core tifm_core mac80211 snd_seq snd_timer snd_seq_device cfg80211 sky2 battery yenta_socket rsrc_nonstatic pcmcia_core ac snd soundcore snd_page_alloc button shpchp pci_hotplug sr_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 252.868469] [ 252.868472] Pid: 7088, comm: head Not tainted (2.6.24-rc5-mm1 #9) [ 252.868476] EIP: 0060:[] EFLAGS: 00010297 CPU: 0 [ 252.868481] EIP is at r_show+0x2a/0x70 [ 252.868483] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 252.868486] ESI: 0008 EDI: ed1f52c0 EBP: f5320f10 ESP: f5320f04 [ 252.868489] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 252.868493] Process head (pid: 7088, ti=f532 task=f532e000 task.ti=f532) [ 252.868495] Stack: c03a6cac ed1f52c0 c07e3224 f5320f50 c0199a7e 2000 bf930807 e1007800 [ 252.868504]ed1f52e0 01d3 000e 000d [ 252.868512]fffb f7d39370 c01998e4 f5320f74 c01af4f5 f5320f9c 2000 bf930807 [ 252.868521] Call Trace: [ 252.868523] [] show_trace_log_lvl+0x12/0x25 [ 252.868529] [] show_stack_log_lvl+0x8a/0x95 [ 252.868534] [] show_registers+0x8c/0x154 [ 252.868538] [] die+0x10e/0x1d2 [ 252.868542] [] do_page_fault+0x52b/0x600 [ 252.868547] [] error_code+0x72/0x78 [ 252.868552] [] seq_read+0x19a/0x26c [ 252.868557] [] proc_reg_read+0x60/0x74 [ 252.868562] [] vfs_read+0xa2/0x11e [ 252.868567] [] sys_read+0x3b/0x60 [ 252.868571] [] sysenter_past_esp+0x6b/0xc1 [ 252.868575] === [ 252.868577] Code: c3 55 89 d1 89 e5 57 89 c7 56 53 8b 50 64 83 7a 0c 00 77 0e 81 7a 08 ff ff 00 00 be 04 00 00 00 76 05 be 08 00 00 00 89 c8 31 db <8b> 40 18 39 d0 74 06 43 83 fb 05 75 f3 8b 41 10 ba 2f 1b 45 c0 [ 252.868623] EIP: [] r_show+0x2a/0x70 SS:ESP 0068:f5320f04 -- 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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem")
On Dec 20, 2007 6:37 AM, David Howells <[EMAIL PROTECTED]> wrote: > Andrew Morton <[EMAIL PROTECTED]> wrote: > > > I would be suspecting iget-stop-procfs-from-using-iget-and-read_inode.patch. > > I think your suspicions are very unlikely. The patch only affects > proc_get_inode() - and looking at the patch backtrace, it looks like the > system is successfully past that already (it's unlikely that > proc_reg_read+0x60/0x74 would have been reached otherwise). > > If my patch to procfs is wrong, it would affect all proc files and ought be > immediately detectable. I tested the patch Andrew sent. I ran "cat /proc/iomem" before trying a suspend-to-disk. It worked fine. Then I suspended and resumed. This time, "cat /proc/iomem" caused the stack trace to be generated. So, you are right, you patch is not the problem. Thanks, Miles -- 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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by cat /proc/iomem)
On Dec 20, 2007 6:37 AM, David Howells [EMAIL PROTECTED] wrote: Andrew Morton [EMAIL PROTECTED] wrote: I would be suspecting iget-stop-procfs-from-using-iget-and-read_inode.patch. I think your suspicions are very unlikely. The patch only affects proc_get_inode() - and looking at the patch backtrace, it looks like the system is successfully past that already (it's unlikely that proc_reg_read+0x60/0x74 would have been reached otherwise). If my patch to procfs is wrong, it would affect all proc files and ought be immediately detectable. I tested the patch Andrew sent. I ran cat /proc/iomem before trying a suspend-to-disk. It worked fine. Then I suspended and resumed. This time, cat /proc/iomem caused the stack trace to be generated. So, you are right, you patch is not the problem. Thanks, Miles -- 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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by cat /proc/iomem AFTER suspend-to-disk/resume)
On further investigation, cat /proc/iomem does not trigger the stack trace until after a suspend-to-disk/resume cycle has occurred. I am removing Ingo and Russell from the TO list (as they are apparently the wrong people) and adding the suspend folks, as suspend is implicated. My .config file can be found here: http://marc.info/?l=linux-kernelm=119812903001296w=2 Miles Lane wrote: .config attached in order to not trip spam filters. Miles Lane wrote: [ 252.868386] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 252.868393] printing ip: c012d527 *pde = [ 252.868399] Oops: [#1] SMP [ 252.868403] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 252.868407] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi snd_hda_intel snd_pcm_oss snd_mixer_oss pcmcia snd_pcm iTCO_wdt iTCO_vendor_support snd_seq_dummy watchdog_core watchdog_dev snd_seq_oss snd_seq_midi tifm_7xx1 snd_rawmidi iwl3945 snd_seq_midi_event rng_core tifm_core mac80211 snd_seq snd_timer snd_seq_device cfg80211 sky2 battery yenta_socket rsrc_nonstatic pcmcia_core ac snd soundcore snd_page_alloc button shpchp pci_hotplug sr_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 252.868469] [ 252.868472] Pid: 7088, comm: head Not tainted (2.6.24-rc5-mm1 #9) [ 252.868476] EIP: 0060:[c012d527] EFLAGS: 00010297 CPU: 0 [ 252.868481] EIP is at r_show+0x2a/0x70 [ 252.868483] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 252.868486] ESI: 0008 EDI: ed1f52c0 EBP: f5320f10 ESP: f5320f04 [ 252.868489] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 252.868493] Process head (pid: 7088, ti=f532 task=f532e000 task.ti=f532) [ 252.868495] Stack: c03a6cac ed1f52c0 c07e3224 f5320f50 c0199a7e 2000 bf930807 e1007800 [ 252.868504]ed1f52e0 01d3 000e 000d [ 252.868512]fffb f7d39370 c01998e4 f5320f74 c01af4f5 f5320f9c 2000 bf930807 [ 252.868521] Call Trace: [ 252.868523] [c0107d55] show_trace_log_lvl+0x12/0x25 [ 252.868529] [c0107df2] show_stack_log_lvl+0x8a/0x95 [ 252.868534] [c0107e89] show_registers+0x8c/0x154 [ 252.868538] [c010805f] die+0x10e/0x1d2 [ 252.868542] [c039c8c9] do_page_fault+0x52b/0x600 [ 252.868547] [c039af9a] error_code+0x72/0x78 [ 252.868552] [c0199a7e] seq_read+0x19a/0x26c [ 252.868557] [c01af4f5] proc_reg_read+0x60/0x74 [ 252.868562] [c018390d] vfs_read+0xa2/0x11e [ 252.868567] [c0183d02] sys_read+0x3b/0x60 [ 252.868571] [c0106bae] sysenter_past_esp+0x6b/0xc1 [ 252.868575] === [ 252.868577] Code: c3 55 89 d1 89 e5 57 89 c7 56 53 8b 50 64 83 7a 0c 00 77 0e 81 7a 08 ff ff 00 00 be 04 00 00 00 76 05 be 08 00 00 00 89 c8 31 db 8b 40 18 39 d0 74 06 43 83 fb 05 75 f3 8b 41 10 ba 2f 1b 45 c0 [ 252.868623] EIP: [c012d527] r_show+0x2a/0x70 SS:ESP 0068:f5320f04 -- 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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by cat /proc/iomem AFTER suspend-to-disk/resume)
Resending... Curse GMail's HTML messages! On Dec 21, 2007 12:58 AM, Miles Lane [EMAIL PROTECTED] wrote: On Dec 20, 2007 12:32 PM, Andrew Morton [EMAIL PROTECTED] wrote: On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane [EMAIL PROTECTED] wrote: On further investigation, cat /proc/iomem does not trigger the stack trace until after a suspend-to-disk/resume cycle has occurred. I still can't reproduce this. Could you please try this? - cat /proc/iomem - suspend/resume - do while read i do echo $i sleep 1 done /proc/iomem then, with luck, we'll be able to work out which /proc/iomem record immediately precedes the corrupted one. [EMAIL PROTECTED]:~$ cat test.sh while read i do echo $i sleep 1 done /proc/iomem ^C [EMAIL PROTECTED]:~$ sh test.sh -0009f7ff : System RAM 0009f800-0009 : reserved 000a-000b : Video RAM area 000c-000c7fff : Video ROM 000f-000f : System ROM 0010-7f68 : System RAM 0010-0039e4b7 : Kernel code 0039e4b8-004f0983 : Kernel data 00553000-007ecdfb : Kernel bss 7f69-7f698fff : ACPI Tables 7f699000-7f6f : ACPI Non-volatile Storage 7f70-7fff : reserved 8800-8bff : PCI CardBus #05 8c00-8fff : PCI CardBus #05 Segmentation fault How do I determine what comes next? Thanks, Miles -- 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: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem")
Okay. The command that directly triggers this is: cat /proc/iomem Here is the stack trace without the line-wrapping (sorry!): [ 251.602965] wlan0_rename: RX non-WEP frame, but expected encryption [ 252.868386] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 252.868393] printing ip: c012d527 *pde = [ 252.868399] Oops: [#1] SMP [ 252.868403] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 252.868407] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi snd_hda_intel snd_pcm_oss snd_mixer_oss pcmcia snd_pcm iTCO_wdt iTCO_vendor_support snd_seq_dummy watchdog_core watchdog_dev snd_seq_oss snd_seq_midi tifm_7xx1 snd_rawmidi iwl3945 snd_seq_midi_event rng_core tifm_core mac80211 snd_seq snd_timer snd_seq_device cfg80211 sky2 battery yenta_socket rsrc_nonstatic pcmcia_core ac snd soundcore snd_page_alloc button shpchp pci_hotplug sr_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 252.868469] [ 252.868472] Pid: 7088, comm: head Not tainted (2.6.24-rc5-mm1 #9) [ 252.868476] EIP: 0060:[] EFLAGS: 00010297 CPU: 0 [ 252.868481] EIP is at r_show+0x2a/0x70 [ 252.868483] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 252.868486] ESI: 0008 EDI: ed1f52c0 EBP: f5320f10 ESP: f5320f04 [ 252.868489] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 252.868493] Process head (pid: 7088, ti=f532 task=f532e000 task.ti=f532) [ 252.868495] Stack: c03a6cac ed1f52c0 c07e3224 f5320f50 c0199a7e 2000 bf930807 e1007800 [ 252.868504]ed1f52e0 01d3 000e 000d [ 252.868512]fffb f7d39370 c01998e4 f5320f74 c01af4f5 f5320f9c 2000 bf930807 [ 252.868521] Call Trace: [ 252.868523] [] show_trace_log_lvl+0x12/0x25 [ 252.868529] [] show_stack_log_lvl+0x8a/0x95 [ 252.868534] [] show_registers+0x8c/0x154 [ 252.868538] [] die+0x10e/0x1d2 [ 252.868542] [] do_page_fault+0x52b/0x600 [ 252.868547] [] error_code+0x72/0x78 [ 252.868552] [] seq_read+0x19a/0x26c [ 252.868557] [] proc_reg_read+0x60/0x74 [ 252.868562] [] vfs_read+0xa2/0x11e [ 252.868567] [] sys_read+0x3b/0x60 [ 252.868571] [] sysenter_past_esp+0x6b/0xc1 [ 252.868575] === [ 252.868577] Code: c3 55 89 d1 89 e5 57 89 c7 56 53 8b 50 64 83 7a 0c 00 77 0e 81 7a 08 ff ff 00 00 be 04 00 00 00 76 05 be 08 00 00 00 89 c8 31 db <8b> 40 18 39 d0 74 06 43 83 fb 05 75 f3 8b 41 10 ba 2f 1b 45 c0 [ 252.868623] EIP: [] r_show+0x2a/0x70 SS:ESP 0068:f5320f04 -- 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/
OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70
I have the patch "find /proc | xargs tail" [ 50.595474] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 54.733829] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 54.733836] printing ip: c012d527 *pde = [ 54.733843] Oops: [#1] SMP [ 54.733847] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 54.733851] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi pcmcia snd_hda_intel snd_pcm_oss snd_mixer_oss iwl3945 snd_pcm snd_seq_dumm y mac80211 snd_seq_oss cfg80211 sky2 tifm_7xx1 yenta_socket rsrc_nonstatic pcmcia_core tifm_core iTCO_wdt iTCO_vendor_support watchdog_core watchdog_dev snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq rng_core snd_timer snd_seq_device shpchp pci_hotplug battery snd ac button soundcore snd_page_alloc s r_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 54.733915] [ 54.733918] Pid: 5703, comm: tail Not tainted (2.6.24-rc5-mm1 #9) [ 54.733921] EIP: 0060:[] EFLAGS: 00210297 CPU: 1 [ 54.733926] EIP is at r_show+0x2a/0x70 [ 54.733928] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 54.733931] ESI: 0008 EDI: efbe9420 EBP: eed41f10 ESP: eed41f04 [ 54.733934] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 54.733938] Process tail (pid: 5703, ti=eed41000 task=ee5a8000 task.ti=eed41000) [ 54.733940] Stack: c03a6cac efbe9420 c07e3224 eed41f50 c0199a7e 2000 097d1f20 e1112500 [ 54.733949]efbe9440 01d3 000e 000d [ 54.733958]fffb f7d79210 c01998e4 eed41f74 c01af4f5 eed41f9c 2000 097d1f20 [ 54.733966] Call Trace: [ 54.733968] [] show_trace_log_lvl+0x12/0x25 [ 54.733975] [] show_stack_log_lvl+0x8a/0x95 [ 54.733980] [] show_registers+0x8c/0x154 [ 54.733984] [] die+0x10e/0x1d2 [ 54.733988] [] do_page_fault+0x52b/0x600 [ 54.733993] [] error_code+0x72/0x78 [ 54.733998] [] seq_read+0x19a/0x26c [ 54.734004] [] proc_reg_read+0x60/0x74 [ 54.734009] [] vfs_read+0xa2/0x11e [ 54.734015] [] sys_read+0x3b/0x60 [ 54.734019] [] sysenter_past_esp+0x6b/0xc1 [ 54.734023] === [ 54.734025] Code: c3 55 89 d1 89 e5 57 89 c7 56 53 8b 50 64 83 7a 0c 00 77 0e 81 7a 08 ff ff 00 00 be 04 00 00 00 76 05 be 08 00 00 00 89 c8 31 db <8b > 40 18 39 d0 74 06 43 83 fb 05 75 f3 8b 41 10 ba 2f 1b 45 c0 [ 54.734071] EIP: [] r_show+0x2a/0x70 SS:ESP 0068:eed41f04 [ 55.363749] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 55.363756] printing ip: c012d527 *pde = [ 55.363762] Oops: [#2] SMP [ 55.363766] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 55.363770] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi pcmcia snd_hda_intel snd_pcm_oss snd_mixer_oss iwl3945 snd_pcm snd_seq_dumm y mac80211 snd_seq_oss cfg80211 sky2 tifm_7xx1 yenta_socket rsrc_nonstatic pcmcia_core tifm_core iTCO_wdt iTCO_vendor_support watchdog_core watchdog_dev snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq rng_core snd_timer snd_seq_device shpchp pci_hotplug battery snd ac button soundcore snd_page_alloc s r_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 55.363834] [ 55.363837] Pid: 5710, comm: tail Tainted: G D (2.6.24-rc5-mm1 #9) [ 55.363840] EIP: 0060:[] EFLAGS: 00210297 CPU: 1 [ 55.363845] EIP is at r_show+0x2a/0x70 [ 55.363848] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 55.363851] ESI: 0008 EDI: efbe9420 EBP: ee5a8f10 ESP: ee5a8f04 [ 55.363854] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 55.363857] Process tail (pid: 5710, ti=ee5a8000 task=f76ae000 task.ti=ee5a8000) [ 55.363860] Stack: c03a6cac efbe9420 c07e3224 ee5a8f50 c0199a7e 2000 09e26f20 f7036d00 [ 55.363868]efbe9440 01d3 000e 000d [ 55.363877]fffb f7d79210 c01998e4 ee5a8f74 c01af4f5 ee5a8f9c 2000 09e26f20 [ 55.363885] Call Trace: [ 55.363887] [] show_trace_log_lvl+0x12/0x25 [ 55.363894] [] show_stack_log_lvl+0x8a/0x95 [ 55.363898] [] show_registers+0x8c/0x154 [ 55.363902] [] die+0x10e/0x1d2 [ 55.363906] [] do_page_fault+0x52b/0x600 [ 55.363911] [] error_code+0x72/0x78 [ 55.363915] [] seq_read+0x19a/0x26c [ 55.363921] [] proc_reg_read+0x60/0x74 [ 55.363925] [] vfs_read+0xa2/0x11e [ 55.363930] [] sys_read+0x3b/0x60 [ 55.363934] [] sysenter_past_esp+0x6b/0xc1 [ 55.363938] === [ 55.363940] Code: c3
Re: 2.6.24-rc5-mm1 -- inconsistent {in-hardirq-W} -> {hardirq-on-W} usage -- pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1]
On Dec 19, 2007 8:31 PM, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> On Thursday, 20 of December 2007, Miles Lane wrote:
> > On Dec 19, 2007 7:09 PM, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> >
> > > On Thursday, 20 of December 2007, Christoph Lameter wrote:
> > > > On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
> > > >
> > > > > > We could reexport drain_local_pages() again but then I do not
> > > understand
> > > > > > why we would only drain the pages of this processor and not of all
> > > other
> > > > > > processors as well. It seems that software suspend intend was to
> > > flush
> > > > > > them all right?
> > > > >
> > > > > Well, not exactly. We are on one CPU at this point, the others have
> > > been
> > > > > disabled.
> > > >
> > > > Ok so the others are flush. Here is a patch to re-export
> > > > drain_local_pages() again and use it for software suspend:
> > > >
> > > > Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
> > > >
> > > > ---
> > > > include/linux/gfp.h |1 +
> > > > kernel/power/snapshot.c |2 +-
> > > > mm/page_alloc.c |2 +-
> > > > 3 files changed, 3 insertions(+), 2 deletions(-)
> > > >
> > > > Index: linux-2.6.24-rc5-mm1/kernel/power/snapshot.c
> > > > ===
> > > > --- linux-2.6.24-rc5-mm1.orig/kernel/power/snapshot.c 2007-12-19 11:59:
> > > 25.233961700 -0800
> > > > +++ linux-2.6.24-rc5-mm1/kernel/power/snapshot.c 2007-12-19 15:16:
> > > 34.179661929 -0800
> > > > @@ -1203,7 +1203,7 @@ asmlinkage int swsusp_save(void)
> > > >
> > > > printk(KERN_INFO "PM: Creating hibernation image: \n");
> > > >
> > > > - drain_all_pages();
> > > > + drain_local_pages(NULL);
> > > > nr_pages = count_data_pages();
> > > > nr_highmem = count_highmem_pages();
> > > > printk(KERN_INFO "PM: Need to copy %u pages\n", nr_pages +
> > > nr_highmem);
> > >
> > > You've omitted the second instance, right before the copy_data_pages()
> > > call.
> > >
> >
> > I guess I will wait for a revised patch.
>
> There's an Andrew's fix on top of this one in -mm:
> http://marc.info/?l=linux-mm-commits=119810866812965=2
>
>
>
> > > > Index: linux-2.6.24-rc5-mm1/mm/page_alloc.c
> > > > ===
> > > > --- linux-2.6.24-rc5-mm1.orig/mm/page_alloc.c 2007-12-19 12:01:
> > > 00.630421258 -0800
> > > > +++ linux-2.6.24-rc5-mm1/mm/page_alloc.c 2007-12-19 15:12:
> > > 19.850545818 -0800
> > > > @@ -930,7 +930,7 @@ static void drain_pages(unsigned int cpu
> > > > /*
> > > > * Spill all of this CPU's per-cpu pages back into the buddy allocator.
> > > > */
> > > > -static void drain_local_pages(void *arg)
> > > > +void drain_local_pages(void *arg)
> > > > {
> > > > drain_pages(smp_processor_id());
> > > > }
> > > > Index: linux-2.6.24-rc5-mm1/include/linux/gfp.h
> > > > ===
> > > > --- linux-2.6.24-rc5-mm1.orig/include/linux/gfp.h 2007-12-19 15:13:
> > > 51.926950065 -0800
> > > > +++ linux-2.6.24-rc5-mm1/include/linux/gfp.h 2007-12-19 15:16:
> > > 11.951564369 -0800
> > > > @@ -229,5 +229,6 @@ extern void FASTCALL(free_cold_page(stru
> > > > void page_alloc_init(void);
> > > > void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp);
> > > > void drain_all_pages(void);
> > > > +void drain_local_pages(void *dummy);
> > > >
> > > > #endif /* __LINUX_GFP_H */
> > >
>
I applied Christoph and Andrew's patches and recompiled. I suspended
to disk and to ram several times and all looks good.
Miles
--
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: 2.6.24-rc5-mm1 -- inconsistent {in-hardirq-W} -> {hardirq-on-W} usage -- pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1]
On Dec 19, 2007 7:09 PM, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> On Thursday, 20 of December 2007, Christoph Lameter wrote:
> > On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
> >
> > > > We could reexport drain_local_pages() again but then I do not understand
> > > > why we would only drain the pages of this processor and not of all other
> > > > processors as well. It seems that software suspend intend was to flush
> > > > them all right?
> > >
> > > Well, not exactly. We are on one CPU at this point, the others have been
> > > disabled.
> >
> > Ok so the others are flush. Here is a patch to re-export
> > drain_local_pages() again and use it for software suspend:
> >
> > Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
> >
> > ---
> > include/linux/gfp.h |1 +
> > kernel/power/snapshot.c |2 +-
> > mm/page_alloc.c |2 +-
> > 3 files changed, 3 insertions(+), 2 deletions(-)
> >
> > Index: linux-2.6.24-rc5-mm1/kernel/power/snapshot.c
> > ===
> > --- linux-2.6.24-rc5-mm1.orig/kernel/power/snapshot.c 2007-12-19
> > 11:59:25.233961700 -0800
> > +++ linux-2.6.24-rc5-mm1/kernel/power/snapshot.c 2007-12-19
> > 15:16:34.179661929 -0800
> > @@ -1203,7 +1203,7 @@ asmlinkage int swsusp_save(void)
> >
> > printk(KERN_INFO "PM: Creating hibernation image: \n");
> >
> > - drain_all_pages();
> > + drain_local_pages(NULL);
> > nr_pages = count_data_pages();
> > nr_highmem = count_highmem_pages();
> > printk(KERN_INFO "PM: Need to copy %u pages\n", nr_pages +
> > nr_highmem);
>
> You've omitted the second instance, right before the copy_data_pages() call.
I will wait for a revised patch and then test.
(Sorry for the duplicate message. I am resending because I
accidentally sent an HTML
message the first time. Whoops.)
> > Index: linux-2.6.24-rc5-mm1/mm/page_alloc.c
> > ===
> > --- linux-2.6.24-rc5-mm1.orig/mm/page_alloc.c 2007-12-19 12:01:00.630421258
> > -0800
> > +++ linux-2.6.24-rc5-mm1/mm/page_alloc.c 2007-12-19 15:12:19.850545818
> > -0800
> > @@ -930,7 +930,7 @@ static void drain_pages(unsigned int cpu
> > /*
> > * Spill all of this CPU's per-cpu pages back into the buddy allocator.
> > */
> > -static void drain_local_pages(void *arg)
> > +void drain_local_pages(void *arg)
> > {
> > drain_pages(smp_processor_id());
> > }
> > Index: linux-2.6.24-rc5-mm1/include/linux/gfp.h
> > ===
> > --- linux-2.6.24-rc5-mm1.orig/include/linux/gfp.h 2007-12-19
> > 15:13:51.926950065 -0800
> > +++ linux-2.6.24-rc5-mm1/include/linux/gfp.h 2007-12-19 15:16:11.951564369
> > -0800
> > @@ -229,5 +229,6 @@ extern void FASTCALL(free_cold_page(stru
> > void page_alloc_init(void);
> > void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp);
> > void drain_all_pages(void);
> > +void drain_local_pages(void *dummy);
> >
> > #endif /* __LINUX_GFP_H */
>
--
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: 2.6.24-rc5-mm1 -- inconsistent {in-hardirq-W} -> {hardirq-on-W} usage -- pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1]
I discovered that I can use IMAP with GMail now, so I can send messages
using Thunderbird and avoid the line wrapping problem.
I tried doing a series: suspend-to-disk, suspend-to-ram and suspend-to-disk
Here is the result:
[ 11.827653] PM: Creating hibernation image:
[ 11.827658] WARNING: at arch/x86/kernel/smp_32.c:561
native_smp_call_function_mask()
[ 11.827661] Pid: 9940, comm: pm-hibernate Not tainted 2.6.24-rc5-mm1 #8
[ 11.827665] [] show_trace_log_lvl+0x12/0x25
[ 11.827673] [] show_trace+0xd/0x10
[ 11.827677] [] dump_stack+0x57/0x5f
[ 11.827681] [] native_smp_call_function_mask+0x41/0x126
[ 11.827686] [] smp_call_function+0x18/0x1f
[ 11.827690] [] on_each_cpu+0x12/0x40
[ 11.827695] [] drain_all_pages+0x13/0x16
[ 11.827700] [] swsusp_save+0x18/0x46b
[ 11.827705] [] swsusp_arch_suspend+0x2a/0x2c
[ 11.827710] [] hibernate+0xba/0x16e
[ 11.827714] [] state_store+0x45/0xac
[ 11.827717] [] kobj_attr_store+0x1a/0x22
[ 11.827722] [] sysfs_write_file+0xb8/0xe3
[ 11.827726] [] vfs_write+0xa4/0x120
[ 11.827731] [] sys_write+0x3b/0x60
[ 11.827734] [] sysenter_past_esp+0x6b/0xc1
[ 11.827738] ===
[ 11.920363] PM: Need to copy 124108 pages
[ 11.920368] PM: Normal pages needed: 46468 + 1024 + 40, available
pages: 182806
[ 15.623893] PM: Hibernation image created (124108 pages copied)
[ 15.624618] Intel machine check architecture supported.
[ 15.624625] Intel machine check reporting enabled on CPU#0.
[ 15.624992]
[ 15.624993] =
[ 15.624995] [ INFO: inconsistent lock state ]
[ 15.624998] 2.6.24-rc5-mm1 #8
[ 15.624999] -
[ 15.625001] inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
[ 15.625005] pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 15.625007] (_base->lock_key){++..}, at: []
retrigger_next_event+0x63/0x9f
[ 15.625017] {in-hardirq-W} state was registered at:
[ 15.625019] [] __lock_acquire+0x408/0xbf4
[ 15.625025] [] lock_acquire+0x76/0x9d
[ 15.625029] [] _spin_lock+0x19/0x28
[ 15.625035] [] hrtimer_interrupt+0x72/0x1b0
[ 15.625039] [] smp_apic_timer_interrupt+0x69/0x7c
[ 15.625045] [] apic_timer_interrupt+0x33/0x38
[ 15.625050] [] mwait_idle+0x1b/0x1d
[ 15.625054] [] cpu_idle+0xb3/0xd4
[ 15.625058] [] rest_init+0x49/0x4b
[ 15.625062] [] start_kernel+0x357/0x35f
[ 15.625069] [<>] 0x0
[ 15.625082] [] 0x
[ 15.625087] irq event stamp: 1182359
[ 15.625089] hardirqs last enabled at (1182359): []
restore_nocheck+0x12/0x15
[ 15.625094] hardirqs last disabled at (1182358): []
apic_timer_interrupt+0x29/0x38
[ 15.625098] softirqs last enabled at (933018): []
__rcu_offline_cpu+0x32/0x62
[ 15.625104] softirqs last disabled at (933016): []
_spin_lock_bh+0xb/0x2d
[ 15.625109]
[ 15.625110] other info that might help us debug this:
[ 15.625112] 2 locks held by pm-hibernate/9940:
[ 15.625114] #0: (>mutex){--..}, at: []
sysfs_write_file+0x25/0xe3
[ 15.625121] #1: (pm_mutex){--..}, at: [] hibernate+0x10/0x16e
[ 15.625127]
[ 15.625128] stack backtrace:
[ 15.625131] Pid: 9940, comm: pm-hibernate Not tainted 2.6.24-rc5-mm1 #8
[ 15.625133] [] show_trace_log_lvl+0x12/0x25
[ 15.625138] [] show_trace+0xd/0x10
[ 15.625141] [] dump_stack+0x57/0x5f
[ 15.625144] [] print_usage_bug+0x10a/0x117
[ 15.625148] [] mark_lock+0x1e7/0x3fe
[ 15.625152] [] __lock_acquire+0x475/0xbf4
[ 15.625156] [] lock_acquire+0x76/0x9d
[ 15.625159] [] _spin_lock+0x19/0x28
[ 15.625163] [] retrigger_next_event+0x63/0x9f
[ 15.625167] [] hres_timers_resume+0x4d/0x4f
[ 15.625170] [] timekeeping_resume+0x117/0x11e
[ 15.625175] [] __sysdev_resume+0x14/0x34
[ 15.625179] [] sysdev_resume+0x21/0x57
[ 15.625183] [] device_power_up+0x8/0xf
[ 15.625188] [] hibernation_snapshot+0x13c/0x173
[ 15.625192] [] hibernate+0xba/0x16e
[ 15.625195] [] state_store+0x45/0xac
[ 15.625199] [] kobj_attr_store+0x1a/0x22
[ 15.625203] [] sysfs_write_file+0xb8/0xe3
[ 15.625207] [] vfs_write+0xa4/0x120
[ 15.625211] [] sys_write+0x3b/0x60
[ 15.625214] [] sysenter_past_esp+0x6b/0xc1
[ 15.625217] ===
[ 15.625242] agpgart-intel :00:00.0: EARLY resume
...
[ 15.624618] Intel machine check architecture supported.
[ 15.624625] Intel machine check reporting enabled on CPU#0.
[ 15.624992]
[ 15.624993] =
[ 15.624995] [ INFO: inconsistent lock state ]
[ 15.624998] 2.6.24-rc5-mm1 #8
[ 15.624999] -
[ 15.625001] inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
[ 15.625005] pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 15.625007] (_base->lock_key){++..}, at: []
retrigger_next_event+0x63/0x9f
[ 15.625017] {in-hardirq-W} state was registered at:
[ 15.625019] [] __lock_acquire+0x408/0xbf4
[ 15.625025] [] lock_acquire+0x76/0x9d
[
Re: [ipw3945-devel] 2.6.24-rc5-mm1 -- INFO: possible circular locking dependency detected -- pm-suspend/5800 is trying to acquire lock
On Dec 18, 2007 9:58 PM, Zhu Yi <[EMAIL PROTECTED]> wrote: > > On Tue, 2007-12-18 at 15:57 +0100, Johannes Berg wrote: > > Thanks. This is a bug in iwlwifi. > > > > The problem is actually another case where my workqueue debugging with > > lockdep is triggering a warning :)) > > > > Here's the thing: > > > > iwl3945_cancel_deferred_work does > > > > cancel_delayed_work_sync(>init_alive_start); > > > > (which is the "(&(>init_alive_start)->work)" lock) > > > > but it is called from within a locked section of > > mutex_lock(>mutex); (locked from iwl3945_pci_suspend) > > > > On the other hand, the task that runs from the init_alive_start > > workqueue is iwl3945_bg_init_alive_start() which will lock the same > > mutex. > > > > So the deadlock condition is that you can be in > > cancel_delayed_work_sync() above while the mutex is locked, and be > > waiting for iwl_3945_bg_init_alive_start() which tries to lock the > > mutex. > > Thanks for the analysis. > > Miles, please try the attached patch. I'll send a patch for both 3945 > and 4965 to linux-wireless later. I tested it and it looks good here. Thanks! Miles -- 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: [ipw3945-devel] 2.6.24-rc5-mm1 -- INFO: possible circular locking dependency detected -- pm-suspend/5800 is trying to acquire lock
On Dec 18, 2007 9:58 PM, Zhu Yi [EMAIL PROTECTED] wrote: On Tue, 2007-12-18 at 15:57 +0100, Johannes Berg wrote: Thanks. This is a bug in iwlwifi. The problem is actually another case where my workqueue debugging with lockdep is triggering a warning :)) Here's the thing: iwl3945_cancel_deferred_work does cancel_delayed_work_sync(priv-init_alive_start); (which is the ((priv-init_alive_start)-work) lock) but it is called from within a locked section of mutex_lock(priv-mutex); (locked from iwl3945_pci_suspend) On the other hand, the task that runs from the init_alive_start workqueue is iwl3945_bg_init_alive_start() which will lock the same mutex. So the deadlock condition is that you can be in cancel_delayed_work_sync() above while the mutex is locked, and be waiting for iwl_3945_bg_init_alive_start() which tries to lock the mutex. Thanks for the analysis. Miles, please try the attached patch. I'll send a patch for both 3945 and 4965 to linux-wireless later. I tested it and it looks good here. Thanks! Miles -- 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: 2.6.24-rc5-mm1 -- inconsistent {in-hardirq-W} - {hardirq-on-W} usage -- pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1]
I discovered that I can use IMAP with GMail now, so I can send messages
using Thunderbird and avoid the line wrapping problem.
I tried doing a series: suspend-to-disk, suspend-to-ram and suspend-to-disk
Here is the result:
[ 11.827653] PM: Creating hibernation image:
[ 11.827658] WARNING: at arch/x86/kernel/smp_32.c:561
native_smp_call_function_mask()
[ 11.827661] Pid: 9940, comm: pm-hibernate Not tainted 2.6.24-rc5-mm1 #8
[ 11.827665] [c0107d55] show_trace_log_lvl+0x12/0x25
[ 11.827673] [c010848a] show_trace+0xd/0x10
[ 11.827677] [c0108763] dump_stack+0x57/0x5f
[ 11.827681] [c0117db4] native_smp_call_function_mask+0x41/0x126
[ 11.827686] [c01192d9] smp_call_function+0x18/0x1f
[ 11.827690] [c012c624] on_each_cpu+0x12/0x40
[ 11.827695] [c0166ece] drain_all_pages+0x13/0x16
[ 11.827700] [c014f7b3] swsusp_save+0x18/0x46b
[ 11.827705] [c03103fa] swsusp_arch_suspend+0x2a/0x2c
[ 11.827710] [c014e7d8] hibernate+0xba/0x16e
[ 11.827714] [c014d56b] state_store+0x45/0xac
[ 11.827717] [c01ffe95] kobj_attr_store+0x1a/0x22
[ 11.827722] [c01b92c7] sysfs_write_file+0xb8/0xe3
[ 11.827726] [c01837eb] vfs_write+0xa4/0x120
[ 11.827731] [c0183d5e] sys_write+0x3b/0x60
[ 11.827734] [c0106bae] sysenter_past_esp+0x6b/0xc1
[ 11.827738] ===
[ 11.920363] PM: Need to copy 124108 pages
[ 11.920368] PM: Normal pages needed: 46468 + 1024 + 40, available
pages: 182806
[ 15.623893] PM: Hibernation image created (124108 pages copied)
[ 15.624618] Intel machine check architecture supported.
[ 15.624625] Intel machine check reporting enabled on CPU#0.
[ 15.624992]
[ 15.624993] =
[ 15.624995] [ INFO: inconsistent lock state ]
[ 15.624998] 2.6.24-rc5-mm1 #8
[ 15.624999] -
[ 15.625001] inconsistent {in-hardirq-W} - {hardirq-on-W} usage.
[ 15.625005] pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 15.625007] (cpu_base-lock_key){++..}, at: [c013c453]
retrigger_next_event+0x63/0x9f
[ 15.625017] {in-hardirq-W} state was registered at:
[ 15.625019] [c0145432] __lock_acquire+0x408/0xbf4
[ 15.625025] [c0145c94] lock_acquire+0x76/0x9d
[ 15.625029] [c039aa08] _spin_lock+0x19/0x28
[ 15.625035] [c013cd92] hrtimer_interrupt+0x72/0x1b0
[ 15.625039] [c011a2b7] smp_apic_timer_interrupt+0x69/0x7c
[ 15.625045] [c010] apic_timer_interrupt+0x33/0x38
[ 15.625050] [c01054b5] mwait_idle+0x1b/0x1d
[ 15.625054] [c01055e9] cpu_idle+0xb3/0xd4
[ 15.625058] [c03986c5] rest_init+0x49/0x4b
[ 15.625062] [c04f696d] start_kernel+0x357/0x35f
[ 15.625069] [] 0x0
[ 15.625082] [] 0x
[ 15.625087] irq event stamp: 1182359
[ 15.625089] hardirqs last enabled at (1182359): [c0106cb3]
restore_nocheck+0x12/0x15
[ 15.625094] hardirqs last disabled at (1182358): [c010776d]
apic_timer_interrupt+0x29/0x38
[ 15.625098] softirqs last enabled at (933018): [c0137d89]
__rcu_offline_cpu+0x32/0x62
[ 15.625104] softirqs last disabled at (933016): [c039aa22]
_spin_lock_bh+0xb/0x2d
[ 15.625109]
[ 15.625110] other info that might help us debug this:
[ 15.625112] 2 locks held by pm-hibernate/9940:
[ 15.625114] #0: (buffer-mutex){--..}, at: [c01b9234]
sysfs_write_file+0x25/0xe3
[ 15.625121] #1: (pm_mutex){--..}, at: [c014e72e] hibernate+0x10/0x16e
[ 15.625127]
[ 15.625128] stack backtrace:
[ 15.625131] Pid: 9940, comm: pm-hibernate Not tainted 2.6.24-rc5-mm1 #8
[ 15.625133] [c0107d55] show_trace_log_lvl+0x12/0x25
[ 15.625138] [c010848a] show_trace+0xd/0x10
[ 15.625141] [c0108763] dump_stack+0x57/0x5f
[ 15.625144] [c0143e45] print_usage_bug+0x10a/0x117
[ 15.625148] [c01447de] mark_lock+0x1e7/0x3fe
[ 15.625152] [c014549f] __lock_acquire+0x475/0xbf4
[ 15.625156] [c0145c94] lock_acquire+0x76/0x9d
[ 15.625159] [c039aa08] _spin_lock+0x19/0x28
[ 15.625163] [c013c453] retrigger_next_event+0x63/0x9f
[ 15.625167] [c013caf7] hres_timers_resume+0x4d/0x4f
[ 15.625170] [c013eed1] timekeeping_resume+0x117/0x11e
[ 15.625175] [c027b2ba] __sysdev_resume+0x14/0x34
[ 15.625179] [c027b752] sysdev_resume+0x21/0x57
[ 15.625183] [c027f426] device_power_up+0x8/0xf
[ 15.625188] [c014e6e7] hibernation_snapshot+0x13c/0x173
[ 15.625192] [c014e7d8] hibernate+0xba/0x16e
[ 15.625195] [c014d56b] state_store+0x45/0xac
[ 15.625199] [c01ffe95] kobj_attr_store+0x1a/0x22
[ 15.625203] [c01b92c7] sysfs_write_file+0xb8/0xe3
[ 15.625207] [c01837eb] vfs_write+0xa4/0x120
[ 15.625211] [c0183d5e] sys_write+0x3b/0x60
[ 15.625214] [c0106bae] sysenter_past_esp+0x6b/0xc1
[ 15.625217] ===
[ 15.625242] agpgart-intel :00:00.0: EARLY resume
...
[ 15.624618] Intel machine check architecture supported.
[ 15.624625] Intel machine check reporting enabled on CPU#0.
[ 15.624992]
[ 15.624993] =
[ 15.624995] [ INFO: inconsistent lock
Re: 2.6.24-rc5-mm1 -- inconsistent {in-hardirq-W} - {hardirq-on-W} usage -- pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1]
On Dec 19, 2007 7:09 PM, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 20 of December 2007, Christoph Lameter wrote:
On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
We could reexport drain_local_pages() again but then I do not understand
why we would only drain the pages of this processor and not of all other
processors as well. It seems that software suspend intend was to flush
them all right?
Well, not exactly. We are on one CPU at this point, the others have been
disabled.
Ok so the others are flush. Here is a patch to re-export
drain_local_pages() again and use it for software suspend:
Signed-off-by: Christoph Lameter [EMAIL PROTECTED]
---
include/linux/gfp.h |1 +
kernel/power/snapshot.c |2 +-
mm/page_alloc.c |2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
Index: linux-2.6.24-rc5-mm1/kernel/power/snapshot.c
===
--- linux-2.6.24-rc5-mm1.orig/kernel/power/snapshot.c 2007-12-19
11:59:25.233961700 -0800
+++ linux-2.6.24-rc5-mm1/kernel/power/snapshot.c 2007-12-19
15:16:34.179661929 -0800
@@ -1203,7 +1203,7 @@ asmlinkage int swsusp_save(void)
printk(KERN_INFO PM: Creating hibernation image: \n);
- drain_all_pages();
+ drain_local_pages(NULL);
nr_pages = count_data_pages();
nr_highmem = count_highmem_pages();
printk(KERN_INFO PM: Need to copy %u pages\n, nr_pages +
nr_highmem);
You've omitted the second instance, right before the copy_data_pages() call.
I will wait for a revised patch and then test.
(Sorry for the duplicate message. I am resending because I
accidentally sent an HTML
message the first time. Whoops.)
Index: linux-2.6.24-rc5-mm1/mm/page_alloc.c
===
--- linux-2.6.24-rc5-mm1.orig/mm/page_alloc.c 2007-12-19 12:01:00.630421258
-0800
+++ linux-2.6.24-rc5-mm1/mm/page_alloc.c 2007-12-19 15:12:19.850545818
-0800
@@ -930,7 +930,7 @@ static void drain_pages(unsigned int cpu
/*
* Spill all of this CPU's per-cpu pages back into the buddy allocator.
*/
-static void drain_local_pages(void *arg)
+void drain_local_pages(void *arg)
{
drain_pages(smp_processor_id());
}
Index: linux-2.6.24-rc5-mm1/include/linux/gfp.h
===
--- linux-2.6.24-rc5-mm1.orig/include/linux/gfp.h 2007-12-19
15:13:51.926950065 -0800
+++ linux-2.6.24-rc5-mm1/include/linux/gfp.h 2007-12-19 15:16:11.951564369
-0800
@@ -229,5 +229,6 @@ extern void FASTCALL(free_cold_page(stru
void page_alloc_init(void);
void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp);
void drain_all_pages(void);
+void drain_local_pages(void *dummy);
#endif /* __LINUX_GFP_H */
--
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: 2.6.24-rc5-mm1 -- inconsistent {in-hardirq-W} - {hardirq-on-W} usage -- pm-hibernate/9940 [HC0[0]:SC0[0]:HE1:SE1]
On Dec 19, 2007 8:31 PM, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 20 of December 2007, Miles Lane wrote:
On Dec 19, 2007 7:09 PM, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 20 of December 2007, Christoph Lameter wrote:
On Thu, 20 Dec 2007, Rafael J. Wysocki wrote:
We could reexport drain_local_pages() again but then I do not
understand
why we would only drain the pages of this processor and not of all
other
processors as well. It seems that software suspend intend was to
flush
them all right?
Well, not exactly. We are on one CPU at this point, the others have
been
disabled.
Ok so the others are flush. Here is a patch to re-export
drain_local_pages() again and use it for software suspend:
Signed-off-by: Christoph Lameter [EMAIL PROTECTED]
---
include/linux/gfp.h |1 +
kernel/power/snapshot.c |2 +-
mm/page_alloc.c |2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
Index: linux-2.6.24-rc5-mm1/kernel/power/snapshot.c
===
--- linux-2.6.24-rc5-mm1.orig/kernel/power/snapshot.c 2007-12-19 11:59:
25.233961700 -0800
+++ linux-2.6.24-rc5-mm1/kernel/power/snapshot.c 2007-12-19 15:16:
34.179661929 -0800
@@ -1203,7 +1203,7 @@ asmlinkage int swsusp_save(void)
printk(KERN_INFO PM: Creating hibernation image: \n);
- drain_all_pages();
+ drain_local_pages(NULL);
nr_pages = count_data_pages();
nr_highmem = count_highmem_pages();
printk(KERN_INFO PM: Need to copy %u pages\n, nr_pages +
nr_highmem);
You've omitted the second instance, right before the copy_data_pages()
call.
I guess I will wait for a revised patch.
There's an Andrew's fix on top of this one in -mm:
http://marc.info/?l=linux-mm-commitsm=119810866812965w=2
Index: linux-2.6.24-rc5-mm1/mm/page_alloc.c
===
--- linux-2.6.24-rc5-mm1.orig/mm/page_alloc.c 2007-12-19 12:01:
00.630421258 -0800
+++ linux-2.6.24-rc5-mm1/mm/page_alloc.c 2007-12-19 15:12:
19.850545818 -0800
@@ -930,7 +930,7 @@ static void drain_pages(unsigned int cpu
/*
* Spill all of this CPU's per-cpu pages back into the buddy allocator.
*/
-static void drain_local_pages(void *arg)
+void drain_local_pages(void *arg)
{
drain_pages(smp_processor_id());
}
Index: linux-2.6.24-rc5-mm1/include/linux/gfp.h
===
--- linux-2.6.24-rc5-mm1.orig/include/linux/gfp.h 2007-12-19 15:13:
51.926950065 -0800
+++ linux-2.6.24-rc5-mm1/include/linux/gfp.h 2007-12-19 15:16:
11.951564369 -0800
@@ -229,5 +229,6 @@ extern void FASTCALL(free_cold_page(stru
void page_alloc_init(void);
void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp);
void drain_all_pages(void);
+void drain_local_pages(void *dummy);
#endif /* __LINUX_GFP_H */
I applied Christoph and Andrew's patches and recompiled. I suspended
to disk and to ram several times and all looks good.
Miles
--
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/
OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70
I have the patch find /proc | xargs tail [ 50.595474] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 54.733829] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 54.733836] printing ip: c012d527 *pde = [ 54.733843] Oops: [#1] SMP [ 54.733847] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 54.733851] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi pcmcia snd_hda_intel snd_pcm_oss snd_mixer_oss iwl3945 snd_pcm snd_seq_dumm y mac80211 snd_seq_oss cfg80211 sky2 tifm_7xx1 yenta_socket rsrc_nonstatic pcmcia_core tifm_core iTCO_wdt iTCO_vendor_support watchdog_core watchdog_dev snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq rng_core snd_timer snd_seq_device shpchp pci_hotplug battery snd ac button soundcore snd_page_alloc s r_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 54.733915] [ 54.733918] Pid: 5703, comm: tail Not tainted (2.6.24-rc5-mm1 #9) [ 54.733921] EIP: 0060:[c012d527] EFLAGS: 00210297 CPU: 1 [ 54.733926] EIP is at r_show+0x2a/0x70 [ 54.733928] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 54.733931] ESI: 0008 EDI: efbe9420 EBP: eed41f10 ESP: eed41f04 [ 54.733934] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 54.733938] Process tail (pid: 5703, ti=eed41000 task=ee5a8000 task.ti=eed41000) [ 54.733940] Stack: c03a6cac efbe9420 c07e3224 eed41f50 c0199a7e 2000 097d1f20 e1112500 [ 54.733949]efbe9440 01d3 000e 000d [ 54.733958]fffb f7d79210 c01998e4 eed41f74 c01af4f5 eed41f9c 2000 097d1f20 [ 54.733966] Call Trace: [ 54.733968] [c0107d55] show_trace_log_lvl+0x12/0x25 [ 54.733975] [c0107df2] show_stack_log_lvl+0x8a/0x95 [ 54.733980] [c0107e89] show_registers+0x8c/0x154 [ 54.733984] [c010805f] die+0x10e/0x1d2 [ 54.733988] [c039c8c9] do_page_fault+0x52b/0x600 [ 54.733993] [c039af9a] error_code+0x72/0x78 [ 54.733998] [c0199a7e] seq_read+0x19a/0x26c [ 54.734004] [c01af4f5] proc_reg_read+0x60/0x74 [ 54.734009] [c018390d] vfs_read+0xa2/0x11e [ 54.734015] [c0183d02] sys_read+0x3b/0x60 [ 54.734019] [c0106bae] sysenter_past_esp+0x6b/0xc1 [ 54.734023] === [ 54.734025] Code: c3 55 89 d1 89 e5 57 89 c7 56 53 8b 50 64 83 7a 0c 00 77 0e 81 7a 08 ff ff 00 00 be 04 00 00 00 76 05 be 08 00 00 00 89 c8 31 db 8b 40 18 39 d0 74 06 43 83 fb 05 75 f3 8b 41 10 ba 2f 1b 45 c0 [ 54.734071] EIP: [c012d527] r_show+0x2a/0x70 SS:ESP 0068:eed41f04 [ 55.363749] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 55.363756] printing ip: c012d527 *pde = [ 55.363762] Oops: [#2] SMP [ 55.363766] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 55.363770] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi pcmcia snd_hda_intel snd_pcm_oss snd_mixer_oss iwl3945 snd_pcm snd_seq_dumm y mac80211 snd_seq_oss cfg80211 sky2 tifm_7xx1 yenta_socket rsrc_nonstatic pcmcia_core tifm_core iTCO_wdt iTCO_vendor_support watchdog_core watchdog_dev snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq rng_core snd_timer snd_seq_device shpchp pci_hotplug battery snd ac button soundcore snd_page_alloc s r_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 55.363834] [ 55.363837] Pid: 5710, comm: tail Tainted: G D (2.6.24-rc5-mm1 #9) [ 55.363840] EIP: 0060:[c012d527] EFLAGS: 00210297 CPU: 1 [ 55.363845] EIP is at r_show+0x2a/0x70 [ 55.363848] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 55.363851] ESI: 0008 EDI: efbe9420 EBP: ee5a8f10 ESP: ee5a8f04 [ 55.363854] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 55.363857] Process tail (pid: 5710, ti=ee5a8000 task=f76ae000 task.ti=ee5a8000) [ 55.363860] Stack: c03a6cac efbe9420 c07e3224 ee5a8f50 c0199a7e 2000 09e26f20 f7036d00 [ 55.363868]efbe9440 01d3 000e 000d [ 55.363877]fffb f7d79210 c01998e4 ee5a8f74 c01af4f5 ee5a8f9c 2000 09e26f20 [ 55.363885] Call Trace: [ 55.363887] [c0107d55] show_trace_log_lvl+0x12/0x25 [ 55.363894] [c0107df2] show_stack_log_lvl+0x8a/0x95 [ 55.363898] [c0107e89] show_registers+0x8c/0x154 [ 55.363902] [c010805f] die+0x10e/0x1d2 [ 55.363906] [c039c8c9] do_page_fault+0x52b/0x600 [ 55.363911] [c039af9a] error_code+0x72/0x78 [ 55.363915] [c0199a7e] seq_read+0x19a/0x26c [ 55.363921] [c01af4f5] proc_reg_read+0x60/0x74 [ 55.363925]
Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by cat /proc/iomem)
Okay. The command that directly triggers this is: cat /proc/iomem Here is the stack trace without the line-wrapping (sorry!): [ 251.602965] wlan0_rename: RX non-WEP frame, but expected encryption [ 252.868386] BUG: unable to handle kernel NULL pointer dereference at virtual address 0018 [ 252.868393] printing ip: c012d527 *pde = [ 252.868399] Oops: [#1] SMP [ 252.868403] last sysfs file: /sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat [ 252.868407] Modules linked in: aes_i586 aes_generic i915 drm rfcomm l2cap bluetooth acpi_cpufreq cpufreq_stats cpufreq_conservative sbs sbshc dm_crypt sbp2 parport_pc lp parport arc4 ecb crypto_blkcipher cryptomgr crypto_algapi snd_hda_intel snd_pcm_oss snd_mixer_oss pcmcia snd_pcm iTCO_wdt iTCO_vendor_support snd_seq_dummy watchdog_core watchdog_dev snd_seq_oss snd_seq_midi tifm_7xx1 snd_rawmidi iwl3945 snd_seq_midi_event rng_core tifm_core mac80211 snd_seq snd_timer snd_seq_device cfg80211 sky2 battery yenta_socket rsrc_nonstatic pcmcia_core ac snd soundcore snd_page_alloc button shpchp pci_hotplug sr_mod cdrom pata_acpi piix ide_core firewire_ohci firewire_core crc_itu_t thermal processor fan [ 252.868469] [ 252.868472] Pid: 7088, comm: head Not tainted (2.6.24-rc5-mm1 #9) [ 252.868476] EIP: 0060:[c012d527] EFLAGS: 00010297 CPU: 0 [ 252.868481] EIP is at r_show+0x2a/0x70 [ 252.868483] EAX: EBX: 0001 ECX: c07e3224 EDX: c04bb034 [ 252.868486] ESI: 0008 EDI: ed1f52c0 EBP: f5320f10 ESP: f5320f04 [ 252.868489] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 252.868493] Process head (pid: 7088, ti=f532 task=f532e000 task.ti=f532) [ 252.868495] Stack: c03a6cac ed1f52c0 c07e3224 f5320f50 c0199a7e 2000 bf930807 e1007800 [ 252.868504]ed1f52e0 01d3 000e 000d [ 252.868512]fffb f7d39370 c01998e4 f5320f74 c01af4f5 f5320f9c 2000 bf930807 [ 252.868521] Call Trace: [ 252.868523] [c0107d55] show_trace_log_lvl+0x12/0x25 [ 252.868529] [c0107df2] show_stack_log_lvl+0x8a/0x95 [ 252.868534] [c0107e89] show_registers+0x8c/0x154 [ 252.868538] [c010805f] die+0x10e/0x1d2 [ 252.868542] [c039c8c9] do_page_fault+0x52b/0x600 [ 252.868547] [c039af9a] error_code+0x72/0x78 [ 252.868552] [c0199a7e] seq_read+0x19a/0x26c [ 252.868557] [c01af4f5] proc_reg_read+0x60/0x74 [ 252.868562] [c018390d] vfs_read+0xa2/0x11e [ 252.868567] [c0183d02] sys_read+0x3b/0x60 [ 252.868571] [c0106bae] sysenter_past_esp+0x6b/0xc1 [ 252.868575] === [ 252.868577] Code: c3 55 89 d1 89 e5 57 89 c7 56 53 8b 50 64 83 7a 0c 00 77 0e 81 7a 08 ff ff 00 00 be 04 00 00 00 76 05 be 08 00 00 00 89 c8 31 db 8b 40 18 39 d0 74 06 43 83 fb 05 75 f3 8b 41 10 ba 2f 1b 45 c0 [ 252.868623] EIP: [c012d527] r_show+0x2a/0x70 SS:ESP 0068:f5320f04 -- 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.24-rc5-mm1 -- INFO: possible circular locking dependency detected -- pm-suspend/5800 is trying to acquire lock
I have only seen this happen once, and cannot reproduce it. I'll keep
trying, though.
Dec 16 22:10:48 syntropy kernel: [ 231.718023]
===
Dec 16 22:10:48 syntropy kernel: [ 231.718025] [ INFO: possible
circular locking dependency detected ]
Dec 16 22:10:48 syntropy kernel: [ 231.718028] 2.6.24-rc5-mm1 #7
Dec 16 22:10:48 syntropy kernel: [ 231.718029]
---
Dec 16 22:10:48 syntropy kernel: [ 231.718032] pm-suspend/5800 is
trying to acquire lock:
Dec 16 22:10:48 syntropy kernel: [ 231.718034]
(&(>init_alive_start)->work){--..}, at:
[__cancel_work_timer+0x8a/0x17f] __cancel_work_timer+0x8a/0x17f
Dec 16 22:10:48 syntropy kernel: [ 231.718045]
Dec 16 22:10:48 syntropy kernel: [ 231.718046] but task is already
holding lock:
Dec 16 22:10:48 syntropy kernel: [ 231.718047] (>mutex){--..},
at: [] iwl3945_pci_suspend+0x1d/0x65 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718065]
Dec 16 22:10:48 syntropy kernel: [ 231.718066] which lock already
depends on the new lock.
Dec 16 22:10:48 syntropy kernel: [ 231.718067]
Dec 16 22:10:48 syntropy kernel: [ 231.718068]
Dec 16 22:10:48 syntropy kernel: [ 231.718069] the existing
dependency chain (in reverse order) is:
Dec 16 22:10:48 syntropy kernel: [ 231.718071]
Dec 16 22:10:48 syntropy kernel: [ 231.718072] -> #1 (>mutex){--..}:
Dec 16 22:10:48 syntropy kernel: [ 231.718075]
[__lock_acquire+0xa17/0xbf4] __lock_acquire+0xa17/0xbf4
Dec 16 22:10:48 syntropy kernel: [ 231.718083]
[mac80211:lock_acquire+0x76/0x1d8] lock_acquire+0x76/0x9d
Dec 16 22:10:48 syntropy kernel: [ 231.718088]
[pcmcia:mutex_lock_nested+0xf7/0xd7d] mutex_lock_nested+0xf7/0x294
Dec 16 22:10:48 syntropy kernel: [ 231.718096][]
iwl3945_bg_init_alive_start+0x2d/0x1d7 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718109]
[run_workqueue+0xbb/0x18b] run_workqueue+0xbb/0x18b
Dec 16 22:10:48 syntropy kernel: [ 231.718115]
[worker_thread+0xbe/0xcd] worker_thread+0xbe/0xcd
Dec 16 22:10:48 syntropy kernel: [ 231.718121]
[kthread+0x3b/0x61] kthread+0x3b/0x61
Dec 16 22:10:48 syntropy kernel: [ 231.718126]
[kernel_thread_helper+0x7/0x10] kernel_thread_helper+0x7/0x10
Dec 16 22:10:48 syntropy kernel: [ 231.718133][] 0x
Dec 16 22:10:48 syntropy kernel: [ 231.718145]
Dec 16 22:10:48 syntropy kernel: [ 231.718146] -> #0
(&(>init_alive_start)->work){--..}:
Dec 16 22:10:48 syntropy kernel: [ 231.718149]
[__lock_acquire+0x93e/0xbf4] __lock_acquire+0x93e/0xbf4
Dec 16 22:10:48 syntropy kernel: [ 231.718155]
[mac80211:lock_acquire+0x76/0x1d8] lock_acquire+0x76/0x9d
Dec 16 22:10:48 syntropy kernel: [ 231.718161]
[__cancel_work_timer+0xb3/0x17f] __cancel_work_timer+0xb3/0x17f
Dec 16 22:10:48 syntropy kernel: [ 231.718167]
[iwl3945:cancel_delayed_work_sync+0xb/0x0d]
cancel_delayed_work_sync+0xb/0xd
Dec 16 22:10:48 syntropy kernel: [ 231.718173][]
__iwl3945_down+0x51/0x310 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718184][]
iwl3945_pci_suspend+0x2d/0x65 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718196]
[pci_device_suspend+0x1b/0x4b] pci_device_suspend+0x1b/0x4b
Dec 16 22:10:48 syntropy kernel: [ 231.718203]
[device_suspend+0x17e/0x259] device_suspend+0x17e/0x259
Dec 16 22:10:48 syntropy kernel: [ 231.718210]
[suspend_devices_and_enter+0x3d/0x138]
suspend_devices_and_enter+0x3d/0x138
Dec 16 22:10:48 syntropy kernel: [ 231.718217]
[enter_state+0x121/0x17d] enter_state+0x121/0x17d
Dec 16 22:10:48 syntropy kernel: [ 231.718222]
[state_store+0x96/0xac] state_store+0x96/0xac
Dec 16 22:10:48 syntropy kernel: [ 231.718228]
[kobj_attr_store+0x1a/0x22] kobj_attr_store+0x1a/0x22
Dec 16 22:10:48 syntropy kernel: [ 231.718234]
[sysfs_write_file+0xb8/0xe3] sysfs_write_file+0xb8/0xe3
Dec 16 22:10:48 syntropy kernel: [ 231.718242]
[vfs_write+0xa4/0x120] vfs_write+0xa4/0x120
Dec 16 22:10:48 syntropy kernel: [ 231.718248]
[sys_write+0x3b/0x60] sys_write+0x3b/0x60
Dec 16 22:10:48 syntropy kernel: [ 231.718254]
[sysenter_past_esp+0x6b/0xc1] sysenter_past_esp+0x6b/0xc1
Dec 16 22:10:48 syntropy kernel: [ 231.718259][] 0x
Dec 16 22:10:48 syntropy kernel: [ 231.718269]
Dec 16 22:10:48 syntropy kernel: [ 231.718269] other info that might
help us debug this:
Dec 16 22:10:48 syntropy kernel: [ 231.718271]
Dec 16 22:10:48 syntropy kernel: [ 231.718272] 4 locks held by pm-suspend/5800:
Dec 16 22:10:48 syntropy kernel: [ 231.718274] #0:
(>mutex){--..}, at: [sysfs_write_file+0x25/0xe3]
sysfs_write_file+0x25/0xe3
Dec 16 22:10:48 syntropy kernel: [ 231.718280] #1:
(pm_mutex){--..}, at: [enter_state+0x166/0x17d]
enter_state+0x166/0x17d
Dec 16 22:10:48 syntropy kernel: [ 231.718286] #2: (dpm_mtx){--..},
at: [device_suspend+0x2b/0x259] device_suspend+0x2b/0x259
Dec 16 22:10:48 syntropy kernel: [ 231.718291] #3:
(>mutex){--..}, at: [] iwl3945_pci_suspend+0x1d/0x65
[iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718304]
Dec 16 22:10:48
2.6.24-rc5-mm1 -- INFO: possible circular locking dependency detected -- pm-suspend/5800 is trying to acquire lock
I have only seen this happen once, and cannot reproduce it. I'll keep
trying, though.
Dec 16 22:10:48 syntropy kernel: [ 231.718023]
===
Dec 16 22:10:48 syntropy kernel: [ 231.718025] [ INFO: possible
circular locking dependency detected ]
Dec 16 22:10:48 syntropy kernel: [ 231.718028] 2.6.24-rc5-mm1 #7
Dec 16 22:10:48 syntropy kernel: [ 231.718029]
---
Dec 16 22:10:48 syntropy kernel: [ 231.718032] pm-suspend/5800 is
trying to acquire lock:
Dec 16 22:10:48 syntropy kernel: [ 231.718034]
((priv-init_alive_start)-work){--..}, at:
[__cancel_work_timer+0x8a/0x17f] __cancel_work_timer+0x8a/0x17f
Dec 16 22:10:48 syntropy kernel: [ 231.718045]
Dec 16 22:10:48 syntropy kernel: [ 231.718046] but task is already
holding lock:
Dec 16 22:10:48 syntropy kernel: [ 231.718047] (priv-mutex){--..},
at: [f8a587e7] iwl3945_pci_suspend+0x1d/0x65 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718065]
Dec 16 22:10:48 syntropy kernel: [ 231.718066] which lock already
depends on the new lock.
Dec 16 22:10:48 syntropy kernel: [ 231.718067]
Dec 16 22:10:48 syntropy kernel: [ 231.718068]
Dec 16 22:10:48 syntropy kernel: [ 231.718069] the existing
dependency chain (in reverse order) is:
Dec 16 22:10:48 syntropy kernel: [ 231.718071]
Dec 16 22:10:48 syntropy kernel: [ 231.718072] - #1 (priv-mutex){--..}:
Dec 16 22:10:48 syntropy kernel: [ 231.718075]
[__lock_acquire+0xa17/0xbf4] __lock_acquire+0xa17/0xbf4
Dec 16 22:10:48 syntropy kernel: [ 231.718083]
[mac80211:lock_acquire+0x76/0x1d8] lock_acquire+0x76/0x9d
Dec 16 22:10:48 syntropy kernel: [ 231.718088]
[pcmcia:mutex_lock_nested+0xf7/0xd7d] mutex_lock_nested+0xf7/0x294
Dec 16 22:10:48 syntropy kernel: [ 231.718096][f8a56ff7]
iwl3945_bg_init_alive_start+0x2d/0x1d7 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718109]
[run_workqueue+0xbb/0x18b] run_workqueue+0xbb/0x18b
Dec 16 22:10:48 syntropy kernel: [ 231.718115]
[worker_thread+0xbe/0xcd] worker_thread+0xbe/0xcd
Dec 16 22:10:48 syntropy kernel: [ 231.718121]
[kthread+0x3b/0x61] kthread+0x3b/0x61
Dec 16 22:10:48 syntropy kernel: [ 231.718126]
[kernel_thread_helper+0x7/0x10] kernel_thread_helper+0x7/0x10
Dec 16 22:10:48 syntropy kernel: [ 231.718133][] 0x
Dec 16 22:10:48 syntropy kernel: [ 231.718145]
Dec 16 22:10:48 syntropy kernel: [ 231.718146] - #0
((priv-init_alive_start)-work){--..}:
Dec 16 22:10:48 syntropy kernel: [ 231.718149]
[__lock_acquire+0x93e/0xbf4] __lock_acquire+0x93e/0xbf4
Dec 16 22:10:48 syntropy kernel: [ 231.718155]
[mac80211:lock_acquire+0x76/0x1d8] lock_acquire+0x76/0x9d
Dec 16 22:10:48 syntropy kernel: [ 231.718161]
[__cancel_work_timer+0xb3/0x17f] __cancel_work_timer+0xb3/0x17f
Dec 16 22:10:48 syntropy kernel: [ 231.718167]
[iwl3945:cancel_delayed_work_sync+0xb/0x0d]
cancel_delayed_work_sync+0xb/0xd
Dec 16 22:10:48 syntropy kernel: [ 231.718173][f8a542cb]
__iwl3945_down+0x51/0x310 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718184][f8a587f7]
iwl3945_pci_suspend+0x2d/0x65 [iwl3945]
Dec 16 22:10:48 syntropy kernel: [ 231.718196]
[pci_device_suspend+0x1b/0x4b] pci_device_suspend+0x1b/0x4b
Dec 16 22:10:48 syntropy kernel: [ 231.718203]
[device_suspend+0x17e/0x259] device_suspend+0x17e/0x259
Dec 16 22:10:48 syntropy kernel: [ 231.718210]
[suspend_devices_and_enter+0x3d/0x138]
suspend_devices_and_enter+0x3d/0x138
Dec 16 22:10:48 syntropy kernel: [ 231.718217]
[enter_state+0x121/0x17d] enter_state+0x121/0x17d
Dec 16 22:10:48 syntropy kernel: [ 231.718222]
[state_store+0x96/0xac] state_store+0x96/0xac
Dec 16 22:10:48 syntropy kernel: [ 231.718228]
[kobj_attr_store+0x1a/0x22] kobj_attr_store+0x1a/0x22
Dec 16 22:10:48 syntropy kernel: [ 231.718234]
[sysfs_write_file+0xb8/0xe3] sysfs_write_file+0xb8/0xe3
Dec 16 22:10:48 syntropy kernel: [ 231.718242]
[vfs_write+0xa4/0x120] vfs_write+0xa4/0x120
Dec 16 22:10:48 syntropy kernel: [ 231.718248]
[sys_write+0x3b/0x60] sys_write+0x3b/0x60
Dec 16 22:10:48 syntropy kernel: [ 231.718254]
[sysenter_past_esp+0x6b/0xc1] sysenter_past_esp+0x6b/0xc1
Dec 16 22:10:48 syntropy kernel: [ 231.718259][] 0x
Dec 16 22:10:48 syntropy kernel: [ 231.718269]
Dec 16 22:10:48 syntropy kernel: [ 231.718269] other info that might
help us debug this:
Dec 16 22:10:48 syntropy kernel: [ 231.718271]
Dec 16 22:10:48 syntropy kernel: [ 231.718272] 4 locks held by pm-suspend/5800:
Dec 16 22:10:48 syntropy kernel: [ 231.718274] #0:
(buffer-mutex){--..}, at: [sysfs_write_file+0x25/0xe3]
sysfs_write_file+0x25/0xe3
Dec 16 22:10:48 syntropy kernel: [ 231.718280] #1:
(pm_mutex){--..}, at: [enter_state+0x166/0x17d]
enter_state+0x166/0x17d
Dec 16 22:10:48 syntropy kernel: [ 231.718286] #2: (dpm_mtx){--..},
at: [device_suspend+0x2b/0x259] device_suspend+0x2b/0x259
Dec 16 22:10:48 syntropy kernel: [ 231.718291] #3:
(priv-mutex){--..}, at: [f8a587e7]
2.6.24-rc5-mm1 -- inconsistent {in-softirq-W} -> {softirq-on-R} usage.
Sorry Andrew, I don't know who to forward this problem to.
I tried running: find /proc | xargs cat
and got this:
=
[ INFO: inconsistent lock state ]
2.6.24-rc5-mm1 #26
-
inconsistent {in-softirq-W} -> {softirq-on-R} usage.
cat/6944 [HC0[0]:SC0[0]:HE1:SE1] takes:
BUG: unable to handle kernel paging request at virtual address 0f1eff0b
printing ip: c01fe64d *pde =
Oops: [#1] PREEMPT SMP
last sysfs file: /sys/block/sda/sda3/stat
Modules linked in: aes_generic i915 drm rfcomm l2cap bluetooth
cpufreq_stats cpufreq_conservative cpufreq_performance sbs sbshc
dm_crypt sbp2 parport_pc lp parport pcmcia arc4 ecb crypto_blkcipher
cryptomgr crypto_algapi tifm_7xx1 tifm_core yenta_socket
rsrc_nonstatic pcmcia_core iwl3945 iTCO_wdt iTCO_vendor_support
watchdog_core watchdog_dev snd_hda_intel mac80211 snd_pcm_oss
snd_mixer_oss cfg80211 snd_pcm sky2 snd_seq_dummy snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
snd_seq_device snd soundcore snd_page_alloc shpchp pci_hotplug
firewire_ohci firewire_core crc_itu_t ata_generic piix ide_core
Pid: 6944, comm: cat Not tainted (2.6.24-rc5-mm1 #26)
EIP: 0060:[] EFLAGS: 00210097 CPU: 0
EIP is at strnlen+0x9/0x1c
EAX: 0f1eff0b EBX: 0f1eff0b ECX: 0f1eff0b EDX: fffe
ESI: c05b74f6 EDI: d6267d94 EBP: d6267cc8 ESP: d6267cc8
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process cat (pid: 6944, ti=d6267000 task=d5a09000 task.ti=d6267000)
Stack: d6267cfc c01fdd22 0400 c05b74f4 0001 c05b78f4
c048f503 0400 d5a09000 0002 d6267d0c c01fdf41 d6267d94
db68c04a d6267d74 c012ae81 d6267d94 0028 c05b89f7 00200046
Call Trace:
[] show_trace_log_lvl+0x12/0x25
[] show_stack_log_lvl+0x8a/0x95
[] show_registers+0x8a/0x1bd
[] die+0x118/0x1dc
[] do_page_fault+0x5a4/0x681
[] error_code+0x72/0x78
[] vsnprintf+0x277/0x40e
[] vscnprintf+0xe/0x1d
[] vprintk+0xcb/0x2f3
[] printk+0x15/0x17
[] print_lock_name+0x4e/0xa2
[] print_lock+0xe/0x3a
[] print_usage_bug+0xbc/0x117
[] mark_lock+0x2e7/0x3fe
[] __lock_acquire+0x498/0xbf4
[] lock_acquire+0x76/0x9d
[] _read_lock+0x23/0x32
[] sock_i_ino+0x14/0x30
[] packet_seq_show+0x22/0x75
[] seq_read+0x19d/0x26f
[] proc_reg_read+0x60/0x74
[] vfs_read+0x8a/0x106
[] sys_read+0x3b/0x60
[] sysenter_past_esp+0x6b/0xc1
===
Code: 01 00 00 00 4f 89 fa 5f 89 d0 5d c3 55 85 c9 89 e5 57 89 c7 89
d0 74 05 f2 ae 75 01 4f 89 f8 5f 5d c3 55 89 c1 89 e5 89 c8 eb 06 <80>
38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 5d c3 90 90 90 55 83
EIP: [] strnlen+0x9/0x1c SS:ESP 0068:d6267cc8
note: cat[6944] exited with preempt_count 4
--
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.24-rc5-mm1 -- inconsistent {in-softirq-W} - {softirq-on-R} usage.
Sorry Andrew, I don't know who to forward this problem to.
I tried running: find /proc | xargs cat
and got this:
=
[ INFO: inconsistent lock state ]
2.6.24-rc5-mm1 #26
-
inconsistent {in-softirq-W} - {softirq-on-R} usage.
cat/6944 [HC0[0]:SC0[0]:HE1:SE1] takes:
BUG: unable to handle kernel paging request at virtual address 0f1eff0b
printing ip: c01fe64d *pde =
Oops: [#1] PREEMPT SMP
last sysfs file: /sys/block/sda/sda3/stat
Modules linked in: aes_generic i915 drm rfcomm l2cap bluetooth
cpufreq_stats cpufreq_conservative cpufreq_performance sbs sbshc
dm_crypt sbp2 parport_pc lp parport pcmcia arc4 ecb crypto_blkcipher
cryptomgr crypto_algapi tifm_7xx1 tifm_core yenta_socket
rsrc_nonstatic pcmcia_core iwl3945 iTCO_wdt iTCO_vendor_support
watchdog_core watchdog_dev snd_hda_intel mac80211 snd_pcm_oss
snd_mixer_oss cfg80211 snd_pcm sky2 snd_seq_dummy snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
snd_seq_device snd soundcore snd_page_alloc shpchp pci_hotplug
firewire_ohci firewire_core crc_itu_t ata_generic piix ide_core
Pid: 6944, comm: cat Not tainted (2.6.24-rc5-mm1 #26)
EIP: 0060:[c01fe64d] EFLAGS: 00210097 CPU: 0
EIP is at strnlen+0x9/0x1c
EAX: 0f1eff0b EBX: 0f1eff0b ECX: 0f1eff0b EDX: fffe
ESI: c05b74f6 EDI: d6267d94 EBP: d6267cc8 ESP: d6267cc8
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process cat (pid: 6944, ti=d6267000 task=d5a09000 task.ti=d6267000)
Stack: d6267cfc c01fdd22 0400 c05b74f4 0001 c05b78f4
c048f503 0400 d5a09000 0002 d6267d0c c01fdf41 d6267d94
db68c04a d6267d74 c012ae81 d6267d94 0028 c05b89f7 00200046
Call Trace:
[c0108eb2] show_trace_log_lvl+0x12/0x25
[c0108f4f] show_stack_log_lvl+0x8a/0x95
[c0108fe4] show_registers+0x8a/0x1bd
[c010922f] die+0x118/0x1dc
[c03cf706] do_page_fault+0x5a4/0x681
[c03cdd72] error_code+0x72/0x78
[c01fdd22] vsnprintf+0x277/0x40e
[c01fdf41] vscnprintf+0xe/0x1d
[c012ae81] vprintk+0xcb/0x2f3
[c012b0be] printk+0x15/0x17
[c0145e55] print_lock_name+0x4e/0xa2
[c0146099] print_lock+0xe/0x3a
[c01464cf] print_usage_bug+0xbc/0x117
[c0146fb6] mark_lock+0x2e7/0x3fe
[c0147b9a] __lock_acquire+0x498/0xbf4
[c014836c] lock_acquire+0x76/0x9d
[c03cd6d2] _read_lock+0x23/0x32
[c03491ae] sock_i_ino+0x14/0x30
[c03c88ed] packet_seq_show+0x22/0x75
[c019b41a] seq_read+0x19d/0x26f
[c01b0ded] proc_reg_read+0x60/0x74
[c01854aa] vfs_read+0x8a/0x106
[c01858a8] sys_read+0x3b/0x60
[c0107cea] sysenter_past_esp+0x6b/0xc1
===
Code: 01 00 00 00 4f 89 fa 5f 89 d0 5d c3 55 85 c9 89 e5 57 89 c7 89
d0 74 05 f2 ae 75 01 4f 89 f8 5f 5d c3 55 89 c1 89 e5 89 c8 eb 06 80
38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 5d c3 90 90 90 55 83
EIP: [c01fe64d] strnlen+0x9/0x1c SS:ESP 0068:d6267cc8
note: cat[6944] exited with preempt_count 4
--
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: 2.6.24-rc5-mm1 -- drivers/video/logo/logo_linux_clut224.c:598: error: conflicting type qualifiers for ‘logo_linux_clut224’
On Dec 13, 2007 8:57 PM, Randy Dunlap <[EMAIL PROTECTED]> wrote: > On Thu, 13 Dec 2007 20:16:13 -0500 Miles Lane wrote: > > > CC drivers/video/logo/logo_linux_clut224.o > > drivers/video/logo/logo_linux_clut224.c:598: error: conflicting type > > qualifiers for 'logo_linux_clut224' > > include/linux/linux_logo.h:47: error: previous declaration of > > 'logo_linux_clut224' was here > > make[3]: *** [drivers/video/logo/logo_linux_clut224.o] Error 1 > > Hi Miles, > > Did you try the patch that was posted today? > > http://lkml.org/lkml/2007/12/13/439 & click on "Get diff 1" > on the left side. No. Thanks. I searched on marc.info but didn't find this. I'll give it a try now. Miles -- 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: 2.6.24-rc5-mm1 -- drivers/video/logo/logo_linux_clut224.c:598: error: conflicting type qualifiers for ‘logo_linux_clut224’
On Dec 13, 2007 8:57 PM, Randy Dunlap [EMAIL PROTECTED] wrote: On Thu, 13 Dec 2007 20:16:13 -0500 Miles Lane wrote: CC drivers/video/logo/logo_linux_clut224.o drivers/video/logo/logo_linux_clut224.c:598: error: conflicting type qualifiers for 'logo_linux_clut224' include/linux/linux_logo.h:47: error: previous declaration of 'logo_linux_clut224' was here make[3]: *** [drivers/video/logo/logo_linux_clut224.o] Error 1 Hi Miles, Did you try the patch that was posted today? http://lkml.org/lkml/2007/12/13/439 click on Get diff 1 on the left side. No. Thanks. I searched on marc.info but didn't find this. I'll give it a try now. Miles -- 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: 2.6.24-rc4-mm1 -- boot process hangs -- tty4 main process (2988) terminated with status 1
> > Dec 6 21:24:28 erratic-orbits init: tty3 main process (2991) > > terminated with status 1 > > Boggle. We broke the vt driver? > > config, please... I sent the .config. Is there nothing else to follow up on? I have tried rebuilding about seven kernels, tweaking the options each time. All the kernels have failed to boot. I am currently trying with a "defconfig" kernel. Perhaps I will have better luck with it. Thanks, Miles -- 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: 2.6.24-rc4-mm1 -- boot process hangs -- tty4 main process (2988) terminated with status 1
Dec 6 21:24:28 erratic-orbits init: tty3 main process (2991) terminated with status 1 Boggle. We broke the vt driver? config, please... I sent the .config. Is there nothing else to follow up on? I have tried rebuilding about seven kernels, tweaking the options each time. All the kernels have failed to boot. I am currently trying with a defconfig kernel. Perhaps I will have better luck with it. Thanks, Miles -- 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.24-rc4-mm1 -- boot process hangs -- tty4 main process (2988) terminated with status 1
The machine is: http://www.gateway.com/retail/mt6821.php Gnu C 4.2.3 Gnu make 3.81 binutils 2.18.20071027 util-linux 2.13.1-rc1 mount 2.13.1-rc1 module-init-tools 3.3-pre11 e2fsprogs 1.40.2 reiserfsprogs 3.6.19 pcmciautils014 PPP2.4.4 Linux C Library2.6.1 Dynamic linker (ldd) 2.6.1 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.97 udev 113 wireless-tools 29 Dec 6 21:24:09 erratic-orbits kernel: Inspecting /boot/System.map-2.6.24-rc4-mm1 Dec 6 21:24:09 erratic-orbits kernel: Loaded 32575 symbols from /boot/System.map-2.6.24-rc4-mm1. Dec 6 21:24:09 erratic-orbits kernel: Symbols match kernel version 2.6.24. Dec 6 21:24:09 erratic-orbits kernel: Loaded 2594 symbols from 18 modules. Dec 6 21:24:09 erratic-orbits kernel: Initializing cgroup subsys cpuset Dec 6 21:24:09 erratic-orbits kernel: Linux version 2.6.24-rc4-mm1 ([EMAIL PROTECTED]) (gcc version 4.2.3 20071123 (prerelease) (Ubuntu 4.2.2-3ubuntu4)) #2 SMP PREEMPT Thu Dec 6 21:15:36 EST 2007 Dec 6 21:24:09 erratic-orbits kernel: BIOS-provided physical RAM map: Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: - 0009f800 (usable) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 0009f800 - 000a (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 000dc000 - 0010 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 0010 - 7f69 (usable) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 7f69 - 7f699000 (ACPI data) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 7f699000 - 7f70 (ACPI NVS) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 7f70 - 8000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: e000 - f000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fec0 - fec1 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fed0 - fed00400 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fed14000 - fed1a000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fed1c000 - fed9 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fee0 - fee01000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: ff00 - 0001 (reserved) Dec 6 21:24:09 erratic-orbits kernel: 1142MB HIGHMEM available. Dec 6 21:24:09 erratic-orbits kernel: 896MB LOWMEM available. Dec 6 21:24:09 erratic-orbits kernel: found SMP MP-table at 000f66b0 Dec 6 21:24:09 erratic-orbits kernel: Entering add_active_range(0, 0, 521872) 0 entries of 256 used Dec 6 21:24:09 erratic-orbits kernel: sizeof(struct page) = 36 Dec 6 21:24:09 erratic-orbits kernel: Zone PFN ranges: Dec 6 21:24:09 erratic-orbits kernel: DMA 0 -> 4096 Dec 6 21:24:09 erratic-orbits kernel: Normal 4096 -> 229376 Dec 6 21:24:09 erratic-orbits kernel: HighMem229376 -> 521872 Dec 6 21:24:09 erratic-orbits kernel: Movable zone start PFN for each node Dec 6 21:24:09 erratic-orbits kernel: early_node_map[1] active PFN ranges Dec 6 21:24:09 erratic-orbits kernel: 0:0 -> 521872 Dec 6 21:24:09 erratic-orbits kernel: On node 0 totalpages: 521872 Dec 6 21:24:09 erratic-orbits kernel: DMA zone: 36 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: DMA zone: 0 pages reserved Dec 6 21:24:09 erratic-orbits kernel: DMA zone: 4060 pages, LIFO batch:0 Dec 6 21:24:09 erratic-orbits kernel: Normal zone: 1980 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: Normal zone: 223300 pages, LIFO batch:31 Dec 6 21:24:09 erratic-orbits kernel: HighMem zone: 2570 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: HighMem zone: 289926 pages, LIFO batch:31 Dec 6 21:24:09 erratic-orbits kernel: Movable zone: 0 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: DMI 2.4 present. Dec 6 21:24:09 erratic-orbits kernel: ACPI: RSDP 000F6600, 0014 (r0 PTLTD ) Dec 6 21:24:09 erratic-orbits kernel: ACPI: RSDT 7F6928B4, 0044 (r1 GATEWA SYSTEM 20070319 LTP0) Dec 6 21:24:09 erratic-orbits kernel: ACPI: FACP 7F698CAA, 0074 (r1 GATEWA SYSTEM 20070319 LOHR 5A) Dec 6 21:24:09 erratic-orbits kernel: ACPI: DSDT 7F6932A6, 5A04 (r1 GATEWA SYSTEM 20070319 MSFT 10E) Dec 6 21:24:09 erratic-orbits kernel: ACPI: FACS 7F699FC0, 0040 Dec 6 21:24:09 erratic-orbits kernel: ACPI: APIC 7F698D1E, 0068 (r1 GATEWA SYSTEM 20070319 LOHR 5A) Dec 6 21:24:09 erratic-orbits kernel: ACPI: HPET 7F698D86, 0038 (r1 GATEWA SYSTEM 20070319 LOHR 5A) Dec 6 21:24:09 erratic-orbits kernel: ACPI: MCFG 7F698DBE, 003C (r1
Re: [PATCH x86/mm] x86 vDSO: canonicalize sysenter .eh_frame
Thanks. That enabled me to compile as well. Now, if I can figure out why the resulting kernel has a boot process that hangs... :-) Miles -- 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: 2.6.24-rc4-mm1: VDSOSYM build error
I found: http://marc.info/?l=linux-kernel=119550978915647=2 through http://marc.info/?l=linux-kernel=119551057816829=2 (I was unable to locate the 6th patch in the set) When I tried backing out the patches, there were tons of errors. I guess I'll punt on trying to build this MM tree. Sorry. Miles -- 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: 2.6.24-rc4-mm1: VDSOSYM build error
How can I find Roland's patches, so I can try backing them out? I looked in the broken out patches and only saw one related to VDSO. Backing it out did not help. I tried searching for messages to LKML sent by "roland" but mostly got a bunch of folks sending spam. Thanks, Miles -- 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: 2.6.24-rc4-mm1: VDSOSYM build error
How can I find Roland's patches, so I can try backing them out? I looked in the broken out patches and only saw one related to VDSO. Backing it out did not help. I tried searching for messages to LKML sent by roland but mostly got a bunch of folks sending spam. Thanks, Miles -- 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: 2.6.24-rc4-mm1: VDSOSYM build error
I found: http://marc.info/?l=linux-kernelm=119550978915647w=2 through http://marc.info/?l=linux-kernelm=119551057816829w=2 (I was unable to locate the 6th patch in the set) When I tried backing out the patches, there were tons of errors. I guess I'll punt on trying to build this MM tree. Sorry. Miles -- 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: [PATCH x86/mm] x86 vDSO: canonicalize sysenter .eh_frame
Thanks. That enabled me to compile as well. Now, if I can figure out why the resulting kernel has a boot process that hangs... :-) Miles -- 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.24-rc4-mm1 -- boot process hangs -- tty4 main process (2988) terminated with status 1
The machine is: http://www.gateway.com/retail/mt6821.php Gnu C 4.2.3 Gnu make 3.81 binutils 2.18.20071027 util-linux 2.13.1-rc1 mount 2.13.1-rc1 module-init-tools 3.3-pre11 e2fsprogs 1.40.2 reiserfsprogs 3.6.19 pcmciautils014 PPP2.4.4 Linux C Library2.6.1 Dynamic linker (ldd) 2.6.1 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.97 udev 113 wireless-tools 29 Dec 6 21:24:09 erratic-orbits kernel: Inspecting /boot/System.map-2.6.24-rc4-mm1 Dec 6 21:24:09 erratic-orbits kernel: Loaded 32575 symbols from /boot/System.map-2.6.24-rc4-mm1. Dec 6 21:24:09 erratic-orbits kernel: Symbols match kernel version 2.6.24. Dec 6 21:24:09 erratic-orbits kernel: Loaded 2594 symbols from 18 modules. Dec 6 21:24:09 erratic-orbits kernel: Initializing cgroup subsys cpuset Dec 6 21:24:09 erratic-orbits kernel: Linux version 2.6.24-rc4-mm1 ([EMAIL PROTECTED]) (gcc version 4.2.3 20071123 (prerelease) (Ubuntu 4.2.2-3ubuntu4)) #2 SMP PREEMPT Thu Dec 6 21:15:36 EST 2007 Dec 6 21:24:09 erratic-orbits kernel: BIOS-provided physical RAM map: Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: - 0009f800 (usable) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 0009f800 - 000a (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 000dc000 - 0010 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 0010 - 7f69 (usable) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 7f69 - 7f699000 (ACPI data) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 7f699000 - 7f70 (ACPI NVS) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: 7f70 - 8000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: e000 - f000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fec0 - fec1 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fed0 - fed00400 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fed14000 - fed1a000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fed1c000 - fed9 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: fee0 - fee01000 (reserved) Dec 6 21:24:09 erratic-orbits kernel: BIOS-e820: ff00 - 0001 (reserved) Dec 6 21:24:09 erratic-orbits kernel: 1142MB HIGHMEM available. Dec 6 21:24:09 erratic-orbits kernel: 896MB LOWMEM available. Dec 6 21:24:09 erratic-orbits kernel: found SMP MP-table at 000f66b0 Dec 6 21:24:09 erratic-orbits kernel: Entering add_active_range(0, 0, 521872) 0 entries of 256 used Dec 6 21:24:09 erratic-orbits kernel: sizeof(struct page) = 36 Dec 6 21:24:09 erratic-orbits kernel: Zone PFN ranges: Dec 6 21:24:09 erratic-orbits kernel: DMA 0 - 4096 Dec 6 21:24:09 erratic-orbits kernel: Normal 4096 - 229376 Dec 6 21:24:09 erratic-orbits kernel: HighMem229376 - 521872 Dec 6 21:24:09 erratic-orbits kernel: Movable zone start PFN for each node Dec 6 21:24:09 erratic-orbits kernel: early_node_map[1] active PFN ranges Dec 6 21:24:09 erratic-orbits kernel: 0:0 - 521872 Dec 6 21:24:09 erratic-orbits kernel: On node 0 totalpages: 521872 Dec 6 21:24:09 erratic-orbits kernel: DMA zone: 36 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: DMA zone: 0 pages reserved Dec 6 21:24:09 erratic-orbits kernel: DMA zone: 4060 pages, LIFO batch:0 Dec 6 21:24:09 erratic-orbits kernel: Normal zone: 1980 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: Normal zone: 223300 pages, LIFO batch:31 Dec 6 21:24:09 erratic-orbits kernel: HighMem zone: 2570 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: HighMem zone: 289926 pages, LIFO batch:31 Dec 6 21:24:09 erratic-orbits kernel: Movable zone: 0 pages used for memmap Dec 6 21:24:09 erratic-orbits kernel: DMI 2.4 present. Dec 6 21:24:09 erratic-orbits kernel: ACPI: RSDP 000F6600, 0014 (r0 PTLTD ) Dec 6 21:24:09 erratic-orbits kernel: ACPI: RSDT 7F6928B4, 0044 (r1 GATEWA SYSTEM 20070319 LTP0) Dec 6 21:24:09 erratic-orbits kernel: ACPI: FACP 7F698CAA, 0074 (r1 GATEWA SYSTEM 20070319 LOHR 5A) Dec 6 21:24:09 erratic-orbits kernel: ACPI: DSDT 7F6932A6, 5A04 (r1 GATEWA SYSTEM 20070319 MSFT 10E) Dec 6 21:24:09 erratic-orbits kernel: ACPI: FACS 7F699FC0, 0040 Dec 6 21:24:09 erratic-orbits kernel: ACPI: APIC 7F698D1E, 0068 (r1 GATEWA SYSTEM 20070319 LOHR 5A) Dec 6 21:24:09 erratic-orbits kernel: ACPI: HPET 7F698D86, 0038 (r1 GATEWA SYSTEM 20070319 LOHR 5A) Dec 6 21:24:09 erratic-orbits kernel: ACPI: MCFG 7F698DBE, 003C (r1 GATEWA
Re: [v4l-dvb-maintainer] 2.6.23-rc6-mm1 -- "dvb_dmx_swfilter" [dr ivers/media/video/video-buf-dvb.ko] undefined!
On 9/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Miles Lane wrote: > > ERROR: "dvb_dmx_swfilter" [drivers/media/video/video-buf-dvb.ko] > undefined! > > ERROR: "dvb_net_init" [drivers/media/video/video-buf-dvb.ko] undefined! > > ERROR: "dvb_dmxdev_init" [drivers/media/video/video-buf-dvb.ko] undefined! > > ERROR: "dvb_dmx_init" [drivers/media/video/video-buf-dvb.ko] undefined! > > ERROR: "dvb_register_frontend" [drivers/media/video/video-buf-dvb.ko] > undefined! > > ERROR: "dvb_register_adapter" [drivers/media/video/video-buf-dvb.ko] > undefined! > > ERROR: "dvb_unregister_adapter" [drivers/media/video/video-buf-dvb.ko] > > undefined! > > ERROR: "dvb_frontend_detach" [drivers/media/video/video-buf-dvb.ko] > undefined! > > ERROR: "dvb_unregister_frontend" > > [drivers/media/video/video-buf-dvb.ko] undefined! > > ERROR: "dvb_dmx_release" [drivers/media/video/video-buf-dvb.ko] undefined! > > ERROR: "dvb_dmxdev_release" [drivers/media/video/video-buf-dvb.ko] > undefined! > > ERROR: "dvb_net_release" [drivers/media/video/video-buf-dvb.ko] undefined! > > ERROR: "mt2131_attach" [drivers/media/video/cx23885/cx23885.ko] undefined! > > ERROR: "s5h1409_attach" [drivers/media/video/cx23885/cx23885.ko] > undefined! > > > > The attached fix should fix the problem. Thanks! Looks good here. Miles - 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: 2.6.23-rc6-mm1
On 9/18/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: > Hi Miles. > On Tue, Sep 18, 2007 at 11:27:23AM -0400, Miles Lane wrote: > > Selecting Help for "Subarchitecture Type" causes "make menuconfig" to > > crash, and the bash display settings have to be reset. > > Not reproduceable here. > But I noticed that we pass a null pointer to a vsprintf function which > in the cases you pointed out printed a (null) at my system. > Could you plase try if attached patch fix your system. Sorry, it still crashes. I am running Ubuntu pre-6.10 (Gutsy -- the development version of the distro). Maybe I should try "make mrproper" first? ncurses 5.6+20070716-1ubuntu1 bash 3.2-0ubuntu9 GNU Make 3.81 - 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: 2.6.23-rc6-mm1
LD .tmp_vmlinux1 drivers/built-in.o: In function `acpi_ac_remove': ac.c:(.text+0x3eeec): undefined reference to `power_supply_unregister' drivers/built-in.o: In function `acpi_ac_add': ac.c:(.text+0x3f10b): undefined reference to `power_supply_register' make: *** [.tmp_vmlinux1] Error 1 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc6-mm1 # Tue Sep 18 12:42:42 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set CONFIG_USER_NS=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 # CONFIG_CONTAINERS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_LBD=y CONFIG_BLK_DEV_IO_TRACE=y # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=m CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_PREEMPT_NOTIFIERS=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set CONFIG_PARAVIRT=y CONFIG_XEN=y CONFIG_VMI=y # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MCORE2 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y CONFIG_NR_CPUS=2 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=m CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_EFI_VARS is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_DMIID=y # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y
Re: 2.6.23-rc6-mm1 -- drivers/kvm/ioapic.c: In function ‘ioapic_deliver’: error: ‘dest_LowestPrio’ undeclared (first use in this function)
CC [M] drivers/kvm/ioapic.o drivers/kvm/ioapic.c: In function 'ioapic_deliver': drivers/kvm/ioapic.c:204: error: 'dest_LowestPrio' undeclared (first use in this function) drivers/kvm/ioapic.c:204: error: (Each undeclared identifier is reported only once drivers/kvm/ioapic.c:204: error: for each function it appears in.) drivers/kvm/ioapic.c:215: error: 'dest_Fixed' undeclared (first use in this function) # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc6-mm1 # Tue Sep 18 11:45:53 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_CONTAINERS=y # CONFIG_CONTAINER_DEBUG is not set CONFIG_CONTAINER_NS=y CONFIG_CONTAINER_CPUACCT=y # CONFIG_RESOURCE_COUNTERS is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_LBD=y CONFIG_BLK_DEV_IO_TRACE=y # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=m CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_PREEMPT_NOTIFIERS=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MCORE2 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_MCE is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_EFI_VARS is not set # CONFIG_DELL_RBU
Re: 2.6.23-rc6-mm1
On 9/18/07, Miles Lane <[EMAIL PROTECTED]> wrote: > Selecting Help for "Subarchitecture Type" causes "make menuconfig" to > crash, and the bash display settings have to be reset. There seem to be a lot of config option help screens that are crashing "make menuconfig". I poked around a little and found a couple more: Under CPU Scaling Frequency, "'userspace' governer for userspace frequency scaling" help causes a crash. Under IO Schedulers, if you have: Anticipatory I/O scheduler Deadline I/O scheduler <*> CFQ I/O scheduler Default I/O scheduler (CFQ) ---> and then select "Default I/O Scheduler (CFQ)" and then select help, you'll get a crash. I got another crash when I selected help for "Symmetric multi-processing support". It seems likely that there are loads more. - 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: 2.6.23-rc6-mm1
Selecting Help for "Subarchitecture Type" causes "make menuconfig" to crash, and the bash display settings have to be reset. Miles - 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/
What can be done to reduce the huge number of build fixes required to release an MM tree?
Hello Andrew and all, What can be done to reduce the huge number of build fixes required to release an MM tree? Perhaps it would be helpful if you identified specific individuals who send you patches that break the build. If necessary, we could keep a running total. The main thought is that maybe we need to identify who regularly sends troublesome patches. There are three metrics that might be good to know: 1) Who sends patches that are regularly broken, but sends patches rarely? 2) Who sends patches all the time, and once in while causes trouble? And 3) Who is causing the most cumulative trouble? Is there any possibility that we ought to refuse patches from people who break the build too often? Another area that might be helpful might be how the patches break things. Are there major groupings of errors that developers could be educated about? I am sorry you are having to work so hard to do your job, Andrew. Miles - 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/
What can be done to reduce the huge number of build fixes required to release an MM tree?
Hello Andrew and all, What can be done to reduce the huge number of build fixes required to release an MM tree? Perhaps it would be helpful if you identified specific individuals who send you patches that break the build. If necessary, we could keep a running total. The main thought is that maybe we need to identify who regularly sends troublesome patches. There are three metrics that might be good to know: 1) Who sends patches that are regularly broken, but sends patches rarely? 2) Who sends patches all the time, and once in while causes trouble? And 3) Who is causing the most cumulative trouble? Is there any possibility that we ought to refuse patches from people who break the build too often? Another area that might be helpful might be how the patches break things. Are there major groupings of errors that developers could be educated about? I am sorry you are having to work so hard to do your job, Andrew. Miles - 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: 2.6.23-rc6-mm1
Selecting Help for Subarchitecture Type causes make menuconfig to crash, and the bash display settings have to be reset. Miles - 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: 2.6.23-rc6-mm1
On 9/18/07, Miles Lane [EMAIL PROTECTED] wrote: Selecting Help for Subarchitecture Type causes make menuconfig to crash, and the bash display settings have to be reset. There seem to be a lot of config option help screens that are crashing make menuconfig. I poked around a little and found a couple more: Under CPU Scaling Frequency, 'userspace' governer for userspace frequency scaling help causes a crash. Under IO Schedulers, if you have: M Anticipatory I/O scheduler M Deadline I/O scheduler * CFQ I/O scheduler Default I/O scheduler (CFQ) --- and then select Default I/O Scheduler (CFQ) and then select help, you'll get a crash. I got another crash when I selected help for Symmetric multi-processing support. It seems likely that there are loads more. - 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: 2.6.23-rc6-mm1 -- drivers/kvm/ioapic.c: In function ‘ioapic_deliver’: error: ‘dest_LowestPrio’ undeclared (first use in this function)
CC [M] drivers/kvm/ioapic.o drivers/kvm/ioapic.c: In function 'ioapic_deliver': drivers/kvm/ioapic.c:204: error: 'dest_LowestPrio' undeclared (first use in this function) drivers/kvm/ioapic.c:204: error: (Each undeclared identifier is reported only once drivers/kvm/ioapic.c:204: error: for each function it appears in.) drivers/kvm/ioapic.c:215: error: 'dest_Fixed' undeclared (first use in this function) # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc6-mm1 # Tue Sep 18 11:45:53 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_CONTAINERS=y # CONFIG_CONTAINER_DEBUG is not set CONFIG_CONTAINER_NS=y CONFIG_CONTAINER_CPUACCT=y # CONFIG_RESOURCE_COUNTERS is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_LBD=y CONFIG_BLK_DEV_IO_TRACE=y # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=m CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=cfq CONFIG_PREEMPT_NOTIFIERS=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MCORE2 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_MCE is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_EFI_VARS is not set # CONFIG_DELL_RBU is not
Re: 2.6.23-rc6-mm1
LD .tmp_vmlinux1 drivers/built-in.o: In function `acpi_ac_remove': ac.c:(.text+0x3eeec): undefined reference to `power_supply_unregister' drivers/built-in.o: In function `acpi_ac_add': ac.c:(.text+0x3f10b): undefined reference to `power_supply_register' make: *** [.tmp_vmlinux1] Error 1 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc6-mm1 # Tue Sep 18 12:42:42 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set CONFIG_USER_NS=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 # CONFIG_CONTAINERS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_LBD=y CONFIG_BLK_DEV_IO_TRACE=y # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=m CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=cfq CONFIG_PREEMPT_NOTIFIERS=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set CONFIG_PARAVIRT=y CONFIG_XEN=y CONFIG_VMI=y # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MCORE2 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y CONFIG_NR_CPUS=2 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=m CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_EFI_VARS is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_DMIID=y # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y
Re: 2.6.23-rc6-mm1
On 9/18/07, Sam Ravnborg [EMAIL PROTECTED] wrote: Hi Miles. On Tue, Sep 18, 2007 at 11:27:23AM -0400, Miles Lane wrote: Selecting Help for Subarchitecture Type causes make menuconfig to crash, and the bash display settings have to be reset. Not reproduceable here. But I noticed that we pass a null pointer to a vsprintf function which in the cases you pointed out printed a (null) at my system. Could you plase try if attached patch fix your system. Sorry, it still crashes. I am running Ubuntu pre-6.10 (Gutsy -- the development version of the distro). Maybe I should try make mrproper first? ncurses 5.6+20070716-1ubuntu1 bash 3.2-0ubuntu9 GNU Make 3.81 - 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: [v4l-dvb-maintainer] 2.6.23-rc6-mm1 -- dvb_dmx_swfilter [dr ivers/media/video/video-buf-dvb.ko] undefined!
On 9/18/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Miles Lane wrote: ERROR: dvb_dmx_swfilter [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_net_init [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_dmxdev_init [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_dmx_init [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_register_frontend [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_register_adapter [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_unregister_adapter [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_frontend_detach [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_unregister_frontend [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_dmx_release [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_dmxdev_release [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: dvb_net_release [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: mt2131_attach [drivers/media/video/cx23885/cx23885.ko] undefined! ERROR: s5h1409_attach [drivers/media/video/cx23885/cx23885.ko] undefined! The attached fix should fix the problem. Thanks! Looks good here. Miles - 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.23-rc2-mm2 -- sysctl table check failed: /kernel/cad_pid .1.54 Missing strategy
Not sure if these are important issues or not: sysctl table check failed: /kernel/cad_pid .1.54 Missing strategy sysctl table check failed: /kernel/pty/nr .1.62.2 No data sysctl table check failed: /dev/parport/default/timeslice .7.3.-3.1 Missing strategy sysctl table check failed: /dev/parport/default/spintime .7.3.-3.2 Missing strategy - 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: 2.6.23-rc2-mm1 -- drivers/dma/ioat_dca.c:177: error: implicit declaration of function ___cpu_physical_id___
On 8/9/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Thu, 9 Aug 2007 10:18:15 -0400
> "Miles Lane" <[EMAIL PROTECTED]> wrote:
>
> > CC drivers/dma/ioat_dca.o
> > drivers/dma/ioat_dca.c: In function 'ioat_dca_get_tag':
> > drivers/dma/ioat_dca.c:177: error: implicit declaration of function
> > 'cpu_physical_id'
>
> Looks like cpu_physical_id() doesn't get implemented if CONFIG_SMP=n.
>
> Either ioat needs to stop using cpu_physical_id() if SMP=n, or the
> supported architectures (i386, x86_64, ia64) should provide a non-SMP
> version of cpu_physical_id(). Preferably the latter, I'd say.
>
> Something like this, I suppose...
>
>
> From: Andrew Morton <[EMAIL PROTECTED]>
>
> i386, x86_64 and ia64 implement cpu_physical_id() if CONFIG_SMP=y.
>
> Provide a uniprocessor stub so that callers will dtrt.
>
> Cc: Andi Kleen <[EMAIL PROTECTED]>
> Cc: "Luck, Tony" <[EMAIL PROTECTED]>
> Cc: Shannon Nelson <[EMAIL PROTECTED]>
> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
> ---
>
> include/linux/smp.h |5 +
> 1 files changed, 5 insertions(+)
>
> diff -puN include/linux/smp.h~implement-cpu_physical_id-on-smp=n
> include/linux/smp.h
> --- a/include/linux/smp.h~implement-cpu_physical_id-on-smp=n
> +++ a/include/linux/smp.h
> @@ -108,6 +108,11 @@ static inline void smp_send_reschedule(i
> 0; \
> })
>
> +static inline unsigned cpu_physical_id(unsigned cpu)
> +{
> + return 0;
> +}
> +
> #endif /* !SMP */
>
> /*
> _
Worked for me.
Thanks,
Miles
-
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.23-rc2-mm2 -- sysctl table check failed: /kernel/cad_pid .1.54 Missing strategy
Not sure if these are important issues or not: sysctl table check failed: /kernel/cad_pid .1.54 Missing strategy sysctl table check failed: /kernel/pty/nr .1.62.2 No data sysctl table check failed: /dev/parport/default/timeslice .7.3.-3.1 Missing strategy sysctl table check failed: /dev/parport/default/spintime .7.3.-3.2 Missing strategy - 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: 2.6.23-rc2-mm1 -- drivers/dma/ioat_dca.c:177: error: implicit declaration of function ___cpu_physical_id___
On 8/9/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Thu, 9 Aug 2007 10:18:15 -0400
Miles Lane [EMAIL PROTECTED] wrote:
CC drivers/dma/ioat_dca.o
drivers/dma/ioat_dca.c: In function 'ioat_dca_get_tag':
drivers/dma/ioat_dca.c:177: error: implicit declaration of function
'cpu_physical_id'
Looks like cpu_physical_id() doesn't get implemented if CONFIG_SMP=n.
Either ioat needs to stop using cpu_physical_id() if SMP=n, or the
supported architectures (i386, x86_64, ia64) should provide a non-SMP
version of cpu_physical_id(). Preferably the latter, I'd say.
Something like this, I suppose...
From: Andrew Morton [EMAIL PROTECTED]
i386, x86_64 and ia64 implement cpu_physical_id() if CONFIG_SMP=y.
Provide a uniprocessor stub so that callers will dtrt.
Cc: Andi Kleen [EMAIL PROTECTED]
Cc: Luck, Tony [EMAIL PROTECTED]
Cc: Shannon Nelson [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
include/linux/smp.h |5 +
1 files changed, 5 insertions(+)
diff -puN include/linux/smp.h~implement-cpu_physical_id-on-smp=n
include/linux/smp.h
--- a/include/linux/smp.h~implement-cpu_physical_id-on-smp=n
+++ a/include/linux/smp.h
@@ -108,6 +108,11 @@ static inline void smp_send_reschedule(i
0; \
})
+static inline unsigned cpu_physical_id(unsigned cpu)
+{
+ return 0;
+}
+
#endif /* !SMP */
/*
_
Worked for me.
Thanks,
Miles
-
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.23-rc2-mm1 -- INFO: possible circular locking dependency detected
[ INFO: possible circular locking dependency detected ]
2.6.23-rc2-mm1 #7
---
kacpid/53 is trying to acquire lock:
(>lock){--..}, at: [] mutex_lock+0x1c/0x1f
but task is already holding lock:
(>work){--..}, at: [] run_workqueue+0xa0/0x182
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (>work){--..}:
[] __lock_acquire+0x9a6/0xb6f
[] lock_acquire+0x61/0x7d
[] run_workqueue+0xb5/0x182
[] worker_thread+0xb7/0xc2
[] kthread+0x39/0x61
[] kernel_thread_helper+0x7/0x10
[] 0x
-> #1 (kacpid){--..}:
[] __lock_acquire+0x9a6/0xb6f
[] lock_acquire+0x61/0x7d
[] flush_workqueue+0x2d/0x4f
[] acpi_os_wait_events_complete+0xd/0xf
[] acpi_remove_gpe_handler+0x7b/0xdd
[] ec_remove_handlers+0x26/0x29
[] acpi_ec_add+0x8f/0x13e
[] acpi_device_probe+0x3e/0xdb
[] driver_probe_device+0xd7/0x14d
[] __driver_attach+0x6a/0xa1
[] bus_for_each_dev+0x36/0x5b
[] driver_attach+0x14/0x16
[] bus_add_driver+0x70/0x16c
[] driver_register+0x60/0x65
[] acpi_bus_register_driver+0x3a/0x3c
[] acpi_ec_init+0x36/0x55
[] kernel_init+0xc5/0x20f
[] kernel_thread_helper+0x7/0x10
[] 0x
-> #0 (>lock){--..}:
[] __lock_acquire+0x8c6/0xb6f
[] lock_acquire+0x61/0x7d
[] __mutex_lock_slowpath+0xbc/0x241
[] mutex_lock+0x1c/0x1f
[] acpi_ec_transaction+0x65/0x1c1
[] acpi_ec_gpe_query+0x2b/0xab
[] acpi_os_execute_deferred+0x20/0x31
[] run_workqueue+0xba/0x182
[] worker_thread+0xb7/0xc2
[] kthread+0x39/0x61
[] kernel_thread_helper+0x7/0x10
[] 0x
other info that might help us debug this:
2 locks held by kacpid/53:
#0: (kacpid){--..}, at: [] run_workqueue+0x85/0x182
#1: (>work){--..}, at: [] run_workqueue+0xa0/0x182
stack backtrace:
[] show_trace_log_lvl+0x12/0x25
[] show_trace+0xd/0x10
[] dump_stack+0x15/0x17
[] print_circular_bug_tail+0x5a/0x65
[] __lock_acquire+0x8c6/0xb6f
[] lock_acquire+0x61/0x7d
[] __mutex_lock_slowpath+0xbc/0x241
[] mutex_lock+0x1c/0x1f
[] acpi_ec_transaction+0x65/0x1c1
[] acpi_ec_gpe_query+0x2b/0xab
[] acpi_os_execute_deferred+0x20/0x31
[] run_workqueue+0xba/0x182
[] worker_thread+0xb7/0xc2
[] kthread+0x39/0x61
[] kernel_thread_helper+0x7/0x10
===
-
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: 2.6.23-rc2-mm1 -- drivers/dma/ioat_dca.c:177: error: implicit declaration of function ‘cpu_physical_id’
On 8/9/07, Adrian Bunk <[EMAIL PROTECTED]> wrote: > On Thu, Aug 09, 2007 at 10:18:15AM -0400, Miles Lane wrote: > > CC drivers/dma/ioat_dca.o > > drivers/dma/ioat_dca.c: In function 'ioat_dca_get_tag': > > drivers/dma/ioat_dca.c:177: error: implicit declaration of function > > 'cpu_physical_id' > > make[2]: *** [drivers/dma/ioat_dca.o] Error 1 > > -ENODOTCONFIG # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc2-mm1 # Thu Aug 9 12:18:45 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_NONIRQ_WAKEUP=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_CONTAINERS=y CONFIG_CONTAINER_DEBUG=y CONFIG_CONTAINER_NS=y CONFIG_CONTAINER_CPUACCT=y # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=m CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MCORE2 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=m CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m
2.6.23-rc2-mm1 -- drivers/dma/ioat_dca.c:177: error: implicit declaration of function ‘cpu_physical_id’
CC drivers/dma/ioat_dca.o drivers/dma/ioat_dca.c: In function 'ioat_dca_get_tag': drivers/dma/ioat_dca.c:177: error: implicit declaration of function 'cpu_physical_id' make[2]: *** [drivers/dma/ioat_dca.o] Error 1 - 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.23-rc2-mm1 -- drivers/dma/ioat_dca.c:177: error: implicit declaration of function ‘cpu_physical_id’
CC drivers/dma/ioat_dca.o drivers/dma/ioat_dca.c: In function 'ioat_dca_get_tag': drivers/dma/ioat_dca.c:177: error: implicit declaration of function 'cpu_physical_id' make[2]: *** [drivers/dma/ioat_dca.o] Error 1 - 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: 2.6.23-rc2-mm1 -- drivers/dma/ioat_dca.c:177: error: implicit declaration of function ‘cpu_physical_id’
On 8/9/07, Adrian Bunk [EMAIL PROTECTED] wrote: On Thu, Aug 09, 2007 at 10:18:15AM -0400, Miles Lane wrote: CC drivers/dma/ioat_dca.o drivers/dma/ioat_dca.c: In function 'ioat_dca_get_tag': drivers/dma/ioat_dca.c:177: error: implicit declaration of function 'cpu_physical_id' make[2]: *** [drivers/dma/ioat_dca.o] Error 1 -ENODOTCONFIG # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc2-mm1 # Thu Aug 9 12:18:45 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_NONIRQ_WAKEUP=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_CONTAINERS=y CONFIG_CONTAINER_DEBUG=y CONFIG_CONTAINER_NS=y CONFIG_CONTAINER_CPUACCT=y # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=m CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=anticipatory # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MCORE2 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_HPET_TIMER=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=m CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y # CONFIG_NOHIGHMEM is not set
2.6.23-rc2-mm1 -- INFO: possible circular locking dependency detected
[ INFO: possible circular locking dependency detected ]
2.6.23-rc2-mm1 #7
---
kacpid/53 is trying to acquire lock:
(ec-lock){--..}, at: [c03031a7] mutex_lock+0x1c/0x1f
but task is already holding lock:
(dpc-work){--..}, at: [c012689d] run_workqueue+0xa0/0x182
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
- #2 (dpc-work){--..}:
[c0133d24] __lock_acquire+0x9a6/0xb6f
[c0133f4e] lock_acquire+0x61/0x7d
[c01268b2] run_workqueue+0xb5/0x182
[c01271a9] worker_thread+0xb7/0xc2
[c01296c4] kthread+0x39/0x61
[c0104913] kernel_thread_helper+0x7/0x10
[] 0x
- #1 (kacpid){--..}:
[c0133d24] __lock_acquire+0x9a6/0xb6f
[c0133f4e] lock_acquire+0x61/0x7d
[c0126f62] flush_workqueue+0x2d/0x4f
[c01e85e0] acpi_os_wait_events_complete+0xd/0xf
[c01ef605] acpi_remove_gpe_handler+0x7b/0xdd
[c0205981] ec_remove_handlers+0x26/0x29
[c02062b4] acpi_ec_add+0x8f/0x13e
[c0205477] acpi_device_probe+0x3e/0xdb
[c023c4c8] driver_probe_device+0xd7/0x14d
[c023c652] __driver_attach+0x6a/0xa1
[c023baaa] bus_for_each_dev+0x36/0x5b
[c023c32e] driver_attach+0x14/0x16
[c023bd7e] bus_add_driver+0x70/0x16c
[c023c82d] driver_register+0x60/0x65
[c020577b] acpi_bus_register_driver+0x3a/0x3c
[c04292e4] acpi_ec_init+0x36/0x55
[c0416650] kernel_init+0xc5/0x20f
[c0104913] kernel_thread_helper+0x7/0x10
[] 0x
- #0 (ec-lock){--..}:
[c0133c44] __lock_acquire+0x8c6/0xb6f
[c0133f4e] lock_acquire+0x61/0x7d
[c0303006] __mutex_lock_slowpath+0xbc/0x241
[c03031a7] mutex_lock+0x1c/0x1f
[c0205bbd] acpi_ec_transaction+0x65/0x1c1
[c0205d44] acpi_ec_gpe_query+0x2b/0xab
[c01e8602] acpi_os_execute_deferred+0x20/0x31
[c01268b7] run_workqueue+0xba/0x182
[c01271a9] worker_thread+0xb7/0xc2
[c01296c4] kthread+0x39/0x61
[c0104913] kernel_thread_helper+0x7/0x10
[] 0x
other info that might help us debug this:
2 locks held by kacpid/53:
#0: (kacpid){--..}, at: [c0126882] run_workqueue+0x85/0x182
#1: (dpc-work){--..}, at: [c012689d] run_workqueue+0xa0/0x182
stack backtrace:
[c0104c6a] show_trace_log_lvl+0x12/0x25
[c0105552] show_trace+0xd/0x10
[c0105656] dump_stack+0x15/0x17
[c0132580] print_circular_bug_tail+0x5a/0x65
[c0133c44] __lock_acquire+0x8c6/0xb6f
[c0133f4e] lock_acquire+0x61/0x7d
[c0303006] __mutex_lock_slowpath+0xbc/0x241
[c03031a7] mutex_lock+0x1c/0x1f
[c0205bbd] acpi_ec_transaction+0x65/0x1c1
[c0205d44] acpi_ec_gpe_query+0x2b/0xab
[c01e8602] acpi_os_execute_deferred+0x20/0x31
[c01268b7] run_workqueue+0xba/0x182
[c01271a9] worker_thread+0xb7/0xc2
[c01296c4] kthread+0x39/0x61
[c0104913] kernel_thread_helper+0x7/0x10
===
-
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.23-rc1-mm2 + cpufreq patch + hot-fixes -- [] usb_stor_scan_thread+0xbd/0x15a [usb_storage]
usb usb4: usb resume ehci_hcd :00:1d.7: resume root hub hub 4-0:1.0: hub_resume hub 4-0:1.0: state 7 ports 6 chg evt ehci_hcd :00:1d.7: GetStatus port 3 status 001803 POWER sig=j CSC CONNECT hub 4-0:1.0: port 3, status 0501, change 0001, 480 Mb/s hub 4-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501 ehci_hcd :00:1d.7: port 3 high speed ehci_hcd :00:1d.7: GetStatus port 3 status 001005 POWER sig=se0 PE CONNECT usb 4-3: new high speed USB device using ehci_hcd and address 2 ehci_hcd :00:1d.7: port 3 high speed ehci_hcd :00:1d.7: GetStatus port 3 status 001005 POWER sig=se0 PE CONNECT usb 4-3: default language 0x0409 usb 4-3: new device found, idVendor=0781, idProduct=5150 usb 4-3: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-3: Product: Cruzer Mini usb 4-3: Manufacturer: SanDisk Corporation usb 4-3: SerialNumber: SNDK5C31950CBB106202 usb 4-3: uevent usb 4-3: usb_probe_device usb 4-3: configuration #1 chosen from 1 choice usb 4-3: adding 4-3:1.0 (config #1, interface 0) usb 4-3:1.0: uevent usb 4-3:1.0: uevent drivers/usb/core/inode.c: creating file '002' Initializing USB Mass Storage driver... usb-storage 4-3:1.0: usb_probe_interface usb-storage 4-3:1.0: usb_probe_interface - got id scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning schedule_timeout: wrong timeout value f8ea51d2 [] show_trace_log_lvl+0x12/0x25 [] show_trace+0xd/0x10 [] dump_stack+0x16/0x18 [] schedule_timeout+0x2c/0x8b [] usb_stor_scan_thread+0xbd/0x15a [usb_storage] [] kthread+0x3b/0x63 [] kernel_thread_helper+0x7/0x10 === USB Mass Storage support registered. scsi 2:0:0:0: Direct-Access SanDisk Cruzer Mini 0.4 PQ: 0 ANSI: 2 sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 sd 2:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 2:0:0:0: [sdb] Attached SCSI removable disk sd 2:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete - 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.23-rc1-mm2 + cpufreq patch + hot-fixes -- [f8ea528f] usb_stor_scan_thread+0xbd/0x15a [usb_storage]
usb usb4: usb resume ehci_hcd :00:1d.7: resume root hub hub 4-0:1.0: hub_resume hub 4-0:1.0: state 7 ports 6 chg evt ehci_hcd :00:1d.7: GetStatus port 3 status 001803 POWER sig=j CSC CONNECT hub 4-0:1.0: port 3, status 0501, change 0001, 480 Mb/s hub 4-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501 ehci_hcd :00:1d.7: port 3 high speed ehci_hcd :00:1d.7: GetStatus port 3 status 001005 POWER sig=se0 PE CONNECT usb 4-3: new high speed USB device using ehci_hcd and address 2 ehci_hcd :00:1d.7: port 3 high speed ehci_hcd :00:1d.7: GetStatus port 3 status 001005 POWER sig=se0 PE CONNECT usb 4-3: default language 0x0409 usb 4-3: new device found, idVendor=0781, idProduct=5150 usb 4-3: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-3: Product: Cruzer Mini usb 4-3: Manufacturer: SanDisk Corporation usb 4-3: SerialNumber: SNDK5C31950CBB106202 usb 4-3: uevent usb 4-3: usb_probe_device usb 4-3: configuration #1 chosen from 1 choice usb 4-3: adding 4-3:1.0 (config #1, interface 0) usb 4-3:1.0: uevent usb 4-3:1.0: uevent drivers/usb/core/inode.c: creating file '002' Initializing USB Mass Storage driver... usb-storage 4-3:1.0: usb_probe_interface usb-storage 4-3:1.0: usb_probe_interface - got id scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning schedule_timeout: wrong timeout value f8ea51d2 [c01080ab] show_trace_log_lvl+0x12/0x25 [c0108a9e] show_trace+0xd/0x10 [c0108bac] dump_stack+0x16/0x18 [c031e31e] schedule_timeout+0x2c/0x8b [f8ea528f] usb_stor_scan_thread+0xbd/0x15a [usb_storage] [c0139d64] kthread+0x3b/0x63 [c0107c63] kernel_thread_helper+0x7/0x10 === USB Mass Storage support registered. scsi 2:0:0:0: Direct-Access SanDisk Cruzer Mini 0.4 PQ: 0 ANSI: 2 sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 sd 2:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 2:0:0:0: [sdb] Attached SCSI removable disk sd 2:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete - 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.23-rc1-mm2 + cpufreq patch -- another "inconsistent {in-hardirq-W} -> {hardirq-on-W} usage."
When I ran "modprobe -r ipw2200" I got:
=
[ INFO: inconsistent lock state ]
2.6.23-rc1-mm2 #21
-
inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
modprobe/6888 [HC0[0]:SC0[0]:HE1:SE1] takes:
(>irq_lock){++..}, at: [] ipw_isr+0x1c/0xa9 [ipw2200]
{in-hardirq-W} state was registered at:
[] __lock_acquire+0x430/0xbca
[] lock_acquire+0x76/0x9d
[] _spin_lock+0x23/0x32
[] ipw_isr+0x1c/0xa9 [ipw2200]
[] handle_IRQ_event+0x1a/0x4f
[] handle_fasteoi_irq+0x7d/0xb6
[] do_IRQ+0xaf/0xd9
[] 0x
irq event stamp: 136973
hardirqs last enabled at (136973): [] kfree+0xc7/0xdb
hardirqs last disabled at (136972): [] kfree+0x67/0xdb
softirqs last enabled at (136286): [] __do_softirq+0xf5/0xfb
softirqs last disabled at (136277): [] do_softirq+0x74/0xed
other info that might help us debug this:
no locks held by modprobe/6888.
stack backtrace:
[] show_trace_log_lvl+0x12/0x25
[] show_trace+0xd/0x10
[] dump_stack+0x16/0x18
[] print_usage_bug+0x107/0x114
[] mark_lock+0x1e9/0x400
[] __lock_acquire+0x4a4/0xbca
[] lock_acquire+0x76/0x9d
[] _spin_lock+0x23/0x32
[] ipw_isr+0x1c/0xa9 [ipw2200]
[] free_irq+0xc9/0xf2
[] ipw_pci_remove+0x189/0x1c9 [ipw2200]
[] pci_device_remove+0x19/0x39
[] __device_release_driver+0x74/0x90
[] driver_detach+0xa2/0xe0
[] bus_remove_driver+0x5d/0x79
[] driver_unregister+0x8/0xa
[] pci_unregister_driver+0x13/0x55
[] ipw_exit+0x1c/0x1e [ipw2200]
[] sys_delete_module+0x1c6/0x237
[] sysenter_past_esp+0x6b/0xb5
===
-
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.23-rc1-mm2 + cpufreq patch -- another inconsistent {in-hardirq-W} - {hardirq-on-W} usage.
When I ran modprobe -r ipw2200 I got:
=
[ INFO: inconsistent lock state ]
2.6.23-rc1-mm2 #21
-
inconsistent {in-hardirq-W} - {hardirq-on-W} usage.
modprobe/6888 [HC0[0]:SC0[0]:HE1:SE1] takes:
(priv-irq_lock){++..}, at: [f8ce9b1c] ipw_isr+0x1c/0xa9 [ipw2200]
{in-hardirq-W} state was registered at:
[c0144837] __lock_acquire+0x430/0xbca
[c0145047] lock_acquire+0x76/0x9d
[c031ffe0] _spin_lock+0x23/0x32
[f8ce9b1c] ipw_isr+0x1c/0xa9 [ipw2200]
[c0154b44] handle_IRQ_event+0x1a/0x4f
[c0155c6c] handle_fasteoi_irq+0x7d/0xb6
[c0109a5a] do_IRQ+0xaf/0xd9
[] 0x
irq event stamp: 136973
hardirqs last enabled at (136973): [c0173232] kfree+0xc7/0xdb
hardirqs last disabled at (136972): [c01731d2] kfree+0x67/0xdb
softirqs last enabled at (136286): [c012d8a1] __do_softirq+0xf5/0xfb
softirqs last disabled at (136277): [c0109932] do_softirq+0x74/0xed
other info that might help us debug this:
no locks held by modprobe/6888.
stack backtrace:
[c01080ab] show_trace_log_lvl+0x12/0x25
[c0108a9e] show_trace+0xd/0x10
[c0108bac] dump_stack+0x16/0x18
[c0143374] print_usage_bug+0x107/0x114
[c0143bdd] mark_lock+0x1e9/0x400
[c01448ab] __lock_acquire+0x4a4/0xbca
[c0145047] lock_acquire+0x76/0x9d
[c031ffe0] _spin_lock+0x23/0x32
[f8ce9b1c] ipw_isr+0x1c/0xa9 [ipw2200]
[c015506f] free_irq+0xc9/0xf2
[f8cea09c] ipw_pci_remove+0x189/0x1c9 [ipw2200]
[c0206dec] pci_device_remove+0x19/0x39
[c026a23a] __device_release_driver+0x74/0x90
[c026a6b6] driver_detach+0xa2/0xe0
[c0269dc5] bus_remove_driver+0x5d/0x79
[c026a71b] driver_unregister+0x8/0xa
[c0206f56] pci_unregister_driver+0x13/0x55
[f8cead75] ipw_exit+0x1c/0x1e [ipw2200]
[c014c85f] sys_delete_module+0x1c6/0x237
[c0106f02] sysenter_past_esp+0x6b/0xb5
===
-
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.23-rc1-mm2 + cpufreq patch -- inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
I am running Ubuntu Gutsy with latest updates.
When I run "/etc/init.d/networking stop" with my custom kernel, I get:
=
[ INFO: inconsistent lock state ]
2.6.23-rc1-mm2 #21
-
inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
ifconfig/8982 [HC0[0]:SC0[0]:HE1:SE1] takes:
(>lock){++..}, at: [] rtl8139_interrupt+0x22/0x377 [8139too]
{in-hardirq-W} state was registered at:
[] __lock_acquire+0x430/0xbca
[] lock_acquire+0x76/0x9d
[] _spin_lock+0x23/0x32
[] rtl8139_interrupt+0x22/0x377 [8139too]
[] handle_IRQ_event+0x1a/0x4f
[] handle_fasteoi_irq+0x7d/0xb6
[] do_IRQ+0xaf/0xd9
[] 0x
irq event stamp: 1501
hardirqs last enabled at (1501): [] kfree+0xc7/0xdb
hardirqs last disabled at (1500): [] kfree+0x67/0xdb
softirqs last enabled at (1480): [] dev_deactivate+0x87/0xa0
softirqs last disabled at (1478): [] _spin_lock_bh+0xb/0x37
other info that might help us debug this:
1 lock held by ifconfig/8982:
#0: (rtnl_mutex){--..}, at: [] mutex_lock+0x1c/0x1f
stack backtrace:
[] show_trace_log_lvl+0x12/0x25
[] show_trace+0xd/0x10
[] dump_stack+0x16/0x18
[] print_usage_bug+0x107/0x114
[] mark_lock+0x1e9/0x400
[] __lock_acquire+0x4a4/0xbca
[] lock_acquire+0x76/0x9d
[] _spin_lock+0x23/0x32
[] rtl8139_interrupt+0x22/0x377 [8139too]
[] free_irq+0xc9/0xf2
[] rtl8139_close+0xac/0x14a [8139too]
[] dev_close+0x4e/0x6b
[] dev_change_flags+0x9f/0x152
[] devinet_ioctl+0x209/0x506
[] inet_ioctl+0x86/0xa4
[] sock_ioctl+0x1a9/0x1c7
[] do_ioctl+0x22/0x67
[] vfs_ioctl+0x249/0x25c
[] sys_ioctl+0x2c/0x45
[] sysenter_past_esp+0x6b/0xb5
===
eth2: link down
-
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/
