* oops 2.6.1 adsl
From: rollor @ 2004-01-28 20:01 UTC (permalink / raw)
To: linux-kernel
hi,
I am testing the 2.6.1 kernel on a p4,
debian sarge. I tried to start my adsl
connection and received this:
Jan 28 17:40:54 rock pppd[913]: pppd
2.4.2 started by oot, uid 0
Jan 28 17:40:54 rock pppd[913]: Serial
connection established.
Jan 28 17:40:54 rock pppd[913]: Using
interface ppp0
Jan 28 17:40:54 rock pppd[913]:
Connect: ppp0 <--> /dev/pts/0
Jan 28 17:40:54 rock kernel: Badness
in local_bh_enable at kernel/softirq.c:121
Jan 28 17:40:54 rock kernel: Call Trace:
Jan 28 17:40:54 rock kernel:
[local_bh_enable+133/135]
local_bh_enable+0x85/0x87 Jan 28
17:40:54 rock kernel:
[ppp_async_push+158/373]
ppp_async_push+0x9e/0x175
Jan 28 17:40:54 rock kernel:
[ppp_asynctty_wakeup+45/94]
ppp_asynctty_wakeup+0x2d/0x5e
Jan 28 17:40:54 rock kernel:
[pty_unthrottle+88/90]
pty_unthrottle+0x58/0x5a Jan
28 17:40:54 rock kernel:
[check_unthrottle+57/59]
check_unthrottle+0x39/0x3b
Jan 28 17:40:54 rock kernel:
[n_tty_flush_buffer+19/85]
n_tty_flush_buffer+0x13/0x55
Jan 28 17:40:54 rock kernel:
[pty_flush_buffer+102/104]
pty_flush_buffer+0x66/0x68
Jan 28 17:40:54 rock kernel:
[do_tty_hangup+1146/1243]
do_tty_hangup+0x47a/0x4db
Jan 28 17:40:54 rock kernel:
[release_dev+1752/1796]
release_dev+0x6d8/0x704
Jan 28 17:40:54 rock kernel:
[unmap_page_range+67/105]
unmap_page_range+0x43/0x69 Jan 28
17:40:54 rock pppd[913]: Modem hangup
Jan 28 17:40:54 rock kernel:
[tty_release+45/102] tty_release+0x2d/0x66
Jan 28 17:40:54 rock pppd[913]:
Connection terminated.
Jan 28 17:40:54 rock kernel:
[__fput+258/276] __fput+0x102/0x114
Jan 28 17:40:54 rock kernel:
[filp_close+89/134] filp_close+0x59/0x86
Jan 28 17:40:54 rock kernel:
[put_files_struct+132/233]
put_files_struct+0x84/0xe9 Jan 28
17:40:54 rock kernel:
[do_exit+397/1034] do_exit+0x18d/0x40a
Jan 28 17:40:54 rock kernel:
[do_group_exit+58/172]
do_group_exit+0x3a/0xac
Jan 28 17:40:54 rock kernel:
[syscall_call+7/11] syscall_call+0x7/0xb
if someone needs more information,
please let me now.
PS: CC to me.
thanks.
__________________________________________________________________________
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - É grátis!
http://antipopup.uol.com.br/
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 20:01 UTC (permalink / raw)
To: davidm; +Cc: davidm, iod00d, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <16408.4597.123125.788631@napali.hpl.hp.com>
On Wed, 28 Jan 2004 11:48:05 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Wed, 28 Jan 2004 20:39:15 +0100, Andi Kleen <ak@suse.de> said:
>
> >> Yet they are a good indicator that something is wrong (not performing
> >> properly) or may be failing soon. I don't think putting on blinders
> >> for such problems is a good idea. Though I agree that the question of
>
> Andi> Most server class hardware should log it somewhere and allow
> Andi> to read the event log in the firmware. This even works for
> Andi> unhandleable errors unlike what the OS could do.
>
> And you'd want to reboot your server just so you can check on the soft
> failure rate? ;-)
Yep, I reboot my machines all the time ;-)
Seriously you can count it somewhere and present it in sysfs or /proc.
Or log it somewhere else and supply a special utility to show them
that makes it clear that the events are hardware and not software related.
I suppose if your server vendor is serious they will supply a tool
to read the firmware log from a running system.
But printks enabled by default are a bad idea (and a bug too BTW - printk called from
MCE handlers can randomly deadlock)
-Andi
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: Torrey Hoffman @ 2004-01-28 19:55 UTC (permalink / raw)
To: Andrew Morton; +Cc: Linux-Kernel List, linux-mm
In-Reply-To: <20040127233402.6f5d3497.akpm@osdl.org>
On Tue, 2004-01-27 at 23:34, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2.6.2-rc2-mm1/
Got this during system startup, just before X came up.
System is Fedora Core 1 with lots of updates on a P4 HT.
(I include a few lines before and after from dmesg, in case context is
relevant?)
...
lp: driver loaded but no devices found
request_module: failed /sbin/modprobe -- char-major-4-72. error = 256
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49844 usecs
intel8x0: clocking to 48000
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c0243b74
*pde = 00000000
Oops: 0000 [#1]
PREEMPT SMP
CPU: 1
EIP: 0060:[<c0243b74>] Not tainted VLI
EFLAGS: 00010286
EIP is at vt_ioctl+0x14/0x1f80
eax: 00000000 ebx: f5dde000 ecx: 00005607 edx: f14cd480
esi: f5dde000 edi: 00005607 ebp: f6593f70 esp: f6593ea0
ds: 007b es: 007b ss: 0068
Process X (pid: 2378, threadinfo=f6592000 task=f11ca6c0)
Stack: 00000006 f7f00068 f7043005 00299a31 00000003 f7337280 f6593f14
f6593f6c
f6593f0c f7337280 f6e88480 f6593ee0 c0178bec f6593f0c f7043008
f6e88480
f6593f30 c016fdda 00000020 f6593f30 00001846 00000001 c047991e
f7177e00
Call Trace:
[<c0178bec>] dput+0x1c/0x2d0
[<c016fdda>] link_path_walk+0x6ba/0xa60
[<c016adc4>] cdev_get+0x54/0xc0
[<c016ae3f>] cdev_put+0xf/0x60
[<c01232f0>] schedule+0x3b0/0x740
[<c0243b60>] vt_ioctl+0x0/0x1f80
[<c023e885>] tty_ioctl+0x355/0x450
[<c0173e6b>] sys_ioctl+0x11b/0x2d0
[<c023e530>] tty_ioctl+0x0/0x450
[<c0160b96>] sys_open+0x56/0x70
[<c033c65a>] sysenter_past_esp+0x43/0x69
Code: ff e8 05 88 ec ff e9 70 ff ff ff 90 90 90 90 90 90 90 90 90 90 90
90 55 89 e5 57 56 53 81 ec c4 00 00 00 89 c6 8b 80 78 09 00 00 <8b> 00
89 85 30 ff ff ff 8b 04 85 20 9b 47 c0 89 45 8c 8b 85 30
<7>request_module: failed /sbin/modprobe -- char-major-10-134. error =
256
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
--
Torrey Hoffman <thoffman@arnor.net>
^ permalink raw reply
* Re: 2.6.2-rc2-mm1:Badness in try_to_wake_up at kernel/sched.c:722
From: Felipe Alfaro Solana @ 2004-01-28 19:52 UTC (permalink / raw)
To: Adam Koszela; +Cc: Linux Kernel Mailinglist
In-Reply-To: <1075312502.2090.28.camel@arrakis>
On Wed, 2004-01-28 at 18:55, Adam Koszela wrote:
> So here's my problem:
> Performance, especially when switching/launching/killing apps is awful,
> and dmesg spits out:
>
> Badness in try_to_wake_up at kernel/sched.c:722
> Call Trace:
> [<c011aac5>] try_to_wake_up+0x91/0x1c9
C'mon people, this has been reported at least four times ;-)
I'm sure Andrew is looking into it right now.
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: David Mosberger @ 2004-01-28 19:48 UTC (permalink / raw)
To: Andi Kleen
Cc: davidm, davidm, iod00d, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128203915.22d84e8d.ak@suse.de>
>>>>> On Wed, 28 Jan 2004 20:39:15 +0100, Andi Kleen <ak@suse.de> said:
>> Yet they are a good indicator that something is wrong (not performing
>> properly) or may be failing soon. I don't think putting on blinders
>> for such problems is a good idea. Though I agree that the question of
Andi> Most server class hardware should log it somewhere and allow
Andi> to read the event log in the firmware. This even works for
Andi> unhandleable errors unlike what the OS could do.
And you'd want to reboot your server just so you can check on the soft
failure rate? ;-)
--david
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 19:40 UTC (permalink / raw)
To: Linus Torvalds; +Cc: willy, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <Pine.LNX.4.58.0401281129570.28145@home.osdl.org>
On Wed, 28 Jan 2004 11:33:33 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:
> For example, if checking for an error involves actually reading a value
> from a bridge register, then that implies some _serious_ amount of
> serialization and external CPU stuff.
Which is _extremly_ hard to do from an MCE handler ...
(currently all our MCE handlers are buggy because they can deadlock on the
printk lock)
-Andi
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 19:39 UTC (permalink / raw)
To: davidm; +Cc: davidm, iod00d, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <16408.3157.336306.812481@napali.hpl.hp.com>
On Wed, 28 Jan 2004 11:24:05 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Wed, 28 Jan 2004 19:52:46 +0100, Andi Kleen <ak@suse.de> said:
>
> >> I find this comment interesting. Can you elaborate what you mean by
> >> "slightly buggy systems"?
>
> Andi> e.g. one bit ECC errors in memory are quite common. And with
> Andi> ECC memory they are not really fatal.
>
> Yet they are a good indicator that something is wrong (not performing
> properly) or may be failing soon. I don't think putting on blinders
> for such problems is a good idea. Though I agree that the question of
Most server class hardware should log it somewhere and allow
to read the event log in the firmware. This even works for unhandleable
errors unlike what the OS could do.
But when printed in Linux they will report it to the linux maintainer or their
distribution vendor. "My Linux is buggy and giving these weird messages" And they
are both in no position at all to do something about it.
I toyed with the idea of printking a disclaimer of
"This is likely not a software bug. Report it to your hardware vendor."
But I doubt this would help much. Even when you say clearly in the message
that the hardware failed the user sees a weird message and thinks
it is Linux's fault.
You could enable it with CONFIG_I_HAVE_A_HARDWARE_SUPPORT_CONTRACT_OR_I_WRITE_DRIVERS
Or just make it a kernel command line option with off by default.
-Andi
^ permalink raw reply
* Re: 2.6.2-rc2-mm1
From: David S. Miller @ 2004-01-28 19:38 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: akpm, linux-kernel, linux-mm, netdev
In-Reply-To: <20040128094106.A26158@infradead.org>
On Wed, 28 Jan 2004 09:41:06 +0000
Christoph Hellwig <hch@infradead.org> wrote:
> On Tue, Jan 27, 2004 at 11:34:02PM -0800, Andrew Morton wrote:
> > Jeff's tree: netdev.patch
>
> Any plan when we'll get the damn netdev lifetime rule fixes merged?
> They're real life problems and have been around for a long time..
Please be more specific, show me what patch you're talking about.
^ permalink raw reply
* Re: some combinations of make targets do not work anymore
From: Sam Ravnborg @ 2004-01-28 19:45 UTC (permalink / raw)
To: Olaf Hering; +Cc: linux-kernel
In-Reply-To: <20040128180111.GA23021@suse.de>
On Wed, Jan 28, 2004 at 07:01:11PM +0100, Olaf Hering wrote:
>
> Stuff like that used to work with 2.4 kernels, 2.6.2-rc2-mm2 runs make
> oldconfig and depmod, but 'all' and 'modules_install' is not executed.
> Bug or feature? target is ppc32.
Unexpected to say it. I have noticed some time ago, but since noone complained...
I will take a look.
Sam
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Linus Torvalds @ 2004-01-28 19:33 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: Hironobu Ishii, linux-kernel, linux-ia64
In-Reply-To: <20040128182003.GL11844@parcelfarce.linux.theplanet.co.uk>
On Wed, 28 Jan 2004, Matthew Wilcox wrote:
>
> If there are, Linus' interface is probably the best one. If not, we could
> simply have readX_check() / writeX_check() call dev->driver->unregister()
> if they notice an error has occurred and then the driver doesn't even
> need to call read_pcix_errors().
What worries me is that not only can the errors be asynchronous, they may
well be relatively expensive to check for.
For example, if checking for an error involves actually reading a value
from a bridge register, then that implies some _serious_ amount of
serialization and external CPU stuff.
The advantage of having the "check for errors" be done later and
independently of the actual IO access itself is not only that I think it
makes the code look nicer - it also allows you to do the IO independently
of the check. Which potentially means that the CPU can burst out the
writes as a burst write, rather than doing them one at a time and then
doing a read of a bridge register in between that serializes everything.
Linus
^ permalink raw reply
* 2.6.2-rc2-mm1 scheduler badness
From: Adam Koszela @ 2004-01-28 19:26 UTC (permalink / raw)
To: Linux Kernel Mailing List
I sent this before, but I don't think it got through. Anyway, here goes:
I'm running Debian/unstable on a P4.
So here's my problem:
Performance, especially when switching/launching apps is awful,
and dmesg spits out massive amounts of:
Badness in try_to_wake_up at kernel/sched.c:722
Call Trace:
[<c011aac5>] try_to_wake_up+0x91/0x1c9
[<c0126fea>] schedule_timeout+0xb5/0xb7
[<c013aa84>] __get_free_pages+0x1f/0x41
[<c011bae1>] __wake_up_common+0x31/0x50
[<c011bb32>] __wake_up+0x32/0x57
[<c01311ef>] wake_futex+0x30/0x5b
[<c01314a8>] futex_requeue+0x1c3/0x1c8
[<c0131a03>] do_futex+0x48/0x80
[<c0131b47>] sys_futex+0x10c/0x124
[<c0311f13>] syscall_call+0x7/0xb
My .config:
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS 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
#
# Processor support
#
#
# Select all processors your kernel should support
#
# CONFIG_CPU_386 is not set
# CONFIG_CPU_486 is not set
# CONFIG_CPU_586 is not set
# CONFIG_CPU_586TSC is not set
# CONFIG_CPU_586MMX is not set
# CONFIG_CPU_686 is not set
# CONFIG_CPU_PENTIUMII is not set
# CONFIG_CPU_PENTIUMIII is not set
# CONFIG_CPU_PENTIUMM is not set
CONFIG_CPU_PENTIUM4=y
# CONFIG_CPU_K6 is not set
# CONFIG_CPU_K7 is not set
# CONFIG_CPU_K8 is not set
# CONFIG_CPU_CRUSOE is not set
# CONFIG_CPU_WINCHIPC6 is not set
# CONFIG_CPU_WINCHIP2 is not set
# CONFIG_CPU_WINCHIP3D is not set
# CONFIG_CPU_CYRIXIII is not set
# CONFIG_CPU_VIAC3_2 is not set
CONFIG_CPU_INTEL=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=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=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=m
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G 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
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_SLEEP is not set
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
CONFIG_X86_PM_TIMER=y
#
# 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=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_USE_VECTOR is not set
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_FW_LOADER=y
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD is not set
#
# 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_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 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_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX 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_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=y
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_OUI_DB=y
#
# Device Drivers
#
#
# Texas Instruments PCILynx requires I2C
#
CONFIG_IEEE1394_OHCI1394=y
#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=y
CONFIG_IEEE1394_ETH1394=y
CONFIG_IEEE1394_DV1394=y
CONFIG_IEEE1394_RAWIO=y
CONFIG_IEEE1394_CMP=y
CONFIG_IEEE1394_AMDTP=y
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN 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_IPV6=m
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=m
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
CONFIG_LLC=m
# CONFIG_LLC2 is not set
CONFIG_IPX=m
# CONFIG_IPX_INTERN 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
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=m
# CONFIG_E100_NAPI is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_8139_RXBUF_IDX=2
# 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
#
# 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_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# Bluetooth support
#
CONFIG_BT=y
CONFIG_BT_L2CAP=y
CONFIG_BT_SCO=y
CONFIG_BT_RFCOMM=y
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=y
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=y
# CONFIG_BT_HCIUSB_SCO is not set
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL 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=1280
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1024
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD 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_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC 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_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_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=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_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY 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_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_PCI_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
#
# Sound
#
CONFIG_SOUND=y
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=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=m
# 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
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_KORG1212 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 is not set
# 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_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
#
# USB Bluetooth TTY can only be used with disabled Bluetooth subsystem
#
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
#
# SCSI support is needed for USB Storage
#
# CONFIG_USB_STORAGE is not set
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
# 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_XPAD is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# 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
#
# USB port drivers
#
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=m
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=m
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_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 is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_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=y
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 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_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
--
Adam Koszela <lameaim@bredband.tiscali.se>
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: David Mosberger @ 2004-01-28 19:24 UTC (permalink / raw)
To: Andi Kleen
Cc: davidm, davidm, iod00d, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128195246.47a84498.ak@suse.de>
>>>>> On Wed, 28 Jan 2004 19:52:46 +0100, Andi Kleen <ak@suse.de> said:
>> I find this comment interesting. Can you elaborate what you mean by
>> "slightly buggy systems"?
Andi> e.g. one bit ECC errors in memory are quite common. And with
Andi> ECC memory they are not really fatal.
Yet they are a good indicator that something is wrong (not performing
properly) or may be failing soon. I don't think putting on blinders
for such problems is a good idea. Though I agree that the question of
how to report such things without needlessly alerting Joe Clueless is
an interesting challenge.
--david
^ permalink raw reply
* Re: long long on 32-bit machines
From: Arnd Bergmann @ 2004-01-28 19:22 UTC (permalink / raw)
To: linux-kernel; +Cc: H. Peter Anvin
H.P.A wrote:
> Does anyone happen to know if there are *any* 32-bit architectures (on
> which Linux runs) for which the ABI for a "long long" is different from
> passing two "longs" in the appropriate order, i.e. (hi,lo) for bigendian
> or (lo,hi) for littleendian?
Some architectures require long long arguments to be passed as an
even/odd register pair. For example on s390,
void f(int a, int b, long long x)
uses registers 2, 3, 4 and 5, while
void f(int a, long long x, int b)
uses registers 2, 4, 5 and 6. AFAIK, mips does the same, probably others
as well.
Arnd <><
^ permalink raw reply
* Re: [PATCH] smbfs: Large File Support (3/3)
From: Arjan van de Ven @ 2004-01-28 19:21 UTC (permalink / raw)
To: Linux Kernel Mailing List
In-Reply-To: <200401281202.i0SC2s6Y010350@hera.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
On Wed, 2004-01-28 at 06:05, Linux Kernel Mailing List wrote:
> diff -Nru a/include/linux/smb.h b/include/linux/smb.h
> --- a/include/linux/smb.h Wed Jan 28 04:02:56 2004
> +++ b/include/linux/smb.h Wed Jan 28 04:02:56 2004
> @@ -85,7 +85,7 @@
> uid_t f_uid;
> gid_t f_gid;
> kdev_t f_rdev;
> - off_t f_size;
> + loff_t f_size;
> time_t f_atime;
> time_t f_mtime;
> time_t f_ctime;
ehhmmmm doesn't this change the userspace ABI incompatibly ???
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* PROBLEM: ACPI crashes (2.6.2-rc2-mm1)
From: Georg C. F. Greve @ 2004-01-28 19:21 UTC (permalink / raw)
To: linux-kernel; +Cc: acpi-devel
[-- Attachment #1.1: Type: text/plain, Size: 502 bytes --]
Hi all,
still having problems with ACPI on ASUS M2N. [1]
With linux-2.6.2-rc2-mm1 with acpi4asus from CVS as of today:
Suspending to disk (S4) suspends just fine. It also finds the file and
reads the data back into active memory, as well. But when it comes to
the message
"Waiting for DMAs to settle down."
the machine suddenly crashes (reboot).
I tried to get some debugging output by not having swap mounted when
trying to suspend so it would have to come right back up. Here is the
output
[-- Attachment #1.2: Type: text/plain, Size: 619 bytes --]
Suspend Machine: Suspend failed, trying to recover...
Restarting tasks...<3>bad: scheduling while atomic!
Call Trace:
[<c011b553>] schedule+0x5b3/0x5c0
[<c011a5d9>] try_to_wake_up+0x109/0x1c0
[<c011a69d>] wake_up_process+0xd/0x20
[<c0135514>] thaw_processes+0xa4/0xe0
[<c013677d>] software_suspend+0x8d/0xc0
[<c01fe95a>] acpi_system_write_sleep+0xb3/0xce
[<c01530cc>] vfs_write+0x9c/0x100
[<c01531ad>] sys_write+0x2d/0x50
[<c0366de7>] syscall_call+0x7/0xb
done
bad: scheduling while atomic!
Call Trace:
[<c011b553>] schedule+0x5b3/0x5c0
[<c01531ad>] sys_write+0x2d/0x50
[<c0366e1a>] work_resched+0x5/0x16
[-- Attachment #1.3: Type: text/plain, Size: 708 bytes --]
Suspend to RAM (S3 via 3bios) seems to suspend the machine just
fine. Only the power button brings it back up, but when it comes back
up it seems to hang -- cannot tell as even though the disk seems to
have come activity the screen remains black and network apparently
doesn't come up.
Hope this helps tracking down the ACPI problems.
Help appreciated, if more input is needed, please let me know.
Regards,
Georg
[1] System info at http://bugzilla.kernel.org/show_bug.cgi?id=1774
--
Georg C. F. Greve <greve@gnu.org>
Free Software Foundation Europe (http://fsfeurope.org)
Brave GNU World (http://brave-gnu-world.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]
^ permalink raw reply
* Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 19:19 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: torvalds, ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128182003.GL11844@parcelfarce.linux.theplanet.co.uk>
On Wed, 28 Jan 2004 18:20:03 +0000
Matthew Wilcox <willy@debian.org> wrote:
> If there are, Linus' interface is probably the best one. If not, we could
> simply have readX_check() / writeX_check() call dev->driver->unregister()
> if they notice an error has occurred and then the driver doesn't even
> need to call read_pcix_errors().
It just won't really work for platforms with inexact MCEs for IO errors.
And even for those with exact MCEs it would probably be a nightmare
to implement (writing MCE handlers is extremly hard because you cannot
rely on any locking guarantees - even a printk can randomly deadlock)
For those the per pci_dev callback is the only realistic way.
-Andi
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Andi Kleen @ 2004-01-28 19:17 UTC (permalink / raw)
To: Grant Grundler; +Cc: ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128190923.GA6333@cup.hp.com>
On Wed, 28 Jan 2004 11:09:23 -0800
Grant Grundler <iod00d@hp.com> wrote:
> ...
> > In short this stuff
> > probably only makes sense when you're a system vendor who sells
> > support contracts for whole systems including hardware support.
> > For the normal linux model where software is independent from hardware
> > (and hardware is usually crappy) it just doesn't work very well.
>
> While ia64/parisc platforms have HW support for this,
> I totally agree it won't work well for most (x86) platforms.
> I'd like to reduce the burden on the driver writers for common
> drivers (eg MPT) used on "vanilla" x86.
It would probably a good idea to implement it for i386 on chipsets
that support it reliably and try to educate driver writers to
enable it when they are testing drivers. This would likely
improve the quality of linux drivers long term and make your
job as maintainer of an "anal IO error" platform easier.
Just it should not be enabled by default in production kernels.
And finding out where it works reliably will be some work.
>
> And like I pointed out before, linux kernel needs to review panic()
> calls to see if some of them could easily be eliminated. The general
> robustness issues (eg pci_map_single() panics on failure) aren't
> prerequisites for IO error checking, but the latter seems less
> useful with out the former.
There is no reason pci_map_single() has to panic on overflow. On x86-64
it returns an unmapped address that is guaranteed to cause an bus abort
for 128KB. And you have an macro to test for it (pci_dma_error()).
I believe ppc64 has adopted it too. Of course most drivers don't
use it yet.
Still panic on overflow is useful for testing and it is kept as an
kernel command line option.
-Andi
^ permalink raw reply
* Re: long long on 32-bit machines
From: David S. Miller @ 2004-01-28 19:15 UTC (permalink / raw)
To: Timothy Miller; +Cc: hpa, klibc, linux-kernel
In-Reply-To: <401809B2.70907@techsource.com>
On Wed, 28 Jan 2004 14:12:50 -0500
Timothy Miller <miller@techsource.com> wrote:
> I don't know how it is for GCC, but when using the Sun compiler, "long
> long" for 32-bit is low-high, while "long long" (or just long) for
> 64-bit is high-low. This has been an annoyance to me. :)
For 64-bit it goes into a single 64-bit register.
And for 32-bit the sequence is high 32-bits low 32-bits.
At least on Sparc.
extern void foo(long long a);
void bar(void)
{
foo(1);
}
/* gcc -m32 -S -o bar.s bar.c */
bar:
!#PROLOGUE# 0
save %sp, -104, %sp
!#PROLOGUE# 1
mov 0, %o0
mov 1, %o1
call foo, 0
nop
nop
ret
restore
/* gcc -m64 -S -o bar.s bar.c */
bar:
!#PROLOGUE# 0
save %sp, -192, %sp
!#PROLOGUE# 1
mov 1, %o0
call foo, 0
nop
nop
return %i7+8
^ permalink raw reply
* tdfxfb in linux-2.6 and 1GiB RAM
From: Gerardo Exequiel Pozzi @ 2004-01-28 19:13 UTC (permalink / raw)
To: linux-kernel; +Cc: hmallat, jsimmons, geert
Hi people,
I can't use frame buffer (tdfxfb) in linux-2.6 with 1GiB of RAM, but yes with 512MiB.
(The linux-2.4 works ok, in both cases.)
HIGHMEM disabled.
The another problem is, when boot in low resolution default 640x480 and switch with
fbset to 1024x768 for example, it changes ok, but can't draw in all screen, only in a
small area of 640x480 located at upper left of screen, the same for all VTs.
If you need more info in logs/proc/sysfs please let me know.
the @dmesg (1GiB) appears:
fb: Can't remap 3Dfx Voodoo5 register area.
tdfxfb: probe of 0000:01:00.0 failed with error -6
and @dmesg (512MiB):
fb: 3Dfx Voodoo5 memory = 32768K
lspci -vv output:
01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 4 / Voodoo 5 (rev 01) (prog-if 00 [VGA])
Subsystem: 3Dfx Interactive, Inc.: Unknown device 0004
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=128M]
Region 1: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Region 2: I/O ports at c000 [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [54] AGP version 2.0
Status: RQ=16 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit+ FW- AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
/proc/iomem (1GiB)
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-1ffeffff : System RAM
00100000-00366df4 : Kernel code
00366df5-0043613f : Kernel data
1fff0000-1fff2fff : ACPI Non-volatile Storage
1fff3000-1fffffff : ACPI Tables
d0000000-dfffffff : PCI Bus #01
d0000000-d7ffffff : 0000:01:00.0
e0000000-e7ffffff : PCI Bus #01
e0000000-e7ffffff : 0000:01:00.0
e8000000-ebffffff : 0000:00:00.0
ec000000-ec0000ff : 0000:00:09.0
ec000000-ec0000ff : 8139too
ec001000-ec0010ff : 0000:00:10.3
fec00000-fec00fff : reserved
fee00000-fee00fff : reserved
ffff0000-ffffffff : reserved
/proc/iomem (512MiB)
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-1ffeffff : System RAM
00100000-003504e0 : Kernel code
003504e1-0041c13f : Kernel data
1fff0000-1fff2fff : ACPI Non-volatile Storage
1fff3000-1fffffff : ACPI Tables
d0000000-dfffffff : PCI Bus #01
d0000000-d7ffffff : 0000:01:00.0
d0000000-d7ffffff : tdfx regbase
e0000000-e7ffffff : PCI Bus #01
e0000000-e7ffffff : 0000:01:00.0
e0000000-e7ffffff : tdfx smem
e8000000-ebffffff : 0000:00:00.0
ec000000-ec0000ff : 0000:00:09.0
ec000000-ec0000ff : 8139too
ec001000-ec0010ff : 0000:00:10.3
fec00000-fec00fff : reserved
fee00000-fee00fff : reserved
ffff0000-ffffffff : reserved
chau,
djgera
--
Gerardo Exequiel Pozzi ( djgera )
http://www.vmlinuz.com.ar http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
^ permalink raw reply
* Re: pmdisk working on ppc (WAS: Help port swsusp to ppc), swsusp2 works.
From: Hugang @ 2004-01-28 19:10 UTC (permalink / raw)
To: ncunningham
Cc: Benjamin Herrenschmidt, Pavel Machek, Patrick Mochel,
Linux Kernel Mailing List, linuxppc-dev list
In-Reply-To: <1075316748.12285.84.camel@laptop-linux>
On Thu, 29 Jan 2004 08:05:49 +1300
Nigel Cunningham <ncunningham@users.sourceforge.net> wrote:
> Congratulations on getting it going!
Not easy for me. But do it improve my kernel understand.
>
> I'll add it to the patch, but mark it as experimental for the moment.
thanks.
--
Hu Gang / Steve
Linux Registered User 204016
GPG Public Key: http://soulinfo.com/~hugang/HuGang.asc
^ permalink raw reply
* Re: Cset 1.1490.4.201 - dasd naming
From: Arnd Bergmann @ 2004-01-28 19:10 UTC (permalink / raw)
To: Martin Schwidefsky ; +Cc: linux-kernel, Pete Zaitcev, Horst Hummel
> That is probably the main argument to go back to the old names. After
> udev and friends are in place it is not important how the disk is named
> internally. The only place where it would surface is on the root=
> parameter.
Even for root=, it probably does not matter as long as udev is used
in the initrd/initramfs. The main argument against the new naming is
that udev can trivially create these or other persistent names, while
it's very hard for udev to calculate the compatible names.
Arnd <><
^ permalink raw reply
* Re: long long on 32-bit machines
From: Timothy Miller @ 2004-01-28 19:12 UTC (permalink / raw)
To: H. Peter Anvin; +Cc: klibc list, linux-kernel
In-Reply-To: <4017F991.2090604@zytor.com>
H. Peter Anvin wrote:
> Hi all,
>
> Does anyone happen to know if there are *any* 32-bit architectures (on
> which Linux runs) for which the ABI for a "long long" is different from
> passing two "longs" in the appropriate order, i.e. (hi,lo) for bigendian
> or (lo,hi) for littleendian?
>
> I'd like to switch klibc to use the 64-bit file ABI thoughout, but it's
> a considerable porting effort, and I'm trying to figure out how to best
> manage it.
>
I don't know how it is for GCC, but when using the Sun compiler, "long
long" for 32-bit is low-high, while "long long" (or just long) for
64-bit is high-low. This has been an annoyance to me. :)
^ permalink raw reply
* Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
From: Grant Grundler @ 2004-01-28 19:09 UTC (permalink / raw)
To: Andi Kleen; +Cc: ishii.hironobu, linux-kernel, linux-ia64
In-Reply-To: <20040128184137.616b6425.ak@suse.de>
On Wed, Jan 28, 2004 at 06:41:37PM +0100, Andi Kleen wrote:
> > I could be wrong. Exception handling is ugly.
...
> One big problem is how to get rid of the spinlocks after the exception though
> (hardware access usually happens inside a spinlock)
>
> I presume you could return a magic value (all ones), but then you still
> have to make sure the driver doesn't break when that happens.
yes - any proposal is going to require reviewing all PIO reads
and how the read return value is consumed (or discarded).
> That would
> likely require testing for that value on every read access and make
> the code similarly ugly and difficult to write as with Linus'
> explicit checking model.
yeah. My hope was it would be less invasive.
But more changes are probably needed than I expected.
...
> In short this stuff
> probably only makes sense when you're a system vendor who sells
> support contracts for whole systems including hardware support.
> For the normal linux model where software is independent from hardware
> (and hardware is usually crappy) it just doesn't work very well.
While ia64/parisc platforms have HW support for this,
I totally agree it won't work well for most (x86) platforms.
I'd like to reduce the burden on the driver writers for common
drivers (eg MPT) used on "vanilla" x86.
And like I pointed out before, linux kernel needs to review panic()
calls to see if some of them could easily be eliminated. The general
robustness issues (eg pci_map_single() panics on failure) aren't
prerequisites for IO error checking, but the latter seems less
useful with out the former.
I'd like to defend the pci_map_single() interface. It was designed
to reduce the complexity at the cost of robustness.
I think it was a fair trade off at the time and it sounds like
the time has come for a different trade off.
thanks,
grant
> -Andi
^ permalink raw reply
* Re: Official NVIDIA drivers for 2.6
From: Voicu Liviu @ 2004-01-28 19:05 UTC (permalink / raw)
To: Voicu Liviu; +Cc: Con Kolivas, linux kernel mailing list
In-Reply-To: <4017BFF8.7060706@mscc.huji.ac.il>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a Prophet 3D Radeon 9600 Pro 128 Ram, any chance to have it
working with 2.6x ?
Thanks
Voicu Liviu wrote:
| Anything about ATI support on 2.6x ? :-( Liviu
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAGAfbkj4I0Et8EMgRAnxyAJ0Tz1w7ZN0cbw3W9FZECbLFTaK5HgCfZNvA
i9oijFaVoWmWjysmL/0jIRc=
=2mSw
-----END PGP SIGNATURE-----
^ permalink raw reply
* Re: pmdisk working on ppc (WAS: Help port swsusp to ppc), swsusp2 works.
From: Nigel Cunningham @ 2004-01-28 19:05 UTC (permalink / raw)
To: Hugang
Cc: Benjamin Herrenschmidt, Pavel Machek, Patrick Mochel,
Linux Kernel Mailing List, linuxppc-dev list
In-Reply-To: <20040129012720.1385c41a@localhost>
Congratulations on getting it going!
I'll add it to the patch, but mark it as experimental for the moment.
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox