* Re: 2.4.21-pre3-ac2 oops
From: Magnus Månsson @ 2003-01-10 22:39 UTC (permalink / raw)
To: alan, linux-kernel
In-Reply-To: <20030110220919.GT7259@gagarin>
Just found out that I could fsck it in 2.4.20. So it has to be something
that is changed between those kernels. But I can't test any more kernels
due to the fact that my filesystem now is ok.
On Fri, Jan 10, 2003 at 11:09:19PM +0100, Magnus Månsson wrote:
> Hi,
> I have a problem while accessing one of my partitions. It started with
> oopses when I was rsyncing to the partition. After that I thought that I
> should run fsck and that also made my system oops.
>
> I have the same problem with 2.4.21-pre3-ac3, but it started in -ac2.
>
> My system is a Dell inspiron 8200 and here is my config and oops ran
> through ksymoops:
>
> ---[start oops]---
>
> ksymoops 2.4.8 on i686 2.4.21-pre3-ac3. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.21-pre3-ac3/ (default)
> -m /boot/System.map-2.4.21-pre3-ac3 (default)
>
> Warning: You did not tell me where to find symbol information. I will
> assume that the log matches the kernel and modules that are running
> right now and I'll use the default options above for symbol resolution.
> If the current kernel and/or modules do not match the log, you can get
> more accurate output by telling me the kernel version and where to find
> map, modules, ksyms etc. ksymoops -h explains the options.
>
> ac97_codec: AC97 Audio codec, id: CRY91 (Unknown)
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> cs: IO port probe 0x0c00-0x0cff: clean.
> cs: IO port probe 0x0800-0x08ff: clean.
> cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> Unable to handle kernel NULL pointer dereference at virtual address 00000004
> c01374ed
> *pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[<c01374ed>] Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010246
> eax: 00000000 ebx: c147a510 ecx: d7c94000 edx: d7c9405c
> esi: 00000000 edi: 00000000 ebp: c02b72b0 esp: d7c95dec
> ds: 0018 es: 0018 ss: 0018
> Process fsck.ext3 (pid: 1961, stackpage=d7c95000)
> Stack: 00000001 00000286 da168580 da168580 da168580 c147a510 c0141aee da168580
> df839428 c147a510 00004346 c02b72b0 c013667f c147a510 000001d2 d7c94000
> 00000200 000001d2 00000020 00000020 000001d2 00000020 00000006 c01368c3
> Call Trace: [<c0141aee>] [<c013667f>] [<c01368c3>] [<c0136936>] [<c01377d7>]
> [<c0137a63>] [<c012cf1c>] [<c012d207>] [<c0118158>] [<c010d3ee>] [<c0118020>]
> [<c0107438>]
> Code: 89 58 04 89 03 89 53 04 89 59 5c 89 73 0c ff 41 68 eb bf 0f
>
>
> >>EIP; c01374ed <__free_pages_ok+27d/2a0> <=====
>
> >>ebx; c147a510 <_end+112f4e8/2050b038>
> >>ecx; d7c94000 <_end+17948fd8/2050b038>
> >>edx; d7c9405c <_end+17949034/2050b038>
> >>ebp; c02b72b0 <contig_page_data+b0/340>
> >>esp; d7c95dec <_end+1794adc4/2050b038>
>
> Trace; c0141aee <try_to_free_buffers+8e/100>
> Trace; c013667f <shrink_cache+21f/310>
> Trace; c01368c3 <shrink_caches+63/a0>
> Trace; c0136936 <try_to_free_pages_zone+36/50>
> Trace; c01377d7 <balance_classzone+57/1f0>
> Trace; c0137a63 <__alloc_pages+f3/190>
> Trace; c012cf1c <do_anonymous_page+6c/120>
> Trace; c012d207 <handle_mm_fault+77/110>
> Trace; c0118158 <do_page_fault+138/4cf>
> Trace; c010d3ee <old_mmap+de/120>
> Trace; c0118020 <do_page_fault+0/4cf>
> Trace; c0107438 <error_code+34/3c>
>
> Code; c01374ed <__free_pages_ok+27d/2a0>
> 00000000 <_EIP>:
> Code; c01374ed <__free_pages_ok+27d/2a0> <=====
> 0: 89 58 04 mov %ebx,0x4(%eax) <=====
> Code; c01374f0 <__free_pages_ok+280/2a0>
> 3: 89 03 mov %eax,(%ebx)
> Code; c01374f2 <__free_pages_ok+282/2a0>
> 5: 89 53 04 mov %edx,0x4(%ebx)
> Code; c01374f5 <__free_pages_ok+285/2a0>
> 8: 89 59 5c mov %ebx,0x5c(%ecx)
> Code; c01374f8 <__free_pages_ok+288/2a0>
> b: 89 73 0c mov %esi,0xc(%ebx)
> Code; c01374fb <__free_pages_ok+28b/2a0>
> e: ff 41 68 incl 0x68(%ecx)
> Code; c01374fe <__free_pages_ok+28e/2a0>
> 11: eb bf jmp ffffffd2 <_EIP+0xffffffd2>
> Code; c0137500 <__free_pages_ok+290/2a0>
> 13: 0f 00 00 sldtl (%eax)
>
> <1>Unable to handle kernel NULL pointer dereference at virtual address 00000004
> c01374ed
> *pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[<c01374ed>] Not tainted
> EFLAGS: 00010246
> eax: 00000000 ebx: c14165c4 ecx: d7c94000 edx: d7c9405c
> esi: 00000000 edi: 00000000 ebp: 00000000 esp: d7c95c10
> ds: 0018 es: 0018 ss: 0018
> Process fsck.ext3 (pid: 1961, stackpage=d7c95000)
> Stack: 00000001 c01c1fe9 00000006 c011c53f c02bc820 c159d380 00000292 00000292
> 00000000 d8015190 00001000 00000001 c012d797 c14165c4 00000000 00000046
> c012574b c14165c4 08400000 df1d7084 08065000 00000000 c012bfeb d8690880
> Call Trace: [<c01c1fe9>] [<c011c53f>] [<c012d797>] [<c012574b>] [<c012bfeb>]
> [<c012eed9>] [<c011a9a7>] [<c011f88f>] [<c01079df>] [<c01182c4>] [<c01eb4a8>]
> [<c01eb686>] [<c01eb30e>] [<c01eaf30>] [<c01e6eed>] [<c0118020>] [<c0107438>]
> [<c01374ed>] [<c0141aee>] [<c013667f>] [<c01368c3>] [<c0136936>] [<c01377d7>]
> [<c0137a63>] [<c012cf1c>] [<c012d207>] [<c0118158>] [<c010d3ee>] [<c0118020>]
> [<c0107438>]
> Code: 89 58 04 89 03 89 53 04 89 59 5c 89 73 0c ff 41 68 eb bf 0f
>
>
> >>EIP; c01374ed <__free_pages_ok+27d/2a0> <=====
>
> >>ebx; c14165c4 <_end+10cb59c/2050b038>
> >>ecx; d7c94000 <_end+17948fd8/2050b038>
> >>edx; d7c9405c <_end+17949034/2050b038>
> >>esp; d7c95c10 <_end+1794abe8/2050b038>
>
> Trace; c01c1fe9 <vt_console_print+59/310>
> Trace; c011c53f <__call_console_drivers+5f/70>
> Trace; c012d797 <zap_pte_range+f7/120>
> Trace; c012574b <run_timer_list+10b/170>
> Trace; c012bfeb <zap_page_range+8b/f0>
> Trace; c012eed9 <exit_mmap+b9/160>
> Trace; c011a9a7 <mmput+47/a0>
> Trace; c011f88f <do_exit+8f/240>
> Trace; c01079df <die+7f/c0>
> Trace; c01182c4 <do_page_fault+2a4/4cf>
> Trace; c01eb4a8 <__ide_dma_begin+38/50>
> Trace; c01eb686 <__ide_dma_count+16/20>
> Trace; c01eb30e <__ide_dma_read+13e/150>
> Trace; c01eaf30 <dma_timer_expiry+0/e0>
> Trace; c01e6eed <do_rw_disk+1ed/6d0>
> Trace; c0118020 <do_page_fault+0/4cf>
> Trace; c0107438 <error_code+34/3c>
> Trace; c01374ed <__free_pages_ok+27d/2a0>
> Trace; c0141aee <try_to_free_buffers+8e/100>
> Trace; c013667f <shrink_cache+21f/310>
> Trace; c01368c3 <shrink_caches+63/a0>
> Trace; c0136936 <try_to_free_pages_zone+36/50>
> Trace; c01377d7 <balance_classzone+57/1f0>
> Trace; c0137a63 <__alloc_pages+f3/190>
> Trace; c012cf1c <do_anonymous_page+6c/120>
> Trace; c012d207 <handle_mm_fault+77/110>
> Trace; c0118158 <do_page_fault+138/4cf>
> Trace; c010d3ee <old_mmap+de/120>
> Trace; c0118020 <do_page_fault+0/4cf>
> Trace; c0107438 <error_code+34/3c>
>
> Code; c01374ed <__free_pages_ok+27d/2a0>
> 00000000 <_EIP>:
> Code; c01374ed <__free_pages_ok+27d/2a0> <=====
> 0: 89 58 04 mov %ebx,0x4(%eax) <=====
> Code; c01374f0 <__free_pages_ok+280/2a0>
> 3: 89 03 mov %eax,(%ebx)
> Code; c01374f2 <__free_pages_ok+282/2a0>
> 5: 89 53 04 mov %edx,0x4(%ebx)
> Code; c01374f5 <__free_pages_ok+285/2a0>
> 8: 89 59 5c mov %ebx,0x5c(%ecx)
> Code; c01374f8 <__free_pages_ok+288/2a0>
> b: 89 73 0c mov %esi,0xc(%ebx)
> Code; c01374fb <__free_pages_ok+28b/2a0>
> e: ff 41 68 incl 0x68(%ecx)
> Code; c01374fe <__free_pages_ok+28e/2a0>
> 11: eb bf jmp ffffffd2 <_EIP+0xffffffd2>
> Code; c0137500 <__free_pages_ok+290/2a0>
> 13: 0f 00 00 sldtl (%eax)
>
> <1>Unable to handle kernel NULL pointer dereference at virtual address 00000004
> c01374ed
> *pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[<c01374ed>] Not tainted
> EFLAGS: 00010246
> eax: 00000000 ebx: c147f764 ecx: d7c94000 edx: d7c9405c
> esi: 00000000 edi: 00000000 ebp: 00000000 esp: d7c95a30
> ds: 0018 es: 0018 ss: 0018
> Process fsck.ext3 (pid: 1961, stackpage=d7c95000)
> Stack: 00000001 00000286 da2ef200 da2ef200 da2ef200 c147f764 c0141aee da2ef200
> c147f764 c14801e0 df839428 00000000 c012f2b5 c147f764 dfe46740 dfe4675c
> df839380 c01433fb df839380 00000001 dfe46740 dfe46740 c01442fd dfe46740
> Call Trace: [<c0141aee>] [<c012f2b5>] [<c01433fb>] [<c01442fd>] [<c013e4c2>]
> [<c013caed>] [<c011f1cc>] [<c011f8ae>] [<c0118020>] [<c01079df>] [<c01182c4>]
> [<c01379bb>] [<c0118020>] [<c0107438>] [<c01374ed>] [<c01c1fe9>] [<c011c53f>]
> [<c012d797>] [<c012574b>] [<c012bfeb>] [<c012eed9>] [<c011a9a7>] [<c011f88f>]
> [<c01079df>] [<c01182c4>] [<c01eb4a8>] [<c01eb686>] [<c01eb30e>] [<c01eaf30>]
> [<c01e6eed>] [<c0118020>] [<c0107438>] [<c01374ed>] [<c0141aee>] [<c013667f>]
> [<c01368c3>] [<c0136936>] [<c01377d7>] [<c0137a63>] [<c012cf1c>] [<c012d207>]
> [<c0118158>] [<c010d3ee>] [<c0118020>] [<c0107438>]
> Code: 89 58 04 89 03 89 53 04 89 59 5c 89 73 0c ff 41 68 eb bf 0f
>
>
> >>EIP; c01374ed <__free_pages_ok+27d/2a0> <=====
>
> >>ebx; c147f764 <_end+113473c/2050b038>
> >>ecx; d7c94000 <_end+17948fd8/2050b038>
> >>edx; d7c9405c <_end+17949034/2050b038>
> >>esp; d7c95a30 <_end+1794aa08/2050b038>
>
> Trace; c0141aee <try_to_free_buffers+8e/100>
> Trace; c012f2b5 <invalidate_inode_pages+75/90>
> Trace; c01433fb <kill_bdev+1b/50>
> Trace; c01442fd <blkdev_put+ad/d0>
> Trace; c013e4c2 <fput+102/130>
> Trace; c013caed <filp_close+4d/80>
> Trace; c011f1cc <put_files_struct+6c/e0>
> Trace; c011f8ae <do_exit+ae/240>
> Trace; c0118020 <do_page_fault+0/4cf>
> Trace; c01079df <die+7f/c0>
> Trace; c01182c4 <do_page_fault+2a4/4cf>
> Trace; c01379bb <__alloc_pages+4b/190>
> Trace; c0118020 <do_page_fault+0/4cf>
> Trace; c0107438 <error_code+34/3c>
> Trace; c01374ed <__free_pages_ok+27d/2a0>
> Trace; c01c1fe9 <vt_console_print+59/310>
> Trace; c011c53f <__call_console_drivers+5f/70>
> Trace; c012d797 <zap_pte_range+f7/120>
> Trace; c012574b <run_timer_list+10b/170>
> Trace; c012bfeb <zap_page_range+8b/f0>
> Trace; c012eed9 <exit_mmap+b9/160>
> Trace; c011a9a7 <mmput+47/a0>
> Trace; c011f88f <do_exit+8f/240>
> Trace; c01079df <die+7f/c0>
> Trace; c01182c4 <do_page_fault+2a4/4cf>
> Trace; c01eb4a8 <__ide_dma_begin+38/50>
> Trace; c01eb686 <__ide_dma_count+16/20>
> Trace; c01eb30e <__ide_dma_read+13e/150>
> Trace; c01eaf30 <dma_timer_expiry+0/e0>
> Trace; c01e6eed <do_rw_disk+1ed/6d0>
> Trace; c0118020 <do_page_fault+0/4cf>
> Trace; c0107438 <error_code+34/3c>
> Trace; c01374ed <__free_pages_ok+27d/2a0>
> Trace; c0141aee <try_to_free_buffers+8e/100>
> Trace; c013667f <shrink_cache+21f/310>
> Trace; c01368c3 <shrink_caches+63/a0>
> Trace; c0136936 <try_to_free_pages_zone+36/50>
> Trace; c01377d7 <balance_classzone+57/1f0>
> Trace; c0137a63 <__alloc_pages+f3/190>
> Trace; c012cf1c <do_anonymous_page+6c/120>
> Trace; c012d207 <handle_mm_fault+77/110>
> Trace; c0118158 <do_page_fault+138/4cf>
> Trace; c010d3ee <old_mmap+de/120>
> Trace; c0118020 <do_page_fault+0/4cf>
> Trace; c0107438 <error_code+34/3c>
>
> Code; c01374ed <__free_pages_ok+27d/2a0>
> 00000000 <_EIP>:
> Code; c01374ed <__free_pages_ok+27d/2a0> <=====
> 0: 89 58 04 mov %ebx,0x4(%eax) <=====
> Code; c01374f0 <__free_pages_ok+280/2a0>
> 3: 89 03 mov %eax,(%ebx)
> Code; c01374f2 <__free_pages_ok+282/2a0>
> 5: 89 53 04 mov %edx,0x4(%ebx)
> Code; c01374f5 <__free_pages_ok+285/2a0>
> 8: 89 59 5c mov %ebx,0x5c(%ecx)
> Code; c01374f8 <__free_pages_ok+288/2a0>
> b: 89 73 0c mov %esi,0xc(%ebx)
> Code; c01374fb <__free_pages_ok+28b/2a0>
> e: ff 41 68 incl 0x68(%ecx)
> Code; c01374fe <__free_pages_ok+28e/2a0>
> 11: eb bf jmp ffffffd2 <_EIP+0xffffffd2>
> Code; c0137500 <__free_pages_ok+290/2a0>
> 13: 0f 00 00 sldtl (%eax)
>
>
> 1 warning issued. Results may not be reliable.
>
> ---[end oops]---
>
> ---[start config]---
>
> CONFIG_X86=y
> CONFIG_UID16=y
> CONFIG_EXPERIMENTAL=y
> CONFIG_MODULES=y
> CONFIG_MODVERSIONS=y
> CONFIG_KMOD=y
> CONFIG_MPENTIUM4=y
> CONFIG_X86_WP_WORKS_OK=y
> CONFIG_X86_INVLPG=y
> CONFIG_X86_CMPXCHG=y
> CONFIG_X86_XADD=y
> CONFIG_X86_BSWAP=y
> CONFIG_X86_POPAD_OK=y
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_X86_L1_CACHE_SHIFT=7
> CONFIG_X86_HAS_TSC=y
> CONFIG_X86_GOOD_APIC=y
> CONFIG_X86_PGE=y
> CONFIG_X86_USE_PPRO_CHECKSUM=y
> CONFIG_X86_F00F_WORKS_OK=y
> CONFIG_X86_MCE=y
> CONFIG_CPU_FREQ=y
> CONFIG_X86_SPEEDSTEP=m
> CONFIG_I8K=y
> CONFIG_MICROCODE=y
> CONFIG_X86_MSR=y
> CONFIG_X86_CPUID=y
> CONFIG_NOHIGHMEM=y
> CONFIG_MTRR=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_NET=y
> CONFIG_PCI=y
> CONFIG_PCI_GOANY=y
> CONFIG_PCI_BIOS=y
> CONFIG_PCI_DIRECT=y
> CONFIG_ISA=y
> CONFIG_PCI_NAMES=y
> CONFIG_HOTPLUG=y
> CONFIG_PCMCIA=y
> CONFIG_CARDBUS=y
> CONFIG_I82092=y
> CONFIG_I82365=y
> CONFIG_SYSVIPC=y
> CONFIG_BSD_PROCESS_ACCT=y
> CONFIG_SYSCTL=y
> CONFIG_KCORE_ELF=y
> CONFIG_BINFMT_ELF=y
> CONFIG_BINFMT_MISC=m
> CONFIG_IKCONFIG=y
> CONFIG_PM=y
> CONFIG_APM=y
> CONFIG_APM_RTC_IS_GMT=y
> CONFIG_PARPORT=m
> CONFIG_PARPORT_PC=m
> CONFIG_PARPORT_PC_CML1=m
> CONFIG_PARPORT_PC_FIFO=y
> CONFIG_PNP=y
> CONFIG_PNPBIOS=y
> CONFIG_BLK_DEV_FD=y
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_BLK_STATS=y
> CONFIG_CRYPTO=y
> CONFIG_CIPHERS=y
> CONFIG_CIPHER_BLOWFISH=m
> CONFIG_DIGESTS=y
> CONFIG_DIGEST_MD5=y
> CONFIG_DIGEST_SHA1=y
> CONFIG_DIGEST_RIPEMD160=y
> CONFIG_DIGEST_SHA256=y
> CONFIG_DIGEST_SHA384=y
> CONFIG_DIGEST_SHA512=y
> CONFIG_CRYPTODEV=y
> CONFIG_CRYPTOLOOP=m
> CONFIG_CRYPTOLOOP_IV_HACK=y
> CONFIG_PACKET=y
> CONFIG_NETFILTER=y
> CONFIG_UNIX=m
> CONFIG_INET=y
> CONFIG_IP_MULTICAST=y
> CONFIG_IDE=y
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_BLK_DEV_IDECS=m
> CONFIG_BLK_DEV_IDECD=m
> CONFIG_BLK_DEV_IDEFLOPPY=m
> CONFIG_BLK_DEV_IDESCSI=m
> CONFIG_BLK_DEV_IDEPCI=y
> CONFIG_IDEPCI_SHARE_IRQ=y
> CONFIG_BLK_DEV_IDEDMA_PCI=y
> CONFIG_IDEDMA_PCI_AUTO=y
> CONFIG_BLK_DEV_IDEDMA=y
> CONFIG_BLK_DEV_ADMA=y
> CONFIG_BLK_DEV_PIIX=y
> CONFIG_IDEDMA_AUTO=y
> CONFIG_BLK_DEV_IDE_MODES=y
> CONFIG_SCSI=m
> CONFIG_BLK_DEV_SD=m
> CONFIG_SD_EXTRA_DEVS=40
> CONFIG_BLK_DEV_SR=m
> CONFIG_SR_EXTRA_DEVS=2
> CONFIG_CHR_DEV_SG=m
> CONFIG_SCSI_DEBUG_QUEUES=y
> CONFIG_SCSI_MULTI_LUN=y
> CONFIG_SCSI_CONSTANTS=y
> CONFIG_IEEE1394=m
> CONFIG_IEEE1394_OHCI1394=m
> CONFIG_IEEE1394_SBP2=m
> CONFIG_IEEE1394_RAWIO=m
> CONFIG_I2O=m
> CONFIG_I2O_PCI=m
> CONFIG_NETDEVICES=y
> CONFIG_DUMMY=m
> CONFIG_ETHERTAP=m
> CONFIG_NET_ETHERNET=y
> CONFIG_NET_VENDOR_3COM=y
> CONFIG_VORTEX=m
> CONFIG_PPP=m
> CONFIG_PPP_ASYNC=m
> CONFIG_PPP_SYNC_TTY=m
> CONFIG_SLIP=m
> CONFIG_SLIP_COMPRESSED=y
> CONFIG_SLIP_SMART=y
> CONFIG_NET_RADIO=y
> CONFIG_HERMES=m
> CONFIG_PCMCIA_HERMES=m
> CONFIG_NET_WIRELESS=y
> CONFIG_NET_PCMCIA=y
> CONFIG_PCMCIA_3C589=m
> CONFIG_PCMCIA_3C574=m
> CONFIG_IRDA=m
> CONFIG_IRCOMM=m
> CONFIG_IRTTY_SIR=m
> CONFIG_IRPORT_SIR=m
> CONFIG_INPUT=y
> CONFIG_INPUT_KEYBDEV=y
> CONFIG_INPUT_MOUSEDEV=y
> CONFIG_INPUT_MOUSEDEV_SCREEN_X=1600
> CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1200
> CONFIG_INPUT_EVDEV=y
> CONFIG_VT=y
> CONFIG_VT_CONSOLE=y
> CONFIG_SERIAL=y
> CONFIG_SERIAL_CONSOLE=y
> CONFIG_UNIX98_PTYS=y
> CONFIG_UNIX98_PTY_COUNT=256
> CONFIG_BUSMOUSE=y
> CONFIG_MOUSE=y
> CONFIG_PSMOUSE=y
> CONFIG_INPUT_SERIO=y
> CONFIG_INTEL_RNG=m
> CONFIG_NVRAM=m
> CONFIG_RTC=y
> CONFIG_DTLK=m
> CONFIG_AGP=m
> CONFIG_AGP_INTEL=y
> CONFIG_DRM=y
> CONFIG_DRM_NEW=y
> CONFIG_DRM_RADEON=m
> CONFIG_PCMCIA_SERIAL_CS=y
> CONFIG_PCMCIA_CHRDEV=y
> CONFIG_AUTOFS4_FS=y
> CONFIG_REISERFS_FS=m
> CONFIG_REISERFS_PROC_INFO=y
> CONFIG_EXT3_FS=y
> CONFIG_JBD=y
> CONFIG_FAT_FS=m
> CONFIG_MSDOS_FS=m
> CONFIG_VFAT_FS=m
> CONFIG_RAMFS=y
> CONFIG_ISO9660_FS=y
> CONFIG_JOLIET=y
> CONFIG_JFS_FS=y
> CONFIG_JFS_STATISTICS=y
> CONFIG_MINIX_FS=m
> CONFIG_NTFS_FS=m
> CONFIG_PROC_FS=y
> CONFIG_DEVFS_FS=y
> CONFIG_DEVFS_MOUNT=y
> CONFIG_DEVPTS_FS=y
> CONFIG_EXT2_FS=y
> CONFIG_SYSV_FS=m
> CONFIG_UDF_FS=m
> CONFIG_CODA_FS=m
> CONFIG_NFS_FS=m
> CONFIG_NFS_V3=y
> CONFIG_NFSD=m
> CONFIG_NFSD_V3=y
> CONFIG_NFSD_TCP=y
> CONFIG_SUNRPC=m
> CONFIG_LOCKD=m
> CONFIG_LOCKD_V4=y
> CONFIG_SMB_FS=m
> CONFIG_MSDOS_PARTITION=y
> CONFIG_SMB_NLS=y
> CONFIG_NLS=y
> CONFIG_NLS_DEFAULT="cp437"
> CONFIG_NLS_CODEPAGE_437=m
> CONFIG_NLS_CODEPAGE_850=m
> CONFIG_NLS_ISO8859_1=m
> CONFIG_VGA_CONSOLE=y
> CONFIG_VIDEO_SELECT=y
> CONFIG_MDA_CONSOLE=m
> CONFIG_FB=y
> CONFIG_DUMMY_CONSOLE=y
> CONFIG_VIDEO_SELECT=y
> CONFIG_FB_RADEON=m
> CONFIG_FB_VIRTUAL=m
> CONFIG_FBCON_MFB=m
> CONFIG_FBCON_CFB2=m
> CONFIG_FBCON_CFB4=m
> CONFIG_FBCON_CFB8=m
> CONFIG_FBCON_CFB16=m
> CONFIG_FBCON_CFB24=m
> CONFIG_FBCON_CFB32=m
> CONFIG_FBCON_MAC=m
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> CONFIG_SOUND=y
> CONFIG_SOUND_ICH=y
> CONFIG_USB=m
> CONFIG_USB_DEVICEFS=y
> CONFIG_USB_UHCI=m
> CONFIG_USB_UHCI_ALT=m
> CONFIG_USB_AUDIO=m
> CONFIG_USB_SERIAL=m
> CONFIG_USB_SERIAL_PL2303=m
> CONFIG_BLUEZ=y
> CONFIG_BLUEZ_L2CAP=m
> CONFIG_BLUEZ_RFCOMM=m
> CONFIG_BLUEZ_RFCOMM_TTY=y
> CONFIG_BLUEZ_BNEP=m
> CONFIG_BLUEZ_HCIUSB=m
> CONFIG_DEBUG_KERNEL=y
> CONFIG_MAGIC_SYSRQ=y
> CONFIG_PANIC_MORSE=y
> CONFIG_ZLIB_INFLATE=m
> CONFIG_ZLIB_DEFLATE=m
>
> --[end config]---
>
> --
> Magnus Månsson
--
ganja
^ permalink raw reply
* Re: PrintScreen
From: Stas Sergeev @ 2003-01-10 22:32 UTC (permalink / raw)
To: linux-msdos
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Hello.
Jan Willem Stumpel wrote:
> Pressing the PrtSc key in dosemu (1.1.4.0) prints the (text)
> screen, which is a nice surprise.
Why? I can assure you you'll have
the same also with 1.1.3.
What did you expect anyway? :)
> Specifying a different printer in dosemu.conf works for "normal"
> DOS printing (printing from applications and COPYing to LPT1), but
> not for PrtSc: the printer always seems to be "lp". Can anyone
> confirm this? Is there a fix?
Maybe the attached patch can help?
[-- Attachment #2: pr0.diff --]
[-- Type: text/plain, Size: 764 bytes --]
--- src/base/async/int.c Thu Jan 9 19:02:03 2003
+++ src/base/async/int.c Sat Jan 11 01:23:17 2003
@@ -1471,15 +1471,15 @@
int x_pos, y_pos;
ushort *base=SCREEN_ADR(READ_BYTE(BIOS_CURRENT_SCREEN_PAGE));
g_printf("PrintScreen: base=%p, lines=%i columns=%i\n", base, li, co);
- printer_open(1);
+ printer_open(0);
for (y_pos=0; y_pos < li; y_pos++) {
for (x_pos=0; x_pos < co; x_pos++)
- printer_write(1, READ_BYTE(base + y_pos*co + x_pos));
- printer_write(1, 0x0d);
- printer_write(1, 0x0a);
+ printer_write(0, READ_BYTE(base + y_pos*co + x_pos));
+ printer_write(0, 0x0d);
+ printer_write(0, 0x0a);
}
- printer_flush(1);
- printer_close(1);
+ printer_flush(0);
+ printer_close(0);
}
static void int05(u_char i)
^ permalink raw reply
* Re: set_user_nice() not defined on 2.4.21+
From: Joakim Tjernlund @ 2003-01-10 23:04 UTC (permalink / raw)
To: Xiaogeng (Shawn) Jin, linux-mtd
In-Reply-To: <3E1F0F47.1080606@redswitch.com>
Hi
I had the impression that set_user_nice() would be in 2.4.21 when I added set_user_nice() to
mtd/compatmac.h. I can change it to KERNEL_VERSION(2,5,0) or someone can
submit a patch to Marcelo.
Jocke
> Hi,
>
> When compiled JFFS2 with kernel 2.4.21-pre3, the linker complains that
> the reference to set_user_nice() in function
> jffs2_garbage_collect_thread() hasn't been defined. I traced the code
> down to <linux/mtd/compatmac.h> and found that set_user_nice() is not
> defined if linux verion is equal or greater than 2.4.21. See the code
> below. Why? Does it mean that 2.4.21+ has already such a function
> defined somewhere else or that 2.4.21+ doesn't need it? Actually I
> searched 2.4.21-pre3 code and found no set_user_nice() defined except in
> <linux/mtd/compatmac.h>. I guess it's possibly a bug.
>
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2,4,0) /* Is this right? */
> #define set_user_nice(tsk, n) do { (tsk)->priority = 20-(n); } while(0)
> #elif LINUX_VERSION_CODE < KERNEL_VERSION(2,4,21) &&
> !defined(RED_HAT_LINUX_KERNEL)
> #define set_user_nice(tsk, n) do { (tsk)->nice = n; } while(0)
> #endif
>
> --
> Shawn Jin
> RedSwitch Inc.
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply
* Re: buddy algorithm
From: Dan Olson @ 2003-01-10 22:36 UTC (permalink / raw)
To: Martin Herrman; +Cc: linux-8086
In-Reply-To: <Pine.LNX.4.44.0301102301320.16753-100000@tuxserver.dyndns.org>
I was under the impression that ELKS assigns 64k to each process, so a
single 16 bit data pointer can be used and the different segments can be
simply divided so that each process owns one. There are others on the
list with much more knowledge about this, though, so I'll wait for one of
them to clear things up.
Dan
On Fri, 10 Jan 2003, Martin Herrman wrote:
> Hi all,
>
> first I want to give a short introduction about myself. I'm a 22 year old
> student computer sience at Eindhoven University of Technology, which is
> located in the south of The Netherlands, Europe. I'm using Linux as
> desktop and server operating system since about 3 years now. I like
> motorcycles, beer and most important: I like my girlfriend :-) More about
> me at http://tuxserver.dyndns.org
>
> Now let's get to the point why I subscribed to this mailinglist: I'm
> taking a course 'The Linux Kernel' at the moment and together with a
> friend I have to find a nice assignment with which we will (probably :-)
> pass the course. We heard about the 'buddy algorithm', which assigns
> memory to processes. Now the question is: how does the ELKS project deal
> with it? Does it use the same algorithm as the official linux kernel does?
> Is there any interest in a different version of the algorithm which uses
> fibonacci to assign memory parts to processes if they ask for it? The
> fibonacci way (1,1,2,3,5,8,13, etc.) will cost some speed (compared to
> 1,2,4,8,16, etc.), but will yield some better utilisation of available
> memory.
>
> I'm really looking forward to your replies!
>
> Martin
>
> --
> Bezoek http://tuxserver.dyndns.org :
> Linux Gebruikers Handleiding, GS500, SV650
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply
* IPSec
From: latten @ 2003-01-10 22:45 UTC (permalink / raw)
To: linux-kernel
I am configuring IPSec and was wondering are there
any plans to add AES to the crypto algorithms IPSec uses?
Joy
^ permalink raw reply
* Re: buddy algorithm
From: Harry Kalogirou @ 2003-01-10 22:37 UTC (permalink / raw)
To: Dan Olson; +Cc: Martin Herrman, Linux-8086
In-Reply-To: <20030110143434.G27221-100000@agora.rdrop.com>
> I was under the impression that ELKS assigns 64k to each process, so a
> single 16 bit data pointer can be used and the different segments can be
> simply divided so that each process owns one. There are others on the
> list with much more knowledge about this, though, so I'll wait for one of
> them to clear things up.
>
> Dan
ELKS assigns to the process an initial amount of memory for the stack.
From there that memory is grown as the libc instructs with sys_brk()
calls.
Harry
^ permalink raw reply
* Re: 2.5.55 - loading bttv gives Unknown symbol videobuf_iol
From: Petr Vandrovec @ 2003-01-10 22:46 UTC (permalink / raw)
To: Kees Bakker; +Cc: linux-kernel, kraxel
On 10 Jan 03 at 23:28, Kees Bakker wrote:
> With 2.5.55 I get the following error in syslog when I load bttv:
>
> bttv: Unknown symbol videobuf_iolock
See my few minutes old patch to Rusty's depmod. It does not handle
GPL symbols, and as Gerd uses them...
Petr Vandrovec
vandrove@vc.cvut.cz
^ permalink raw reply
* Re: Linus BK tree crashes with PANIC: INIT: segmentation violation
From: Linus Torvalds @ 2003-01-10 22:52 UTC (permalink / raw)
To: Derek Atkins; +Cc: Kernel Mailing List, Larry McVoy
In-Reply-To: <sjm7kdc63ul.fsf@kikki.mit.edu>
[ Larry added to cc in case he has some magic ways to make BK more easily
do the "split the set in half" problem for doing binary searches on BK
trees ]
On 10 Jan 2003, Derek Atkins wrote:
>
> Linus Torvalds <torvalds@transmeta.com> writes:
>
> > Hmm.. Can you try to pinpoint more exactly the change that caused it?
>
> Well, which change-point do you want? Do you want the change-point
> from the string-of-oppses to the "PANIC: INIT: ..."? Or the
> change-point from a working kernel to the string-of-oopses? I already
> computed the latter point. I have not computed the former.
Well, both are interesting. Nothing says that the problems have to be
related, but it's certainly not inconceivable, and as such both points end
up being interesting.
> 1) PANIC: INIT: ...
> 2) String of Oopses
> 3) Working Tree.
>
> The changeover from 2-3 is approximately December 30 (see my previous
> post).
I was hoping for a exact changset, your post didn't seem to be 100% sure.
Anyway, the one you pinpointed ("Make x86 platform choice strings more
easily selectable" top-of-tree is working), is followed by a patch by
Christop Hellwig ("Missed one 'try_inc_mod_count'") which almost certainly
isn't the cause of your trouble. So I'd like you to go forward a bit.
For example, if you know that your (2) happens before 2.5.54, then you can
do
bk clone -ql -rv2.5.54 linux-BK test-tree
bk changes
.. look for the one you already know is ok: it's called
"1.911.13.50" in the full 2.5.54 tree ..
Now you can either just visibly look at what got merged afterwards:
bk revtool
.. look for it in the tree - now you see what followed it
and merge points are interesting places to look at.
Then you can figure out some interesting places to look for (depends on
your hardware - if you have a aic7xxx controller, one obvious interesting
place to look at is the merge of the aic7xx changes by justin gibbs).
If you care about full BK magic, you can also see a full list of changes
between two versions by doing
bk set -n -d -rXXXX -rYYYY | bk -R prs -h -d':I: <:P:@:HOST:>\n$each(:C:){\t(:C:)\n}\n' -
to see every changeset that happened between XXXX and YYYY.
(In case you care: the "bk set" will spit out all keys that are the "set
difference" between what is in XXXX and YYYY, and then the "bk prs" part
will print out those keys in a readable manner according to the
description string given by "-d").
So with XXXX being 1.911.13.50 and YYYY being top-of-tree (you can use '+'
for this), you get:
1.858.2.3 <jsimmons@maxwell.earthlink.net>
Added in Radeon PCI ids into pci_ids.h from radeon.h. IGA fbdev uses C99 now.
1.865.2.1 <jsimmons@maxwell.earthlink.net>
Merge maxwell.earthlink.net:/usr/src/linus-2.5
into maxwell.earthlink.net:/usr/src/fbdev-2.5
1.865.2.2 <jsimmons@infradead.org>
Fixes from the PPC guys. Lots of small fixes.
....
and you can look for things that look interesting and decide to try a
kernel with that instead..
I don't know what the right way to make bk show a "halfway point" between
two releases is, since a BK tree is not just a linear collection. The
above will give all points between two releases, but won't help you much
decide _which_ point is the best one to start with (unless the description
makes you suspicious).
> Question: how do I determine the "global" id for a particular
> revision? My 1.1004 is certainly not the same as yours (which is why
> I gave the changelog and timestamp information).
The "global ID" is the key of a changeset, and you can get it with ':KEY:'
in the bk prs description (ie in the above command, you can add a :KEY:\n
to the beginning of the string that '-d' specifies, and you'll see
something like
jsimmons@maxwell.earthlink.net|ChangeSet|20021210013840|58905
1.858.2.3 <jsimmons@maxwell.earthlink.net>
Added in Radeon PCI ids into pci_ids.h from radeon.h. IGA fbdev uses C99 now.
jsimmons@maxwell.earthlink.net|ChangeSet|20021210063345|36692
1.865.2.1 <jsimmons@maxwell.earthlink.net>
Merge maxwell.earthlink.net:/usr/src/linus-2.5
into maxwell.earthlink.net:/usr/src/fbdev-2.5
jsimmons@infradead.org|ChangeSet|20021211155159|31301
1.865.2.2 <jsimmons@infradead.org>
Fixes from the PPC guys. Lots of small fixes.
...
instead, where the "jsimmons@infradead.org|ChangeSet|20021211155159|31301"
things are the global keys that are stable across merges. They are kind of
awkward to use for day-to-day stuff, though, for obvious reasons.
Linus
^ permalink raw reply
* Re: Interrupt Routing
From: Stephen L Johnson @ 2003-01-10 22:46 UTC (permalink / raw)
To: Dominik Brodowski; +Cc: ACPI Dev Mailing List
In-Reply-To: <20030110213137.GA10841-JhLEnvuH02M@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
On Fri, 2003-01-10 at 15:31, Dominik Brodowski wrote:
> Hi Stephen,
>
> Could you please send me a dmesg? CONFIG_ACPI_DEBUG should be enabled :-)
>
> Dominik
>
Here it is.
--
Stephen L Johnson <sjohnson-WpdXj7kV/NVg9hUCZPvPmw@public.gmane.org>
[-- Attachment #2: dmesg.out.gz --]
[-- Type: application/x-gzip, Size: 5106 bytes --]
^ permalink raw reply
* Re: [PATCH] RPC match and conntrack modules v2.1
From: Ian Latter @ 2003-01-10 22:47 UTC (permalink / raw)
To: Harald Welte; +Cc: netfilter-devel
Hi Harald,
> This is cool stuff. Thanks a lot. The kind of contribution I really
> like :)
Cool, thanks .. :-) I think there will be a lot of embedded firewall
manufacturers that will enjoy this one ...
> Sorry, I didn't understand the part about the NAT module. Are you
> saying that NAT support is not functional right now?
That's correct - there was no NAT built into record-rpc, not even in an
old API. I wanted to make the module set complete by writing the
corresponding NAT module(s) but I didn't get time. I might be re-inspired
later in January if no one else picks it up -- the code should be almost
identical to the RSH work module that I wrote, because the connection
handling is quite similar ..... actually ... maybe it doesn't need a nat helper;
the connections are all initiated from the client to the server, and the
internal protocols aren't carrying payloads that need to be rewritten ... so
as long as the nat stuff handles "related" streams sanely, then its
probably ok ...
> See attached patch. Mostly CodingStyle updates (you seem to like 8 spaces
> instead of tab), but also a minor fix:
Cool ... could you resent it as a "zip" attachment ... my mail software
decodes text attachments which will make all the tabs in your patch
spaces again ...
> - when unloading, only unregister up to ports_n_c ports
ok
> btw: I'd really love to see the large chunk of code in the switch
> statement of the match() function in ipt_rpc.c be split up in seperate
> functions (thus reducing indentation and improving readability).
possibly could be ... the gumby way might be to do udp and tcp
functions ... but a better way might be to pull out the rpc payload
stuff .... I can take a look at that.
> I don't know, but I think esp. in cases where you have lots of rpc
> activity (NFS?, I'm not an RPC expert) it might be wise to use a slab
> cache for the 'struct request_p' list items.
I have not done that before, is there an example some place in the
existing modules?
> Please integrate my patch [and maybe consider my suggestions, that's of
> course up to you], test it and resubmit it.
hopefully be done by the end of the weekend/early next week.
> Thanks!
Thanks for taking a look at it, and providing feed back ...
> > Regards,
> > Ian Latter
>
> --
> - Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/
>
===========================================================================
=
> "If this were a dictatorship, it'd be a heck of a lot easier, just so long
> as I'm the dictator." -- George W. Bush Dec 18, 2000
--
Ian Latter
Internet and Networking Security Officer
Macquarie University
^ permalink raw reply
* Re: Kernel Oops with HIMEM+VM in 2.4.19,20
From: William Lee Irwin III @ 2003-01-10 22:58 UTC (permalink / raw)
To: Anthony Lau; +Cc: linux-kernel
In-Reply-To: <20030110180953.GB1292@kimagure>
On Fri, Jan 10, 2003 at 02:48:27AM -0800, William Lee Irwin III wrote:
>> Looks like someone e.g. invalidate_inode_pages(), truncate_inode_pages(),
>> etc. etc., left pages hanging around. Borderline VM/vfs stuff. Or swap
>> code mangled something important. This oops either has buttloads of
>> stack noise or some other issue corrupting it. Can you find the first
>> oops? If this is not the first oops, then it's probably not useful.
On Fri, Jan 10, 2003 at 10:09:53AM -0800, Anthony Lau wrote:
> That was the first Oops message logged. System instability starts before
> any oop messages begin to show up in the standard syslogd logs. Something
> does appear in ksymoops. I have setup "klogd -x" and await the next log.
Okay, what filesystem(s) are you using (this usually has something to do
with a filesystem)?
Also, are you applying any patches to 2.4.19/2.4.20?
Thanks,
Bill
^ permalink raw reply
* Re: reiserfsck --rebuild-tree aborted
From: John Fettig @ 2003-01-10 22:58 UTC (permalink / raw)
To: Vitaly Fertman; +Cc: John Fettig, reiserfs-list
In-Reply-To: <200301101640.13350.vitaly@namesys.com>
* Vitaly Fertman <vitaly@namesys.com>:
> > build_the_tree: Nothing but leaves are expected. Block 8532-??22683
> > build_the_tree: Nothing but leaves are expected. Block 8580-??22660
> > pass1.c 405 pass1_correct_leaf
> > pass1_correct_leaf: block 8581, item 0, pointer 22: The wrong pointer
> > (944715855) in the file [7471218 636]. Must be fixed on pass0.
> > Aborted
>
> All this looks like an fsck bug, but could be some kind of hardware
> problem also. I would like to have a look at the metadata of your
> partition. Could you run debugreiserfs -p /dev/xxx | bzip2 -c > xxx.bz2
> and make it available for downloading.
You can download the output from debugreiserfs from:
http://salty.ncsa.uiuc.edu/debugout.bz2
Please let me know what you find.
John
^ permalink raw reply
* Re: Linus BK tree crashes with PANIC: INIT: segmentation violation
From: Tomas Szepe @ 2003-01-10 23:07 UTC (permalink / raw)
To: Derek Atkins; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.44.0301101424590.1193-100000@penguin.transmeta.com>
> [torvalds@transmeta.com]
>
> I was hoping for a exact changset, your post didn't seem to be 100% sure.
>
> Anyway, the one you pinpointed ("Make x86 platform choice strings more
> easily selectable" top-of-tree is working), is followed by a patch by
> Christop Hellwig ("Missed one 'try_inc_mod_count'") which almost certainly
> isn't the cause of your trouble. So I'd like you to go forward a bit.
>
> For example, if you know that your (2) happens before 2.5.54, then you can
> do
>
> bk clone -ql -rv2.5.54 linux-BK test-tree
> bk changes
> .. look for the one you already know is ok: it's called
> "1.911.13.50" in the full 2.5.54 tree ..
Or you can just do everything "by hand" using these two together:
http://linux.bkbits.net:8080/linux-2.5
ftp://ftp.nl.linux.org/pub/linux/bk2patch/v2.5
--
Tomas Szepe <szepe@pinerecords.com>
^ permalink raw reply
* Re: [LARTC] Question on TC filter
From: Stef Coene @ 2003-01-10 23:00 UTC (permalink / raw)
To: lartc
In-Reply-To: <marc-lartc-104222313403706@msgid-missing>
On Friday 10 January 2003 19:24, Cheng Kwok Wing, William wrote:
> Hi,
>
> I want work out a GUI interface for htb and now here
> comes to the part about adding and removing classes
> and filters.
Like I do :à
http://home.docum.org/qos/
> Suppose I want to remove the class 1:20. What should I
> do? I need to first remove the filters with flowid
> 1:20, but how can I remove it independently???
> If I run "tc filter del $DEV parent 1:0......", then
> all filters will be removed. Any suggestion on how to
> solve this problem or a better way to organise the
> classes or filters??
I create all rules, generate the tc script, execute the script. So no
changing of running classes and filters. I don't think you can delete 1
filter like you want.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* Re: [patch 2.5] 2-pass PCI probing, generic part
From: Grant Grundler @ 2003-01-10 23:07 UTC (permalink / raw)
To: Ivan Kokshaysky
Cc: Eric W. Biederman, Linus Torvalds, Benjamin Herrenschmidt,
Alan Cox, Paul Mackerras, davidm, Linux Kernel Mailing List, greg
In-Reply-To: <20030111004239.A757@localhost.park.msu.ru>
On Sat, Jan 11, 2003 at 12:42:39AM +0300, Ivan Kokshaysky wrote:
> Eh? In general case, to make room for newly added device, you have
> to shutdown the whole PCI bus starting from level 0, reassign _all_
> BARs and bridge windows and then restart...
That might be true for x86. I'm pretty sure it's not true for the
parisc machines I'm familiar with. One "window" register is set to
a "default" at boot time by the firmware and behaves as you describe above.
But a *second* window register in the PCI controller was intended
for dynamic MMIO assignment in case the first one was too small.
The trick is to find MMIO space in the region already being routed
by the IOC (parent of the PCI controller). My point is a second
somewhat larger MMIO region can be routed to a few additional PCI
controllers given sufficient MMIO space.
Again, I believe HP's ia64 HW has leveraged this design but I haven't
checked specs. And methods to reprogram the window registers might
require firmware to do it instead of the OS.
> The "hotplug resource reservation" is the only viable approach, it has
> been discussed numerous times.
ok - I'll to look for those when the time comes.
> I believe 1GB is a theoretical maximum for a 32-bit BAR.
2GB. But my argument is enough "bigger" BARs may not work either.
grant
^ permalink raw reply
* Re: [LARTC] howto skip some traffic in TC
From: Stef Coene @ 2003-01-10 23:01 UTC (permalink / raw)
To: lartc
In-Reply-To: <marc-lartc-104221550023840@msgid-missing>
On Friday 10 January 2003 17:16, nedco@unacs.bg wrote:
> Hi
> i have one simple question
> I use HTB and i like to shape some traffic but
> i have game servers CS and diablo that generate
> to much traffic that must be with lo latency
>
> So hire is my question:
> Is there possibility traffic generated from and to game servers
> go transparently without going to any tc ( qdisc htb class )
Yes. Htb has a :0 class that sends at link speed.
If you have a default class, it will catch all not-matched traffic. So if all
your filters are failing, the packets still ends up in a class.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* problem with FORWARD chain
From: Reed Wiedower @ 2003-01-10 23:11 UTC (permalink / raw)
To: 'netfilter@lists.netfilter.org'
I'm setting up a simple bridge firewall, and I've managed to get the
bridging working properly. However, every time I attempt to create a
firewall rule to prevent packets from traversing the FORWARD chain, I notice
that, at least according to "iptables -L -vX", no packets are going across
that particular chain. Any idea why this might be happening? I can implement
rules on both the INPUT and OUTPUT chains and they work as expected, but for
some reason nothing will display on the FORWARD chain.
The bridging folks seem to think that it's an issue with iptables, not with
the bridging code. Thanks in advance if anyone has seen this or knows how to
deal with it.
eol,
Reed
reed wiedower
reed.wiedower@peyser.com
peyser.com
202.638.3730x115
^ permalink raw reply
* Re: Kernel Oops with HIMEM+VM in 2.4.19,20
From: Anthony Lau @ 2003-01-10 23:29 UTC (permalink / raw)
To: William Lee Irwin III, linux-kernel
In-Reply-To: <20030110225835.GC1147@holomorphy.com>
On Fri, Jan 10, 2003 at 02:58:35PM -0800, William Lee Irwin III wrote:
> On Fri, Jan 10, 2003 at 10:09:53AM -0800, Anthony Lau wrote:
> > That was the first Oops message logged. System instability starts before
> > any oop messages begin to show up in the standard syslogd logs. Something
> > does appear in ksymoops. I have setup "klogd -x" and await the next log.
>
> Okay, what filesystem(s) are you using (this usually has something to do
> with a filesystem)?
The only filesystem I am using on the hardrive is ext3. The swap
partition was made as new style. I have tried reinitializing the swap,
and after rebooting, the symptoms reappeared.
> Also, are you applying any patches to 2.4.19/2.4.20?
2.4.19: I applied only the HTB2 patch for QoS.
2.4.20: no patches
The .config file I used for 2.4.19:
#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor type and features
#
# 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_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_MCE=y
# 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
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_BIGPHYS_AREA is not set
# CONFIG_SMP is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
#
# General setup
#
CONFIG_NET=y
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_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=m
CONFIG_CARDBUS=y
# CONFIG_TCIC is not set
# CONFIG_I82092 is not set
# CONFIG_I82365 is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
# CONFIG_HOTPLUG_PCI_IBM is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PM=y
# CONFIG_ACPI is not set
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=y
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# 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_CISS_SCSI_TAPE is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# 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_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_COMPAT_IPCHAINS=m
CONFIG_IP_NF_NAT_NEEDED=y
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
CONFIG_IPV6=m
#
# IPv6: Netfilter Configuration
#
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_LIMIT=m
CONFIG_IP6_NF_MATCH_MAC=m
CONFIG_IP6_NF_MATCH_MULTIPORT=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_MARK=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_MARK=m
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
#
# Appletalk devices
#
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC 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=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_CSZ=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_POLICE=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
# CONFIG_PHONE_IXJ_PCMCIA is not set
#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# 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=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_IDEDMA_TIMEOUT is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CMD680 is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_PIIX_TUNING is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_SVWKS 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=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_BLK_DEV_ATARAID=m
CONFIG_BLK_DEV_ATARAID_PDC=m
CONFIG_BLK_DEV_ATARAID_HPT=m
#
# SCSI support
#
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
# 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_SR_EXTRA_DEVS=2
# CONFIG_CHR_DEV_SCH is not set
CONFIG_CHR_DEV_SG=m
CONFIG_SCSI_DEBUG_QUEUES=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID 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_AHA1740=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_PROBE_EISA_VL=y
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
CONFIG_SCSI_AIC7XXX_OLD=m
# CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT is not set
CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE=8
# CONFIG_AIC7XXX_OLD_PROC_STATS is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID 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_DMA 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_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_NCR53C8XX is not set
CONFIG_SCSI_SYM53C8XX=m
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=4
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_PQS_PDS is not set
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT 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_SEAGATE is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
CONFIG_SCSI_DC390T=m
# CONFIG_SCSI_DC390T_NOGENSUPP is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_DEBUG is not set
#
# PCMCIA SCSI adapter support
#
# CONFIG_SCSI_PCMCIA is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set
#
# Network device support
#
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
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE 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
# 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_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
CONFIG_TULIP=m
# CONFIG_TC35815 is not set
CONFIG_TULIP_MWI=y
CONFIG_TULIP_MMIO=y
# CONFIG_DE4X5 is not set
# CONFIG_DM9102 is not set
CONFIG_EEPRO100=m
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
CONFIG_NATSEMI=m
CONFIG_NATSEMI_CABLE_MAGIC=y
CONFIG_NE2K_PCI=m
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
CONFIG_8139CP=m
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
CONFIG_8139_NEW_RX_RESET=y
# 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_VIA_RHINE_MMIO is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_DL2K is not set
# CONFIG_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# 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=m
# CONFIG_PCMCIA_AXNET is not set
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
# CONFIG_ARCNET_COM20020_CS is not set
# CONFIG_PCMCIA_IBMTR is not set
# CONFIG_PCMCIA_XIRCOM is not set
# CONFIG_PCMCIA_XIRTULIP is not set
CONFIG_NET_PCMCIA_RADIO=y
CONFIG_PCMCIA_RAYCS=m
# CONFIG_PCMCIA_NETWAVE is not set
# CONFIG_PCMCIA_WAVELAN is not set
# CONFIG_AIRONET4500_CS is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Input core support
#
CONFIG_INPUT=y
CONFIG_INPUT_KEYBDEV=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
# CONFIG_I2C is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set
# CONFIG_MK712_MOUSE is not set
#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set
# CONFIG_INPUT_NS558 is not set
# CONFIG_INPUT_LIGHTNING is not set
# CONFIG_INPUT_PCIGAME is not set
# CONFIG_INPUT_CS461X is not set
# CONFIG_INPUT_EMU10K1 is not set
# CONFIG_INPUT_SERIO is not set
# CONFIG_INPUT_SERPORT is not set
# CONFIG_INPUT_ANALOG is not set
# CONFIG_INPUT_A3D is not set
# CONFIG_INPUT_ADI is not set
# CONFIG_INPUT_COBRA is not set
# CONFIG_INPUT_GF2K is not set
# CONFIG_INPUT_GRIP is not set
# CONFIG_INPUT_INTERACT is not set
# CONFIG_INPUT_TMDC is not set
# CONFIG_INPUT_SIDEWINDER is not set
# CONFIG_INPUT_IFORCE_USB is not set
# CONFIG_INPUT_IFORCE_232 is not set
# CONFIG_INPUT_WARRIOR is not set
# CONFIG_INPUT_MAGELLAN is not set
# CONFIG_INPUT_SPACEORB is not set
# CONFIG_INPUT_SPACEBALL is not set
# CONFIG_INPUT_STINGER is not set
# CONFIG_INPUT_DB9 is not set
# CONFIG_INPUT_GAMECON is not set
# CONFIG_INPUT_TURBOGRAFX is not set
# CONFIG_QIC02_TAPE is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_AMD_RNG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# 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_INTEL=y
CONFIG_AGP_I810=y
CONFIG_AGP_VIA=y
CONFIG_AGP_AMD=y
CONFIG_AGP_SIS=y
CONFIG_AGP_ALI=y
CONFIG_AGP_SWORKS=y
CONFIG_DRM=y
# CONFIG_DRM_OLD is not set
CONFIG_DRM_NEW=y
# CONFIG_DRM_TDFX is not set
CONFIG_DRM_R128=y
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
#
# PCMCIA character devices
#
# CONFIG_PCMCIA_SERIAL_CS is not set
# CONFIG_MWAVE is not set
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
#
# Video For Linux
#
CONFIG_VIDEO_PROC_FS=y
# CONFIG_I2C_PARPORT is not set
CONFIG_VIDEO_PMS=m
CONFIG_VIDEO_CPIA=m
# CONFIG_VIDEO_CPIA_PP is not set
CONFIG_VIDEO_CPIA_USB=m
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
CONFIG_VIDEO_STRADIS=m
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_ZORAN_BUZ is not set
# CONFIG_VIDEO_ZORAN_DC10 is not set
# CONFIG_VIDEO_ZORAN_LML33 is not set
# CONFIG_VIDEO_ZR36120 is not set
# CONFIG_VIDEO_MEYE is not set
#
# Radio Adapters
#
CONFIG_RADIO_CADET=m
CONFIG_RADIO_RTRACK=m
CONFIG_RADIO_RTRACK2=m
CONFIG_RADIO_AZTECH=m
CONFIG_RADIO_GEMTEK=m
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
# CONFIG_RADIO_MIROPCM20 is not set
# CONFIG_RADIO_MIROPCM20_RDS is not set
CONFIG_RADIO_SF16FMI=m
CONFIG_RADIO_TERRATEC=m
CONFIG_RADIO_TRUST=m
CONFIG_RADIO_TYPHOON=m
CONFIG_RADIO_TYPHOON_PROC_FS=y
CONFIG_RADIO_ZOLTRIX=m
#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=y
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
CONFIG_NTFS_FS=y
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
CONFIG_UDF_FS=y
# CONFIG_UDF_RW is not set
CONFIG_UFS_FS=y
# CONFIG_UFS_FS_WRITE is not set
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
CONFIG_ZISOFS_FS=y
CONFIG_ZLIB_FS_INFLATE=y
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
CONFIG_SMB_NLS=y
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# 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=y
CONFIG_NLS_CODEPAGE_950=y
CONFIG_NLS_CODEPAGE_932=y
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# 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
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set
#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FB_RIVA is not set
# CONFIG_FB_CLGEN is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_RADEON is not set
CONFIG_FB_ATY128=y
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC 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
# CONFIG_FBCON_ADVANCED is not set
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
# CONFIG_FBCON_FONTWIDTH8_ONLY is not set
# CONFIG_FBCON_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Sound
#
CONFIG_SOUND=m
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_MIDI_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
CONFIG_SOUND_ES1371=m
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
CONFIG_SOUND_ICH=m
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_VIA82CXXX=m
CONFIG_MIDI_VIA82CXXX=y
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_TRACEINIT is not set
# CONFIG_SOUND_DMAP is not set
CONFIG_SOUND_AD1816=m
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_ADLIB is not set
# CONFIG_SOUND_ACI_MIXER is not set
# CONFIG_SOUND_CS4232 is not set
# CONFIG_SOUND_SSCAPE is not set
# CONFIG_SOUND_GUS is not set
# CONFIG_SOUND_VMIDI is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_NM256 is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_PAS is not set
# CONFIG_PAS_JOYSTICK is not set
# CONFIG_SOUND_PSS is not set
# CONFIG_SOUND_SB is not set
# CONFIG_SOUND_AWE32_SYNTH is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_MAUI is not set
# CONFIG_SOUND_YM3812 is not set
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_YMFPCI is not set
# CONFIG_SOUND_YMFPCI_LEGACY is not set
# CONFIG_SOUND_UART6850 is not set
# CONFIG_SOUND_AEDSP16 is not set
# CONFIG_SOUND_TVMIXER is not set
#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_LONG_TIMEOUT is not set
# CONFIG_USB_EHCI_HCD is not set
CONFIG_USB_UHCI_ALT=y
# CONFIG_USB_OHCI is not set
CONFIG_USB_AUDIO=m
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_BLUETOOTH is not set
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_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
# CONFIG_USB_WACOM is not set
CONFIG_USB_DC2XX=m
CONFIG_USB_MDC800=m
CONFIG_USB_SCANNER=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_HPUSBSCSI=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_OV511=m
CONFIG_USB_PWC=m
CONFIG_USB_SE401=m
CONFIG_USB_STV680=m
CONFIG_USB_VICAM=m
CONFIG_USB_DSBR=m
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=y
# CONFIG_USB_SERIAL_DEBUG is not set
# 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_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
CONFIG_USB_SERIAL_KEYSPAN=y
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_BRLVGER is not set
#
# Bluetooth support
#
# CONFIG_BLUEZ is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_FRAME_POINTER is not set
^ permalink raw reply
* ..abusive quoting, was: netfilter digest, Vol 1 #514 - 7 msgs (was Re: portforwarding-HOWTO)
From: Arnt Karlsen @ 2003-01-10 23:27 UTC (permalink / raw)
To: netfilter
In-Reply-To: <200301101507.12420.netfilter@newkirk.us>
On Fri, 10 Jan 2003 15:07:12 -0500,
Joel Newkirk <netfilter@newkirk.us> wrote in message
<200301101507.12420.netfilter@newkirk.us>:
> Please snip unrelated material out of a digest message when replying -
> the other six messages had nothing to do with this... A single-line
> response with over 450 quoted lines is a big waste, especially since
> you didn't sign the response making it appear that there might be
> more you had added further on in the quoted part.
..one way is have the list reject these long appended digest quotes
with such give-aways as "netfilter digest, Vol 1 #514 - 7 msgs" in
the subject line. The appropriate response IMNTHO is return these
abuses back to the abuser, asking him to remove his abusive waste
before reposting. Procmail can automate this.
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
^ permalink raw reply
* RE: problem with FORWARD chain
From: Reed M Wiedower @ 2003-01-10 23:31 UTC (permalink / raw)
To: netfilter
In-Reply-To: <211E94403B74D211878A0008C71C74DC60DCD5@ip216-50-5-162.z5-50-216.customer.algx.net>
(Forgot this info in last post!)
I'm running the 2.4.19 kernel on a debian box with the bridging/firewall patch from bridging.sourceforge.net (version 0.0.7) and the latest version of iptables.
A sample output from iptables -L -vx would be:
Chain INPUT (policy ACCEPT 20403 packets, 27177359 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 12188 packets, 786022 bytes)
pkts bytes target prot opt in out source destination
The few other people (who also don't get the FORWARD chain to properly show the counters) are still able to activate and implement rules, although as you can see, my policy should drop everything, and yet I'm still able to use the bridge.
eol,
Reed
reed wiedower
reed.wiedower@peyser.com
peyser.com
202.638.3730x115
| -----Original Message-----
| From: Reed Wiedower
| Sent: Friday, January 10, 2003 6:11 PM
| To: 'netfilter@lists.netfilter.org'
| Subject: problem with FORWARD chain
|
|
| I'm setting up a simple bridge firewall, and I've managed to get the
| bridging working properly. However, every time I attempt to create a
| firewall rule to prevent packets from traversing the FORWARD
| chain, I notice
| that, at least according to "iptables -L -vX", no packets are
| going across
| that particular chain. Any idea why this might be happening?
| I can implement
| rules on both the INPUT and OUTPUT chains and they work as
| expected, but for
| some reason nothing will display on the FORWARD chain.
|
| The bridging folks seem to think that it's an issue with
| iptables, not with
| the bridging code. Thanks in advance if anyone has seen this
| or knows how to
| deal with it.
|
|
| eol,
|
| Reed
|
|
| reed wiedower
| reed.wiedower@peyser.com
| peyser.com
| 202.638.3730x115
|
|
^ permalink raw reply
* ANNOUNCE: New versions of LinWSJT and UKW Tools
From: Jonathan Naylor @ 2003-01-10 23:32 UTC (permalink / raw)
To: Linux Hams
Hi All
I am happy to announce the availability of new versions of two of my
software packages. They both run under Linux and are open source (GPL).
The first is LinWSJT 0.4 which is an implementation of the FSK441 and
JT44 data modes for use with Meteor Scatter and EME/Tropo respectively.
New with this release is the FSK441 program as well as changes to the
JT44 program, although these are not visible to the user. Both programs
make use of the sound card in a PC to do the receiving and
transmitting, the hard work is done by Digital Signal Processing
functions within the program. The only real requirement is that the
computer clock is within one second or so of the correct time. Within
the package is a Word 2000 document outlining in simple language some
of the techniques that are used.
The second piece of software is UKW Tools which allows for the plotting
of terrain so that radio paths can be investigated. The actual data
used for this must be obtained separately over the Internet. This is a
minor revision of the previous release and fixes a couple of bugs.
Both of these packages can be found on my web pages
http://www.qsl.net/g4klx under Software. There you will also find
MTrack my satellite tracking program and Baken which visualises
European V/U/SHF beacons. Both of these latter two packages have
whiskers on.
Jonathan HB9DRD/G4KLX
^ permalink raw reply
* Re: A humble request for help
From: James Simmons @ 2003-01-10 23:42 UTC (permalink / raw)
To: Stefan Görling; +Cc: linux-kernel
In-Reply-To: <3E1C4215.5080306@gorling.se>
> James Simmons,Transvirtual
That is no longer the case. The company went under. Currently I'm
out of work. I can help out.
^ permalink raw reply
* Re: problem with ./runme in --batch mode. -- current p-o-m
From: Arnt Karlsen @ 2003-01-10 23:38 UTC (permalink / raw)
To: netfilter
In-Reply-To: <200301092244.09844.Alistair@nerdnet.ca>
On Thu, 9 Jan 2003 22:44:09 -0500,
Alistair Tonner <Alistair@nerdnet.ca> wrote in message
<200301092244.09844.Alistair@nerdnet.ca>:
>
> Hi folks:
>
> Its too late at night, and I shouldn't be mucking with scripts.
> ... I realize now that my previous email was in error ... and
> now realize what is actually happening when passing a long list to
> ./runme ... its just disconcerting to see patches that I don't want in
> the "already applied" list that ./runme spits up when running in batch
> mode ... I can now see that the $EXCLUDED are copied to $SEEN and
> listed in already applied list because of that ...
>
> perhaps we could put a *bypassed* tag in there so that others don't
> get as confused as I.....
..on finishing a batch run, it would be nice finding
a batch run log somewhere, to ease my confusion some,
on what works and not.
..does anyone run p-o-m from rpmbuild at all?
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
^ permalink raw reply
* [patch][2.5] setup default dma_mask for cardbus devices
From: Zwane Mwaikambo @ 2003-01-10 23:48 UTC (permalink / raw)
To: Linux Kernel; +Cc: Linus Torvalds, Russell King
Devices hanging off a cardbus bridge don't get a default dma mask which
causes problems later when doing pci_alloc_consistent. Patch has been
tested with tulip based ethernet.
Linux Tulip driver version 1.1.13 (May 11, 2002)
Unable to handle kernel NULL pointer dereference at virtual address
00000004
printing eip:
c011100c
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0060:[<c011100c>] Not tainted
EFLAGS: 00010282
EIP is at dma_alloc_coherent+0x1c/0x90
eax: 00000000 ebx: 0000003c ecx: 00000020 edx: c767a9e0
esi: 00000300 edi: c767bc00 ebp: c113da6c esp: c113da5c
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c113c000 task=c778e040)
Stack: c767bc4c 0000003c 00000080 c767bc00 c113dacc c02b0365 c767bc4c
00000300
c767a9f0 c01922cc c767bc4c c769c78c 00000000 00000003 c800f000
c767a800
c113dab4 00000009 c767a9e0 4167c694 c767c93c c769c89c c113dacc
c0192450
Call Trace:
[<c02b0365>] tulip_init_one+0x1f5/0xde0
[<c01922cc>] sysfs_get_inode+0x5c/0x110
[<c0192450>] sysfs_create+0x20/0x30
[<c0248ec5>] pci_device_probe+0x45/0x60
[<c025fde5>] bus_match+0x35/0x60
[<c025fe5a>] device_attach+0x4a/0x60
[<c025ffde>] bus_add_device+0x6e/0xb0
[<c025f2ac>] device_add+0xec/0x150
[<c032eb6e>] cb_alloc+0x2ae/0x310
[<c032b2d4>] get_socket_status+0x14/0x20
[<c032b976>] unreset_socket+0x86/0x100
[<c032b848>] setup_socket+0xa8/0xf0
[<c032cf34>] pcmcia_register_client+0x254/0x280
[<c01454c7>] cache_alloc_debugcheck_after+0x97/0xb0
[<c0144418>] kmalloc+0x98/0xe0
[<c032c11c>] pcmcia_bind_device+0x6c/0xe0
[<c011c3b6>] edd_create_symlink_to_scsidev+0x16/0xb0
[<c032f1e0>] ds_event+0x0/0xb0
[<c011c546>] edd_device_register+0x76/0x80
[<c01050c4>] init+0x84/0x1a0
[<c0105040>] init+0x0/0x1a0
[<c0105040>] init+0x0/0x1a0
[<c0105040>] init+0x0/0x1a0
[<c0107375>] kernel_thread_helper+0x5/0x10
Code: 8b 50 04 8b 00 83 fa 00 77 0a 83 f8 fe 77 05 b9 21 00 00 00
<0>Kernel panic: Attempted to kill init!
Index: linux-2.5.56/drivers/pcmcia/cardbus.c
===================================================================
RCS file: /build/cvsroot/linux-2.5.56/drivers/pcmcia/cardbus.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 cardbus.c
--- linux-2.5.56/drivers/pcmcia/cardbus.c 10 Jan 2003 21:22:48 -0000 1.1.1.1
+++ linux-2.5.56/drivers/pcmcia/cardbus.c 10 Jan 2003 23:38:24 -0000
@@ -281,6 +281,8 @@
dev->vendor = vend;
pci_readw(dev, PCI_DEVICE_ID, &dev->device);
dev->hdr_type = hdr & 0x7f;
+ dev->dma_mask = 0xffffffff;
+ dev->dev.dma_mask = &dev->dma_mask;
pci_setup_device(dev);
if (pci_enable_device(dev))
--
function.linuxpower.ca
^ permalink raw reply
* RE: problem with FORWARD chain
From: Reed Wiedower @ 2003-01-10 23:39 UTC (permalink / raw)
To: 'netfilter@lists.netfilter.org'
(Forgot this info in last post!)
I'm running the 2.4.19 kernel on a debian box with the bridging/firewall
patch from bridging.sourceforge.net (version 0.0.7) and the latest version
of iptables.
A sample output from iptables -L -vx would be:
Chain INPUT (policy ACCEPT 20403 packets, 27177359 bytes)
pkts bytes target prot opt in out source
destination
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 12188 packets, 786022 bytes)
pkts bytes target prot opt in out source
destination
The few other people (who also don't get the FORWARD chain to properly show
the counters) are still able to activate and implement rules, although as
you can see, my policy should drop everything, and yet I'm still able to use
the bridge.
eol,
Reed
reed wiedower
reed.wiedower@peyser.com
peyser.com
202.638.3730x115
| -----Original Message-----
| From: Reed Wiedower
| Sent: Friday, January 10, 2003 6:11 PM
| To: 'netfilter@lists.netfilter.org'
| Subject: problem with FORWARD chain
|
|
| I'm setting up a simple bridge firewall, and I've managed to get the
| bridging working properly. However, every time I attempt to create a
| firewall rule to prevent packets from traversing the FORWARD
| chain, I notice
| that, at least according to "iptables -L -vX", no packets are
| going across
| that particular chain. Any idea why this might be happening?
| I can implement
| rules on both the INPUT and OUTPUT chains and they work as
| expected, but for
| some reason nothing will display on the FORWARD chain.
|
| The bridging folks seem to think that it's an issue with
| iptables, not with
| the bridging code. Thanks in advance if anyone has seen this
| or knows how to
| deal with it.
|
|
| eol,
|
| Reed
|
|
| reed wiedower
| reed.wiedower@peyser.com
| peyser.com
| 202.638.3730x115
|
|
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.