* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
@ 2005-04-05 7:21 ` Dave Airlie
2005-04-05 7:33 ` 2.6.12-rc2-mm1 Nick Piggin
` (16 subsequent siblings)
17 siblings, 0 replies; 84+ messages in thread
From: Dave Airlie @ 2005-04-05 7:21 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Well the DRI is, both reports of bugs have been fixed :-), the bug
should be closed on bugs.kernel.org I think, and it looks rock solid
on my box both FC3 and Debian sarge..
Dave.
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
2005-04-05 7:21 ` 2.6.12-rc2-mm1 Dave Airlie
@ 2005-04-05 7:33 ` Nick Piggin
2005-04-05 7:59 ` 2.6.12-rc2-mm1 Ingo Molnar
2005-04-05 18:51 ` 2.6.12-rc2-mm1 Siddha, Suresh B
2005-04-05 7:39 ` 2.6.12-rc2-mm1 Brice Goglin
` (15 subsequent siblings)
17 siblings, 2 replies; 84+ messages in thread
From: Nick Piggin @ 2005-04-05 7:33 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Andrew Morton wrote:
> +sched-remove-unnecessary-sched-domains.patch
> +sched-improve-pinned-task-handling-again.patch
[snip]
>
> CPU scheduler updates
>
It is no problem that you picked these up for testing. But
don't merge them yet, please.
Suresh's underlying problem with the unnecessary sched domains
is a failing of sched-balance-exec and sched-balance-fork, which
I am working on now.
Removing unnecessary domains is a nice optimisation, but just
needs to account for a few more flags before declaring that a
domain is unnecessary (not to mention this probably breaks if
isolcpus= is used). I have made some modifications to the patch
to fix these problems.
Lastly, I'd like to be a bit less intrusive with pinned task
handling improvements. I think we can do this while still being
effective in preventing livelocks.
I will keep you posted with regards to the various scheduler
patches.
--
SUSE Labs, Novell Inc.
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:33 ` 2.6.12-rc2-mm1 Nick Piggin
@ 2005-04-05 7:59 ` Ingo Molnar
2005-04-05 18:51 ` 2.6.12-rc2-mm1 Siddha, Suresh B
1 sibling, 0 replies; 84+ messages in thread
From: Ingo Molnar @ 2005-04-05 7:59 UTC (permalink / raw)
To: Nick Piggin; +Cc: Andrew Morton, linux-kernel
* Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Andrew Morton wrote:
>
> >+sched-remove-unnecessary-sched-domains.patch
> >+sched-improve-pinned-task-handling-again.patch
> [snip]
> >
> > CPU scheduler updates
> >
>
> It is no problem that you picked these up for testing. But
> don't merge them yet, please.
almost all current scheduler patches in -mm are post-2.6.12 items and
are conditional on testing feedback from the big boxes, but otherwise
have my conceptual ack. The only trivial one that would be fine for
2.6.12 is sched-uninline-task_timeslice.patch.
Ingo
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:33 ` 2.6.12-rc2-mm1 Nick Piggin
2005-04-05 7:59 ` 2.6.12-rc2-mm1 Ingo Molnar
@ 2005-04-05 18:51 ` Siddha, Suresh B
2005-04-05 23:42 ` 2.6.12-rc2-mm1 Nick Piggin
2005-04-06 17:11 ` 2.6.12-rc2-mm1 Nick Piggin
1 sibling, 2 replies; 84+ messages in thread
From: Siddha, Suresh B @ 2005-04-05 18:51 UTC (permalink / raw)
To: Nick Piggin; +Cc: Andrew Morton, linux-kernel
On Tue, Apr 05, 2005 at 05:33:49PM +1000, Nick Piggin wrote:
> Andrew Morton wrote:
>
> > +sched-remove-unnecessary-sched-domains.patch
> > +sched-improve-pinned-task-handling-again.patch
> [snip]
> >
> > CPU scheduler updates
> >
>
> It is no problem that you picked these up for testing. But
> don't merge them yet, please.
>
> Suresh's underlying problem with the unnecessary sched domains
> is a failing of sched-balance-exec and sched-balance-fork, which
That wasn't the only motivation. For example, on non-HT cpu's we shouldn't
be setting up SMT sched-domain, same with NUMA domains on non-NUMA systems.
> I am working on now.
>
> Removing unnecessary domains is a nice optimisation, but just
> needs to account for a few more flags before declaring that a
Can you elaborate when we require a domain with special flags but has
no or only one group in it.
> domain is unnecessary (not to mention this probably breaks if
> isolcpus= is used). I have made some modifications to the patch
I have tested my patch with "ioslcpus=" and it works just fine.
> to fix these problems.
>
> Lastly, I'd like to be a bit less intrusive with pinned task
> handling improvements. I think we can do this while still being
> effective in preventing livelocks.
We want to see this fixed. Please post your patch and I can let you know
the test results.
>
> I will keep you posted with regards to the various scheduler
> patches.
Nick, Can you post the patches you sent me earlier to this list?
thanks,
suresh
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 18:51 ` 2.6.12-rc2-mm1 Siddha, Suresh B
@ 2005-04-05 23:42 ` Nick Piggin
2005-04-06 17:11 ` 2.6.12-rc2-mm1 Nick Piggin
1 sibling, 0 replies; 84+ messages in thread
From: Nick Piggin @ 2005-04-05 23:42 UTC (permalink / raw)
To: Siddha, Suresh B; +Cc: Andrew Morton, linux-kernel
Siddha, Suresh B wrote:
> On Tue, Apr 05, 2005 at 05:33:49PM +1000, Nick Piggin wrote:
>>Suresh's underlying problem with the unnecessary sched domains
>>is a failing of sched-balance-exec and sched-balance-fork, which
>
>
> That wasn't the only motivation. For example, on non-HT cpu's we shouldn't
> be setting up SMT sched-domain, same with NUMA domains on non-NUMA systems.
>
Yep, sure. It is a good, if slight, optimisation. And I've also just
slightly extended your patch, so we don't have any domains if booting
with maxcpus=1
>
>>I am working on now.
>>
>>Removing unnecessary domains is a nice optimisation, but just
>>needs to account for a few more flags before declaring that a
>
>
> Can you elaborate when we require a domain with special flags but has
> no or only one group in it.
>
The SD_WAKE_* flags do not use groups, so it would be legitimate to
have a domain that has one of these set, with no groups.
>
>>domain is unnecessary (not to mention this probably breaks if
>>isolcpus= is used). I have made some modifications to the patch
>
>
> I have tested my patch with "ioslcpus=" and it works just fine.
>
OK, my apologies ;)
>
>>to fix these problems.
>>
>>Lastly, I'd like to be a bit less intrusive with pinned task
>>handling improvements. I think we can do this while still being
>>effective in preventing livelocks.
>
>
> We want to see this fixed. Please post your patch and I can let you know
> the test results.
>
I will try to get it working and tested tonight for you.
>
>>I will keep you posted with regards to the various scheduler
>>patches.
>
>
> Nick, Can you post the patches you sent me earlier to this list?
>
Yep, I'll post them.
--
SUSE Labs, Novell Inc.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 18:51 ` 2.6.12-rc2-mm1 Siddha, Suresh B
2005-04-05 23:42 ` 2.6.12-rc2-mm1 Nick Piggin
@ 2005-04-06 17:11 ` Nick Piggin
2005-04-08 1:08 ` 2.6.12-rc2-mm1 Siddha, Suresh B
1 sibling, 1 reply; 84+ messages in thread
From: Nick Piggin @ 2005-04-06 17:11 UTC (permalink / raw)
To: Siddha, Suresh B; +Cc: Andrew Morton, linux-kernel, Ingo Molnar
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
Siddha, Suresh B wrote:
> On Tue, Apr 05, 2005 at 05:33:49PM +1000, Nick Piggin wrote:
>
>>Lastly, I'd like to be a bit less intrusive with pinned task
>>handling improvements. I think we can do this while still being
>>effective in preventing livelocks.
>
>
> We want to see this fixed. Please post your patch and I can let you know
> the test results.
>
Using the attached patch, a puny dual PIII-650 with ~400MB RAM swapped
itself to death after 20000 infinite loop tasks had been pinned to one
of the CPUs. See how you go.
--
SUSE Labs, Novell Inc.
[-- Attachment #2: sched-relax-pinned-balancing.patch --]
[-- Type: text/plain, Size: 1148 bytes --]
Index: linux-2.6/kernel/sched.c
===================================================================
--- linux-2.6.orig/kernel/sched.c 2005-04-07 02:39:22.000000000 +1000
+++ linux-2.6/kernel/sched.c 2005-04-07 02:45:26.000000000 +1000
@@ -2041,6 +2041,12 @@ static runqueue_t *find_busiest_queue(st
}
/*
+ * Max backoff if we encounter pinned tasks. Pretty arbitrary value, but
+ * so long as it is large enough.
+ */
+#define MAX_PINNED_INTERVAL 1024
+
+/*
* Check this_cpu to ensure it is balanced within domain. Attempt to move
* tasks if there is an imbalance.
*
@@ -2052,7 +2058,7 @@ static int load_balance(int this_cpu, ru
struct sched_group *group;
runqueue_t *busiest;
unsigned long imbalance;
- int nr_moved, all_pinned;
+ int nr_moved, all_pinned = 0;
int active_balance = 0;
spin_lock(&this_rq->lock);
@@ -2143,7 +2149,8 @@ out_balanced:
sd->nr_balance_failed = 0;
/* tune up the balancing interval */
- if (sd->balance_interval < sd->max_interval)
+ if ((all_pinned && sd->balance_interval < MAX_PINNED_INTERVAL) ||
+ (sd->balance_interval < sd->max_interval))
sd->balance_interval *= 2;
return 0;
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-06 17:11 ` 2.6.12-rc2-mm1 Nick Piggin
@ 2005-04-08 1:08 ` Siddha, Suresh B
2005-04-08 2:28 ` 2.6.12-rc2-mm1 Nick Piggin
0 siblings, 1 reply; 84+ messages in thread
From: Siddha, Suresh B @ 2005-04-08 1:08 UTC (permalink / raw)
To: Nick Piggin; +Cc: Siddha, Suresh B, Andrew Morton, linux-kernel, Ingo Molnar
On Thu, Apr 07, 2005 at 03:11:12AM +1000, Nick Piggin wrote:
> Using the attached patch, a puny dual PIII-650 with ~400MB RAM swapped
> itself to death after 20000 infinite loop tasks had been pinned to one
> of the CPUs. See how you go.
Its goes well beyond the initial 7000 number I mentioned. Thanks.
One side-effect of this patch is: for example we have only two processes
running on a cpu and both are pinned to that cpu. If someone comes and
changes the affinity of one of these processes to all cpu's in the system,
then it might take MAX_PINNED_INTERVAL before this process moves to an idle cpu.
thanks,
suresh
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-08 1:08 ` 2.6.12-rc2-mm1 Siddha, Suresh B
@ 2005-04-08 2:28 ` Nick Piggin
0 siblings, 0 replies; 84+ messages in thread
From: Nick Piggin @ 2005-04-08 2:28 UTC (permalink / raw)
To: Siddha, Suresh B; +Cc: Andrew Morton, lkml, Ingo Molnar
On Thu, 2005-04-07 at 18:08 -0700, Siddha, Suresh B wrote:
> On Thu, Apr 07, 2005 at 03:11:12AM +1000, Nick Piggin wrote:
> > Using the attached patch, a puny dual PIII-650 with ~400MB RAM swapped
> > itself to death after 20000 infinite loop tasks had been pinned to one
> > of the CPUs. See how you go.
>
> Its goes well beyond the initial 7000 number I mentioned. Thanks.
>
OK, good thanks for testing that. I'll send it to Andrew.
> One side-effect of this patch is: for example we have only two processes
> running on a cpu and both are pinned to that cpu. If someone comes and
> changes the affinity of one of these processes to all cpu's in the system,
> then it might take MAX_PINNED_INTERVAL before this process moves to an idle cpu.
>
Yeah, that is true. OTOH it is a bit of a special case, and our
multiprocessor scheduling in general practically shuts down when
we have a situation with a single queue with a lot of pinned tasks.
What did I have for MAX_PINNED_INTERVAL? ~1second. I guess that could
come down a bit - maybe 1/4 or 1/2 a second? I think it is a "good
enough for now" kind of situation.
--
SUSE Labs, Novell Inc.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
2005-04-05 7:21 ` 2.6.12-rc2-mm1 Dave Airlie
2005-04-05 7:33 ` 2.6.12-rc2-mm1 Nick Piggin
@ 2005-04-05 7:39 ` Brice Goglin
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Andrew Morton
2005-04-05 8:30 ` 2.6.12-rc2-mm1 Ingo Molnar
2005-04-05 7:44 ` 2.6.12-rc2-mm1 Christoph Hellwig
` (14 subsequent siblings)
17 siblings, 2 replies; 84+ messages in thread
From: Brice Goglin @ 2005-04-05 7:39 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
Andrew Morton a écrit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
Hi Andrew,
printk timing seems broken.
It always shows [ 0.000000] on my Compaq Evo N600c.
dmesg and config attached.
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
DRI's working great here.
Regards,
Brice
[-- Attachment #2: config --]
[-- Type: text/plain, Size: 38288 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.12-rc2-mm1
# Tue Apr 5 09:08:02 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION="=LoulousMobile"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_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=y
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_FLATMEM=y
# CONFIG_DISCONTIGMEM is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set
CONFIG_SECCOMP=y
#
# Performance-monitoring counters support
#
# CONFIG_PERFCTR is not set
CONFIG_PHYSICAL_START=0x100000
CONFIG_KEXEC=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_DEBUG=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/hda4"
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_HOTKEY=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF 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=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE 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
#
# CPUFreq processor drivers
#
# CONFIG_X86_ACPI_CPUFREQ is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=y
# CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI is not set
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=y
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
#
# shared options
#
CONFIG_X86_SPEEDSTEP_LIB=y
# CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=m
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
# CONFIG_I82365 is not set
# CONFIG_TCIC is not set
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=m
#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=y
CONFIG_HOTPLUG_PCI_COMPAQ=y
CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM=y
# CONFIG_HOTPLUG_PCI_IBM is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_STANDALONE is not set
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_PC_PCMCIA is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_1284 is not set
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
# CONFIG_ISAPNP is not set
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y
CONFIG_PNPACPI=y
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE 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=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# 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_BLK_DEV_RAM_COUNT=16
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set
CONFIG_AOE_PARTITIONS=16
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
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=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 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_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
# CONFIG_IP_NF_FTP is not set
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
# CONFIG_IP_NF_MATCH_LIMIT is not set
# CONFIG_IP_NF_MATCH_IPRANGE is not set
# CONFIG_IP_NF_MATCH_MAC is not set
# CONFIG_IP_NF_MATCH_PKTTYPE is not set
# CONFIG_IP_NF_MATCH_MARK is not set
# CONFIG_IP_NF_MATCH_MULTIPORT is not set
# CONFIG_IP_NF_MATCH_TOS is not set
# CONFIG_IP_NF_MATCH_RECENT is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_DSCP is not set
# CONFIG_IP_NF_MATCH_AH_ESP is not set
# CONFIG_IP_NF_MATCH_LENGTH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_MATCH_TCPMSS is not set
# CONFIG_IP_NF_MATCH_HELPER is not set
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
# CONFIG_IP_NF_MATCH_OWNER is not set
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
# CONFIG_IP_NF_TARGET_ULOG is not set
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
# CONFIG_IP_NF_TARGET_REDIRECT is not set
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_ARPTABLES is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_KGDBOE is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
# CONFIG_HAMRADIO is not set
CONFIG_IRDA=m
#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
CONFIG_IRDA_ULTRA=y
#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
CONFIG_IRDA_DEBUG=y
#
# Infrared-port device drivers
#
#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m
#
# Dongle support
#
# CONFIG_DONGLE is not set
#
# Old SIR device drivers
#
CONFIG_IRPORT_SIR=m
#
# Old Serial dongle support
#
# CONFIG_DONGLE_OLD is not set
#
# FIR device drivers
#
# CONFIG_USB_IRDA is not set
# CONFIG_SIGMATEL_FIR is not set
# CONFIG_NSC_FIR is not set
# CONFIG_WINBOND_FIR is not set
# CONFIG_TOSHIBA_FIR is not set
# CONFIG_SMC_IRCC_FIR is not set
# CONFIG_ALI_FIR is not set
# CONFIG_VLSI_FIR is not set
# CONFIG_VIA_FIR is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_NET_SB1000 is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA 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_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS 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_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_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SKGE is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y
#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
# CONFIG_ARLAN is not set
# CONFIG_WAVELAN is not set
# CONFIG_PCMCIA_WAVELAN is not set
# CONFIG_PCMCIA_NETWAVE is not set
#
# Wireless 802.11 Frequency Hopping cards support
#
# CONFIG_PCMCIA_RAYCS is not set
#
# Wireless 802.11b ISA/PCI cards support
#
# CONFIG_AIRO is not set
CONFIG_HERMES=m
# CONFIG_PLX_HERMES is not set
# CONFIG_TMD_HERMES is not set
# CONFIG_PCI_HERMES is not set
# CONFIG_ATMEL is not set
#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
CONFIG_PCMCIA_HERMES=m
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set
#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
# CONFIG_PRISM54 is not set
# CONFIG_HOSTAP is not set
CONFIG_NET_WIRELESS=y
#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
# CONFIG_PCMCIA_3C589 is not set
# CONFIG_PCMCIA_3C574 is not set
# CONFIG_PCMCIA_FMVJ18X is not set
# CONFIG_PCMCIA_PCNET is not set
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
# CONFIG_PCMCIA_AXNET is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PLIP=m
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
# CONFIG_PPP_SYNC_TTY is not set
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPPOE is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=m
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
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_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_UINPUT is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_CS is not set
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
# CONFIG_NVRAM is not set
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# TPM devices
#
# CONFIG_TCG_TPM is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
#
# Video For Linux
#
#
# Video Adapters
#
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_STRADIS 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
#
# Radio Adapters
#
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SOFT_CURSOR=y
# CONFIG_FB_MACMODES is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
# CONFIG_FB_RADEON_I2C is not set
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# 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
#
# ISA devices
#
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# 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_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI 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_MAESTRO3=m
# CONFIG_SND_FM801 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_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_HDA_INTEL is not set
#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_VXP440 is not set
# CONFIG_SND_PDAUDIOCF is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_ITMTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC 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_PWC is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_ZD1201 is not set
CONFIG_USB_MON=m
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_BELKIN 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_VISOR=m
# 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_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_PL2303 is not set
# CONFIG_USB_SERIAL_SAFE 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_OMNINET is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_TEST is not set
#
# USB ATM/DSL drivers
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# InfiniBand support
#
# CONFIG_INFINIBAND 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_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
# CONFIG_REISERFS_FS_SECURITY is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
#
# XFS support
#
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
#
# Caches
#
# CONFIG_FSCACHE is not set
CONFIG_FUSE_FS=m
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_RELAYFS_FS=m
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp850"
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# 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
#
# Native Language Support
#
CONFIG_NLS=m
CONFIG_NLS_DEFAULT="iso8859-15"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_PRINTK_TIME=y
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_PAGE_OWNER is not set
CONFIG_DEBUG_FS=y
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
#
# Page alloc debug is incompatible with Software Suspend on i386
#
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
# CONFIG_KGDB is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Hardware crypto devices
#
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
[-- Attachment #3: dmesg --]
[-- Type: text/plain, Size: 15633 bytes --]
>[ 0.000000] PCI: Using ACPI for IRQ routing
[ 0.000000] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 0.000000] pnp: 00:0b: ioport range 0x140-0x14f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x4d0-0x4d1 has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1000-0x1087 could not be reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1100-0x113f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1200-0x121f has been reserved
[ 0.000000] Machine check exception polling timer started.
[ 0.000000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
[ 0.000000] apm: overridden by ACPI.
[ 0.000000] inotify device minor=63
[ 0.000000] devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
[ 0.000000] devfs: boot_options: 0x0
[ 0.000000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.000000] fakephp: Fake PCI Hot Plug Controller Driver
[ 0.000000] cpqphp: Compaq Hot Plug PCI Controller Driver version: 0.9.8
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BB] enabled at IRQ 11
[ 0.000000] PCI: setting IRQ 11 as level-triggered
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] radeonfb: Retreived PLL infos from BIOS
[ 0.000000] radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=166.00 MHz
[ 0.000000] radeonfb: PLL min 12000 max 35000
[ 0.000000] Non-DDC laptop panel detected
[ 0.000000] radeonfb: Monitor 1 type LCD found
[ 0.000000] radeonfb: Monitor 2 type no found
[ 0.000000] radeonfb: panel ID string: 1024x768
[ 0.000000] radeonfb: detected LVDS panel size from BIOS: 1024x768
[ 0.000000] radeondb: BIOS provided dividers will be used
[ 0.000000] radeonfb: Dynamic Clock Power Management enabled
[ 0.000000] Console: switching to colour frame buffer device 128x48
[ 0.000000] radeonfb (0000:01:00.0): ATI Radeon LY
[ 0.000000] ACPI: AC Adapter [C1A2] (off-line)
[ 0.000000] ACPI: Battery Slot [C19F] (battery present)
[ 0.000000] ACPI: Battery Slot [C1A0] (battery absent)
[ 0.000000] ACPI: Power Button (FF) [PWRF]
[ 0.000000] ACPI: Sleep Button (CM) [C1A3]
[ 0.000000] ACPI: Lid Switch [C1A4]
[ 0.000000] ACPI: Fan [C1F6] (off)
[ 0.000000] ACPI: Fan [C1F7] (off)
[ 0.000000] ACPI: Fan [C1F8] (off)
[ 0.000000] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[ 0.000000] ACPI: Thermal Zone [TZ1] (57 C)
[ 0.000000] Linux agpgart interface v0.101 (c) Dave Jones
[ 0.000000] agpgart: Detected an Intel 830M Chipset.
[ 0.000000] agpgart: AGP aperture is 256M @ 0x60000000
[ 0.000000] [drm] Initialized drm 1.0.0 20040925
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc Radeon Mobility M6 LY
[ 0.000000] PNP: PS/2 Controller [PNP0303:C171,PNP0f0e:C172] at 0x60,0x64 irq 1,12
[ 0.000000] i8042: probe of i8042 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for i8042
[ 0.000000] i8042.c: Detected active multiplexing controller, rev 1.1.
[ 0.000000] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.000000] Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
[ 0.000000] i8042: probe of serial8250 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for serial8250
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] io scheduler noop registered
[ 0.000000] io scheduler anticipatory registered
[ 0.000000] io scheduler deadline registered
[ 0.000000] io scheduler cfq registered
[ 0.000000] e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
[ 0.000000] e100: Copyright(c) 1999-2004 Intel Corporation
[ 0.000000] ACPI: PCI Interrupt Link [C0BE] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [C0BE] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] e100: eth0: e100_probe: addr 0x40100000, irq 11, MAC addr 00:02:A5:B5:03:7C
[ 0.000000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 0.000000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 0.000000] ICH3M: IDE controller at PCI slot 0000:00:1f.1
[ 0.000000] PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
[ 0.000000] ACPI: PCI Interrupt Link [C0BC] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] ICH3M: chipset revision 1
[ 0.000000] ICH3M: not 100% native mode: will probe irqs later
[ 0.000000] ide0: BM-DMA at 0x4060-0x4067, BIOS settings: hda:DMA, hdb:pio
[ 0.000000] ide1: BM-DMA at 0x4068-0x406f, BIOS settings: hdc:DMA, hdd:pio
[ 0.000000] Probing IDE interface ide0...
[ 0.000000] ACPI: No ACPI bus support for serio0
[ 0.000000] ACPI: No ACPI bus support for serio1
[ 0.000000] ACPI: No ACPI bus support for serio2
[ 0.000000] ACPI: No ACPI bus support for serio3
[ 0.000000] ACPI: No ACPI bus support for serio4
[ 0.000000] hda: IC25N020ATDA04-0, ATA DISK drive
[ 0.000000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 0.000000] ACPI: No ACPI bus support for 0.0
[ 0.000000] Probing IDE interface ide1...
[ 0.000000] hdc: Compaq DVD-ROM SD-C2402, ATAPI CD/DVD-ROM drive
[ 0.000000] ide1 at 0x170-0x177,0x376 on irq 15
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] ide2: I/O resource 0x3EE-0x3EE not free.
[ 0.000000] ide2: ports already in use, skipping probe
[ 0.000000] Probing IDE interface ide3...
[ 0.000000] Probing IDE interface ide4...
[ 0.000000] Probing IDE interface ide5...
[ 0.000000] hda: max request size: 128KiB
[ 0.000000] hda: 39070080 sectors (20003 MB) w/1806KiB Cache, CHS=38760/16/63, UDMA(100)
[ 0.000000] hda: cache flushes not supported
[ 0.000000] /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4
[ 0.000000] hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, DMA
[ 0.000000] Uniform CD-ROM driver Revision: 3.20
[ 0.000000] mice: PS/2 mouse device common for all mice
[ 0.000000] NET: Registered protocol family 2
[ 0.000000] IP: routing cache hash table of 8192 buckets, 64Kbytes
[ 0.000000] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.000000] NET: Registered protocol family 1
[ 0.000000] NET: Registered protocol family 17
[ 0.000000] PM: Checking swsusp image.
[ 0.000000] swsusp: Resume From Partition /dev/hda4
[ 0.000000] swsusp: Suspend partition has wrong signature?
[ 0.000000] swsusp: Error -22 check for resume file
[ 0.000000] PM: Resume from disk failed.
[ 0.000000] ACPI wakeup devices:
[ 0.000000] C052 C17E C185 C0A4 C0AA C19F C1A0 C1A3 C1A4
[ 0.000000] ACPI: (supports S0 S1 S3 S4 S4bios S5)
[ 0.000000] input: AT Translated Set 2 keyboard on isa0060/serio0
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3-fs: hda2: orphan cleanup on readonly fs
[ 0.000000] ext3_orphan_cleanup: deleting unreferenced inode 531194
[ 0.000000] ext3_orphan_cleanup: deleting unreferenced inode 531191
[ 0.000000] EXT3-fs: hda2: 2 orphan inodes deleted
[ 0.000000] EXT3-fs: recovery complete.
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] VFS: Mounted root (ext3 filesystem) readonly.
[ 0.000000] Freeing unused kernel memory: 176k freed
[ 0.000000] Synaptics Touchpad, model: 1
[ 0.000000] Firmware: 5.8
[ 0.000000] 180 degree mounted touchpad
[ 0.000000] Sensor: 27
[ 0.000000] new absolute packet format
[ 0.000000] Touchpad has extended capability bits
[ 0.000000] -> multifinger detection
[ 0.000000] -> palm detection
[ 0.000000] -> pass-through port
[ 0.000000] serio: Synaptics pass-through port at isa0060/serio4/input0
[ 0.000000] input: SynPS/2 Synaptics TouchPad on isa0060/serio4
[ 0.000000] atkbd: probe of serio5 failed with error -19
[ 0.000000] Adding 665272k swap on /dev/hda4. Priority:-1 extents:1
[ 0.000000] EXT3 FS on hda2, internal journal
[ 0.000000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
[ 0.000000] input: PS/2 Generic Mouse on synaptics-pt/serio0
[ 0.000000] psmouse: probe of serio5 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for serio5
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3 FS on hda3, internal journal
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0C0] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.0 [0e11:004e]
[ 0.000000] Yenta: Enabling burst memory read transactions
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.0, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000006
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.1[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.1 [0e11:004e]
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.1, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000010
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BA] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] usbcore: registered new driver usbfs
[ 0.000000] usbcore: registered new driver hub
[ 0.000000] USB Universal Host Controller Interface driver v2.2
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[ 0.000000] uhci_hcd 0000:00:1d.0: Intel Corporation 82801CA/CAM USB (Hub #1)
[ 0.000000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 0.000000] uhci_hcd 0000:00:1d.0: irq 11, io base 0x00004000
[ 0.000000] ACPI: No ACPI bus support for usb1
[ 0.000000] usbfs: probe of 1-0:1.0 failed with error -19
[ 0.000000] hub 1-0:1.0: USB hub found
[ 0.000000] hub 1-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 1-0:1.0 failed with error 0
[ 0.000000] usb: probe of 1-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 1-0:1.0
[ 0.000000] ACPI: PCI Interrupt Link [C0BD] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [C0BD] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[ 0.000000] uhci_hcd 0000:00:1d.1: Intel Corporation 82801CA/CAM USB (Hub #2)
[ 0.000000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[ 0.000000] uhci_hcd 0000:00:1d.1: irq 11, io base 0x00004020
[ 0.000000] ACPI: No ACPI bus support for usb2
[ 0.000000] usbfs: probe of 2-0:1.0 failed with error -19
[ 0.000000] hub 2-0:1.0: USB hub found
[ 0.000000] hub 2-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 2-0:1.0 failed with error 0
[ 0.000000] usb: probe of 2-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 2-0:1.0
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[ 0.000000] uhci_hcd 0000:00:1d.2: Intel Corporation 82801CA/CAM USB (Hub #3)
[ 0.000000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[ 0.000000] uhci_hcd 0000:00:1d.2: irq 11, io base 0x00004040
[ 0.000000] ACPI: No ACPI bus support for usb3
[ 0.000000] usbfs: probe of 3-0:1.0 failed with error -19
[ 0.000000] hub 3-0:1.0: USB hub found
[ 0.000000] hub 3-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 3-0:1.0 failed with error 0
[ 0.000000] usb: probe of 3-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 3-0:1.0
[ 0.000000] hw_random hardware driver 1.0.0 loaded
[ 0.000000] irda_init()
[ 0.000000] NET: Registered protocol family 23
[ 0.000000] parport: PnPBIOS parport detected.
[ 0.000000] parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
[ 0.000000] input: PC Speaker
[ 0.000000] Real Time Clock Driver v1.12
[ 0.000000] cs: memory probe 0x40000000-0x401fffff: excluding 0x40000000-0x4001ffff 0x40040000-0x4009ffff 0x400c0000-0x4011ffff 0x40140000-0x4019ffff 0x401c0000-0x401fffff
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] orinoco 0.14alpha2 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
[ 0.000000] orinoco_cs 0.14alpha2 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
[ 0.000000] eth1: Hardware identity 0001:0004:0005:0000
[ 0.000000] eth1: Station identity 001f:0001:0008:002a
[ 0.000000] eth1: Firmware determined as Lucent/Agere 8.42
[ 0.000000] eth1: Ad-hoc demo mode supported
[ 0.000000] eth1: IEEE standard IBSS ad-hoc mode supported
[ 0.000000] eth1: WEP supported, 104-bit key
[ 0.000000] eth1: MAC address 00:02:A5:6F:9E:14
[ 0.000000] eth1: Station name "HERMES I"
[ 0.000000] eth1: ready
[ 0.000000] eth1: index 0x01: Vcc 5.0, irq 3, io 0x2100-0x213f
[ 0.000000] eth1: New link status: Connected (0001)
[ 0.000000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[ 0.000000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
[ 0.000000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:39 ` 2.6.12-rc2-mm1 Brice Goglin
@ 2005-04-05 7:45 ` Andrew Morton
2005-04-05 7:59 ` 2.6.12-rc2-mm1 Brice Goglin
2005-04-07 17:00 ` 2.6.12-rc2-mm1 - printk timing broken Damir Perisa
2005-04-05 8:30 ` 2.6.12-rc2-mm1 Ingo Molnar
1 sibling, 2 replies; 84+ messages in thread
From: Andrew Morton @ 2005-04-05 7:45 UTC (permalink / raw)
To: Brice Goglin; +Cc: linux-kernel
Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
>
> Andrew Morton a écrit :
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> Hi Andrew,
>
> printk timing seems broken.
> It always shows [ 0.000000] on my Compaq Evo N600c.
What sort of CPU does that thing have? Please share the /proc/cpuinfo
output.
Does reverting
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
fix it?
Thanks.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Andrew Morton
@ 2005-04-05 7:59 ` Brice Goglin
2005-04-05 8:05 ` 2.6.12-rc2-mm1 Andrew Morton
2005-04-07 17:00 ` 2.6.12-rc2-mm1 - printk timing broken Damir Perisa
1 sibling, 1 reply; 84+ messages in thread
From: Brice Goglin @ 2005-04-05 7:59 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Andrew Morton a écrit :
> Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
>
>>Andrew Morton a écrit :
>> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>>
>> Hi Andrew,
>>
>> printk timing seems broken.
>> It always shows [ 0.000000] on my Compaq Evo N600c.
>
>
> What sort of CPU does that thing have? Please share the /proc/cpuinfo
> output.
It's a Mobile Pentium 3:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 11
model name : Intel(R) Pentium(R) III Mobile CPU 1000MHz
stepping : 1
cpu MHz : 996.763
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
cmov pat pse36 mmx fxsr sse
bogomips : 1977.25
> Does reverting
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
> fix it?
Yes!
Brice
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1 - printk timing broken
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Andrew Morton
2005-04-05 7:59 ` 2.6.12-rc2-mm1 Brice Goglin
@ 2005-04-07 17:00 ` Damir Perisa
1 sibling, 0 replies; 84+ messages in thread
From: Damir Perisa @ 2005-04-07 17:00 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Hi Andrew,
Le Tuesday 05 April 2005 09:45, Andrew Morton a écrit :
> Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
> > Andrew Morton a écrit :
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.
> > >12-rc2/2.6.12-rc2-mm1/
> >
> > Hi Andrew,
> >
> > printk timing seems broken.
> > It always shows [ 0.000000] on my Compaq Evo N600c.
>
> What sort of CPU does that thing have? Please share the /proc/cpuinfo
> output.
i can reproduce this "[ 0.000000]"-bug with a Thinkpad A31p with a P4M:
cpu family : 15
model : 2
model name : Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz
stepping : 7
cpu MHz : 1998.447
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
> Does reverting
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc
>2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_h
>pet-or-config_numa-systems.patch fix it?
for me too - yes
strange, because the cpu supports tsc as the flags indicate in the cpuinfo
i posted. hopefully this mystery is no more, soon ;-)
best regards,
Damir
--
Don't confuse things that need action with those that take care of
themselves.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:39 ` 2.6.12-rc2-mm1 Brice Goglin
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Andrew Morton
@ 2005-04-05 8:30 ` Ingo Molnar
2005-04-05 8:40 ` 2.6.12-rc2-mm1 Brice Goglin
1 sibling, 1 reply; 84+ messages in thread
From: Ingo Molnar @ 2005-04-05 8:30 UTC (permalink / raw)
To: Brice Goglin; +Cc: Andrew Morton, linux-kernel
* Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
> Andrew Morton a écrit :
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> Hi Andrew,
>
> printk timing seems broken.
> It always shows [ 0.000000] on my Compaq Evo N600c.
could you send the full bootlog (starting at the 'gcc...' line)? I'm not
sure whether TSC calibration was done on your CPU. If cyc2ns_scale is
not set up then sched_clock() will return 0, and this could result in
that printk symptom.
Ingo
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 8:30 ` 2.6.12-rc2-mm1 Ingo Molnar
@ 2005-04-05 8:40 ` Brice Goglin
2005-04-05 18:34 ` 2.6.12-rc2-mm1 Ingo Molnar
0 siblings, 1 reply; 84+ messages in thread
From: Brice Goglin @ 2005-04-05 8:40 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Andrew Morton, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Ingo Molnar a écrit :
> * Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
>
>
>>Andrew Morton a écrit :
>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>>
>>Hi Andrew,
>>
>>printk timing seems broken.
>>It always shows [ 0.000000] on my Compaq Evo N600c.
>
>
> could you send the full bootlog (starting at the 'gcc...' line)? I'm not
> sure whether TSC calibration was done on your CPU. If cyc2ns_scale is
> not set up then sched_clock() will return 0, and this could result in
> that printk symptom.
Here you are.
Brice
[-- Attachment #2: dmesg.full --]
[-- Type: text/plain, Size: 21437 bytes --]
1.4.1#16: restart.
klogd 1.4.1#16, log source = /proc/kmsg started.
Cannot find map file.
No module symbols loaded - kernel modules not enabled.
[4294667.296000] Linux version 2.6.12-rc2-mm1=LoulousMobile (bgoglin@puligny) (version gcc 3.3.5 (Debian 1:3.3.5-8)) #9 PREEMPT Tue Apr 5 09:28:57 CEST 2005
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000027fd0000 (usable)
[ 0.000000] BIOS-e820: 0000000027fd0000 - 0000000027ff0c00 (reserved)
[ 0.000000] BIOS-e820: 0000000027ff0c00 - 0000000027ffc000 (ACPI NVS)
[ 0.000000] BIOS-e820: 0000000027ffc000 - 0000000028000000 (reserved)
[ 0.000000] 639MB LOWMEM available.
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: PM-Timer IO Port: 0x1008
[ 0.000000] Allocating PCI resources starting at 28000000 (gap: 28000000:d8000000)
[ 0.000000] Built 1 zonelists
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
[ 0.000000] Initializing CPU#0
[ 0.000000] Kernel command line: root=/dev/hda2 ro
[ 0.000000] CPU 0 irqstacks, hard=c04a0000 soft=c049f000
[ 0.000000] PID hash table entries: 4096 (order: 12, 65536 bytes)
[ 0.000000] Detected 730.935 MHz processor.
[ 0.000000] Using pmtmr for high-res timesource
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 644672k/655168k available (2314k kernel code, 9976k reserved, 1191k data, 176k init, 0k highmem)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] CPU: L1 I cache: 16K, L1 D cache: 16K
[ 0.000000] CPU: L2 cache: 512K
[ 0.000000] Intel machine check architecture supported.
[ 0.000000] Intel machine check reporting enabled on CPU#0.
[ 0.000000] CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz stepping 01
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Checking 'hlt' instruction... OK.
[ 0.000000] tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired
[ 0.000000] Parsing all Control Methods:..........................................................................................................................................................................................................................................................................
[ 0.000000] Table [DSDT](id F006) - 833 Objects with 89 Devices 266 Methods 26 Regions
[ 0.000000] Parsing all Control Methods:.
[ 0.000000] Table [SSDT](id F003) - 3 Objects with 0 Devices 1 Methods 0 Regions
[ 0.000000] Parsing all Control Methods:..
[ 0.000000] Table [SSDT](id F004) - 4 Objects with 0 Devices 2 Methods 0 Regions
[ 0.000000] ACPI Namespace successfully loaded at root c04d56c0
[ 0.000000] ACPI: setting ELCR to 0200 (from 0800)
[ 0.000000] evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful
[ 0.000000] softlockup thread 0 started up.
[ 0.000000] NET: Registered protocol family 16
[ 0.000000] PCI: PCI BIOS revision 2.10 entry at 0xf04dd, last bus=4
[ 0.000000] PCI: Using configuration type 1
[ 0.000000] mtrr: v2.0 (20020519)
[ 0.000000] ACPI: Subsystem revision 20050309
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C13E (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C18F (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C1DC (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 00 to 0F [_GPE] 2 regs on int 0x9
[ 0.000000] evgpeblk-0987 [06] ev_create_gpe_block : Found 3 Wake, Enabled 1 Runtime GPEs in this block
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C13E (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C18F (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C1DC (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 10 to 1F [_GPE] 2 regs on int 0x9
[ 0.000000] evgpeblk-0987 [06] ev_create_gpe_block : Found 2 Wake, Enabled 5 Runtime GPEs in this block
[ 0.000000] Completing Region/Field/Buffer/Package initialization:..................................................................................................
[ 0.000000] Initialized 25/26 Regions 0/0 Fields 26/26 Buffers 47/56 Packages (849 nodes)
[ 0.000000] Executing all Device _STA and_INI methods:...........................................................................................
[ 0.000000] 91 Devices found containing: 91 _STA, 8 _INI methods
[ 0.000000] ACPI: Interpreter enabled
[ 0.000000] ACPI: Using PIC for interrupt routing
[ 0.000000] ACPI: PCI Root Bridge [C03E] (0000:00)
[ 0.000000] PCI: Probing PCI hardware (bus 00)
[ 0.000000] ACPI: Assume root bridge [\_SB_.C03E] segment is 0
[ 0.000000] ACPI: Assume root bridge [\_SB_.C03E] bus is 0
[ 0.000000] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
[ 0.000000] ACPI: Can't get handler for 0000:02:08.0
[ 0.000000] ACPI: Power Resource [C14E] (on)
[ 0.000000] ACPI: Power Resource [C167] (on)
[ 0.000000] ACPI: Power Resource [C16B] (on)
[ 0.000000] ACPI: Power Resource [C174] (on)
[ 0.000000] ACPI: PCI Interrupt Link [C0BA] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BB] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BC] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BD] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BE] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BF] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0C0] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0C1] (IRQs 5 10 11) *0, disabled.
[ 0.000000] ACPI: Power Resource [C1F3] (off)
[ 0.000000] ACPI: Power Resource [C1F4] (off)
[ 0.000000] ACPI: Power Resource [C1F5] (off)
[ 0.000000] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 0.000000] pnp: PnP ACPI init
[ 0.000000] ACPI: No ACPI bus support for 00:00
[ 0.000000] ACPI: No ACPI bus support for 00:01
[ 0.000000] ACPI: No ACPI bus support for 00:02
[ 0.000000] ACPI: No ACPI bus support for 00:03
[ 0.000000] ACPI: No ACPI bus support for 00:04
[ 0.000000] ACPI: No ACPI bus support for 00:05
[ 0.000000] ACPI: No ACPI bus support for 00:06
[ 0.000000] ACPI: No ACPI bus support for 00:07
[ 0.000000] ACPI: No ACPI bus support for 00:08
[ 0.000000] ACPI: No ACPI bus support for 00:09
[ 0.000000] ACPI: No ACPI bus support for 00:0a
[ 0.000000] ACPI: No ACPI bus support for 00:0b
[ 0.000000] ACPI: No ACPI bus support for 00:0c
[ 0.000000] ACPI: No ACPI bus support for 00:0d
[ 0.000000] pnp: PnP ACPI: found 14 devices
[ 0.000000] PnPBIOS: Disabled by ACPI PNP
[ 0.000000] SCSI subsystem initialized
[ 0.000000] PCI: Using ACPI for IRQ routing
[ 0.000000] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 0.000000] pnp: 00:0b: ioport range 0x140-0x14f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x4d0-0x4d1 has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1000-0x1087 could not be reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1100-0x113f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1200-0x121f has been reserved
[ 0.000000] Machine check exception polling timer started.
[ 0.000000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
[ 0.000000] apm: overridden by ACPI.
[ 0.000000] inotify device minor=63
[ 0.000000] devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
[ 0.000000] devfs: boot_options: 0x0
[ 0.000000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.000000] fakephp: Fake PCI Hot Plug Controller Driver
[ 0.000000] cpqphp: Compaq Hot Plug PCI Controller Driver version: 0.9.8
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BB] enabled at IRQ 11
[ 0.000000] PCI: setting IRQ 11 as level-triggered
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] radeonfb: Retreived PLL infos from BIOS
[ 0.000000] radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=166.00 MHz
[ 0.000000] radeonfb: PLL min 12000 max 35000
[ 0.000000] Non-DDC laptop panel detected
[ 0.000000] radeonfb: Monitor 1 type LCD found
[ 0.000000] radeonfb: Monitor 2 type no found
[ 0.000000] radeonfb: panel ID string: 1024x768
[ 0.000000] radeonfb: detected LVDS panel size from BIOS: 1024x768
[ 0.000000] radeondb: BIOS provided dividers will be used
[ 0.000000] radeonfb: Dynamic Clock Power Management enabled
[ 0.000000] Console: switching to colour frame buffer device 128x48
[ 0.000000] radeonfb (0000:01:00.0): ATI Radeon LY
[ 0.000000] ACPI: AC Adapter [C1A2] (off-line)
[ 0.000000] ACPI: Battery Slot [C19F] (battery present)
[ 0.000000] ACPI: Battery Slot [C1A0] (battery absent)
[ 0.000000] ACPI: Power Button (FF) [PWRF]
[ 0.000000] ACPI: Sleep Button (CM) [C1A3]
[ 0.000000] ACPI: Lid Switch [C1A4]
[ 0.000000] ACPI: Fan [C1F6] (off)
[ 0.000000] ACPI: Fan [C1F7] (off)
[ 0.000000] ACPI: Fan [C1F8] (off)
[ 0.000000] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[ 0.000000] ACPI: Thermal Zone [TZ1] (57 C)
[ 0.000000] Linux agpgart interface v0.101 (c) Dave Jones
[ 0.000000] agpgart: Detected an Intel 830M Chipset.
[ 0.000000] agpgart: AGP aperture is 256M @ 0x60000000
[ 0.000000] [drm] Initialized drm 1.0.0 20040925
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc Radeon Mobility M6 LY
[ 0.000000] PNP: PS/2 Controller [PNP0303:C171,PNP0f0e:C172] at 0x60,0x64 irq 1,12
[ 0.000000] i8042: probe of i8042 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for i8042
[ 0.000000] i8042.c: Detected active multiplexing controller, rev 1.1.
[ 0.000000] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.000000] Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
[ 0.000000] i8042: probe of serial8250 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for serial8250
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] io scheduler noop registered
[ 0.000000] io scheduler anticipatory registered
[ 0.000000] io scheduler deadline registered
[ 0.000000] io scheduler cfq registered
[ 0.000000] e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
[ 0.000000] e100: Copyright(c) 1999-2004 Intel Corporation
[ 0.000000] ACPI: PCI Interrupt Link [C0BE] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [C0BE] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] e100: eth0: e100_probe: addr 0x40100000, irq 11, MAC addr 00:02:A5:B5:03:7C
[ 0.000000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 0.000000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 0.000000] ICH3M: IDE controller at PCI slot 0000:00:1f.1
[ 0.000000] PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
[ 0.000000] ACPI: PCI Interrupt Link [C0BC] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] ICH3M: chipset revision 1
[ 0.000000] ICH3M: not 100%% native mode: will probe irqs later
[ 0.000000] ide0: BM-DMA at 0x4060-0x4067, BIOS settings: hda:DMA, hdb:pio
[ 0.000000] ide1: BM-DMA at 0x4068-0x406f, BIOS settings: hdc:DMA, hdd:pio
[ 0.000000] ACPI: No ACPI bus support for serio0
[ 0.000000] ACPI: No ACPI bus support for serio1
[ 0.000000] ACPI: No ACPI bus support for serio2
[ 0.000000] ACPI: No ACPI bus support for serio3
[ 0.000000] ACPI: No ACPI bus support for serio4
[ 0.000000] hda: IC25N020ATDA04-0, ATA DISK drive
[ 0.000000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 0.000000] ACPI: No ACPI bus support for 0.0
[ 0.000000] hdc: Compaq DVD-ROM SD-C2402, ATAPI CD/DVD-ROM drive
[ 0.000000] ide1 at 0x170-0x177,0x376 on irq 15
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] hda: max request size: 128KiB
[ 0.000000] hda: 39070080 sectors (20003 MB) w/1806KiB Cache, CHS=38760/16/63, UDMA(100)
[ 0.000000] hda: cache flushes not supported
[ 0.000000] /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4
[ 0.000000] hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, DMA
[ 0.000000] Uniform CD-ROM driver Revision: 3.20
[ 0.000000] mice: PS/2 mouse device common for all mice
[ 0.000000] NET: Registered protocol family 2
[ 0.000000] IP: routing cache hash table of 8192 buckets, 64Kbytes
[ 0.000000] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.000000] NET: Registered protocol family 1
[ 0.000000] NET: Registered protocol family 17
[ 0.000000] ACPI wakeup devices:
[ 0.000000] C052 C17E C185 C0A4 C0AA C19F C1A0 C1A3 C1A4
[ 0.000000] ACPI: (supports S0 S1 S3 S4 S4bios S5)
[ 0.000000] input: AT Translated Set 2 keyboard on isa0060/serio0
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3-fs: hda2: orphan cleanup on readonly fs
[ 0.000000] EXT3-fs: hda2: 2 orphan inodes deleted
[ 0.000000] EXT3-fs: recovery complete.
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] VFS: Mounted root (ext3 filesystem) readonly.
[ 0.000000] Freeing unused kernel memory: 176k freed
[ 0.000000] Synaptics Touchpad, model: 1
[ 0.000000] Firmware: 5.8
[ 0.000000] 180 degree mounted touchpad
[ 0.000000] Sensor: 27
[ 0.000000] new absolute packet format
[ 0.000000] Touchpad has extended capability bits
[ 0.000000] -> multifinger detection
[ 0.000000] -> palm detection
[ 0.000000] -> pass-through port
[ 0.000000] serio: Synaptics pass-through port at isa0060/serio4/input0
[ 0.000000] input: SynPS/2 Synaptics TouchPad on isa0060/serio4
[ 0.000000] atkbd: probe of serio5 failed with error -19
[ 0.000000] Adding 665272k swap on /dev/hda4. Priority:-1 extents:1
[ 0.000000] EXT3 FS on hda2, internal journal
[ 0.000000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
[ 0.000000] input: PS/2 Generic Mouse on synaptics-pt/serio0
[ 0.000000] psmouse: probe of serio5 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for serio5
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3 FS on hda3, internal journal
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0C0] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.0 [0e11:004e]
[ 0.000000] Yenta: Enabling burst memory read transactions
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.0, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000006
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.1[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.1 [0e11:004e]
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.1, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000010
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BA] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] usbcore: registered new driver usbfs
[ 0.000000] usbcore: registered new driver hub
[ 0.000000] USB Universal Host Controller Interface driver v2.2
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] uhci_hcd 0000:00:1d.0: Intel Corporation 82801CA/CAM USB (Hub #1)
[ 0.000000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 0.000000] uhci_hcd 0000:00:1d.0: irq 11, io base 0x00004000
[ 0.000000] ACPI: No ACPI bus support for usb1
[ 0.000000] usbfs: probe of 1-0:1.0 failed with error -19
[ 0.000000] hub 1-0:1.0: USB hub found
[ 0.000000] hub 1-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 1-0:1.0 failed with error 0
[ 0.000000] usb: probe of 1-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 1-0:1.0
[ 0.000000] ACPI: PCI Interrupt Link [C0BD] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [C0BD] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] uhci_hcd 0000:00:1d.1: Intel Corporation 82801CA/CAM USB (Hub #2)
[ 0.000000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[ 0.000000] uhci_hcd 0000:00:1d.1: irq 11, io base 0x00004020
[ 0.000000] ACPI: No ACPI bus support for usb2
[ 0.000000] usbfs: probe of 2-0:1.0 failed with error -19
[ 0.000000] hub 2-0:1.0: USB hub found
[ 0.000000] hub 2-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 2-0:1.0 failed with error 0
[ 0.000000] usb: probe of 2-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 2-0:1.0
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] uhci_hcd 0000:00:1d.2: Intel Corporation 82801CA/CAM USB (Hub #3)
[ 0.000000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[ 0.000000] uhci_hcd 0000:00:1d.2: irq 11, io base 0x00004040
[ 0.000000] ACPI: No ACPI bus support for usb3
[ 0.000000] usbfs: probe of 3-0:1.0 failed with error -19
[ 0.000000] hub 3-0:1.0: USB hub found
[ 0.000000] hub 3-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 3-0:1.0 failed with error 0
[ 0.000000] usb: probe of 3-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 3-0:1.0
[ 0.000000] hw_random hardware driver 1.0.0 loaded
[ 0.000000] NET: Registered protocol family 23
[ 0.000000] parport: PnPBIOS parport detected.
[ 0.000000] parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
[ 0.000000] input: PC Speaker
[ 0.000000] Real Time Clock Driver v1.12
[ 0.000000] cs: memory probe 0x40000000-0x401fffff: excluding 0x40000000-0x4001ffff 0x40040000-0x4009ffff 0x400c0000-0x4011ffff 0x40140000-0x4019ffff 0x401c0000-0x401fffff
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] eth1: New link status: Connected (0001)
[ 0.000000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[ 0.000000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
[ 0.000000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 8:40 ` 2.6.12-rc2-mm1 Brice Goglin
@ 2005-04-05 18:34 ` Ingo Molnar
2005-04-06 9:09 ` 2.6.12-rc2-mm1 Brice Goglin
0 siblings, 1 reply; 84+ messages in thread
From: Ingo Molnar @ 2005-04-05 18:34 UTC (permalink / raw)
To: Brice Goglin; +Cc: Andrew Morton, linux-kernel
* Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
> >could you send the full bootlog (starting at the 'gcc...' line)? I'm not
> >sure whether TSC calibration was done on your CPU. If cyc2ns_scale is
> >not set up then sched_clock() will return 0, and this could result in
> >that printk symptom.
>
> Here you are.
weird - none of the WARN_ON(1)'s show up. In particular, the
sched_clock() ones should have triggered at least once! I've attached a
new version of the patch below (please unapply the previous patch),
could you try it and send me the log? (It will unconditionally print
something in tsc_init(), which is always called during the boot
process.)
Ingo
--- linux/arch/i386/kernel/timers/timer_tsc.c.orig
+++ linux/arch/i386/kernel/timers/timer_tsc.c
@@ -137,16 +137,15 @@ static unsigned long long monotonic_cloc
unsigned long long sched_clock(void)
{
unsigned long long this_offset;
+ static int once = 1;
- /*
- * In the NUMA case we dont use the TSC as they are not
- * synchronized across all CPUs.
- */
-#ifndef CONFIG_NUMA
- if (!use_tsc)
-#endif
+ if (!cpu_has_tsc) {
+ if (once) { once = 0; WARN_ON(1); }
/* no locking but a rare wrong value is not a big deal */
return jiffies_64 * (1000000000 / HZ);
+ }
+
+ if (once) { once = 0; WARN_ON(1); }
/* Read the Time Stamp Counter */
rdtscll(this_offset);
@@ -434,7 +433,8 @@ static void mark_offset_tsc(void)
static int __init init_tsc(char* override)
{
-
+ printk("TSC init.\n");
+ WARN_ON(1);
/* check clock override */
if (override[0] && strncmp(override,"tsc",3)) {
#ifdef CONFIG_HPET_TIMER
@@ -443,6 +443,7 @@ static int __init init_tsc(char* overrid
} else
#endif
{
+ WARN_ON(1);
return -ENODEV;
}
}
@@ -518,8 +519,10 @@ static int __init init_tsc(char* overrid
}
set_cyc2ns_scale(cpu_khz/1000);
return 0;
- }
+ } else
+ WARN_ON(1);
}
+ WARN_ON(1);
return -ENODEV;
}
@@ -528,12 +531,14 @@ static int __init init_tsc(char* overrid
* in cpu/common.c */
static int __init tsc_setup(char *str)
{
+ WARN_ON(1);
tsc_disable = 1;
return 1;
}
#else
static int __init tsc_setup(char *str)
{
+ WARN_ON(1);
printk(KERN_WARNING "notsc: Kernel compiled with CONFIG_X86_TSC, "
"cannot disable TSC.\n");
return 1;
--- linux/arch/i386/kernel/timers/common.c.orig
+++ linux/arch/i386/kernel/timers/common.c
@@ -39,8 +39,10 @@ unsigned long __init calibrate_tsc(void)
/* Error: ECTCNEVERSET */
- if (count <= 1)
+ if (count <= 1) {
+ WARN_ON(1);
goto bad_ctc;
+ }
/* 64-bit subtract - gcc just messes up with long longs */
__asm__("subl %2,%0\n\t"
@@ -50,12 +52,16 @@ unsigned long __init calibrate_tsc(void)
"0" (endlow), "1" (endhigh));
/* Error: ECPUTOOFAST */
- if (endhigh)
+ if (endhigh) {
+ WARN_ON(1);
goto bad_ctc;
+ }
/* Error: ECPUTOOSLOW */
- if (endlow <= CALIBRATE_TIME)
+ if (endlow <= CALIBRATE_TIME) {
+ WARN_ON(1);
goto bad_ctc;
+ }
__asm__("divl %2"
:"=a" (endlow), "=d" (endhigh)
@@ -107,12 +113,16 @@ unsigned long __init calibrate_tsc_hpet(
"0" (tsc_endlow), "1" (tsc_endhigh));
/* Error: ECPUTOOFAST */
- if (tsc_endhigh)
+ if (tsc_endhigh) {
+ WARN_ON(1);
goto bad_calibration;
+ }
/* Error: ECPUTOOSLOW */
- if (tsc_endlow <= CALIBRATE_TIME_HPET)
+ if (tsc_endlow <= CALIBRATE_TIME_HPET) {
+ WARN_ON(1);
goto bad_calibration;
+ }
ASM_DIV64_REG(result, remain, tsc_endlow, 0, CALIBRATE_TIME_HPET);
if (remain > (tsc_endlow >> 1))
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 18:34 ` 2.6.12-rc2-mm1 Ingo Molnar
@ 2005-04-06 9:09 ` Brice Goglin
0 siblings, 0 replies; 84+ messages in thread
From: Brice Goglin @ 2005-04-06 9:09 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Andrew Morton, linux-kernel
Ingo Molnar a écrit :
> weird - none of the WARN_ON(1)'s show up. In particular, the
> sched_clock() ones should have triggered at least once! I've attached a
> new version of the patch below (please unapply the previous patch),
> could you try it and send me the log? (It will unconditionally print
> something in tsc_init(), which is always called during the boot
> process.)
Hi Ingo,
The result is exactly the same, except the following lines at the
begining of dmesg. Note that only these lines have a valid timestamp.
All remaining lines show 0.000.
[4294667.296000] Linux version 2.6.12-rc2-mm1=LoulousMobile
(bgoglin@puligny) (version gcc 3.3.5 (Debian 1:3.3.5-8)) #9 PREEMPT Tue
Apr 5 09:28:57 CEST 2005
[4294667.296000] Badness in sched_clock at
arch/i386/kernel/timers/timer_tsc.c:143
[4294667.296000] [<c010f464>] sched_clock+0x84/0x110
[4294667.296000] [<c01d7b5b>] vscnprintf+0x2b/0x40
[4294667.296000] [<c011e252>] vprintk+0xa2/0x260
[4294667.296000] [<c011e1a7>] printk+0x17/0x20
[4294667.296000] [<c046f6f4>] start_kernel+0x14/0x180
[4294667.296000] art_kernel+0x14/0x180
Brice
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (2 preceding siblings ...)
2005-04-05 7:39 ` 2.6.12-rc2-mm1 Brice Goglin
@ 2005-04-05 7:44 ` Christoph Hellwig
2005-04-05 9:07 ` 2.6.12-rc2-mm1 Dave Airlie
2005-04-05 9:11 ` 2.6.12-rc2-mm1 Paul Mackerras
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Christoph Hellwig
` (13 subsequent siblings)
17 siblings, 2 replies; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 7:44 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> +officially-deprecate-register_ioctl32_conversion.patch
>
> deprecate a compat function (mainly affects DRI)
Those DRI callers aren't in mainline but introduced in bk-drm.patch,
looks like the DRI folks need beating with a big stick..
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:44 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 9:07 ` Dave Airlie
2005-04-05 9:20 ` 2.6.12-rc2-mm1 Paul Mackerras
2005-04-05 9:11 ` 2.6.12-rc2-mm1 Paul Mackerras
1 sibling, 1 reply; 84+ messages in thread
From: Dave Airlie @ 2005-04-05 9:07 UTC (permalink / raw)
To: Christoph Hellwig, Andrew Morton, linux-kernel, Paul Mackerras
On Apr 5, 2005 5:44 PM, Christoph Hellwig <hch@infradead.org> wrote:
> On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> > +officially-deprecate-register_ioctl32_conversion.patch
> >
> > deprecate a compat function (mainly affects DRI)
>
> Those DRI callers aren't in mainline but introduced in bk-drm.patch,
> looks like the DRI folks need beating with a big stick..
Paulus these look like your patches care to update them with the "new"
method of doing stuff..
Deprecating would be no fun if the DRI didn't produce a bucket of
warnings every time..
Dave.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:07 ` 2.6.12-rc2-mm1 Dave Airlie
@ 2005-04-05 9:20 ` Paul Mackerras
2005-04-05 9:25 ` 2.6.12-rc2-mm1 Dave Airlie
` (2 more replies)
0 siblings, 3 replies; 84+ messages in thread
From: Paul Mackerras @ 2005-04-05 9:20 UTC (permalink / raw)
To: Dave Airlie; +Cc: Christoph Hellwig, Andrew Morton, linux-kernel
Dave Airlie writes:
> Paulus these look like your patches care to update them with the "new"
> method of doing stuff..
What are we going to do about the DRM CVS? Change it to the new way
and break everyone running 2.6.10 or earlier, or leave it at the old
way that will work for people with distro kernels, and have a
divergence between it and what's in the kernel?
Also, the compat_ioctl method is called without the BKL held, unlike
the ioctl method. What impact will that have? Do we need to take the
BKL in the compat_ioctl method?
Paul.
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 9:20 ` 2.6.12-rc2-mm1 Paul Mackerras
@ 2005-04-05 9:25 ` Dave Airlie
2005-04-05 9:30 ` 2.6.12-rc2-mm1 Christoph Hellwig
2005-04-05 9:33 ` 2.6.12-rc2-mm1 Arjan van de Ven
2 siblings, 0 replies; 84+ messages in thread
From: Dave Airlie @ 2005-04-05 9:25 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Christoph Hellwig, Andrew Morton, linux-kernel
>
> > Paulus these look like your patches care to update them with the "new"
> > method of doing stuff..
>
> What are we going to do about the DRM CVS? Change it to the new way
> and break everyone running 2.6.10 or earlier, or leave it at the old
> way that will work for people with distro kernels, and have a
> divergence between it and what's in the kernel?
Yet more backwards compatibility is more than likely going to be
needed, but if it is a biggie I'd be happy to drop the older 32/64-bit
stuff from CVS and make it contingent on having 2.6.11 or greater as
it is a new feature anyways and hasn't seen a release yet...
>
> Also, the compat_ioctl method is called without the BKL held, unlike
> the ioctl method. What impact will that have? Do we need to take the
> BKL in the compat_ioctl method?
I don't think so as the DRM has its own locking that handles most of
the issues at a higher level... I've been thinking of switching DRM to
ioctl_unlocked but I'd really want someone with an SMP system to beat
on it .. (not that the DRI has a great record on SMP anyways..)
Dave.
Dave.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:20 ` 2.6.12-rc2-mm1 Paul Mackerras
2005-04-05 9:25 ` 2.6.12-rc2-mm1 Dave Airlie
@ 2005-04-05 9:30 ` Christoph Hellwig
2005-04-05 9:44 ` 2.6.12-rc2-mm1 Paul Mackerras
2005-04-05 9:33 ` 2.6.12-rc2-mm1 Arjan van de Ven
2 siblings, 1 reply; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 9:30 UTC (permalink / raw)
To: Paul Mackerras
Cc: Dave Airlie, Christoph Hellwig, Andrew Morton, linux-kernel
Btw, some more comments on the 32bit compat code in drm:
- instead of set_fs & co and passing kernel addresses to drm_ioctl
please use compat_alloc_user_space()
- this:
+ifeq ($(CONFIG_COMPAT),y)
+drm-objs += drm_ioc32.o
+radeon-objs += radeon_ioc32.o
+endif
should be written as
drm-$(CONFIG_COMPAT) += drm_ioc32.o
radeon-$(CONFIG_COMPAT) += radeon_ioc32.o
and everything else should use foo-y instead of foo-objs
- the magic CONFIG_COMPAT changes for SHM handles should only be done when
a module is set. CONFIG_COMPAT is set for mostly 64bit systems that can
run 32bit code and drm shouldn't behave differently just because we can
run 32bit code.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:30 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 9:44 ` Paul Mackerras
2005-04-05 9:45 ` 2.6.12-rc2-mm1 Christoph Hellwig
0 siblings, 1 reply; 84+ messages in thread
From: Paul Mackerras @ 2005-04-05 9:44 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Dave Airlie, Andrew Morton, linux-kernel
Christoph Hellwig writes:
> - the magic CONFIG_COMPAT changes for SHM handles should only be done when
> a module is set. CONFIG_COMPAT is set for mostly 64bit systems that can
> run 32bit code and drm shouldn't behave differently just because we can
> run 32bit code.
Yes it should - we can have a 64-bit X server and a 32-bit DRI
client. In this case the server will allocate a _DRM_SHM area and
pass the handle to the client, which will then try to mmap the area.
If we give a 64-bit handle to the server the client won't be able to
access the area.
Paul.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:44 ` 2.6.12-rc2-mm1 Paul Mackerras
@ 2005-04-05 9:45 ` Christoph Hellwig
2005-04-05 9:51 ` 2.6.12-rc2-mm1 Paul Mackerras
0 siblings, 1 reply; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 9:45 UTC (permalink / raw)
To: Paul Mackerras
Cc: Christoph Hellwig, Dave Airlie, Andrew Morton, linux-kernel
On Tue, Apr 05, 2005 at 07:44:38PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > - the magic CONFIG_COMPAT changes for SHM handles should only be done when
> > a module is set. CONFIG_COMPAT is set for mostly 64bit systems that can
> > run 32bit code and drm shouldn't behave differently just because we can
> > run 32bit code.
>
> Yes it should - we can have a 64-bit X server and a 32-bit DRI
> client. In this case the server will allocate a _DRM_SHM area and
> pass the handle to the client, which will then try to mmap the area.
> If we give a 64-bit handle to the server the client won't be able to
> access the area.
Please make it a module option so it doesn't regress everyone for your
specific needs.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:45 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 9:51 ` Paul Mackerras
2005-04-05 9:54 ` 2.6.12-rc2-mm1 Christoph Hellwig
0 siblings, 1 reply; 84+ messages in thread
From: Paul Mackerras @ 2005-04-05 9:51 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Dave Airlie, Andrew Morton, linux-kernel
Christoph Hellwig writes:
> Please make it a module option so it doesn't regress everyone for your
> specific needs.
Sorry, I don't follow you.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:51 ` 2.6.12-rc2-mm1 Paul Mackerras
@ 2005-04-05 9:54 ` Christoph Hellwig
2005-04-05 9:58 ` 2.6.12-rc2-mm1 Dave Airlie
2005-04-05 9:58 ` 2.6.12-rc2-mm1 Paul Mackerras
0 siblings, 2 replies; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 9:54 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Dave Airlie, Andrew Morton, linux-kernel
On Tue, Apr 05, 2005 at 07:51:57PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > Please make it a module option so it doesn't regress everyone for your
> > specific needs.
>
> Sorry, I don't follow you.
E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
in for running i386 apps. But I don't want dri to hand out 32bit handles
everywhere just because of that, because I most certainly won't be running
i386 OpenGL apps.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:54 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 9:58 ` Dave Airlie
2005-04-05 10:03 ` 2.6.12-rc2-mm1 Christoph Hellwig
2005-04-05 9:58 ` 2.6.12-rc2-mm1 Paul Mackerras
1 sibling, 1 reply; 84+ messages in thread
From: Dave Airlie @ 2005-04-05 9:58 UTC (permalink / raw)
To: Christoph Hellwig, Paul Mackerras, Dave Airlie, Andrew Morton,
linux-kernel
>
> E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
> in for running i386 apps. But I don't want dri to hand out 32bit handles
> everywhere just because of that, because I most certainly won't be running
> i386 OpenGL apps.
>
It doesn't actually matter what size the handles are from what I
understand of this... as long as they are hashed properly.. I've been
thinking of changing the handle from something with meaning to a hash
just to find out some more bugs.. even on plain 32-bit systems..
Dave.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:58 ` 2.6.12-rc2-mm1 Dave Airlie
@ 2005-04-05 10:03 ` Christoph Hellwig
0 siblings, 0 replies; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 10:03 UTC (permalink / raw)
To: Dave Airlie
Cc: Christoph Hellwig, Paul Mackerras, Andrew Morton, linux-kernel
On Tue, Apr 05, 2005 at 07:58:19PM +1000, Dave Airlie wrote:
> >
> > E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
> > in for running i386 apps. But I don't want dri to hand out 32bit handles
> > everywhere just because of that, because I most certainly won't be running
> > i386 OpenGL apps.
> >
>
> It doesn't actually matter what size the handles are from what I
> understand of this... as long as they are hashed properly.. I've been
> thinking of changing the handle from something with meaning to a hash
> just to find out some more bugs.. even on plain 32-bit systems..
Or, I though the handle was related to the dma_mask somewhat. I'll take
all flames on this subject back and apologize for not researching the subject
better, although I still think it's not a good idea to have a different
handle format depending on whether CONFIG_COMPAT is set or not.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:54 ` 2.6.12-rc2-mm1 Christoph Hellwig
2005-04-05 9:58 ` 2.6.12-rc2-mm1 Dave Airlie
@ 2005-04-05 9:58 ` Paul Mackerras
1 sibling, 0 replies; 84+ messages in thread
From: Paul Mackerras @ 2005-04-05 9:58 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Dave Airlie, Andrew Morton, linux-kernel
Christoph Hellwig writes:
> E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
> in for running i386 apps. But I don't want dri to hand out 32bit handles
> everywhere just because of that, because I most certainly won't be running
> i386 OpenGL apps.
The handle for a _DRM_SHM area is almost completely arbitrary, why do
you care whether it fits in 32 bits or not? All that matters is that
you can take the handle you get and use it as the offset in an mmap
call. The CONFIG_COMPAT changes don't break 64-bit clients.
Paul.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:20 ` 2.6.12-rc2-mm1 Paul Mackerras
2005-04-05 9:25 ` 2.6.12-rc2-mm1 Dave Airlie
2005-04-05 9:30 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 9:33 ` Arjan van de Ven
2 siblings, 0 replies; 84+ messages in thread
From: Arjan van de Ven @ 2005-04-05 9:33 UTC (permalink / raw)
To: Paul Mackerras
Cc: Dave Airlie, Christoph Hellwig, Andrew Morton, linux-kernel
On Tue, 2005-04-05 at 19:20 +1000, Paul Mackerras wrote:
> Dave Airlie writes:
>
> > Paulus these look like your patches care to update them with the "new"
> > method of doing stuff..
>
> What are we going to do about the DRM CVS? Change it to the new way
> and break everyone running 2.6.10 or earlier, or leave it at the old
> way that will work for people with distro kernels, and have a
> divergence between it and what's in the kernel?
(some distros like Fedora Core have modern kernels even for older
releases)
> Also, the compat_ioctl method is called without the BKL held, unlike
> the ioctl method. What impact will that have? Do we need to take the
> BKL in the compat_ioctl method?
How much does DRM actually depend on the BKL? I would hope not too
much...
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:44 ` 2.6.12-rc2-mm1 Christoph Hellwig
2005-04-05 9:07 ` 2.6.12-rc2-mm1 Dave Airlie
@ 2005-04-05 9:11 ` Paul Mackerras
2005-04-05 9:12 ` 2.6.12-rc2-mm1 Christoph Hellwig
1 sibling, 1 reply; 84+ messages in thread
From: Paul Mackerras @ 2005-04-05 9:11 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Andrew Morton, Dave Airlie, linux-kernel
Christoph Hellwig writes:
> Those DRI callers aren't in mainline but introduced in bk-drm.patch,
> looks like the DRI folks need beating with a big stick..
Settle down Christoph, the compat_ioctl method is less than 3 months
old, has only been in one official 2.6.x release, and isn't documented
at all in the Documentation directory AFAICS. Don't be so impatient.
Anyway, I did the 32-bit ioctl conversion stuff for the DRM. I'll
look at changing it to use compat_ioctl. The big question of course
is whether the DRM code will work correctly without the BKL held.
Paul.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:11 ` 2.6.12-rc2-mm1 Paul Mackerras
@ 2005-04-05 9:12 ` Christoph Hellwig
2005-04-05 9:35 ` 2.6.12-rc2-mm1 Paul Mackerras
0 siblings, 1 reply; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 9:12 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Andrew Morton, Dave Airlie, linux-kernel
On Tue, Apr 05, 2005 at 07:11:26PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > Those DRI callers aren't in mainline but introduced in bk-drm.patch,
> > looks like the DRI folks need beating with a big stick..
>
> Settle down Christoph, the compat_ioctl method is less than 3 months
> old, has only been in one official 2.6.x release, and isn't documented
> at all in the Documentation directory AFAICS. Don't be so impatient.
It's documented where the other filesystem entry points are documented.
This is not about beeing impatient but about adding APIs that at the same
time are actively removed all over the tree.
> Anyway, I did the 32-bit ioctl conversion stuff for the DRM. I'll
> look at changing it to use compat_ioctl. The big question of course
> is whether the DRM code will work correctly without the BKL held.
You can of course take the BKL inside your ->compat_ioctl method.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:12 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 9:35 ` Paul Mackerras
2005-04-05 9:36 ` 2.6.12-rc2-mm1 Christoph Hellwig
0 siblings, 1 reply; 84+ messages in thread
From: Paul Mackerras @ 2005-04-05 9:35 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Andrew Morton, Dave Airlie, linux-kernel
Christoph Hellwig writes:
> It's documented where the other filesystem entry points are documented.
Which is?
$ grep -r compat_ioctl Documentation
Documentation/filesystems/Locking: long (*compat_ioctl) (struct file *, unsigned int, unsigned long);
Documentation/filesystems/Locking:compat_ioctl: no
Marvellous documentation, that. :)
> This is not about beeing impatient but about adding APIs that at the same
> time are actively removed all over the tree.
Sure, just don't be so impatient... :)
> You can of course take the BKL inside your ->compat_ioctl method.
Yes, the question is whether we need to or not.
Paul.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 9:35 ` 2.6.12-rc2-mm1 Paul Mackerras
@ 2005-04-05 9:36 ` Christoph Hellwig
0 siblings, 0 replies; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 9:36 UTC (permalink / raw)
To: Paul Mackerras
Cc: Christoph Hellwig, Andrew Morton, Dave Airlie, linux-kernel
On Tue, Apr 05, 2005 at 07:35:46PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > It's documented where the other filesystem entry points are documented.
>
> Which is?
>
> $ grep -r compat_ioctl Documentation
> Documentation/filesystems/Locking: long (*compat_ioctl) (struct file *, unsigned int, unsigned long);
> Documentation/filesystems/Locking:compat_ioctl: no
>
> Marvellous documentation, that. :)
The other methods don't have much more documentation either ;-)
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (3 preceding siblings ...)
2005-04-05 7:44 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 7:45 ` Christoph Hellwig
2005-04-05 7:51 ` 2.6.12-rc2-mm1 Andrew Morton
2005-04-05 16:48 ` 2.6.12-rc2-mm1 David Woodhouse
2005-04-05 8:18 ` 2.6.12-rc2-mm1 Brice Goglin
` (12 subsequent siblings)
17 siblings, 2 replies; 84+ messages in thread
From: Christoph Hellwig @ 2005-04-05 7:45 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
> bk-audit.patch
This introduces various AUDIT_ARCH numerical constants, which is a blatantly
stupid idea. We already have a way to uniquely identify architectures, and
that's the ELF headers, no need for another parallel namespace.
(btw, could you please add to all patches who's responsible for them,
bk-audit.patch doesn't tell)
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 7:51 ` Andrew Morton
2005-04-05 16:48 ` 2.6.12-rc2-mm1 David Woodhouse
1 sibling, 0 replies; 84+ messages in thread
From: Andrew Morton @ 2005-04-05 7:51 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: linux-kernel
Christoph Hellwig <hch@infradead.org> wrote:
>
> (btw, could you please add to all patches who's responsible for them,
> bk-audit.patch doesn't tell)
It's supposed to, but if I have to fix rejects and refresh the patch, I
lose that info. Right now, bk-audit stomps on bk-ia64, so we lost the info.
I'll finally get around to fixing that up right now.
Anyway. dwmw2.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Christoph Hellwig
2005-04-05 7:51 ` 2.6.12-rc2-mm1 Andrew Morton
@ 2005-04-05 16:48 ` David Woodhouse
1 sibling, 0 replies; 84+ messages in thread
From: David Woodhouse @ 2005-04-05 16:48 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Andrew Morton, linux-kernel
On Tue, 2005-04-05 at 08:45 +0100, Christoph Hellwig wrote:
> This introduces various AUDIT_ARCH numerical constants, which is a blatantly
> stupid idea. We already have a way to uniquely identify architectures, and
> that's the ELF headers, no need for another parallel namespace.
We do use the EM_xxx number space but that isn't sufficient to
distinguish between 32-bit and 64-bit incarnations of certain machine
types (S390,SH,MIPS,...). I didn't much like adding it either, but
couldn't see a better option.
I pondered strings but we want to filter on this and don't want to have
to use strcmp. Got any better answers?
> (btw, could you please add to all patches who's responsible for them,
> bk-audit.patch doesn't tell)
If it were just to point to the BK tree, that might help.
( linux-audit.bkbits.net/audit-2.6-mm )
--
dwmw2
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (4 preceding siblings ...)
2005-04-05 7:45 ` 2.6.12-rc2-mm1 Christoph Hellwig
@ 2005-04-05 8:18 ` Brice Goglin
2005-04-05 8:46 ` 2.6.12-rc2-mm1 Rafael J. Wysocki
` (11 subsequent siblings)
17 siblings, 0 replies; 84+ messages in thread
From: Brice Goglin @ 2005-04-05 8:18 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Andrew Morton a écrit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
I'm sorry, I did not follow this "PM resume broken" thread.
But, suspend to disk does not work here, at least since 2.6.12-rc1-mm4
(I can't be sure about other releases, I don't use suspend-to-disk
intensively).
Basically, "Freeing memory" looks much slower than before but suspend
finally looks ok.
When resuming, it says it's restarting tasks. But actually it does not
resume anyone of my real applications.
Here's a part of what I see with rc2-mm1:
input: AT Translated Set 2 keyboard on isa0060/serio0
Stopping tasks: =<6>Synaptics Touchpad, model: 1
Firmware: 5.8
180 degree mounted touchpad
[...]
-> pass-through port
serio: Synaptics pass-through port at isa0060/serio4/input0
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
atkbd: probe of serio5 failed with error -19
input: PS/2 Generic Mouse on synaptics-pt/serio0
Restarting tasks...<6> Strange, kseriod not stopped
done
Actually, most of these lines appear when booting a fresh kernel.
The resume-specific ones are "Stopping tasks", "Restarting tasks"
and "Strange, kseriod not stopped".
Brice
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (5 preceding siblings ...)
2005-04-05 8:18 ` 2.6.12-rc2-mm1 Brice Goglin
@ 2005-04-05 8:46 ` Rafael J. Wysocki
2005-04-05 10:08 ` 2.6.12-rc2-mm1 Jindrich Makovicka
` (10 subsequent siblings)
17 siblings, 0 replies; 84+ messages in thread
From: Rafael J. Wysocki @ 2005-04-05 8:46 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Hi,
On Tuesday, 5 of April 2005 09:05, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
> `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be fixed. We
> haven't heard yet.
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Well, "my" problem with the PM suspend has turned out to be at least partially
hardware/BIOS-related, so it is not easily reproducible. It is being worked on,
however, AFAICS, so I didn't reported it all over again.
There also is a problem with the ACPI battery driver, which is known to the
right people, too.
Anyway, the patches that cause these issues to appear have been identified
(they both come from the ACPI -bk tree).
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (6 preceding siblings ...)
2005-04-05 8:46 ` 2.6.12-rc2-mm1 Rafael J. Wysocki
@ 2005-04-05 10:08 ` Jindrich Makovicka
2005-04-06 22:07 ` 2.6.12-rc2-mm1 Andrew Morton
2005-04-05 10:18 ` 2.6.12-rc2-mm1 Andrey Panin
` (9 subsequent siblings)
17 siblings, 1 reply; 84+ messages in thread
From: Jindrich Makovicka @ 2005-04-05 10:08 UTC (permalink / raw)
To: linux-kernel
Andrew Morton wrote:
[...]
Does not compile on AthlonXP. For mmx_clear_page, only the prototype was
changed, but the implementation is still the same. I guess that part of
the patch slipped out somehow.
-extern void mmx_clear_page(void *page);
+extern void mmx_clear_page(void *page, int order);
--
Jindrich Makovicka
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 10:08 ` 2.6.12-rc2-mm1 Jindrich Makovicka
@ 2005-04-06 22:07 ` Andrew Morton
0 siblings, 0 replies; 84+ messages in thread
From: Andrew Morton @ 2005-04-06 22:07 UTC (permalink / raw)
To: Jindrich Makovicka; +Cc: linux-kernel, Christoph Lameter
Jindrich Makovicka <makovick@kmlinux.fjfi.cvut.cz> wrote:
>
> oes not compile on AthlonXP. For mmx_clear_page, only the prototype was
> changed, but the implementation is still the same. I guess that part of
> the patch slipped out somehow.
>
> -extern void mmx_clear_page(void *page);
>
> +extern void mmx_clear_page(void *page, int order);
I guess this will fix it...
diff -puN arch/i386/lib/mmx.c~add-a-clear_pages-function-to-clear-pages-of-higher-fix arch/i386/lib/mmx.c
--- 25/arch/i386/lib/mmx.c~add-a-clear_pages-function-to-clear-pages-of-higher-fix Wed Apr 6 15:00:54 2005
+++ 25-akpm/arch/i386/lib/mmx.c Wed Apr 6 15:06:09 2005
@@ -128,9 +128,10 @@ void *_mmx_memcpy(void *to, const void *
* other MMX using processors do not.
*/
-static void fast_clear_page(void *page)
+static void fast_clear_page(void *page, int order)
{
int i;
+ int chunks = (4096 << order) / 64;
kernel_fpu_begin();
@@ -138,8 +139,7 @@ static void fast_clear_page(void *page)
" pxor %%mm0, %%mm0\n" : :
);
- for(i=0;i<4096/64;i++)
- {
+ for (i = 0; i < chunks; i++) {
__asm__ __volatile__ (
" movntq %%mm0, (%0)\n"
" movntq %%mm0, 8(%0)\n"
@@ -257,18 +257,18 @@ static void fast_copy_page(void *to, voi
* Generic MMX implementation without K7 specific streaming
*/
-static void fast_clear_page(void *page)
+static void fast_clear_page(void *page, int order)
{
int i;
-
+ int chunks = (4096 << order) / 128;
+
kernel_fpu_begin();
__asm__ __volatile__ (
" pxor %%mm0, %%mm0\n" : :
);
- for(i=0;i<4096/128;i++)
- {
+ for (i = 0; i < chunks; i++) {
__asm__ __volatile__ (
" movq %%mm0, (%0)\n"
" movq %%mm0, 8(%0)\n"
@@ -359,23 +359,23 @@ static void fast_copy_page(void *to, voi
* Favour MMX for page clear and copy.
*/
-static void slow_zero_page(void * page)
+static void slow_zero_page(void *page, int order)
{
int d0, d1;
__asm__ __volatile__( \
"cld\n\t" \
"rep ; stosl" \
: "=&c" (d0), "=&D" (d1)
- :"a" (0),"1" (page),"0" (1024)
+ :"a" (0),"1" (page),"0" (1024 << order)
:"memory");
}
-void mmx_clear_page(void * page)
+void mmx_clear_page(void *page, int order)
{
if(unlikely(in_interrupt()))
- slow_zero_page(page);
+ slow_zero_page(page, order);
else
- fast_clear_page(page);
+ fast_clear_page(page, order);
}
static void slow_copy_page(void *to, void *from)
_
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (7 preceding siblings ...)
2005-04-05 10:08 ` 2.6.12-rc2-mm1 Jindrich Makovicka
@ 2005-04-05 10:18 ` Andrey Panin
2005-04-05 12:21 ` [-mm patch] Makefile: fix spaces instead of tab Adrian Bunk
` (8 subsequent siblings)
17 siblings, 0 replies; 84+ messages in thread
From: Andrey Panin @ 2005-04-05 10:18 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On 095, 04 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
what useful this part of the patch is supposed to do ?
Looks like the result of whitespace damage.
--- linux-2.6.12-rc2/drivers/acpi/sleep/main.c 2005-03-02 01:09:19.000000000 -0800
+++ 25/drivers/acpi/sleep/main.c 2005-04-04 22:33:10.000000000 -0700
<snip>
@@ -190,16 +180,16 @@ static int __init init_ints_after_s1(str
static struct dmi_system_id __initdata acpisleep_dmi_table[] = {
{
- .callback = init_ints_after_s1,
- .ident = "Toshiba Satellite 4030cdt",
- .matches = { DMI_MATCH(DMI_PRODUCT_NAME, "S4030CDT/4.3"), },
- },
- { },
+ .callback = init_ints_after_s1,
+ .ident = "Toshiba Satellite 4030cdt",
+ .matches = {DMI_MATCH(DMI_PRODUCT_NAME, "S4030CDT/4.3"),},
+ },
+ {},
};
^ permalink raw reply [flat|nested] 84+ messages in thread* [-mm patch] Makefile: fix spaces instead of tab
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (8 preceding siblings ...)
2005-04-05 10:18 ` 2.6.12-rc2-mm1 Andrey Panin
@ 2005-04-05 12:21 ` Adrian Bunk
2005-04-05 13:19 ` Sam Ravnborg
2005-04-05 12:40 ` 2.6.12-rc2-mm1 Borislav Petkov
` (7 subsequent siblings)
17 siblings, 1 reply; 84+ messages in thread
From: Adrian Bunk @ 2005-04-05 12:21 UTC (permalink / raw)
To: Andrew Morton, Ryan Anderson, Sam Ravnborg; +Cc: linux-kernel
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.12-rc1-mm4:
>...
> bk-kbuild.patch
>...
GNU Emacs correctly complains because of spaces instead of a tab.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.12-rc2-mm1-full/Makefile.old 2005-04-05 14:00:06.000000000 +0200
+++ linux-2.6.12-rc2-mm1-full/Makefile 2005-04-05 14:00:16.000000000 +0200
@@ -577,7 +577,7 @@
ifdef CONFIG_LOCALVERSION_AUTO
localversion-auto := \
- $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
+ $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
LOCALVERSION := $(LOCALVERSION)$(localversion-auto)
endif
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: [-mm patch] Makefile: fix spaces instead of tab
2005-04-05 12:21 ` [-mm patch] Makefile: fix spaces instead of tab Adrian Bunk
@ 2005-04-05 13:19 ` Sam Ravnborg
0 siblings, 0 replies; 84+ messages in thread
From: Sam Ravnborg @ 2005-04-05 13:19 UTC (permalink / raw)
To: Adrian Bunk; +Cc: Andrew Morton, Ryan Anderson, linux-kernel
On Tue, Apr 05, 2005 at 02:21:57PM +0200, Adrian Bunk wrote:
> GNU Emacs correctly complains because of spaces instead of a tab.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6.12-rc2-mm1-full/Makefile.old 2005-04-05 14:00:06.000000000 +0200
> +++ linux-2.6.12-rc2-mm1-full/Makefile 2005-04-05 14:00:16.000000000 +0200
> @@ -577,7 +577,7 @@
>
> ifdef CONFIG_LOCALVERSION_AUTO
> localversion-auto := \
> - $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
> + $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
> LOCALVERSION := $(LOCALVERSION)$(localversion-auto)
> endif
In this case it makes sense - thanks.
Sam
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (9 preceding siblings ...)
2005-04-05 12:21 ` [-mm patch] Makefile: fix spaces instead of tab Adrian Bunk
@ 2005-04-05 12:40 ` Borislav Petkov
2005-04-05 13:44 ` 2.6.12-rc2-mm1 Barry K. Nathan
` (6 subsequent siblings)
17 siblings, 0 replies; 84+ messages in thread
From: Borislav Petkov @ 2005-04-05 12:40 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, mdharm-usb
<snip>
a missing include:
...
drivers/usb/storage/debug.c: In function `usb_stor_show_sense':
drivers/usb/storage/debug.c:166: warning: implicit declaration of function `scsi_sense_key_string'
drivers/usb/storage/debug.c:167: warning: implicit declaration of function `scsi_extd_sense_format'
...
--- drivers/usb/storage/debug.c.orig 2005-04-05 14:24:21.000000000 +0200
+++ drivers/usb/storage/debug.c 2005-04-05 14:24:35.000000000 +0200
@@ -47,7 +47,7 @@
#include <linux/cdrom.h>
#include <scsi/scsi.h>
#include <scsi/scsi_cmnd.h>
-
+#include <scsi/scsi_dbg.h>
#include "debug.h"
#include "scsi.h"
Regards,
Boris.
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (10 preceding siblings ...)
2005-04-05 12:40 ` 2.6.12-rc2-mm1 Borislav Petkov
@ 2005-04-05 13:44 ` Barry K. Nathan
2005-04-05 14:14 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-05 14:24 ` [-mm patch] drivers/infiniband/hw/mthca/mthca_main.c: remove an unused label Adrian Bunk
` (5 subsequent siblings)
17 siblings, 1 reply; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-05 13:44 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
No, I just didn't get a chance to send mail yet.
Compared to 2.6.11-ac5, I'm seeing one regression: the part of the
resume where it says something like:
swsusp: reading slkf;jalksfsadflkjas;dlfasdfkl (12345 pages): 34%
[sorry, I just got up so my short-term memory isn't working that well
yet]
takes 10-30 minutes (depending on whether it's closer to 11000 pages or
20000) rather than the 5-10 seconds or so that it takes under 2.6.11-ac5
(or mainline 2.6.11 if I remember correctly).
However, this is not vanilla 2.6.12-rc1-mm4. It has my own modified
version of the Win4Lin patch applied; this is GPL, but the userspace
program that uses this patch (Win4Lin 5.1) isn't, nor is the software
ultimately executed by this patch via Win4Lin (Microsoft Windows
Millennium Edition[*]). And I didn't try swsusp on any kernels between
2.6.11 and 2.6.12-rc1-mm4.
I'll try to do some more testing to see (a) when this problem started
and (b) whether it still exists in 2.6.12-rc2 or later. This is going to
be ridiculously difficult for me to fit into my schedule right now, but
I'll try....
BTW, ieee1394 is still broken after resume (impossible to rmmod, too) and
snd_cmipci (but this can be resurrected by quitting anything that uses
sound, rmmod snd_cmipci, then modprobe snd_cmipci). But these are
long-standing issues, and under 2.6.12-rc1-mm4, ieee1394/sbp2 can at
least stay up indefinitely as long as I don't suspend -- that's a
tremendous improvement over 2.6.11.
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 13:44 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-05 14:14 ` Barry K. Nathan
2005-04-05 22:03 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-06 0:56 ` 2.6.12-rc2-mm1 Andrew Morton
0 siblings, 2 replies; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-05 14:14 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: Andrew Morton, linux-kernel
On Tue, Apr 05, 2005 at 06:44:08AM -0700, Barry K. Nathan wrote:
> swsusp: reading slkf;jalksfsadflkjas;dlfasdfkl (12345 pages): 34%
> [sorry, I just got up so my short-term memory isn't working that well
> yet]
>
> takes 10-30 minutes (depending on whether it's closer to 11000 pages or
> 20000) rather than the 5-10 seconds or so that it takes under 2.6.11-ac5
> (or mainline 2.6.11 if I remember correctly).
[snip]
> I'll try to do some more testing to see (a) when this problem started
> and (b) whether it still exists in 2.6.12-rc2 or later. This is going to
> be ridiculously difficult for me to fit into my schedule right now, but
> I'll try....
2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
2.6.11-bk10 has the weird slowdown.
I'll see if I can isolate it any further.
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 14:14 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-05 22:03 ` Barry K. Nathan
2005-04-06 0:56 ` 2.6.12-rc2-mm1 Andrew Morton
1 sibling, 0 replies; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-05 22:03 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: Andrew Morton, linux-kernel
On Tue, Apr 05, 2005 at 07:14:45AM -0700, Barry K. Nathan wrote:
> 2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
> 2.6.11-bk10 has the weird slowdown.
>
> I'll see if I can isolate it any further.
2.6.11-mm2 works, but 2.6.11-mm3 has the ridiculously slow resumes.
Later today I'll see if I can narrow things down any further (e.g. to a
specific patch in 2.6.11-mm3 or whatever).
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 14:14 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-05 22:03 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-06 0:56 ` Andrew Morton
2005-04-06 7:19 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-06 12:59 ` 2.6.12-rc2-mm1 Barry K. Nathan
1 sibling, 2 replies; 84+ messages in thread
From: Andrew Morton @ 2005-04-06 0:56 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: barryn, linux-kernel
"Barry K. Nathan" <barryn@pobox.com> wrote:
>
> On Tue, Apr 05, 2005 at 06:44:08AM -0700, Barry K. Nathan wrote:
> > swsusp: reading slkf;jalksfsadflkjas;dlfasdfkl (12345 pages): 34%
> > [sorry, I just got up so my short-term memory isn't working that well
> > yet]
> >
> > takes 10-30 minutes (depending on whether it's closer to 11000 pages or
> > 20000) rather than the 5-10 seconds or so that it takes under 2.6.11-ac5
> > (or mainline 2.6.11 if I remember correctly).
Odd.
> [snip]
> > I'll try to do some more testing to see (a) when this problem started
> > and (b) whether it still exists in 2.6.12-rc2 or later. This is going to
> > be ridiculously difficult for me to fit into my schedule right now, but
> > I'll try....
>
> 2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
> 2.6.11-bk10 has the weird slowdown.
Unfortunately that's a pretty bug diff (2 megs).
The only thing I can see in the memory reclaim area is this:
--- b/mm/vmscan.c 2005-03-10 00:39:02 -08:00
+++ b/mm/vmscan.c 2005-03-13 15:29:39 -08:00
@@ -313,8 +313,20 @@
*/
if (!is_page_cache_freeable(page))
return PAGE_KEEP;
- if (!mapping)
+ if (!mapping) {
+ /*
+ * Some data journaling orphaned pages can have
+ * page->mapping == NULL while being dirty with clean buffers.
+ */
+ if (PageDirty(page) && PagePrivate(page)) {
+ if (try_to_free_buffers(page)) {
+ ClearPageDirty(page);
+ printk("%s: orphaned page\n", __FUNCTION__);
+ return PAGE_CLEAN;
+ }
+ }
return PAGE_KEEP;
+ }
if (mapping->a_ops->writepage == NULL)
return PAGE_ACTIVATE;
if (!may_write_to_queue(mapping->backing_dev_info))
but you'd be getting a printk storm if that was triggering.
> I'll see if I can isolate it any further.
Please, that would help.
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-06 0:56 ` 2.6.12-rc2-mm1 Andrew Morton
@ 2005-04-06 7:19 ` Barry K. Nathan
2005-04-06 12:59 ` 2.6.12-rc2-mm1 Barry K. Nathan
1 sibling, 0 replies; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-06 7:19 UTC (permalink / raw)
To: Andrew Morton; +Cc: Barry K. Nathan, linux-kernel
On Tue, Apr 05, 2005 at 05:56:00PM -0700, Andrew Morton wrote:
> Odd.
Yes, it is odd...
> > 2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
> > 2.6.11-bk10 has the weird slowdown.
>
> Unfortunately that's a pretty bug diff (2 megs).
Yeah, I know. *sigh*
[snip]
> but you'd be getting a printk storm if that was triggering.
I'm not seeing a printk storm, at least, none that I can discern...
> > I'll see if I can isolate it any further.
>
> Please, that would help.
I'm working on it right now.
2.6.11 + linus.patch from 2.6.11-mm3 works.
2.6.11 + approx. 292 patches from 2.6.11-mm3 is broken.
2.6.11 + approx. 130 patches (a proper subset of the 292 patches) works.
(this is counting each subsystem bk tree as a single patch)
The diff between the latter two trees is still larger than the
2.6.11-bk9 -> -bk10 diff, but after one or two more iterations of
(psuedo-)binary search, it should be much smaller.
I'm planning to go as far as I can before going to bed tonight.
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-06 0:56 ` 2.6.12-rc2-mm1 Andrew Morton
2005-04-06 7:19 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-06 12:59 ` Barry K. Nathan
2005-04-06 21:27 ` 2.6.12-rc2-mm1 Andrew Morton
1 sibling, 1 reply; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-06 12:59 UTC (permalink / raw)
To: Andrew Morton; +Cc: Barry K. Nathan, linux-kernel
On Tue, Apr 05, 2005 at 05:56:00PM -0700, Andrew Morton wrote:
> > I'll see if I can isolate it any further.
>
> Please, that would help.
[Right now I'm in a race against my lack of sleep. I'm trying to send
this e-mail before I involuntarily fall asleep, so the contents
and/or recipient list may be incomplete...]
Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
problem goes away if I remove this patch:
swsusp-enable-resume-from-initrd.patch
(Recap of the problem in case this gets forwarded: Resume is almost
instant without the apparently-guilty patch. With the patch, resume
takes almost half an hour.)
BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
With that kernel, suspend is also ridiculously slow (speed is comparable
to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
have that problem.
Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
all the printk timestamps are 0000000.0000000 (don't take the # of
digits too literally). Probably unrelated, but I may as well mention it.
(System is an Athlon XP 2200+ with SiS chipset. I can't remember which
model of SiS chipset.)
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-06 12:59 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-06 21:27 ` Andrew Morton
2005-04-07 3:06 ` 2.6.12-rc2-mm1 Barry K. Nathan
0 siblings, 1 reply; 84+ messages in thread
From: Andrew Morton @ 2005-04-06 21:27 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: barryn, linux-kernel, Pavel Machek, mjg59
"Barry K. Nathan" <barryn@pobox.com> wrote:
>
> Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> problem goes away if I remove this patch:
> swsusp-enable-resume-from-initrd.patch
That really helps, thanks.
The patch looks fairly innocent. I'll give up on this and cc the
developers.
> (Recap of the problem in case this gets forwarded: Resume is almost
> instant without the apparently-guilty patch. With the patch, resume
> takes almost half an hour.)
>
> BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
> With that kernel, suspend is also ridiculously slow (speed is comparable
> to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
> have that problem.
Does reverting swsusp-enable-resume-from-initrd.patch fix this also?
> Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
> all the printk timestamps are 0000000.0000000 (don't take the # of
> digits too literally). Probably unrelated, but I may as well mention it.
> (System is an Athlon XP 2200+ with SiS chipset. I can't remember which
> model of SiS chipset.)
Yes, sorry. Reverting
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
will fix that one.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-06 21:27 ` 2.6.12-rc2-mm1 Andrew Morton
@ 2005-04-07 3:06 ` Barry K. Nathan
2005-04-07 6:55 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-08 10:33 ` 2.6.12-rc2-mm1 Pavel Machek
0 siblings, 2 replies; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-07 3:06 UTC (permalink / raw)
To: Andrew Morton; +Cc: Barry K. Nathan, linux-kernel, Pavel Machek, mjg59
On Wed, Apr 06, 2005 at 02:27:49PM -0700, Andrew Morton wrote:
> "Barry K. Nathan" <barryn@pobox.com> wrote:
> >
> > Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> > problem goes away if I remove this patch:
> > swsusp-enable-resume-from-initrd.patch
>
> That really helps, thanks.
You're welcome.
> The patch looks fairly innocent. I'll give up on this and cc the
> developers.
Yeah, it *seemed* innocent enough -- that's why I had to do a binary
search on the 2.6.11-mm3 "series" file in order to find it as the
culprit...
> > (Recap of the problem in case this gets forwarded: Resume is almost
> > instant without the apparently-guilty patch. With the patch, resume
> > takes almost half an hour.)
> >
> > BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
> > With that kernel, suspend is also ridiculously slow (speed is comparable
> > to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
> > have that problem.
>
> Does reverting swsusp-enable-resume-from-initrd.patch fix this also?
No. Reverting it from 2.6.12-rc2-mm1 (oops, I got the version number
wrong in my previous mail -- and that should also be 2.6.12-rc2 not
2.6.11-rc2) speeds up resume to the original speed, but suspend is still
ridiculously slow. Time to narrow things down again, I presume...
> > Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
> > all the printk timestamps are 0000000.0000000 (don't take the # of
> > digits too literally). Probably unrelated, but I may as well mention it.
> > (System is an Athlon XP 2200+ with SiS chipset. I can't remember which
> > model of SiS chipset.)
>
> Yes, sorry. Reverting
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
> will fix that one.
I kind of figured that from another LKML discussion but I wasn't 100%
sure that's what I should do.
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-07 3:06 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-07 6:55 ` Barry K. Nathan
2005-04-08 10:33 ` 2.6.12-rc2-mm1 Pavel Machek
1 sibling, 0 replies; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-07 6:55 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: Andrew Morton, linux-kernel, Pavel Machek, mjg59
On Wed, Apr 06, 2005 at 08:06:14PM -0700, Barry K. Nathan wrote:
> > > BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
> > > With that kernel, suspend is also ridiculously slow (speed is comparable
> > > to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
> > > have that problem.
> >
> > Does reverting swsusp-enable-resume-from-initrd.patch fix this also?
>
> No. Reverting it from 2.6.12-rc2-mm1 (oops, I got the version number
> wrong in my previous mail -- and that should also be 2.6.12-rc2 not
> 2.6.11-rc2) speeds up resume to the original speed, but suspend is still
> ridiculously slow. Time to narrow things down again, I presume...
>
> > > Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
> > > all the printk timestamps are 0000000.0000000 (don't take the # of
> > > digits too literally). Probably unrelated, but I may as well mention it.
> > > (System is an Athlon XP 2200+ with SiS chipset. I can't remember which
> > > model of SiS chipset.)
> >
> > Yes, sorry. Reverting
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
> > will fix that one.
Reverting
sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
fixed both the printk timestamps and the slow suspend. And it also fixed
a **major** interactivity problem (running kernel compiles made X almost
unusably slow) which I discovered since sending the previous e-mail. So,
something about this patch is seriously evil.
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-07 3:06 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-07 6:55 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-08 10:33 ` Pavel Machek
2005-04-10 21:18 ` 2.6.12-rc2-mm1 Barry K. Nathan
1 sibling, 1 reply; 84+ messages in thread
From: Pavel Machek @ 2005-04-08 10:33 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: Andrew Morton, linux-kernel, mjg59, hare
Hi!
> > > Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> > > problem goes away if I remove this patch:
> > > swsusp-enable-resume-from-initrd.patch
> >
> > That really helps, thanks.
>
> You're welcome.
>
> > The patch looks fairly innocent. I'll give up on this and cc the
> > developers.
>
> Yeah, it *seemed* innocent enough -- that's why I had to do a binary
> search on the 2.6.11-mm3 "series" file in order to find it as the
> culprit...
Do you have XFS compiled in, by chance?
You are not actually resuming from initrd, right?
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-08 10:33 ` 2.6.12-rc2-mm1 Pavel Machek
@ 2005-04-10 21:18 ` Barry K. Nathan
2005-04-10 21:27 ` 2.6.12-rc2-mm1 Pavel Machek
0 siblings, 1 reply; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-10 21:18 UTC (permalink / raw)
To: Pavel Machek; +Cc: Barry K. Nathan, Andrew Morton, linux-kernel, mjg59, hare
(Sorry I took so long to respond. I was busy with tons of stuff
offline...)
On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
> Do you have XFS compiled in, by chance?
Yes.
> You are not actually resuming from initrd, right?
That is correct.
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-10 21:18 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-10 21:27 ` Pavel Machek
2005-04-10 22:57 ` 2.6.12-rc2-mm1 Barry K. Nathan
0 siblings, 1 reply; 84+ messages in thread
From: Pavel Machek @ 2005-04-10 21:27 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: Andrew Morton, linux-kernel, mjg59, hare
Hi!
> (Sorry I took so long to respond. I was busy with tons of stuff
> offline...)
>
> On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
> > Do you have XFS compiled in, by chance?
>
> Yes.
Can you try without XFS?
I do not why it interferes, but I've seen that before on suse
kernels...
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-10 21:27 ` 2.6.12-rc2-mm1 Pavel Machek
@ 2005-04-10 22:57 ` Barry K. Nathan
2005-04-10 23:00 ` 2.6.12-rc2-mm1 Pavel Machek
2005-04-11 7:38 ` 2.6.12-rc2-mm1 Stefan Seyfried
0 siblings, 2 replies; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-10 22:57 UTC (permalink / raw)
To: Pavel Machek; +Cc: Barry K. Nathan, Andrew Morton, linux-kernel, mjg59, hare
On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
> Can you try without XFS?
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
I'll see if I can reproduce this on one of my test boxes. I'll *try* to
get to it later today, but it's possible that I won't be able to get to
it until next Friday or Saturday.
> I do not why it interferes, but I've seen that before on suse
> kernels...
Have you seen it without the resume-from-initrd patch too, or only with
that patch?
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-10 22:57 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-10 23:00 ` Pavel Machek
2005-04-11 4:31 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-11 7:38 ` 2.6.12-rc2-mm1 Stefan Seyfried
1 sibling, 1 reply; 84+ messages in thread
From: Pavel Machek @ 2005-04-10 23:00 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: Andrew Morton, linux-kernel, hare
Hi!
> > Can you try without XFS?
>
> No, XFS is my root filesystem. :( (Now that I think about it, would
> modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
> I'll see if I can reproduce this on one of my test boxes. I'll *try* to
> get to it later today, but it's possible that I won't be able to get to
> it until next Friday or Saturday.
>
> > I do not why it interferes, but I've seen that before on suse
> > kernels...
>
> Have you seen it without the resume-from-initrd patch too, or only with
> that patch?
Only with resume-from-initrd.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-10 23:00 ` 2.6.12-rc2-mm1 Pavel Machek
@ 2005-04-11 4:31 ` Barry K. Nathan
2005-04-11 10:57 ` swsusp vs. xfs [was Re: 2.6.12-rc2-mm1] Pavel Machek
0 siblings, 1 reply; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-11 4:31 UTC (permalink / raw)
To: Pavel Machek; +Cc: Barry K. Nathan, Andrew Morton, linux-kernel, hare
On Mon, Apr 11, 2005 at 01:00:53AM +0200, Pavel Machek wrote:
> > No, XFS is my root filesystem. :( (Now that I think about it, would
> > modularizing XFS and using an initrd be OK?)
>
> Yes, loading xfs from initrd should help. [At least it did during
> suse9.3 testing.]
Once I modularized xfs and switched to using an initrd, the problem
disappeared.
I just noticed a difference between the kernel messages with XFS
built-in and with it modularized. I'm having trouble putting my finger
on it; it seems like the screen gets cleared at some point during
resume, and with XFS built-in, it starts reading the data from swap
*after* the screen gets cleared. In contrast, if the enable-initrd patch
is removed or XFS is modularized, it reads in from swap *before* the
screen gets cleared. Or something like that.
I'll see if I can get anything more detailed & useful with a serial
console... Failing that, I'll try a camcorder or digital camera and
transcribe from that.
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]
2005-04-11 4:31 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-11 10:57 ` Pavel Machek
2005-04-11 23:12 ` [xfs-masters] " Nathan Scott
0 siblings, 1 reply; 84+ messages in thread
From: Pavel Machek @ 2005-04-11 10:57 UTC (permalink / raw)
To: Barry K. Nathan
Cc: Andrew Morton, linux-kernel, hare, xfs-masters, nathans,
linux-xfs
Hi!
> > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > modularizing XFS and using an initrd be OK?)
> >
> > Yes, loading xfs from initrd should help. [At least it did during
> > suse9.3 testing.]
>
> Once I modularized xfs and switched to using an initrd, the problem
> disappeared.
I reproduced it locally. Problem is that xfsbufd goes refrigerated,
but someone still tries to wake it up *very* often. Probably something
else in xfs needs refrigerating, too, but I'm not a XFS wizard...
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: [xfs-masters] swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]
2005-04-11 10:57 ` swsusp vs. xfs [was Re: 2.6.12-rc2-mm1] Pavel Machek
@ 2005-04-11 23:12 ` Nathan Scott
2005-04-11 23:51 ` Pavel Machek
0 siblings, 1 reply; 84+ messages in thread
From: Nathan Scott @ 2005-04-11 23:12 UTC (permalink / raw)
To: Pavel Machek
Cc: Barry K. Nathan, Andrew Morton, linux-kernel, hare, linux-xfs
On Mon, Apr 11, 2005 at 12:57:59PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > > modularizing XFS and using an initrd be OK?)
> > >
> > > Yes, loading xfs from initrd should help. [At least it did during
> > > suse9.3 testing.]
> >
> > Once I modularized xfs and switched to using an initrd, the problem
> > disappeared.
>
> I reproduced it locally. Problem is that xfsbufd goes refrigerated,
> but someone still tries to wake it up *very* often. Probably something
> else in xfs needs refrigerating, too, but I'm not a XFS wizard...
Thanks Pavel - I've been reading the thread from the other side
of the fence, not understanding the swsusp side of things. :)
There are two ways the xfsbufd thread will wake up - either by its
timer going off (for it to flush delayed write metadata buffers)
or by being explicitly woken up when we're low on memory (in which
case it also flushes out dirty metadata, such that pages can be
cleaned and made available to the system).
Since the refrigerator() call is in place in the main xfsbufd loop,
I suspect we're hitting that second case here, where a low memory
situation is resulting in someone attempting to wakeup xfsbufd --
I'm not sure if this is the right way to check if we're in that
state, but does this patch help? (it would certainly prevent the
spurious wakeups, but only if the caller has PF_FREEZE set - will
that be the case here?)
cheers.
--
Nathan
--- fs/xfs/linux-2.6/xfs_buf.c.orig 2005-04-12 09:00:26.375351560 +1000
+++ fs/xfs/linux-2.6/xfs_buf.c 2005-04-12 08:59:38.973557728 +1000
@@ -1753,6 +1753,8 @@ pagebuf_daemon_wakeup(
int priority,
unsigned int mask)
{
+ if (current->flags & PF_FREEZE)
+ return 0;
force_flush = 1;
barrier();
wake_up_process(pagebuf_daemon_task);
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: [xfs-masters] swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]
2005-04-11 23:12 ` [xfs-masters] " Nathan Scott
@ 2005-04-11 23:51 ` Pavel Machek
2005-04-12 0:26 ` Nathan Scott
2005-04-12 12:47 ` Rafael J. Wysocki
0 siblings, 2 replies; 84+ messages in thread
From: Pavel Machek @ 2005-04-11 23:51 UTC (permalink / raw)
To: Nathan Scott
Cc: Barry K. Nathan, Andrew Morton, linux-kernel, hare, linux-xfs
Hi!
> > > > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > > > modularizing XFS and using an initrd be OK?)
> > > >
> > > > Yes, loading xfs from initrd should help. [At least it did during
> > > > suse9.3 testing.]
> > >
> > > Once I modularized xfs and switched to using an initrd, the problem
> > > disappeared.
> >
> > I reproduced it locally. Problem is that xfsbufd goes refrigerated,
> > but someone still tries to wake it up *very* often. Probably something
> > else in xfs needs refrigerating, too, but I'm not a XFS wizard...
>
> Thanks Pavel - I've been reading the thread from the other side
> of the fence, not understanding the swsusp side of things. :)
>
> There are two ways the xfsbufd thread will wake up - either by its
> timer going off (for it to flush delayed write metadata buffers)
> or by being explicitly woken up when we're low on memory (in which
> case it also flushes out dirty metadata, such that pages can be
> cleaned and made available to the system).
>
> Since the refrigerator() call is in place in the main xfsbufd loop,
> I suspect we're hitting that second case here, where a low memory
> situation is resulting in someone attempting to wakeup xfsbufd --
> I'm not sure if this is the right way to check if we're in that
> state, but does this patch help? (it would certainly prevent the
> spurious wakeups, but only if the caller has PF_FREEZE set - will
> that be the case here?)
I should take some sleep now, so I can't test the patch, but I don't
think it will help. If someone has PF_FREEZE set, he should be in
refrigerator.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: [xfs-masters] swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]
2005-04-11 23:51 ` Pavel Machek
@ 2005-04-12 0:26 ` Nathan Scott
2005-04-12 11:04 ` Pavel Machek
2005-04-12 12:47 ` Rafael J. Wysocki
1 sibling, 1 reply; 84+ messages in thread
From: Nathan Scott @ 2005-04-12 0:26 UTC (permalink / raw)
To: Pavel Machek
Cc: Barry K. Nathan, Andrew Morton, linux-kernel, hare, linux-xfs
On Tue, Apr 12, 2005 at 01:51:10AM +0200, Pavel Machek wrote:
> I should take some sleep now, so I can't test the patch, but I don't
> think it will help. If someone has PF_FREEZE set, he should be in
> refrigerator.
OK, so if that doesn't help, here's an alternate approach - this
lets xfsbufd track when its entering the refrigerator(), so that
other callers know that attempts to wake it are futile.
cheers.
--
Nathan
--- fs/xfs/linux-2.6/xfs_buf.c.orig 2005-04-12 09:00:26.375351560 +1000
+++ fs/xfs/linux-2.6/xfs_buf.c 2005-04-12 10:14:27.468202824 +1000
@@ -1746,13 +1746,15 @@ STATIC DECLARE_COMPLETION(pagebuf_daemon
STATIC struct task_struct *pagebuf_daemon_task;
STATIC int pagebuf_daemon_active;
STATIC int force_flush;
-
+STATIC int force_sleep;
STATIC int
pagebuf_daemon_wakeup(
int priority,
unsigned int mask)
{
+ if (force_sleep)
+ return 0;
force_flush = 1;
barrier();
wake_up_process(pagebuf_daemon_task);
@@ -1778,7 +1780,12 @@ pagebuf_daemon(
INIT_LIST_HEAD(&tmp);
do {
- try_to_freeze(PF_FREEZE);
+ if (unlikely(current->flags & PF_FREEZE)) {
+ force_sleep = 1;
+ refrigerator(PF_FREEZE);
+ } else {
+ force_sleep = 0;
+ }
set_current_state(TASK_INTERRUPTIBLE);
schedule_timeout((xfs_buf_timer_centisecs * HZ) / 100);
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: [xfs-masters] swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]
2005-04-12 0:26 ` Nathan Scott
@ 2005-04-12 11:04 ` Pavel Machek
2005-04-12 11:50 ` Barry K. Nathan
0 siblings, 1 reply; 84+ messages in thread
From: Pavel Machek @ 2005-04-12 11:04 UTC (permalink / raw)
To: Nathan Scott
Cc: Barry K. Nathan, Andrew Morton, linux-kernel, hare, linux-xfs
Hi!
> > I should take some sleep now, so I can't test the patch, but I don't
> > think it will help. If someone has PF_FREEZE set, he should be in
> > refrigerator.
>
> OK, so if that doesn't help, here's an alternate approach - this
> lets xfsbufd track when its entering the refrigerator(), so that
> other callers know that attempts to wake it are futile.
Thanks, this patch helped.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: [xfs-masters] swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]
2005-04-12 11:04 ` Pavel Machek
@ 2005-04-12 11:50 ` Barry K. Nathan
0 siblings, 0 replies; 84+ messages in thread
From: Barry K. Nathan @ 2005-04-12 11:50 UTC (permalink / raw)
To: Pavel Machek
Cc: Nathan Scott, Barry K. Nathan, Andrew Morton, linux-kernel, hare,
linux-xfs
On Tue, Apr 12, 2005 at 01:04:25PM +0200, Pavel Machek wrote:
> > OK, so if that doesn't help, here's an alternate approach - this
> > lets xfsbufd track when its entering the refrigerator(), so that
> > other callers know that attempts to wake it are futile.
>
> Thanks, this patch helped.
I can confirm, the 2nd patch worked and the 1st one didn't. (This is
against 2.6.12-rc2-mm1 with sched-x86-patch-name-is-way-too-long.patch
backed out. ;) )
-Barry K. Nathan <barryn@pobox.com>
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: [xfs-masters] swsusp vs. xfs [was Re: 2.6.12-rc2-mm1]
2005-04-11 23:51 ` Pavel Machek
2005-04-12 0:26 ` Nathan Scott
@ 2005-04-12 12:47 ` Rafael J. Wysocki
1 sibling, 0 replies; 84+ messages in thread
From: Rafael J. Wysocki @ 2005-04-12 12:47 UTC (permalink / raw)
To: Pavel Machek
Cc: Nathan Scott, Barry K. Nathan, Andrew Morton, linux-kernel, hare,
linux-xfs
Hi,
On Tuesday, 12 of April 2005 01:51, Pavel Machek wrote:
]--snip--[
> > Since the refrigerator() call is in place in the main xfsbufd loop,
> > I suspect we're hitting that second case here, where a low memory
> > situation is resulting in someone attempting to wakeup xfsbufd --
> > I'm not sure if this is the right way to check if we're in that
> > state, but does this patch help? (it would certainly prevent the
> > spurious wakeups, but only if the caller has PF_FREEZE set - will
> > that be the case here?)
>
> I should take some sleep now, so I can't test the patch, but I don't
> think it will help. If someone has PF_FREEZE set, he should be in
> refrigerator.
Or he was in TASK_UNINTERRUPTIBLE while processes were being frozen. :-)
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-10 22:57 ` 2.6.12-rc2-mm1 Barry K. Nathan
2005-04-10 23:00 ` 2.6.12-rc2-mm1 Pavel Machek
@ 2005-04-11 7:38 ` Stefan Seyfried
1 sibling, 0 replies; 84+ messages in thread
From: Stefan Seyfried @ 2005-04-11 7:38 UTC (permalink / raw)
To: Barry K. Nathan; +Cc: Andrew Morton, linux-kernel, mjg59, hare, Pavel Machek
Barry K. Nathan wrote:
> On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
>> Can you try without XFS?
>
> No, XFS is my root filesystem. :( (Now that I think about it, would
> modularizing XFS and using an initrd be OK?)
Yes, although it is not totally trivial.
> I'll see if I can reproduce this on one of my test boxes. I'll *try* to
> get to it later today, but it's possible that I won't be able to get to
> it until next Friday or Saturday.
>
>> I do not why it interferes, but I've seen that before on suse
>> kernels...
>
> Have you seen it without the resume-from-initrd patch too, or only with
> that patch?
We have seen it in 9.3-beta, exact scenario was:
- root fs is XFS, ide driver is modular
=> xfs module and ide-controller module is in initramfs
=> first all modules were loaded (device driver + fs)
=> resume was triggered, resume was _really_ slow.
we worked around it in the initramfs by first loading device drivers,
triggering resume, then loading the fs modules and continuing boot.
In the resume case, we'd never reach the "load fs modules" part and
generally it seems a good idea (if the drivers are modular) to keep the
setup before resume as minimalistic as possible.
We never tried with XFS compiled in. It seems we can no longer hide from
fixing XFS ;-)
Best regards,
Stefan
^ permalink raw reply [flat|nested] 84+ messages in thread
* [-mm patch] drivers/infiniband/hw/mthca/mthca_main.c: remove an unused label
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (11 preceding siblings ...)
2005-04-05 13:44 ` 2.6.12-rc2-mm1 Barry K. Nathan
@ 2005-04-05 14:24 ` Adrian Bunk
2005-04-05 14:37 ` Hal Rosenstock
2005-04-05 16:53 ` Roland Dreier
2005-04-05 15:45 ` 2.6.12-rc2-mm1 Jan Dittmer
` (4 subsequent siblings)
17 siblings, 2 replies; 84+ messages in thread
From: Adrian Bunk @ 2005-04-05 14:24 UTC (permalink / raw)
To: Andrew Morton, Roland Dreier; +Cc: linux-kernel, mshefty, halr, openib-general
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.12-rc1-mm4:
>...
> +ib-mthca-add-support-for-new-mt25204-hca.patch
>
> Infiniband update
>...
This patch causes the following compile warning:
<-- snip -->
...
CC drivers/infiniband/hw/mthca/mthca_main.o
drivers/infiniband/hw/mthca/mthca_main.c: In function `mthca_init_icm':
drivers/infiniband/hw/mthca/mthca_main.c:479: warning: label
`err_unmap_eqp' defined but not used
...
<-- snip -->
I'm not sure whether this patch to remove this label is correct, but if
it isn't correct there must be a bug somewhere.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c.old 2005-04-05 16:18:09.000000000 +0200
+++ linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 16:19:15.000000000 +0200
@@ -475,8 +475,6 @@
err_unmap_rdb:
mthca_free_icm_table(mdev, mdev->qp_table.rdb_table);
-
-err_unmap_eqp:
mthca_free_icm_table(mdev, mdev->qp_table.eqp_table);
err_unmap_qp:
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: [-mm patch] drivers/infiniband/hw/mthca/mthca_main.c: remove an unused label
2005-04-05 14:24 ` [-mm patch] drivers/infiniband/hw/mthca/mthca_main.c: remove an unused label Adrian Bunk
@ 2005-04-05 14:37 ` Hal Rosenstock
2005-04-05 16:53 ` Roland Dreier
1 sibling, 0 replies; 84+ messages in thread
From: Hal Rosenstock @ 2005-04-05 14:37 UTC (permalink / raw)
To: Adrian Bunk
Cc: Andrew Morton, Roland Dreier, linux-kernel, Sean Hefty,
openib-general
On Tue, 2005-04-05 at 10:24, Adrian Bunk wrote:
> On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.12-rc1-mm4:
> >...
> > +ib-mthca-add-support-for-new-mt25204-hca.patch
> >
> > Infiniband update
> >...
>
>
> This patch causes the following compile warning:
>
> <-- snip -->
>
> ...
> CC drivers/infiniband/hw/mthca/mthca_main.o
> drivers/infiniband/hw/mthca/mthca_main.c: In function `mthca_init_icm':
> drivers/infiniband/hw/mthca/mthca_main.c:479: warning: label
> `err_unmap_eqp' defined but not used
> ...
>
> <-- snip -->
>
>
> I'm not sure whether this patch to remove this label is correct, but if
> it isn't correct there must be a bug somewhere.
>
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c.old 2005-04-05 16:18:09.000000000 +0200
> +++ linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 16:19:15.000000000 +0200
> @@ -475,8 +475,6 @@
>
> err_unmap_rdb:
> mthca_free_icm_table(mdev, mdev->qp_table.rdb_table);
> -
> -err_unmap_eqp:
> mthca_free_icm_table(mdev, mdev->qp_table.eqp_table);
>
> err_unmap_qp:
Roland caught this recently and there is a patch for this which will
sent upstream. The proper fix is different from this.
-- Hal
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: [-mm patch] drivers/infiniband/hw/mthca/mthca_main.c: remove an unused label
2005-04-05 14:24 ` [-mm patch] drivers/infiniband/hw/mthca/mthca_main.c: remove an unused label Adrian Bunk
2005-04-05 14:37 ` Hal Rosenstock
@ 2005-04-05 16:53 ` Roland Dreier
1 sibling, 0 replies; 84+ messages in thread
From: Roland Dreier @ 2005-04-05 16:53 UTC (permalink / raw)
To: Adrian Bunk; +Cc: Andrew Morton, linux-kernel, mshefty, halr, openib-general
> CC drivers/infiniband/hw/mthca/mthca_main.o
> drivers/infiniband/hw/mthca/mthca_main.c: In function `mthca_init_icm':
> drivers/infiniband/hw/mthca/mthca_main.c:479: warning: label
> `err_unmap_eqp' defined but not used
Thanks, good catch. I screwed up the error path in that function a
little while merging patches. Here's the correct fix.
Correct unwinding in error path of mthca_init_icm().
Signed-off-by: Roland Dreier <roland@topspin.com>
--- linux-2.6.12-rc2-mm1.orig/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 09:49:02.944473724 -0700
+++ linux-2.6.12-rc2-mm1/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 09:49:15.679708865 -0700
@@ -437,7 +437,7 @@
if (!mdev->qp_table.rdb_table) {
mthca_err(mdev, "Failed to map RDB context memory, aborting\n");
err = -ENOMEM;
- goto err_unmap_rdb;
+ goto err_unmap_eqp;
}
mdev->cq_table.table = mthca_alloc_icm_table(mdev, init_hca->cqc_base,
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (12 preceding siblings ...)
2005-04-05 14:24 ` [-mm patch] drivers/infiniband/hw/mthca/mthca_main.c: remove an unused label Adrian Bunk
@ 2005-04-05 15:45 ` Jan Dittmer
2005-04-05 21:38 ` 2.6.12-rc2-mm1 Sam Ravnborg
2005-04-05 17:11 ` 2.6.12-rc2-mm1 Christophe Saout
` (3 subsequent siblings)
17 siblings, 1 reply; 84+ messages in thread
From: Jan Dittmer @ 2005-04-05 15:45 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, sam
> bk-kbuild.patch
Something has broken make O= :
$ make mrproper
$ mkdir /tmp/42
$ make ARCH=alpha CROSS_COMPILE=alpha-linux- O=/tmp/42 defconfig
$ make ARCH=alpha CROSS_COMPILE=alpha-linux- O=/tmp/42
Using /home/jdittmer/src/lk/linus as source for kernel
GEN /tmp/42/Makefile
CHK include/linux/version.h
SYMLINK /tmp/42/include/asm -> include/asm-alpha
SPLIT include/linux/autoconf.h -> include/config/*
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
make[1]: *** No rule to make target `include/asm', needed by `arch/alpha/kernel/asm-offsets.s'. Stop.
make: *** [_all] Error 2
Happens for most archs. See http://l4x.org/k/
Jan
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 15:45 ` 2.6.12-rc2-mm1 Jan Dittmer
@ 2005-04-05 21:38 ` Sam Ravnborg
0 siblings, 0 replies; 84+ messages in thread
From: Sam Ravnborg @ 2005-04-05 21:38 UTC (permalink / raw)
To: Jan Dittmer; +Cc: Andrew Morton, linux-kernel
On Tue, Apr 05, 2005 at 05:45:58PM +0200, Jan Dittmer wrote:
> Something has broken make O= :
>
> HOSTCC scripts/kallsyms
> HOSTCC scripts/conmakehash
> make[1]: *** No rule to make target `include/asm', needed by `arch/alpha/kernel/asm-offsets.s'. Stop.
> make: *** [_all] Error 2
>
> Happens for most archs. See http://l4x.org/k/
Thanks - here is a patch:
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2005/04/05 23:37:09+02:00 sam@mars.ravnborg.org
# kbuild: fix make O=... build
#
# It fixes the following error:
#
# make[1]: *** No rule to make target `include/asm', needed by `arch/alpha/kernel/asm-offsets.s'. Stop.
#
# Reported by:
# From: Jan Dittmer <j.dittmer@portrix.net>
#
# In same patch fix spaces to tabs as reported by:
# From: Adrian Bunk <bunk@stusta.de>
#
# Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
#
# Makefile
# 2005/04/05 23:36:45+02:00 sam@mars.ravnborg.org +3 -3
# fix make O=... build
#
diff -Nru a/Makefile b/Makefile
--- a/Makefile 2005-04-05 23:37:38 +02:00
+++ b/Makefile 2005-04-05 23:37:38 +02:00
@@ -576,7 +576,7 @@
ifdef CONFIG_LOCALVERSION_AUTO
localversion-auto := \
- $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
+ $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
LOCALVERSION := $(LOCALVERSION)$(localversion-auto)
endif
@@ -808,7 +808,7 @@
# prepare1 creates a makefile if using a separate output directory
prepare1: prepare2 outputmakefile
-prepare0: prepare1 include/linux/version.h $(objtree)/include/asm \
+prepare0: prepare1 include/linux/version.h include/asm \
include/config/MARKER
ifneq ($(KBUILD_MODULES),)
$(Q)rm -rf $(MODVERDIR)
@@ -845,7 +845,7 @@
# hard to detect, but I suppose "make mrproper" is a good idea
# before switching between archs anyway.
-$(objtree)/include/asm:
+include/asm:
@echo ' SYMLINK $@ -> include/asm-$(ARCH)'
$(Q)if [ ! -d include ]; then mkdir -p include; fi;
@ln -fsn asm-$(ARCH) $@
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (13 preceding siblings ...)
2005-04-05 15:45 ` 2.6.12-rc2-mm1 Jan Dittmer
@ 2005-04-05 17:11 ` Christophe Saout
2005-04-06 1:44 ` 2.6.12-rc2-mm1 Neil Brown
` (2 subsequent siblings)
17 siblings, 0 replies; 84+ messages in thread
From: Christophe Saout @ 2005-04-05 17:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
Hi Andrew,
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Yes, works for me. DRI (i915) is working again and USB is now happy
after a PM resume too.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (14 preceding siblings ...)
2005-04-05 17:11 ` 2.6.12-rc2-mm1 Christophe Saout
@ 2005-04-06 1:44 ` Neil Brown
2005-04-06 22:19 ` 2.6.12-rc2-mm1 Andrew Morton
2005-04-07 0:40 ` 2.6.12-rc2-mm1 Ed Tomlinson
2005-04-07 7:14 ` 2.6.12-rc2-mm1 Mickael Marchand
17 siblings, 1 reply; 84+ messages in thread
From: Neil Brown @ 2005-04-06 1:44 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Tuesday April 5, akpm@osdl.org wrote:
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Well, Seeing you asked...
PM resume certainly seems to be improving.
My main problem in rc1-mm3 is with PCMCIA.
If I stop cardmgr before suspend-to-RAM, and then try to
restart it after resume, I cannot. Some message about the socket
being in use, and am I sure there is no other cardmgr running (there
isn't).
I can stop and restart happily before suspending, but not after.
If I leave it running during a suspend/resume cycle it keeps working
but if I then stop and restart, it fails.
(and if I do leave it running, my PCMCIA wireless gets started before
my tg3 wired, so eth0 and eth1 get swapped).
I just tried rc2-mm1 and... decided to go back to rc1-mm3.
It seemed to boot mostly OK. I tried suspend-to-RAM and it seems to
suspend. But when I turned it back on again it rebooted rather than
resumed.
During boot I got:
Apr 6 10:18:46 localhost kernel: cs: memory probe 0xf6000000-0xfbffffff:iounmap: bad address f8828000
Apr 6 10:18:46 localhost kernel: [set_cis_map+150/256] set_cis_map+0x96/0x100
Apr 6 10:18:46 localhost kernel: [remove_vm_area+60/80] remove_vm_area+0x3c/0x50
Apr 6 10:18:46 localhost kernel: [pcmcia_read_cis_mem+412/560] pcmcia_read_cis_mem+0x19c/0x230
Apr 6 10:18:46 localhost kernel: [set_cis_map+150/256] set_cis_map+0x96/0x100
Apr 6 10:18:46 localhost kernel: [read_cis_cache+358/400] read_cis_cache+0x166/0x190
Apr 6 10:18:46 localhost kernel: [follow_link+141/544] follow_link+0x8d/0x220
Apr 6 10:18:46 localhost kernel: [pccard_get_next_tuple+688/784] pccard_get_next_tuple+0x2b0/0x310
Apr 6 10:18:46 localhost kernel: [pccard_get_first_tuple+144/336] pccard_get_first_tuple+0x90/0x150
Apr 6 10:18:46 localhost kernel: [pccard_validate_cis+151/592] pccard_validate_cis+0x97/0x250
Apr 6 10:18:46 localhost kernel: [readable+90/160] readable+0x5a/0xa0
Apr 6 10:18:46 localhost kernel: [cis_readable+129/224] cis_readable+0x81/0xe0
Apr 6 10:18:46 localhost kernel: [do_mem_probe+469/496] do_mem_probe+0x1d5/0x1f0
Apr 6 10:18:46 localhost kernel: [inv_probe+159/176] inv_probe+0x9f/0xb0
Apr 6 10:18:46 localhost kernel: [validate_mem+271/304] validate_mem+0x10f/0x130
Apr 6 10:18:46 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:18:46 localhost kernel: [pcmcia_nonstatic_validate_mem+120/128] pcmcia_nonstatic_validate_mem+0x78/0x80
Apr 6 10:18:46 localhost kernel: [pcmcia_validate_mem+26/32] pcmcia_validate_mem+0x1a/0x20
Apr 6 10:18:46 localhost kernel: [pcmcia_card_add+42/208] pcmcia_card_add+0x2a/0xd0
....
Then it hung in some device discovery. Not sure which device, maybe
firewire.
Alt-Sysrq-T showed
Apr 6 10:19:45 localhost kernel: khpsbpkt S C04643E0 0 1956 1 1973 915 (L-TLB)
Apr 6 10:19:45 localhost kernel: f6cf3f94 00000046 f68dd070 c04643e0 f7c0f030 c0464410 00000000 f7c0f030
Apr 6 10:19:45 localhost kernel: f6cf3f8c 00000000 00000000 00000000 f68dd070 f68dd198 f8af2444 f6cf2000
Apr 6 10:19:45 localhost kernel: 00000246 f68dd070 c031ce5d f8af244c 00000000 00000001 f68dd070 c0114a70
Apr 6 10:19:45 localhost kernel: Call Trace:
Apr 6 10:19:45 localhost kernel: [__down_interruptible+157/300] __down_interruptible+0x9d/0x12c
Apr 6 10:19:45 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:19:45 localhost kernel: [__down_failed_interruptible+7/12] __down_failed_interruptible+0x7/0xc
Apr 6 10:19:45 localhost kernel: [pg0+945105653/1067918336] .text.lock.ieee1394_core+0x1b/0x26 [ieee1394]
Apr 6 10:19:45 localhost kernel: [pg0+945105424/1067918336] hpsbpkt_thread+0x0/0xb0 [ieee1394]
Apr 6 10:19:45 localhost kernel: [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Apr 6 10:19:45 localhost kernel: knodemgrd_0 S C04643E0 0 1973 1 2023 1956 (L-TLB)
Apr 6 10:19:45 localhost kernel: f7e75f7c 00000046 f7c0f030 c04643e0 0000a1ff 00000000 c018a7cc f648e62c
Apr 6 10:19:45 localhost kernel: f6ec8380 00000000 00000000 00000000 f7c0f030 f7c0f158 f6f6b670 f7e74000
Apr 6 10:19:45 localhost kernel: 00000246 f7c0f030 c031ce5d f6f6b678 00000000 00000001 f7c0f030 c0114a70
Apr 6 10:19:45 localhost kernel: Call Trace:
Apr 6 10:19:45 localhost kernel: [sysfs_make_dirent+44/160] sysfs_make_dirent+0x2c/0xa0
Apr 6 10:19:45 localhost kernel: [__down_interruptible+157/300] __down_interruptible+0x9d/0x12c
Apr 6 10:19:45 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:19:45 localhost kernel: [__down_failed_interruptible+7/12] __down_failed_interruptible+0x7/0xc
Apr 6 10:19:45 localhost kernel: [pg0+945133083/1067918336] .text.lock.nodemgr+0x112/0x1a7 [ieee1394]
Apr 6 10:19:45 localhost kernel: [pg0+945131536/1067918336] nodemgr_host_thread+0x0/0x190 [ieee1394]
Apr 6 10:19:45 localhost kernel: [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Apr 6 10:19:45 localhost kernel: grep D C04643E0 0 2023 1 2036 1973 (NOTLB)
Apr 6 10:19:45 localhost kernel: f640beec 00000086 f6c6da50 c04643e0 00000000 f640bec4 f710ca50 f640bec4
Apr 6 10:19:45 localhost kernel: f640bec4 00000000 00000000 00000000 f6c6da50 f6c6db78 f7291424 f6c6da50
Apr 6 10:19:45 localhost kernel: 00000282 f729142c c031cd4b 00000001 f6c6da50 c0114a70 f729142c f729142c
Apr 6 10:19:45 localhost kernel: Call Trace:
Apr 6 10:19:45 localhost kernel: [__down+123/240] __down+0x7b/0xf0
Apr 6 10:19:45 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:19:45 localhost kernel: [__down_failed+7/12] __down_failed+0x7/0xc
Apr 6 10:19:45 localhost kernel: [.text.lock.usb+22/186] .text.lock.usb+0x16/0xba
Apr 6 10:19:45 localhost kernel: [usb_device_read+186/288] usb_device_read+0xba/0x120
Apr 6 10:19:45 localhost kernel: [usb_device_read+0/288] usb_device_read+0x0/0x120
Apr 6 10:19:45 localhost kernel: [vfs_read+182/368] vfs_read+0xb6/0x170
Apr 6 10:19:45 localhost kernel: [sys_read+81/128] sys_read+0x51/0x80
Apr 6 10:19:45 localhost kernel: [syscall_call+7/11] syscall_call+0x7/0xb
I think those are the interesting processes, but I can get the full
list if it is useful.
I managed to proceed into the boot with alt-sysrq-E (tErm) but when it
came up enough bits had been killed that I decided to cut my losses
and go back to a previous working kernel...
This in on a Dell Lattitude D800
NeilBrown
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-06 1:44 ` 2.6.12-rc2-mm1 Neil Brown
@ 2005-04-06 22:19 ` Andrew Morton
0 siblings, 0 replies; 84+ messages in thread
From: Andrew Morton @ 2005-04-06 22:19 UTC (permalink / raw)
To: Neil Brown; +Cc: linux-kernel, Dominik Brodowski
Neil Brown <neilb@cse.unsw.edu.au> wrote:
>
> On Tuesday April 5, akpm@osdl.org wrote:
> >
> > - Nobody said anything about the PM resume and DRI behaviour in
> > 2.6.12-rc1-mm4. So it's all perfect now?
>
> Well, Seeing you asked...
>
> PM resume certainly seems to be improving.
> My main problem in rc1-mm3 is with PCMCIA.
> If I stop cardmgr before suspend-to-RAM, and then try to
> restart it after resume, I cannot. Some message about the socket
> being in use, and am I sure there is no other cardmgr running (there
> isn't).
I don't know whether the PCMCIA problem is due to PCMCIA changes or not.
The only thing I see having changed between 2.6.12-rc1-mm3 and
2.6.12-rc2-mm1 is the addition of pcmcia-resource-handling-fixes.patch.
Would you have time to revert that, retest?
There have been a few problem in the area of device management in
bk-driver-core. I think we're getting that settled down now.
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (15 preceding siblings ...)
2005-04-06 1:44 ` 2.6.12-rc2-mm1 Neil Brown
@ 2005-04-07 0:40 ` Ed Tomlinson
2005-04-07 7:14 ` 2.6.12-rc2-mm1 Mickael Marchand
17 siblings, 0 replies; 84+ messages in thread
From: Ed Tomlinson @ 2005-04-07 0:40 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Tuesday 05 April 2005 03:05, Andrew Morton wrote:
> - x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
> `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be fixed. We
> haven't heard yet.
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
>
> - Various fixes and updates. Nothing earth-shattering.
This refuses to boot here. It dies when assigning the EHCI driver. The mb is an MSI-7030 K8N Neo Platinium
based on a nForce 3 250Gb Chipset (x86_64). I`ve been on vacation - the last kernel tried was 11-mm3 which
booted fine but refuses to use all the usb ports supplied by the system (two work, three do not all using low
speed).
Any ideas what might be happening?
Ed Tomlinson
^ permalink raw reply [flat|nested] 84+ messages in thread* Re: 2.6.12-rc2-mm1
2005-04-05 7:05 2.6.12-rc2-mm1 Andrew Morton
` (16 preceding siblings ...)
2005-04-07 0:40 ` 2.6.12-rc2-mm1 Ed Tomlinson
@ 2005-04-07 7:14 ` Mickael Marchand
2005-04-08 18:13 ` [-mm patch] x86_64: kill obsolete check_nmi_watchdog prototype Adrian Bunk
17 siblings, 1 reply; 84+ messages in thread
From: Mickael Marchand @ 2005-04-07 7:14 UTC (permalink / raw)
To: linux-kernel; +Cc: Andrew Morton
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
> `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be fixed. We
> haven't heard yet.
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
>
> - Various fixes and updates. Nothing earth-shattering.
>
Hi,
-> compiling 2.6.12-rc2-mm1 on amd64 :
arch/x86_64/kernel/nmi.c:116: error: static declaration of
'check_nmi_watchdog' follows non-static declaration
include/asm/apic.h:102: error: previous declaration of
'check_nmi_watchdog' was here
I guess the fix is easy enough :)
-> while I am it, I got a soft lookup on a bi-opteron using
2.6.12-rc1-mm4 (while stressing reiser4 with rsync so I guess it is
reiser4's fault ;)
config at
http://www-fourier.ujf-grenoble.fr/~mmarcha/config-2.6.12-rc1-mm4.gz
I also got some "flushing like mad" warning messages from reiser4 (which
are safe apparently).
BUG: soft lockup detected on CPU#0!
Modules linked in: ipv6 parport_pc parport eth1394 ehci_hcd uhci_hcd
ohci1394 ieee1394 ohci_hcd usbcore snd_intel8x0 snd_ac97_codec snd_pcm
snd_timer snd snd_page_alloc i2c_amd756 i2c_amd8111 i2c_isa w83781d
i2c_sensor i2c_core e1000
Pid: 25291, comm: pdflush Not tainted 2.6.12-rc1-mm4
RIP: 0010:[<ffffffff8021f7de>] <ffffffff8021f7de>{protect_extent_nodes+382}
RSP: 0018:ffff81007df45678 EFLAGS: 00000202
RAX: ffff810015c7c5e0 RBX: ffff81007c609000 RCX: ffff81001074ba60
RDX: ffff81001074b220 RSI: ffff81001074b1c0 RDI: ffff81001074b210
RBP: 0000002000000000 R08: ffff81007df458a0 R09: ffff810044068e14
R10: 000000000000001c R11: ffffffff802119a0 R12: 00007fe07df455e0
R13: ffff81007c609004 R14: ffff81007df4565c R15: 00007fe000000001
FS: 00002aaaaadfeae0(0000) GS:ffffffff806e7840(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002aaaaaac2000 CR3: 000000009bc83000 CR4: 00000000000006e0
Call Trace:<ffffffff8021f7da>{protect_extent_nodes+378}
<ffffffff8021c00e>{extent_size+30}
<ffffffff801f5df9>{txnh_get_atom+41}
<ffffffff8021ffd2>{alloc_extent+562}
<ffffffff8020a0bc>{plugin_by_unsafe_id+28}
<ffffffff80220bd1>{item_length_by_coord+17}
<ffffffff801f8a4f>{handle_pos_on_twig+351}
<ffffffff801fabc6>{flush_current_atom+2022}
<ffffffff801f7aca>{flush_some_atom+458}
<ffffffff801a2993>{generic_sync_sb_inodes+723}
<ffffffff8014cc50>{keventd_create_kthread+0}
<ffffffff80203b85>{reiser4_sync_inodes+229}
<ffffffff801a2bd9>{writeback_inodes+137}
<ffffffff8016012c>{background_writeout+124}
<ffffffff80160c10>{pdflush+0} <ffffffff80160d4c>{pdflush+316}
<ffffffff801600b0>{background_writeout+0}
<ffffffff8014cec9>{kthread+217}
<ffffffff80133160>{schedule_tail+64} <ffffffff8010f59b>{child_rip+8}
<ffffffff8014cc50>{keventd_create_kthread+0}
<ffffffff8014cdf0>{kthread+0}
<ffffffff8010f593>{child_rip+0}
Cheers,
Mik
^ permalink raw reply [flat|nested] 84+ messages in thread* [-mm patch] x86_64: kill obsolete check_nmi_watchdog prototype
2005-04-07 7:14 ` 2.6.12-rc2-mm1 Mickael Marchand
@ 2005-04-08 18:13 ` Adrian Bunk
2005-04-08 18:21 ` Mickael Marchand
0 siblings, 1 reply; 84+ messages in thread
From: Adrian Bunk @ 2005-04-08 18:13 UTC (permalink / raw)
To: Mickael Marchand; +Cc: linux-kernel, Andrew Morton, jfv
On Thu, Apr 07, 2005 at 09:14:19AM +0200, Mickael Marchand wrote:
>...
> -> compiling 2.6.12-rc2-mm1 on amd64 :
>
> arch/x86_64/kernel/nmi.c:116: error: static declaration of
> 'check_nmi_watchdog' follows non-static declaration
> include/asm/apic.h:102: error: previous declaration of
> 'check_nmi_watchdog' was here
Is this with gcc 4.0?
> I guess the fix is easy enough :)
>...
Yup, fix below.
> Cheers,
> Mik
cu
Adrian
<-- snip -->
This patch kills an obsolete check_nmi_watchdog prototype
(check_nmi_watchdog is now static) found by
Mickael Marchand <marchand@kde.org>.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h.old 2005-04-08 20:12:01.000000000 +0200
+++ linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h 2005-04-08 20:12:11.000000000 +0200
@@ -99,7 +99,6 @@
extern void enable_APIC_timer(void);
extern void clustered_apic_check(void);
-extern int check_nmi_watchdog(void);
extern void nmi_watchdog_default(void);
extern int setup_nmi_watchdog(char *);
^ permalink raw reply [flat|nested] 84+ messages in thread
* Re: [-mm patch] x86_64: kill obsolete check_nmi_watchdog prototype
2005-04-08 18:13 ` [-mm patch] x86_64: kill obsolete check_nmi_watchdog prototype Adrian Bunk
@ 2005-04-08 18:21 ` Mickael Marchand
0 siblings, 0 replies; 84+ messages in thread
From: Mickael Marchand @ 2005-04-08 18:21 UTC (permalink / raw)
To: Adrian Bunk; +Cc: linux-kernel, Andrew Morton, jfv
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Adrian Bunk a écrit :
> On Thu, Apr 07, 2005 at 09:14:19AM +0200, Mickael Marchand wrote:
>
>>...
>>-> compiling 2.6.12-rc2-mm1 on amd64 :
>>
>>arch/x86_64/kernel/nmi.c:116: error: static declaration of
>>'check_nmi_watchdog' follows non-static declaration
>>include/asm/apic.h:102: error: previous declaration of
>>'check_nmi_watchdog' was here
>
>
> Is this with gcc 4.0?
yes :)
>
>
>>I guess the fix is easy enough :)
>>...
>
>
> Yup, fix below.
yes, I realize that I should just have just posted it.
thanks for doing it.
Cheers,
Mik
>
>
>>Cheers,
>>Mik
>
>
> cu
> Adrian
>
>
> <-- snip -->
>
>
> This patch kills an obsolete check_nmi_watchdog prototype
> (check_nmi_watchdog is now static) found by
> Mickael Marchand <marchand@kde.org>.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h.old 2005-04-08 20:12:01.000000000 +0200
> +++ linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h 2005-04-08 20:12:11.000000000 +0200
> @@ -99,7 +99,6 @@
> extern void enable_APIC_timer(void);
> extern void clustered_apic_check(void);
>
> -extern int check_nmi_watchdog(void);
> extern void nmi_watchdog_default(void);
> extern int setup_nmi_watchdog(char *);
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCVsubyOYzc4nQ8j0RAooBAJ9wnRNrhAVmRM6VUuqLY7Bms/uxTgCgml3R
OezYa56tE0cw6GBn0BYO2Qo=
=aK0h
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 84+ messages in thread