Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
On Thu, Jul 05, 2001 at 12:18:46PM +0100, Alan Cox wrote: > > This bug hits me since 2.4.6-pre5 but nobody answered to my emails... The > > code line is identical (and the softirq.c:206 ofc). > > > > Anyone, any idea? > > None at all. There are odd items in your config - like khttpd which if > involved might explain why there are not more reports. If you look closer at my post you'll see that I do not have khttpd configured. I've just replied to that message because I saw somebody crying about the same thing. My configuration is posted in an earlier message but here it is again: CONFIG_X86=y CONFIG_ISA=y CONFIG_UID16=y CONFIG_EXPERIMENTAL=y CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y CONFIG_M586=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=5 CONFIG_X86_USE_STRING_486=y CONFIG_X86_ALIGNMENT_16=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_NET=y CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y CONFIG_FILTER=y CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_RTNETLINK=y CONFIG_NETLINK=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_FWMARK=y CONFIG_IP_ROUTE_VERBOSE=y CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m CONFIG_SYN_COOKIES=y CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y CONFIG_IP_NF_QUEUE=y CONFIG_IP_NF_IPTABLES=y CONFIG_IP_NF_MATCH_LIMIT=y CONFIG_IP_NF_MATCH_MAC=y CONFIG_IP_NF_MATCH_MARK=y CONFIG_IP_NF_MATCH_MULTIPORT=y CONFIG_IP_NF_MATCH_TOS=y CONFIG_IP_NF_MATCH_TCPMSS=y CONFIG_IP_NF_MATCH_STATE=y CONFIG_IP_NF_MATCH_UNCLEAN=y CONFIG_IP_NF_MATCH_OWNER=y CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_TARGET_MIRROR=y CONFIG_IP_NF_NAT=y CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=y CONFIG_IP_NF_TARGET_REDIRECT=y CONFIG_IP_NF_NAT_FTP=y CONFIG_IP_NF_MANGLE=y CONFIG_IP_NF_TARGET_TOS=y CONFIG_IP_NF_TARGET_MARK=y CONFIG_IP_NF_TARGET_LOG=y CONFIG_IP_NF_TARGET_TCPMSS=y CONFIG_NET_SCHED=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NET_SCH_CBQ=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 CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y 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_PIIX=y CONFIG_IDEDMA_AUTO=y CONFIG_BLK_DEV_IDE_MODES=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_NET_ISA=y CONFIG_NE2000=y CONFIG_NET_PCI=y CONFIG_NE2K_PCI=y CONFIG_8139TOO=y CONFIG_PPP=y CONFIG_PPP_ASYNC=y CONFIG_PPP_DEFLATE=y CONFIG_PPP_BSDCOMP=y CONFIG_PPPOE=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_REISERFS_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_TMPFS=y CONFIG_MINIX_FS=y CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y CONFIG_EXT2_FS=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_ISO8859_1=y CONFIG_VGA_CONSOLE=y CONFIG_VIDEO_SELECT=y CONFIG_MAGIC_SYSRQ=y -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
On Thu, Jul 05, 2001 at 06:52:43PM +0800, Thibaut Laurent wrote: > Hi, > > I posted a message 2 weeks ago regarding this bug, though I can't trigger the > kernel panic every time (see original post). My CPU is a MediaGX, and > Manfred's one is a 6x86MX. What about yours ? > After my first unsuccessful attempt with a 2.4.6-pre3, I tried several other > 2.4.6-preX and 2.4.5-acX kernels. All 2.4.6 (since pre1) seem to be > affected, and so do the latest ac's. I don't have tested 2.4.7-pre[12] yet, > but looking at the changelog, I doubt the fix is in. My CPU is: root@cyrix:~# cat /proc/cpuinfo processor : 0 vendor_id : CyrixInstead cpu family : 6 model : 2 model name : 6x86MX 2.5x Core/Bus Clock stepping: 7 cpu MHz : 166.452 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: yes fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr cx8 pge cmov mmx cyrix_arr bogomips : 331.77 -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
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_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_TCPMSS=m > CONFIG_KHTTPD=m > > CONFIG_IDE=y > > CONFIG_BLK_DEV_IDE=y > CONFIG_BLK_DEV_IDEDISK=y > 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_IDEDMA_AUTO=y > CONFIG_IDEDMA_IVB=y > > CONFIG_SCSI=m > CONFIG_BLK_DEV_SD=m > CONFIG_SD_EXTRA_DEVS=40 > CONFIG_CHR_DEV_ST=m > CONFIG_BLK_DEV_SR=m > CONFIG_SR_EXTRA_DEVS=2 > CONFIG_CHR_DEV_SG=m > CONFIG_SCSI_CONSTANTS=y > CONFIG_SCSI_LOGGING=y > > CONFIG_SCSI_AIC7XXX=m > CONFIG_AIC7XXX_CMDS_PER_DEVICE=8 > CONFIG_AIC7XXX_RESET_DELAY_MS=5000 > CONFIG_AIC7XXX_BUILD_FIRMWARE=y > > CONFIG_NETDEVICES=y > > CONFIG_DUMMY=m > > CONFIG_NET_ETHERNET=y > CONFIG_NET_PCI=y > CONFIG_8139TOO=m > > CONFIG_PPP=m > CONFIG_PPP_ASYNC=m > CONFIG_PPP_DEFLATE=m > CONFIG_PPP_BSDCOMP=m > > CONFIG_INPUT=m > CONFIG_INPUT_JOYDEV=m > CONFIG_INPUT_EVDEV=m > > CONFIG_VT=y > CONFIG_VT_CONSOLE=y > CONFIG_SERIAL=m > CONFIG_UNIX98_PTYS=y > CONFIG_UNIX98_PTY_COUNT=256 > CONFIG_PRINTER=m > > CONFIG_MOUSE=m > CONFIG_PSMOUSE=y > > CONFIG_JOYSTICK=y > CONFIG_INPUT_NS558=m > CONFIG_INPUT_ANALOG=m > > CONFIG_NVRAM=m > CONFIG_RTC=m > > CONFIG_AUTOFS4_FS=m > CONFIG_REISERFS_FS=y > CONFIG_FAT_FS=m > CONFIG_MSDOS_FS=m > CONFIG_VFAT_FS=m > CONFIG_TMPFS=y > CONFIG_ISO9660_FS=m > CONFIG_JOLIET=y > CONFIG_MINIX_FS=m > CONFIG_PROC_FS=y > CONFIG_DEVPTS_FS=y > CONFIG_EXT2_FS=y > CONFIG_UDF_FS=m > CONFIG_UDF_RW=y > > CONFIG_PARTITION_ADVANCED=y > CONFIG_MSDOS_PARTITION=y > CONFIG_NLS=y > > CONFIG_NLS_DEFAULT="iso8859-15" > CONFIG_NLS_CODEPAGE_437=m > CONFIG_NLS_CODEPAGE_850=m > CONFIG_NLS_ISO8859_1=m > CONFIG_NLS_ISO8859_15=m > CONFIG_NLS_UTF8=m > > CONFIG_VGA_CONSOLE=y > CONFIG_VIDEO_SELECT=y > > CONFIG_SOUND=m > CONFIG_SOUND_OSS=m > CONFIG_SOUND_TRACEINIT=y > CONFIG_SOUND_DMAP=y > CONFIG_SOUND_SB=m > CONFIG_SOUND_AWE32_SYNTH=m > CONFIG_SOUND_YM3812=m > > CONFIG_MAGIC_SYSRQ=y > > +++ > > If you need more information, tell me. > > Bye, > > Manfred > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
CONFIG_SCSI_AIC7XXX=m CONFIG_AIC7XXX_CMDS_PER_DEVICE=8 CONFIG_AIC7XXX_RESET_DELAY_MS=5000 CONFIG_AIC7XXX_BUILD_FIRMWARE=y CONFIG_NETDEVICES=y CONFIG_DUMMY=m CONFIG_NET_ETHERNET=y CONFIG_NET_PCI=y CONFIG_8139TOO=m CONFIG_PPP=m CONFIG_PPP_ASYNC=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_INPUT=m CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=m CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_SERIAL=m CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256 CONFIG_PRINTER=m CONFIG_MOUSE=m CONFIG_PSMOUSE=y CONFIG_JOYSTICK=y CONFIG_INPUT_NS558=m CONFIG_INPUT_ANALOG=m CONFIG_NVRAM=m CONFIG_RTC=m CONFIG_AUTOFS4_FS=m CONFIG_REISERFS_FS=y CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_TMPFS=y CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_MINIX_FS=m CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y CONFIG_EXT2_FS=y CONFIG_UDF_FS=m CONFIG_UDF_RW=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT=iso8859-15 CONFIG_NLS_CODEPAGE_437=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_UTF8=m CONFIG_VGA_CONSOLE=y CONFIG_VIDEO_SELECT=y CONFIG_SOUND=m CONFIG_SOUND_OSS=m CONFIG_SOUND_TRACEINIT=y CONFIG_SOUND_DMAP=y CONFIG_SOUND_SB=m CONFIG_SOUND_AWE32_SYNTH=m CONFIG_SOUND_YM3812=m CONFIG_MAGIC_SYSRQ=y +++ If you need more information, tell me. Bye, Manfred - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
On Thu, Jul 05, 2001 at 06:52:43PM +0800, Thibaut Laurent wrote: Hi, I posted a message 2 weeks ago regarding this bug, though I can't trigger the kernel panic every time (see original post). My CPU is a MediaGX, and Manfred's one is a 6x86MX. What about yours ? After my first unsuccessful attempt with a 2.4.6-pre3, I tried several other 2.4.6-preX and 2.4.5-acX kernels. All 2.4.6 (since pre1) seem to be affected, and so do the latest ac's. I don't have tested 2.4.7-pre[12] yet, but looking at the changelog, I doubt the fix is in. My CPU is: root@cyrix:~# cat /proc/cpuinfo processor : 0 vendor_id : CyrixInstead cpu family : 6 model : 2 model name : 6x86MX 2.5x Core/Bus Clock stepping: 7 cpu MHz : 166.452 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: yes fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr cx8 pge cmov mmx cyrix_arr bogomips: 331.77 -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
On Thu, Jul 05, 2001 at 12:18:46PM +0100, Alan Cox wrote: This bug hits me since 2.4.6-pre5 but nobody answered to my emails... The code line is identical (and the softirq.c:206 ofc). Anyone, any idea? None at all. There are odd items in your config - like khttpd which if involved might explain why there are not more reports. If you look closer at my post you'll see that I do not have khttpd configured. I've just replied to that message because I saw somebody crying about the same thing. My configuration is posted in an earlier message but here it is again: CONFIG_X86=y CONFIG_ISA=y CONFIG_UID16=y CONFIG_EXPERIMENTAL=y CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y CONFIG_M586=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=5 CONFIG_X86_USE_STRING_486=y CONFIG_X86_ALIGNMENT_16=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_NET=y CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y CONFIG_FILTER=y CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_RTNETLINK=y CONFIG_NETLINK=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_FWMARK=y CONFIG_IP_ROUTE_VERBOSE=y CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m CONFIG_SYN_COOKIES=y CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y CONFIG_IP_NF_QUEUE=y CONFIG_IP_NF_IPTABLES=y CONFIG_IP_NF_MATCH_LIMIT=y CONFIG_IP_NF_MATCH_MAC=y CONFIG_IP_NF_MATCH_MARK=y CONFIG_IP_NF_MATCH_MULTIPORT=y CONFIG_IP_NF_MATCH_TOS=y CONFIG_IP_NF_MATCH_TCPMSS=y CONFIG_IP_NF_MATCH_STATE=y CONFIG_IP_NF_MATCH_UNCLEAN=y CONFIG_IP_NF_MATCH_OWNER=y CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_TARGET_MIRROR=y CONFIG_IP_NF_NAT=y CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=y CONFIG_IP_NF_TARGET_REDIRECT=y CONFIG_IP_NF_NAT_FTP=y CONFIG_IP_NF_MANGLE=y CONFIG_IP_NF_TARGET_TOS=y CONFIG_IP_NF_TARGET_MARK=y CONFIG_IP_NF_TARGET_LOG=y CONFIG_IP_NF_TARGET_TCPMSS=y CONFIG_NET_SCHED=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NET_SCH_CBQ=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 CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y 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_PIIX=y CONFIG_IDEDMA_AUTO=y CONFIG_BLK_DEV_IDE_MODES=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_NET_ISA=y CONFIG_NE2000=y CONFIG_NET_PCI=y CONFIG_NE2K_PCI=y CONFIG_8139TOO=y CONFIG_PPP=y CONFIG_PPP_ASYNC=y CONFIG_PPP_DEFLATE=y CONFIG_PPP_BSDCOMP=y CONFIG_PPPOE=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_REISERFS_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_TMPFS=y CONFIG_MINIX_FS=y CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y CONFIG_EXT2_FS=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT=iso8859-1 CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_ISO8859_1=y CONFIG_VGA_CONSOLE=y CONFIG_VIDEO_SELECT=y CONFIG_MAGIC_SYSRQ=y -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.6-pre[5-8] fails to boot on my computer but ...
... 2.4.0 - 2.4.5-pre1 work just fine. Since the last changes related to the softirq stuff I'm getting an OOPS at boot after: Calibrating delay loop... kernel BUG at softirq.c:206! Here is the decode trace: ksymoops 2.3.4 on i686 2.4.5-pre1. Options used -v /usr/src/linux/vmlinux (specified) -K (specified) -L (specified) -o /lib/modules/2.4.5-pre1/ (default) -m /boot/System.map (specified) No modules in ksyms, skipping objects invalid operand: CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: 001d ebx: c02cc2c0 ecx: 0001 edx: 0001 esi: c02cc2c0 edi: 0001 ebp: esp: c027df60 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c027d000) Stack: c0226bf1 c0226c8d 00ce c02b6880 0009 c02b6880 c027dfa4 c0115ca1 c02b6880 c0269034 c0107ef1 0001 000a0600 c0105000 c02af900 0008e000 c0106be0 0001 0001 0001 000a0600 c0105000 Call Trace: [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 90 8b 43 08 85 c0 75 15 fb 8b 43 10 50 8b 43 >>EIP; c0115e82<= Trace; c0115ca1 Trace; c0107ef1 Trace; c0105000 <_stext+0/0> Trace; c0106be0 Trace; c0105000 <_stext+0/0> Trace; c0105000 <_stext+0/0> Code; c0115e82 <_EIP>: Code; c0115e82<= 0: 0f 0b ud2a <= Code; c0115e84 2: 83 c4 0c add$0xc,%esp Code; c0115e87 5: 90nop Code; c0115e88 6: 8b 43 08 mov0x8(%ebx),%eax Code; c0115e8b 9: 85 c0 test %eax,%eax Code; c0115e8d b: 75 15 jne22 <_EIP+0x22> c0115ea4 Code; c0115e8f d: fbsti Code; c0115e90 e: 8b 43 10 mov0x10(%ebx),%eax Code; c0115e93 11: 50push %eax Code; c0115e94 12: 8b 43 00 mov0x0(%ebx),%eax Kernel panic: Aiee, killing interrupt handler! If you need any other info please see my previous post: http://www.uwsg.indiana.edu/hypermail/linux/kernel/0106.2/0790.html (about the same problem and the OOPS is almost the same) or just drop me an e-mail. Please advise! -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.6-pre[5-8] fails to boot on my computer but ...
... 2.4.0 - 2.4.5-pre1 work just fine. Since the last changes related to the softirq stuff I'm getting an OOPS at boot after: Calibrating delay loop... kernel BUG at softirq.c:206! Here is the decode trace: ksymoops 2.3.4 on i686 2.4.5-pre1. Options used -v /usr/src/linux/vmlinux (specified) -K (specified) -L (specified) -o /lib/modules/2.4.5-pre1/ (default) -m /boot/System.map (specified) No modules in ksyms, skipping objects invalid operand: CPU:0 EIP:0010:[c0115e82] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: 001d ebx: c02cc2c0 ecx: 0001 edx: 0001 esi: c02cc2c0 edi: 0001 ebp: esp: c027df60 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c027d000) Stack: c0226bf1 c0226c8d 00ce c02b6880 0009 c02b6880 c027dfa4 c0115ca1 c02b6880 c0269034 c0107ef1 0001 000a0600 c0105000 c02af900 0008e000 c0106be0 0001 0001 0001 000a0600 c0105000 Call Trace: [c0115ca1] [c0107ef1] [c0105000] [c0106be0] [c0105000] [c0105000] Code: 0f 0b 83 c4 0c 90 8b 43 08 85 c0 75 15 fb 8b 43 10 50 8b 43 EIP; c0115e82 tasklet_hi_action+6a/ac = Trace; c0115ca1 do_softirq+45/68 Trace; c0107ef1 do_IRQ+9d/b0 Trace; c0105000 _stext+0/0 Trace; c0106be0 ret_from_intr+0/7 Trace; c0105000 _stext+0/0 Trace; c0105000 _stext+0/0 Code; c0115e82 tasklet_hi_action+6a/ac _EIP: Code; c0115e82 tasklet_hi_action+6a/ac = 0: 0f 0b ud2a = Code; c0115e84 tasklet_hi_action+6c/ac 2: 83 c4 0c add$0xc,%esp Code; c0115e87 tasklet_hi_action+6f/ac 5: 90nop Code; c0115e88 tasklet_hi_action+70/ac 6: 8b 43 08 mov0x8(%ebx),%eax Code; c0115e8b tasklet_hi_action+73/ac 9: 85 c0 test %eax,%eax Code; c0115e8d tasklet_hi_action+75/ac b: 75 15 jne22 _EIP+0x22 c0115ea4 tasklet_hi_action+8c/ac Code; c0115e8f tasklet_hi_action+77/ac d: fbsti Code; c0115e90 tasklet_hi_action+78/ac e: 8b 43 10 mov0x10(%ebx),%eax Code; c0115e93 tasklet_hi_action+7b/ac 11: 50push %eax Code; c0115e94 tasklet_hi_action+7c/ac 12: 8b 43 00 mov0x0(%ebx),%eax Kernel panic: Aiee, killing interrupt handler! If you need any other info please see my previous post: http://www.uwsg.indiana.edu/hypermail/linux/kernel/0106.2/0790.html (about the same problem and the OOPS is almost the same) or just drop me an e-mail. Please advise! -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[OOPS] Failed to boot 2.4.6-pre5
Hi,
[1.] One line summary of the problem:
I can not start 2.4.6-pre5 on my machine.
[2.] Full description of the problem/report:
I've tried to upgrade from 2.4.5-pre1 to 2.4.6-pre5 but it failed the new
kernel failed to boot. It OOPS-es while it's starting. I managed to write
down some of the OOPS parameters.
[3.] Keywords (i.e., modules, networking, kernel):
kernel boot.
[4.] Kernel version (from /proc/version):
2.4.6-pre5
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
All information that I have not saved is replaced with zeroes. So I got
only the EIP, call trace and the Code:
ksymoops 2.3.4 on i686 2.4.5-pre1. Options used
-v /usr/src/linux/vmlinux (specified)
-K (specified)
-L (specified)
-o /lib/modules/2.4.5-pre1/ (default)
-m /boot/System.map (specified)
No modules in ksyms, skipping objects
Oops: 0001
CPU:1
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS:
eax: ebx: ecx: edx:
esi: edi: ebp: esp:
ds: es: ss:
Process swapper (pid: 0, stackpage=)
Call Trace: [] [] [] [] []
[]
Code: 0f 0b 83 c4 0c 90 8b 43 08 85 c0 75 15 fb 8b 43 10 50 8b 43
>>EIP; c0116f72<=
Trace; c0116d8d
Trace; c0107fe9
Trace; c0105000 <_stext+0/0>
Trace; c0106bd0
Trace; c0105000 <_stext+0/0>
Trace; c0105000 <_stext+0/0>
Code; c0116f72
<_EIP>:
Code; c0116f72<=
0: 0f 0b ud2a <=
Code; c0116f74
2: 83 c4 0c addl $0xc,%esp
Code; c0116f77
5: 90nop
Code; c0116f78
6: 8b 43 08 movl 0x8(%ebx),%eax
Code; c0116f7b
9: 85 c0 testl %eax,%eax
Code; c0116f7d
b: 75 15 jne22 <_EIP+0x22> c0116f94
Code; c0116f7f
d: fbsti
Code; c0116f80
e: 8b 43 10 movl 0x10(%ebx),%eax
Code; c0116f83
11: 50pushl %eax
Code; c0116f84
12: 8b 43 00 movl 0x0(%ebx),%eax
[6.] A small shell script or example program which triggers the
problem (if possible)
N/A.
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux cyrix 2.4.5-pre1 #1 Tue May 8 11:27:27 EEST 2001 i686 unknown
Gnu C egcs-2.91.66
Gnu make 3.77
binutils 2.9.1.0.25
usage: fdformat [ -n ] device
mount 2.9v
modutils 2.4.6
e2fsprogs 1.15
PPP2.4.0b1
Linux C Library2.2.3
Dynamic linker (ldd) 2.2.3
Procps 2.0.6
Net-tools 1.52
Kbd0.99
Sh-utils 1.16
Modules Loaded
[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : CyrixInstead
cpu family : 6
model : 2
model name : 6x86MX 2.5x Core/Bus Clock
stepping: 7
cpu MHz : 166.451
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: yes
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de tsc msr cx8 pge cmov mmx cyrix_arr
bogomips: 331.77
[7.3.] Module information (from /proc/modules):
No modules are loaded.
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
0280-029f : eth0
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
4000-403f : Intel Corporation 82371AB PIIX4 ACPI
5000-501f : Intel Corporation 82371AB PIIX4 ACPI
6400-641f : Intel Corporation 82371AB PIIX4 USB
6800-68ff : Realtek Semiconductor Co., Ltd. RTL-8139
6800-68ff : 8139too
6c00-6c1f : Realtek Semiconductor Co., Ltd. RTL-8029(AS)
6c00-6c1f : ne2k-pci
7000-70ff : Realtek Semiconductor Co., Ltd. RTL-8139 (#2)
7000-70ff : 8139too
7400-741f : Realtek Semiconductor Co., Ltd. RTL-8029(AS) (#2)
7400-741f : ne2k-pci
f000-f00f : Intel Corporation 82371AB PIIX4 IDE
f000-f007 : ide0
-0009 : System RAM
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-01ff : System RAM
0010-0021cd7f : Kernel code
0021cd80-0027c73f : Kernel data
e000-e0ff : Realtek Semiconductor Co., Ltd. RTL-8139
e000-e0ff : 8139too
e0001000-e00010ff : Realtek
[OOPS] Failed to boot 2.4.6-pre5
82371AB PIIX4 IDE
f000-f007 : ide0
-0009 : System RAM
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-01ff : System RAM
0010-0021cd7f : Kernel code
0021cd80-0027c73f : Kernel data
e000-e0ff : Realtek Semiconductor Co., Ltd. RTL-8139
e000-e0ff : 8139too
e0001000-e00010ff : Realtek Semiconductor Co., Ltd. RTL-8139 (#2)
e0001000-e00010ff : 8139too
- : reserved
[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort-
MAbort+ SERR- PERR-
Latency: 64 set
00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Latency: 0 set
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80)
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Latency: 64 set
Region 4: I/O ports at f000
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Latency: 64 set
Interrupt: pin D routed to IRQ 15
Region 4: I/O ports at 6400
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Interrupt: pin ? routed to IRQ 9
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8139 (rev 10)
Subsystem: Unknown device 10ec:8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Latency: 32 min, 64 max, 64 set
Interrupt: pin A routed to IRQ 12
Region 0: I/O ports at 6800
Region 1: Memory at e000 (32-bit, non-prefetchable)
Capabilities: [50] Power Management version 2
Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME-
Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8029
Subsystem: Unknown device 10ec:8029
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at 6c00
00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8139 (rev 10)
Subsystem: Unknown device 10bd:0320
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Latency: 32 min, 64 max, 64 set
Interrupt: pin A routed to IRQ 7
Region 0: I/O ports at 7000
Region 1: Memory at e0001000 (32-bit, non-prefetchable)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8029
Subsystem: Unknown device 10ec:8029
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort-
MAbort- SERR- PERR-
Interrupt: pin A routed to IRQ 15
Region 0: I/O ports at 7400
[7.6.] SCSI information (from /proc/scsi/scsi)
No SCSI.
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
[X.] Other notes, patches, fixes, workarounds:
It seems to be something related to the latest changes in the do_softirq stuff.
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: loop problems continue in 2.4.3
On Mon, Apr 16, 2001 at 05:30:45AM -0400, Alexander Viro wrote: > > > On Mon, 16 Apr 2001, Jens Axboe wrote: > > > > I can mount the same file on the same mountpoint more than once. If I > > > mount a file twice (same file on the same mount point) > > > > This is a 2.4 feature > > Ability to losetup different loop devices to the same underlying > file is a bug, though. Not that it was new, though... But the guy said: " > disappers from cat /proc/mounts output, but the module 'loop' shows as > busy and cannot be removed even though there are no more loop mounts. " So he has no loop mounts and he can not remove the module. This is a bug! -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: loop problems continue in 2.4.3
On Mon, Apr 16, 2001 at 05:30:45AM -0400, Alexander Viro wrote: On Mon, 16 Apr 2001, Jens Axboe wrote: I can mount the same file on the same mountpoint more than once. If I mount a file twice (same file on the same mount point) This is a 2.4 feature Ability to losetup different loop devices to the same underlying file is a bug, though. Not that it was new, though... But the guy said: " disappers from cat /proc/mounts output, but the module 'loop' shows as busy and cannot be removed even though there are no more loop mounts. " So he has no loop mounts and he can not remove the module. This is a bug! -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
No one wants to help me :-(
Hello,
I was expecting to receive some replies to my last desperate messages:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg35446.html
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg36591.html
My machine is dyeing in add_timer(). It seems to happen only on SMP
machines and is something related to the network driver. For some reason
one of the timer lists gets broken so we (we are two people trying to
solve this issue) wrote a "safe" timer.c which tries to rebuild the chain
in case it hits a NULL pointer.
The machine is (ofcourse) slower with this patch but at least it works.
Maybe someone can see which is the real bug and fix it.
Please help!
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
/*
* linux/kernel/timer.c
*
* Kernel internal timers, kernel timekeeping, basic process system calls
*
* Copyright (C) 1991, 1992 Linus Torvalds
*
* 1997-01-28 Modified by Finn Arne Gangstad to make timers scale better.
*
* 1997-09-10 Updated NTP code according to technical memorandum Jan '96
* "A Kernel Model for Precision Timekeeping" by Dave Mills
* 1998-12-24 Fixed a xtime SMP race (we need the xtime_lock rw spinlock to
* serialize accesses to xtime/lost_ticks).
* Copyright (C) 1998 Andrea Arcangeli
* 1999-03-10 Improved NTP compatibility by Ulrich Windl
*/
#include
#include
#include
#include
#include
#include
#include
#include
/*
* Timekeeping variables
*/
long tick = (100 + HZ/2) / HZ; /* timer interrupt period */
/* The current time */
volatile struct timeval xtime __attribute__ ((aligned (16)));
/* Don't completely fail for HZ > 500. */
int tickadj = 500/HZ ? : 1; /* microsecs */
DECLARE_TASK_QUEUE(tq_timer);
DECLARE_TASK_QUEUE(tq_immediate);
/*
* phase-lock loop variables
*/
/* TIME_ERROR prevents overwriting the CMOS clock */
int time_state = TIME_OK; /* clock synchronization status */
int time_status = STA_UNSYNC; /* clock status bits*/
long time_offset; /* time adjustment (us) */
long time_constant = 2; /* pll time constant*/
long time_tolerance = MAXFREQ; /* frequency tolerance (ppm)*/
long time_precision = 1;/* clock precision (us) */
long time_maxerror = NTP_PHASE_LIMIT; /* maximum error (us) */
long time_esterror = NTP_PHASE_LIMIT; /* estimated error (us) */
long time_phase;/* phase offset (scaled us) */
long time_freq = ((100 + HZ/2) % HZ - HZ/2) << SHIFT_USEC;
/* frequency offset (scaled ppm)*/
long time_adj; /* tick adjust (scaled 1 / HZ) */
long time_reftime; /* time at last adjustment (s) */
long time_adjust;
long time_adjust_step;
unsigned long event;
extern int do_setitimer(int, struct itimerval *, struct itimerval *);
unsigned long volatile jiffies;
unsigned int * prof_buffer;
unsigned long prof_len;
unsigned long prof_shift;
/*
* Event timer code
*/
#define TVN_BITS 6
#define TVR_BITS 8
#define TVN_SIZE (1 << TVN_BITS)
#define TVR_SIZE (1 << TVR_BITS)
#define TVN_MASK (TVN_SIZE - 1)
#define TVR_MASK (TVR_SIZE - 1)
struct timer_vec {
int index;
struct list_head vec[TVN_SIZE];
};
struct timer_vec_root {
int index;
struct list_head vec[TVR_SIZE];
};
static struct timer_vec tv5;
static struct timer_vec tv4;
static struct timer_vec tv3;
static struct timer_vec tv2;
static struct timer_vec_root tv1;
static struct timer_vec * const tvecs[] = {
(struct timer_vec *), , , ,
};
#define NOOF_TVECS (sizeof(tvecs) / sizeof(tvecs[0]))
void init_timervecs (void)
{
int i;
for (i = 0; i < TVN_SIZE; i++) {
INIT_LIST_HEAD(tv5.vec + i);
INIT_LIST_HEAD(tv4.vec + i);
INIT_LIST_HEAD(tv3.vec + i);
INIT_LIST_HEAD(tv2.vec + i);
}
for (i = 0; i < TVR_SIZE; i++)
INIT_LIST_HEAD(tv1.vec + i);
}
static unsigned long timer_jiffies;
void inline debug_timer_list(struct list_head *L, int v, int i);
static inline void internal_add_timer(struct timer_list *timer)
{
/*
* must be cli-ed when calling this
*/
unsigned long expires = timer->expires;
unsigned long idx = expires - timer_jiffies;
struct list_head * vec;
int i=-10,v=-10;
if (idx < TVR_SIZE) {
i = expires & TVR_MASK;
vec = tv1.vec + i;
v=1;
} else if (idx < 1 << (TVR_BITS + TVN_BITS)) {
i = (expires >> TVR_BITS) & TVN_MASK;
vec = tv2.vec + i;
v=2;
} else if (idx &
No one wants to help me :-(
Hello,
I was expecting to receive some replies to my last desperate messages:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg35446.html
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg36591.html
My machine is dyeing in add_timer(). It seems to happen only on SMP
machines and is something related to the network driver. For some reason
one of the timer lists gets broken so we (we are two people trying to
solve this issue) wrote a "safe" timer.c which tries to rebuild the chain
in case it hits a NULL pointer.
The machine is (ofcourse) slower with this patch but at least it works.
Maybe someone can see which is the real bug and fix it.
Please help!
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
/*
* linux/kernel/timer.c
*
* Kernel internal timers, kernel timekeeping, basic process system calls
*
* Copyright (C) 1991, 1992 Linus Torvalds
*
* 1997-01-28 Modified by Finn Arne Gangstad to make timers scale better.
*
* 1997-09-10 Updated NTP code according to technical memorandum Jan '96
* "A Kernel Model for Precision Timekeeping" by Dave Mills
* 1998-12-24 Fixed a xtime SMP race (we need the xtime_lock rw spinlock to
* serialize accesses to xtime/lost_ticks).
* Copyright (C) 1998 Andrea Arcangeli
* 1999-03-10 Improved NTP compatibility by Ulrich Windl
*/
#include linux/config.h
#include linux/mm.h
#include linux/timex.h
#include linux/delay.h
#include linux/smp_lock.h
#include linux/interrupt.h
#include linux/kernel_stat.h
#include asm/uaccess.h
/*
* Timekeeping variables
*/
long tick = (100 + HZ/2) / HZ; /* timer interrupt period */
/* The current time */
volatile struct timeval xtime __attribute__ ((aligned (16)));
/* Don't completely fail for HZ 500. */
int tickadj = 500/HZ ? : 1; /* microsecs */
DECLARE_TASK_QUEUE(tq_timer);
DECLARE_TASK_QUEUE(tq_immediate);
/*
* phase-lock loop variables
*/
/* TIME_ERROR prevents overwriting the CMOS clock */
int time_state = TIME_OK; /* clock synchronization status */
int time_status = STA_UNSYNC; /* clock status bits*/
long time_offset; /* time adjustment (us) */
long time_constant = 2; /* pll time constant*/
long time_tolerance = MAXFREQ; /* frequency tolerance (ppm)*/
long time_precision = 1;/* clock precision (us) */
long time_maxerror = NTP_PHASE_LIMIT; /* maximum error (us) */
long time_esterror = NTP_PHASE_LIMIT; /* estimated error (us) */
long time_phase;/* phase offset (scaled us) */
long time_freq = ((100 + HZ/2) % HZ - HZ/2) SHIFT_USEC;
/* frequency offset (scaled ppm)*/
long time_adj; /* tick adjust (scaled 1 / HZ) */
long time_reftime; /* time at last adjustment (s) */
long time_adjust;
long time_adjust_step;
unsigned long event;
extern int do_setitimer(int, struct itimerval *, struct itimerval *);
unsigned long volatile jiffies;
unsigned int * prof_buffer;
unsigned long prof_len;
unsigned long prof_shift;
/*
* Event timer code
*/
#define TVN_BITS 6
#define TVR_BITS 8
#define TVN_SIZE (1 TVN_BITS)
#define TVR_SIZE (1 TVR_BITS)
#define TVN_MASK (TVN_SIZE - 1)
#define TVR_MASK (TVR_SIZE - 1)
struct timer_vec {
int index;
struct list_head vec[TVN_SIZE];
};
struct timer_vec_root {
int index;
struct list_head vec[TVR_SIZE];
};
static struct timer_vec tv5;
static struct timer_vec tv4;
static struct timer_vec tv3;
static struct timer_vec tv2;
static struct timer_vec_root tv1;
static struct timer_vec * const tvecs[] = {
(struct timer_vec *)tv1, tv2, tv3, tv4, tv5
};
#define NOOF_TVECS (sizeof(tvecs) / sizeof(tvecs[0]))
void init_timervecs (void)
{
int i;
for (i = 0; i TVN_SIZE; i++) {
INIT_LIST_HEAD(tv5.vec + i);
INIT_LIST_HEAD(tv4.vec + i);
INIT_LIST_HEAD(tv3.vec + i);
INIT_LIST_HEAD(tv2.vec + i);
}
for (i = 0; i TVR_SIZE; i++)
INIT_LIST_HEAD(tv1.vec + i);
}
static unsigned long timer_jiffies;
void inline debug_timer_list(struct list_head *L, int v, int i);
static inline void internal_add_timer(struct timer_list *timer)
{
/*
* must be cli-ed when calling this
*/
unsigned long expires = timer-expires;
unsigned long idx = expires - timer_jiffies;
struct list_head * vec;
int i=-10,v=-10;
if (idx TVR_SIZE) {
i = expires TVR_MASK;
vec = tv1.vec + i;
v=1;
} else if (idx 1 (TVR_BITS + TVN_BITS)) {
i = (expires TVR_BITS) TVN_MASK;
Re: SCSI tape corruption problem
This seems to happen on my system too but I have and IDE tape: Apr 3 00:00:48 www kernel: ide-tape: hdb <-> ht0: Seagate STT8000A rev 5.02 Apr 3 00:00:48 www kernel: ide-tape: hdb <-> ht0: 600KBps, 14*26kB buffer, 5850kB pipeline, 80ms tDSC, DMA I have managed to recover the tar archive by writing the data through a faucet pipe on another machine. So this seems to be a problem only when I write the data on the same IDE interface. On Wed, Apr 11, 2001 at 01:37:02PM +0200, [EMAIL PROTECTED] wrote: > I've recently installed a SDT-9000 tape drive. Running kernel 2.4.x I've > noticed the following (critical) problem: > > Apparently the data are corrupted on the way to (from?) tape. I'm sure the > DAT > drive is good (worked good on NT, head clean, new cartridge). It doesn't > report > data errors. I've got bad CRC errors on tar (the gzip part, of course) > > The drive is on an Adaptec 2904 controller, with a Yamaha CDRW on the same > bus. > I'm pretty sure it's terminated correctly. Another SCSI controller (2940) > is > driving 2 hard drives. Underlying HW: Athlon 1GHz, on Asus board (VIA > chipset). > It seems to happen frequently (tried four times with about 600MB of data, > three > times failed the restore :((. Tried all the 2.4.x kernel series (thru > 2.4.3) > > What can it be? (I'll try to compare the read data with the original...) > > -- Lorenzo Marcantonio > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: SCSI tape corruption problem
This seems to happen on my system too but I have and IDE tape: Apr 3 00:00:48 www kernel: ide-tape: hdb - ht0: Seagate STT8000A rev 5.02 Apr 3 00:00:48 www kernel: ide-tape: hdb - ht0: 600KBps, 14*26kB buffer, 5850kB pipeline, 80ms tDSC, DMA I have managed to recover the tar archive by writing the data through a faucet pipe on another machine. So this seems to be a problem only when I write the data on the same IDE interface. On Wed, Apr 11, 2001 at 01:37:02PM +0200, [EMAIL PROTECTED] wrote: I've recently installed a SDT-9000 tape drive. Running kernel 2.4.x I've noticed the following (critical) problem: Apparently the data are corrupted on the way to (from?) tape. I'm sure the DAT drive is good (worked good on NT, head clean, new cartridge). It doesn't report data errors. I've got bad CRC errors on tar (the gzip part, of course) The drive is on an Adaptec 2904 controller, with a Yamaha CDRW on the same bus. I'm pretty sure it's terminated correctly. Another SCSI controller (2940) is driving 2 hard drives. Underlying HW: Athlon 1GHz, on Asus board (VIA chipset). It seems to happen frequently (tried four times with about 600MB of data, three times failed the restore :((. Tried all the 2.4.x kernel series (thru 2.4.3) What can it be? (I'll try to compare the read data with the original...) -- Lorenzo Marcantonio - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: OOPS: Resend - more info
?? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: OOPS: Resend - more info
?? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
OOPS: Resend - more info
Hello,
I hope that this time it will be clear enough to extract some info. I got
the full OOPS and decoded it. Please find attached the decoded OOPS and
other info.
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
[1.] One line summary of the problem:
Kernel OOPS. Machine hanged under heavy load.
[2.] Full description of the problem/report:
The computer that is handling our e-mail hanged with an OOPS. This is the fifth time.
I hope that we'll get it.
[3.] Keywords (i.e., modules, networking, kernel):
kernel, networking
[4.] Kernel version (from /proc/version):
Linux version 2.4.3-pre8 (root@k) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2
release)) #1 SMP Mon Mar 26 14:39:35 EEST 2001
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
See the other attached file.
[6.] A small shell script or example program which triggers the
problem (if possible)
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
Linux k 2.4.3-pre8 #1 SMP Mon Mar 26 14:39:35 EEST 2001 i686 unknown
Gnu C egcs-2.91.66
Gnu make 3.79
binutils 2.10.1.0.2
util-linux 2.10o
modutils 2.4.2
e2fsprogs 1.19
PPP2.3.11
Linux C Library2.2.1
ldd: version 1.9.9
Procps 2.0.7
Net-tools 1.57
Kbd0.99
Sh-utils 2.0
Modules Loaded
[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping: 3
cpu MHz : 736.019
cache size : 256 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 mmx fxsr sse
bogomips: 1468.00
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping: 3
cpu MHz : 736.019
cache size : 256 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 mmx fxsr sse
bogomips: 1471.28
[7.3.] Module information (from /proc/modules):
none
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
5000-500f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
6000-607f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
9000-9fff : PCI Bus #01
9000-907f : Silicon Integrated Systems [SiS] 86C326
a000-a00f : VIA Technologies, Inc. Bus Master IDE
a000-a007 : ide0
a008-a00f : ide1
ac00-ac07 : Triones Technologies, Inc. HPT366
b000-b003 : Triones Technologies, Inc. HPT366
b400-b407 : Triones Technologies, Inc. HPT366
b800-b803 : Triones Technologies, Inc. HPT366
bc00-bcff : Triones Technologies, Inc. HPT366
bc00-bc07 : ide2
bc08-bc0f : ide3
bc10-bcff : HPT370
c000-c0ff : Realtek Semiconductor Co., Ltd. RTL-8139
c000-c0ff : 8139too
-0009fbff : System RAM
0009fc00-0009 : System RAM
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-1fff : System RAM
0010-0021da15 : Kernel code
0021da16-002817bf : Kernel data
d000-d3ff : VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x]
d400-d5ff : PCI Bus #01
d500-d500 : Silicon Integrated Systems [SiS] 86C326
d700-d77f : PCI Bus #01
d700-d77f : Silicon Integrated Systems [SiS] 86C326
d780-d78000ff : Realtek Semiconductor Co., Ltd. RTL-8139
d780-d78000ff : 8139too
fec0-fec00fff : reserved
fee0-fee00fff : reserved
- : reserved
[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev c4)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- Fast
B2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR
-
Capabilities: [c0] 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-
00:01.0 PCI bridge:
OOPS: Resend - more info
Hello,
I hope that this time it will be clear enough to extract some info. I got
the full OOPS and decoded it. Please find attached the decoded OOPS and
other info.
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
[1.] One line summary of the problem:
Kernel OOPS. Machine hanged under heavy load.
[2.] Full description of the problem/report:
The computer that is handling our e-mail hanged with an OOPS. This is the fifth time.
I hope that we'll get it.
[3.] Keywords (i.e., modules, networking, kernel):
kernel, networking
[4.] Kernel version (from /proc/version):
Linux version 2.4.3-pre8 (root@k) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2
release)) #1 SMP Mon Mar 26 14:39:35 EEST 2001
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
See the other attached file.
[6.] A small shell script or example program which triggers the
problem (if possible)
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
Linux k 2.4.3-pre8 #1 SMP Mon Mar 26 14:39:35 EEST 2001 i686 unknown
Gnu C egcs-2.91.66
Gnu make 3.79
binutils 2.10.1.0.2
util-linux 2.10o
modutils 2.4.2
e2fsprogs 1.19
PPP2.3.11
Linux C Library2.2.1
ldd: version 1.9.9
Procps 2.0.7
Net-tools 1.57
Kbd0.99
Sh-utils 2.0
Modules Loaded
[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping: 3
cpu MHz : 736.019
cache size : 256 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 mmx fxsr sse
bogomips: 1468.00
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping: 3
cpu MHz : 736.019
cache size : 256 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 mmx fxsr sse
bogomips: 1471.28
[7.3.] Module information (from /proc/modules):
none
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
5000-500f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
6000-607f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
9000-9fff : PCI Bus #01
9000-907f : Silicon Integrated Systems [SiS] 86C326
a000-a00f : VIA Technologies, Inc. Bus Master IDE
a000-a007 : ide0
a008-a00f : ide1
ac00-ac07 : Triones Technologies, Inc. HPT366
b000-b003 : Triones Technologies, Inc. HPT366
b400-b407 : Triones Technologies, Inc. HPT366
b800-b803 : Triones Technologies, Inc. HPT366
bc00-bcff : Triones Technologies, Inc. HPT366
bc00-bc07 : ide2
bc08-bc0f : ide3
bc10-bcff : HPT370
c000-c0ff : Realtek Semiconductor Co., Ltd. RTL-8139
c000-c0ff : 8139too
-0009fbff : System RAM
0009fc00-0009 : System RAM
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-1fff : System RAM
0010-0021da15 : Kernel code
0021da16-002817bf : Kernel data
d000-d3ff : VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x]
d400-d5ff : PCI Bus #01
d500-d500 : Silicon Integrated Systems [SiS] 86C326
d700-d77f : PCI Bus #01
d700-d77f : Silicon Integrated Systems [SiS] 86C326
d780-d78000ff : Realtek Semiconductor Co., Ltd. RTL-8139
d780-d78000ff : 8139too
fec0-fec00fff : reserved
fee0-fee00fff : reserved
- : reserved
[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev c4)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- Fast
B2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort-
MAbort+ SERR
- PERR-
Latency: 8
Region 0: Memory at d000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ
[dmircea@kappa.ro: OOPS]
Resend. I got no answer.
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
Hello,
[1.] One line summary of the problem:
Kernel OOPS. Machine hanged under heavy load.
[2.] Full description of the problem/report:
The computer that is handling our e-mail hanged with an OOPS from which I
recovered only the EIP.
[3.] Keywords (i.e., modules, networking, kernel):
networking, kernel
[4.] Kernel version (from /proc/version):
Linux version 2.4.3-pre4 (root@k) (gcc version egcs-2.91.66 19990314/Linux
(egcs-1.1.2 release)) #1 SMP Tue Mar 13 11:00:08 EET 2001
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
This is all that I could save:
Unable to handle kernel paging request 86c90cc0
OOPS:000 CPU1: EIP=0010:[]
I could not get the stack trace. Next-time I'll log the message on a serial
console.
If I read from System.map the address is between:
c01f7b98 T tcp_v4_rcv
c01f81b0 t __tcp_v4_rehash
[6.] A small shell script or example program which triggers the
problem (if possible)
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
Linux k 2.4.3-pre4 #1 SMP Tue Mar 13 11:00:08 EET 2001 i686 unknown
Gnu C egcs-2.91.66
Gnu make 3.79
binutils 2.10.1.0.2
util-linux 2.10o
modutils 2.4.2
e2fsprogs 1.19
PPP2.3.11
Linux C Library2.2.1
ldd: version 1.9.9
Procps 2.0.7
Net-tools 1.57
Kbd0.99
Sh-utils 2.0
Modules Loaded
[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping: 3
cpu MHz : 736.019
cache size : 256 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse
bogomips: 1468.00
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping: 3
cpu MHz : 736.019
cache size : 256 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse
bogomips: 1471.28
[7.3.] Module information (from /proc/modules):
none
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
5000-500f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
6000-607f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
9000-9fff : PCI Bus #01
9000-907f : Silicon Integrated Systems [SiS] 86C326
a000-a00f : VIA Technologies, Inc. Bus Master IDE
a000-a007 : ide0
a008-a00f : ide1
ac00-ac07 : Triones Technologies, Inc. HPT366
b000-b003 : Triones Technologies, Inc. HPT366
b400-b407 : Triones Technologies, Inc. HPT366
b800-b803 : Triones Technologies, Inc. HPT366
bc00-bcff : Triones Technologies, Inc. HPT366
bc00-bc07 : ide2
bc08-bc0f : ide3
bc10-bcff : HPT370
c000-c0ff : Realtek Semiconductor Co., Ltd. RTL-8139
c000-c0ff : eth0
-0009fbff : System RAM
0009fc00-0009 : System RAM
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-1fff : System RAM
0010-00220086 : Kernel code
00220087-00286b7f : Kernel data
d000-d3ff : VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x]
d400-d5ff : PCI Bus #01
d500-d500 : Silicon Integrated Systems [SiS] 86C326
d700-d77f : PCI Bus #01
d700-d77f : Silicon Integrated Systems [SiS] 86C326
d780-d78000ff : Realtek Semiconductor Co., Ltd. RTL-8139
d780-d78000ff : eth0
fec0-fec00fff : reserved
fee0-fee00fff : reserved
- : reserved
[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev c4)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=
OOPS
Inc. VT82C598 [Apollo MVP3 AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [80] 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- 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 40) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=128K] 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- 00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable+ DSel=0 DScale=0 PME- 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326 (rev 0b) (prog-if 00 [VGA]) Subsystem: Palit Microsystems Inc. SiS6326 GUI Accelerator Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=64K] Capabilities: [40] Power Management version 1 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] AGP version 1.0 Status: RQ=1 SBA- 64bit- FW- Rate=x1,x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate= [7.6.] SCSI information (from /proc/scsi/scsi) no scsi adapters [7.7.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant): This is a very loaded server running lots of apache processes and sendmail. [X.] Other notes, patches, fixes, workarounds: -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
OOPS
- Latency: 32 (500ns min) Interrupt: pin A routed to IRQ 12 Region 0: Memory at d700 (32-bit, prefetchable) [size=8M] Region 1: Memory at d500 (32-bit, non-prefetchable) [size=64K] Region 2: I/O ports at 9000 [size=128] Expansion ROM at unassigned [disabled] [size=64K] Capabilities: [40] Power Management version 1 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] AGP version 1.0 Status: RQ=1 SBA- 64bit- FW- Rate=x1,x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate=none [7.6.] SCSI information (from /proc/scsi/scsi) no scsi adapters [7.7.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant): This is a very loaded server running lots of apache processes and sendmail. [X.] Other notes, patches, fixes, workarounds: -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel crash - reboot or hang
Hello, I NEED TO TRACE THIS!!! I had two crashes with 2.4.2 and 2.4.2-pre2 on my local SMTP/POP3/SAMBA/WWW server (once under some load and the second one - with 2.4.2-pre2 - while it was almost idle). The machine is an HP Netserver LHII without the standard raid card that comes with it (see bellow for dmesg output for a better description of hardware). I do not see any corruption nor any messages in logs. Should I use kdb or just remote logging would do the job? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ Linux version 2.4.3-pre2 (root@linux) (gcc version 2.95.2 19991024 (release)) #1 SMP Mon Mar 5 18:08:49 EET 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: eb0e @ 000f14f2 (reserved) BIOS-e820: 00e0 @ 0010 (usable) BIOS-e820: 0010 @ 00f0 (usable) BIOS-e820: 1f00 @ 0100 (usable) BIOS-e820: 1000 @ fec0 (reserved) BIOS-e820: 1000 @ fee0 (reserved) BIOS-e820: eb0e @ 14f2 (reserved) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. found SMP MP-table at 000fd8d0 hm, page 000fd000 reserved twice. hm, page 000fe000 reserved twice. hm, page 0009f000 reserved twice. hm, page 000a reserved twice. On node 0 totalpages: 131072 zone(0): 4096 pages. zone(1): 126976 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.1 Virtual Wire compatibility mode. OEM ID: HP Product ID: LH IIAPIC at: 0xFEE0 Processor #1 Pentium(tm) Pro APIC version 17 Floating point unit present. Machine Exception supported. 64 bit compare & exchange supported. Internal APIC present. SEP present. MTRR present. PGE present. MCA present. CMOV present. MMX present. Bootup CPU Processor #0 Pentium(tm) Pro APIC version 17 Floating point unit present. Machine Exception supported. 64 bit compare & exchange supported. Internal APIC present. SEP present. MTRR present. PGE present. MCA present. CMOV present. MMX present. Bus #0 is PCI Bus #1 is PCI Bus #2 is EISA I/O APIC #2 Version 17 at 0xFEC0. Int: type 3, pol 1, trig 1, bus 2, IRQ 00, APIC ID 2, APIC INT 00 Int: type 0, pol 0, trig 0, bus 2, IRQ 01, APIC ID 2, APIC INT 01 Int: type 0, pol 0, trig 0, bus 2, IRQ 00, APIC ID 2, APIC INT 02 Int: type 0, pol 0, trig 0, bus 2, IRQ 03, APIC ID 2, APIC INT 03 Int: type 0, pol 0, trig 0, bus 2, IRQ 04, APIC ID 2, APIC INT 04 Int: type 0, pol 0, trig 0, bus 2, IRQ 05, APIC ID 2, APIC INT 05 Int: type 0, pol 0, trig 0, bus 2, IRQ 06, APIC ID 2, APIC INT 06 Int: type 0, pol 0, trig 0, bus 2, IRQ 07, APIC ID 2, APIC INT 07 Int: type 0, pol 0, trig 0, bus 2, IRQ 08, APIC ID 2, APIC INT 08 Int: type 0, pol 0, trig 0, bus 2, IRQ 09, APIC ID 2, APIC INT 09 Int: type 0, pol 0, trig 0, bus 2, IRQ 0a, APIC ID 2, APIC INT 0a Int: type 0, pol 0, trig 0, bus 2, IRQ 0b, APIC ID 2, APIC INT 0b Int: type 0, pol 0, trig 0, bus 2, IRQ 0c, APIC ID 2, APIC INT 0c Int: type 0, pol 0, trig 0, bus 2, IRQ 0d, APIC ID 2, APIC INT 0d Int: type 0, pol 0, trig 0, bus 2, IRQ 0e, APIC ID 2, APIC INT 0e Int: type 0, pol 0, trig 0, bus 2, IRQ 0f, APIC ID 2, APIC INT 0f Lint: type 3, pol 1, trig 1, bus 2, IRQ 00, APIC ID ff, APIC LINT 00 Lint: type 1, pol 1, trig 1, bus 0, IRQ 00, APIC ID ff, APIC LINT 01 Processors: 2 mapped APIC to e000 (fee0) mapped IOAPIC to d000 (fec0) Kernel command line: auto BOOT_IMAGE=Linux ro root=802 Initializing CPU#0 Detected 300.694 MHz processor. Console: colour VGA+ 80x30 Calibrating delay loop... 599.65 BogoMIPS Memory: 512764k/524288k available (1348k kernel code, 11136k reserved, 522k data, 208k init, 0k highmem) Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes) Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) CPU: Before vendor init, caps: 0080fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0080fbff CPU: After generic, caps: 0080fbff CPU: Common caps: 0080fbff Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel CPU: Before vendor init, caps: 0080fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check reporting enable
Kernel crash - reboot or hang
Hello, I NEED TO TRACE THIS!!! I had two crashes with 2.4.2 and 2.4.2-pre2 on my local SMTP/POP3/SAMBA/WWW server (once under some load and the second one - with 2.4.2-pre2 - while it was almost idle). The machine is an HP Netserver LHII without the standard raid card that comes with it (see bellow for dmesg output for a better description of hardware). I do not see any corruption nor any messages in logs. Should I use kdb or just remote logging would do the job? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ Linux version 2.4.3-pre2 (root@linux) (gcc version 2.95.2 19991024 (release)) #1 SMP Mon Mar 5 18:08:49 EET 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: eb0e @ 000f14f2 (reserved) BIOS-e820: 00e0 @ 0010 (usable) BIOS-e820: 0010 @ 00f0 (usable) BIOS-e820: 1f00 @ 0100 (usable) BIOS-e820: 1000 @ fec0 (reserved) BIOS-e820: 1000 @ fee0 (reserved) BIOS-e820: eb0e @ 14f2 (reserved) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. found SMP MP-table at 000fd8d0 hm, page 000fd000 reserved twice. hm, page 000fe000 reserved twice. hm, page 0009f000 reserved twice. hm, page 000a reserved twice. On node 0 totalpages: 131072 zone(0): 4096 pages. zone(1): 126976 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.1 Virtual Wire compatibility mode. OEM ID: HP Product ID: LH IIAPIC at: 0xFEE0 Processor #1 Pentium(tm) Pro APIC version 17 Floating point unit present. Machine Exception supported. 64 bit compare exchange supported. Internal APIC present. SEP present. MTRR present. PGE present. MCA present. CMOV present. MMX present. Bootup CPU Processor #0 Pentium(tm) Pro APIC version 17 Floating point unit present. Machine Exception supported. 64 bit compare exchange supported. Internal APIC present. SEP present. MTRR present. PGE present. MCA present. CMOV present. MMX present. Bus #0 is PCI Bus #1 is PCI Bus #2 is EISA I/O APIC #2 Version 17 at 0xFEC0. Int: type 3, pol 1, trig 1, bus 2, IRQ 00, APIC ID 2, APIC INT 00 Int: type 0, pol 0, trig 0, bus 2, IRQ 01, APIC ID 2, APIC INT 01 Int: type 0, pol 0, trig 0, bus 2, IRQ 00, APIC ID 2, APIC INT 02 Int: type 0, pol 0, trig 0, bus 2, IRQ 03, APIC ID 2, APIC INT 03 Int: type 0, pol 0, trig 0, bus 2, IRQ 04, APIC ID 2, APIC INT 04 Int: type 0, pol 0, trig 0, bus 2, IRQ 05, APIC ID 2, APIC INT 05 Int: type 0, pol 0, trig 0, bus 2, IRQ 06, APIC ID 2, APIC INT 06 Int: type 0, pol 0, trig 0, bus 2, IRQ 07, APIC ID 2, APIC INT 07 Int: type 0, pol 0, trig 0, bus 2, IRQ 08, APIC ID 2, APIC INT 08 Int: type 0, pol 0, trig 0, bus 2, IRQ 09, APIC ID 2, APIC INT 09 Int: type 0, pol 0, trig 0, bus 2, IRQ 0a, APIC ID 2, APIC INT 0a Int: type 0, pol 0, trig 0, bus 2, IRQ 0b, APIC ID 2, APIC INT 0b Int: type 0, pol 0, trig 0, bus 2, IRQ 0c, APIC ID 2, APIC INT 0c Int: type 0, pol 0, trig 0, bus 2, IRQ 0d, APIC ID 2, APIC INT 0d Int: type 0, pol 0, trig 0, bus 2, IRQ 0e, APIC ID 2, APIC INT 0e Int: type 0, pol 0, trig 0, bus 2, IRQ 0f, APIC ID 2, APIC INT 0f Lint: type 3, pol 1, trig 1, bus 2, IRQ 00, APIC ID ff, APIC LINT 00 Lint: type 1, pol 1, trig 1, bus 0, IRQ 00, APIC ID ff, APIC LINT 01 Processors: 2 mapped APIC to e000 (fee0) mapped IOAPIC to d000 (fec0) Kernel command line: auto BOOT_IMAGE=Linux ro root=802 Initializing CPU#0 Detected 300.694 MHz processor. Console: colour VGA+ 80x30 Calibrating delay loop... 599.65 BogoMIPS Memory: 512764k/524288k available (1348k kernel code, 11136k reserved, 522k data, 208k init, 0k highmem) Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes) Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) CPU: Before vendor init, caps: 0080fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0080fbff CPU: After generic, caps: 0080fbff CPU: Common caps: 0080fbff Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel CPU: Before vendor init, caps: 0080fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check reporting enabled on CPU#0
Re: LILO error with 2.4.3-pre1...
On Sun, Mar 04, 2001 at 12:39:32PM +1100, Keith Owens wrote: > On Sat, 03 Mar 2001 19:19:28 -0600, > "Steven J. Hill" <[EMAIL PROTECTED]> wrote: > >I have no idea why the 1023 limit is coming up considering 2.4.2 and > >LILO were working just fine together and I have a newer BIOS that has > >not problems detecting the driver properly. Go ahead, call me idiot :). > > OK, you're an idiot :). It only worked before because all the files > that lilo used just happened to be below cylinder 1024. Your partition > goes past cyl 1024 and your new kernel is using space above 1024. Find > a version of lilo that can cope with cyl >= 1024 (is there one?) or > move the kernel below cyl 1024. You might need to repartition your > disk to get / all below 1024. Call me idiot too but please explain what is wrong here: # cat /etc/lilo.conf boot = /dev/hda timeout = 150 vga = 4 ramdisk = 0 lba32 append = "hdc=scsi" prompt image = /boot/vmlinuz-2.4.2 root = /dev/hda2 read-only label = Linux other = /dev/hda3 label = win table = /dev/hda # fdisk -l /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 1650 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hda1 117136521 82 Linux swap /dev/hda218 1165 9221310 83 Linux /dev/hda3 * 1166 1650 3895762+ c Win95 FAT32 (LBA) root@taz:~# lilo -v LILO version 21.7, Copyright (C) 1992-1998 Werner Almesberger Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof Development beyond version 21 Copyright (C) 1999-2001 John Coffman Released 24-Feb-2001 and compiled at 18:31:02 on Mar 3 2001. Reading boot sector from /dev/hda Merging with /boot/boot.b Boot image: /boot/vmlinuz-2.4.2 Added Linux * Boot other: /dev/hda3, on /dev/hda, loader /boot/chain.b Device 0x0300: Invalid partition table, 3rd entry 3D address: 63/254/141 (2281229) Linear address: 1/0/1165 (18715725) Mar 2 20:26:29 taz kernel: hda: IBM-DJNA-371350, ATA DISK drive Mar 2 20:26:29 taz kernel: hda: 26520480 sectors (13578 MB) w/1966KiB Cache, CHS=1650/255/63 Is anybody able to explain the error? That partition contains a valid VFAT partition with win98se installed on it (and it works fine, ofc if I remove lilo from MBR). -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: LILO error with 2.4.3-pre1...
On Sun, Mar 04, 2001 at 12:39:32PM +1100, Keith Owens wrote: On Sat, 03 Mar 2001 19:19:28 -0600, "Steven J. Hill" [EMAIL PROTECTED] wrote: I have no idea why the 1023 limit is coming up considering 2.4.2 and LILO were working just fine together and I have a newer BIOS that has not problems detecting the driver properly. Go ahead, call me idiot :). OK, you're an idiot :). It only worked before because all the files that lilo used just happened to be below cylinder 1024. Your partition goes past cyl 1024 and your new kernel is using space above 1024. Find a version of lilo that can cope with cyl = 1024 (is there one?) or move the kernel below cyl 1024. You might need to repartition your disk to get / all below 1024. Call me idiot too but please explain what is wrong here: # cat /etc/lilo.conf boot = /dev/hda timeout = 150 vga = 4 ramdisk = 0 lba32 append = "hdc=scsi" prompt image = /boot/vmlinuz-2.4.2 root = /dev/hda2 read-only label = Linux other = /dev/hda3 label = win table = /dev/hda # fdisk -l /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 1650 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hda1 117136521 82 Linux swap /dev/hda218 1165 9221310 83 Linux /dev/hda3 * 1166 1650 3895762+ c Win95 FAT32 (LBA) root@taz:~# lilo -v LILO version 21.7, Copyright (C) 1992-1998 Werner Almesberger Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof Development beyond version 21 Copyright (C) 1999-2001 John Coffman Released 24-Feb-2001 and compiled at 18:31:02 on Mar 3 2001. Reading boot sector from /dev/hda Merging with /boot/boot.b Boot image: /boot/vmlinuz-2.4.2 Added Linux * Boot other: /dev/hda3, on /dev/hda, loader /boot/chain.b Device 0x0300: Invalid partition table, 3rd entry 3D address: 63/254/141 (2281229) Linear address: 1/0/1165 (18715725) Mar 2 20:26:29 taz kernel: hda: IBM-DJNA-371350, ATA DISK drive Mar 2 20:26:29 taz kernel: hda: 26520480 sectors (13578 MB) w/1966KiB Cache, CHS=1650/255/63 Is anybody able to explain the error? That partition contains a valid VFAT partition with win98se installed on it (and it works fine, ofc if I remove lilo from MBR). -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel 2.4.0 loop device still hangs
On Sun, Jan 28, 2001 at 03:43:00AM +0100, Jens Axboe wrote: > > It should be safe. Thanks for the feedback. The patch works fine here too, but I have not tested it very hard ... just normal read/write small/big files into it. It looks fine here. Any thoughts to integrate it into 2.4.1? What's Linus opinion? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel 2.4.0 loop device still hangs
On Sun, Jan 28, 2001 at 03:43:00AM +0100, Jens Axboe wrote: It should be safe. Thanks for the feedback. The patch works fine here too, but I have not tested it very hard ... just normal read/write small/big files into it. It looks fine here. Any thoughts to integrate it into 2.4.1? What's Linus opinion? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: do NOT compile 2.2.18 with egcs-1.1.2
On Thu, Dec 14, 2000 at 10:23:14AM +, Alan Cox wrote: > > I just want to let other know that kernel 2.2.18 does not work properly (*) > > on my box if I compile it with egcs-2.91.66 19990314/Linux (egcs-1.1.2 > > release). Instead gcc-2.7.2.3 works ok. > > > > (*) the network driver PCI NE2000 does not work with all three cards. It > > just sees them but they do not work. > > I don't believe that is likely to be the reason. The driver has not changed > since 2.2.15 if not earlier, and it still seems to work with the cards I have > here (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Then I don't think that I can explain why it works with gcc-2.7.2.3. My particular setup is: - 3 PCI NE2000 cards and 1 ISA NE2000 card. The isa card worked always but from the PCI cards only one worked (I just ifconfig ethX up; tcpdump -i ethX -nlqt and I see no packets there, I also see no interrupts from that cards too, so this may be related to pci code). Anyway, as I said before, with gcc-2.7.2.3 it works fine. .. ah, and something else: first I had a EtherExpress Pro 10/100 card which behaved in the same way but I thought I have a bus-mastering problem with PCI cards so I replaced it. -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
do NOT compile 2.2.18 with egcs-1.1.2
Hello, I just want to let other know that kernel 2.2.18 does not work properly (*) on my box if I compile it with egcs-2.91.66 19990314/Linux (egcs-1.1.2 release). Instead gcc-2.7.2.3 works ok. (*) the network driver PCI NE2000 does not work with all three cards. It just sees them but they do not work. -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: do NOT compile 2.2.18 with egcs-1.1.2
On Thu, Dec 14, 2000 at 10:23:14AM +, Alan Cox wrote: I just want to let other know that kernel 2.2.18 does not work properly (*) on my box if I compile it with egcs-2.91.66 19990314/Linux (egcs-1.1.2 release). Instead gcc-2.7.2.3 works ok. (*) the network driver PCI NE2000 does not work with all three cards. It just sees them but they do not work. I don't believe that is likely to be the reason. The driver has not changed since 2.2.15 if not earlier, and it still seems to work with the cards I have here (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Then I don't think that I can explain why it works with gcc-2.7.2.3. My particular setup is: - 3 PCI NE2000 cards and 1 ISA NE2000 card. The isa card worked always but from the PCI cards only one worked (I just ifconfig ethX up; tcpdump -i ethX -nlqt and I see no packets there, I also see no interrupts from that cards too, so this may be related to pci code). Anyway, as I said before, with gcc-2.7.2.3 it works fine. .. ah, and something else: first I had a EtherExpress Pro 10/100 card which behaved in the same way but I thought I have a bus-mastering problem with PCI cards so I replaced it. -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: corruption on my ext2fs with 2.4.0-test10
OK, problem found.
Something is broken (I've tested on a new 2.4.0-test12-pre3). Look here:
If I run strace through the perl script I get something like:
root@invasion:/usr/src/archives/perl-5.6.0/t# strace ./perl op/lfs.t
...
open("big", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40015000
_llseek(3, 50, [50], SEEK_SET) = 0
write(3, "big", 3) = 3
close(3)= 0
munmap(0x40015000, 4096)= 0
stat("big", 0xb980) = -1 EOVERFLOW (Value too large for defined
data type)
...
I believe that _llseek() call should return EINVAL. Right?
On Sun, Dec 03, 2000 at 02:46:06PM +0200, Mircea Damian wrote:
>
> Sorry that I have to follow my self but I forgot to say that e2fsck is
> happy with it:
>
> root@invasion:~# e2fsck -C 0 -f /dev/hda2
> e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> /dev/hda2: 43056/1548288 files (1.7% non-contiguous), 237689/1548264 blocks
>
> ... file-utils like ls, rm say:
> root@invasion:/usr/src/perl-5.6.0/t# ls -sail
> /bin/ls: big: Value too large for defined data type
> total 8
> 10973604 drwx-- 2 504 1001 4096 Dec 3 13:43 ./
> 13549794 drwxr-xr-x 3 504 1001 4096 Dec 3 13:43 ../
>
> root@invasion:/usr/src/perl-5.6.0/t# rm big
> rm: cannot remove `big': Value too large for defined data type
>
> I can not keep this machine down (my /-fs is read-only right now just to be
> sure that nothing changes) for too much time.
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: corruption on my ext2fs with 2.4.0-test10
Sorry that I have to follow my self but I forgot to say that e2fsck is happy with it: root@invasion:~# e2fsck -C 0 -f /dev/hda2 e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/hda2: 43056/1548288 files (1.7% non-contiguous), 237689/1548264 blocks ... file-utils like ls, rm say: root@invasion:/usr/src/perl-5.6.0/t# ls -sail /bin/ls: big: Value too large for defined data type total 8 10973604 drwx-- 2 504 1001 4096 Dec 3 13:43 ./ 13549794 drwxr-xr-x 3 504 1001 4096 Dec 3 13:43 ../ root@invasion:/usr/src/perl-5.6.0/t# rm big rm: cannot remove `big': Value too large for defined data type I can not keep this machine down (my /-fs is read-only right now just to be sure that nothing changes) for too much time. On Sun, Dec 03, 2000 at 02:24:33PM +0200, Mircea Damian wrote: > > Hello people, > > Since I've seen that there are some problems with corruption on ext2fs I > thought that it would be a good idea to report my problem too. > > I have a 2.4.0-test10 patched with reiserfs (but I do not use it - it was > just in my plan to create a partition sometime; so I think that it does not > matter to much). Kernel compiled with egcs-1.1.2: > > root@invasion:~# gcc -v > Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs > gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) > > The problem is that I tried to build perl-5.6.0 and some of my tests were > failing. First I thought that it is a problem with shared libraries but I > was wrong, in the test directory I have a file named "big" which has 5Gb > (almost): > > root@invasion:/# debugfs /dev/hda2 > debugfs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 > debugfs: cd /usr/src/perl-5.6.0/t/ > debugfs: ls > 1097360 (12) . 1354979 (184) .. 1097503 (3900) big > debugfs: ls -l > 1097360 40700504 10014096 3-Dec-2000 13:43 . > 1354979 40755504 10014096 3-Dec-2000 13:43 .. > 1097503 100644 0 0 53 3-Dec-2000 10:00 big > > Ofcourse this is wrong because: > debugfs: q > root@invasion:/# df > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/hda2 5999072756772 4932648 13% / > > > I've checked my syslog and messages for ext2 warnings but I found nothing > unusual. > > The system is UP and dmesg output is attached. > > OTOH does anyone know how to silent messages like: > NAT: 0 dropping untracked packet c7d205c0 1 192.129.3.151 -> 224.0.0.1 > NAT: 0 dropping untracked packet c7d129a0 1 192.129.3.151 -> 224.0.0.1 > They are annoying and after some time they just fill up my dmesg output > (all dropped packets are multicast just like the two above). > > > > uto BOOT_IMAGE=Linux ro root=302 console=ttyS0,38400 > Initializing CPU#0 > Detected 400.914 MHz processor. > Console: colour VGA+ 80x30 > Calibrating delay loop... 799.54 BogoMIPS > Memory: 126788k/131072k available (1207k kernel code, 3896k reserved, 85k data, 196k >init, 0k highmem) > Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) > Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes) > Page-cache hash table entries: 32768 (order: 5, 131072 bytes) > Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) > CPU: Before vendor init, caps: 0183fbff , vendor = 0 > CPU: L1 I cache: 16K, L1 D cache: 16K > CPU: L2 cache: 512K > Intel machine check architecture supported. > Intel machine check reporting enabled on CPU#0. > CPU: After vendor init, caps: 0183fbff > CPU: After generic, caps: 0183fbff > CPU: Common caps: 0183fbff > CPU: Intel Pentium II (Deschutes) stepping 02 > Checking 'hlt' instruction... OK. > POSIX conformance testing by UNIFIX > enabled ExtINT on CPU#0 > ESR value before enabling vector: 0004 > ESR value after enabling vector: > ENABLING IO-APIC IRQs > ...changing IO-APIC physical APIC ID to 2 ... ok. > Synchronizing Arb IDs. > init IO_APIC IRQs > IO-APIC (apicid-pin) 2-0, 2-16, 2-20, 2-21, 2-22, 2-23 not connected. > ..TIMER: vector=49 pin1=2 pin2=0 > activating NMI Watchdog ... done. > number of MP IRQ sources: 20. > number of IO-APIC #2 registers: 24. > testing the IO APIC... > > IO APIC #2.. > register #00: 0
corruption on my ext2fs with 2.4.0-test10
Hello people, Since I've seen that there are some problems with corruption on ext2fs I thought that it would be a good idea to report my problem too. I have a 2.4.0-test10 patched with reiserfs (but I do not use it - it was just in my plan to create a partition sometime; so I think that it does not matter to much). Kernel compiled with egcs-1.1.2: root@invasion:~# gcc -v Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) The problem is that I tried to build perl-5.6.0 and some of my tests were failing. First I thought that it is a problem with shared libraries but I was wrong, in the test directory I have a file named "big" which has 5Gb (almost): root@invasion:/# debugfs /dev/hda2 debugfs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 debugfs: cd /usr/src/perl-5.6.0/t/ debugfs: ls 1097360 (12) . 1354979 (184) .. 1097503 (3900) big debugfs: ls -l 1097360 40700504 10014096 3-Dec-2000 13:43 . 1354979 40755504 10014096 3-Dec-2000 13:43 .. 1097503 100644 0 0 53 3-Dec-2000 10:00 big Ofcourse this is wrong because: debugfs: q root@invasion:/# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda2 5999072756772 4932648 13% / I've checked my syslog and messages for ext2 warnings but I found nothing unusual. The system is UP and dmesg output is attached. OTOH does anyone know how to silent messages like: NAT: 0 dropping untracked packet c7d205c0 1 192.129.3.151 -> 224.0.0.1 NAT: 0 dropping untracked packet c7d129a0 1 192.129.3.151 -> 224.0.0.1 They are annoying and after some time they just fill up my dmesg output (all dropped packets are multicast just like the two above). -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ uto BOOT_IMAGE=Linux ro root=302 console=ttyS0,38400 Initializing CPU#0 Detected 400.914 MHz processor. Console: colour VGA+ 80x30 Calibrating delay loop... 799.54 BogoMIPS Memory: 126788k/131072k available (1207k kernel code, 3896k reserved, 85k data, 196k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) CPU: Before vendor init, caps: 0183fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0183fbff CPU: After generic, caps: 0183fbff CPU: Common caps: 0183fbff CPU: Intel Pentium II (Deschutes) stepping 02 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: 0004 ESR value after enabling vector: ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. Synchronizing Arb IDs. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 activating NMI Watchdog ... done. number of MP IRQ sources: 20. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00170011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 001 01 000 0 01139 02 001 01 000 0 01131 03 001 01 000 0 01141 04 001 01 000 0 01149 05 001 01 000 0 01151 06 001 01 000 0 01159 07 001 01 000 0 01161 08 001 01 000 0 01169 09 001 01 000 0 01171 0a 001 01 000 0 01179 0b 001 01 000 0 01181 0c 001 01 000 0 01189 0d 000 00 100 0 00000 0e 001 01 000 0 01191 0f 001 01 000 0 01199 10 000 00 100 0 00000 11 001 01 110 1 011A1 12 001 01 110 1 011A9 13 001 01 110 1 011B1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 -> 2 IRQ1 -> 1 IRQ3 -> 3 IRQ4 -> 4 IRQ5 -> 5 IRQ
corruption on my ext2fs with 2.4.0-test10
Hello people, Since I've seen that there are some problems with corruption on ext2fs I thought that it would be a good idea to report my problem too. I have a 2.4.0-test10 patched with reiserfs (but I do not use it - it was just in my plan to create a partition sometime; so I think that it does not matter to much). Kernel compiled with egcs-1.1.2: root@invasion:~# gcc -v Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) The problem is that I tried to build perl-5.6.0 and some of my tests were failing. First I thought that it is a problem with shared libraries but I was wrong, in the test directory I have a file named "big" which has 5Gb (almost): root@invasion:/# debugfs /dev/hda2 debugfs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 debugfs: cd /usr/src/perl-5.6.0/t/ debugfs: ls 1097360 (12) . 1354979 (184) .. 1097503 (3900) big debugfs: ls -l 1097360 40700504 10014096 3-Dec-2000 13:43 . 1354979 40755504 10014096 3-Dec-2000 13:43 .. 1097503 100644 0 0 53 3-Dec-2000 10:00 big Ofcourse this is wrong because: debugfs: q root@invasion:/# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda2 5999072756772 4932648 13% / I've checked my syslog and messages for ext2 warnings but I found nothing unusual. The system is UP and dmesg output is attached. OTOH does anyone know how to silent messages like: NAT: 0 dropping untracked packet c7d205c0 1 192.129.3.151 - 224.0.0.1 NAT: 0 dropping untracked packet c7d129a0 1 192.129.3.151 - 224.0.0.1 They are annoying and after some time they just fill up my dmesg output (all dropped packets are multicast just like the two above). -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ uto BOOT_IMAGE=Linux ro root=302 console=ttyS0,38400 Initializing CPU#0 Detected 400.914 MHz processor. Console: colour VGA+ 80x30 Calibrating delay loop... 799.54 BogoMIPS Memory: 126788k/131072k available (1207k kernel code, 3896k reserved, 85k data, 196k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) CPU: Before vendor init, caps: 0183fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0183fbff CPU: After generic, caps: 0183fbff CPU: Common caps: 0183fbff CPU: Intel Pentium II (Deschutes) stepping 02 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: 0004 ESR value after enabling vector: ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. Synchronizing Arb IDs. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 activating NMI Watchdog ... done. number of MP IRQ sources: 20. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00170011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 001 01 000 0 01139 02 001 01 000 0 01131 03 001 01 000 0 01141 04 001 01 000 0 01149 05 001 01 000 0 01151 06 001 01 000 0 01159 07 001 01 000 0 01161 08 001 01 000 0 01169 09 001 01 000 0 01171 0a 001 01 000 0 01179 0b 001 01 000 0 01181 0c 001 01 000 0 01189 0d 000 00 100 0 00000 0e 001 01 000 0 01191 0f 001 01 000 0 01199 10 000 00 100 0 00000 11 001 01 110 1 011A1 12 001 01 110 1 011A9 13 001 01 110 1 011B1 14 000 00 100 0 00000 15 000 00 100 0 00000 16 000 00 100 0 00000 17 000 00 100 0 00000 IRQ to pin mappings: IRQ0 - 2 IRQ1 - 1 IRQ3 - 3 IRQ4 - 4 IRQ5 - 5 IRQ6 - 6 IRQ7 - 7 IRQ8 - 8 IRQ9
Re: corruption on my ext2fs with 2.4.0-test10
Sorry that I have to follow my self but I forgot to say that e2fsck is happy with it: root@invasion:~# e2fsck -C 0 -f /dev/hda2 e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/hda2: 43056/1548288 files (1.7% non-contiguous), 237689/1548264 blocks ... file-utils like ls, rm say: root@invasion:/usr/src/perl-5.6.0/t# ls -sail /bin/ls: big: Value too large for defined data type total 8 10973604 drwx-- 2 504 1001 4096 Dec 3 13:43 ./ 13549794 drwxr-xr-x 3 504 1001 4096 Dec 3 13:43 ../ root@invasion:/usr/src/perl-5.6.0/t# rm big rm: cannot remove `big': Value too large for defined data type I can not keep this machine down (my /-fs is read-only right now just to be sure that nothing changes) for too much time. On Sun, Dec 03, 2000 at 02:24:33PM +0200, Mircea Damian wrote: Hello people, Since I've seen that there are some problems with corruption on ext2fs I thought that it would be a good idea to report my problem too. I have a 2.4.0-test10 patched with reiserfs (but I do not use it - it was just in my plan to create a partition sometime; so I think that it does not matter to much). Kernel compiled with egcs-1.1.2: root@invasion:~# gcc -v Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) The problem is that I tried to build perl-5.6.0 and some of my tests were failing. First I thought that it is a problem with shared libraries but I was wrong, in the test directory I have a file named "big" which has 5Gb (almost): root@invasion:/# debugfs /dev/hda2 debugfs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 debugfs: cd /usr/src/perl-5.6.0/t/ debugfs: ls 1097360 (12) . 1354979 (184) .. 1097503 (3900) big debugfs: ls -l 1097360 40700504 10014096 3-Dec-2000 13:43 . 1354979 40755504 10014096 3-Dec-2000 13:43 .. 1097503 100644 0 0 53 3-Dec-2000 10:00 big Ofcourse this is wrong because: debugfs: q root@invasion:/# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda2 5999072756772 4932648 13% / I've checked my syslog and messages for ext2 warnings but I found nothing unusual. The system is UP and dmesg output is attached. OTOH does anyone know how to silent messages like: NAT: 0 dropping untracked packet c7d205c0 1 192.129.3.151 - 224.0.0.1 NAT: 0 dropping untracked packet c7d129a0 1 192.129.3.151 - 224.0.0.1 They are annoying and after some time they just fill up my dmesg output (all dropped packets are multicast just like the two above). uto BOOT_IMAGE=Linux ro root=302 console=ttyS0,38400 Initializing CPU#0 Detected 400.914 MHz processor. Console: colour VGA+ 80x30 Calibrating delay loop... 799.54 BogoMIPS Memory: 126788k/131072k available (1207k kernel code, 3896k reserved, 85k data, 196k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) CPU: Before vendor init, caps: 0183fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0183fbff CPU: After generic, caps: 0183fbff CPU: Common caps: 0183fbff CPU: Intel Pentium II (Deschutes) stepping 02 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: 0004 ESR value after enabling vector: ENABLING IO-APIC IRQs ...changing IO-APIC physical APIC ID to 2 ... ok. Synchronizing Arb IDs. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=49 pin1=2 pin2=0 activating NMI Watchdog ... done. number of MP IRQ sources: 20. number of IO-APIC #2 registers: 24. testing the IO APIC... IO APIC #2.. register #00: 0200 ...: physical APIC id: 02 register #01: 00170011 ... : max redirection entries: 0017 ... : IO APIC version: 0011 register #02: ... : arbitration: 00 IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 100 0 00000 01 001
Re: corruption on my ext2fs with 2.4.0-test10
OK, problem found.
Something is broken (I've tested on a new 2.4.0-test12-pre3). Look here:
If I run strace through the perl script I get something like:
root@invasion:/usr/src/archives/perl-5.6.0/t# strace ./perl op/lfs.t
...
open("big", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40015000
_llseek(3, 50, [50], SEEK_SET) = 0
write(3, "big", 3) = 3
close(3)= 0
munmap(0x40015000, 4096)= 0
stat("big", 0xb980) = -1 EOVERFLOW (Value too large for defined
data type)
...
I believe that _llseek() call should return EINVAL. Right?
On Sun, Dec 03, 2000 at 02:46:06PM +0200, Mircea Damian wrote:
Sorry that I have to follow my self but I forgot to say that e2fsck is
happy with it:
root@invasion:~# e2fsck -C 0 -f /dev/hda2
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda2: 43056/1548288 files (1.7% non-contiguous), 237689/1548264 blocks
... file-utils like ls, rm say:
root@invasion:/usr/src/perl-5.6.0/t# ls -sail
/bin/ls: big: Value too large for defined data type
total 8
10973604 drwx-- 2 504 1001 4096 Dec 3 13:43 ./
13549794 drwxr-xr-x 3 504 1001 4096 Dec 3 13:43 ../
root@invasion:/usr/src/perl-5.6.0/t# rm big
rm: cannot remove `big': Value too large for defined data type
I can not keep this machine down (my /-fs is read-only right now just to be
sure that nothing changes) for too much time.
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
ppp.txt
Hello, I just want to say that the file 'Documentation/networking/ppp.txt' (as it is mentioned in Configure.help at CONFIG_PPP option) does not exists. -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ppp.txt
Hello, I just want to say that the file 'Documentation/networking/ppp.txt' (as it is mentioned in Configure.help at CONFIG_PPP option) does not exists. -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel OOPS on boot
On Thu, Oct 26, 2000 at 10:20:45AM -0400, Brian Gerst wrote: > Mircea Damian wrote: > > > > Hello, > > > > I'm unable to boot kernel 2.4.0-test10-pre5 on a: > > Upgrade GCC to 2.91.66 (aka egcs-1.1.2) Ok. I can do that, but there is nowhere written that I should do that. If I remember right gcc-2.7.2.3 was the preferred compiler for all kernels. Am I wrong? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Kernel OOPS on boot
Hello, I'm unable to boot kernel 2.4.0-test10-pre5 on a: root@cyrix:/usr/src/linux/arch/i386/mm# cat /proc/cpuinfo processor : 0 vendor_id : CyrixInstead cpu family : 6 model : 2 model name : 6x86MX 2.5x Core/Bus Clock stepping: 7 cpu MHz : 166.452871 fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: no coma_bug: yes fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr cx8 mtrr pge cmov mmx bogomips: 331.78 2.4.0-test6-pre5 is the current version that works fine on this computer. Here is the ksymoops dump (the serial console was my salvation this time :-)). ksymoops 2.3.4 on i686 2.4.0-test6. Options used -v /usr/src/linux/vmlinux (specified) -K (specified) -L (specified) -O (specified) -m /usr/src/linux/System.map (default) Unable to handle kernel paging request at virtual address c000 c0112913 *pde = 1063 Oops: 0003 CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010206 eax: c000 ebx: 1000 ecx: 0001 edx: 0001 esi: 0163 edi: 0050 ebp: 0004 esp: c0253fbc ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c0253000) Stack: c025af9f c000 04f6 c025b198 69727943 0009e200 c0105000 0008e000 0051 0005 2000 0264 c025495e 69727943 c0285e24 c0100193 Call Trace: [] [] Code: 88 10 31 c9 89 c8 c3 89 f6 56 53 bb 00 40 25 c0 81 fb 00 30 >>EIP; c0112913<= Trace; c0105000 Trace; c0100193 Code; c0112913 <_EIP>: Code; c0112913<= 0: 88 10 movb %dl,(%eax) <= Code; c0112915 2: 31 c9 xorl %ecx,%ecx Code; c0112917 4: 89 c8 movl %ecx,%eax Code; c0112919 6: c3ret Code; c011291a 7: 89 f6 movl %esi,%esi Code; c011291c 9: 56pushl %esi Code; c011291d a: 53pushl %ebx Code; c011291e b: bb 00 40 25 c0movl $0xc0254000,%ebx Code; c0112923 10: 81 fb 00 30 00 00 cmpl $0x3000,%ebx Kernel panic: Attempted to kill the idle task! And here is the broken routine: 03f4 : 3f4: 8b 44 24 04 movl 0x4(%esp,1),%eax 3f8: b9 01 00 00 00 movl $0x1,%ecx 3fd: 8a 10 movb (%eax),%dl 3ff: 88 10 movb %dl,(%eax) 401: 31 c9 xorl %ecx,%ecx 403: 89 c8 movl %ecx,%eax 405: c3 ret 406: 89 f6 movl %esi,%esi It works fine with 2.2.14 too if that matters. Thank you for your patience, -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel OOPS on boot
On Thu, Oct 26, 2000 at 10:20:45AM -0400, Brian Gerst wrote: Mircea Damian wrote: Hello, I'm unable to boot kernel 2.4.0-test10-pre5 on a: Upgrade GCC to 2.91.66 (aka egcs-1.1.2) Ok. I can do that, but there is nowhere written that I should do that. If I remember right gcc-2.7.2.3 was the preferred compiler for all kernels. Am I wrong? -- Mircea Damian E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED] WebPage: http://taz.mania.k.ro/~dmircea/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
