* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
@ 2008-05-02 10:02 ` Petr Tesarik
2008-05-02 22:53 ` Luck, Tony
` (20 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Petr Tesarik @ 2008-05-02 10:02 UTC (permalink / raw)
To: linux-ia64
[-- Attachment #1: Type: text/plain, Size: 2684 bytes --]
On Fri, 2008-05-02 at 18:27 +0900, KOSAKI Motohiro wrote:
> Hi
>
> On ia64 2.6.25-mm1, below message is displayed at stress test running.
> Is it bug or not?
This surely is a bug. I bet this was introduced by Hidetoshi's latest
commit:
commit 38477ad75188b2a7370fef7145f956e6c446928b
Author: Hidetoshi Seto
Date: Mon Apr 21 14:34:39 2008 -0700
[IA64] disable interrupts on exit of ia64_trace_syscall
Obviously, if interrupts are disabled and notify_resume_user
synchronizes the RBS, the following condition in __might_sleep() is
true:
if ((in_atomic() || irqs_disabled()) &&
Cheers,
Petr Tesarik
---------------------------------------------
> BUG: sleeping function called from invalid context at kernel/rwsem.c:21
> in_atomic():0, irqs_disabled():1
>
> Call Trace:
> [<a000000100015d00>] show_stack+0x80/0xa0
> sp=e00001608577f840 bsp=e000016085771038
> [<a000000100015d50>] dump_stack+0x30/0x60
> sp=e00001608577fa10 bsp=e000016085771020
> [<a000000100092e80>] __might_sleep+0x1e0/0x2e0
> sp=e00001608577fa10 bsp=e000016085770ff0
> [<a000000100791f00>] down_read+0x20/0x60
> sp=e00001608577fa10 bsp=e000016085770fd0
> [<a00000010015cd50>] access_process_vm+0x70/0x3a0
> sp=e00001608577fa10 bsp=e000016085770f28
> [<a000000100030f60>] ia64_sync_kernel_rbs+0x40/0x100
> sp=e00001608577fa20 bsp=e000016085770ef0
> [<a00000010002f640>] do_sync_rbs+0xc0/0x100
> sp=e00001608577fa30 bsp=e000016085770ec0
> [<a00000010000b250>] unw_init_running+0x70/0xa0
> sp=e00001608577fa40 bsp=e000016085770e98
> [<a000000100033ee0>] ia64_sync_krbs+0x80/0xa0
> sp=e00001608577fe20 bsp=e000016085770e80
> [<a0000001000168a0>] do_notify_resume_user+0x1c0/0x1e0
> sp=e00001608577fe20 bsp=e000016085770e50
> [<a00000010000b0e0>] notify_resume_user+0x40/0x60
> sp=e00001608577fe20 bsp=e000016085770e00
> [<a00000010000b010>] skip_rbs_switch+0xe0/0x110
> sp=e00001608577fe30 bsp=e000016085770e00
> [<a000000000010720>] __kernel_syscall_via_break+0x0/0x20
> sp=e000016085780000 bsp=e000016085770e0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
2008-05-02 10:02 ` Petr Tesarik
@ 2008-05-02 22:53 ` Luck, Tony
2008-05-03 7:28 ` KOSAKI Motohiro
` (19 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Luck, Tony @ 2008-05-02 22:53 UTC (permalink / raw)
To: linux-ia64
> This surely is a bug. I bet this was introduced by Hidetoshi's latest
> commit:
>
> commit 38477ad75188b2a7370fef7145f956e6c446928b
> Author: Hidetoshi Seto
> Date: Mon Apr 21 14:34:39 2008 -0700
>
> [IA64] disable interrupts on exit of ia64_trace_syscall
Can you try reverting this patch and re-running the
same stress tests?
-Tony
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
2008-05-02 10:02 ` Petr Tesarik
2008-05-02 22:53 ` Luck, Tony
@ 2008-05-03 7:28 ` KOSAKI Motohiro
2008-05-04 15:47 ` KOSAKI Motohiro
` (18 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: KOSAKI Motohiro @ 2008-05-03 7:28 UTC (permalink / raw)
To: linux-ia64
> > This surely is a bug. I bet this was introduced by Hidetoshi's latest
> > commit:
> >
> > commit 38477ad75188b2a7370fef7145f956e6c446928b
> > Author: Hidetoshi Seto
> > Date: Mon Apr 21 14:34:39 2008 -0700
> >
> > [IA64] disable interrupts on exit of ia64_trace_syscall
>
> Can you try reverting this patch and re-running the
> same stress tests?
OK, I'll try it at head of next week.
Thank you!
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (2 preceding siblings ...)
2008-05-03 7:28 ` KOSAKI Motohiro
@ 2008-05-04 15:47 ` KOSAKI Motohiro
2008-05-05 8:40 ` Petr Tesarik
` (17 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: KOSAKI Motohiro @ 2008-05-04 15:47 UTC (permalink / raw)
To: linux-ia64
Hi Tony-san,
> > > This surely is a bug. I bet this was introduced by Hidetoshi's latest
> > > commit:
> > >
> > > commit 38477ad75188b2a7370fef7145f956e6c446928b
> > > Author: Hidetoshi Seto
> > > Date: Mon Apr 21 14:34:39 2008 -0700
> > >
> > > [IA64] disable interrupts on exit of ia64_trace_syscall
> >
> > Can you try reverting this patch and re-running the
> > same stress tests?
>
> OK, I'll try it at head of next week.
Hmmm,
if I am not stupid, I think 2.6.25-mm1 doesn't contain this patch.
I am very confusing now...
and, I found easy reproduce way.
that is
% pstack $$
Can you reproduce it?
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (3 preceding siblings ...)
2008-05-04 15:47 ` KOSAKI Motohiro
@ 2008-05-05 8:40 ` Petr Tesarik
2008-05-05 15:43 ` Petr Tesarik
` (16 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Petr Tesarik @ 2008-05-05 8:40 UTC (permalink / raw)
To: linux-ia64
On Mon, 2008-05-05 at 00:47 +0900, KOSAKI Motohiro wrote:
> Hi Tony-san,
>
> > > > This surely is a bug. I bet this was introduced by Hidetoshi's latest
> > > > commit:
> > > >
> > > > commit 38477ad75188b2a7370fef7145f956e6c446928b
> > > > Author: Hidetoshi Seto
> > > > Date: Mon Apr 21 14:34:39 2008 -0700
> > > >
> > > > [IA64] disable interrupts on exit of ia64_trace_syscall
> > >
> > > Can you try reverting this patch and re-running the
> > > same stress tests?
> >
> > OK, I'll try it at head of next week.
>
> Hmmm,
> if I am not stupid, I think 2.6.25-mm1 doesn't contain this patch.
> I am very confusing now...
You're right, this patch is not present in -mm1. I'm sorry for the
noise.
> and, I found easy reproduce way.
> that is
>
> % pstack $$
>
> Can you reproduce it?
Thank you for isolating the test case!
I tried SUSE Factory, which is a 2.6.25 (and was readily available to
me), and I could not reproduce it. I used gstack from gdb 6.6, because I
couldn't find a true pstack for Linux. I'm now compiling -mm1 to see if
it makes any difference. I can also try on a larger machine (the testing
one is a real small Altix 350 with 2 cores).
Regards,
Petr Tesarik
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (4 preceding siblings ...)
2008-05-05 8:40 ` Petr Tesarik
@ 2008-05-05 15:43 ` Petr Tesarik
2008-05-05 15:48 ` Petr Tesarik
` (15 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Petr Tesarik @ 2008-05-05 15:43 UTC (permalink / raw)
To: linux-ia64
On Mon, 2008-05-05 at 10:40 +0200, Petr Tesarik wrote:
> On Mon, 2008-05-05 at 00:47 +0900, KOSAKI Motohiro wrote:
> > Hi Tony-san,
> >
> > > > > This surely is a bug. I bet this was introduced by Hidetoshi's latest
> > > > > commit:
> > > > >
> > > > > commit 38477ad75188b2a7370fef7145f956e6c446928b
> > > > > Author: Hidetoshi Seto
> > > > > Date: Mon Apr 21 14:34:39 2008 -0700
> > > > >
> > > > > [IA64] disable interrupts on exit of ia64_trace_syscall
> > > >
> > > > Can you try reverting this patch and re-running the
> > > > same stress tests?
> > >
> > > OK, I'll try it at head of next week.
> >
> > Hmmm,
> > if I am not stupid, I think 2.6.25-mm1 doesn't contain this patch.
> > I am very confusing now...
>
> You're right, this patch is not present in -mm1. I'm sorry for the
> noise.
>
> > and, I found easy reproduce way.
> > that is
> >
> > % pstack $$
> >
> > Can you reproduce it?
>
> Thank you for isolating the test case!
>
> I tried SUSE Factory, which is a 2.6.25 (and was readily available to
> me), and I could not reproduce it. I used gstack from gdb 6.6, because I
> couldn't find a true pstack for Linux. I'm now compiling -mm1 to see if
> it makes any difference. I can also try on a larger machine (the testing
> one is a real small Altix 350 with 2 cores).
Unfortunately, I was not able to reproduce the bug you're seeing. Maybe
it depends on a specific config option..?
Petr
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (5 preceding siblings ...)
2008-05-05 15:43 ` Petr Tesarik
@ 2008-05-05 15:48 ` Petr Tesarik
2008-05-05 18:37 ` Luck, Tony
` (14 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Petr Tesarik @ 2008-05-05 15:48 UTC (permalink / raw)
To: linux-ia64
On Mon, 2008-05-05 at 00:47 +0900, KOSAKI Motohiro wrote:
> Hi Tony-san,
>
> > > > This surely is a bug. I bet this was introduced by Hidetoshi's latest
> > > > commit:
> > > >
> > > > commit 38477ad75188b2a7370fef7145f956e6c446928b
> > > > Author: Hidetoshi Seto
> > > > Date: Mon Apr 21 14:34:39 2008 -0700
> > > >
> > > > [IA64] disable interrupts on exit of ia64_trace_syscall
> > >
> > > Can you try reverting this patch and re-running the
> > > same stress tests?
> >
> > OK, I'll try it at head of next week.
>
> Hmmm,
> if I am not stupid, I think 2.6.25-mm1 doesn't contain this patch.
> I am very confusing now...
>
>
> and, I found easy reproduce way.
> that is
>
> % pstack $$
>
> Can you reproduce it?
Oh, by the way, could it be related to Stephen Eranian's note on
do_notify_resume_user being called too frequently? In other words, are
you running with perfmon?
Petr
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (6 preceding siblings ...)
2008-05-05 15:48 ` Petr Tesarik
@ 2008-05-05 18:37 ` Luck, Tony
2008-05-06 3:09 ` KOSAKI Motohiro
` (13 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Luck, Tony @ 2008-05-05 18:37 UTC (permalink / raw)
To: linux-ia64
> and, I found easy reproduce way.
> that is
>
> % pstack $$
>
> Can you reproduce it?
I tried 2.6.26-rc1 (actually about 50 commits past -rc1 as pulled
from kernel.org this morning) and could not reproduce this.
I was using the pstack(1) that shipped with Redhat EL4.5
I ran thousands of "pstack $$" with the system:
1) idle
2) busy (running kernel build with make -j16)
3) swapping (running hackbench)
and did not see the "BUG: sleeping function" message.
So Seto-san is off the hook (his patch is definitely in -rc1).
This is probably some other patch in -mm ... unless there is
something different about your .config. Do you have PREEMPT
enabled (or anything else that looks "interesting" for this
problem)?
-Tony
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (7 preceding siblings ...)
2008-05-05 18:37 ` Luck, Tony
@ 2008-05-06 3:09 ` KOSAKI Motohiro
2008-05-06 3:12 ` KOSAKI Motohiro
` (12 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: KOSAKI Motohiro @ 2008-05-06 3:09 UTC (permalink / raw)
To: linux-ia64
> > and, I found easy reproduce way.
> > that is
> >
> > % pstack $$
> >
> > Can you reproduce it?
>
> Oh, by the way, could it be related to Stephen Eranian's note on
> do_notify_resume_user being called too frequently? In other words, are
> you running with perfmon?
No. I don't use perfmon.
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (8 preceding siblings ...)
2008-05-06 3:09 ` KOSAKI Motohiro
@ 2008-05-06 3:12 ` KOSAKI Motohiro
2008-05-06 18:25 ` Luck, Tony
` (11 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: KOSAKI Motohiro @ 2008-05-06 3:12 UTC (permalink / raw)
To: linux-ia64
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
> I ran thousands of "pstack $$" with the system:
> 1) idle
> 2) busy (running kernel build with make -j16)
> 3) swapping (running hackbench)
>
> and did not see the "BUG: sleeping function" message.
>
> So Seto-san is off the hook (his patch is definitely in -rc1).
>
> This is probably some other patch in -mm ... unless there is
> something different about your .config. Do you have PREEMPT
> enabled (or anything else that looks "interesting" for this
> problem)?
no preempt.
attached my .config.
Hmm, amazing..
[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 31163 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.25-mm1
# Tue Apr 29 18:13:23 2008
#
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_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=20
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUP_CPUACCT is not set
CONFIG_RESOURCE_COUNTERS=y
CONFIG_MM_OWNER=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_SYSCTL_SYSCALL=y
CONFIG_SYSCTL_SYSCALL_CHECK=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_COMPAT_BRK=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_PROFILING=y
CONFIG_MARKERS=y
CONFIG_OPROFILE=m
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SLABINFO=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 is not set
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_IOSCHED_BFQ is not set
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_BFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_CLASSIC_RCU=y
#
# Processor type and features
#
CONFIG_IA64=y
CONFIG_64BIT=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_MMU=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_HUGETLB_PAGE_SIZE_VARIABLE=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_DMI=y
CONFIG_EFI=y
CONFIG_GENERIC_IOMAP=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_AUDIT_ARCH=y
CONFIG_IA64_GENERIC=y
# CONFIG_IA64_DIG is not set
# CONFIG_IA64_HP_ZX1 is not set
# CONFIG_IA64_HP_ZX1_SWIOTLB is not set
# CONFIG_IA64_SGI_SN2 is not set
# CONFIG_IA64_HP_SIM is not set
# CONFIG_ITANIUM is not set
CONFIG_MCKINLEY=y
# CONFIG_IA64_PAGE_SIZE_4KB is not set
# CONFIG_IA64_PAGE_SIZE_8KB is not set
# CONFIG_IA64_PAGE_SIZE_16KB is not set
CONFIG_IA64_PAGE_SIZE_64KB=y
CONFIG_PGTABLE_3=y
# CONFIG_PGTABLE_4 is not set
CONFIG_HZ=250
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
# CONFIG_SCHED_HRTICK is not set
CONFIG_IA64_L1_CACHE_SHIFT=7
CONFIG_IA64_CYCLONE=y
CONFIG_IOSAPIC=y
# CONFIG_IA64_SGI_SN_XP is not set
CONFIG_FORCE_MAX_ZONEORDER=17
# CONFIG_VIRT_CPU_ACCOUNTING is not set
CONFIG_SMP=y
CONFIG_NR_CPUS=512
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
# CONFIG_SCHED_SMT is not set
# CONFIG_PERMIT_BSP_REMOVE is not set
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y
CONFIG_NUMA=y
CONFIG_NODES_SHIFT=10
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
CONFIG_HAVE_ARCH_NODEDATA_EXTENSION=y
CONFIG_IA32_SUPPORT=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_IA64_MCA_RECOVERY=y
CONFIG_PERFMON=y
CONFIG_IA64_PALINFO=y
# CONFIG_IA64_MC_ERR_INJECT is not set
CONFIG_SGI_SN=y
# CONFIG_IA64_ESI is not set
# CONFIG_IA64_HP_AML_NFW is not set
#
# SN Devices
#
CONFIG_SGI_IOC3=m
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
#
# Firmware Drivers
#
CONFIG_EFI_VARS=y
CONFIG_EFI_PCDP=y
CONFIG_DMIID=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
#
# Power management and ACPI
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_ACPI=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_ACPI_CONTAINER=m
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA)
#
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_SYSCALL=y
CONFIG_PCIEPORTBUS=y
# CONFIG_HOTPLUG_PCI_PCIE is not set
CONFIG_PCIEAER=y
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
CONFIG_HOTPLUG_PCI=m
# CONFIG_HOTPLUG_PCI_FAKE is not set
CONFIG_HOTPLUG_PCI_ACPI=m
# CONFIG_HOTPLUG_PCI_ACPI_IBM is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
# CONFIG_HOTPLUG_PCI_SGI is not set
# CONFIG_PCCARD is not set
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
CONFIG_ARPD=y
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=m
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_MISC_DEVICES=y
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
CONFIG_SGI_IOC4=y
# CONFIG_TIFM_CORE is not set
# CONFIG_ENCLOSURE_SERVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
CONFIG_SCSI_SAS_ATTRS=m
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_STEX is not set
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_QLOGIC_1280=y
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_ATA is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID10=y
CONFIG_MD_RAID456=y
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=y
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
# CONFIG_DM_MULTIPATH_EMC is not set
# CONFIG_DM_MULTIPATH_RDAC is not set
# CONFIG_DM_MULTIPATH_HP is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_CTL=m
# CONFIG_FUSION_LOGGING is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
CONFIG_EEPRO100=m
CONFIG_E100=m
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000_NAPI is not set
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
CONFIG_E1000E=y
CONFIG_E1000E_ENABLED=y
# CONFIG_IP1000 is not set
# CONFIG_IGB is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=y
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
CONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not set
# CONFIG_TR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_IWLWIFI_LEDS is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
CONFIG_NETCONSOLE=y
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
CONFIG_GAMEPORT=m
# CONFIG_GAMEPORT_NS558 is not set
# CONFIG_GAMEPORT_L4 is not set
# CONFIG_GAMEPORT_EMU10K1 is not set
# CONFIG_GAMEPORT_FM801 is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
# CONFIG_NOZOMI is not set
CONFIG_SGI_SNSC=y
CONFIG_SGI_TIOCX=y
CONFIG_SGI_MBCS=m
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=6
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_RSA is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_SGI_L1_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_SERIAL_SGI_IOC4=y
# CONFIG_SERIAL_SGI_IOC3 is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_IPMI_HANDLER=m
CONFIG_IPMI_PANIC_EVENT=y
# CONFIG_IPMI_PANIC_STRING is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
# CONFIG_HW_RANDOM is not set
CONFIG_EFI_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set
CONFIG_MMTIMER=y
# CONFIG_TCG_TPM is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set
# CONFIG_SPI is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_IBMPEX is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_THERMAL=y
# CONFIG_WATCHDOG is not set
#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set
#
# Graphics support
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set
#
# USB Input Devices
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_WUSB is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HWA_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
CONFIG_USB_MON=y
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GOTEMP is not set
# CONFIG_USB_GADGET is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_UIO is not set
# CONFIG_MSPEC is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4DEV_FS=y
CONFIG_EXT4DEV_FS_XATTR=y
CONFIG_EXT4DEV_FS_POSIX_ACL=y
CONFIG_EXT4DEV_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISER4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
#
# Layered filesystems
#
# CONFIG_UNION_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_NETWORK_FILESYSTEMS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
CONFIG_NLS_CODEPAGE_932=m
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m
# CONFIG_DLM is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=y
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
# CONFIG_TRACE is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_PER_CPU=y
#
# HP Simulator drivers
#
# CONFIG_HP_SIMETH is not set
# CONFIG_HP_SIMSERIAL is not set
# CONFIG_HP_SIMSCSI is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_PAGE_OWNER is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_VM=y
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_PROFILE_LIKELY is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DEBUG_SYNCHRO_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_SAMPLES is not set
CONFIG_IA64_GRANULE_16MB=y
# CONFIG_IA64_GRANULE_64MB is not set
# CONFIG_IA64_PRINT_HAZARDS is not set
# CONFIG_DISABLE_VHPT is not set
# CONFIG_IA64_DEBUG_CMPXCHG is not set
# CONFIG_IA64_DEBUG_IRQ is not set
CONFIG_SYSVIPC_COMPAT=y
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_XOR_BLOCKS=y
CONFIG_ASYNC_CORE=y
CONFIG_ASYNC_MEMCPY=y
CONFIG_ASYNC_XOR=y
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_MANAGER=m
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set
#
# Block modes
#
CONFIG_CRYPTO_CBC=m
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=m
# CONFIG_CRYPTO_LRW is not set
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=m
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_LZO is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (9 preceding siblings ...)
2008-05-06 3:12 ` KOSAKI Motohiro
@ 2008-05-06 18:25 ` Luck, Tony
2008-05-06 20:03 ` Luck, Tony
` (10 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Luck, Tony @ 2008-05-06 18:25 UTC (permalink / raw)
To: linux-ia64
> attached my .config.
>
> Hmm, amazing..
Ah. With that .config I see the "BUG:" too (on linus-latest).
Now to try to figure out what is different in that one
from the tiger_defconfig.
-Tony
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (10 preceding siblings ...)
2008-05-06 18:25 ` Luck, Tony
@ 2008-05-06 20:03 ` Luck, Tony
2008-05-06 21:41 ` Luck, Tony
` (9 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Luck, Tony @ 2008-05-06 20:03 UTC (permalink / raw)
To: linux-ia64
> Now to try to figure out what is different in that one
> from the tiger_defconfig.
Well that was obvious ... CONFIG_DEBUG_SPINLOCK_SLEEP
Now that I can reproduce it easily, I tried backing
out Seto-san's fix to entry.S ... and the "pstack $$"
test still gives the BUG.
So it's definitely in mainline, and its definitely
not Seto-san's patch.
-Tony
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (11 preceding siblings ...)
2008-05-06 20:03 ` Luck, Tony
@ 2008-05-06 21:41 ` Luck, Tony
2008-05-06 21:54 ` Luck, Tony
` (8 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Luck, Tony @ 2008-05-06 21:41 UTC (permalink / raw)
To: linux-ia64
> So it's definitely in mainline, and its definitely
> not Seto-san's patch.
Here's the root of the problem (arch/ia64/kernel/entry.S):
1175 br.call.spnt.many rp=schedule
1176 .ret9: cmp.eq p6,p0=r0,r0 // p6 <- 1
1177 rsm psr.i // disable interrupts
1178 ;;
1179 #ifdef CONFIG_PREEMPT
1180 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
1181 ;;
1182 (pKStk) st4 [r20]=r0 // preempt_count() <- 0
1183 #endif
1184 (pLvSys)br.cond.sptk.few .work_pending_syscall_end
1185 br.cond.sptk.many .work_processed_kernel // re-check
1186
1187 .notify:
1188 (pUStk) br.call.spnt.many rp=notify_resume_user
on line 1188 we call notify_resume_user() with interrupts disabled (at
least if we fall through from the code above ... I didn't check the
state of interrupts if we branch to ".notify").
So we start down this call chain to the might_sleep() check:
[<a000000100011bf0>] show_stack+0x50/0xa0
[<a000000100011c70>] dump_stack+0x30/0x60
[<a000000100061a90>] __might_sleep+0x1f0/0x220
[<a000000100709020>] down_read+0x20/0x60
[<a0000001000fe060>] access_process_vm+0x60/0x2c0
[<a00000010002a280>] ia64_sync_kernel_rbs+0x40/0x100
[<a00000010002a400>] do_sync_rbs+0xc0/0x100
[<a00000010000ac30>] unw_init_running+0x70/0xa0
[<a00000010002a5c0>] ia64_sync_krbs+0x80/0xa0
[<a000000100012690>] do_notify_resume_user+0x110/0x140
[<a00000010000aac0>] notify_resume_user+0x40/0x60
[<a00000010000a9f0>] skip_rbs_switch+0xe0/0x110
[<a000000000010740>] __kernel_syscall_via_break+0x0/0x20
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (12 preceding siblings ...)
2008-05-06 21:41 ` Luck, Tony
@ 2008-05-06 21:54 ` Luck, Tony
2008-05-07 0:57 ` Hidetoshi Seto
` (7 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Luck, Tony @ 2008-05-06 21:54 UTC (permalink / raw)
To: linux-ia64
> 1185 br.cond.sptk.many .work_processed_kernel // re-check
> 1186
> 1187 .notify:
> 1188 (pUStk) br.call.spnt.many rp=notify_resume_user
>
> on line 1188 we call notify_resume_user() with interrupts disabled (at
> least if we fall through from the code above ... I didn't check the
> state of interrupts if we branch to ".notify").
Oops ... that's a br.cond on 1185 (not a br.call) ... so there is
no fall through to .notify. So we do have to trace backwards and
check on the state of interrupts for the places that branch to the
.notify label ... someone is doing so with interrupts masked.
-Tony
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (13 preceding siblings ...)
2008-05-06 21:54 ` Luck, Tony
@ 2008-05-07 0:57 ` Hidetoshi Seto
2008-05-07 6:59 ` Petr Tesarik
` (6 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Hidetoshi Seto @ 2008-05-07 0:57 UTC (permalink / raw)
To: linux-ia64
Hi all,
Luck, Tony wrote:
>> So it's definitely in mainline, and its definitely
>> not Seto-san's patch.
>
> Here's the root of the problem (arch/ia64/kernel/entry.S):
>
Please see:
841 GLOBAL_ENTRY(ia64_leave_kernel)
842 PT_REGS_UNWIND_INFO(0)
843 /*
844 * work.need_resched etc. mustn't get changed by this CPU before it returns to
845 * user- or fsys-mode, hence we disable interrupts early on.
846 *
847 * p6 controls whether current_thread_info()->flags needs to be check for
848 * extra work. We always check for extra work when returning to user-level.
849 * With CONFIG_PREEMPT, we also check for extra work when the preempt_count
850 * is 0. After extra work processing has been completed, execution
851 * resumes at .work_processed_syscall with p6 set to 1 if the extra-work-check
852 * needs to be redone.
853 */
854 #ifdef CONFIG_PREEMPT
855 rsm psr.i // disable interrupts
856 cmp.eq p0,pLvSys=r0,r0 // pLvSys=0: leave from
856 kernel
857 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
858 ;;
859 .pred.rel.mutex pUStk,pKStk
860 (pKStk) ld4 r21=[r20] // r21 <- preempt_count
861 (pUStk) mov r21=0 // r21 <- 0
862 ;;
863 cmp.eq p6,p0=r21,r0 // p6 <- pUStk || (preempt_count
863 = 0)
864 #else
865 (pUStk) rsm psr.i
866 cmp.eq p0,pLvSys=r0,r0 // pLvSys=0: leave from kernel
867 (pUStk) cmp.eq.unc p6,p0=r0,r0 // p6 <- pUStk
868 #endif
869 .work_processed_kernel:
870 adds r17=TI_FLAGS+IA64_TASK_SIZE,r13
871 ;;
872 (p6) ld4 r31=[r17] // load current_thread_i
872 nfo()->flags
873 adds r21=PT(PR)+16,r12
874 ;;
875
876 lfetch [r21],PT(CR_IPSR)-PT(PR)
877 adds r2=PT(B6)+16,r12
878 adds r3=PT(R16)+16,r12
879 ;;
880 lfetch [r21]
881 ld8 r28=[r2],8 // load b6
882 adds r29=PT(R24)+16,r12
883
884 ld8.fill r16=[r3],PT(AR_CSD)-PT(R16)
885 adds r30=PT(AR_CCV)+16,r12
886 (p6) and r19=TIF_WORK_MASK,r31 // any work other than T
886 IF_SYSCALL_TRACE?
887 ;;
888 ld8.fill r24=[r29]
889 ld8 r15=[r30] // load ar.ccv
890 (p6) cmp4.ne.unc p6,p0=r19, r0 // any special work pend
890 ing?
891 ;;
892 ld8 r29=[r2],16 // load b7
893 ld8 r30=[r3],16 // load ar.csd
894 (p6) br.cond.spnt .work_pending
and:
1160 .work_pending_syscall:
1161 add r2=-8,r2
1162 add r3=-8,r3
1163 ;;
1164 st8 [r2]=r8
1165 st8 [r3]=r10
1166 .work_pending:
1167 tbit.z p6,p0=r31,TIF_NEED_RESCHED // current_thread_info()->need_resched=0?
1168 (p6) br.cond.sptk.few .notify
1169 #ifdef CONFIG_PREEMPT
1170 (pKStk) dep r21=-1,r0,PREEMPT_ACTIVE_BIT,1
1171 ;;
1172 (pKStk) st4 [r20]=r21
1173 ssm psr.i // enable interrupts
1174 #endif
> 1175 br.call.spnt.many rp=schedule
> 1176 .ret9: cmp.eq p6,p0=r0,r0 // p6 <- 1
> 1177 rsm psr.i // disable interrupts
> 1178 ;;
> 1179 #ifdef CONFIG_PREEMPT
> 1180 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
> 1181 ;;
> 1182 (pKStk) st4 [r20]=r0 // preempt_count() <- 0
> 1183 #endif
> 1184 (pLvSys)br.cond.sptk.few .work_pending_syscall_end
> 1185 br.cond.sptk.many .work_processed_kernel // re-check
> 1186
> 1187 .notify:
> 1188 (pUStk) br.call.spnt.many rp=notify_resume_user
>
> on line 1188 we call notify_resume_user() with interrupts disabled (at
> least if we fall through from the code above ... I didn't check the
> state of interrupts if we branch to ".notify").
AFAIK, we always call notify_resume_user() with interrupts disabled.
Is this right?
> So we start down this call chain to the might_sleep() check:
>
> [<a000000100011bf0>] show_stack+0x50/0xa0
> [<a000000100011c70>] dump_stack+0x30/0x60
> [<a000000100061a90>] __might_sleep+0x1f0/0x220
> [<a000000100709020>] down_read+0x20/0x60
> [<a0000001000fe060>] access_process_vm+0x60/0x2c0
> [<a00000010002a280>] ia64_sync_kernel_rbs+0x40/0x100
> [<a00000010002a400>] do_sync_rbs+0xc0/0x100
> [<a00000010000ac30>] unw_init_running+0x70/0xa0
> [<a00000010002a5c0>] ia64_sync_krbs+0x80/0xa0
> [<a000000100012690>] do_notify_resume_user+0x110/0x140
> [<a00000010000aac0>] notify_resume_user+0x40/0x60
> [<a00000010000a9f0>] skip_rbs_switch+0xe0/0x110
> [<a000000000010740>] __kernel_syscall_via_break+0x0/0x20
So, I think the problem is not "why interrupts are disabled," but
"why sleep in this path which always with interrupts disabled."
It obviously means ia64_sync_kernel_rbs should care about that.
The function was introduced by the following commit:
> commit 3b2ce0b17824c42bc2e46f7dd903b4acf5e9fff9
> Author: Petr Tesarik <ptesarik@suse.cz>
> Date: Wed Dec 12 15:23:34 2007 +0100
>
> [IA64] Synchronize kernel RSE to user-space and back
Hmm, could you make ia64_sync_kernel_rbs to safe with interrupts
disabled, Petr?
Thanks,
H.Seto
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (14 preceding siblings ...)
2008-05-07 0:57 ` Hidetoshi Seto
@ 2008-05-07 6:59 ` Petr Tesarik
2008-05-07 8:54 ` Shaohua Li
` (5 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Petr Tesarik @ 2008-05-07 6:59 UTC (permalink / raw)
To: linux-ia64
On Wed, 2008-05-07 at 09:57 +0900, Hidetoshi Seto wrote:
> Hi all,
>
> Luck, Tony wrote:
> >> So it's definitely in mainline, and its definitely
> >> not Seto-san's patch.
> >
> > Here's the root of the problem (arch/ia64/kernel/entry.S):
> >
> Please see:
>
> 841 GLOBAL_ENTRY(ia64_leave_kernel)
> 842 PT_REGS_UNWIND_INFO(0)
> 843 /*
> 844 * work.need_resched etc. mustn't get changed by this CPU before it returns to
> 845 * user- or fsys-mode, hence we disable interrupts early on.
> 846 *
> 847 * p6 controls whether current_thread_info()->flags needs to be check for
> 848 * extra work. We always check for extra work when returning to user-level.
> 849 * With CONFIG_PREEMPT, we also check for extra work when the preempt_count
> 850 * is 0. After extra work processing has been completed, execution
> 851 * resumes at .work_processed_syscall with p6 set to 1 if the extra-work-check
> 852 * needs to be redone.
> 853 */
> 854 #ifdef CONFIG_PREEMPT
> 855 rsm psr.i // disable interrupts
> 856 cmp.eq p0,pLvSys=r0,r0 // pLvSys=0: leave from
> 856 kernel
> 857 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
> 858 ;;
> 859 .pred.rel.mutex pUStk,pKStk
> 860 (pKStk) ld4 r21=[r20] // r21 <- preempt_count
> 861 (pUStk) mov r21=0 // r21 <- 0
> 862 ;;
> 863 cmp.eq p6,p0=r21,r0 // p6 <- pUStk || (preempt_count
> 863 = 0)
> 864 #else
> 865 (pUStk) rsm psr.i
> 866 cmp.eq p0,pLvSys=r0,r0 // pLvSys=0: leave from kernel
> 867 (pUStk) cmp.eq.unc p6,p0=r0,r0 // p6 <- pUStk
> 868 #endif
> 869 .work_processed_kernel:
> 870 adds r17=TI_FLAGS+IA64_TASK_SIZE,r13
> 871 ;;
> 872 (p6) ld4 r31=[r17] // load current_thread_i
> 872 nfo()->flags
> 873 adds r21=PT(PR)+16,r12
> 874 ;;
> 875
> 876 lfetch [r21],PT(CR_IPSR)-PT(PR)
> 877 adds r2=PT(B6)+16,r12
> 878 adds r3=PT(R16)+16,r12
> 879 ;;
> 880 lfetch [r21]
> 881 ld8 r28=[r2],8 // load b6
> 882 adds r29=PT(R24)+16,r12
> 883
> 884 ld8.fill r16=[r3],PT(AR_CSD)-PT(R16)
> 885 adds r30=PT(AR_CCV)+16,r12
> 886 (p6) and r19=TIF_WORK_MASK,r31 // any work other than T
> 886 IF_SYSCALL_TRACE?
> 887 ;;
> 888 ld8.fill r24=[r29]
> 889 ld8 r15=[r30] // load ar.ccv
> 890 (p6) cmp4.ne.unc p6,p0=r19, r0 // any special work pend
> 890 ing?
> 891 ;;
> 892 ld8 r29=[r2],16 // load b7
> 893 ld8 r30=[r3],16 // load ar.csd
> 894 (p6) br.cond.spnt .work_pending
>
> and:
>
> 1160 .work_pending_syscall:
> 1161 add r2=-8,r2
> 1162 add r3=-8,r3
> 1163 ;;
> 1164 st8 [r2]=r8
> 1165 st8 [r3]=r10
> 1166 .work_pending:
> 1167 tbit.z p6,p0=r31,TIF_NEED_RESCHED // current_thread_info()->need_resched=0?
> 1168 (p6) br.cond.sptk.few .notify
> 1169 #ifdef CONFIG_PREEMPT
> 1170 (pKStk) dep r21=-1,r0,PREEMPT_ACTIVE_BIT,1
> 1171 ;;
> 1172 (pKStk) st4 [r20]=r21
> 1173 ssm psr.i // enable interrupts
> 1174 #endif
> > 1175 br.call.spnt.many rp=schedule
> > 1176 .ret9: cmp.eq p6,p0=r0,r0 // p6 <- 1
> > 1177 rsm psr.i // disable interrupts
> > 1178 ;;
> > 1179 #ifdef CONFIG_PREEMPT
> > 1180 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
> > 1181 ;;
> > 1182 (pKStk) st4 [r20]=r0 // preempt_count() <- 0
> > 1183 #endif
> > 1184 (pLvSys)br.cond.sptk.few .work_pending_syscall_end
> > 1185 br.cond.sptk.many .work_processed_kernel // re-check
> > 1186
> > 1187 .notify:
> > 1188 (pUStk) br.call.spnt.many rp=notify_resume_user
> >
> > on line 1188 we call notify_resume_user() with interrupts disabled (at
> > least if we fall through from the code above ... I didn't check the
> > state of interrupts if we branch to ".notify").
>
> AFAIK, we always call notify_resume_user() with interrupts disabled.
> Is this right?
>
> > So we start down this call chain to the might_sleep() check:
> >
> > [<a000000100011bf0>] show_stack+0x50/0xa0
> > [<a000000100011c70>] dump_stack+0x30/0x60
> > [<a000000100061a90>] __might_sleep+0x1f0/0x220
> > [<a000000100709020>] down_read+0x20/0x60
> > [<a0000001000fe060>] access_process_vm+0x60/0x2c0
> > [<a00000010002a280>] ia64_sync_kernel_rbs+0x40/0x100
> > [<a00000010002a400>] do_sync_rbs+0xc0/0x100
> > [<a00000010000ac30>] unw_init_running+0x70/0xa0
> > [<a00000010002a5c0>] ia64_sync_krbs+0x80/0xa0
> > [<a000000100012690>] do_notify_resume_user+0x110/0x140
> > [<a00000010000aac0>] notify_resume_user+0x40/0x60
> > [<a00000010000a9f0>] skip_rbs_switch+0xe0/0x110
> > [<a000000000010740>] __kernel_syscall_via_break+0x0/0x20
>
> So, I think the problem is not "why interrupts are disabled," but
> "why sleep in this path which always with interrupts disabled."
>
> It obviously means ia64_sync_kernel_rbs should care about that.
> The function was introduced by the following commit:
>
> > commit 3b2ce0b17824c42bc2e46f7dd903b4acf5e9fff9
> > Author: Petr Tesarik <ptesarik@suse.cz>
> > Date: Wed Dec 12 15:23:34 2007 +0100
> >
> > [IA64] Synchronize kernel RSE to user-space and back
>
> Hmm, could you make ia64_sync_kernel_rbs to safe with interrupts
> disabled, Petr?
No, the point of that function is to copy part of the kernel RBS to user
RBS. Accesses to user space are always allowed to sleep and there's
nothing I can do about it (without rewriting the whole memory management
in Linux from scratch). All I can do is to take the simpler approach
without TIF_RESTORE_RSE I proposed in the very beginning of the RSE sync
discussion, but which was then turned down, because Roland warned about
possible severe performance degradations.
The introduction of TIF_RESTORE_RSE was originally Shaohua's idea, so
maybe he knows how to do it properly.
BTW why must be interrupts disabled in this path? Would it be possible
to re-enable them for the duration of the synchronization, or does it
harm somehow?
Petr Tesarik
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (15 preceding siblings ...)
2008-05-07 6:59 ` Petr Tesarik
@ 2008-05-07 8:54 ` Shaohua Li
2008-05-07 9:05 ` Hidetoshi Seto
` (4 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Shaohua Li @ 2008-05-07 8:54 UTC (permalink / raw)
To: linux-ia64
On Wed, 2008-05-07 at 08:59 +0200, Petr Tesarik wrote:
> On Wed, 2008-05-07 at 09:57 +0900, Hidetoshi Seto wrote:
> > Hi all,
> >
> > Luck, Tony wrote:
> > >> So it's definitely in mainline, and its definitely
> > >> not Seto-san's patch.
> > >
> > > Here's the root of the problem (arch/ia64/kernel/entry.S):
> > >
> > Please see:
> >
> > 841 GLOBAL_ENTRY(ia64_leave_kernel)
> > 842 PT_REGS_UNWIND_INFO(0)
> > 843 /*
> > 844 * work.need_resched etc. mustn't get changed by this CPU before it returns to
> > 845 * user- or fsys-mode, hence we disable interrupts early on.
> > 846 *
> > 847 * p6 controls whether current_thread_info()->flags needs to be check for
> > 848 * extra work. We always check for extra work when returning to user-level.
> > 849 * With CONFIG_PREEMPT, we also check for extra work when the preempt_count
> > 850 * is 0. After extra work processing has been completed, execution
> > 851 * resumes at .work_processed_syscall with p6 set to 1 if the extra-work-check
> > 852 * needs to be redone.
> > 853 */
> > 854 #ifdef CONFIG_PREEMPT
> > 855 rsm psr.i // disable interrupts
> > 856 cmp.eq p0,pLvSys=r0,r0 // pLvSys=0: leave from
> > 856 kernel
> > 857 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
> > 858 ;;
> > 859 .pred.rel.mutex pUStk,pKStk
> > 860 (pKStk) ld4 r21=[r20] // r21 <- preempt_count
> > 861 (pUStk) mov r21=0 // r21 <- 0
> > 862 ;;
> > 863 cmp.eq p6,p0=r21,r0 // p6 <- pUStk || (preempt_count
> > 863 = 0)
> > 864 #else
> > 865 (pUStk) rsm psr.i
> > 866 cmp.eq p0,pLvSys=r0,r0 // pLvSys=0: leave from kernel
> > 867 (pUStk) cmp.eq.unc p6,p0=r0,r0 // p6 <- pUStk
> > 868 #endif
> > 869 .work_processed_kernel:
> > 870 adds r17=TI_FLAGS+IA64_TASK_SIZE,r13
> > 871 ;;
> > 872 (p6) ld4 r31=[r17] // load current_thread_i
> > 872 nfo()->flags
> > 873 adds r21=PT(PR)+16,r12
> > 874 ;;
> > 875
> > 876 lfetch [r21],PT(CR_IPSR)-PT(PR)
> > 877 adds r2=PT(B6)+16,r12
> > 878 adds r3=PT(R16)+16,r12
> > 879 ;;
> > 880 lfetch [r21]
> > 881 ld8 r28=[r2],8 // load b6
> > 882 adds r29=PT(R24)+16,r12
> > 883
> > 884 ld8.fill r16=[r3],PT(AR_CSD)-PT(R16)
> > 885 adds r30=PT(AR_CCV)+16,r12
> > 886 (p6) and r19=TIF_WORK_MASK,r31 // any work other than T
> > 886 IF_SYSCALL_TRACE?
> > 887 ;;
> > 888 ld8.fill r24=[r29]
> > 889 ld8 r15=[r30] // load ar.ccv
> > 890 (p6) cmp4.ne.unc p6,p0=r19, r0 // any special work pend
> > 890 ing?
> > 891 ;;
> > 892 ld8 r29=[r2],16 // load b7
> > 893 ld8 r30=[r3],16 // load ar.csd
> > 894 (p6) br.cond.spnt .work_pending
> >
> > and:
> >
> > 1160 .work_pending_syscall:
> > 1161 add r2=-8,r2
> > 1162 add r3=-8,r3
> > 1163 ;;
> > 1164 st8 [r2]=r8
> > 1165 st8 [r3]=r10
> > 1166 .work_pending:
> > 1167 tbit.z p6,p0=r31,TIF_NEED_RESCHED // current_thread_info()->need_resched=0?
> > 1168 (p6) br.cond.sptk.few .notify
> > 1169 #ifdef CONFIG_PREEMPT
> > 1170 (pKStk) dep r21=-1,r0,PREEMPT_ACTIVE_BIT,1
> > 1171 ;;
> > 1172 (pKStk) st4 [r20]=r21
> > 1173 ssm psr.i // enable interrupts
> > 1174 #endif
> > > 1175 br.call.spnt.many rp=schedule
> > > 1176 .ret9: cmp.eq p6,p0=r0,r0 // p6 <- 1
> > > 1177 rsm psr.i // disable interrupts
> > > 1178 ;;
> > > 1179 #ifdef CONFIG_PREEMPT
> > > 1180 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
> > > 1181 ;;
> > > 1182 (pKStk) st4 [r20]=r0 // preempt_count() <- 0
> > > 1183 #endif
> > > 1184 (pLvSys)br.cond.sptk.few .work_pending_syscall_end
> > > 1185 br.cond.sptk.many .work_processed_kernel // re-check
> > > 1186
> > > 1187 .notify:
> > > 1188 (pUStk) br.call.spnt.many rp=notify_resume_user
> > >
> > > on line 1188 we call notify_resume_user() with interrupts disabled (at
> > > least if we fall through from the code above ... I didn't check the
> > > state of interrupts if we branch to ".notify").
> >
> > AFAIK, we always call notify_resume_user() with interrupts disabled.
> > Is this right?
> >
> > > So we start down this call chain to the might_sleep() check:
> > >
> > > [<a000000100011bf0>] show_stack+0x50/0xa0
> > > [<a000000100011c70>] dump_stack+0x30/0x60
> > > [<a000000100061a90>] __might_sleep+0x1f0/0x220
> > > [<a000000100709020>] down_read+0x20/0x60
> > > [<a0000001000fe060>] access_process_vm+0x60/0x2c0
> > > [<a00000010002a280>] ia64_sync_kernel_rbs+0x40/0x100
> > > [<a00000010002a400>] do_sync_rbs+0xc0/0x100
> > > [<a00000010000ac30>] unw_init_running+0x70/0xa0
> > > [<a00000010002a5c0>] ia64_sync_krbs+0x80/0xa0
> > > [<a000000100012690>] do_notify_resume_user+0x110/0x140
> > > [<a00000010000aac0>] notify_resume_user+0x40/0x60
> > > [<a00000010000a9f0>] skip_rbs_switch+0xe0/0x110
> > > [<a000000000010740>] __kernel_syscall_via_break+0x0/0x20
> >
> > So, I think the problem is not "why interrupts are disabled," but
> > "why sleep in this path which always with interrupts disabled."
> >
> > It obviously means ia64_sync_kernel_rbs should care about that.
> > The function was introduced by the following commit:
> >
> > > commit 3b2ce0b17824c42bc2e46f7dd903b4acf5e9fff9
> > > Author: Petr Tesarik <ptesarik@suse.cz>
> > > Date: Wed Dec 12 15:23:34 2007 +0100
> > >
> > > [IA64] Synchronize kernel RSE to user-space and back
> >
> > Hmm, could you make ia64_sync_kernel_rbs to safe with interrupts
> > disabled, Petr?
>
> No, the point of that function is to copy part of the kernel RBS to user
> RBS. Accesses to user space are always allowed to sleep and there's
> nothing I can do about it (without rewriting the whole memory management
> in Linux from scratch). All I can do is to take the simpler approach
> without TIF_RESTORE_RSE I proposed in the very beginning of the RSE sync
> discussion, but which was then turned down, because Roland warned about
> possible severe performance degradations.
>
> The introduction of TIF_RESTORE_RSE was originally Shaohua's idea, so
> maybe he knows how to do it properly.
>
> BTW why must be interrupts disabled in this path? Would it be possible
> to re-enable them for the duration of the synchronization, or does it
> harm somehow?
No idea how to fix it. i have the same question why
do_notify_resume_user in called with interrupt disabled.
do_notify_resume_user->ia64_do_signal->get_signal_to_deliver which could
sleep (like try_to_freeze) and this routine calls
spin_lock_irq()/spin_unlock_irq(), this will enable interrupt.
Thanks,
Shaohua
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (16 preceding siblings ...)
2008-05-07 8:54 ` Shaohua Li
@ 2008-05-07 9:05 ` Hidetoshi Seto
2008-05-07 9:12 ` Hidetoshi Seto
` (3 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Hidetoshi Seto @ 2008-05-07 9:05 UTC (permalink / raw)
To: linux-ia64
Oh, wait...
Petr Tesarik wrote:
> On Wed, 2008-05-07 at 09:57 +0900, Hidetoshi Seto wrote:
>>
>> 1160 .work_pending_syscall:
>> 1161 add r2=-8,r2
>> 1162 add r3=-8,r3
>> 1163 ;;
>> 1164 st8 [r2]=r8
>> 1165 st8 [r3]=r10
>> 1166 .work_pending:
>> 1167 tbit.z p6,p0=r31,TIF_NEED_RESCHED // current_thread_info()->need_resched=0?
>> 1168 (p6) br.cond.sptk.few .notify
>> 1169 #ifdef CONFIG_PREEMPT
>> 1170 (pKStk) dep r21=-1,r0,PREEMPT_ACTIVE_BIT,1
>> 1171 ;;
>> 1172 (pKStk) st4 [r20]=r21
>> 1173 ssm psr.i // enable interrupts
>> 1174 #endif
>>> 1175 br.call.spnt.many rp=schedule
>>> 1176 .ret9: cmp.eq p6,p0=r0,r0 // p6 <- 1
>>> 1177 rsm psr.i // disable interrupts
>>> 1178 ;;
>>> 1179 #ifdef CONFIG_PREEMPT
>>> 1180 (pKStk) adds r20=TI_PRE_COUNT+IA64_TASK_SIZE,r13
>>> 1181 ;;
>>> 1182 (pKStk) st4 [r20]=r0 // preempt_count() <- 0
>>> 1183 #endif
>>> 1184 (pLvSys)br.cond.sptk.few .work_pending_syscall_end
>>> 1185 br.cond.sptk.many .work_processed_kernel // re-check
>>> 1186
>>> 1187 .notify:
>>> 1188 (pUStk) br.call.spnt.many rp=notify_resume_user
>>>
>> AFAIK, we always call notify_resume_user() with interrupts disabled.
>> Is this right?
If I am right, this also means we always call schedule() with interrupts
disabled, when it is required without CONFIG_PREEMPT.
...Doesn't it matter, Tony? I think it is quite strange.
>> Hmm, could you make ia64_sync_kernel_rbs to safe with interrupts
>> disabled, Petr?
>
> No, the point of that function is to copy part of the kernel RBS to user
> RBS. Accesses to user space are always allowed to sleep and there's
> nothing I can do about it (without rewriting the whole memory management
> in Linux from scratch). All I can do is to take the simpler approach
> without TIF_RESTORE_RSE I proposed in the very beginning of the RSE sync
> discussion, but which was then turned down, because Roland warned about
> possible severe performance degradations.
>
> The introduction of TIF_RESTORE_RSE was originally Shaohua's idea, so
> maybe he knows how to do it properly.
>
> BTW why must be interrupts disabled in this path? Would it be possible
> to re-enable them for the duration of the synchronization, or does it
> harm somehow?
Good point.
I'm not sure the reason, but I suppose we can call notify_resume_user()
and schedule() with interrupts enabled. Possibly we must do so.
Thanks,
H.Seto
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (17 preceding siblings ...)
2008-05-07 9:05 ` Hidetoshi Seto
@ 2008-05-07 9:12 ` Hidetoshi Seto
2008-05-07 18:20 ` Roland McGrath
` (2 subsequent siblings)
21 siblings, 0 replies; 23+ messages in thread
From: Hidetoshi Seto @ 2008-05-07 9:12 UTC (permalink / raw)
To: linux-ia64
Shaohua Li wrote:
> On Wed, 2008-05-07 at 08:59 +0200, Petr Tesarik wrote:
>> BTW why must be interrupts disabled in this path? Would it be possible
>> to re-enable them for the duration of the synchronization, or does it
>> harm somehow?
> No idea how to fix it. i have the same question why
> do_notify_resume_user in called with interrupt disabled.
> do_notify_resume_user->ia64_do_signal->get_signal_to_deliver which could
> sleep (like try_to_freeze) and this routine calls
> spin_lock_irq()/spin_unlock_irq(), this will enable interrupt.
Yes, I found it too.
It seems that ia64_do_signal should be called with interrupts enabled.
Thanks,
H.Seto
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (18 preceding siblings ...)
2008-05-07 9:12 ` Hidetoshi Seto
@ 2008-05-07 18:20 ` Roland McGrath
2008-05-07 21:50 ` Luck, Tony
2008-05-07 23:23 ` Roland McGrath
21 siblings, 0 replies; 23+ messages in thread
From: Roland McGrath @ 2008-05-07 18:20 UTC (permalink / raw)
To: linux-ia64
It sure sounds wrong to me that notify_resume_user runs with interrupts
disabled.
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (19 preceding siblings ...)
2008-05-07 18:20 ` Roland McGrath
@ 2008-05-07 21:50 ` Luck, Tony
2008-05-07 23:23 ` Roland McGrath
21 siblings, 0 replies; 23+ messages in thread
From: Luck, Tony @ 2008-05-07 21:50 UTC (permalink / raw)
To: linux-ia64
> It sure sounds wrong to me that notify_resume_user runs with interrupts
> disabled.
The "leave kernel" paths on ia64 are a bit tortuous ... clearly there
is some point at which the kernel needs to lock out interrupts and
just get on with returning to the user. We don't want to allow races
after we check the TIF* bits where interrupts could result in more
signals pending for the process.
Perhaps we can re-order things to satisfy all the interrupts enabled
vs. interrupts disabled requirements.
-Tony
^ permalink raw reply [flat|nested] 23+ messages in thread* RE: [BUG?][2.6.25-mm1] sleeping during IRQ disabled
2008-05-02 9:27 [BUG?][2.6.25-mm1] sleeping during IRQ disabled KOSAKI Motohiro
` (20 preceding siblings ...)
2008-05-07 21:50 ` Luck, Tony
@ 2008-05-07 23:23 ` Roland McGrath
21 siblings, 0 replies; 23+ messages in thread
From: Roland McGrath @ 2008-05-07 23:23 UTC (permalink / raw)
To: linux-ia64
On other machines, the assembly code does: disable interrupts; check TIF ||
return to user; (else) TIF_has_work: enable interrupts; call out to C.
For ia64, it's your business whether the assembly code reenables interrupts
or do_notify_resume_user does it from C. But it certainly is expected to
have been done before you call into the signals code.
Thanks,
Roland
^ permalink raw reply [flat|nested] 23+ messages in thread