* [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path
2008-08-23 18:07 2.6.27-rc4-git1: Reported regressions from 2.6.26 Rafael J. Wysocki
@ 2008-08-23 18:10 ` Rafael J. Wysocki
0 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-08-23 18:10 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Jeff Garzik, Tobias Diedrich, Yinghai Lu
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11358
Subject : net: forcedeth call restore mac addr in nv_shutdown path
Submitter : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-17 3:30 (7 days old)
References : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path
2008-08-30 19:46 2.6.27-rc5-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
@ 2008-08-30 19:50 ` Rafael J. Wysocki
2008-08-31 8:41 ` Tobias Diedrich
0 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-08-30 19:50 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Jeff Garzik, Tobias Diedrich, Yinghai Lu
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11358
Subject : net: forcedeth call restore mac addr in nv_shutdown path
Submitter : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-17 3:30 (14 days old)
References : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path
2008-08-30 19:50 ` [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path Rafael J. Wysocki
@ 2008-08-31 8:41 ` Tobias Diedrich
[not found] ` <20080831084135.GA2698-LEnv4NkkRI/kz0gr9c1H3IV7twrRs5iQ@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Tobias Diedrich @ 2008-08-31 8:41 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Jeff Garzik,
Yinghai Lu
Rafael J. Wysocki wrote:
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11358
> Subject : net: forcedeth call restore mac addr in nv_shutdown path
> Submitter : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date : 2008-08-17 3:30 (14 days old)
> References : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
> Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Patch : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
I got around to try kexec and found that on 2.6.27-rc5, without
Yinghai Lu's patch, when I kexec while forecdeth is loaded I get the
following when the new kernel tries to load the module (on my Asus
M2N-SLI Deluxe):
|Aug 31 10:10:42 melchior kernel: [ 10.578053] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
|Aug 31 10:10:42 melchior kernel: [ 10.578256] forcedeth 0000:00:08.0: BAR 0: error updating (0xfe02a000 != 0x000000)
|Aug 31 10:10:42 melchior kernel: [ 10.580901] forcedeth 0000:00:08.0: enabling device (0000 -> 0003)
|Aug 31 10:10:42 melchior kernel: [ 10.581405] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
|Aug 31 10:10:42 melchior kernel: [ 10.581509] forcedeth 0000:00:08.0: PCI INT A -> Link[APCH] -> GSI 22 (level, low) -> IRQ 22
|Aug 31 10:10:42 melchior kernel: [ 10.581699] forcedeth 0000:00:08.0: setting latency timer to 64
|Aug 31 10:10:42 melchior kernel: [ 10.581748] forcedeth 0000:00:08.0: Invalid Mac address detected: ff:ff:ff:ff:ff:ff
|Aug 31 10:10:42 melchior kernel: [ 10.581936] forcedeth 0000:00:08.0: Please complain to your hardware vendor. Switching to a random MAC.
|Aug 31 10:10:42 melchior kernel: [ 15.981960] forcedeth 0000:00:08.0: open: Could not find a valid PHY.
|Aug 31 10:10:42 melchior kernel: [ 15.982131] forcedeth 0000:00:08.0: PCI INT A disabled
|Aug 31 10:10:42 melchior kernel: [ 15.982283] forcedeth: probe of 0000:00:08.0 failed with error -12
|Aug 31 10:10:42 melchior kernel: [ 16.017545] forcedeth 0000:00:09.0: BAR 0: error updating (0xfe027000 != 0x000000)
|Aug 31 10:10:42 melchior kernel: [ 16.017766] forcedeth 0000:00:09.0: enabling device (0000 -> 0003)
|Aug 31 10:10:42 melchior kernel: [ 16.018720] ACPI: PCI Interrupt Link [AMC1] enabled at IRQ 21
|Aug 31 10:10:42 melchior kernel: [ 16.018839] forcedeth 0000:00:09.0: PCI INT A -> Link[AMC1] -> GSI 21 (level, low) -> IRQ 21
|Aug 31 10:10:42 melchior kernel: [ 16.019050] forcedeth 0000:00:09.0: setting latency timer to 64
|Aug 31 10:10:42 melchior kernel: [ 16.019129] forcedeth 0000:00:09.0: Invalid Mac address detected: ff:ff:ff:ff:ff:ff
|Aug 31 10:10:42 melchior kernel: [ 16.019339] forcedeth 0000:00:09.0: Please complain to your hardware vendor. Switching to a random MAC.
|Aug 31 10:10:42 melchior kernel: [ 21.399400] forcedeth 0000:00:09.0: open: Could not find a valid PHY.
|Aug 31 10:10:42 melchior kernel: [ 21.399572] forcedeth 0000:00:09.0: PCI INT A disabled
|Aug 31 10:10:42 melchior kernel: [ 21.399723] forcedeth: probe of 0000:00:09.0 failed with error -12
If I rmmod forcedeth before kexec, it loads fine later.
This is with MSI enabled:
| CPU0
| 0: 99 IO-APIC-edge timer
| 1: 2 IO-APIC-edge i8042
| 7: 1 IO-APIC-edge
| 8: 1 IO-APIC-edge rtc
| 9: 0 IO-APIC-fasteoi acpi
| 12: 3 IO-APIC-edge i8042
| 14: 53 IO-APIC-edge pata_amd
| 15: 0 IO-APIC-edge pata_amd
| 16: 76975 IO-APIC-fasteoi ahci, radeon@pci:0000:02:00.0
| 18: 0 IO-APIC-fasteoi EMU10K1
| 20: 6 IO-APIC-fasteoi ehci_hcd:usb1
| 21: 54 IO-APIC-fasteoi sata_nv
| 22: 0 IO-APIC-fasteoi sata_nv
| 23: 11230 IO-APIC-fasteoi sata_nv, ohci_hcd:usb2
|284: 81038 PCI-MSI-edge eth1
|285: 74728 PCI-MSI-edge eth0
|NMI: 0 Non-maskable interrupts
|LOC: 29209 Local timer interrupts
|TRM: 0 Thermal event interrupts
|THR: 0 Threshold APIC interrupts
|SPU: 0 Spurious interrupts
|ERR: 1
Maybe also calling nv_restore_phy() and/or pci_release_regions() in
the shutdown hook would help.
TODO:
Try with the patch, maybe try nv_restore_phy, test if WOL is
affected by the patch.
HTH,
--
Tobias PGP: http://9ac7e0bc.uguu.de
このメールは十割再利用されたビットで作られています。
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path
[not found] ` <20080831084135.GA2698-LEnv4NkkRI/kz0gr9c1H3IV7twrRs5iQ@public.gmane.org>
@ 2008-08-31 13:09 ` Tobias Diedrich
[not found] ` <20080831130904.GA4070-LEnv4NkkRI/kz0gr9c1H3IV7twrRs5iQ@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Tobias Diedrich @ 2008-08-31 13:09 UTC (permalink / raw)
To: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List,
Jeff Garzik, Ying
Tobias Diedrich wrote:
> I got around to try kexec and found that on 2.6.27-rc5, without
> Yinghai Lu's patch, when I kexec while forecdeth is loaded I get the
> following when the new kernel tries to load the module (on my Asus
> M2N-SLI Deluxe):
>
> |Aug 31 10:10:42 melchior kernel: [ 10.578053] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
> |Aug 31 10:10:42 melchior kernel: [ 10.578256] forcedeth 0000:00:08.0: BAR 0: error updating (0xfe02a000 != 0x000000)
> |Aug 31 10:10:42 melchior kernel: [ 10.580901] forcedeth 0000:00:08.0: enabling device (0000 -> 0003)
> |Aug 31 10:10:42 melchior kernel: [ 10.581405] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
> |Aug 31 10:10:42 melchior kernel: [ 10.581509] forcedeth 0000:00:08.0: PCI INT A -> Link[APCH] -> GSI 22 (level, low) -> IRQ 22
> |Aug 31 10:10:42 melchior kernel: [ 10.581699] forcedeth 0000:00:08.0: setting latency timer to 64
> |Aug 31 10:10:42 melchior kernel: [ 10.581748] forcedeth 0000:00:08.0: Invalid Mac address detected: ff:ff:ff:ff:ff:ff
> |Aug 31 10:10:42 melchior kernel: [ 10.581936] forcedeth 0000:00:08.0: Please complain to your hardware vendor. Switching to a random MAC.
> |Aug 31 10:10:42 melchior kernel: [ 15.981960] forcedeth 0000:00:08.0: open: Could not find a valid PHY.
> |Aug 31 10:10:42 melchior kernel: [ 15.982131] forcedeth 0000:00:08.0: PCI INT A disabled
> |Aug 31 10:10:42 melchior kernel: [ 15.982283] forcedeth: probe of 0000:00:08.0 failed with error -12
> |Aug 31 10:10:42 melchior kernel: [ 16.017545] forcedeth 0000:00:09.0: BAR 0: error updating (0xfe027000 != 0x000000)
> |Aug 31 10:10:42 melchior kernel: [ 16.017766] forcedeth 0000:00:09.0: enabling device (0000 -> 0003)
> |Aug 31 10:10:42 melchior kernel: [ 16.018720] ACPI: PCI Interrupt Link [AMC1] enabled at IRQ 21
> |Aug 31 10:10:42 melchior kernel: [ 16.018839] forcedeth 0000:00:09.0: PCI INT A -> Link[AMC1] -> GSI 21 (level, low) -> IRQ 21
> |Aug 31 10:10:42 melchior kernel: [ 16.019050] forcedeth 0000:00:09.0: setting latency timer to 64
> |Aug 31 10:10:42 melchior kernel: [ 16.019129] forcedeth 0000:00:09.0: Invalid Mac address detected: ff:ff:ff:ff:ff:ff
> |Aug 31 10:10:42 melchior kernel: [ 16.019339] forcedeth 0000:00:09.0: Please complain to your hardware vendor. Switching to a random MAC.
> |Aug 31 10:10:42 melchior kernel: [ 21.399400] forcedeth 0000:00:09.0: open: Could not find a valid PHY.
> |Aug 31 10:10:42 melchior kernel: [ 21.399572] forcedeth 0000:00:09.0: PCI INT A disabled
> |Aug 31 10:10:42 melchior kernel: [ 21.399723] forcedeth: probe of 0000:00:09.0 failed with error -12
>
> If I rmmod forcedeth before kexec, it loads fine later.
[...]
> Maybe also calling nv_restore_phy() and/or pci_release_regions() in
> the shutdown hook would help.
>
> TODO:
> Try with the patch, maybe try nv_restore_phy, test if WOL is
> affected by the patch.
I just tried with the patch and both options above in the shutdown
path and the kexec'd kernel still had the same problems as above.
Interestingly the message comes from drivers/pci/setup-res.c, where
it updates the BAR register and reads it back to make sure it was
updated and somehow reads back zeroes?
I wonder what's going on there, that should never happen AFAIK...
Maybe the pci device was not properly reenabled, but OTOH when I
just rmmod before kexec it seems to work and nv_remove also calls
pci_disable_device()...
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.27-rc5
# Sat Aug 30 09:46:25 2008
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
# CONFIG_GENERIC_LOCKBREAK is not set
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_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
# CONFIG_KTIME_SCALAR is not set
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 is not set
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
# CONFIG_CGROUPS is not set
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
# CONFIG_PCSPKR_PLATFORM is not set
# CONFIG_COMPAT_BRK is not set
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_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
# CONFIG_HAVE_ARCH_TRACEHOOK is not set
# CONFIG_HAVE_DMA_ATTRS is not set
# CONFIG_USE_GENERIC_SMP_HELPERS is not set
# CONFIG_HAVE_CLK is not set
CONFIG_PROC_PAGE_MONITOR=y
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
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_BLK_DEV_IO_TRACE is not set
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
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
CONFIG_CLASSIC_RCU=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_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_MEMTEST 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 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
CONFIG_MK8=y
# 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_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_AMD_IOMMU=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_INTEL is not set
CONFIG_X86_MCE_AMD=y
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
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_HAVE_MEMORY_PRESENT=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
#
# Memory hotplug is currently incompatible with Software Suspend
#
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MMU_NOTIFIER=y
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
# CONFIG_EFI is not set
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_300=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=300
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x200000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x200000
# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
# Power management options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_VERBOSE is not set
CONFIG_CAN_PM_TRACE=y
# CONFIG_PM_TRACE_RTC is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_WMI is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_CUSTOM_DSDT_FILE=""
# 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=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
#
# CPUFreq processor drivers
#
# CONFIG_X86_ACPI_CPUFREQ is not set
CONFIG_X86_POWERNOW_K8=y
CONFIG_X86_POWERNOW_K8_ACPI=y
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_P4_CLOCKMOD is not set
#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_MMCONFIG is not set
CONFIG_PCI_DOMAINS=y
CONFIG_DMAR=y
CONFIG_DMAR_GFX_WA=y
CONFIG_DMAR_FLOPPY_WA=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=y
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=y
# CONFIG_NET_IPGRE is not set
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=y
CONFIG_TCP_CONG_HTCP=y
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
CONFIG_TCP_CONG_VEGAS=y
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
CONFIG_TCP_CONG_YEAH=y
# CONFIG_TCP_CONG_ILLINOIS is not set
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IP_VS is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=y
CONFIG_INET6_ESP=y
CONFIG_INET6_IPCOMP=y
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=y
CONFIG_INET6_TUNNEL=y
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
CONFIG_INET6_XFRM_MODE_TUNNEL=y
CONFIG_INET6_XFRM_MODE_BEET=y
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=y
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
CONFIG_NF_CONNTRACK=y
# CONFIG_NF_CT_ACCT is not set
CONFIG_NF_CONNTRACK_MARK=y
# CONFIG_NF_CONNTRACK_EVENTS is not set
# CONFIG_NF_CT_PROTO_DCCP is not set
# CONFIG_NF_CT_PROTO_SCTP is not set
# CONFIG_NF_CT_PROTO_UDPLITE is not set
# CONFIG_NF_CONNTRACK_AMANDA is not set
# CONFIG_NF_CONNTRACK_FTP is not set
# CONFIG_NF_CONNTRACK_H323 is not set
# CONFIG_NF_CONNTRACK_IRC is not set
# CONFIG_NF_CONNTRACK_NETBIOS_NS is not set
# CONFIG_NF_CONNTRACK_PPTP is not set
# CONFIG_NF_CONNTRACK_SANE is not set
# CONFIG_NF_CONNTRACK_SIP is not set
# CONFIG_NF_CONNTRACK_TFTP is not set
# CONFIG_NF_CT_NETLINK is not set
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
# CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
CONFIG_NETFILTER_XT_TARGET_MARK=y
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
# CONFIG_NETFILTER_XT_TARGET_NOTRACK is not set
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
# CONFIG_NETFILTER_XT_TARGET_TRACE is not set
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
# CONFIG_NETFILTER_XT_MATCH_COMMENT is not set
# CONFIG_NETFILTER_XT_MATCH_CONNBYTES is not set
# CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set
CONFIG_NETFILTER_XT_MATCH_CONNMARK=y
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_DCCP=y
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
# CONFIG_NETFILTER_XT_MATCH_ESP is not set
# CONFIG_NETFILTER_XT_MATCH_HELPER is not set
# CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set
CONFIG_NETFILTER_XT_MATCH_LENGTH=y
CONFIG_NETFILTER_XT_MATCH_LIMIT=y
CONFIG_NETFILTER_XT_MATCH_MAC=y
CONFIG_NETFILTER_XT_MATCH_MARK=y
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
# CONFIG_NETFILTER_XT_MATCH_POLICY is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=y
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
CONFIG_NETFILTER_XT_MATCH_REALM=y
CONFIG_NETFILTER_XT_MATCH_SCTP=y
# CONFIG_NETFILTER_XT_MATCH_STATE is not set
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
CONFIG_NETFILTER_XT_MATCH_U32=y
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
#
# IP: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_RECENT=y
CONFIG_IP_NF_MATCH_ECN=y
# CONFIG_IP_NF_MATCH_AH is not set
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_NF_NAT=y
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_NF_NAT_SNMP_BASIC is not set
# CONFIG_NF_NAT_FTP is not set
# CONFIG_NF_NAT_IRC is not set
# CONFIG_NF_NAT_TFTP is not set
# CONFIG_NF_NAT_AMANDA is not set
# CONFIG_NF_NAT_PPTP is not set
# CONFIG_NF_NAT_H323 is not set
# CONFIG_NF_NAT_SIP is not set
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_TTL=y
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
CONFIG_IP_NF_RAW=y
# CONFIG_IP_NF_ARPTABLES is not set
#
# IPv6: Netfilter Configuration
#
# CONFIG_NF_CONNTRACK_IPV6 is not set
CONFIG_IP6_NF_QUEUE=y
# CONFIG_IP6_NF_IPTABLES is not set
#
# Bridge: Netfilter Configuration
#
# CONFIG_BRIDGE_NF_EBTABLES 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_STP=y
CONFIG_BRIDGE=y
CONFIG_VLAN_8021Q=y
# CONFIG_VLAN_8021Q_GVRP is not set
# CONFIG_DECNET is not set
CONFIG_LLC=y
# 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=y
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
# CONFIG_NET_SCH_HFSC is not set
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
# CONFIG_NET_SCH_NETEM is not set
CONFIG_NET_SCH_INGRESS=y
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
# CONFIG_NET_EMATCH is not set
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=y
CONFIG_NET_ACT_GACT=y
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=y
CONFIG_NET_ACT_IPT=y
# CONFIG_NET_ACT_NAT is not set
CONFIG_NET_ACT_PEDIT=y
# CONFIG_NET_ACT_SIMP is not set
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
CONFIG_BT=y
CONFIG_BT_L2CAP=y
CONFIG_BT_SCO=y
CONFIG_BT_RFCOMM=y
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=y
# CONFIG_BT_BNEP_MC_FILTER is not set
# CONFIG_BT_BNEP_PROTO_FILTER is not set
CONFIG_BT_HIDP=y
#
# Bluetooth device drivers
#
CONFIG_BT_HCIBTUSB=y
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
# CONFIG_BT_HCIUART_LL is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
#
# 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 is not set
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_CONCAT is not set
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
# CONFIG_MTD_AR7_PARTS is not set
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_MTD_OOPS is not set
#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_TS5500 is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
CONFIG_MTD_BLOCK2MTD=y
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
# CONFIG_MTD_NAND is not set
# CONFIG_MTD_ONENAND is not set
#
# UBI - Unsorted block images
#
# CONFIG_MTD_UBI 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_DEV_FD is not set
# 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=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_COMPAL_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_EEEPC_LAPTOP is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO 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 is not set
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# 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_DPT_I2O 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_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH 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 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# 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_SCSI_DH is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
CONFIG_SATA_NV=y
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ACPI is not set
# CONFIG_PATA_ALI is not set
CONFIG_PATA_AMD=m
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_SCH is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=y
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
CONFIG_DM_ZERO=y
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
#
# Enable only one of the two stacks, unless you know what you are doing
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_IFB is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
# 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=y
# 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 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=m
# CONFIG_FORCEDETH_NAPI is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=y
# 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_TLAN 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 is not set
CONFIG_E1000E=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=y
CONFIG_R8169_VLAN=y
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E 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_SFC 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=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
# CONFIG_USB_NET_DM9601 is not set
# CONFIG_USB_NET_GL620A is not set
CONFIG_USB_NET_NET1080=m
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
# CONFIG_USB_NET_CDC_SUBSET is not set
CONFIG_USB_NET_ZAURUS=m
# 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 is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# 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 is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1600
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1200
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
# 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 is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_UINPUT is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 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=m
# CONFIG_GAMEPORT_FM801 is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
CONFIG_FIX_EARLYCON_MEM=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_HELPER_AUTO=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_NFORCE2=y
# CONFIG_I2C_NFORCE2_S4985 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_SIMTEC is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Graphics adapter I2C/DDC channel drivers
#
# CONFIG_I2C_VOODOO3 is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_STUB is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
# CONFIG_AT24 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_PCF8575 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
# CONFIG_SPI is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB 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=y
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7473 is not set
CONFIG_SENSORS_K8TEMP=m
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
CONFIG_SENSORS_IT87=y
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_THERMAL=y
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
#
# Multimedia devices
#
#
# Multimedia core support
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
CONFIG_VIDEO_ALLOW_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
# CONFIG_DVB_CORE is not set
CONFIG_VIDEO_MEDIA=m
#
# Multimedia drivers
#
# CONFIG_MEDIA_ATTACH is not set
CONFIG_MEDIA_TUNER=m
# CONFIG_MEDIA_TUNER_CUSTOMIZE is not set
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA9887=m
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L1=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_IVTV is not set
# CONFIG_VIDEO_CAFE_CCIC is not set
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
# CONFIG_USB_GSPCA is not set
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_W9968CF is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
# CONFIG_SOC_CAMERA is not set
# CONFIG_VIDEO_SH_MOBILE_CEU is not set
# CONFIG_RADIO_ADAPTERS is not set
# CONFIG_DAB is not set
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_CORGI is not set
# CONFIG_BACKLIGHT_PROGEAR is not set
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_SOUND=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
# CONFIG_SND_PCM_OSS_PLUGINS is not set
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_VERBOSE is not set
# CONFIG_SND_PCM_XRUN_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=m
# CONFIG_SND_HDA_HWDEP is not set
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
# CONFIG_SND_HDA_POWER_SAVE is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_HIFIER is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set
#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV 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=y
# 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_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
CONFIG_USB_MON=y
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=y
# 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_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=y
# 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=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
# CONFIG_USB_WDM 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_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_SIERRA 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
#
# USB port drivers
#
CONFIG_USB_SERIAL=m
# CONFIG_USB_EZUSB is not set
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP2101 is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_FUNSOFT is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MOTOROLA is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_DEBUG 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_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_ISIGHTFW is not set
# CONFIG_USB_GADGET 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_EDAC is not set
# CONFIG_RTC_CLASS is not set
CONFIG_DMADEVICES=y
#
# DMA Devices
#
# CONFIG_INTEL_IOATDMA is not set
# CONFIG_UIO is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_ISCSI_IBFT_FIND 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 is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=y
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
# CONFIG_XFS_DEBUG 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=y
CONFIG_FUSE_FS=y
CONFIG_GENERIC_ACL=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=932
CONFIG_FAT_DEFAULT_IOCHARSET="utf8"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_CONFIGFS_FS=y
#
# 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_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
# CONFIG_JFFS2_FS_XATTR is not set
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_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=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
# CONFIG_NFS_V4 is not set
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp850"
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
# 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=y
# 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=y
# 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=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=0
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS 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 is not set
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
CONFIG_HAVE_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_TRACING=y
# CONFIG_FTRACE is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
CONFIG_DIRECT_GBPAGES=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_IOMMU_DEBUG is not set
CONFIG_MMIOTRACE_HOOKS=y
CONFIG_MMIOTRACE=y
# CONFIG_MMIOTRACE_TEST is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not set
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
CONFIG_IO_DELAY_NONE=y
CONFIG_DEFAULT_IO_DELAY_TYPE=3
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_NULL=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y
# 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=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# 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=y
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_WP512=y
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_BLOWFISH=y
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 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
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_LZO is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
# CONFIG_KVM_INTEL is not set
CONFIG_KVM_AMD=y
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_BALLOON is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
--
Tobias PGP: http://9ac7e0bc.uguu.de
このメールは十割再利用されたビットで作られています。
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path
[not found] ` <20080831130904.GA4070-LEnv4NkkRI/kz0gr9c1H3IV7twrRs5iQ@public.gmane.org>
@ 2008-08-31 18:02 ` Yinghai Lu
0 siblings, 0 replies; 126+ messages in thread
From: Yinghai Lu @ 2008-08-31 18:02 UTC (permalink / raw)
To: Tobias Diedrich, Rafael J. Wysocki, Linux Kernel Mailing List,
Kernel Testers List
On Sun, Aug 31, 2008 at 6:09 AM, Tobias Diedrich
<ranma+kernel-YxUgxmcw2FPQD6PfKP4TzA@public.gmane.org> wrote:
> Tobias Diedrich wrote:
>> I got around to try kexec and found that on 2.6.27-rc5, without
>> Yinghai Lu's patch, when I kexec while forecdeth is loaded I get the
>> following when the new kernel tries to load the module (on my Asus
>> M2N-SLI Deluxe):
>>
>> |Aug 31 10:10:42 melchior kernel: [ 10.578053] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
>> |Aug 31 10:10:42 melchior kernel: [ 10.578256] forcedeth 0000:00:08.0: BAR 0: error updating (0xfe02a000 != 0x000000)
>> |Aug 31 10:10:42 melchior kernel: [ 10.580901] forcedeth 0000:00:08.0: enabling device (0000 -> 0003)
>> |Aug 31 10:10:42 melchior kernel: [ 10.581405] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
>> |Aug 31 10:10:42 melchior kernel: [ 10.581509] forcedeth 0000:00:08.0: PCI INT A -> Link[APCH] -> GSI 22 (level, low) -> IRQ 22
>> |Aug 31 10:10:42 melchior kernel: [ 10.581699] forcedeth 0000:00:08.0: setting latency timer to 64
>> |Aug 31 10:10:42 melchior kernel: [ 10.581748] forcedeth 0000:00:08.0: Invalid Mac address detected: ff:ff:ff:ff:ff:ff
>> |Aug 31 10:10:42 melchior kernel: [ 10.581936] forcedeth 0000:00:08.0: Please complain to your hardware vendor. Switching to a random MAC.
>> |Aug 31 10:10:42 melchior kernel: [ 15.981960] forcedeth 0000:00:08.0: open: Could not find a valid PHY.
>> |Aug 31 10:10:42 melchior kernel: [ 15.982131] forcedeth 0000:00:08.0: PCI INT A disabled
>> |Aug 31 10:10:42 melchior kernel: [ 15.982283] forcedeth: probe of 0000:00:08.0 failed with error -12
>> |Aug 31 10:10:42 melchior kernel: [ 16.017545] forcedeth 0000:00:09.0: BAR 0: error updating (0xfe027000 != 0x000000)
>> |Aug 31 10:10:42 melchior kernel: [ 16.017766] forcedeth 0000:00:09.0: enabling device (0000 -> 0003)
>> |Aug 31 10:10:42 melchior kernel: [ 16.018720] ACPI: PCI Interrupt Link [AMC1] enabled at IRQ 21
>> |Aug 31 10:10:42 melchior kernel: [ 16.018839] forcedeth 0000:00:09.0: PCI INT A -> Link[AMC1] -> GSI 21 (level, low) -> IRQ 21
>> |Aug 31 10:10:42 melchior kernel: [ 16.019050] forcedeth 0000:00:09.0: setting latency timer to 64
>> |Aug 31 10:10:42 melchior kernel: [ 16.019129] forcedeth 0000:00:09.0: Invalid Mac address detected: ff:ff:ff:ff:ff:ff
>> |Aug 31 10:10:42 melchior kernel: [ 16.019339] forcedeth 0000:00:09.0: Please complain to your hardware vendor. Switching to a random MAC.
>> |Aug 31 10:10:42 melchior kernel: [ 21.399400] forcedeth 0000:00:09.0: open: Could not find a valid PHY.
>> |Aug 31 10:10:42 melchior kernel: [ 21.399572] forcedeth 0000:00:09.0: PCI INT A disabled
>> |Aug 31 10:10:42 melchior kernel: [ 21.399723] forcedeth: probe of 0000:00:09.0 failed with error -12
>>
>> If I rmmod forcedeth before kexec, it loads fine later.
> [...]
>> Maybe also calling nv_restore_phy() and/or pci_release_regions() in
>> the shutdown hook would help.
>>
>> TODO:
>> Try with the patch, maybe try nv_restore_phy, test if WOL is
>> affected by the patch.
>
> I just tried with the patch and both options above in the shutdown
> path and the kexec'd kernel still had the same problems as above.
>
> Interestingly the message comes from drivers/pci/setup-res.c, where
> it updates the BAR register and reads it back to make sure it was
> updated and somehow reads back zeroes?
>
> I wonder what's going on there, that should never happen AFAIK...
> Maybe the pci device was not properly reenabled, but OTOH when I
> just rmmod before kexec it seems to work and nv_remove also calls
> pci_disable_device()...
in addition to this patch, you may need another patch from Rafael...,
that one fix the MSI...etc,
YH
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path
2008-09-06 21:24 2.6.27-rc5-git8: Reported regressions from 2.6.26 Rafael J. Wysocki
@ 2008-09-06 21:30 ` Rafael J. Wysocki
0 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-06 21:30 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Jeff Garzik, Tobias Diedrich, Yinghai Lu
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11358
Subject : net: forcedeth call restore mac addr in nv_shutdown path
Submitter : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-17 3:30 (21 days old)
References : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* 2.6.27-rc6-git2: Reported regressions from 2.6.26
@ 2008-09-12 18:59 Rafael J. Wysocki
2008-09-12 18:59 ` [Bug #11207] VolanoMark regression with 2.6.27-rc1 Rafael J. Wysocki
` (48 more replies)
0 siblings, 49 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 18:59 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Adrian Bunk, Andrew Morton, Linus Torvalds, Natalie Protasevich,
Kernel Testers List
This message contains a list of some regressions from 2.6.26, for which there
are no fixes in the mainline I know of. If any of them have been fixed already,
please let me know.
If you know of any other unresolved regressions from 2.6.26, please let me know
either and I'll add them to the list. Also, please let me know if any of the
entries below are invalid.
Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.
Listed regressions statistics:
Date Total Pending Unresolved
----------------------------------------
2008-09-12 163 51 38
2008-09-07 150 43 33
2008-08-30 135 48 36
2008-08-23 122 48 40
2008-08-16 103 47 37
2008-08-10 80 52 31
2008-08-02 47 31 20
Unresolved regressions
----------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11559
Subject : 2.6.27-rc6: nohz + s2ram = need to press keys to get progress
Submitter : Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Date : 2008-09-12 8:31 (1 days old)
References : http://marc.info/?l=linux-kernel&m=122121384705262&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11557
Subject : Controlling backlight on thinkpad x60
Submitter : Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Date : 2008-09-08 15:10 (5 days old)
References : http://marc.info/?l=linux-kernel&m=122088987319698&w=4
Handled-By : Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11554
Subject : Partition check considered as error is breaking mounting in 2.6.27
Submitter : Herton Ronaldo Krzesinski <herton-4qZELD6Fgxg39yzSjRtAkw@public.gmane.org>
Date : 2008-09-12 16:56 (1 days old)
References : http://marc.info/?l=linux-kernel&m=122123862519434&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11553
Subject : Strange looking line from "ps aux"
Submitter : Rogério Brito <rbrito-qczF+2RCDl1fyO9Q7EP/yw@public.gmane.org>
Date : 2008-09-11 17:43 (2 days old)
References : http://marc.info/?l=linux-kernel&m=122115506018275&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11552
Subject : Disabling IRQ #23
Submitter : Justin Mattock <justinmattock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-09 19:08 (4 days old)
References : http://marc.info/?l=linux-kernel&m=122098735230906&w=4
http://marc.info/?l=linux-kernel&m=122107367715361&w=4
Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11551
Subject : Semi-repeatable hard lockup on 2.6.27-rc6
Submitter : Steven Noonan <steven-Cunn4gMjHvbm+q05EWxUEA@public.gmane.org>
Date : 2008-09-10 18:07 (3 days old)
References : http://marc.info/?l=linux-kernel&m=122107007407994&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11548
Subject : kernel BUG at drivers/pci/intel-iommu.c:1373!
Submitter : Chris Mason <chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-09-08 14:26 (5 days old)
References : http://marc.info/?l=linux-kernel&m=122088566310440&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11516
Subject : severe performance degradation on x86_64 going from 2.6.26-rc9 -> 2.6.27-rc5
Submitter : Jason Vas Dias <jason.vas.dias-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-07 13:59 (6 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11512
Subject : sort-of regression due to "kconfig: speed up all*config + randconfig"
Submitter : Alexey Dobriyan <adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-05 22:50 (8 days old)
References : http://marc.info/?l=linux-kernel&m=122065498013858&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11506
Subject : oops during unmount - ext3? (2.6.27-rc5)
Submitter : Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-04 19:14 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122055573123449&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11505
Subject : oltp ~10% regression with 2.6.27-rc5 on stoakley machine
Submitter : Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date : 2008-09-04 7:06 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122051202202373&w=4
http://marc.info/?t=122089704700005&r=1&w=4
Handled-By : Peter Zijlstra <a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>
Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11504
Subject : reiserfs BUG in 2.6.27-rc5
Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-09-03 16:35 (10 days old)
References : http://marc.info/?l=linux-kernel&m=122045982120138&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11501
Subject : Failed to open destination file: Permission deniedihex2fw
Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Date : 2008-09-04 18:34 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122055342419068&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
Subject : /proc/net bug related to selinux
Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Date : 2008-09-04 17:45 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11485
Subject : 2.6.27-rc xen pvops regression?
Submitter : Bernhard Schmidt <berni-wpePDvIxQxvMZTq/7ZfH4Q@public.gmane.org>
Date : 2008-08-31 17:18 (13 days old)
References : http://marc.info/?l=linux-kernel&m=122020367015025&w=4
Handled-By : Alex Nixon <alex.nixon-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Jeremy Fitzhardinge <jeremy-TSDbQ3PG+2Y@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11476
Subject : failure to associate after resume from suspend to ram
Submitter : Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-01 13:33 (12 days old)
References : http://marc.info/?l=linux-kernel&m=122028529415108&w=4
Handled-By : Zhu Yi <yi.zhu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Jouni Malinen <j@w1.fi>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11471
Subject : GPE storm detected, kernel freezes
Submitter : George Gibbs <Vash63-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-31 22:00 (13 days old)
Handled-By : Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11465
Subject : Linux-2.6.27-rc5, drm errors in log
Submitter : Gene Heskett <gene.heskett-H+0wwilmMs3R7s880joybQ@public.gmane.org>
Date : 2008-08-30 18:52 (14 days old)
References : http://marc.info/?l=linux-kernel&m=122012238925775&w=4
Handled-By : Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11463
Subject : sshd hangs on close
Submitter : Matthias Urlichs <matthias-+qxcz+fHsVSELgA04lAiVw@public.gmane.org>
Date : 2008-08-30 9:18 (14 days old)
References : http://marc.info/?l=linux-kernel&m=122008800512864&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11459
Subject : kernel crash after wifi connection established
Submitter : Alexey Kuznetsov <ak-b7SOpcJQXxU@public.gmane.org>
Date : 2008-08-30 03:08 (14 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11407
Subject : suspend: unable to handle kernel paging request
Submitter : Vegard Nossum <vegard.nossum-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-21 17:28 (23 days old)
References : http://marc.info/?l=linux-kernel&m=121933974928881&w=4
Handled-By : Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
Pekka Enberg <penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.org>
Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11404
Subject : BUG: in 2.6.23-rc3-git7 in do_cciss_intr
Submitter : rdunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-21 5:52 (23 days old)
References : http://marc.info/?l=linux-kernel&m=121929819616273&w=4
http://marc.info/?l=linux-kernel&m=121932889105368&w=4
Handled-By : Miller, Mike (OS Dev) <Mike.Miller-VXdhtT5mjnY@public.gmane.org>
James Bottomley <James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11398
Subject : hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-08-21 17:17 (23 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11380
Subject : lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
Submitter : Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Date : 2008-08-20 6:44 (24 days old)
References : http://marc.info/?l=linux-kernel&m=121921480931970&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11357
Subject : Can not boot up with zd1211rw USB-Wlan Stick
Submitter : uwe <kender-KuiJ5kEpwI6ELgA04lAiVw@public.gmane.org>
Date : 2008-08-16 14:17 (28 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11343
Subject : SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i
Submitter : Manny Maxwell <mannymax-7UBucS1kxs3k1uMJSBkQmQ@public.gmane.org>
Date : 2008-08-14 4:16 (30 days old)
References : http://marc.info/?l=linux-kernel&m=121868782917600&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11340
Subject : LTP overnight run resulted in unusable box
Submitter : Alexey Dobriyan <adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-13 9:24 (31 days old)
References : http://marc.info/?l=linux-kernel&m=121861951902949&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11335
Subject : 2.6.27-rc2-git5 BUG: unable to handle kernel paging request
Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-12 4:18 (32 days old)
References : http://marc.info/?l=linux-kernel&m=121851477201960&w=4
http://lkml.org/lkml/2008/8/16/274
Handled-By : Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11308
Subject : tbench regression on each kernel release from 2.6.22 -> 2.6.28
Submitter : Christoph Lameter <cl-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Date : 2008-08-11 18:36 (33 days old)
References : http://marc.info/?l=linux-kernel&m=121847986119495&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11272
Subject : BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835
Submitter : Jaswinder Singh <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-05 15:12 (39 days old)
References : http://marc.info/?l=linux-kernel&m=121794900319776&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11271
Subject : BUG: fealnx in 2.6.27-rc1
Submitter : Jaswinder Singh <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-05 14:58 (39 days old)
References : http://marc.info/?l=linux-netdev&m=121794762016830&w=4
http://lkml.org/lkml/2008/8/10/98
Handled-By : Francois Romieu <romieu-W8zweXLXuWQS+FvcfC7Uqw@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11264
Subject : Invalid op opcode in kernel/workqueue
Submitter : Jean-Luc Coulon <jean.luc.coulon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-07 04:18 (37 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11230
Subject : Kconfig no longer outputs a .config with freshly updated defconfigs
Submitter : Josh Boyer <jwboyer-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date : 2008-08-02 16:03 (42 days old)
References : http://marc.info/?l=linux-kernel&m=121769306319391&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11224
Subject : Only three cores found on quad-core machine.
Submitter : Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-01 18:15 (43 days old)
References : http://marc.info/?l=linux-kernel&m=121761475224719&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11220
Subject : Screen stays black after resume
Submitter : Nico Schottelius <nico-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Date : 2008-07-31 21:05 (44 days old)
References : http://marc.info/?l=linux-kernel&m=121753882422899&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11215
Subject : INFO: possible recursive locking detected ps2_command
Submitter : Zdenek Kabelac <zdenek.kabelac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-07-31 9:41 (44 days old)
References : http://marc.info/?l=linux-kernel&m=121749737011637&w=4
Handled-By : Peter Zijlstra <a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11210
Subject : libata badness
Submitter : Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Date : 2008-07-31 18:53 (44 days old)
References : http://marc.info/?l=linux-ide&m=121753059307310&w=4
Handled-By : Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11207
Subject : VolanoMark regression with 2.6.27-rc1
Submitter : Zhang, Yanmin <yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Date : 2008-07-31 3:20 (44 days old)
References : http://marc.info/?l=linux-kernel&m=121747464114335&w=4
Handled-By : Zhang, Yanmin <yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Peter Zijlstra <a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>
Dhaval Giani <dhaval-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Miao Xie <miaox-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Regressions with patches
------------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11556
Subject : e100: PCI wake-up handling rework causes "Error clearing wake event"
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-09-09 6:12 (4 days old)
References : http://marc.info/?l=linux-netdev&m=122094080712131&w=4
Handled-By : Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122096638020191&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11555
Subject : rmmod ide-cd_mod: tried to init an initialized object, something is seriously wrong.
Submitter : Mariusz Kozlowski <m.kozlowski-NWF1p15JEu3VItvQsEIGlw@public.gmane.org>
Date : 2008-07-16 2:22 (59 days old)
References : http://marc.info/?l=linux-ide&m=122061839713526&w=4
Handled-By : Jens Axboe <jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122095622602315&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11550
Subject : pnp: Huge number of "io resource overlap" messages
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-09-09 10:50 (4 days old)
References : http://marc.info/?l=linux-kernel&m=122095745403793&w=4
Handled-By : Rene Herman <rene.herman-cENuUygGYd//D1n+0JDH9g@public.gmane.org>
Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122098498125536&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11549
Subject : 2.6.27-rc5 acpi: EC Storm error message on bootup
Submitter : <jmerkey-6KXTs3wnGaZTqo3+vT/QGPegYHeGw8Jk@public.gmane.org>
Date : 2008-09-02 21:27 (11 days old)
References : http://marc.info/?l=linux-kernel&m=122039255517586&w=4
Handled-By : Alexey Starikovskiy <astarikovskiy-l3A5Bk7waGM@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122098180019264&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11547
Subject : build issue #565 for v2.6.27-rc5 : undefined reference to `ei_interrupt' in hp-plus.c
Submitter : Toralf Förster <toralf.foerster-Mmb7MZpHnFY@public.gmane.org>
Date : 2008-09-07 13:19 (6 days old)
References : http://marc.info/?l=linux-kernel&m=122079361508022&w=4
Handled-By : Randy.Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Patch : http://marc.info/?l=linux-next&m=122038632306156&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11507
Subject : usb: sometimes dead keyboard after boot
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-08-26 21:03 (18 days old)
References : http://marc.info/?l=linux-kernel&m=121977815018224&w=2
Handled-By : Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>
Patch : http://www.spinics.net/lists/linux-usb/msg09735.html
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11442
Subject : btusb hibernation/suspend breakage in current -git
Submitter : Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
Date : 2008-08-25 11:37 (19 days old)
References : http://marc.info/?l=linux-bluetooth&m=121966402012074&w=4
Handled-By : Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
Patch : http://marc.info/?l=linux-bluetooth&m=121967226027323&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11439
Subject : [2.6.27-rc4-git4] compilation warnings
Submitter : Rufus & Azrael <rufus-azrael-Bf/eaXMDFuuXqB7oj33eUg@public.gmane.org>
Date : 2008-08-26 9:37 (18 days old)
References : http://marc.info/?l=linux-kernel&m=121974353815440&w=4
Handled-By : Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=121976424221858&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11382
Subject : e1000e: 2.6.27-rc1 corrupts EEPROM/NVM
Submitter : David Vrabel <david.vrabel-kQvG35nSl+M@public.gmane.org>
Date : 2008-08-08 10:47 (36 days old)
References : http://marc.info/?l=linux-kernel&m=121819267211679&w=4
Handled-By : Christopher Li <chrisl-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Patch : http://marc.info/?l=linux-mm-commits&m=122038324200305&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11358
Subject : net: forcedeth call restore mac addr in nv_shutdown path
Submitter : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-17 3:30 (27 days old)
References : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11336
Subject : 2.6.27-rc2:stall while mounting root fs
Submitter : Torsten Kaiser <just.for.lkml-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Date : 2008-08-12 12:37 (32 days old)
References : http://marc.info/?l=linux-kernel&m=121854484015909&w=4
Handled-By : Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=17622
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11276
Subject : build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-06 17:18 (38 days old)
References : http://marc.info/?l=linux-kernel&m=121804329014332&w=4
http://lkml.org/lkml/2008/7/22/353
Handled-By : Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Patch : http://lkml.org/lkml/2008/7/22/364
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11237
Subject : corrupt PMD after resume
Submitter : Alan Jenkins <alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
Date : 2008-08-02 9:51 (42 days old)
References : http://marc.info/?l=linux-kernel&m=121767073424952&w=4
Handled-By : Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
Jeremy Fitzhardinge <jeremy-TSDbQ3PG+2Y@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122001615314700&w=2
For details, please visit the bug entries and follow the links given in
references.
As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.26,
unresolved as well as resolved, at:
http://bugzilla.kernel.org/show_bug.cgi?id=11167
Please let me know if there are any Bugzilla entries that should be added to
the list in there.
Thanks,
Rafael
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11207] VolanoMark regression with 2.6.27-rc1
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
@ 2008-09-12 18:59 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11220] Screen stays black after resume Rafael J. Wysocki
` (47 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 18:59 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Dhaval Giani, Miao Xie, Peter Zijlstra,
Zhang, Yanmin
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11207
Subject : VolanoMark regression with 2.6.27-rc1
Submitter : Zhang, Yanmin <yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Date : 2008-07-31 3:20 (44 days old)
References : http://marc.info/?l=linux-kernel&m=121747464114335&w=4
Handled-By : Zhang, Yanmin <yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Peter Zijlstra <a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>
Dhaval Giani <dhaval-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Miao Xie <miaox-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11210] libata badness
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
2008-09-12 18:59 ` [Bug #11207] VolanoMark regression with 2.6.27-rc1 Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11220] Screen stays black after resume Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11215] INFO: possible recursive locking detected ps2_command Rafael J. Wysocki
` (45 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Kumar Gala
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11210
Subject : libata badness
Submitter : Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Date : 2008-07-31 18:53 (44 days old)
References : http://marc.info/?l=linux-ide&m=121753059307310&w=4
Handled-By : Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11215] INFO: possible recursive locking detected ps2_command
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (2 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11210] libata badness Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11224] Only three cores found on quad-core machine Rafael J. Wysocki
` (44 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Peter Zijlstra, Zdenek Kabelac
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11215
Subject : INFO: possible recursive locking detected ps2_command
Submitter : Zdenek Kabelac <zdenek.kabelac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-07-31 9:41 (44 days old)
References : http://marc.info/?l=linux-kernel&m=121749737011637&w=4
Handled-By : Peter Zijlstra <a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11220] Screen stays black after resume
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
2008-09-12 18:59 ` [Bug #11207] VolanoMark regression with 2.6.27-rc1 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11210] libata badness Rafael J. Wysocki
` (46 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Nico Schottelius
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11220
Subject : Screen stays black after resume
Submitter : Nico Schottelius <nico-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Date : 2008-07-31 21:05 (44 days old)
References : http://marc.info/?l=linux-kernel&m=121753882422899&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11224] Only three cores found on quad-core machine.
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (3 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11215] INFO: possible recursive locking detected ps2_command Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11230] Kconfig no longer outputs a .config with freshly updated defconfigs Rafael J. Wysocki
` (43 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Dave Jones
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11224
Subject : Only three cores found on quad-core machine.
Submitter : Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-01 18:15 (43 days old)
References : http://marc.info/?l=linux-kernel&m=121761475224719&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11237] corrupt PMD after resume
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (5 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11230] Kconfig no longer outputs a .config with freshly updated defconfigs Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11271] BUG: fealnx in 2.6.27-rc1 Rafael J. Wysocki
` (41 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Alan Jenkins, Hugh Dickins, Ingo Molnar,
Jeremy Fitzhardinge, Jeremy Fitzhardinge
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11237
Subject : corrupt PMD after resume
Submitter : Alan Jenkins <alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
Date : 2008-08-02 9:51 (42 days old)
References : http://marc.info/?l=linux-kernel&m=121767073424952&w=4
Handled-By : Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
Jeremy Fitzhardinge <jeremy-TSDbQ3PG+2Y@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122001615314700&w=2
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11230] Kconfig no longer outputs a .config with freshly updated defconfigs
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (4 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11224] Only three cores found on quad-core machine Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11237] corrupt PMD after resume Rafael J. Wysocki
` (42 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Josh Boyer
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11230
Subject : Kconfig no longer outputs a .config with freshly updated defconfigs
Submitter : Josh Boyer <jwboyer-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date : 2008-08-02 16:03 (42 days old)
References : http://marc.info/?l=linux-kernel&m=121769306319391&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11271] BUG: fealnx in 2.6.27-rc1
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (6 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11237] corrupt PMD after resume Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-13 8:47 ` Jaswinder Singh
2008-09-12 19:06 ` [Bug #11264] Invalid op opcode in kernel/workqueue Rafael J. Wysocki
` (40 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Francois Romieu, Jaswinder Singh
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11271
Subject : BUG: fealnx in 2.6.27-rc1
Submitter : Jaswinder Singh <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-05 14:58 (39 days old)
References : http://marc.info/?l=linux-netdev&m=121794762016830&w=4
http://lkml.org/lkml/2008/8/10/98
Handled-By : Francois Romieu <romieu-W8zweXLXuWQS+FvcfC7Uqw@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (8 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11264] Invalid op opcode in kernel/workqueue Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 20:46 ` Randy Dunlap
2008-09-12 19:06 ` [Bug #11272] BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835 Rafael J. Wysocki
` (38 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Bjorn Helgaas, Ingo Molnar, Randy Dunlap
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11276
Subject : build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-06 17:18 (38 days old)
References : http://marc.info/?l=linux-kernel&m=121804329014332&w=4
http://lkml.org/lkml/2008/7/22/353
Handled-By : Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Patch : http://lkml.org/lkml/2008/7/22/364
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11264] Invalid op opcode in kernel/workqueue
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (7 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11271] BUG: fealnx in 2.6.27-rc1 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things Rafael J. Wysocki
` (39 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Jean-Luc Coulon
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11264
Subject : Invalid op opcode in kernel/workqueue
Submitter : Jean-Luc Coulon <jean.luc.coulon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-07 04:18 (37 days old)
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11272] BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (9 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-16 15:25 ` Jaswinder Singh
2008-09-12 19:06 ` [Bug #11335] 2.6.27-rc2-git5 BUG: unable to handle kernel paging request Rafael J. Wysocki
` (37 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Jaswinder Singh
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11272
Subject : BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835
Submitter : Jaswinder Singh <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-05 15:12 (39 days old)
References : http://marc.info/?l=linux-kernel&m=121794900319776&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11335] 2.6.27-rc2-git5 BUG: unable to handle kernel paging request
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (10 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11272] BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28 Rafael J. Wysocki
` (36 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Hugh Dickins, Randy Dunlap
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11335
Subject : 2.6.27-rc2-git5 BUG: unable to handle kernel paging request
Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-12 4:18 (32 days old)
References : http://marc.info/?l=linux-kernel&m=121851477201960&w=4
http://lkml.org/lkml/2008/8/16/274
Handled-By : Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11340] LTP overnight run resulted in unusable box
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (12 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11336] 2.6.27-rc2:stall while mounting root fs Rafael J. Wysocki
` (34 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Alexey Dobriyan
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11340
Subject : LTP overnight run resulted in unusable box
Submitter : Alexey Dobriyan <adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-13 9:24 (31 days old)
References : http://marc.info/?l=linux-kernel&m=121861951902949&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11336] 2.6.27-rc2:stall while mounting root fs
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (13 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11340] LTP overnight run resulted in unusable box Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path Rafael J. Wysocki
` (33 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Thomas Gleixner, Torsten Kaiser
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11336
Subject : 2.6.27-rc2:stall while mounting root fs
Submitter : Torsten Kaiser <just.for.lkml-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Date : 2008-08-12 12:37 (32 days old)
References : http://marc.info/?l=linux-kernel&m=121854484015909&w=4
Handled-By : Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=17622
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (11 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11335] 2.6.27-rc2-git5 BUG: unable to handle kernel paging request Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 22:05 ` Christoph Lameter
2008-09-12 19:06 ` [Bug #11340] LTP overnight run resulted in unusable box Rafael J. Wysocki
` (35 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Christoph Lameter
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11308
Subject : tbench regression on each kernel release from 2.6.22 -> 2.6.28
Submitter : Christoph Lameter <cl-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Date : 2008-08-11 18:36 (33 days old)
References : http://marc.info/?l=linux-kernel&m=121847986119495&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11343] SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (17 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11357] Can not boot up with zd1211rw USB-Wlan Stick Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11404] BUG: in 2.6.23-rc3-git7 in do_cciss_intr Rafael J. Wysocki
` (29 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Manny Maxwell, Tejun Heo
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11343
Subject : SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i
Submitter : Manny Maxwell <mannymax-7UBucS1kxs3k1uMJSBkQmQ@public.gmane.org>
Date : 2008-08-14 4:16 (30 days old)
References : http://marc.info/?l=linux-kernel&m=121868782917600&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (14 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11336] 2.6.27-rc2:stall while mounting root fs Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11380] lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16 Rafael J. Wysocki
` (32 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Jeff Garzik, Tobias Diedrich, Yinghai Lu
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11358
Subject : net: forcedeth call restore mac addr in nv_shutdown path
Submitter : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-17 3:30 (27 days old)
References : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=121894389018584&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11357] Can not boot up with zd1211rw USB-Wlan Stick
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (16 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11380] lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11343] SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i Rafael J. Wysocki
` (30 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, uwe
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11357
Subject : Can not boot up with zd1211rw USB-Wlan Stick
Submitter : uwe <kender-KuiJ5kEpwI6ELgA04lAiVw@public.gmane.org>
Date : 2008-08-16 14:17 (28 days old)
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11380] lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (15 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11357] Can not boot up with zd1211rw USB-Wlan Stick Rafael J. Wysocki
` (31 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Ingo Molnar
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11380
Subject : lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
Submitter : Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Date : 2008-08-20 6:44 (24 days old)
References : http://marc.info/?l=linux-kernel&m=121921480931970&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (19 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11404] BUG: in 2.6.23-rc3-git7 in do_cciss_intr Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj Rafael J. Wysocki
` (27 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Christopher Li, David Vrabel
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11382
Subject : e1000e: 2.6.27-rc1 corrupts EEPROM/NVM
Submitter : David Vrabel <david.vrabel-kQvG35nSl+M@public.gmane.org>
Date : 2008-08-08 10:47 (36 days old)
References : http://marc.info/?l=linux-kernel&m=121819267211679&w=4
Handled-By : Christopher Li <chrisl-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Patch : http://marc.info/?l=linux-mm-commits&m=122038324200305&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11404] BUG: in 2.6.23-rc3-git7 in do_cciss_intr
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (18 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11343] SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM Rafael J. Wysocki
` (28 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, James Bottomley, Miller, Mike (OS Dev),
rdunlap
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11404
Subject : BUG: in 2.6.23-rc3-git7 in do_cciss_intr
Submitter : rdunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-08-21 5:52 (23 days old)
References : http://marc.info/?l=linux-kernel&m=121929819616273&w=4
http://marc.info/?l=linux-kernel&m=121932889105368&w=4
Handled-By : Miller, Mike (OS Dev) <Mike.Miller-VXdhtT5mjnY@public.gmane.org>
James Bottomley <James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (20 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-13 7:37 ` Frans Pop
2008-09-12 19:06 ` [Bug #11463] sshd hangs on close Rafael J. Wysocki
` (26 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Frans Pop
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11398
Subject : hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-08-21 17:17 (23 days old)
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11407] suspend: unable to handle kernel paging request
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (25 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11439] [2.6.27-rc4-git4] compilation warnings Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 20:50 ` Vegard Nossum
2008-09-12 19:06 ` [Bug #11442] btusb hibernation/suspend breakage in current -git Rafael J. Wysocki
` (21 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Pavel Machek, Pekka Enberg,
Rafael J. Wysocki, Vegard Nossum
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11407
Subject : suspend: unable to handle kernel paging request
Submitter : Vegard Nossum <vegard.nossum-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-21 17:28 (23 days old)
References : http://marc.info/?l=linux-kernel&m=121933974928881&w=4
Handled-By : Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
Pekka Enberg <penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.org>
Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11442] btusb hibernation/suspend breakage in current -git
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (26 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11407] suspend: unable to handle kernel paging request Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11471] GPE storm detected, kernel freezes Rafael J. Wysocki
` (20 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Oliver Neukum, Rafael J. Wysocki
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11442
Subject : btusb hibernation/suspend breakage in current -git
Submitter : Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
Date : 2008-08-25 11:37 (19 days old)
References : http://marc.info/?l=linux-bluetooth&m=121966402012074&w=4
Handled-By : Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
Patch : http://marc.info/?l=linux-bluetooth&m=121967226027323&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11439] [2.6.27-rc4-git4] compilation warnings
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (24 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11465] Linux-2.6.27-rc5, drm errors in log Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11407] suspend: unable to handle kernel paging request Rafael J. Wysocki
` (22 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Greg KH, Rufus & Azrael
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11439
Subject : [2.6.27-rc4-git4] compilation warnings
Submitter : Rufus & Azrael <rufus-azrael-Bf/eaXMDFuuXqB7oj33eUg@public.gmane.org>
Date : 2008-08-26 9:37 (18 days old)
References : http://marc.info/?l=linux-kernel&m=121974353815440&w=4
Handled-By : Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=121976424221858&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11459] kernel crash after wifi connection established
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (22 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11463] sshd hangs on close Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11465] Linux-2.6.27-rc5, drm errors in log Rafael J. Wysocki
` (24 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Alexey Kuznetsov
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11459
Subject : kernel crash after wifi connection established
Submitter : Alexey Kuznetsov <ak-b7SOpcJQXxU@public.gmane.org>
Date : 2008-08-30 03:08 (14 days old)
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11463] sshd hangs on close
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (21 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11459] kernel crash after wifi connection established Rafael J. Wysocki
` (25 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Matthias Urlichs
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11463
Subject : sshd hangs on close
Submitter : Matthias Urlichs <matthias-+qxcz+fHsVSELgA04lAiVw@public.gmane.org>
Date : 2008-08-30 9:18 (14 days old)
References : http://marc.info/?l=linux-kernel&m=122008800512864&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11465] Linux-2.6.27-rc5, drm errors in log
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (23 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11459] kernel crash after wifi connection established Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11439] [2.6.27-rc4-git4] compilation warnings Rafael J. Wysocki
` (23 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Dave Airlie, Gene Heskett
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11465
Subject : Linux-2.6.27-rc5, drm errors in log
Submitter : Gene Heskett <gene.heskett-H+0wwilmMs3R7s880joybQ@public.gmane.org>
Date : 2008-08-30 18:52 (14 days old)
References : http://marc.info/?l=linux-kernel&m=122012238925775&w=4
Handled-By : Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11471] GPE storm detected, kernel freezes
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (27 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11442] btusb hibernation/suspend breakage in current -git Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-16 5:50 ` Zhang Rui
2008-09-12 19:06 ` [Bug #11500] /proc/net bug related to selinux Rafael J. Wysocki
` (19 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, George Gibbs, Zhang Rui
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11471
Subject : GPE storm detected, kernel freezes
Submitter : George Gibbs <Vash63-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-08-31 22:00 (13 days old)
Handled-By : Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11485] 2.6.27-rc xen pvops regression?
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (29 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11500] /proc/net bug related to selinux Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11476] failure to associate after resume from suspend to ram Rafael J. Wysocki
` (17 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Alex Nixon, Bernhard Schmidt,
Jeremy Fitzhardinge
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11485
Subject : 2.6.27-rc xen pvops regression?
Submitter : Bernhard Schmidt <berni-wpePDvIxQxvMZTq/7ZfH4Q@public.gmane.org>
Date : 2008-08-31 17:18 (13 days old)
References : http://marc.info/?l=linux-kernel&m=122020367015025&w=4
Handled-By : Alex Nixon <alex.nixon-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Jeremy Fitzhardinge <jeremy-TSDbQ3PG+2Y@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11501] Failed to open destination file: Permission deniedihex2fw
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (31 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11476] failure to associate after resume from suspend to ram Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11505] oltp ~10% regression with 2.6.27-rc5 on stoakley machine Rafael J. Wysocki
` (15 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Andrew Morton
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11501
Subject : Failed to open destination file: Permission deniedihex2fw
Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Date : 2008-09-04 18:34 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122055342419068&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11476] failure to associate after resume from suspend to ram
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (30 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11485] 2.6.27-rc xen pvops regression? Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11501] Failed to open destination file: Permission deniedihex2fw Rafael J. Wysocki
` (16 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Dan Williams, Jouni Malinen,
Michael S. Tsirkin, Zhu Yi
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11476
Subject : failure to associate after resume from suspend to ram
Submitter : Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-01 13:33 (12 days old)
References : http://marc.info/?l=linux-kernel&m=122028529415108&w=4
Handled-By : Zhu Yi <yi.zhu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Jouni Malinen <j@w1.fi>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11500] /proc/net bug related to selinux
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (28 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11471] GPE storm detected, kernel freezes Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 22:14 ` James Morris
2008-09-12 19:06 ` [Bug #11485] 2.6.27-rc xen pvops regression? Rafael J. Wysocki
` (18 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Andrew Morton
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
Subject : /proc/net bug related to selinux
Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Date : 2008-09-04 17:45 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11505] oltp ~10% regression with 2.6.27-rc5 on stoakley machine
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (32 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11501] Failed to open destination file: Permission deniedihex2fw Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11507] usb: sometimes dead keyboard after boot Rafael J. Wysocki
` (14 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Gregory Haskins, Ingo Molnar, Lin Ming,
Peter Zijlstra
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11505
Subject : oltp ~10% regression with 2.6.27-rc5 on stoakley machine
Submitter : Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date : 2008-09-04 7:06 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122051202202373&w=4
http://marc.info/?t=122089704700005&r=1&w=4
Handled-By : Peter Zijlstra <a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>
Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11507] usb: sometimes dead keyboard after boot
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (33 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11505] oltp ~10% regression with 2.6.27-rc5 on stoakley machine Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11506] oops during unmount - ext3? (2.6.27-rc5) Rafael J. Wysocki
` (13 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Alan Stern, Frans Pop
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11507
Subject : usb: sometimes dead keyboard after boot
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-08-26 21:03 (18 days old)
References : http://marc.info/?l=linux-kernel&m=121977815018224&w=2
Handled-By : Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>
Patch : http://www.spinics.net/lists/linux-usb/msg09735.html
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11506] oops during unmount - ext3? (2.6.27-rc5)
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (34 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11507] usb: sometimes dead keyboard after boot Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-19 16:17 ` Marcin Slusarz
2008-09-12 19:06 ` [Bug #11516] severe performance degradation on x86_64 going from 2.6.26-rc9 -> 2.6.27-rc5 Rafael J. Wysocki
` (12 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Marcin Slusarz
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11506
Subject : oops during unmount - ext3? (2.6.27-rc5)
Submitter : Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-04 19:14 (9 days old)
References : http://marc.info/?l=linux-kernel&m=122055573123449&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11549] 2.6.27-rc5 acpi: EC Storm error message on bootup
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (39 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11512] sort-of regression due to "kconfig: speed up all*config + randconfig" Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11551] Semi-repeatable hard lockup on 2.6.27-rc6 Rafael J. Wysocki
` (7 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Alexey Starikovskiy,
jmerkey-6KXTs3wnGaZTqo3+vT/QGPegYHeGw8Jk
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11549
Subject : 2.6.27-rc5 acpi: EC Storm error message on bootup
Submitter : <jmerkey-6KXTs3wnGaZTqo3+vT/QGPegYHeGw8Jk@public.gmane.org>
Date : 2008-09-02 21:27 (11 days old)
References : http://marc.info/?l=linux-kernel&m=122039255517586&w=4
Handled-By : Alexey Starikovskiy <astarikovskiy-l3A5Bk7waGM@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122098180019264&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11512] sort-of regression due to "kconfig: speed up all*config + randconfig"
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (38 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11547] build issue #565 for v2.6.27-rc5 : undefined reference to `ei_interrupt' in hp-plus.c Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11549] 2.6.27-rc5 acpi: EC Storm error message on bootup Rafael J. Wysocki
` (8 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Alexey Dobriyan
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11512
Subject : sort-of regression due to "kconfig: speed up all*config + randconfig"
Submitter : Alexey Dobriyan <adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-05 22:50 (8 days old)
References : http://marc.info/?l=linux-kernel&m=122065498013858&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11516] severe performance degradation on x86_64 going from 2.6.26-rc9 -> 2.6.27-rc5
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (35 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11506] oops during unmount - ext3? (2.6.27-rc5) Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11548] kernel BUG at drivers/pci/intel-iommu.c:1373! Rafael J. Wysocki
` (11 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Jason Vas Dias
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11516
Subject : severe performance degradation on x86_64 going from 2.6.26-rc9 -> 2.6.27-rc5
Submitter : Jason Vas Dias <jason.vas.dias-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-07 13:59 (6 days old)
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11547] build issue #565 for v2.6.27-rc5 : undefined reference to `ei_interrupt' in hp-plus.c
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (37 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11548] kernel BUG at drivers/pci/intel-iommu.c:1373! Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11512] sort-of regression due to "kconfig: speed up all*config + randconfig" Rafael J. Wysocki
` (9 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Randy.Dunlap, Toralf Förster
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11547
Subject : build issue #565 for v2.6.27-rc5 : undefined reference to `ei_interrupt' in hp-plus.c
Submitter : Toralf Förster <toralf.foerster-Mmb7MZpHnFY@public.gmane.org>
Date : 2008-09-07 13:19 (6 days old)
References : http://marc.info/?l=linux-kernel&m=122079361508022&w=4
Handled-By : Randy.Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Patch : http://marc.info/?l=linux-next&m=122038632306156&w=2
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11548] kernel BUG at drivers/pci/intel-iommu.c:1373!
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (36 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11516] severe performance degradation on x86_64 going from 2.6.26-rc9 -> 2.6.27-rc5 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 20:56 ` Chris Mason
2008-09-12 19:06 ` [Bug #11547] build issue #565 for v2.6.27-rc5 : undefined reference to `ei_interrupt' in hp-plus.c Rafael J. Wysocki
` (10 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Chris Mason
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11548
Subject : kernel BUG at drivers/pci/intel-iommu.c:1373!
Submitter : Chris Mason <chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date : 2008-09-08 14:26 (5 days old)
References : http://marc.info/?l=linux-kernel&m=122088566310440&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11552] Disabling IRQ #23
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (42 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11553] Strange looking line from "ps aux" Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-13 3:24 ` Justin Mattock
2008-09-12 19:06 ` [Bug #11554] Partition check considered as error is breaking mounting in 2.6.27 Rafael J. Wysocki
` (4 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Justin Mattock, Yinghai Lu
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11552
Subject : Disabling IRQ #23
Submitter : Justin Mattock <justinmattock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date : 2008-09-09 19:08 (4 days old)
References : http://marc.info/?l=linux-kernel&m=122098735230906&w=4
http://marc.info/?l=linux-kernel&m=122107367715361&w=4
Handled-By : Yinghai Lu <yhlu.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11551] Semi-repeatable hard lockup on 2.6.27-rc6
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (40 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11549] 2.6.27-rc5 acpi: EC Storm error message on bootup Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11553] Strange looking line from "ps aux" Rafael J. Wysocki
` (6 subsequent siblings)
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Steven Noonan
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11551
Subject : Semi-repeatable hard lockup on 2.6.27-rc6
Submitter : Steven Noonan <steven-Cunn4gMjHvbm+q05EWxUEA@public.gmane.org>
Date : 2008-09-10 18:07 (3 days old)
References : http://marc.info/?l=linux-kernel&m=122107007407994&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11550] pnp: Huge number of "io resource overlap" messages
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (44 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11554] Partition check considered as error is breaking mounting in 2.6.27 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 22:52 ` Rene Herman
2008-09-12 19:06 ` [Bug #11556] e100: PCI wake-up handling rework causes "Error clearing wake event" Rafael J. Wysocki
` (2 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Bjorn Helgaas, Frans Pop, Rene Herman
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11550
Subject : pnp: Huge number of "io resource overlap" messages
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-09-09 10:50 (4 days old)
References : http://marc.info/?l=linux-kernel&m=122095745403793&w=4
Handled-By : Rene Herman <rene.herman-cENuUygGYd//D1n+0JDH9g@public.gmane.org>
Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122098498125536&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11553] Strange looking line from "ps aux"
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (41 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11551] Semi-repeatable hard lockup on 2.6.27-rc6 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-13 8:51 ` Alan Jenkins
2008-09-12 19:06 ` [Bug #11552] Disabling IRQ #23 Rafael J. Wysocki
` (5 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Rogério Brito
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11553
Subject : Strange looking line from "ps aux"
Submitter : Rogério Brito <rbrito-qczF+2RCDl1fyO9Q7EP/yw@public.gmane.org>
Date : 2008-09-11 17:43 (2 days old)
References : http://marc.info/?l=linux-kernel&m=122115506018275&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11554] Partition check considered as error is breaking mounting in 2.6.27
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (43 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11552] Disabling IRQ #23 Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-13 23:37 ` Herton Ronaldo Krzesinski
2008-09-12 19:06 ` [Bug #11550] pnp: Huge number of "io resource overlap" messages Rafael J. Wysocki
` (3 subsequent siblings)
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Abdel Benamrouche, Andrew Morton,
Herton Ronaldo Krzesinski, Linus Torvalds
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11554
Subject : Partition check considered as error is breaking mounting in 2.6.27
Submitter : Herton Ronaldo Krzesinski <herton-4qZELD6Fgxg39yzSjRtAkw@public.gmane.org>
Date : 2008-09-12 16:56 (1 days old)
References : http://marc.info/?l=linux-kernel&m=122123862519434&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11557] Controlling backlight on thinkpad x60
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (47 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11559] 2.6.27-rc6: nohz + s2ram = need to press keys to get progress Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-13 15:13 ` Matthew Garrett
48 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Matthew Garrett, Pavel Machek
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11557
Subject : Controlling backlight on thinkpad x60
Submitter : Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Date : 2008-09-08 15:10 (5 days old)
References : http://marc.info/?l=linux-kernel&m=122088987319698&w=4
Handled-By : Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11559] 2.6.27-rc6: nohz + s2ram = need to press keys to get progress
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (46 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11556] e100: PCI wake-up handling rework causes "Error clearing wake event" Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11557] Controlling backlight on thinkpad x60 Rafael J. Wysocki
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: Kernel Testers List, Pavel Machek
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11559
Subject : 2.6.27-rc6: nohz + s2ram = need to press keys to get progress
Submitter : Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Date : 2008-09-12 8:31 (1 days old)
References : http://marc.info/?l=linux-kernel&m=122121384705262&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* [Bug #11556] e100: PCI wake-up handling rework causes "Error clearing wake event"
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
` (45 preceding siblings ...)
2008-09-12 19:06 ` [Bug #11550] pnp: Huge number of "io resource overlap" messages Rafael J. Wysocki
@ 2008-09-12 19:06 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11559] 2.6.27-rc6: nohz + s2ram = need to press keys to get progress Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11557] Controlling backlight on thinkpad x60 Rafael J. Wysocki
48 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 19:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Frans Pop, Rafael J. Wysocki
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.26. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11556
Subject : e100: PCI wake-up handling rework causes "Error clearing wake event"
Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date : 2008-09-09 6:12 (4 days old)
References : http://marc.info/?l=linux-netdev&m=122094080712131&w=4
Handled-By : Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
Patch : http://marc.info/?l=linux-kernel&m=122096638020191&w=4
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
2008-09-12 19:06 ` [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things Rafael J. Wysocki
@ 2008-09-12 20:46 ` Randy Dunlap
[not found] ` <48CAD51D.4060908-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Randy Dunlap @ 2008-09-12 20:46 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Bjorn Helgaas,
Ingo Molnar
Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11276
> Subject : build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
> Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> Date : 2008-08-06 17:18 (38 days old)
> References : http://marc.info/?l=linux-kernel&m=121804329014332&w=4
> http://lkml.org/lkml/2008/7/22/353
> Handled-By : Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
> Patch : http://lkml.org/lkml/2008/7/22/364
Yes, I still see this build error.
What would it take to have Bjorn's patch merged into mainline?
--
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11407] suspend: unable to handle kernel paging request
2008-09-12 19:06 ` [Bug #11407] suspend: unable to handle kernel paging request Rafael J. Wysocki
@ 2008-09-12 20:50 ` Vegard Nossum
0 siblings, 0 replies; 126+ messages in thread
From: Vegard Nossum @ 2008-09-12 20:50 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Pavel Machek,
Pekka Enberg
On Fri, Sep 12, 2008 at 9:06 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11407
> Subject : suspend: unable to handle kernel paging request
> Submitter : Vegard Nossum <vegard.nossum-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date : 2008-08-21 17:28 (23 days old)
> References : http://marc.info/?l=linux-kernel&m=121933974928881&w=4
> Handled-By : Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
> Pekka Enberg <penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.org>
> Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
I'm sorry for not replying sooner. This is current status: Problem was
never resolved. I tried to bisect, but I only ran into other problems
with either config not being supported for my machine prior to certain
date while trying to find a good bisection point. It's been a while
now, so I don't remember everything exactly, but I may try to
reproduce it tomorrow on the latest -git and see what comes up.
Will report back as soon as I have more info. Thanks,
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11548] kernel BUG at drivers/pci/intel-iommu.c:1373!
2008-09-12 19:06 ` [Bug #11548] kernel BUG at drivers/pci/intel-iommu.c:1373! Rafael J. Wysocki
@ 2008-09-12 20:56 ` Chris Mason
[not found] ` <1221252989.8709.11.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Chris Mason @ 2008-09-12 20:56 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List
On Fri, 2008-09-12 at 21:06 +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
This is still a bug, but I haven't tried this workload on 2.6.26, so I'm
not sure it is a regression. Unfortunately, I won't be able to test it
again until after the plumber's conference.
-chris
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
[not found] ` <48CAD51D.4060908-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
@ 2008-09-12 21:19 ` Rafael J. Wysocki
[not found] ` <200809122319.18633.rjw-KKrjLPT3xs0@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 21:19 UTC (permalink / raw)
To: Randy Dunlap
Cc: Linux Kernel Mailing List, Kernel Testers List, Bjorn Helgaas,
Ingo Molnar, Andrew Morton
On Friday, 12 of September 2008, Randy Dunlap wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.26. Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11276
> > Subject : build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
> > Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> > Date : 2008-08-06 17:18 (38 days old)
> > References : http://marc.info/?l=linux-kernel&m=121804329014332&w=4
> > http://lkml.org/lkml/2008/7/22/353
> > Handled-By : Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
> > Patch : http://lkml.org/lkml/2008/7/22/364
>
> Yes, I still see this build error.
> What would it take to have Bjorn's patch merged into mainline?
Well, send a request to Andrew I think (with the patch appended).
Thanks,
Rafael
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11548] kernel BUG at drivers/pci/intel-iommu.c:1373!
[not found] ` <1221252989.8709.11.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
@ 2008-09-12 21:21 ` Rafael J. Wysocki
0 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-12 21:21 UTC (permalink / raw)
To: Chris Mason; +Cc: Linux Kernel Mailing List, Kernel Testers List
On Friday, 12 of September 2008, Chris Mason wrote:
> On Fri, 2008-09-12 at 21:06 +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.26. Please verify if it still should be listed and let me know
> > (either way).
> >
>
> This is still a bug, but I haven't tried this workload on 2.6.26, so I'm
> not sure it is a regression. Unfortunately, I won't be able to test it
> again until after the plumber's conference.
That's fine. In case it turns out to be a regression, it's better to list it
for now IMO. :-)
Thanks,
Rafael
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
2008-09-12 19:06 ` [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28 Rafael J. Wysocki
@ 2008-09-12 22:05 ` Christoph Lameter
[not found] ` <48CAE7A0.8000004-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Christoph Lameter @ 2008-09-12 22:05 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List
Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11308
> Subject : tbench regression on each kernel release from 2.6.22 -> 2.6.28
> Submitter : Christoph Lameter <cl-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> Date : 2008-08-11 18:36 (33 days old)
> References : http://marc.info/?l=linux-kernel&m=121847986119495&w=4
>
>
>
tbench
2.6.27-rc6 2760 MB/sec
2.6.22 3235.47 MB/sec
diff on the .config files for each (took .22 config and did a make oldconfig)
--- /boot/config-2.6.22.1-4U4JUMP1.12 2008-01-22 08:06:38.000000000 -0600
+++ .config 2008-09-12 16:33:52.000000000 -0500
@@ -1,55 +1,89 @@
#
# Automatically generated make config: don't edit
-# Linux kernel version: 2.6.22.1-4U4JUMP1.12
-# Mon Jan 21 16:05:52 2008
+# Linux kernel version: 2.6.27-rc6
+# Fri Sep 12 16:33:52 2008
#
+# CONFIG_64BIT is not set
CONFIG_X86_32=y
+# CONFIG_X86_64 is not set
+CONFIG_X86=y
+CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
+# CONFIG_GENERIC_LOCKBREAK is not set
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_HAVE_LATENCYTOP_SUPPORT=y
+CONFIG_FAST_CMPXCHG_LOCAL=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_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
-CONFIG_DMI=y
+# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
+CONFIG_RWSEM_XCHGADD_ALGORITHM=y
+# CONFIG_ARCH_HAS_ILOG2_U32 is not set
+# CONFIG_ARCH_HAS_ILOG2_U64 is not set
+CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
+CONFIG_GENERIC_CALIBRATE_DELAY=y
+# CONFIG_GENERIC_TIME_VSYSCALL is not set
+CONFIG_ARCH_HAS_CPU_RELAX=y
+CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
+CONFIG_HAVE_SETUP_PER_CPU_AREA=y
+# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
+CONFIG_ARCH_HIBERNATION_POSSIBLE=y
+CONFIG_ARCH_SUSPEND_POSSIBLE=y
+# CONFIG_ZONE_DMA32 is not set
+CONFIG_ARCH_POPULATES_NODE_MAP=y
+# CONFIG_AUDIT_ARCH is not set
+CONFIG_ARCH_SUPPORTS_AOUT=y
+CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
+CONFIG_GENERIC_HARDIRQS=y
+CONFIG_GENERIC_IRQ_PROBE=y
+CONFIG_GENERIC_PENDING_IRQ=y
+CONFIG_X86_SMP=y
+CONFIG_X86_32_SMP=y
+CONFIG_X86_HT=y
+CONFIG_X86_BIOS_REBOOT=y
+CONFIG_X86_TRAMPOLINE=y
+CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
-# Code maturity level options
+# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
-
-#
-# General setup
-#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
-# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
-# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
-# CONFIG_CPUSETS is not set
+# CONFIG_CGROUPS is not set
+CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
+# CONFIG_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
+CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
+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=y
@@ -64,6 +98,8 @@
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
+CONFIG_PCSPKR_PLATFORM=y
+CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
@@ -76,28 +112,40 @@
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
+CONFIG_PROFILING=y
+# CONFIG_MARKERS is not set
+CONFIG_OPROFILE=y
+CONFIG_HAVE_OPROFILE=y
+CONFIG_KPROBES=y
+CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
+CONFIG_KRETPROBES=y
+CONFIG_HAVE_IOREMAP_PROT=y
+CONFIG_HAVE_KPROBES=y
+CONFIG_HAVE_KRETPROBES=y
+# CONFIG_HAVE_ARCH_TRACEHOOK is not set
+# CONFIG_HAVE_DMA_ATTRS is not set
+CONFIG_USE_GENERIC_SMP_HELPERS=y
+# CONFIG_HAVE_CLK is not set
+CONFIG_PROC_PAGE_MONITOR=y
+CONFIG_HAVE_GENERIC_DMA_COHERENT=y
+CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
-
-#
-# Loadable module support
-#
CONFIG_MODULES=y
+# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
-# CONFIG_KMOD is not set
+CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
-
-#
-# Block layer
-#
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
+# CONFIG_BLK_DEV_INTEGRITY is not set
#
# IO Schedulers
@@ -111,6 +159,7 @@
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
+CONFIG_CLASSIC_RCU=y
#
# Processor type and features
@@ -118,17 +167,23 @@
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
+CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
+CONFIG_X86_FIND_SMP_CONFIG=y
+CONFIG_X86_MPPARSE=y
# CONFIG_X86_PC is not set
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
+CONFIG_X86_GENERICARCH=y
# 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=y
# CONFIG_X86_ES7000 is not set
-# CONFIG_PARAVIRT is not set
+# CONFIG_X86_BIGSMP is not set
+# CONFIG_X86_VSMP is not set
+# CONFIG_X86_RDC321X is not set
+CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
+# CONFIG_PARAVIRT_GUEST is not set
+# CONFIG_MEMTEST is not set
CONFIG_X86_CYCLONE_TIMER=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
@@ -139,7 +194,6 @@
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
-CONFIG_MCORE2=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
@@ -154,33 +208,34 @@
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
+# CONFIG_MPSC is not set
+CONFIG_MCORE2=y
+# CONFIG_GENERIC_CPU is not set
CONFIG_X86_GENERIC=y
+CONFIG_X86_CPU=y
CONFIG_X86_CMPXCHG=y
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-12 19:06 ` [Bug #11500] /proc/net bug related to selinux Rafael J. Wysocki
@ 2008-09-12 22:14 ` James Morris
[not found] ` <alpine.LRH.1.10.0809130812460.12313-CK9fWmtY32x9JUWOpEiw7w@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: James Morris @ 2008-09-12 22:14 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Andrew Morton,
Stephen Smalley
On Fri, 12 Sep 2008, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> Subject : /proc/net bug related to selinux
> Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> Date : 2008-09-04 17:45 (9 days old)
> References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
I think this might be a regression caused by namespace changes which we
addressed in SELinux policy. Which distro version & policy version is
this seen with?
- James
--
James Morris
<jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <alpine.LRH.1.10.0809130812460.12313-CK9fWmtY32x9JUWOpEiw7w@public.gmane.org>
@ 2008-09-12 22:24 ` Andrew Morton
[not found] ` <20080912152443.c4e59f42.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Andrew Morton @ 2008-09-12 22:24 UTC (permalink / raw)
To: James Morris
Cc: rjw-KKrjLPT3xs0, linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA, sds-+05T5uksL2qpZYMLLGbcSA
On Sat, 13 Sep 2008 08:14:10 +1000 (EST)
James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org> wrote:
> On Fri, 12 Sep 2008, Rafael J. Wysocki wrote:
>
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.26. Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> > Subject : /proc/net bug related to selinux
> > Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > Date : 2008-09-04 17:45 (9 days old)
> > References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
>
> I think this might be a regression caused by namespace changes which we
> addressed in SELinux policy. Which distro version & policy version is
> this seen with?
>
FC5 on x86_32 and FC6 on x86_64.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11550] pnp: Huge number of "io resource overlap" messages
2008-09-12 19:06 ` [Bug #11550] pnp: Huge number of "io resource overlap" messages Rafael J. Wysocki
@ 2008-09-12 22:52 ` Rene Herman
0 siblings, 0 replies; 126+ messages in thread
From: Rene Herman @ 2008-09-12 22:52 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Bjorn Helgaas,
Frans Pop
On 12-09-08 21:06, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11550
> Subject : pnp: Huge number of "io resource overlap" messages
> Submitter : Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
> Date : 2008-09-09 10:50 (4 days old)
> References : http://marc.info/?l=linux-kernel&m=122095745403793&w=4
> Handled-By : Rene Herman <rene.herman-cENuUygGYd//D1n+0JDH9g@public.gmane.org>
> Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
> Patch : http://marc.info/?l=linux-kernel&m=122098498125536&w=4
It should be. The patch listed should be good as far as I'm concerned
but needs to be pushed by Bjorn as PnP mainatainer. Generally speaking 0
wouldn't be a _very_ necesarily invalid value it seems so it's maybe not
very nice.
If someone wants a changelog though, this should do:
===
PNP: avoid checking unitialized BARs for conflicts
Avoid checking a PCI BAR for conflicts if the BIOS left it unitialized.
Reported-by: Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Signed-off-by: Rene Herman <rene.herman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
===
(Frans: Tested-by?)
Rene.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <20080912152443.c4e59f42.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
@ 2008-09-13 0:15 ` James Morris
[not found] ` <alpine.LRH.1.10.0809131012310.13073-CK9fWmtY32x9JUWOpEiw7w@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: James Morris @ 2008-09-13 0:15 UTC (permalink / raw)
To: Andrew Morton
Cc: rjw-KKrjLPT3xs0, linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA, sds-+05T5uksL2qpZYMLLGbcSA
On Fri, 12 Sep 2008, Andrew Morton wrote:
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> > > Subject : /proc/net bug related to selinux
> > > Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > > Date : 2008-09-04 17:45 (9 days old)
> > > References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
> >
> > I think this might be a regression caused by namespace changes which we
By which I mean, this was caused by a non-SELinux change to the upstream
kernel many, many eons ago.
> > addressed in SELinux policy. Which distro version & policy version is
> > this seen with?
> >
>
> FC5 on x86_32 and FC6 on x86_64.
As mentioned in the bugzilla, any related avc messages would be useful.
--
James Morris
<jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11552] Disabling IRQ #23
2008-09-12 19:06 ` [Bug #11552] Disabling IRQ #23 Rafael J. Wysocki
@ 2008-09-13 3:24 ` Justin Mattock
0 siblings, 0 replies; 126+ messages in thread
From: Justin Mattock @ 2008-09-13 3:24 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Yinghai Lu
On Fri, Sep 12, 2008 at 12:06 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11552
> Subject : Disabling IRQ #23
> Submitter : Justin Mattock <justinmattock@gmail.com>
> Date : 2008-09-09 19:08 (4 days old)
> References : http://marc.info/?l=linux-kernel&m=122098735230906&w=4
> http://marc.info/?l=linux-kernel&m=122107367715361&w=4
> Handled-By : Yinghai Lu <yhlu.kernel@gmail.com>
>
>
>
yeah I think it would be a good idea.
something to do with ehci_hcd, i.g. if I blacklist
ehci_hcd Disabling IRQ#23 message doesnt seem to be showing up.
--
Justin P. Mattock
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
2008-09-12 19:06 ` [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj Rafael J. Wysocki
@ 2008-09-13 7:37 ` Frans Pop
[not found] ` <200809130937.52685.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Frans Pop @ 2008-09-13 7:37 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List
On Friday 12 September 2008, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me
> know (either way).
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11398
> Subject : hda_intel: IRQ timing workaround is activated for card #0.
> Suggest a bigger bdl_pos_adj.
Still there.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11271] BUG: fealnx in 2.6.27-rc1
2008-09-12 19:06 ` [Bug #11271] BUG: fealnx in 2.6.27-rc1 Rafael J. Wysocki
@ 2008-09-13 8:47 ` Jaswinder Singh
0 siblings, 0 replies; 126+ messages in thread
From: Jaswinder Singh @ 2008-09-13 8:47 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Francois Romieu,
Jeff Garzik, davem-fT/PcQaiUtIeIZ0/mPfg9Q,
netdev-u79uwXL29TY76Z2rM5mHXA
Hello all,
On Fri, Sep 12, 2008 at 3:06 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11271
> Subject : BUG: fealnx in 2.6.27-rc1
> Submitter : Jaswinder Singh <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date : 2008-08-05 14:58 (39 days old)
> References : http://marc.info/?l=linux-netdev&m=121794762016830&w=4
> http://lkml.org/lkml/2008/8/10/98
I am sorry for delay.
Now I am testing for same problem with 2.6.27-rc6.:
1. On different MYSON Technology Inc SURECOM EP-320X-S 100/10M
Ethernet PCI Adapters
2. On different Linux PCs
3. With different Ethernet switches which supports 100 Mb
4. With different CAT 5 ethernet cables which supports 100 Mb
5. Also checking old patches on fealnx as per Jeff.
And it seems, I am getting following error, with few ethernet switches
and cables and when I switch ethernet cables :
"NETDEV WATCHDOG: eth0 (fealnx): transmit timed out
eth0: Transmit timed out, status 00000000, resetting..."
Now I am trying to confirm that problem is coming from ethernet
switches and cables.
I am also facing one more Issue :
With same 100 Mb ethernet switch and cable my another NIC run at 100
Mb/s and full duplex but MYSON Technology Inc SURECOM EP-320X-S
100/10M runs on 10 Mb/s and half duplex.
I debug fealnx it says : PHYType 1 duplex_mode : 2 line_speed : 2
crvalue : 0xe40e61 bcrvalue : 0x10 imrvalue : 0x46c flags : 0x1
So it is saying duplex_mode : 2 (full duplex) and line_speed = 2
(100M) then why I am getting 10MB half duplex ?
#lspci -vv
02:02.0 Ethernet controller: MYSON Technology Inc SURECOM EP-320X-S
100/10M Ethernet PCI Adapter
Subsystem: MYSON Technology Inc SURECOM EP-320X-S 100/10M
Ethernet PCI Adapter
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at b800 [size=256]
Region 1: Memory at ff9ffc00 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at 50000000 [disabled] [size=64K]
Capabilities: [88] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
PME(D0-,D1+,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: fealnx
#/sbin/ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: off
Current message level: 0x00000000 (0)
Link detected: no
Thank you,
Jaswinder Singh.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11553] Strange looking line from "ps aux"
2008-09-12 19:06 ` [Bug #11553] Strange looking line from "ps aux" Rafael J. Wysocki
@ 2008-09-13 8:51 ` Alan Jenkins
0 siblings, 0 replies; 126+ messages in thread
From: Alan Jenkins @ 2008-09-13 8:51 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List,
Rogério Brito
Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11553
> Subject : Strange looking line from "ps aux"
> Submitter : Rogério Brito <rbrito-qczF+2RCDl1fyO9Q7EP/yw@public.gmane.org>
> Date : 2008-09-11 17:43 (2 days old)
> References : http://marc.info/?l=linux-kernel&m=122115506018275&w=4
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Isn't this another instance of
<http://bugzilla.kernel.org/show_bug.cgi?id=11209>?
If you can try 2.6.27-rc6, that should fix it.
Alan
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <48CAE7A0.8000004-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
@ 2008-09-13 11:44 ` Mike Galbraith
[not found] ` <1221306287.5213.111.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-13 11:44 UTC (permalink / raw)
To: Christoph Lameter
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Fri, 2008-09-12 at 17:05 -0500, Christoph Lameter wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.26. Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11308
> > Subject : tbench regression on each kernel release from 2.6.22 -> 2.6.28
> > Submitter : Christoph Lameter <cl-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > Date : 2008-08-11 18:36 (33 days old)
> > References : http://marc.info/?l=linux-kernel&m=121847986119495&w=4
> >
> >
> >
>
> tbench
>
> 2.6.27-rc6 2760 MB/sec
> 2.6.22 3235.47 MB/sec
Numbers from my Q6600 Aldi supermarket box (hm, your box is from different shelf)
tbench -t 60 4 localhost followed by 4 60s netperf TCP_RR pairs, each pair
jabbering on a separate port and affine to a separate CPU. Configs are
as close as I can make them, all kernels built and tested today by
identical userland.
2.6.22.19
Throughput 1136.02 MB/sec 4 procs
16384 87380 1 1 60.01 94179.12
16384 87380 1 1 60.01 88780.61
16384 87380 1 1 60.01 91057.72
16384 87380 1 1 60.01 94242.16
2.6.22.19-cfs-v24.1 (identical config)
Throughput 1126.79 MB/sec 4 procs
16384 87380 1 1 60.00 88809.14
16384 87380 1 1 60.00 89971.25
16384 87380 1 1 60.01 89452.91
16384 87380 1 1 60.01 89478.63
2.6.23.17
Throughput 1073.2 MB/sec 4 procs
16384 87380 1 1 60.00 83635.61
16384 87380 1 1 60.00 82754.36
16384 87380 1 1 60.00 84594.59
16384 87380 1 1 60.00 82995.81
2.6.23.17-cfs-v24.1 (identical config)
Throughput 1145.28 MB/sec 4 procs
16384 87380 1 1 60.00 90278.55
16384 87380 1 1 60.01 90579.31
16384 87380 1 1 60.01 89412.14
16384 87380 1 1 60.00 90270.97
2.6.24.7
Throughput 1119.28 MB/sec 4 procs
16384 87380 1 1 60.00 84092.78
16384 87380 1 1 60.00 84120.68
16384 87380 1 1 60.00 84076.73
16384 87380 1 1 60.00 83995.07
2.6.25.17
Throughput 1113.82 MB/sec 4 procs
16384 87380 1 1 60.00 84629.98
16384 87380 1 1 60.00 84776.38
16384 87380 1 1 60.00 84356.49
16384 87380 1 1 60.00 84469.71
2.6.26.5
Throughput 1095.26 MB/sec 4 procs
16384 87380 1 1 60.00 84481.11
16384 87380 1 1 60.00 84604.38
16384 87380 1 1 60.01 86526.84
16384 87380 1 1 60.01 84478.01
2.6.27-rc6
Throughput 1037.98 MB/sec 4 procs
16384 87380 1 1 60.00 80293.80
16384 87380 1 1 60.00 80266.60
16384 87380 1 1 60.00 80394.83
16384 87380 1 1 60.01 80397.27
I spent two weeks chasing various and sundry netperf numbers recently,
only learning in the process that netperf is _utterly immune_ to
bisection. Tbench numbers don't look promising for bisection from here.
Note to quixotic self: destroy log immediately lest you be tempted.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221306287.5213.111.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-13 11:57 ` Mike Galbraith
2008-09-14 6:24 ` Mike Galbraith
2008-09-14 14:18 ` Christoph Lameter
2 siblings, 0 replies; 126+ messages in thread
From: Mike Galbraith @ 2008-09-13 11:57 UTC (permalink / raw)
To: Christoph Lameter
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Sat, 2008-09-13 at 13:44 +0200, Mike Galbraith wrote:
> 2.6.23.17-cfs-v24.1 (identical config)
> Throughput 1145.28 MB/sec 4 procs
>
> 16384 87380 1 1 60.00 90278.55
> 16384 87380 1 1 60.01 90579.31
> 16384 87380 1 1 60.01 89412.14
> 16384 87380 1 1 60.00 90270.97
>
> 2.6.24.7
> Throughput 1119.28 MB/sec 4 procs
>
> 16384 87380 1 1 60.00 84092.78
> 16384 87380 1 1 60.00 84120.68
> 16384 87380 1 1 60.00 84076.73
> 16384 87380 1 1 60.00 83995.07
P.S. fwiw, scheduler difference between these two kernels is practically
nill.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11557] Controlling backlight on thinkpad x60
2008-09-12 19:06 ` [Bug #11557] Controlling backlight on thinkpad x60 Rafael J. Wysocki
@ 2008-09-13 15:13 ` Matthew Garrett
[not found] ` <20080913151330.GA20761-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Matthew Garrett @ 2008-09-13 15:13 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Pavel Machek
I don't think this is a regression. The correct way to drive this
hardware has always been through the ACPI video driver. The fact that
thinkpad-acpi would also attempt to drive it was a bug.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[not found] ` <200809130937.52685.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
@ 2008-09-13 17:23 ` Takashi Iwai
[not found] ` <s5habecm03s.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Takashi Iwai @ 2008-09-13 17:23 UTC (permalink / raw)
To: Frans Pop
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
At Sat, 13 Sep 2008 09:37:51 +0200,
Frans Pop wrote:
>
> On Friday 12 September 2008, Rafael J. Wysocki wrote:
> > The following bug entry is on the current list of known regressions
> > from 2.6.26. Please verify if it still should be listed and let me
> > know (either way).
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11398
> > Subject : hda_intel: IRQ timing workaround is activated for card #0.
> > Suggest a bigger bdl_pos_adj.
>
> Still there.
Yeah, the driver wasn't changed about this.
Basically it's a warning message that CPU usage got higher due to
somehow wrongly behaving hardware. The driver behavior itself didn't
do anything wrong. That is, if the driver didn't show it, you
wouldn't have noticed any change (or noticed improvements in some apps
:)
Of course, it would be ideal if we can add a perfect workaround for
it, but right now, I have no idea what to do better. So, I don't
think it's worth to keeping this open as a regression.
thanks,
Takashi
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <alpine.LRH.1.10.0809131012310.13073-CK9fWmtY32x9JUWOpEiw7w@public.gmane.org>
@ 2008-09-13 19:37 ` Andrew Morton
[not found] ` <20080913123722.e238ae2a.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Andrew Morton @ 2008-09-13 19:37 UTC (permalink / raw)
To: James Morris
Cc: rjw-KKrjLPT3xs0, linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA, sds-+05T5uksL2qpZYMLLGbcSA
On Sat, 13 Sep 2008 10:15:43 +1000 (EST) James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org> wrote:
> On Fri, 12 Sep 2008, Andrew Morton wrote:
>
> > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> > > > Subject : /proc/net bug related to selinux
> > > > Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > > > Date : 2008-09-04 17:45 (9 days old)
> > > > References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
> > >
> > > I think this might be a regression caused by namespace changes which we
>
> By which I mean, this was caused by a non-SELinux change to the upstream
> kernel many, many eons ago.
hm, seems that 2.6.24 is OK but 2.6.25 is not. I must have missed the
bug when testing 2.6.25-based kernels.
I started a git bisection search but after half an hour I hit bad
bisection breakage: a complete machine hang in fib_rules_init().
> > > addressed in SELinux policy. Which distro version & policy version is
> > > this seen with?
> > >
> >
> > FC5 on x86_32 and FC6 on x86_64.
>
> As mentioned in the bugzilla, any related avc messages would be useful.
2.6.25 dmesg: http://userweb.kernel.org/~akpm/dmesg-sony.txt
/var/log/messages: http://userweb.kernel.org/~akpm/messages-sony.txt
The latter includes this:
Sep 13 12:32:43 sony kernel: SELinux: class key not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: class dccp_socket not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: class memprotect not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: class peer not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: class capability2 not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission open in class dir not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission open in class file not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission open in class chr_file not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission open in class blk_file not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission open in class fifo_file not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class node not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class node not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission recvfrom in class node not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission sendto in class node not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class netif not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class netif not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission ingress in class netif not defined in policy
Sep 13 12:32:43 sony kernel: SELinux: permission egress in class netif not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission setkeycreate in class process not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission setsockcreate in class process not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission setfcap in class capability not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission polmatch in class association not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission flow_in in class packet not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission flow_out in class packet not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission forward_in in class packet not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: permission forward_out in class packet not defined in policy
Sep 13 12:32:44 sony kernel: SELinux: the above unknown classes and permissions will be denied
Sep 13 12:32:44 sony kernel: type=1403 audit(1221309118.644:3): policy loaded auid=4294967295 ses=4294967295
Sep 13 12:32:44 sony kernel: type=1400 audit(1221334321.726:4): avc: denied { audit_write } for pid=400 comm="hwclock" capability=29 scontext=system_u:system_r:hwclock_t:s0 tcontext=system_u:system_r:hwclock_t:s0 tclass=capability
Why am I seeing this on two machines and two vanilla-installed distros
but nobody else is reporting it?
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11554] Partition check considered as error is breaking mounting in 2.6.27
2008-09-12 19:06 ` [Bug #11554] Partition check considered as error is breaking mounting in 2.6.27 Rafael J. Wysocki
@ 2008-09-13 23:37 ` Herton Ronaldo Krzesinski
[not found] ` <200809132037.55922.herton-4qZELD6Fgxg39yzSjRtAkw@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Herton Ronaldo Krzesinski @ 2008-09-13 23:37 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Abdel Benamrouche,
Andrew Morton, Linus Torvalds
On Friday 12 September 2008 16:06:31 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11554
> Subject : Partition check considered as error is breaking mounting in 2.6.27
> Submitter : Herton Ronaldo Krzesinski <herton-4qZELD6Fgxg39yzSjRtAkw@public.gmane.org>
> Date : 2008-09-12 16:56 (1 days old)
> References : http://marc.info/?l=linux-kernel&m=122123862519434&w=4
>
Fixed now with commit 8d99f83b9478768d3a8d7d1bcd9bd182c75a0447
--
[]'s
Herton
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221306287.5213.111.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-13 11:57 ` Mike Galbraith
@ 2008-09-14 6:24 ` Mike Galbraith
[not found] ` <1221373494.4979.1.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-14 14:18 ` Christoph Lameter
2 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-14 6:24 UTC (permalink / raw)
To: Christoph Lameter
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Sat, 2008-09-13 at 13:44 +0200, Mike Galbraith wrote:
> 2.6.27-rc6
> Throughput 1037.98 MB/sec 4 procs
>
> 16384 87380 1 1 60.00 80293.80
> 16384 87380 1 1 60.00 80266.60
> 16384 87380 1 1 60.00 80394.83
> 16384 87380 1 1 60.01 80397.27
<snip... sigh>
goes back to current real .27 config
Throughput 1022.52 MB/sec 4 procs
16384 87380 1 1 60.00 75941.95
16384 87380 1 1 60.01 76002.46
16384 87380 1 1 60.01 76367.55
16384 87380 1 1 60.00 76188.66
...
demodularizes seriously over-configured network
Throughput 750.175 MB/sec 4 procs
16384 87380 1 1 60.00 49270.35
16384 87380 1 1 60.01 49233.86
16384 87380 1 1 60.00 49265.72
16384 87380 1 1 60.00 49227.00
Very un-good thing to try. Stupid thing too?
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221373494.4979.1.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-14 7:02 ` Mike Galbraith
0 siblings, 0 replies; 126+ messages in thread
From: Mike Galbraith @ 2008-09-14 7:02 UTC (permalink / raw)
To: Christoph Lameter
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Sun, 2008-09-14 at 08:24 +0200, Mike Galbraith wrote:
> On Sat, 2008-09-13 at 13:44 +0200, Mike Galbraith wrote:
>
> > 2.6.27-rc6
> > Throughput 1037.98 MB/sec 4 procs
> >
> > 16384 87380 1 1 60.00 80293.80
> > 16384 87380 1 1 60.00 80266.60
> > 16384 87380 1 1 60.00 80394.83
> > 16384 87380 1 1 60.01 80397.27
>
> <snip... sigh>
>
> goes back to current real .27 config
>
> Throughput 1022.52 MB/sec 4 procs
>
> 16384 87380 1 1 60.00 75941.95
> 16384 87380 1 1 60.01 76002.46
> 16384 87380 1 1 60.01 76367.55
> 16384 87380 1 1 60.00 76188.66
>
> ...
>
> demodularizes seriously over-configured network
>
> Throughput 750.175 MB/sec 4 procs
>
> 16384 87380 1 1 60.00 49270.35
> 16384 87380 1 1 60.01 49233.86
> 16384 87380 1 1 60.00 49265.72
> 16384 87380 1 1 60.00 49227.00
>
> Very un-good thing to try. Stupid thing too?
Apparently stupid for netfilter. Uninteresting to this thread I
suppose, so disregard.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11557] Controlling backlight on thinkpad x60
[not found] ` <20080913151330.GA20761-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
@ 2008-09-14 10:18 ` Pavel Machek
0 siblings, 0 replies; 126+ messages in thread
From: Pavel Machek @ 2008-09-14 10:18 UTC (permalink / raw)
To: Matthew Garrett
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Sat 2008-09-13 16:13:30, Matthew Garrett wrote:
> I don't think this is a regression. The correct way to drive this
> hardware has always been through the ACPI video driver. The fact that
> thinkpad-acpi would also attempt to drive it was a bug.
I'm pretty sure thinkpad-acpi is older then ACPI-video. So yes, I
believe this is a regression, but it may be pretty old one.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221306287.5213.111.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-13 11:57 ` Mike Galbraith
2008-09-14 6:24 ` Mike Galbraith
@ 2008-09-14 14:18 ` Christoph Lameter
[not found] ` <48CD1D25.9080301-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2 siblings, 1 reply; 126+ messages in thread
From: Christoph Lameter @ 2008-09-14 14:18 UTC (permalink / raw)
To: Mike Galbraith
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
Mike Galbraith wrote:
> Numbers from my Q6600 Aldi supermarket box (hm, your box is from different shelf)
>
My box is an 8p with recent quad core processors. 8G, 32bit Linux.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <48CD1D25.9080301-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
@ 2008-09-14 19:51 ` Mike Galbraith
[not found] ` <1221421907.4597.24.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-14 19:51 UTC (permalink / raw)
To: Christoph Lameter
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Sun, 2008-09-14 at 09:18 -0500, Christoph Lameter wrote:
> Mike Galbraith wrote:
> > Numbers from my Q6600 Aldi supermarket box (hm, your box is from different shelf)
> >
> My box is an 8p with recent quad core processors. 8G, 32bit Linux.
Don't hold your breath, but after putting my network config of a very
severe diet, I'm starting to see something resembling sensible results.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[not found] ` <s5habecm03s.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
@ 2008-09-15 0:13 ` Rafael J. Wysocki
0 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-15 0:13 UTC (permalink / raw)
To: Takashi Iwai; +Cc: Frans Pop, Linux Kernel Mailing List, Kernel Testers List
On Saturday, 13 of September 2008, Takashi Iwai wrote:
> At Sat, 13 Sep 2008 09:37:51 +0200,
> Frans Pop wrote:
> >
> > On Friday 12 September 2008, Rafael J. Wysocki wrote:
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.26. Please verify if it still should be listed and let me
> > > know (either way).
> > >
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11398
> > > Subject : hda_intel: IRQ timing workaround is activated for card #0.
> > > Suggest a bigger bdl_pos_adj.
> >
> > Still there.
>
> Yeah, the driver wasn't changed about this.
>
> Basically it's a warning message that CPU usage got higher due to
> somehow wrongly behaving hardware. The driver behavior itself didn't
> do anything wrong. That is, if the driver didn't show it, you
> wouldn't have noticed any change (or noticed improvements in some apps
> :)
>
> Of course, it would be ideal if we can add a perfect workaround for
> it, but right now, I have no idea what to do better. So, I don't
> think it's worth to keeping this open as a regression.
I've closed the bug.
Thanks,
Rafael
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <20080913123722.e238ae2a.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
@ 2008-09-15 0:16 ` Rafael J. Wysocki
2008-09-15 13:05 ` Stephen Smalley
1 sibling, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-15 0:16 UTC (permalink / raw)
To: Andrew Morton
Cc: James Morris, linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA, sds-+05T5uksL2qpZYMLLGbcSA
On Saturday, 13 of September 2008, Andrew Morton wrote:
> On Sat, 13 Sep 2008 10:15:43 +1000 (EST) James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org> wrote:
>
> > On Fri, 12 Sep 2008, Andrew Morton wrote:
> >
> > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> > > > > Subject : /proc/net bug related to selinux
> > > > > Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > > > > Date : 2008-09-04 17:45 (9 days old)
> > > > > References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
> > > >
> > > > I think this might be a regression caused by namespace changes which we
> >
> > By which I mean, this was caused by a non-SELinux change to the upstream
> > kernel many, many eons ago.
>
> hm, seems that 2.6.24 is OK but 2.6.25 is not. I must have missed the
> bug when testing 2.6.25-based kernels.
>
> I started a git bisection search but after half an hour I hit bad
> bisection breakage: a complete machine hang in fib_rules_init().
>
> > > > addressed in SELinux policy. Which distro version & policy version is
> > > > this seen with?
> > > >
> > >
> > > FC5 on x86_32 and FC6 on x86_64.
> >
> > As mentioned in the bugzilla, any related avc messages would be useful.
>
> 2.6.25 dmesg: http://userweb.kernel.org/~akpm/dmesg-sony.txt
> /var/log/messages: http://userweb.kernel.org/~akpm/messages-sony.txt
>
> The latter includes this:
>
> Sep 13 12:32:43 sony kernel: SELinux: class key not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class dccp_socket not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class memprotect not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class peer not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class capability2 not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class dir not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class chr_file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class blk_file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class fifo_file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission recvfrom in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission sendto in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class netif not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class netif not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission ingress in class netif not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission egress in class netif not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission setkeycreate in class process not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission setsockcreate in class process not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission setfcap in class capability not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission polmatch in class association not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission flow_in in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission flow_out in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission forward_in in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission forward_out in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: the above unknown classes and permissions will be denied
> Sep 13 12:32:44 sony kernel: type=1403 audit(1221309118.644:3): policy loaded auid=4294967295 ses=4294967295
> Sep 13 12:32:44 sony kernel: type=1400 audit(1221334321.726:4): avc: denied { audit_write } for pid=400 comm="hwclock" capability=29 scontext=system_u:system_r:hwclock_t:s0 tcontext=system_u:system_r:hwclock_t:s0 tclass=capability
>
>
> Why am I seeing this on two machines and two vanilla-installed distros
> but nobody else is reporting it?
Well, it seems no one else is testing selinux ...
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11554] Partition check considered as error is breaking mounting in 2.6.27
[not found] ` <200809132037.55922.herton-4qZELD6Fgxg39yzSjRtAkw@public.gmane.org>
@ 2008-09-15 0:25 ` Rafael J. Wysocki
0 siblings, 0 replies; 126+ messages in thread
From: Rafael J. Wysocki @ 2008-09-15 0:25 UTC (permalink / raw)
To: Herton Ronaldo Krzesinski
Cc: Linux Kernel Mailing List, Kernel Testers List, Abdel Benamrouche,
Andrew Morton, Linus Torvalds
On Sunday, 14 of September 2008, Herton Ronaldo Krzesinski wrote:
> On Friday 12 September 2008 16:06:31 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.26. Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11554
> > Subject : Partition check considered as error is breaking mounting in 2.6.27
> > Submitter : Herton Ronaldo Krzesinski <herton-4qZELD6Fgxg39yzSjRtAkw@public.gmane.org>
> > Date : 2008-09-12 16:56 (1 days old)
> > References : http://marc.info/?l=linux-kernel&m=122123862519434&w=4
> >
>
> Fixed now with commit 8d99f83b9478768d3a8d7d1bcd9bd182c75a0447
Thanks, closed.
Rafael
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221421907.4597.24.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-15 10:44 ` Mike Galbraith
[not found] ` <1221475440.4784.39.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-15 10:44 UTC (permalink / raw)
To: Christoph Lameter
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Sun, 2008-09-14 at 21:51 +0200, Mike Galbraith wrote:
> On Sun, 2008-09-14 at 09:18 -0500, Christoph Lameter wrote:
> > Mike Galbraith wrote:
> > > Numbers from my Q6600 Aldi supermarket box (hm, your box is from different shelf)
> > >
> > My box is an 8p with recent quad core processors. 8G, 32bit Linux.
>
> Don't hold your breath, but after putting my network config of a very
> severe diet, I'm starting to see something resembling sensible results.
Turns off all netfilter options except tables, etc.
Since 2.6.22.19-cfs-v24.1 and 2.6.23.17-cfs-v24.1 schedulers are
identical, and these are essentially identical with 2.6.24.7, what I
read from numbers below is that cfs in 2.6.23 was somewhat less than
wonderful for either netperf or tbench, Something happened somewhere
other than the scheduler at 23->24 which cost us some performance, and
another something happened at 26->27. I'll likely go looking again..
and likely regret it again ;-)
Math ain't free is part of it, though apparently not much. For me,
tbench regression 22->27 is ~10%, and netperf regression is ~16%.
Data:
2.6.22.19
Throughput 1250.73 MB/sec 4 procs 1.00
16384 87380 1 1 60.01 111272.55 1.00
16384 87380 1 1 60.00 104689.58
16384 87380 1 1 60.00 110733.05
16384 87380 1 1 60.00 110748.88
2.6.22.19-cfs-v24.1
Throughput 1204.14 MB/sec 4 procs .962
16384 87380 1 1 60.01 101799.85 .929
16384 87380 1 1 60.01 101659.41
16384 87380 1 1 60.01 101628.78
16384 87380 1 1 60.01 101700.53
wakeup granularity = 0 (make scheduler as preempt happy as 2.6.22 is)
Throughput 1213.21 MB/sec 4 procs .970
16384 87380 1 1 60.01 108569.27 .992
16384 87380 1 1 60.01 108541.04
16384 87380 1 1 60.00 108579.63
16384 87380 1 1 60.01 108519.09
2.6.23.17
Throughput 1192.49 MB/sec 4 procs .953
16384 87380 1 1 60.00 91124.67 .866
16384 87380 1 1 60.00 93124.38
16384 87380 1 1 60.01 92249.69
16384 87380 1 1 60.01 91103.12
wakeup granularity = 0
Throughput 1200.46 MB/sec 4 procs .959
16384 87380 1 1 60.01 95987.66 .866
16384 87380 1 1 60.01 92819.98
16384 87380 1 1 60.01 95454.00
16384 87380 1 1 60.01 94834.84
2.6.23.17-cfs-v24.1
Throughput 1242.47 MB/sec 4 procs .993
16384 87380 1 1 60.00 101728.34 .931
16384 87380 1 1 60.00 101930.23
16384 87380 1 1 60.00 101803.15
16384 87380 1 1 60.00 101908.29
wakeup granularity = 0
Throughput 1238.68 MB/sec 4 procs .990
16384 87380 1 1 60.01 105871.52 .969
16384 87380 1 1 60.01 105813.11
16384 87380 1 1 60.01 106106.31
16384 87380 1 1 60.01 106310.20
2.6.24.7
Throughput 1202.49 MB/sec 4 procs .961
16384 87380 1 1 60.00 94643.23 .868
16384 87380 1 1 60.00 94754.37
16384 87380 1 1 60.00 94909.77
16384 87380 1 1 60.00 95457.41
wakeup granularity = 0
Throughput 1204 MB/sec 4 procs .962
16384 87380 1 1 60.00 99599.27 .910
16384 87380 1 1 60.00 99439.95
16384 87380 1 1 60.00 99556.38
16384 87380 1 1 60.00 99500.45
2.6.25.17
Throughput 1220.47 MB/sec 4 procs .975
16384 87380 1 1 60.00 94641.06 .867
16384 87380 1 1 60.00 94864.87
16384 87380 1 1 60.01 95033.81
16384 87380 1 1 60.00 94863.49
wakeup granularity = 0
Throughput 1223.16 MB/sec 4 procs .977
16384 87380 1 1 60.00 101768.95 .930
16384 87380 1 1 60.00 101888.46
16384 87380 1 1 60.01 101608.21
16384 87380 1 1 60.01 101833.05
2.6.26.5
Throughput 1182.24 MB/sec 4 procs .945
16384 87380 1 1 60.00 93814.75 .854
16384 87380 1 1 60.00 94173.41
16384 87380 1 1 60.00 92925.24
16384 87380 1 1 60.00 93002.51
wakeup granularity = 0
Throughput 1183.47 MB/sec 4 procs .945
16384 87380 1 1 60.00 100837.12 .922
16384 87380 1 1 60.00 101230.12
16384 87380 1 1 60.00 100868.45
16384 87380 1 1 60.00 100491.41
2.6.27
Throughput 1088.17 MB/sec 4 procs .870
16384 87380 1 1 60.00 84225.59 .766
16384 87380 1 1 60.00 83362.65
16384 87380 1 1 60.00 84060.73
16384 87380 1 1 60.00 83462.72
wakeup granularity = 0
Throughput 1116.22 MB/sec 4 procs .892
16384 87380 1 1 60.00 92502.44 .841
16384 87380 1 1 60.01 92213.72
16384 87380 1 1 60.00 91445.86
16384 87380 1 1 60.00 91832.84
revert sched weight/asym changes, gran = 0
Throughput 1149.16 MB/sec 4 proc .918
16384 87380 1 1 60.00 94824.92 .868
16384 87380 1 1 60.01 94579.45
16384 87380 1 1 60.01 95284.94
16384 87380 1 1 60.01 95228.22
Weight/asym changes cost ~3%. Mysql+oltp agrees. Preempt happy loads
lose a bit, preempt haters gain a bit. Performance shift.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <20080913123722.e238ae2a.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-15 0:16 ` Rafael J. Wysocki
@ 2008-09-15 13:05 ` Stephen Smalley
[not found] ` <1221483926.30816.18.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
1 sibling, 1 reply; 126+ messages in thread
From: Stephen Smalley @ 2008-09-15 13:05 UTC (permalink / raw)
To: Andrew Morton
Cc: James Morris, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Sat, 2008-09-13 at 12:37 -0700, Andrew Morton wrote:
> On Sat, 13 Sep 2008 10:15:43 +1000 (EST) James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org> wrote:
>
> > On Fri, 12 Sep 2008, Andrew Morton wrote:
> >
> > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> > > > > Subject : /proc/net bug related to selinux
> > > > > Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > > > > Date : 2008-09-04 17:45 (9 days old)
> > > > > References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
> > > >
> > > > I think this might be a regression caused by namespace changes which we
> >
> > By which I mean, this was caused by a non-SELinux change to the upstream
> > kernel many, many eons ago.
>
> hm, seems that 2.6.24 is OK but 2.6.25 is not. I must have missed the
> bug when testing 2.6.25-based kernels.
>
> I started a git bisection search but after half an hour I hit bad
> bisection breakage: a complete machine hang in fib_rules_init().
>
> > > > addressed in SELinux policy. Which distro version & policy version is
> > > > this seen with?
> > > >
> > >
> > > FC5 on x86_32 and FC6 on x86_64.
> >
> > As mentioned in the bugzilla, any related avc messages would be useful.
>
> 2.6.25 dmesg: http://userweb.kernel.org/~akpm/dmesg-sony.txt
> /var/log/messages: http://userweb.kernel.org/~akpm/messages-sony.txt
>
> The latter includes this:
>
> Sep 13 12:32:43 sony kernel: SELinux: class key not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class dccp_socket not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class memprotect not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class peer not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: class capability2 not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class dir not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class chr_file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class blk_file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission open in class fifo_file not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission recvfrom in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission sendto in class node not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class netif not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class netif not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission ingress in class netif not defined in policy
> Sep 13 12:32:43 sony kernel: SELinux: permission egress in class netif not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission setkeycreate in class process not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission setsockcreate in class process not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission setfcap in class capability not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission polmatch in class association not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission flow_in in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission flow_out in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission forward_in in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: permission forward_out in class packet not defined in policy
> Sep 13 12:32:44 sony kernel: SELinux: the above unknown classes and permissions will be denied
> Sep 13 12:32:44 sony kernel: type=1403 audit(1221309118.644:3): policy loaded auid=4294967295 ses=4294967295
> Sep 13 12:32:44 sony kernel: type=1400 audit(1221334321.726:4): avc: denied { audit_write } for pid=400 comm="hwclock" capability=29 scontext=system_u:system_r:hwclock_t:s0 tcontext=system_u:system_r:hwclock_t:s0 tclass=capability
>
>
> Why am I seeing this on two machines and two vanilla-installed distros
> but nobody else is reporting it?
What we actually need to see is the output of:
/sbin/ausearch -i -m AVC -sv no
However, the most likely explanation is simply that when /proc/net was
changed from being a directory to being a symlink to /proc/self/net,
that introduced an additional permission check on accesses
of /proc/net/<whatever>, namely the read check on the symlink itself.
And since that check wasn't happening on /proc/net accesses with older
kernels, older policies didn't allow it.
As to why others haven't reported it, I expect that they have updated
their policies to newer ones that allow the necessary access. The fact
that legacy distros wouldn't have such updated policies isn't surprising
- they don't push updates to those distros for new kernels. FC5 and FC6
are both EOL'd, right?
In any event, we didn't change anything in SELinux - the change was
elsewhere (in the proc/net implementation). Don't blame the messenger
please.
--
Stephen Smalley
National Security Agency
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <1221483926.30816.18.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
@ 2008-09-15 13:42 ` Stephen Smalley
2008-09-17 19:50 ` Andrew Morton
1 sibling, 0 replies; 126+ messages in thread
From: Stephen Smalley @ 2008-09-15 13:42 UTC (permalink / raw)
To: Andrew Morton
Cc: James Morris, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Mon, 2008-09-15 at 09:05 -0400, Stephen Smalley wrote:
> On Sat, 2008-09-13 at 12:37 -0700, Andrew Morton wrote:
> > On Sat, 13 Sep 2008 10:15:43 +1000 (EST) James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org> wrote:
> >
> > > On Fri, 12 Sep 2008, Andrew Morton wrote:
> > >
> > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> > > > > > Subject : /proc/net bug related to selinux
> > > > > > Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > > > > > Date : 2008-09-04 17:45 (9 days old)
> > > > > > References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
> > > > >
> > > > > I think this might be a regression caused by namespace changes which we
> > >
> > > By which I mean, this was caused by a non-SELinux change to the upstream
> > > kernel many, many eons ago.
> >
> > hm, seems that 2.6.24 is OK but 2.6.25 is not. I must have missed the
> > bug when testing 2.6.25-based kernels.
> >
> > I started a git bisection search but after half an hour I hit bad
> > bisection breakage: a complete machine hang in fib_rules_init().
> >
> > > > > addressed in SELinux policy. Which distro version & policy version is
> > > > > this seen with?
> > > > >
> > > >
> > > > FC5 on x86_32 and FC6 on x86_64.
> > >
> > > As mentioned in the bugzilla, any related avc messages would be useful.
> >
> > 2.6.25 dmesg: http://userweb.kernel.org/~akpm/dmesg-sony.txt
> > /var/log/messages: http://userweb.kernel.org/~akpm/messages-sony.txt
> >
> > The latter includes this:
> >
> > Sep 13 12:32:43 sony kernel: SELinux: class key not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class dccp_socket not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class memprotect not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class peer not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class capability2 not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class dir not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class chr_file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class blk_file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class fifo_file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission recvfrom in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission sendto in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class netif not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class netif not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission ingress in class netif not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission egress in class netif not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission setkeycreate in class process not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission setsockcreate in class process not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission setfcap in class capability not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission polmatch in class association not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission flow_in in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission flow_out in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission forward_in in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission forward_out in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: the above unknown classes and permissions will be denied
> > Sep 13 12:32:44 sony kernel: type=1403 audit(1221309118.644:3): policy loaded auid=4294967295 ses=4294967295
> > Sep 13 12:32:44 sony kernel: type=1400 audit(1221334321.726:4): avc: denied { audit_write } for pid=400 comm="hwclock" capability=29 scontext=system_u:system_r:hwclock_t:s0 tcontext=system_u:system_r:hwclock_t:s0 tclass=capability
> >
> >
> > Why am I seeing this on two machines and two vanilla-installed distros
> > but nobody else is reporting it?
>
> What we actually need to see is the output of:
> /sbin/ausearch -i -m AVC -sv no
>
> However, the most likely explanation is simply that when /proc/net was
> changed from being a directory to being a symlink to /proc/self/net,
> that introduced an additional permission check on accesses
> of /proc/net/<whatever>, namely the read check on the symlink itself.
> And since that check wasn't happening on /proc/net accesses with older
> kernels, older policies didn't allow it.
>
> As to why others haven't reported it, I expect that they have updated
> their policies to newer ones that allow the necessary access. The fact
> that legacy distros wouldn't have such updated policies isn't surprising
> - they don't push updates to those distros for new kernels. FC5 and FC6
> are both EOL'd, right?
>
> In any event, we didn't change anything in SELinux - the change was
> elsewhere (in the proc/net implementation). Don't blame the messenger
> please.
BTW, if the explanation above is correct, then a user can allow this
permission in their own policy by creating a local policy module and
inserting it, ala:
$ cat fixprocnet.te
policy_module(fixprocnet, 1.0)
require {
attribute domain;
type proc_net_t;
}
# Allow all domains to read the /proc/net symlink.
allow domain proc_net_t:lnk_file read;
$ make -f /usr/share/selinux/devel/Makefile fixprocnet.pp
$ /usr/sbin/semodule -i fixprocnet.pp
Requires selinux-policy-devel to be installed.
--
Stephen Smalley
National Security Agency
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11471] GPE storm detected, kernel freezes
2008-09-12 19:06 ` [Bug #11471] GPE storm detected, kernel freezes Rafael J. Wysocki
@ 2008-09-16 5:50 ` Zhang Rui
0 siblings, 0 replies; 126+ messages in thread
From: Zhang Rui @ 2008-09-16 5:50 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, George Gibbs
On Sat, 2008-09-13 at 03:06 +0800, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me
> know
> (either way).
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11471
> Subject : GPE storm detected, kernel freezes
> Submitter : George Gibbs <Vash63-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date : 2008-08-31 22:00 (13 days old)
> Handled-By : Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
this has already been fixed in -rc6.
please refer to http://bugzilla.kernel.org/show_bug.cgi?id=11471#c22
so I think this should be removed from the list.
thanks,
rui
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221475440.4784.39.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-16 12:28 ` Mike Galbraith
[not found] ` <1221568105.5020.17.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-16 12:28 UTC (permalink / raw)
To: Christoph Lameter
Cc: Rafael J. Wysocki, Linux Kernel Mailing List, Kernel Testers List
On Mon, 2008-09-15 at 12:44 +0200, Mike Galbraith wrote:
> On Sun, 2008-09-14 at 21:51 +0200, Mike Galbraith wrote:
> > On Sun, 2008-09-14 at 09:18 -0500, Christoph Lameter wrote:
> > > Mike Galbraith wrote:
> > > > Numbers from my Q6600 Aldi supermarket box (hm, your box is from different shelf)
> > > >
> > > My box is an 8p with recent quad core processors. 8G, 32bit Linux.
> >
> > Don't hold your breath, but after putting my network config of a very
> > severe diet, I'm starting to see something resembling sensible results.
>
> Turns off all netfilter options except tables, etc.
>
> Since 2.6.22.19-cfs-v24.1 and 2.6.23.17-cfs-v24.1 schedulers are
> identical, and these are essentially identical with 2.6.24.7, what I
> read from numbers below is that cfs in 2.6.23 was somewhat less than
> wonderful for either netperf or tbench, Something happened somewhere
> other than the scheduler at 23->24 which cost us some performance, and
> another something happened at 26->27. I'll likely go looking again..
> and likely regret it again ;-)
Bisecting 26->27 yet again turned up a repeatable downturn in netperf
throughput. There is no difference at this point with tbench.
Bisect says first bad commit is 847106f, a security merge. Post
bisection sanity checkouts say...
v2.6.26-21-g2069f45
16384 87380 1 1 60.00 98435.13
16384 87380 1 1 60.01 99259.90
16384 87380 1 1 60.01 99325.61
16384 87380 1 1 60.00 99039.84
v2.6.26-343-g847106f
16384 87380 1 1 60.00 94764.59
16384 87380 1 1 60.00 94909.89
16384 87380 1 1 60.00 94858.63
16384 87380 1 1 60.00 94801.12
...every time. I knew I'd regret doing this.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221568105.5020.17.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-16 14:07 ` Ilpo Järvinen
2008-09-17 4:39 ` Mike Galbraith
0 siblings, 1 reply; 126+ messages in thread
From: Ilpo Järvinen @ 2008-09-16 14:07 UTC (permalink / raw)
To: Mike Galbraith
Cc: Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Tue, 16 Sep 2008, Mike Galbraith wrote:
> On Mon, 2008-09-15 at 12:44 +0200, Mike Galbraith wrote:
> > On Sun, 2008-09-14 at 21:51 +0200, Mike Galbraith wrote:
> >
> > Since 2.6.22.19-cfs-v24.1 and 2.6.23.17-cfs-v24.1 schedulers are
> > identical, and these are essentially identical with 2.6.24.7, what I
> > read from numbers below is that cfs in 2.6.23 was somewhat less than
> > wonderful for either netperf or tbench, Something happened somewhere
> > other than the scheduler at 23->24 which cost us some performance, and
> > another something happened at 26->27. I'll likely go looking again..
> > and likely regret it again ;-)
>
> Bisecting 26->27 yet again turned up a repeatable downturn in netperf
> throughput. There is no difference at this point with tbench.
>
> Bisect says first bad commit is 847106f, a security merge. Post
> bisection sanity checkouts say...
>
> v2.6.26-21-g2069f45
> 16384 87380 1 1 60.00 98435.13
> 16384 87380 1 1 60.01 99259.90
> 16384 87380 1 1 60.01 99325.61
> 16384 87380 1 1 60.00 99039.84
>
> v2.6.26-343-g847106f
> 16384 87380 1 1 60.00 94764.59
> 16384 87380 1 1 60.00 94909.89
> 16384 87380 1 1 60.00 94858.63
> 16384 87380 1 1 60.00 94801.12
>
> ...every time. I knew I'd regret doing this.
I assume that c142bda458a gave a good results as well...
One additional sanity check could be to rebase security 6f0f0fd4963 on top
of the c142bda458a and then see if bisection among those security commits
on top yields to the the same result... Though I doubt it can change much
because there was not that much relevant non-security things in the merge
in question.
--
i.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11272] BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835
2008-09-12 19:06 ` [Bug #11272] BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835 Rafael J. Wysocki
@ 2008-09-16 15:25 ` Jaswinder Singh
0 siblings, 0 replies; 126+ messages in thread
From: Jaswinder Singh @ 2008-09-16 15:25 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, linux-serial
Hello all,
I am sorry for delay.
On Sat, Sep 13, 2008 at 12:36 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11272
> Subject : BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835
> Submitter : Jaswinder Singh <jaswinderlinux@gmail.com>
> Date : 2008-08-05 15:12 (39 days old)
> References : http://marc.info/?l=linux-kernel&m=121794900319776&w=4
>
I have tested parport_pc and also tried with pcmcia_cs, only thing I
get is disappointment. So I give up :-(
Now I switched to usbserial.
usbserial drivers are working great !!
Now I do not want to use parport_pc and pcmcia_cs atleast for 2 years,
I hope in 2 years this will be solved ;)
In the mean time, If you think my problem is solved just ping to me I
will test and let you know the results.
Thank you for all your support and help.
Jaswinder Singh.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
2008-09-16 14:07 ` Ilpo Järvinen
@ 2008-09-17 4:39 ` Mike Galbraith
2008-09-17 5:01 ` Mike Galbraith
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-17 4:39 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Christoph Lameter, Rafael J. Wysocki, LKML, kernel-testers
On Tue, 2008-09-16 at 17:07 +0300, Ilpo Järvinen wrote:
> On Tue, 16 Sep 2008, Mike Galbraith wrote:
>
> > On Mon, 2008-09-15 at 12:44 +0200, Mike Galbraith wrote:
> > > On Sun, 2008-09-14 at 21:51 +0200, Mike Galbraith wrote:
> > >
> > > Since 2.6.22.19-cfs-v24.1 and 2.6.23.17-cfs-v24.1 schedulers are
> > > identical, and these are essentially identical with 2.6.24.7, what I
> > > read from numbers below is that cfs in 2.6.23 was somewhat less than
> > > wonderful for either netperf or tbench, Something happened somewhere
> > > other than the scheduler at 23->24 which cost us some performance, and
> > > another something happened at 26->27. I'll likely go looking again..
> > > and likely regret it again ;-)
> >
> > Bisecting 26->27 yet again turned up a repeatable downturn in netperf
> > throughput. There is no difference at this point with tbench.
> >
> > Bisect says first bad commit is 847106f, a security merge. Post
> > bisection sanity checkouts say...
> >
> > v2.6.26-21-g2069f45
> > 16384 87380 1 1 60.00 98435.13
> > 16384 87380 1 1 60.01 99259.90
> > 16384 87380 1 1 60.01 99325.61
> > 16384 87380 1 1 60.00 99039.84
> >
> > v2.6.26-343-g847106f
> > 16384 87380 1 1 60.00 94764.59
> > 16384 87380 1 1 60.00 94909.89
> > 16384 87380 1 1 60.00 94858.63
> > 16384 87380 1 1 60.00 94801.12
> >
> > ...every time. I knew I'd regret doing this.
>
> I assume that c142bda458a gave a good results as well...
Yes, just tried it.
> One additional sanity check could be to rebase security 6f0f0fd4963 on top
> of the c142bda458a and then see if bisection among those security commits
> on top yields to the the same result... Though I doubt it can change much
> because there was not that much relevant non-security things in the merge
> in question.
I'm not a master of git-foo, so that is not an option. However, a dinky
bisection c142bda4..847106f very clearly says...
marge:..kernel/linux-2.6.27.git # git bisect bad
6f0f0fd496333777d53daff21a4e3b28c4d03a6d is first bad commit
commit 6f0f0fd496333777d53daff21a4e3b28c4d03a6d
Author: James Morris <jmorris@namei.org>
Date: Thu Jul 10 17:02:07 2008 +0900
security: remove register_security hook
The register security hook is no longer required, as the capability
module is always registered. LSMs wishing to stack capability as
a secondary module should do so explicitly.
Signed-off-by: James Morris <jmorris@namei.org>
Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
:040000 040000 0177ef46d305e51e27bfcc4350a40577f8ba8d3d 64b64c10a424df4539653a8ee34f1a2329300931 M include
:040000 040000 e318891e514de674fd064f6bfad70d5633b1aff1 0dbb38d5aa7fc3e4b2e09dc65796ce7cd5faeb26 M security
git bisect start
# good: [c142bda458a9c81097238800e1bd8eeeea09913d] Merge branch 'drm-reorg' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6
git bisect good c142bda458a9c81097238800e1bd8eeeea09913d
# bad: [847106ff628805e1a0aa91e7f53381f3fdfcd839] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6
git bisect bad 847106ff628805e1a0aa91e7f53381f3fdfcd839
# good: [cea78dc4ca044e9666e8f5d797ec50ab85253e49] SELinux: fix off by 1 reference of class_to_string in context_struct_compute_av
git bisect good cea78dc4ca044e9666e8f5d797ec50ab85253e49
# good: [65fc7668006b537f7ae8451990c0ed9ec882544e] security: fix return of void-valued expressions
git bisect good 65fc7668006b537f7ae8451990c0ed9ec882544e
# good: [b478a9f9889c81e88077d1495daadee64c0af541] security: remove unused sb_get_mnt_opts hook
git bisect good b478a9f9889c81e88077d1495daadee64c0af541
# good: [93cbace7a058bce7f99319ef6ceff4b78cf45051] security: remove dummy module fix
git bisect good 93cbace7a058bce7f99319ef6ceff4b78cf45051
# bad: [6f0f0fd496333777d53daff21a4e3b28c4d03a6d] security: remove register_security hook
git bisect bad 6f0f0fd496333777d53daff21a4e3b28c4d03a6d
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
2008-09-17 4:39 ` Mike Galbraith
@ 2008-09-17 5:01 ` Mike Galbraith
[not found] ` <1221627676.5125.3.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-17 5:01 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Christoph Lameter, Rafael J. Wysocki, LKML, kernel-testers
On Wed, 2008-09-17 at 06:40 +0200, Mike Galbraith wrote:
> On Tue, 2008-09-16 at 17:07 +0300, Ilpo Järvinen wrote:
> > One additional sanity check could be to rebase security 6f0f0fd4963 on top
> > of the c142bda458a and then see if bisection among those security commits
> > on top yields to the the same result... Though I doubt it can change much
> > because there was not that much relevant non-security things in the merge
> > in question.
>
> I'm not a master of git-foo, so that is not an option. However, a dinky
> bisection c142bda4..847106f very clearly says...
>
> marge:..kernel/linux-2.6.27.git # git bisect bad
> 6f0f0fd496333777d53daff21a4e3b28c4d03a6d is first bad commit
> commit 6f0f0fd496333777d53daff21a4e3b28c4d03a6d
> Author: James Morris <jmorris@namei.org>
> Date: Thu Jul 10 17:02:07 2008 +0900
>
> security: remove register_security hook
>
> The register security hook is no longer required, as the capability
> module is always registered. LSMs wishing to stack capability as
> a secondary module should do so explicitly.
>
> Signed-off-by: James Morris <jmorris@namei.org>
> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> :040000 040000 0177ef46d305e51e27bfcc4350a40577f8ba8d3d 64b64c10a424df4539653a8ee34f1a2329300931 M include
> :040000 040000 e318891e514de674fd064f6bfad70d5633b1aff1 0dbb38d5aa7fc3e4b2e09dc65796ce7cd5faeb26 M security
Which is high grade horse-pookey.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221627676.5125.3.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-17 10:40 ` Ingo Molnar
[not found] ` <20080917104044.GC18764-X9Un+BFzKDI@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Ingo Molnar @ 2008-09-17 10:40 UTC (permalink / raw)
To: Mike Galbraith
Cc: Ilpo Järvinen, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
* Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org> wrote:
> On Wed, 2008-09-17 at 06:40 +0200, Mike Galbraith wrote:
> > On Tue, 2008-09-16 at 17:07 +0300, Ilpo Järvinen wrote:
>
> > > One additional sanity check could be to rebase security 6f0f0fd4963 on top
> > > of the c142bda458a and then see if bisection among those security commits
> > > on top yields to the the same result... Though I doubt it can change much
> > > because there was not that much relevant non-security things in the merge
> > > in question.
> >
> > I'm not a master of git-foo, so that is not an option. However, a dinky
> > bisection c142bda4..847106f very clearly says...
> >
> > marge:..kernel/linux-2.6.27.git # git bisect bad
> > 6f0f0fd496333777d53daff21a4e3b28c4d03a6d is first bad commit
> > commit 6f0f0fd496333777d53daff21a4e3b28c4d03a6d
> > Author: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
> > Date: Thu Jul 10 17:02:07 2008 +0900
> >
> > security: remove register_security hook
> >
> > The register security hook is no longer required, as the capability
> > module is always registered. LSMs wishing to stack capability as
> > a secondary module should do so explicitly.
> >
> > Signed-off-by: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
> > Acked-by: Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
> > Acked-by: Greg Kroah-Hartman <gregkh-l3A5Bk7waGM@public.gmane.org>
> >
> > :040000 040000 0177ef46d305e51e27bfcc4350a40577f8ba8d3d 64b64c10a424df4539653a8ee34f1a2329300931 M include
> > :040000 040000 e318891e514de674fd064f6bfad70d5633b1aff1 0dbb38d5aa7fc3e4b2e09dc65796ce7cd5faeb26 M security
>
> Which is high grade horse-pookey.
perhaps re-test commit 6f0f0fd49 and its parent commit, 93cbace7a0.
It looks like a potentially bogus bisection result, but _maybe_ it has
relevance: changes the size of "struct security_operations", which could
have alignment and layout effects on all sorts of kernel variables,
kmalloc sizes, etc.
Ingo
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <20080917104044.GC18764-X9Un+BFzKDI@public.gmane.org>
@ 2008-09-17 11:41 ` Mike Galbraith
[not found] ` <1221651701.5102.17.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-17 11:41 UTC (permalink / raw)
To: Ingo Molnar
Cc: Ilpo Järvinen, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Wed, 2008-09-17 at 12:40 +0200, Ingo Molnar wrote:
> * Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org> wrote:
>
> > On Wed, 2008-09-17 at 06:40 +0200, Mike Galbraith wrote:
> > > On Tue, 2008-09-16 at 17:07 +0300, Ilpo Järvinen wrote:
> >
> > > > One additional sanity check could be to rebase security 6f0f0fd4963 on top
> > > > of the c142bda458a and then see if bisection among those security commits
> > > > on top yields to the the same result... Though I doubt it can change much
> > > > because there was not that much relevant non-security things in the merge
> > > > in question.
> > >
> > > I'm not a master of git-foo, so that is not an option. However, a dinky
> > > bisection c142bda4..847106f very clearly says...
> > >
> > > marge:..kernel/linux-2.6.27.git # git bisect bad
> > > 6f0f0fd496333777d53daff21a4e3b28c4d03a6d is first bad commit
> > > commit 6f0f0fd496333777d53daff21a4e3b28c4d03a6d
> > > Author: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
> > > Date: Thu Jul 10 17:02:07 2008 +0900
> > >
> > > security: remove register_security hook
> > >
> > > The register security hook is no longer required, as the capability
> > > module is always registered. LSMs wishing to stack capability as
> > > a secondary module should do so explicitly.
> > >
> > > Signed-off-by: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
> > > Acked-by: Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
> > > Acked-by: Greg Kroah-Hartman <gregkh-l3A5Bk7waGM@public.gmane.org>
> > >
> > > :040000 040000 0177ef46d305e51e27bfcc4350a40577f8ba8d3d 64b64c10a424df4539653a8ee34f1a2329300931 M include
> > > :040000 040000 e318891e514de674fd064f6bfad70d5633b1aff1 0dbb38d5aa7fc3e4b2e09dc65796ce7cd5faeb26 M security
> >
> > Which is high grade horse-pookey.
>
> perhaps re-test commit 6f0f0fd49 and its parent commit, 93cbace7a0.
Will do.
> It looks like a potentially bogus bisection result, but _maybe_ it has
> relevance: changes the size of "struct security_operations", which could
> have alignment and layout effects on all sorts of kernel variables,
> kmalloc sizes, etc.
This may well be a mythical creature infestation for all I know ;-), but
it's address is somewhere in the 2069f45..847106f block, 316 commits,
none of which look like they should be the least bit interesting to
netperf. I reverted this particular commit in 27.git, got the expected
result. Looks like I'll keep poking at it, can't seem to resist. Grr.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221651701.5102.17.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-17 12:49 ` Ingo Molnar
[not found] ` <20080917124943.GA7738-X9Un+BFzKDI@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Ingo Molnar @ 2008-09-17 12:49 UTC (permalink / raw)
To: Mike Galbraith
Cc: Ilpo Järvinen, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
* Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org> wrote:
> > It looks like a potentially bogus bisection result, but _maybe_ it
> > has relevance: changes the size of "struct security_operations",
> > which could have alignment and layout effects on all sorts of kernel
> > variables, kmalloc sizes, etc.
>
> This may well be a mythical creature infestation for all I know ;-),
> but it's address is somewhere in the 2069f45..847106f block, 316
> commits, none of which look like they should be the least bit
> interesting to netperf. I reverted this particular commit in 27.git,
> got the expected result. Looks like I'll keep poking at it, can't
> seem to resist. Grr.
are you sure it's 2069f45..847106f? Filtering out the
likely-uninteresting commits:
git log --pretty=format:"%h: %s" 2069f45..847106f | grep -viE \
'block|alsa|pcmcia|sound|Merge|iosched|blk|DAC960|scsi|s390|paride|pktcdvd|filter|cdrom|drm'
gives us:
7daf705: Start using the new '%pS' infrastructure to print symbols
6f0f0fd: security: remove register_security hook
93cbace: security: remove dummy module fix
5915eb5: security: remove dummy module
b478a9f: security: remove unused sb_get_mnt_opts hook
32502b8: splice: fix generic_file_splice_read() race with page invalidation
8b3d356: ramfs: enable splice write
a144ff0: xen: Avoid allocations causing swap activity on the resume path
which really only leaves that security commit your bisection fingered.
Which _slightly_ raises its likelyhood of being implicated. Structure
size changes can move two formerly far-apart netperf-relevant symbols on
the same cacheline, which can start cache ping-pong-ing badly.
It wouldnt be the first such incident - alignment changes impacting
macro benchmarks. (and it's hard to find it as the thing that changes
alignment/size/sharedness might be something totally unrelated)
It's still a bit too early to say this for sure though ...
Ingo
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <20080917124943.GA7738-X9Un+BFzKDI@public.gmane.org>
@ 2008-09-17 13:11 ` Mike Galbraith
[not found] ` <1221657111.5511.14.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-17 13:11 UTC (permalink / raw)
To: Ingo Molnar
Cc: Ilpo Järvinen, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Wed, 2008-09-17 at 14:49 +0200, Ingo Molnar wrote:
> * Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org> wrote:
>
> > > It looks like a potentially bogus bisection result, but _maybe_ it
> > > has relevance: changes the size of "struct security_operations",
> > > which could have alignment and layout effects on all sorts of kernel
> > > variables, kmalloc sizes, etc.
> >
> > This may well be a mythical creature infestation for all I know ;-),
> > but it's address is somewhere in the 2069f45..847106f block, 316
> > commits, none of which look like they should be the least bit
> > interesting to netperf. I reverted this particular commit in 27.git,
> > got the expected result. Looks like I'll keep poking at it, can't
> > seem to resist. Grr.
>
> are you sure it's 2069f45..847106f? Filtering out the
> likely-uninteresting commits:
Yeah, as sure as I can be. I've built both (et al) kernels several
times, and it has repeated every time. Would be nice if someone would
try to confirm/deny though. For my little quad, I do..
#!/bin/sh
echo 0 > /proc/sys/kernel/sched_wakeup_granularity_ns
netserver -p 12865
netserver -p 12866
netserver -p 12867
netserver -p 12868
netperf -p 12865 -t TCP_RR -l 60 -H 127.0.0.1 -T 0,0 -- -r 1,1&
netperf -p 12866 -t TCP_RR -l 60 -H 127.0.0.1 -T 1,1 -- -r 1,1&
netperf -p 12867 -t TCP_RR -l 60 -H 127.0.0.1 -T 2,2 -- -r 1,1&
netperf -p 12868 -t TCP_RR -l 60 -H 127.0.0.1 -T 3,3 -- -r 1,1&
wait
killall netserver
> git log --pretty=format:"%h: %s" 2069f45..847106f | grep -viE \
> 'block|alsa|pcmcia|sound|Merge|iosched|blk|DAC960|scsi|s390|paride|pktcdvd|filter|cdrom|drm'
>
> gives us:
>
> 7daf705: Start using the new '%pS' infrastructure to print symbols
> 6f0f0fd: security: remove register_security hook
> 93cbace: security: remove dummy module fix
> 5915eb5: security: remove dummy module
> b478a9f: security: remove unused sb_get_mnt_opts hook
> 32502b8: splice: fix generic_file_splice_read() race with page invalidation
> 8b3d356: ramfs: enable splice write
> a144ff0: xen: Avoid allocations causing swap activity on the resume path
>
> which really only leaves that security commit your bisection fingered.
> Which _slightly_ raises its likelyhood of being implicated. Structure
> size changes can move two formerly far-apart netperf-relevant symbols on
> the same cacheline, which can start cache ping-pong-ing badly.
I sure hope it's something like ping-pong, it's driving me NUTS.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221657111.5511.14.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-17 13:36 ` Ilpo Järvinen
[not found] ` <Pine.LNX.4.64.0809171629550.1034-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2008-09-17 14:47 ` Eric Dumazet
1 sibling, 1 reply; 126+ messages in thread
From: Ilpo Järvinen @ 2008-09-17 13:36 UTC (permalink / raw)
To: Mike Galbraith
Cc: Ingo Molnar, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Wed, 17 Sep 2008, Mike Galbraith wrote:
> On Wed, 2008-09-17 at 14:49 +0200, Ingo Molnar wrote:
>
> > git log --pretty=format:"%h: %s" 2069f45..847106f | grep -viE \
> > 'block|alsa|pcmcia|sound|Merge|iosched|blk|DAC960|scsi|s390|paride|pktcdvd|filter|cdrom|drm'
> >
> > gives us:
> >
> > 7daf705: Start using the new '%pS' infrastructure to print symbols
> > 6f0f0fd: security: remove register_security hook
> > 93cbace: security: remove dummy module fix
> > 5915eb5: security: remove dummy module
> > b478a9f: security: remove unused sb_get_mnt_opts hook
> > 32502b8: splice: fix generic_file_splice_read() race with page invalidation
> > 8b3d356: ramfs: enable splice write
> > a144ff0: xen: Avoid allocations causing swap activity on the resume path
> >
> > which really only leaves that security commit your bisection fingered.
> > Which _slightly_ raises its likelyhood of being implicated. Structure
> > size changes can move two formerly far-apart netperf-relevant symbols on
> > the same cacheline, which can start cache ping-pong-ing badly.
>
> I sure hope it's something like ping-pong, it's driving me NUTS.
How about dividing the problem to smaller blocks then by restoring
parts of the change...
--
i.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <Pine.LNX.4.64.0809171629550.1034-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
@ 2008-09-17 13:57 ` Mike Galbraith
[not found] ` <1221659858.8818.13.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-17 13:57 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Ingo Molnar, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Wed, 2008-09-17 at 16:36 +0300, Ilpo Järvinen wrote:
> On Wed, 17 Sep 2008, Mike Galbraith wrote:
>
> > On Wed, 2008-09-17 at 14:49 +0200, Ingo Molnar wrote:
> >
> > > git log --pretty=format:"%h: %s" 2069f45..847106f | grep -viE \
> > > 'block|alsa|pcmcia|sound|Merge|iosched|blk|DAC960|scsi|s390|paride|pktcdvd|filter|cdrom|drm'
> > >
> > > gives us:
> > >
> > > 7daf705: Start using the new '%pS' infrastructure to print symbols
> > > 6f0f0fd: security: remove register_security hook
> > > 93cbace: security: remove dummy module fix
> > > 5915eb5: security: remove dummy module
> > > b478a9f: security: remove unused sb_get_mnt_opts hook
> > > 32502b8: splice: fix generic_file_splice_read() race with page invalidation
> > > 8b3d356: ramfs: enable splice write
> > > a144ff0: xen: Avoid allocations causing swap activity on the resume path
> > >
> > > which really only leaves that security commit your bisection fingered.
> > > Which _slightly_ raises its likelyhood of being implicated. Structure
> > > size changes can move two formerly far-apart netperf-relevant symbols on
> > > the same cacheline, which can start cache ping-pong-ing badly.
> >
> > I sure hope it's something like ping-pong, it's driving me NUTS.
>
> How about dividing the problem to smaller blocks then by restoring
> parts of the change...
Well, what I've done is check out the "bad" tree, reverted every darn
commit between there and the "good" tree, and then reverted the reverts
so I have a nice merge-free line and don't have to remember to think
backward. (probably sounds silly to git-foo masters) I'll try
bisecting that in the a.m. and see what happens.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
[not found] ` <200809122319.18633.rjw-KKrjLPT3xs0@public.gmane.org>
@ 2008-09-17 14:26 ` Bjorn Helgaas
0 siblings, 0 replies; 126+ messages in thread
From: Bjorn Helgaas @ 2008-09-17 14:26 UTC (permalink / raw)
To: Rafael J. Wysocki, David Miller
Cc: Randy Dunlap, Linux Kernel Mailing List, Kernel Testers List,
Ingo Molnar, Andrew Morton
On Friday 12 September 2008 03:19:17 pm Rafael J. Wysocki wrote:
> On Friday, 12 of September 2008, Randy Dunlap wrote:
> > Rafael J. Wysocki wrote:
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11276
> > > Subject : build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things
> > > Submitter : Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> > > Date : 2008-08-06 17:18 (38 days old)
> > > References : http://marc.info/?l=linux-kernel&m=121804329014332&w=4
> > > http://lkml.org/lkml/2008/7/22/353
> > > Handled-By : Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
> > > Patch : http://lkml.org/lkml/2008/7/22/364
Thanks for pointing out the fix that should have been obvious,
Dave. That's a much better solution than sprinkling #ifdef
CONFIG_PNP through drivers.
Rafael, in case you missed the checkin, it's commit
ef3d7714f6b75b51825ad0384b5ce48358427e50
Bjorn
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221657111.5511.14.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-17 13:36 ` Ilpo Järvinen
@ 2008-09-17 14:47 ` Eric Dumazet
[not found] ` <48D11871.4090805-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
1 sibling, 1 reply; 126+ messages in thread
From: Eric Dumazet @ 2008-09-17 14:47 UTC (permalink / raw)
To: Mike Galbraith
Cc: Ingo Molnar, Ilpo Järvinen, Christoph Lameter,
Rafael J. Wysocki, LKML, kernel-testers-u79uwXL29TY76Z2rM5mHXA
Mike Galbraith a écrit :
> On Wed, 2008-09-17 at 14:49 +0200, Ingo Molnar wrote:
>> * Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org> wrote:
>>
>>>> It looks like a potentially bogus bisection result, but _maybe_ it
>>>> has relevance: changes the size of "struct security_operations",
>>>> which could have alignment and layout effects on all sorts of kernel
>>>> variables, kmalloc sizes, etc.
>>> This may well be a mythical creature infestation for all I know ;-),
>>> but it's address is somewhere in the 2069f45..847106f block, 316
>>> commits, none of which look like they should be the least bit
>>> interesting to netperf. I reverted this particular commit in 27.git,
>>> got the expected result. Looks like I'll keep poking at it, can't
>>> seem to resist. Grr.
>> are you sure it's 2069f45..847106f? Filtering out the
>> likely-uninteresting commits:
>
> Yeah, as sure as I can be. I've built both (et al) kernels several
> times, and it has repeated every time. Would be nice if someone would
> try to confirm/deny though. For my little quad, I do..
>
> #!/bin/sh
>
> echo 0 > /proc/sys/kernel/sched_wakeup_granularity_ns
>
> netserver -p 12865
> netserver -p 12866
> netserver -p 12867
> netserver -p 12868
>
> netperf -p 12865 -t TCP_RR -l 60 -H 127.0.0.1 -T 0,0 -- -r 1,1&
> netperf -p 12866 -t TCP_RR -l 60 -H 127.0.0.1 -T 1,1 -- -r 1,1&
> netperf -p 12867 -t TCP_RR -l 60 -H 127.0.0.1 -T 2,2 -- -r 1,1&
> netperf -p 12868 -t TCP_RR -l 60 -H 127.0.0.1 -T 3,3 -- -r 1,1&
>
> wait
> killall netserver
>
>
>> git log --pretty=format:"%h: %s" 2069f45..847106f | grep -viE \
>> 'block|alsa|pcmcia|sound|Merge|iosched|blk|DAC960|scsi|s390|paride|pktcdvd|filter|cdrom|drm'
>>
>> gives us:
>>
>> 7daf705: Start using the new '%pS' infrastructure to print symbols
>> 6f0f0fd: security: remove register_security hook
>> 93cbace: security: remove dummy module fix
>> 5915eb5: security: remove dummy module
>> b478a9f: security: remove unused sb_get_mnt_opts hook
>> 32502b8: splice: fix generic_file_splice_read() race with page invalidation
>> 8b3d356: ramfs: enable splice write
>> a144ff0: xen: Avoid allocations causing swap activity on the resume path
>>
>> which really only leaves that security commit your bisection fingered.
>> Which _slightly_ raises its likelyhood of being implicated. Structure
>> size changes can move two formerly far-apart netperf-relevant symbols on
>> the same cacheline, which can start cache ping-pong-ing badly.
>
> I sure hope it's something like ping-pong, it's driving me NUTS.
Could you please try following patch ?
[PATCH] security_ops moved to read_mostly section
"struct security_operations *security_ops" should be moved to read_mostly
section in order to NOT let it share a cache line with higly modified variables.
Signed-off-by: Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
diff --git a/security/security.c b/security/security.c
index 3a4b4f5..0b13d65 100644
--- a/security/security.c
+++ b/security/security.c
@@ -24,7 +24,7 @@ static __initdata char chosen_lsm[SECURITY_NAME_MAX + 1];
extern struct security_operations default_security_ops;
extern void security_fixup_ops(struct security_operations *ops);
-struct security_operations *security_ops; /* Initialized to NULL */
+struct security_operations *security_ops __read_mostly;e
/* amount of vm to protect from userspace access */
unsigned long mmap_min_addr = CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR;
^ permalink raw reply related [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <48D11871.4090805-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
@ 2008-09-17 14:50 ` Eric Dumazet
2008-09-17 18:16 ` Mike Galbraith
1 sibling, 0 replies; 126+ messages in thread
From: Eric Dumazet @ 2008-09-17 14:50 UTC (permalink / raw)
To: Mike Galbraith
Cc: Ingo Molnar, Ilpo Järvinen, Christoph Lameter,
Rafael J. Wysocki, LKML, kernel-testers-u79uwXL29TY76Z2rM5mHXA
Eric Dumazet a écrit :
> Mike Galbraith a écrit :
>> I sure hope it's something like ping-pong, it's driving me NUTS.
>
> Could you please try following patch ?
>
> [PATCH] security_ops moved to read_mostly section
>
> "struct security_operations *security_ops" should be moved to
> read_mostly section in order to NOT let it share a cache line with higly
> modified variables.
>
> Signed-off-by: Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
>
> diff --git a/security/security.c b/security/security.c
> index 3a4b4f5..0b13d65 100644
> --- a/security/security.c
> +++ b/security/security.c
> @@ -24,7 +24,7 @@ static __initdata char chosen_lsm[SECURITY_NAME_MAX + 1];
> extern struct security_operations default_security_ops;
> extern void security_fixup_ops(struct security_operations *ops);
>
> -struct security_operations *security_ops; /* Initialized to NULL */
> +struct security_operations *security_ops __read_mostly;e
Sorry for the extra 'e' at the end of this line, please remove it :)
>
> /* amount of vm to protect from userspace access */
> unsigned long mmap_min_addr = CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR;
>
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221659858.8818.13.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-17 17:04 ` Ilpo Järvinen
2008-09-18 7:12 ` Mike Galbraith
1 sibling, 0 replies; 126+ messages in thread
From: Ilpo Järvinen @ 2008-09-17 17:04 UTC (permalink / raw)
To: Mike Galbraith
Cc: Ingo Molnar, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2319 bytes --]
On Wed, 17 Sep 2008, Mike Galbraith wrote:
> On Wed, 2008-09-17 at 16:36 +0300, Ilpo Järvinen wrote:
> > On Wed, 17 Sep 2008, Mike Galbraith wrote:
> >
> > > On Wed, 2008-09-17 at 14:49 +0200, Ingo Molnar wrote:
> > >
> > > > git log --pretty=format:"%h: %s" 2069f45..847106f | grep -viE \
> > > > 'block|alsa|pcmcia|sound|Merge|iosched|blk|DAC960|scsi|s390|paride|pktcdvd|filter|cdrom|drm'
> > > >
> > > > gives us:
> > > >
> > > > 7daf705: Start using the new '%pS' infrastructure to print symbols
> > > > 6f0f0fd: security: remove register_security hook
> > > > 93cbace: security: remove dummy module fix
> > > > 5915eb5: security: remove dummy module
> > > > b478a9f: security: remove unused sb_get_mnt_opts hook
> > > > 32502b8: splice: fix generic_file_splice_read() race with page invalidation
> > > > 8b3d356: ramfs: enable splice write
> > > > a144ff0: xen: Avoid allocations causing swap activity on the resume path
> > > >
> > > > which really only leaves that security commit your bisection fingered.
> > > > Which _slightly_ raises its likelyhood of being implicated. Structure
> > > > size changes can move two formerly far-apart netperf-relevant symbols on
> > > > the same cacheline, which can start cache ping-pong-ing badly.
> > >
> > > I sure hope it's something like ping-pong, it's driving me NUTS.
> >
> > How about dividing the problem to smaller blocks then by restoring
> > parts of the change...
>
> Well, what I've done is check out the "bad" tree, reverted every darn
> commit between there and the "good" tree, and then reverted the reverts
> so I have a nice merge-free line and don't have to remember to think
> backward. (probably sounds silly to git-foo masters) I'll try
> bisecting that in the a.m. and see what happens.
This was my initial idea (which was mainly an error from my part as I
misread some shaids and midunderstood that the first regressing would be
the merge instead of the actual change), but in here I meant taking parts
of the 6f0f0fd on top of 6f0f0fd^. The most easiest way to do that
actually might be to do in fact the opposite, ie., but some of the
datastructure/layout changes back on top of 6f0f0fd and see if the
performance get restored (besides testing the Eric's patch).
--
i.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <48D11871.4090805-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
2008-09-17 14:50 ` Eric Dumazet
@ 2008-09-17 18:16 ` Mike Galbraith
1 sibling, 0 replies; 126+ messages in thread
From: Mike Galbraith @ 2008-09-17 18:16 UTC (permalink / raw)
To: Eric Dumazet
Cc: Ingo Molnar, Ilpo Järvinen, Christoph Lameter,
Rafael J. Wysocki, LKML, kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Wed, 2008-09-17 at 16:47 +0200, Eric Dumazet wrote:
> Could you please try following patch ?
>
> [PATCH] security_ops moved to read_mostly section
>
> "struct security_operations *security_ops" should be moved to read_mostly
> section in order to NOT let it share a cache line with higly modified variables.
v2.6.26-974-g2846693 (tip of revert reverts tree, == 847106f)
16384 87380 1 1 60.00 94350.45
16384 87380 1 1 60.01 95857.25
16384 87380 1 1 60.00 95334.84
16384 87380 1 1 60.00 95052.11
v2.6.26-659-g7804ad8 (first commit prior, == 2069f45)
16384 87380 1 1 60.00 98630.64
16384 87380 1 1 60.00 98653.14
16384 87380 1 1 60.00 99162.65
16384 87380 1 1 60.00 98652.38
v2.6.26-974-g2846693 patched
16384 87380 1 1 60.00 95877.41
16384 87380 1 1 60.00 95810.27
16384 87380 1 1 60.00 95530.03
16384 87380 1 1 60.00 94968.12
(poo, "it" didn't die)
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <1221483926.30816.18.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2008-09-15 13:42 ` Stephen Smalley
@ 2008-09-17 19:50 ` Andrew Morton
2008-09-17 21:24 ` Paul Moore
[not found] ` <20080917125053.1f9ecf37.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
1 sibling, 2 replies; 126+ messages in thread
From: Andrew Morton @ 2008-09-17 19:50 UTC (permalink / raw)
To: Stephen Smalley
Cc: jmorris-gx6/JNMH7DfYtjvyW6yDsg, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA, Eric W. Biederman,
netdev-u79uwXL29TY76Z2rM5mHXA
On Mon, 15 Sep 2008 09:05:26 -0400
Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org> wrote:
>
> On Sat, 2008-09-13 at 12:37 -0700, Andrew Morton wrote:
> > On Sat, 13 Sep 2008 10:15:43 +1000 (EST) James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org> wrote:
> >
> > > On Fri, 12 Sep 2008, Andrew Morton wrote:
> > >
> > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11500
> > > > > > Subject : /proc/net bug related to selinux
> > > > > > Submitter : Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > > > > > Date : 2008-09-04 17:45 (9 days old)
> > > > > > References : http://marc.info/?l=linux-kernel&m=122055041313270&w=4
> > > > >
> > > > > I think this might be a regression caused by namespace changes which we
> > >
> > > By which I mean, this was caused by a non-SELinux change to the upstream
> > > kernel many, many eons ago.
> >
> > hm, seems that 2.6.24 is OK but 2.6.25 is not. I must have missed the
> > bug when testing 2.6.25-based kernels.
> >
> > I started a git bisection search but after half an hour I hit bad
> > bisection breakage: a complete machine hang in fib_rules_init().
> >
> > > > > addressed in SELinux policy. Which distro version & policy version is
> > > > > this seen with?
> > > > >
> > > >
> > > > FC5 on x86_32 and FC6 on x86_64.
> > >
> > > As mentioned in the bugzilla, any related avc messages would be useful.
> >
> > 2.6.25 dmesg: http://userweb.kernel.org/~akpm/dmesg-sony.txt
> > /var/log/messages: http://userweb.kernel.org/~akpm/messages-sony.txt
> >
> > The latter includes this:
> >
> > Sep 13 12:32:43 sony kernel: SELinux: class key not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class dccp_socket not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class memprotect not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class peer not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: class capability2 not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class dir not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class chr_file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class blk_file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission open in class fifo_file not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission recvfrom in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission sendto in class node not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_recv in class netif not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission dccp_send in class netif not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission ingress in class netif not defined in policy
> > Sep 13 12:32:43 sony kernel: SELinux: permission egress in class netif not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission setkeycreate in class process not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission setsockcreate in class process not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission setfcap in class capability not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission polmatch in class association not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission flow_in in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission flow_out in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission forward_in in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: permission forward_out in class packet not defined in policy
> > Sep 13 12:32:44 sony kernel: SELinux: the above unknown classes and permissions will be denied
> > Sep 13 12:32:44 sony kernel: type=1403 audit(1221309118.644:3): policy loaded auid=4294967295 ses=4294967295
> > Sep 13 12:32:44 sony kernel: type=1400 audit(1221334321.726:4): avc: denied { audit_write } for pid=400 comm="hwclock" capability=29 scontext=system_u:system_r:hwclock_t:s0 tcontext=system_u:system_r:hwclock_t:s0 tclass=capability
> >
> >
> > Why am I seeing this on two machines and two vanilla-installed distros
> > but nobody else is reporting it?
Running `ls -l /proc/net' on the FC6 machine produces:
[ 132.591215] type=1400 audit(1221679672.590:10): avc: denied { getattr } for pid=4389 comm="ls" path="/proc/net" dev=proc ino=4026531867 scontext=user_u:system_r:unconfined_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=lnk_file
> What we actually need to see is the output of:
> /sbin/ausearch -i -m AVC -sv no
akpm2:/home/akpm# /sbin/ausearch -i -m AVC -sv no
<no matches>
> However, the most likely explanation is simply that when /proc/net was
> changed from being a directory to being a symlink to /proc/self/net,
> that introduced an additional permission check on accesses
> of /proc/net/<whatever>, namely the read check on the symlink itself.
> And since that check wasn't happening on /proc/net accesses with older
> kernels, older policies didn't allow it.
>
> As to why others haven't reported it, I expect that they have updated
> their policies to newer ones that allow the necessary access. The fact
> that legacy distros wouldn't have such updated policies isn't surprising
> - they don't push updates to those distros for new kernels. FC5 and FC6
> are both EOL'd, right?
>
> In any event, we didn't change anything in SELinux - the change was
> elsewhere (in the proc/net implementation). Don't blame the messenger
> please.
>
Vanilla FC5 broke and vanilla FC6 broke. Did vanilla FC7, 8 or 9 break?
http://smolt.fedoraproject.org/static/stats/stats.html shows 11,000-odd
people running FC5 and FC6. It would be incautious to assume that all
those people have updated their selinux rules.
And _requiring_ people to update their selinux rules to fix a
kernel-caused regression is a pretty big deal for some people, I
expect.
Then again, given that this regression has been out there since 2.6.25,
I guess not too many people are hurting from it. But we suck.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-17 19:50 ` Andrew Morton
@ 2008-09-17 21:24 ` Paul Moore
2008-09-17 21:39 ` Eric W. Biederman
` (2 more replies)
[not found] ` <20080917125053.1f9ecf37.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
1 sibling, 3 replies; 126+ messages in thread
From: Paul Moore @ 2008-09-17 21:24 UTC (permalink / raw)
To: Andrew Morton
Cc: Stephen Smalley, jmorris, rjw, linux-kernel, kernel-testers,
Eric W. Biederman, netdev
On Wednesday 17 September 2008 3:50:53 pm Andrew Morton wrote:
> On Mon, 15 Sep 2008 09:05:26 -0400
> Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > However, the most likely explanation is simply that when /proc/net
> > was changed from being a directory to being a symlink to
> > /proc/self/net, that introduced an additional permission check on
> > accesses of /proc/net/<whatever>, namely the read check on the
> > symlink itself. And since that check wasn't happening on /proc/net
> > accesses with older kernels, older policies didn't allow it.
> >
> > As to why others haven't reported it, I expect that they have
> > updated their policies to newer ones that allow the necessary
> > access. The fact that legacy distros wouldn't have such updated
> > policies isn't surprising - they don't push updates to those
> > distros for new kernels. FC5 and FC6 are both EOL'd, right?
> >
> > In any event, we didn't change anything in SELinux - the change was
> > elsewhere (in the proc/net implementation). Don't blame the
> > messenger please.
>
> Vanilla FC5 broke and vanilla FC6 broke. Did vanilla FC7, 8 or 9
> break?
>
> http://smolt.fedoraproject.org/static/stats/stats.html shows
> 11,000-odd people running FC5 and FC6. It would be incautious to
> assume that all those people have updated their selinux rules.
>
> And _requiring_ people to update their selinux rules to fix a
> kernel-caused regression is a pretty big deal for some people, I
> expect.
Just so I'm clear on the context of the problem, it sounds like if a FC5
(I'm limiting myself to FC5 for the moment) user upgraded to a recent
(2.6.25+) kernel (non-distro supplied in the case of FC5) then they
will run into problems unless they also upgrade their SELinux policy,
yes?
If that is the case I'm not sure it is really that big of a deal. Maybe
I'm in the minority here, but in my mind once you step away from the
distro supplied kernel (also applies to other packages, although those
are arguably less critical) you should also bear the responsibility to
make sure you upgrade/tweak/install whatever other bits need to be
fixed.
> Then again, given that this regression has been out there since
> 2.6.25, I guess not too many people are hurting from it. But we
> suck.
We suck? Maybe, but some explanation about why we suck in this
particular case would be helpful as far as I'm concerned. I don't
really care about identifying the guilty suckees, I'm more interested
in finding out what happened to cause us to suck because of this.
--
paul moore
linux @ hp
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-17 21:24 ` Paul Moore
@ 2008-09-17 21:39 ` Eric W. Biederman
[not found] ` <m1vdwu4fku.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-09-17 21:48 ` Andrew Morton
[not found] ` <200809171724.36269.paul.moore-VXdhtT5mjnY@public.gmane.org>
2 siblings, 1 reply; 126+ messages in thread
From: Eric W. Biederman @ 2008-09-17 21:39 UTC (permalink / raw)
To: Paul Moore
Cc: Andrew Morton, Stephen Smalley, jmorris, rjw, linux-kernel,
kernel-testers, netdev
Paul Moore <paul.moore@hp.com> writes:
> We suck? Maybe, but some explanation about why we suck in this
> particular case would be helpful as far as I'm concerned. I don't
> really care about identifying the guilty suckees, I'm more interested
> in finding out what happened to cause us to suck because of this.
Agreed. I believe we carefully gave selinux the same paths for /proc/net
that it had before so I don't know why this affects user space.
I know we had some selinux review when we made the change.
Eric
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-17 21:24 ` Paul Moore
2008-09-17 21:39 ` Eric W. Biederman
@ 2008-09-17 21:48 ` Andrew Morton
2008-09-17 22:12 ` Paul Moore
[not found] ` <20080917144842.7df59f9e.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
[not found] ` <200809171724.36269.paul.moore-VXdhtT5mjnY@public.gmane.org>
2 siblings, 2 replies; 126+ messages in thread
From: Andrew Morton @ 2008-09-17 21:48 UTC (permalink / raw)
To: Paul Moore
Cc: sds, jmorris, rjw, linux-kernel, kernel-testers, ebiederm, netdev
On Wed, 17 Sep 2008 17:24:36 -0400
Paul Moore <paul.moore@hp.com> wrote:
> On Wednesday 17 September 2008 3:50:53 pm Andrew Morton wrote:
> > On Mon, 15 Sep 2008 09:05:26 -0400
> > Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > > However, the most likely explanation is simply that when /proc/net
> > > was changed from being a directory to being a symlink to
> > > /proc/self/net, that introduced an additional permission check on
> > > accesses of /proc/net/<whatever>, namely the read check on the
> > > symlink itself. And since that check wasn't happening on /proc/net
> > > accesses with older kernels, older policies didn't allow it.
> > >
> > > As to why others haven't reported it, I expect that they have
> > > updated their policies to newer ones that allow the necessary
> > > access. The fact that legacy distros wouldn't have such updated
> > > policies isn't surprising - they don't push updates to those
> > > distros for new kernels. FC5 and FC6 are both EOL'd, right?
> > >
> > > In any event, we didn't change anything in SELinux - the change was
> > > elsewhere (in the proc/net implementation). Don't blame the
> > > messenger please.
> >
> > Vanilla FC5 broke and vanilla FC6 broke. Did vanilla FC7, 8 or 9
> > break?
> >
> > http://smolt.fedoraproject.org/static/stats/stats.html shows
> > 11,000-odd people running FC5 and FC6. It would be incautious to
> > assume that all those people have updated their selinux rules.
> >
> > And _requiring_ people to update their selinux rules to fix a
> > kernel-caused regression is a pretty big deal for some people, I
> > expect.
>
> Just so I'm clear on the context of the problem, it sounds like if a FC5
> (I'm limiting myself to FC5 for the moment) user upgraded to a recent
> (2.6.25+) kernel (non-distro supplied in the case of FC5) then they
> will run into problems unless they also upgrade their SELinux policy,
> yes?
That only true if the 2.6.25+ kernel.org kernel is
backward-incompatible with the distro kernel.
> If that is the case I'm not sure it is really that big of a deal. Maybe
> I'm in the minority here, but in my mind once you step away from the
> distro supplied kernel (also applies to other packages, although those
> are arguably less critical) you should also bear the responsibility to
> make sure you upgrade/tweak/install whatever other bits need to be
> fixed.
Nope. Releasing a non-backward-compatible kernel.org kernel is a big
deal.
We'll do it sometimes, with long notice, much care and much deliberation.
We did it this time by sheer accident. That's known in the trade as a
"bug".
> > Then again, given that this regression has been out there since
> > 2.6.25, I guess not too many people are hurting from it. But we
> > suck.
>
> We suck? Maybe, but some explanation about why we suck in this
> particular case would be helpful as far as I'm concerned. I don't
> really care about identifying the guilty suckees, I'm more interested
> in finding out what happened to cause us to suck because of this.
Because we unintentionally and unknowingly released a kernel which is
not compatible with previous kernels without notifying any of our users
and without any consideration or planning.
Yes, often the consequences of the screwup are fairly small, but it's a
screwup nonetheless.
We don't even know the extent of the damage yet. Which distros were
affected? With which versions of which userspace packages?
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <20080917125053.1f9ecf37.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
@ 2008-09-17 21:56 ` Eric W. Biederman
0 siblings, 0 replies; 126+ messages in thread
From: Eric W. Biederman @ 2008-09-17 21:56 UTC (permalink / raw)
To: Andrew Morton
Cc: Stephen Smalley, jmorris-gx6/JNMH7DfYtjvyW6yDsg, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA,
netdev-u79uwXL29TY76Z2rM5mHXA
Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> writes:
> On Mon, 15 Sep 2008 09:05:26 -0400
> Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org> wrote:
>> On Sat, 2008-09-13 at 12:37 -0700, Andrew Morton wrote:
>> However, the most likely explanation is simply that when /proc/net was
>> changed from being a directory to being a symlink to /proc/self/net,
>> that introduced an additional permission check on accesses
>> of /proc/net/<whatever>, namely the read check on the symlink itself.
>> And since that check wasn't happening on /proc/net accesses with older
>> kernels, older policies didn't allow it.
>> As to why others haven't reported it, I expect that they have updated
>> their policies to newer ones that allow the necessary access. The fact
>> that legacy distros wouldn't have such updated policies isn't surprising
>> - they don't push updates to those distros for new kernels. FC5 and FC6
>> are both EOL'd, right?
>>
>> In any event, we didn't change anything in SELinux - the change was
>> elsewhere (in the proc/net implementation). Don't blame the messenger
>> please.
>>
>
> Vanilla FC5 broke and vanilla FC6 broke. Did vanilla FC7, 8 or 9 break?
>
> http://smolt.fedoraproject.org/static/stats/stats.html shows 11,000-odd
> people running FC5 and FC6. It would be incautious to assume that all
> those people have updated their selinux rules.
>
> And _requiring_ people to update their selinux rules to fix a
> kernel-caused regression is a pretty big deal for some people, I
> expect.
> Then again, given that this regression has been out there since 2.6.25,
> I guess not too many people are hurting from it. But we suck.
Looking at this discussion closely from what I see selinux is designed
to work on the principle of least privilege. If you make a user space
visible but compatible change, selinux will keep the system until
you update selinux. Is selinux exposing too much to user space?
selinux was taken into consideration when the change was made.
The patch was even updated with feedback from Stephen Smiley.
> commit e9720acd728a46cb40daa52c99a979f7c4ff195c
> Author: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
> Date: Fri Mar 7 11:08:40 2008 -0800
>
> [NET]: Make /proc/net a symlink on /proc/self/net (v3)
>
> Current /proc/net is done with so called "shadows", but current
> implementation is broken and has little chances to get fixed.
>
> The problem is that dentries subtree of /proc/net directory has
> fancy revalidation rules to make processes living in different
> net namespaces see different entries in /proc/net subtree, but
> currently, tasks see in the /proc/net subdir the contents of any
> other namespace, depending on who opened the file first.
>
> The proposed fix is to turn /proc/net into a symlink, which points
> to /proc/self/net, which in turn shows what previously was in
> /proc/net - the network-related info, from the net namespace the
> appropriate task lives in.
>
> # ls -l /proc/net
> lrwxrwxrwx 1 root root 8 Mar 5 15:17 /proc/net -> self/net
>
> In other words - this behaves like /proc/mounts, but unlike
> "mounts", "net" is not a file, but a directory.
>
> Changes from v2:
> * Fixed discrepancy of /proc/net nlink count and selinux labeling
> screwup pointed out by Stephen.
>
> To get the correct nlink count the ->getattr callback for /proc/net
> is overridden to read one from the net->proc_net entry.
>
> To make selinux still work the net->proc_net entry is initialized
> properly, i.e. with the "net" name and the proc_net parent.
>
> Selinux fixes are
> Acked-by: Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
>
> Changes from v1:
> * Fixed a task_struct leak in get_proc_task_net, pointed out by Paul.
>
> Signed-off-by: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
> Acked-by: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
> Signed-off-by: David S. Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <m1vdwu4fku.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
@ 2008-09-17 22:11 ` Andrew Morton
0 siblings, 0 replies; 126+ messages in thread
From: Andrew Morton @ 2008-09-17 22:11 UTC (permalink / raw)
To: Eric W. Biederman
Cc: paul.moore-VXdhtT5mjnY, sds-+05T5uksL2qpZYMLLGbcSA,
jmorris-gx6/JNMH7DfYtjvyW6yDsg, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA,
netdev-u79uwXL29TY76Z2rM5mHXA
On Wed, 17 Sep 2008 14:39:45 -0700
ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) wrote:
> Paul Moore <paul.moore-VXdhtT5mjnY@public.gmane.org> writes:
>
> > We suck? Maybe, but some explanation about why we suck in this
> > particular case would be helpful as far as I'm concerned. I don't
> > really care about identifying the guilty suckees, I'm more interested
> > in finding out what happened to cause us to suck because of this.
>
> Agreed. I believe we carefully gave selinux the same paths for /proc/net
> that it had before so I don't know why this affects user space.
>
> I know we had some selinux review when we made the change.
>
> Eric
It's back up-thread somewhere. umm...
On Mon, 15 Sep 2008 09:05:26 -0400
Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org> wrote:
> However, the most likely explanation is simply that when /proc/net was
> changed from being a directory to being a symlink to /proc/self/net,
> that introduced an additional permission check on accesses
> of /proc/net/<whatever>, namely the read check on the symlink itself.
> And since that check wasn't happening on /proc/net accesses with older
> kernels, older policies didn't allow it.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-17 21:48 ` Andrew Morton
@ 2008-09-17 22:12 ` Paul Moore
2008-09-17 22:24 ` Andrew Morton
[not found] ` <20080917144842.7df59f9e.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
1 sibling, 1 reply; 126+ messages in thread
From: Paul Moore @ 2008-09-17 22:12 UTC (permalink / raw)
To: Andrew Morton
Cc: sds, jmorris, rjw, linux-kernel, kernel-testers, ebiederm, netdev
On Wednesday 17 September 2008 5:48:42 pm Andrew Morton wrote:
> On Wed, 17 Sep 2008 17:24:36 -0400
>
> Paul Moore <paul.moore@hp.com> wrote:
> > On Wednesday 17 September 2008 3:50:53 pm Andrew Morton wrote:
> > > On Mon, 15 Sep 2008 09:05:26 -0400
> > >
> > > Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > > > However, the most likely explanation is simply that when
> > > > /proc/net was changed from being a directory to being a symlink
> > > > to /proc/self/net, that introduced an additional permission
> > > > check on accesses of /proc/net/<whatever>, namely the read
> > > > check on the symlink itself. And since that check wasn't
> > > > happening on /proc/net accesses with older kernels, older
> > > > policies didn't allow it.
> > > >
> > > > As to why others haven't reported it, I expect that they have
> > > > updated their policies to newer ones that allow the necessary
> > > > access. The fact that legacy distros wouldn't have such
> > > > updated policies isn't surprising - they don't push updates to
> > > > those distros for new kernels. FC5 and FC6 are both EOL'd,
> > > > right?
> > > >
> > > > In any event, we didn't change anything in SELinux - the change
> > > > was elsewhere (in the proc/net implementation). Don't blame
> > > > the messenger please.
> > >
> > > Vanilla FC5 broke and vanilla FC6 broke. Did vanilla FC7, 8 or 9
> > > break?
> > >
> > > http://smolt.fedoraproject.org/static/stats/stats.html shows
> > > 11,000-odd people running FC5 and FC6. It would be incautious to
> > > assume that all those people have updated their selinux rules.
> > >
> > > And _requiring_ people to update their selinux rules to fix a
> > > kernel-caused regression is a pretty big deal for some people, I
> > > expect.
> >
> > Just so I'm clear on the context of the problem, it sounds like if
> > a FC5 (I'm limiting myself to FC5 for the moment) user upgraded to
> > a recent (2.6.25+) kernel (non-distro supplied in the case of FC5)
> > then they will run into problems unless they also upgrade their
> > SELinux policy, yes?
>
> That only true if the 2.6.25+ kernel.org kernel is
> backward-incompatible with the distro kernel.
Yep, just wanted to make sure I was understanding the problem correctly.
> > If that is the case I'm not sure it is really that big of a deal.
> > Maybe I'm in the minority here, but in my mind once you step away
> > from the distro supplied kernel (also applies to other packages,
> > although those are arguably less critical) you should also bear the
> > responsibility to make sure you upgrade/tweak/install whatever
> > other bits need to be fixed.
>
> Nope. Releasing a non-backward-compatible kernel.org kernel is a big
> deal.
Well, there is also the issue of distro specific "special sauce" patches
which might cause different behavior from the kernel.org kernel, but
now we are starting to do down a rat hole ...
> We'll do it sometimes, with long notice, much care and much
> deliberation.
>
> We did it this time by sheer accident. That's known in the trade as
> a "bug".
It is somewhat comforting to know that we can call what we do a "trade",
further commentary on my part is best left to the imagination :)
> > > Then again, given that this regression has been out there since
> > > 2.6.25, I guess not too many people are hurting from it. But we
> > > suck.
> >
> > We suck? Maybe, but some explanation about why we suck in this
> > particular case would be helpful as far as I'm concerned. I don't
> > really care about identifying the guilty suckees, I'm more
> > interested in finding out what happened to cause us to suck because
> > of this.
>
> Because we unintentionally and unknowingly released a kernel which is
> not compatible with previous kernels without notifying any of our
> users and without any consideration or planning.
>
> Yes, often the consequences of the screwup are fairly small, but it's
> a screwup nonetheless.
Okay, so we suck because broke something in 2.6.25 that went undetected
because current SELinux policies happen to be compatible with the
breakage. Gotcha.
> We don't even know the extent of the damage yet. Which distros were
> affected? With which versions of which userspace packages?
Can I assume that the "right" thing to do would be to find the problem
and revert whatever change caused the issue, yes? Or are we happy to
wait and see since the fallout so far has been minimal?
--
paul moore
linux @ hp
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <200809171724.36269.paul.moore-VXdhtT5mjnY@public.gmane.org>
@ 2008-09-17 22:23 ` David Miller
0 siblings, 0 replies; 126+ messages in thread
From: David Miller @ 2008-09-17 22:23 UTC (permalink / raw)
To: paul.moore-VXdhtT5mjnY
Cc: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b, sds-+05T5uksL2qpZYMLLGbcSA,
jmorris-gx6/JNMH7DfYtjvyW6yDsg, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA,
ebiederm-aS9lmoZGLiVWk0Htik3J/w, netdev-u79uwXL29TY76Z2rM5mHXA
From: Paul Moore <paul.moore-VXdhtT5mjnY@public.gmane.org>
Date: Wed, 17 Sep 2008 17:24:36 -0400
> If that is the case I'm not sure it is really that big of a deal. Maybe
> I'm in the minority here, but in my mind once you step away from the
> distro supplied kernel (also applies to other packages, although those
> are arguably less critical) you should also bear the responsibility to
> make sure you upgrade/tweak/install whatever other bits need to be
> fixed.
No, we tend to call this breaking things instead.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-17 22:12 ` Paul Moore
@ 2008-09-17 22:24 ` Andrew Morton
[not found] ` <20080917152407.76230f0c.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Andrew Morton @ 2008-09-17 22:24 UTC (permalink / raw)
To: Paul Moore
Cc: sds, jmorris, rjw, linux-kernel, kernel-testers, ebiederm, netdev
On Wed, 17 Sep 2008 18:12:59 -0400
Paul Moore <paul.moore@hp.com> wrote:
> > We don't even know the extent of the damage yet. Which distros were
> > affected? With which versions of which userspace packages?
>
> Can I assume that the "right" thing to do would be to find the problem
> and revert whatever change caused the issue, yes? Or are we happy to
> wait and see since the fallout so far has been minimal?
I don't think a revert is justified after all this time. afaik I'm the
first person to notice the problem, and it's been out there for
multiple months.
However it would be good if we could find some not-completely-stinky
way of making the old userspace work.
otoh, people who are shipping 2.6.25- and 2.6.26-based distros probably
wouldn't want such a patch in their kernels anyway.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <20080917144842.7df59f9e.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
@ 2008-09-17 22:32 ` Eric W. Biederman
2008-09-18 12:38 ` Stephen Smalley
0 siblings, 1 reply; 126+ messages in thread
From: Eric W. Biederman @ 2008-09-17 22:32 UTC (permalink / raw)
To: Andrew Morton
Cc: Paul Moore, sds-+05T5uksL2qpZYMLLGbcSA,
jmorris-gx6/JNMH7DfYtjvyW6yDsg, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA,
netdev-u79uwXL29TY76Z2rM5mHXA
Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> writes:
> We don't even know the extent of the damage yet. Which distros were
> affected? With which versions of which userspace packages?
This seems to me to be an extremely fragile selinux user space policy.
In their code that derives security labels from path names.
Why don't we have AppArmor in the kernel again?
Further I don't see how we could have possibly have supported that user space
policy. How can we apply a user space defined label required by the selinux
policy to a symlink that did not exist?
I expect cd /proc/self/net would work. In your situation and you can
see /proc/self/net/dev.
Everything here sounds to me like that selinux policy is impossibly brittle.
And anything that is that brittle I have no intention in claiming is a bug
in proc.
Eric
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <20080917152407.76230f0c.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
@ 2008-09-17 22:53 ` Eric W. Biederman
0 siblings, 0 replies; 126+ messages in thread
From: Eric W. Biederman @ 2008-09-17 22:53 UTC (permalink / raw)
To: Andrew Morton
Cc: Paul Moore, sds-+05T5uksL2qpZYMLLGbcSA,
jmorris-gx6/JNMH7DfYtjvyW6yDsg, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA,
ebiederm-aS9lmoZGLiVWk0Htik3J/w, netdev-u79uwXL29TY76Z2rM5mHXA
Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> writes:
> On Wed, 17 Sep 2008 18:12:59 -0400
> Paul Moore <paul.moore-VXdhtT5mjnY@public.gmane.org> wrote:
>
>> > We don't even know the extent of the damage yet. Which distros were
>> > affected? With which versions of which userspace packages?
>>
>> Can I assume that the "right" thing to do would be to find the problem
>> and revert whatever change caused the issue, yes? Or are we happy to
>> wait and see since the fallout so far has been minimal?
>
> I don't think a revert is justified after all this time. afaik I'm the
> first person to notice the problem, and it's been out there for
> multiple months.
>
> However it would be good if we could find some not-completely-stinky
> way of making the old userspace work.
>
> otoh, people who are shipping 2.6.25- and 2.6.26-based distros probably
> wouldn't want such a patch in their kernels anyway.
Disable selinux?
Get a selinux mystic to update that selinux policy. I bet it is a one line
change to each the policy about /proc/net as a symlink.
Although I am puzzled why we don't get the same label as /proc/net as a directory
had.
Eric
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221659858.8818.13.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-17 17:04 ` Ilpo Järvinen
@ 2008-09-18 7:12 ` Mike Galbraith
[not found] ` <1221721970.5003.9.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
1 sibling, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-18 7:12 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Ingo Molnar, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Wed, 2008-09-17 at 15:57 +0200, Mike Galbraith wrote:
> On Wed, 2008-09-17 at 16:36 +0300, Ilpo Järvinen wrote:
> > On Wed, 17 Sep 2008, Mike Galbraith wrote:
> >
> > > On Wed, 2008-09-17 at 14:49 +0200, Ingo Molnar wrote:
> > >
> > > > git log --pretty=format:"%h: %s" 2069f45..847106f | grep -viE \
> > > > 'block|alsa|pcmcia|sound|Merge|iosched|blk|DAC960|scsi|s390|paride|pktcdvd|filter|cdrom|drm'
> > > >
> > > > gives us:
> > > >
> > > > 7daf705: Start using the new '%pS' infrastructure to print symbols
> > > > 6f0f0fd: security: remove register_security hook
> > > > 93cbace: security: remove dummy module fix
> > > > 5915eb5: security: remove dummy module
> > > > b478a9f: security: remove unused sb_get_mnt_opts hook
> > > > 32502b8: splice: fix generic_file_splice_read() race with page invalidation
> > > > 8b3d356: ramfs: enable splice write
> > > > a144ff0: xen: Avoid allocations causing swap activity on the resume path
> > > >
> > > > which really only leaves that security commit your bisection fingered.
> > > > Which _slightly_ raises its likelyhood of being implicated. Structure
> > > > size changes can move two formerly far-apart netperf-relevant symbols on
> > > > the same cacheline, which can start cache ping-pong-ing badly.
> > >
> > > I sure hope it's something like ping-pong, it's driving me NUTS.
> >
> > How about dividing the problem to smaller blocks then by restoring
> > parts of the change...
>
> Well, what I've done is check out the "bad" tree, reverted every darn
> commit between there and the "good" tree, and then reverted the reverts
> so I have a nice merge-free line and don't have to remember to think
> backward. (probably sounds silly to git-foo masters) I'll try
> bisecting that in the a.m. and see what happens.
It bisected to 1c9ce52. Reverting that in 27.git had the expected
result, nada. Full bisection/test log below - you can jump straight to
post run sanity checks. I'm torn between building a straight line tree
from v2.6.26 through git.today and bisecting that sucker, or exorcising
netperf from my box and swearing a sacred oath to never download the
damned thing again. Nuking netperf is most attractive option.
1e65e841bb5584136ed6047c55cf77532afbbb55 is first bad commit
commit 1e65e841bb5584136ed6047c55cf77532afbbb55
Author: Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org>
Date: Wed Sep 17 14:55:50 2008 +0200
Revert "Revert "block: export "ro" attribute""
This reverts commit 2c8803af5c1bf41200167f29349f7f1396683a51.
:040000 040000 08ca8ba7ff3f9506a5462b4122256356cae28ceb bef679485bc924ad1dc867858ebda1b68196b5a8 M block
git bisect start
# good: [7804ad865f7d0cd9bdc51da601772ce4d2e252ca] Revert "[ALSA] soc - tlv320aic3x - revisit clock setup"
git bisect good 7804ad865f7d0cd9bdc51da601772ce4d2e252ca
# bad: [2846693a63a34ac6d582dd55a7e00605b49b1cec] Revert "Revert "[S390] sclp_tty: Fix scheduling while atomic bug.""
git bisect bad 2846693a63a34ac6d582dd55a7e00605b49b1cec
# bad: [70477f86f63640be2dd1d8968aeb47870a5c21c6] Revert "Revert "xen/blkfront: Make sure we don't use bounce buffers, we don't need them.""
git bisect bad 70477f86f63640be2dd1d8968aeb47870a5c21c6
# good: [7c6ccb520424939deff0a50f3fae621c6477dbbe] Revert "Revert "ALSA: hda - Add bdl_pos_adj option""
git bisect good 7c6ccb520424939deff0a50f3fae621c6477dbbe
# good: [66036beae94f043f99044e285935486126a9c4bd] Revert "Revert "pcmcia: fix Alchemy warnings""
git bisect good 66036beae94f043f99044e285935486126a9c4bd
# good: [6b7b5ef18871c8f7c15eedc6eb53270eaf8bc613] Revert "Revert "ALSA: hda - Added SSID for 'Fujitsu Siemens Amilo M1451G' laptop""
git bisect good 6b7b5ef18871c8f7c15eedc6eb53270eaf8bc613
# good: [024905ea4b2d1ab5d6b845ba84ddfc0857fb2d2a] Revert "Revert "ALSA: hda - Add MacBook 3.1 support""
git bisect good 024905ea4b2d1ab5d6b845ba84ddfc0857fb2d2a
# good: [4bbe3501e06eddaa4900894efa519f1167cb8624] Revert "Revert "as-iosched: properly protect ioc_gone and ioc count""
git bisect good 4bbe3501e06eddaa4900894efa519f1167cb8624
# good: [e124683c1cd5c73c494f9ea6cee8a71e68bb70ca] Revert "Revert "Added in user-injected messages into blk traces""
git bisect good e124683c1cd5c73c494f9ea6cee8a71e68bb70ca
# bad: [f148fae0bc009aa23122c5762368a1a16bb55b86] Revert "Revert "block: kill request_queue_t""
git bisect bad f148fae0bc009aa23122c5762368a1a16bb55b86
# bad: [1e65e841bb5584136ed6047c55cf77532afbbb55] Revert "Revert "block: export "ro" attribute""
git bisect bad 1e65e841bb5584136ed6047c55cf77532afbbb55
v2.6.26-974-g2846693 (847106f)
16384 87380 1 1 60.00 94350.45
16384 87380 1 1 60.01 95857.25
16384 87380 1 1 60.00 95334.84
16384 87380 1 1 60.00 95052.11
v2.6.26-659-g7804ad8 (2069f45)
16384 87380 1 1 60.00 98630.64
16384 87380 1 1 60.00 98653.14
16384 87380 1 1 60.00 99162.65
16384 87380 1 1 60.00 98652.38
v2.6.26-816-g70477f8 (call it bad)
16384 87380 1 1 60.00 95532.19
16384 87380 1 1 60.01 96211.39
16384 87380 1 1 60.01 96246.73
16384 87380 1 1 60.01 96286.40
v2.6.26-737-g7c6ccb5
16384 87380 1 1 60.00 98478.00
16384 87380 1 1 60.00 99221.33
16384 87380 1 1 60.00 98930.70
16384 87380 1 1 60.00 98958.73
v2.6.26-776-g66036be
16384 87380 1 1 60.00 97958.10
16384 87380 1 1 60.01 98683.80
16384 87380 1 1 60.01 98515.34
16384 87380 1 1 60.00 98396.11
v2.6.26-796-g6b7b5ef
16384 87380 1 1 60.00 99047.21
16384 87380 1 1 60.00 98095.23
16384 87380 1 1 60.00 99811.18
16384 87380 1 1 60.00 98651.32
v2.6.26-806-g024905e
16384 87380 1 1 60.00 98823.46
16384 87380 1 1 60.00 98959.11
16384 87380 1 1 60.00 98709.95
16384 87380 1 1 60.00 99042.13
v2.6.26-811-g4bbe350
16384 87380 1 1 60.00 98144.99
16384 87380 1 1 60.01 99023.30
16384 87380 1 1 60.01 98685.45
16384 87380 1 1 60.01 98606.18
v2.6.26-813-ge124683
16384 87380 1 1 60.00 98458.18
16384 87380 1 1 60.00 98163.92
16384 87380 1 1 60.00 98115.62
16384 87380 1 1 60.00 98633.62
v2.6.26-815-gf148fae
16384 87380 1 1 60.00 95649.91
16384 87380 1 1 60.00 96292.34
16384 87380 1 1 60.00 96043.82
16384 87380 1 1 60.00 96093.81
v2.6.26-814-g1e65e84
16384 87380 1 1 60.00 94906.81
16384 87380 1 1 60.00 95445.05
16384 87380 1 1 60.01 94698.68
16384 87380 1 1 60.00 94938.65
Post bisection checkouts
------------------------------------------------
v2.6.26-rc8-208-g02c6230
16384 87380 1 1 60.00 98392.94
16384 87380 1 1 60.00 98199.96
16384 87380 1 1 60.00 98534.27
16384 87380 1 1 60.00 98501.02
v2.6.26-rc8-209-g1c9ce52
16384 87380 1 1 60.00 97583.88
16384 87380 1 1 60.00 97326.23
16384 87380 1 1 60.00 97582.80
16384 87380 1 1 60.00 97568.63
v2.6.26-814-g1e65e84
16384 87380 1 1 60.00 94856.33
16384 87380 1 1 60.00 94594.03
16384 87380 1 1 60.00 94751.74
16384 87380 1 1 60.01 96825.28
v2.6.26-813-ge124683
16384 87380 1 1 60.00 97550.64
16384 87380 1 1 60.00 98024.28
16384 87380 1 1 60.00 98486.85
16384 87380 1 1 60.00 98493.41
marge:..git/linux-2.6 # git rev-list v2.6.26-813-ge124683..v2.6.26-814-g1e65e84
1e65e841bb5584136ed6047c55cf77532afbbb55
marge:..git/linux-2.6 # git show 1e65e841bb5584136ed6047c55cf77532afbbb55
commit 1e65e841bb5584136ed6047c55cf77532afbbb55
Author: Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org>
Date: Wed Sep 17 14:55:50 2008 +0200
Revert "Revert "block: export "ro" attribute""
This reverts commit 2c8803af5c1bf41200167f29349f7f1396683a51.
diff --git a/block/genhd.c b/block/genhd.c
index b922d48..43e468e 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -400,6 +400,14 @@ static ssize_t disk_removable_show(struct device *dev,
(disk->flags & GENHD_FL_REMOVABLE ? 1 : 0));
}
+static ssize_t disk_ro_show(struct device *dev,
+ struct device_attribute *attr, char *buf)
+{
+ struct gendisk *disk = dev_to_disk(dev);
+
+ return sprintf(buf, "%d\n", disk->policy ? 1 : 0);
+}
+
static ssize_t disk_size_show(struct device *dev,
struct device_attribute *attr, char *buf)
{
@@ -472,6 +480,7 @@ static ssize_t disk_fail_store(struct device *dev,
static DEVICE_ATTR(range, S_IRUGO, disk_range_show, NULL);
static DEVICE_ATTR(removable, S_IRUGO, disk_removable_show, NULL);
+static DEVICE_ATTR(ro, S_IRUGO, disk_ro_show, NULL);
static DEVICE_ATTR(size, S_IRUGO, disk_size_show, NULL);
static DEVICE_ATTR(capability, S_IRUGO, disk_capability_show, NULL);
static DEVICE_ATTR(stat, S_IRUGO, disk_stat_show, NULL);
@@ -483,6 +492,7 @@ static struct device_attribute dev_attr_fail =
static struct attribute *disk_attrs[] = {
&dev_attr_range.attr,
&dev_attr_removable.attr,
+ &dev_attr_ro.attr,
&dev_attr_size.attr,
&dev_attr_capability.attr,
&dev_attr_stat.attr,
^ permalink raw reply related [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221721970.5003.9.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-18 7:25 ` Mike Galbraith
[not found] ` <1221722733.5149.6.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Mike Galbraith @ 2008-09-18 7:25 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Ingo Molnar, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Thu, 2008-09-18 at 09:12 +0200, Mike Galbraith wrote:
> 1e65e841bb5584136ed6047c55cf77532afbbb55 is first bad commit
> commit 1e65e841bb5584136ed6047c55cf77532afbbb55
> Author: Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org>
> Date: Wed Sep 17 14:55:50 2008 +0200
>
> Revert "Revert "block: export "ro" attribute""
>
> This reverts commit 2c8803af5c1bf41200167f29349f7f1396683a51.
BTW, the reason it's revert revert is that I reverse bisected the revert
tree yesterday, and it emitted the same darn result. I immediately said
"yeah right, ya screwed up", and created the revert revert tree to make
sure I couldn't fumble negation.
-Mike
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28
[not found] ` <1221722733.5149.6.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
@ 2008-09-18 7:58 ` Ilpo Järvinen
0 siblings, 0 replies; 126+ messages in thread
From: Ilpo Järvinen @ 2008-09-18 7:58 UTC (permalink / raw)
To: Mike Galbraith
Cc: Ingo Molnar, Christoph Lameter, Rafael J. Wysocki, LKML,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
On Thu, 18 Sep 2008, Mike Galbraith wrote:
> On Thu, 2008-09-18 at 09:12 +0200, Mike Galbraith wrote:
>
> > 1e65e841bb5584136ed6047c55cf77532afbbb55 is first bad commit
> > commit 1e65e841bb5584136ed6047c55cf77532afbbb55
> > Author: Mike Galbraith <efault-Mmb7MZpHnFY@public.gmane.org>
> > Date: Wed Sep 17 14:55:50 2008 +0200
> >
> > Revert "Revert "block: export "ro" attribute""
> >
> > This reverts commit 2c8803af5c1bf41200167f29349f7f1396683a51.
>
> BTW, the reason it's revert revert is that I reverse bisected the revert
> tree yesterday, and it emitted the same darn result. I immediately said
> "yeah right, ya screwed up", and created the revert revert tree to make
> sure I couldn't fumble negation.
:-)
gcc compiling something slightly differently would be a nice theory but
it sort of breaks down now as this commit touches only one .c file...
In the past when I did some static inline .h -> .c uninline sizing tests
I noticed that some changes happened also in places which should have been
quite much unrelated. Though all the changes were minor anyway (in the
places I did look), e.g., routed the conditional paths slightly
differently and added one xor clear reg.
--
i.
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-17 22:32 ` Eric W. Biederman
@ 2008-09-18 12:38 ` Stephen Smalley
2008-09-18 13:03 ` Stephen Smalley
0 siblings, 1 reply; 126+ messages in thread
From: Stephen Smalley @ 2008-09-18 12:38 UTC (permalink / raw)
To: Eric W. Biederman
Cc: Andrew Morton, Paul Moore, jmorris, rjw, linux-kernel,
kernel-testers, netdev
On Wed, 2008-09-17 at 15:32 -0700, Eric W. Biederman wrote:
> Andrew Morton <akpm@linux-foundation.org> writes:
>
> > We don't even know the extent of the damage yet. Which distros were
> > affected? With which versions of which userspace packages?
>
> This seems to me to be an extremely fragile selinux user space policy.
> In their code that derives security labels from path names.
> Why don't we have AppArmor in the kernel again?
I think I explained that one before - in the case of /proc, the only
stable basis we have for deducing the security properties / protection
requirements for a given entry is its name, and its name can be reliably
constructed from the kernel's internal proc_dir_entry tree w/o any
ambiguity or potential for userspace manipulation (unlike the pathname
returned by d_path for a normal file). I'd agree that it isn't optimal,
but it is what we have.
> Further I don't see how we could have possibly have supported that user space
> policy. How can we apply a user space defined label required by the selinux
> policy to a symlink that did not exist?
I'm not blaming anyone here, or trying to argue that the /proc/net
changes should be reverted. What happened here is that a kernel
interface (/proc/net) changed in a subtle way that had a side effect on
permission checking, and we tried to hide that change at the time (in
terms of ensuring that the new /proc/self/net tree would still be
labeled correctly), and we missed the fact that there would still be a
new check on the symlink read that wouldn't be covered by existing
policy.
> Everything here sounds to me like that selinux policy is impossibly brittle.
> And anything that is that brittle I have no intention in claiming is a bug
> in proc.
I'm not arguing that this is a bug in proc or in selinux for that
matter.
I do however think that the mantra that we can't require users to update
policy for kernel changes is unsupportable in general. The precise set
of permission checks on a given operation is not set in stone and it is
not part of the kernel/userland interface/contract. Policy isn't
"userspace"; it governs what userspace can do, and it has to adapt to
kernel changes.
Users who are willing/able to run the latest kernel on their own w/o
waiting for a coordinated update of kernel and policy from their
distribution ought to be able to create a local policy module - it isn't
rocket science, and they can always fall back on audit2allow if they
need to do so.
--
Stephen Smalley
National Security Agency
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-18 12:38 ` Stephen Smalley
@ 2008-09-18 13:03 ` Stephen Smalley
2008-09-18 18:09 ` Eric W. Biederman
0 siblings, 1 reply; 126+ messages in thread
From: Stephen Smalley @ 2008-09-18 13:03 UTC (permalink / raw)
To: Eric W. Biederman
Cc: Andrew Morton, Paul Moore, jmorris, rjw, linux-kernel,
kernel-testers, netdev
On Thu, 2008-09-18 at 08:38 -0400, Stephen Smalley wrote:
> On Wed, 2008-09-17 at 15:32 -0700, Eric W. Biederman wrote:
> > Andrew Morton <akpm@linux-foundation.org> writes:
> >
> > > We don't even know the extent of the damage yet. Which distros were
> > > affected? With which versions of which userspace packages?
> >
> > This seems to me to be an extremely fragile selinux user space policy.
> > In their code that derives security labels from path names.
> > Why don't we have AppArmor in the kernel again?
>
> I think I explained that one before - in the case of /proc, the only
> stable basis we have for deducing the security properties / protection
> requirements for a given entry is its name, and its name can be reliably
> constructed from the kernel's internal proc_dir_entry tree w/o any
> ambiguity or potential for userspace manipulation (unlike the pathname
> returned by d_path for a normal file). I'd agree that it isn't optimal,
> but it is what we have.
>
> > Further I don't see how we could have possibly have supported that user space
> > policy. How can we apply a user space defined label required by the selinux
> > policy to a symlink that did not exist?
>
> I'm not blaming anyone here, or trying to argue that the /proc/net
> changes should be reverted. What happened here is that a kernel
> interface (/proc/net) changed in a subtle way that had a side effect on
> permission checking, and we tried to hide that change at the time (in
> terms of ensuring that the new /proc/self/net tree would still be
> labeled correctly), and we missed the fact that there would still be a
> new check on the symlink read that wouldn't be covered by existing
> policy.
>
> > Everything here sounds to me like that selinux policy is impossibly brittle.
> > And anything that is that brittle I have no intention in claiming is a bug
> > in proc.
>
> I'm not arguing that this is a bug in proc or in selinux for that
> matter.
>
> I do however think that the mantra that we can't require users to update
> policy for kernel changes is unsupportable in general. The precise set
> of permission checks on a given operation is not set in stone and it is
> not part of the kernel/userland interface/contract. Policy isn't
> "userspace"; it governs what userspace can do, and it has to adapt to
> kernel changes.
I should note here that for changes to SELinux, we have gone out of our
way to avoid such breakage to date through the introduction of
compatibility switches, policy flags to enable any new checks, etc
(albeit at a cost in complexity and ever creeping compatibility code).
But changes to the rest of the kernel can just as easily alter the set
of permission checks that get applied on a given operation, and I don't
think we are always going to be able to guarantee that new kernel + old
policy will Just Work.
> Users who are willing/able to run the latest kernel on their own w/o
> waiting for a coordinated update of kernel and policy from their
> distribution ought to be able to create a local policy module - it isn't
> rocket science, and they can always fall back on audit2allow if they
> need to do so.
--
Stephen Smalley
National Security Agency
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-18 13:03 ` Stephen Smalley
@ 2008-09-18 18:09 ` Eric W. Biederman
2008-09-18 18:34 ` Stephen Smalley
0 siblings, 1 reply; 126+ messages in thread
From: Eric W. Biederman @ 2008-09-18 18:09 UTC (permalink / raw)
To: Stephen Smalley
Cc: Andrew Morton, Paul Moore, jmorris, rjw, linux-kernel,
kernel-testers, netdev
Stephen Smalley <sds@tycho.nsa.gov> writes:
> On Thu, 2008-09-18 at 08:38 -0400, Stephen Smalley wrote:
>> I do however think that the mantra that we can't require users to update
>> policy for kernel changes is unsupportable in general. The precise set
>> of permission checks on a given operation is not set in stone and it is
>> not part of the kernel/userland interface/contract. Policy isn't
>> "userspace"; it governs what userspace can do, and it has to adapt to
>> kernel changes.
>
> I should note here that for changes to SELinux, we have gone out of our
> way to avoid such breakage to date through the introduction of
> compatibility switches, policy flags to enable any new checks, etc
> (albeit at a cost in complexity and ever creeping compatibility code).
> But changes to the rest of the kernel can just as easily alter the set
> of permission checks that get applied on a given operation, and I don't
> think we are always going to be able to guarantee that new kernel + old
> policy will Just Work.
I know of at least 2 more directories that I intend to turn into
symlinks into somewhere under /proc/self. How do we keep from
breaking selinux policies when I do that?
For comparison how do we handle sysfs?
How do we handle device nodes in tmpfs?
Ultimately do we want to implement xattrs and inotify on /proc?
Or is there another way that would simplify maintenance?
Eric
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-18 18:09 ` Eric W. Biederman
@ 2008-09-18 18:34 ` Stephen Smalley
[not found] ` <1221762850.24048.107.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
0 siblings, 1 reply; 126+ messages in thread
From: Stephen Smalley @ 2008-09-18 18:34 UTC (permalink / raw)
To: Eric W. Biederman
Cc: Andrew Morton, Paul Moore, jmorris, rjw, linux-kernel,
kernel-testers, netdev, Eric Paris
On Thu, 2008-09-18 at 11:09 -0700, Eric W. Biederman wrote:
> Stephen Smalley <sds@tycho.nsa.gov> writes:
>
> > On Thu, 2008-09-18 at 08:38 -0400, Stephen Smalley wrote:
> >> I do however think that the mantra that we can't require users to update
> >> policy for kernel changes is unsupportable in general. The precise set
> >> of permission checks on a given operation is not set in stone and it is
> >> not part of the kernel/userland interface/contract. Policy isn't
> >> "userspace"; it governs what userspace can do, and it has to adapt to
> >> kernel changes.
> >
> > I should note here that for changes to SELinux, we have gone out of our
> > way to avoid such breakage to date through the introduction of
> > compatibility switches, policy flags to enable any new checks, etc
> > (albeit at a cost in complexity and ever creeping compatibility code).
> > But changes to the rest of the kernel can just as easily alter the set
> > of permission checks that get applied on a given operation, and I don't
> > think we are always going to be able to guarantee that new kernel + old
> > policy will Just Work.
>
> I know of at least 2 more directories that I intend to turn into
> symlinks into somewhere under /proc/self. How do we keep from
> breaking selinux policies when I do that?
I suspect we could tweak the logic in selinux_proc_get_sid() to always
label all symlinks under /proc with the base proc_t type already used
for e.g. /proc/self, at which point existing policies would be ok.
> For comparison how do we handle sysfs?
Unresolved; presently has a single label for all nodes.
See https://bugzilla.redhat.com/show_bug.cgi?id=228902
for prior discussion of fine-grained labeling support for sysfs.
> How do we handle device nodes in tmpfs?
udev has selinux support - looks up the appropriate context in a
userland config file (file_contexts) via libselinux matchpathcon(3) and
sets it upon creation. tmpfs has long supported getting/setting
security.* attributes.
> Ultimately do we want to implement xattrs and inotify on /proc?
> Or is there another way that would simplify maintenance?
If proc supported setxattr, then I suppose early userspace could label
it instead of the kernel needing to determine a label internally. But
not sure how we'd cleanly migrate to avoid breakage with old userspace.
--
Stephen Smalley
National Security Agency
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11506] oops during unmount - ext3? (2.6.27-rc5)
2008-09-12 19:06 ` [Bug #11506] oops during unmount - ext3? (2.6.27-rc5) Rafael J. Wysocki
@ 2008-09-19 16:17 ` Marcin Slusarz
0 siblings, 0 replies; 126+ messages in thread
From: Marcin Slusarz @ 2008-09-19 16:17 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Linux Kernel Mailing List, Kernel Testers List
On Fri, Sep 12, 2008 at 09:06:29PM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
I didn't see it since I upgraded to -rc6. You can close it for now.
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11506
> Subject : oops during unmount - ext3? (2.6.27-rc5)
> Submitter : Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date : 2008-09-04 19:14 (9 days old)
> References : http://marc.info/?l=linux-kernel&m=122055573123449&w=4
>
>
Marcin
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <1221762850.24048.107.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
@ 2008-09-19 16:58 ` david-gFPdbfVZQbY
2008-09-19 17:07 ` Stephen Smalley
2008-09-29 16:49 ` Stephen Smalley
1 sibling, 1 reply; 126+ messages in thread
From: david-gFPdbfVZQbY @ 2008-09-19 16:58 UTC (permalink / raw)
To: Stephen Smalley
Cc: Eric W. Biederman, Andrew Morton, Paul Moore,
jmorris-gx6/JNMH7DfYtjvyW6yDsg, rjw-KKrjLPT3xs0,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA,
netdev-u79uwXL29TY76Z2rM5mHXA, Eric Paris
On Thu, 18 Sep 2008, Stephen Smalley wrote:
> On Thu, 2008-09-18 at 11:09 -0700, Eric W. Biederman wrote:
>> Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org> writes:
>>
>>> On Thu, 2008-09-18 at 08:38 -0400, Stephen Smalley wrote:
>>>> I do however think that the mantra that we can't require users to update
>>>> policy for kernel changes is unsupportable in general. The precise set
>>>> of permission checks on a given operation is not set in stone and it is
>>>> not part of the kernel/userland interface/contract. Policy isn't
>>>> "userspace"; it governs what userspace can do, and it has to adapt to
>>>> kernel changes.
>>>
>>> I should note here that for changes to SELinux, we have gone out of our
>>> way to avoid such breakage to date through the introduction of
>>> compatibility switches, policy flags to enable any new checks, etc
>>> (albeit at a cost in complexity and ever creeping compatibility code).
>>> But changes to the rest of the kernel can just as easily alter the set
>>> of permission checks that get applied on a given operation, and I don't
>>> think we are always going to be able to guarantee that new kernel + old
>>> policy will Just Work.
>>
>> I know of at least 2 more directories that I intend to turn into
>> symlinks into somewhere under /proc/self. How do we keep from
>> breaking selinux policies when I do that?
>
> I suspect we could tweak the logic in selinux_proc_get_sid() to always
> label all symlinks under /proc with the base proc_t type already used
> for e.g. /proc/self, at which point existing policies would be ok.
so if proc is mounted anywhere other then /proc the selinux policy would
do odd things?
David Lang
>> For comparison how do we handle sysfs?
>
> Unresolved; presently has a single label for all nodes.
> See https://bugzilla.redhat.com/show_bug.cgi?id=228902
> for prior discussion of fine-grained labeling support for sysfs.
>
>> How do we handle device nodes in tmpfs?
>
> udev has selinux support - looks up the appropriate context in a
> userland config file (file_contexts) via libselinux matchpathcon(3) and
> sets it upon creation. tmpfs has long supported getting/setting
> security.* attributes.
>
>> Ultimately do we want to implement xattrs and inotify on /proc?
>> Or is there another way that would simplify maintenance?
>
> If proc supported setxattr, then I suppose early userspace could label
> it instead of the kernel needing to determine a label internally. But
> not sure how we'd cleanly migrate to avoid breakage with old userspace.
>
>
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
2008-09-19 16:58 ` david-gFPdbfVZQbY
@ 2008-09-19 17:07 ` Stephen Smalley
0 siblings, 0 replies; 126+ messages in thread
From: Stephen Smalley @ 2008-09-19 17:07 UTC (permalink / raw)
To: david
Cc: Eric W. Biederman, Andrew Morton, Paul Moore, jmorris, rjw,
linux-kernel, kernel-testers, netdev, Eric Paris
On Fri, 2008-09-19 at 09:58 -0700, david@lang.hm wrote:
> On Thu, 18 Sep 2008, Stephen Smalley wrote:
>
> > On Thu, 2008-09-18 at 11:09 -0700, Eric W. Biederman wrote:
> >> Stephen Smalley <sds@tycho.nsa.gov> writes:
> >>
> >>> On Thu, 2008-09-18 at 08:38 -0400, Stephen Smalley wrote:
> >>>> I do however think that the mantra that we can't require users to update
> >>>> policy for kernel changes is unsupportable in general. The precise set
> >>>> of permission checks on a given operation is not set in stone and it is
> >>>> not part of the kernel/userland interface/contract. Policy isn't
> >>>> "userspace"; it governs what userspace can do, and it has to adapt to
> >>>> kernel changes.
> >>>
> >>> I should note here that for changes to SELinux, we have gone out of our
> >>> way to avoid such breakage to date through the introduction of
> >>> compatibility switches, policy flags to enable any new checks, etc
> >>> (albeit at a cost in complexity and ever creeping compatibility code).
> >>> But changes to the rest of the kernel can just as easily alter the set
> >>> of permission checks that get applied on a given operation, and I don't
> >>> think we are always going to be able to guarantee that new kernel + old
> >>> policy will Just Work.
> >>
> >> I know of at least 2 more directories that I intend to turn into
> >> symlinks into somewhere under /proc/self. How do we keep from
> >> breaking selinux policies when I do that?
> >
> > I suspect we could tweak the logic in selinux_proc_get_sid() to always
> > label all symlinks under /proc with the base proc_t type already used
> > for e.g. /proc/self, at which point existing policies would be ok.
>
> so if proc is mounted anywhere other then /proc the selinux policy would
> do odd things?
No, the logic doesn't care where proc is mounted. Only the name
relative to the root of proc is used.
--
Stephen Smalley
National Security Agency
^ permalink raw reply [flat|nested] 126+ messages in thread
* Re: [Bug #11500] /proc/net bug related to selinux
[not found] ` <1221762850.24048.107.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2008-09-19 16:58 ` david-gFPdbfVZQbY
@ 2008-09-29 16:49 ` Stephen Smalley
1 sibling, 0 replies; 126+ messages in thread
From: Stephen Smalley @ 2008-09-29 16:49 UTC (permalink / raw)
To: Eric W. Biederman
Cc: Andrew Morton, Paul Moore, jmorris-gx6/JNMH7DfYtjvyW6yDsg,
rjw-KKrjLPT3xs0, linux-kernel-u79uwXL29TY76Z2rM5mHXA,
kernel-testers-u79uwXL29TY76Z2rM5mHXA,
netdev-u79uwXL29TY76Z2rM5mHXA, Eric Paris
On Thu, 2008-09-18 at 14:34 -0400, Stephen Smalley wrote:
> On Thu, 2008-09-18 at 11:09 -0700, Eric W. Biederman wrote:
> > Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org> writes:
> >
> > > On Thu, 2008-09-18 at 08:38 -0400, Stephen Smalley wrote:
> > >> I do however think that the mantra that we can't require users to update
> > >> policy for kernel changes is unsupportable in general. The precise set
> > >> of permission checks on a given operation is not set in stone and it is
> > >> not part of the kernel/userland interface/contract. Policy isn't
> > >> "userspace"; it governs what userspace can do, and it has to adapt to
> > >> kernel changes.
> > >
> > > I should note here that for changes to SELinux, we have gone out of our
> > > way to avoid such breakage to date through the introduction of
> > > compatibility switches, policy flags to enable any new checks, etc
> > > (albeit at a cost in complexity and ever creeping compatibility code).
> > > But changes to the rest of the kernel can just as easily alter the set
> > > of permission checks that get applied on a given operation, and I don't
> > > think we are always going to be able to guarantee that new kernel + old
> > > policy will Just Work.
> >
> > I know of at least 2 more directories that I intend to turn into
> > symlinks into somewhere under /proc/self. How do we keep from
> > breaking selinux policies when I do that?
>
> I suspect we could tweak the logic in selinux_proc_get_sid() to always
> label all symlinks under /proc with the base proc_t type already used
> for e.g. /proc/self, at which point existing policies would be ok.
FWIW, a fix for this issue has been applied to:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next
The particular commit can be viewed at:
http://git.kernel.org/?p=linux/kernel/git/jmorris/security-testing-2.6.git;a=commit;h=ea6b184f7d521a503ecab71feca6e4057562252b
This should address not only the /proc/net breakage but also any future
changes to turn existing directories into symlinks.
--
Stephen Smalley
National Security Agency
^ permalink raw reply [flat|nested] 126+ messages in thread
end of thread, other threads:[~2008-09-29 16:49 UTC | newest]
Thread overview: 126+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-12 18:59 2.6.27-rc6-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
2008-09-12 18:59 ` [Bug #11207] VolanoMark regression with 2.6.27-rc1 Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11220] Screen stays black after resume Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11210] libata badness Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11215] INFO: possible recursive locking detected ps2_command Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11224] Only three cores found on quad-core machine Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11230] Kconfig no longer outputs a .config with freshly updated defconfigs Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11237] corrupt PMD after resume Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11271] BUG: fealnx in 2.6.27-rc1 Rafael J. Wysocki
2008-09-13 8:47 ` Jaswinder Singh
2008-09-12 19:06 ` [Bug #11264] Invalid op opcode in kernel/workqueue Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11276] build error: CONFIG_OPTIMIZE_INLINING=y causes gcc 4.2 to do stupid things Rafael J. Wysocki
2008-09-12 20:46 ` Randy Dunlap
[not found] ` <48CAD51D.4060908-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2008-09-12 21:19 ` Rafael J. Wysocki
[not found] ` <200809122319.18633.rjw-KKrjLPT3xs0@public.gmane.org>
2008-09-17 14:26 ` Bjorn Helgaas
2008-09-12 19:06 ` [Bug #11272] BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835 Rafael J. Wysocki
2008-09-16 15:25 ` Jaswinder Singh
2008-09-12 19:06 ` [Bug #11335] 2.6.27-rc2-git5 BUG: unable to handle kernel paging request Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28 Rafael J. Wysocki
2008-09-12 22:05 ` Christoph Lameter
[not found] ` <48CAE7A0.8000004-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-13 11:44 ` Mike Galbraith
[not found] ` <1221306287.5213.111.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-13 11:57 ` Mike Galbraith
2008-09-14 6:24 ` Mike Galbraith
[not found] ` <1221373494.4979.1.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-14 7:02 ` Mike Galbraith
2008-09-14 14:18 ` Christoph Lameter
[not found] ` <48CD1D25.9080301-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-14 19:51 ` Mike Galbraith
[not found] ` <1221421907.4597.24.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-15 10:44 ` Mike Galbraith
[not found] ` <1221475440.4784.39.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-16 12:28 ` Mike Galbraith
[not found] ` <1221568105.5020.17.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-16 14:07 ` Ilpo Järvinen
2008-09-17 4:39 ` Mike Galbraith
2008-09-17 5:01 ` Mike Galbraith
[not found] ` <1221627676.5125.3.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-17 10:40 ` Ingo Molnar
[not found] ` <20080917104044.GC18764-X9Un+BFzKDI@public.gmane.org>
2008-09-17 11:41 ` Mike Galbraith
[not found] ` <1221651701.5102.17.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-17 12:49 ` Ingo Molnar
[not found] ` <20080917124943.GA7738-X9Un+BFzKDI@public.gmane.org>
2008-09-17 13:11 ` Mike Galbraith
[not found] ` <1221657111.5511.14.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-17 13:36 ` Ilpo Järvinen
[not found] ` <Pine.LNX.4.64.0809171629550.1034-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2008-09-17 13:57 ` Mike Galbraith
[not found] ` <1221659858.8818.13.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-17 17:04 ` Ilpo Järvinen
2008-09-18 7:12 ` Mike Galbraith
[not found] ` <1221721970.5003.9.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-18 7:25 ` Mike Galbraith
[not found] ` <1221722733.5149.6.camel-YqMYhexLQo1vAv1Ojkdn7Q@public.gmane.org>
2008-09-18 7:58 ` Ilpo Järvinen
2008-09-17 14:47 ` Eric Dumazet
[not found] ` <48D11871.4090805-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
2008-09-17 14:50 ` Eric Dumazet
2008-09-17 18:16 ` Mike Galbraith
2008-09-12 19:06 ` [Bug #11340] LTP overnight run resulted in unusable box Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11336] 2.6.27-rc2:stall while mounting root fs Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11380] lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16 Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11357] Can not boot up with zd1211rw USB-Wlan Stick Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11343] SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11404] BUG: in 2.6.23-rc3-git7 in do_cciss_intr Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11398] hda_intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj Rafael J. Wysocki
2008-09-13 7:37 ` Frans Pop
[not found] ` <200809130937.52685.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2008-09-13 17:23 ` Takashi Iwai
[not found] ` <s5habecm03s.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2008-09-15 0:13 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11463] sshd hangs on close Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11459] kernel crash after wifi connection established Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11465] Linux-2.6.27-rc5, drm errors in log Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11439] [2.6.27-rc4-git4] compilation warnings Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11407] suspend: unable to handle kernel paging request Rafael J. Wysocki
2008-09-12 20:50 ` Vegard Nossum
2008-09-12 19:06 ` [Bug #11442] btusb hibernation/suspend breakage in current -git Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11471] GPE storm detected, kernel freezes Rafael J. Wysocki
2008-09-16 5:50 ` Zhang Rui
2008-09-12 19:06 ` [Bug #11500] /proc/net bug related to selinux Rafael J. Wysocki
2008-09-12 22:14 ` James Morris
[not found] ` <alpine.LRH.1.10.0809130812460.12313-CK9fWmtY32x9JUWOpEiw7w@public.gmane.org>
2008-09-12 22:24 ` Andrew Morton
[not found] ` <20080912152443.c4e59f42.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-13 0:15 ` James Morris
[not found] ` <alpine.LRH.1.10.0809131012310.13073-CK9fWmtY32x9JUWOpEiw7w@public.gmane.org>
2008-09-13 19:37 ` Andrew Morton
[not found] ` <20080913123722.e238ae2a.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-15 0:16 ` Rafael J. Wysocki
2008-09-15 13:05 ` Stephen Smalley
[not found] ` <1221483926.30816.18.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2008-09-15 13:42 ` Stephen Smalley
2008-09-17 19:50 ` Andrew Morton
2008-09-17 21:24 ` Paul Moore
2008-09-17 21:39 ` Eric W. Biederman
[not found] ` <m1vdwu4fku.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-09-17 22:11 ` Andrew Morton
2008-09-17 21:48 ` Andrew Morton
2008-09-17 22:12 ` Paul Moore
2008-09-17 22:24 ` Andrew Morton
[not found] ` <20080917152407.76230f0c.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-17 22:53 ` Eric W. Biederman
[not found] ` <20080917144842.7df59f9e.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-17 22:32 ` Eric W. Biederman
2008-09-18 12:38 ` Stephen Smalley
2008-09-18 13:03 ` Stephen Smalley
2008-09-18 18:09 ` Eric W. Biederman
2008-09-18 18:34 ` Stephen Smalley
[not found] ` <1221762850.24048.107.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2008-09-19 16:58 ` david-gFPdbfVZQbY
2008-09-19 17:07 ` Stephen Smalley
2008-09-29 16:49 ` Stephen Smalley
[not found] ` <200809171724.36269.paul.moore-VXdhtT5mjnY@public.gmane.org>
2008-09-17 22:23 ` David Miller
[not found] ` <20080917125053.1f9ecf37.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-09-17 21:56 ` Eric W. Biederman
2008-09-12 19:06 ` [Bug #11485] 2.6.27-rc xen pvops regression? Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11476] failure to associate after resume from suspend to ram Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11501] Failed to open destination file: Permission deniedihex2fw Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11505] oltp ~10% regression with 2.6.27-rc5 on stoakley machine Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11507] usb: sometimes dead keyboard after boot Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11506] oops during unmount - ext3? (2.6.27-rc5) Rafael J. Wysocki
2008-09-19 16:17 ` Marcin Slusarz
2008-09-12 19:06 ` [Bug #11516] severe performance degradation on x86_64 going from 2.6.26-rc9 -> 2.6.27-rc5 Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11548] kernel BUG at drivers/pci/intel-iommu.c:1373! Rafael J. Wysocki
2008-09-12 20:56 ` Chris Mason
[not found] ` <1221252989.8709.11.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-09-12 21:21 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11547] build issue #565 for v2.6.27-rc5 : undefined reference to `ei_interrupt' in hp-plus.c Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11512] sort-of regression due to "kconfig: speed up all*config + randconfig" Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11549] 2.6.27-rc5 acpi: EC Storm error message on bootup Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11551] Semi-repeatable hard lockup on 2.6.27-rc6 Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11553] Strange looking line from "ps aux" Rafael J. Wysocki
2008-09-13 8:51 ` Alan Jenkins
2008-09-12 19:06 ` [Bug #11552] Disabling IRQ #23 Rafael J. Wysocki
2008-09-13 3:24 ` Justin Mattock
2008-09-12 19:06 ` [Bug #11554] Partition check considered as error is breaking mounting in 2.6.27 Rafael J. Wysocki
2008-09-13 23:37 ` Herton Ronaldo Krzesinski
[not found] ` <200809132037.55922.herton-4qZELD6Fgxg39yzSjRtAkw@public.gmane.org>
2008-09-15 0:25 ` Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11550] pnp: Huge number of "io resource overlap" messages Rafael J. Wysocki
2008-09-12 22:52 ` Rene Herman
2008-09-12 19:06 ` [Bug #11556] e100: PCI wake-up handling rework causes "Error clearing wake event" Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11559] 2.6.27-rc6: nohz + s2ram = need to press keys to get progress Rafael J. Wysocki
2008-09-12 19:06 ` [Bug #11557] Controlling backlight on thinkpad x60 Rafael J. Wysocki
2008-09-13 15:13 ` Matthew Garrett
[not found] ` <20080913151330.GA20761-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2008-09-14 10:18 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-09-06 21:24 2.6.27-rc5-git8: Reported regressions from 2.6.26 Rafael J. Wysocki
2008-09-06 21:30 ` [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path Rafael J. Wysocki
2008-08-30 19:46 2.6.27-rc5-git2: Reported regressions from 2.6.26 Rafael J. Wysocki
2008-08-30 19:50 ` [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path Rafael J. Wysocki
2008-08-31 8:41 ` Tobias Diedrich
[not found] ` <20080831084135.GA2698-LEnv4NkkRI/kz0gr9c1H3IV7twrRs5iQ@public.gmane.org>
2008-08-31 13:09 ` Tobias Diedrich
[not found] ` <20080831130904.GA4070-LEnv4NkkRI/kz0gr9c1H3IV7twrRs5iQ@public.gmane.org>
2008-08-31 18:02 ` Yinghai Lu
2008-08-23 18:07 2.6.27-rc4-git1: Reported regressions from 2.6.26 Rafael J. Wysocki
2008-08-23 18:10 ` [Bug #11358] net: forcedeth call restore mac addr in nv_shutdown path Rafael J. Wysocki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox