odd slab memory usage in latest git
PCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_IDEPCI_PCIBUS_ORDER=y CONFIG_BLK_DEV_GENERIC=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDE_ARCH_OBSOLETE_INIT=y CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_FC_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_MEGARAID_LEGACY=y CONFIG_NETDEVICES=y CONFIG_DUMMY=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_NETDEV_1000=y CONFIG_ACENIC=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=y CONFIG_INPUT_EVDEV=y CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MISC=y CONFIG_INPUT_PCSPKR=y CONFIG_INPUT_UINPUT=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_CT82C710=y CONFIG_SERIO_PCIPS2=y CONFIG_SERIO_LIBPS2=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_INTEL=y CONFIG_RTC=y CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=y CONFIG_I2C_ALGOBIT=y CONFIG_I2C_ALGOPCF=y CONFIG_I2C_PIIX4=y CONFIG_POWER_SUPPLY=y CONFIG_HWMON=y CONFIG_HWMON_VID=y CONFIG_SENSORS_ADM1021=y CONFIG_SENSORS_GL518SM=y CONFIG_SENSORS_IT87=y CONFIG_SENSORS_LM75=y CONFIG_SENSORS_LM83=y CONFIG_SENSORS_LM90=y CONFIG_SENSORS_VIA686A=y CONFIG_SENSORS_W83781D=y CONFIG_SSB_POSSIBLE=y CONFIG_VIDEO_OUTPUT_CONTROL=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_HID_SUPPORT=y CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_VIRTUALIZATION=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_FS_POSIX_ACL=y CONFIG_DNOTIFY=y CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=y CONFIG_UDF_NLS=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_NETWORK_FILESYSTEMS=y CONFIG_SMB_FS=y CONFIG_CIFS=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="cp437" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_INSTRUMENTATION=y CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_MAGIC_SYSRQ=y CONFIG_DEBUG_KERNEL=y CONFIG_DETECT_SOFTLOCKUP=y CONFIG_SCHED_DEBUG=y CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_MUTEXES=y CONFIG_DEBUG_SPINLOCK_SLEEP=y CONFIG_DEBUG_BUGVERBOSE=y CONFIG_FORCED_INLINING=y CONFIG_EARLY_PRINTK=y CONFIG_DEBUG_STACKOVERFLOW=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_DOUBLEFAULT=y CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_DEFLATE=y CONFIG_CRYPTO_HW=y CONFIG_BITREVERSE=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y -- Burton Windle [EMAIL PROTECTED] -- 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/
odd slab memory usage in latest git
CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_IDEPCI_PCIBUS_ORDER=y CONFIG_BLK_DEV_GENERIC=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDE_ARCH_OBSOLETE_INIT=y CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_FC_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_MEGARAID_LEGACY=y CONFIG_NETDEVICES=y CONFIG_DUMMY=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_NETDEV_1000=y CONFIG_ACENIC=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=y CONFIG_INPUT_EVDEV=y CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MISC=y CONFIG_INPUT_PCSPKR=y CONFIG_INPUT_UINPUT=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_CT82C710=y CONFIG_SERIO_PCIPS2=y CONFIG_SERIO_LIBPS2=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_INTEL=y CONFIG_RTC=y CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=y CONFIG_I2C_ALGOBIT=y CONFIG_I2C_ALGOPCF=y CONFIG_I2C_PIIX4=y CONFIG_POWER_SUPPLY=y CONFIG_HWMON=y CONFIG_HWMON_VID=y CONFIG_SENSORS_ADM1021=y CONFIG_SENSORS_GL518SM=y CONFIG_SENSORS_IT87=y CONFIG_SENSORS_LM75=y CONFIG_SENSORS_LM83=y CONFIG_SENSORS_LM90=y CONFIG_SENSORS_VIA686A=y CONFIG_SENSORS_W83781D=y CONFIG_SSB_POSSIBLE=y CONFIG_VIDEO_OUTPUT_CONTROL=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_HID_SUPPORT=y CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_VIRTUALIZATION=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_FS_POSIX_ACL=y CONFIG_DNOTIFY=y CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=y CONFIG_UDF_NLS=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_NETWORK_FILESYSTEMS=y CONFIG_SMB_FS=y CONFIG_CIFS=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT=cp437 CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_INSTRUMENTATION=y CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_MAGIC_SYSRQ=y CONFIG_DEBUG_KERNEL=y CONFIG_DETECT_SOFTLOCKUP=y CONFIG_SCHED_DEBUG=y CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_MUTEXES=y CONFIG_DEBUG_SPINLOCK_SLEEP=y CONFIG_DEBUG_BUGVERBOSE=y CONFIG_FORCED_INLINING=y CONFIG_EARLY_PRINTK=y CONFIG_DEBUG_STACKOVERFLOW=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_DOUBLEFAULT=y CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_DEFLATE=y CONFIG_CRYPTO_HW=y CONFIG_BITREVERSE=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y -- Burton Windle [EMAIL PROTECTED] -- 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: 2.6.23-rc9 boot failure (megaraid?)
On Tue, 2 Oct 2007, Adrian Bunk wrote: Cc's added, the complete bug report is at http://lkml.org/lkml/2007/10/2/243 On Tue, Oct 02, 2007 at 12:48:26PM -0400, Burton Windle wrote: 2.6.23-rc9 fails to boot for me; 2.6.22.9 works fine. System is a Dell Poweredge with PERC 2/DC with RAID1 volume. ... Thanks for your report. Does reverting the commit below fix the problem? cu Adrian commit 3f6270ef76f2ce5c134615a470685d6c2a66c07e Author: FUJITA Tomonori <[EMAIL PROTECTED]> Date: Mon May 14 20:17:27 2007 +0900 Confirmed; reverting the above (snipped) patch does fix the issue. -- Burton Windle [EMAIL PROTECTED] - 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.6.23-rc9 boot failure (megaraid?)
r: ide-cdrom 0800 0 sda driver: sd 08018771458 sda1 No filesystem could mount root, tried: ext3 ext2 iso9660 udf Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) From 2.6.22.9: megaraid: found 0x8086:0x1960:bus 0:slot 13:func 1 scsi0:Found MegaRAID controller at 0xf8812000, IRQ:18 megaraid: [1.06:1p00] detected 1 logical drives. megaraid: channel[0] is raid. megaraid: channel[1] is raid. scsi0 : LSI Logic MegaRAID 1.06 254 commands 16 targs 5 chans 7 luns scsi0: scanning scsi channel 0 for logical drives. scsi 0:0:0:0: Direct-Access MegaRAID LD0 RAID1 8568R 1.06 PQ: 0 ANSI: 2 scsi0: scanning scsi channel 4 [P0] for physical devices. scsi0: scanning scsi channel 5 [P1] for physical devices. st: Version 20070203, fixed bufsize 32768, s/g segs 256 sd 0:0:0:0: [sda] 17547264 512-byte hardware sectors (8984 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Asking for cache data failed sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] 17547264 512-byte hardware sectors (8984 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Asking for cache data failed sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI disk PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice input: PC Speaker as /class/input/input1 input: AT Translated Set 2 keyboard as /class/input/input2 i2c /dev entries driver piix4_smbus :00:07.3: Found :00:07.3 device piix4_smbus :00:07.3: Host SMBus controller not enabled! NET: Registered protocol family 26 TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 15 Starting balanced_irq Using IPI Shortcut mode kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 260k freed EXT3 FS on sda1, internal journal 00:0d.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 02) (prog-if 01) Subsystem: Dell PowerEdge Expandable RAID Controller 2/DC Flags: bus master, medium devsel, latency 64, IRQ 18 Memory at f700 (32-bit, prefetchable) [size=4M] [virtual] Expansion ROM at 5000 [disabled] [size=32K] Capabilities: CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_FC_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_MEGARAID_LEGACY=y -- Burton Windle [EMAIL PROTECTED] - 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.6.23-rc9 boot failure (megaraid?)
-cdrom 0800 0 sda driver: sd 08018771458 sda1 No filesystem could mount root, tried: ext3 ext2 iso9660 udf Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) From 2.6.22.9: megaraid: found 0x8086:0x1960:bus 0:slot 13:func 1 scsi0:Found MegaRAID controller at 0xf8812000, IRQ:18 megaraid: [1.06:1p00] detected 1 logical drives. megaraid: channel[0] is raid. megaraid: channel[1] is raid. scsi0 : LSI Logic MegaRAID 1.06 254 commands 16 targs 5 chans 7 luns scsi0: scanning scsi channel 0 for logical drives. scsi 0:0:0:0: Direct-Access MegaRAID LD0 RAID1 8568R 1.06 PQ: 0 ANSI: 2 scsi0: scanning scsi channel 4 [P0] for physical devices. scsi0: scanning scsi channel 5 [P1] for physical devices. st: Version 20070203, fixed bufsize 32768, s/g segs 256 sd 0:0:0:0: [sda] 17547264 512-byte hardware sectors (8984 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Asking for cache data failed sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] 17547264 512-byte hardware sectors (8984 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Asking for cache data failed sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI disk PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice input: PC Speaker as /class/input/input1 input: AT Translated Set 2 keyboard as /class/input/input2 i2c /dev entries driver piix4_smbus :00:07.3: Found :00:07.3 device piix4_smbus :00:07.3: Host SMBus controller not enabled! NET: Registered protocol family 26 TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 15 Starting balanced_irq Using IPI Shortcut mode kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 260k freed EXT3 FS on sda1, internal journal 00:0d.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 02) (prog-if 01) Subsystem: Dell PowerEdge Expandable RAID Controller 2/DC Flags: bus master, medium devsel, latency 64, IRQ 18 Memory at f700 (32-bit, prefetchable) [size=4M] [virtual] Expansion ROM at 5000 [disabled] [size=32K] Capabilities: access denied CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_FC_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_MEGARAID_LEGACY=y -- Burton Windle [EMAIL PROTECTED] - 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: 2.6.23-rc9 boot failure (megaraid?)
On Tue, 2 Oct 2007, Adrian Bunk wrote: Cc's added, the complete bug report is at http://lkml.org/lkml/2007/10/2/243 On Tue, Oct 02, 2007 at 12:48:26PM -0400, Burton Windle wrote: 2.6.23-rc9 fails to boot for me; 2.6.22.9 works fine. System is a Dell Poweredge with PERC 2/DC with RAID1 volume. ... Thanks for your report. Does reverting the commit below fix the problem? cu Adrian commit 3f6270ef76f2ce5c134615a470685d6c2a66c07e Author: FUJITA Tomonori [EMAIL PROTECTED] Date: Mon May 14 20:17:27 2007 +0900 Confirmed; reverting the above (snipped) patch does fix the issue. -- Burton Windle [EMAIL PROTECTED] - 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/
Detecting SMP
Hello. Is there a way, when running a non-SMP kernel, to detect or otherwise tell (software only; the machine is 2400 miles away) if the system has SMP capibilties? Would /proc/cpuinfo show two CPUs if the kernel is non-SMP? Thanks! (btw, the kernel in question is a stock RH6.2 kernel 2.2.14-5, and yes, I know I should update it anyways and that a SMP kernel will run on a UP system) -- Burton Windle [EMAIL PROTECTED] Linux: the "grim reaper of innocent orphaned children." from /usr/src/linux-2.4.0/init/main.c:655 - 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/
Detecting SMP
Hello. Is there a way, when running a non-SMP kernel, to detect or otherwise tell (software only; the machine is 2400 miles away) if the system has SMP capibilties? Would /proc/cpuinfo show two CPUs if the kernel is non-SMP? Thanks! (btw, the kernel in question is a stock RH6.2 kernel 2.2.14-5, and yes, I know I should update it anyways and that a SMP kernel will run on a UP system) -- Burton Windle [EMAIL PROTECTED] Linux: the "grim reaper of innocent orphaned children." from /usr/src/linux-2.4.0/init/main.c:655 - 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/
VM: Undead swap messages at shutdown
Hello Linux VM God :) I think I started seeing this about 2.4.0-ac6...when I shutdown my machine, I see tons of 'VM: Undead swap entry ###', where ### is some memory address. I can also reproduce this 100% by (for example) going into X, loading a lot of crap so that my 112mb ram is full and it starts to swap, then get out of X, and do a 'swapoff -a'. Is this just debugging info, or would you like to see the output of it? My machine is currently a Debian Unstable, with 112mb RAM and about 190mb swap, running 2.4.0-ac8. I have the following kernels installed, so if you need me to see exactly which kernel started this, it'll be easy: toy:/etc# grep label /etc/lilo.conf label = 240ac8 label = 240ac7 # label = 240ac6 # label = 240ac2 # label = 240prac6 # label = 240prac4 # label = 240t13p7 # label = 240t12 # label = 240t12p6 # label = 240t12p5 # label = 240t12p3 # label = 240t12p2 # label = 240t11 # label = 240t11p7 label = k2218p15 label = win98 -- Burton Windle [EMAIL PROTECTED] Linux: the "grim reaper of innocent orphaned children." from /usr/src/linux/init/main.c:1384 - 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/
VM: Undead swap messages at shutdown
Hello Linux VM God :) I think I started seeing this about 2.4.0-ac6...when I shutdown my machine, I see tons of 'VM: Undead swap entry ###', where ### is some memory address. I can also reproduce this 100% by (for example) going into X, loading a lot of crap so that my 112mb ram is full and it starts to swap, then get out of X, and do a 'swapoff -a'. Is this just debugging info, or would you like to see the output of it? My machine is currently a Debian Unstable, with 112mb RAM and about 190mb swap, running 2.4.0-ac8. I have the following kernels installed, so if you need me to see exactly which kernel started this, it'll be easy: toy:/etc# grep label /etc/lilo.conf label = 240ac8 label = 240ac7 # label = 240ac6 # label = 240ac2 # label = 240prac6 # label = 240prac4 # label = 240t13p7 # label = 240t12 # label = 240t12p6 # label = 240t12p5 # label = 240t12p3 # label = 240t12p2 # label = 240t11 # label = 240t11p7 label = k2218p15 label = win98 -- Burton Windle [EMAIL PROTECTED] Linux: the "grim reaper of innocent orphaned children." from /usr/src/linux/init/main.c:1384 - 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/
PROBLEM: 240t12p3: Reproducable Oops
[1.] One line summary of the problem:
PROBLEM: 240t12p3: Reproducable oops involving ping
[2.] Full description of the problem/report:
While teaching myself Perl, I've either demonstrated a compiler error, or
appear to have found a way to make the 2.4.0-test12-pre3 kernel oops
reproducably many times. Perhaps the kernel is just scared of my poor
Perl, but something doesn't like it. I was originally trying to see what a
full arpcache would like like, but then was having fun annoying my
roommates with ping storms when my die got more annoyed.
[3.] Keywords (i.e., modules, networking, kernel):
2.4.0-test12-pre3 oops ping
[4.] Kernel version (from /proc/version):
Linux version 2.4.0-test12-pre3 (root@toy) (gcc version 2.95.2 2220
(Debian GNU/Linux)) #1 Wed Nov 29 11:53:59 EST 2000
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
Note: the oops happens many many times in a row, so much that it fills my
dmesg. This is the first entire oops that I can see, but all the ones
after this look very very similar.
ksymoops 2.3.4 on i586 2.4.0-test12-pre3. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test12-pre3/ (default)
-m /usr/src/linux/System.map (specified)
Unable to handle kernel paging request at virtual address cc012078
c0125ef0
*pde =
Oops:
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010803
eax: 0218 ebx: c11ffc14 ecx: 44012720 edx: c4012000
esi: 0246 edi: 0007 ebp: c1d15d40 esp: c4adff38
ds: 0018 es: 0018 ss: 0018
Process manyping.pl (pid: 478, stackpage=c4adf000)
Stack: c450a000 fff4 c21ff620 c01162e6 c11ffc14 0007 c4ade000
080fa490
0004 c4adffbc c21ff620 c4adff94 c4ade000 c4c23920
c21ff62c
fff4 fff4 c4adffa0 c4adffa0
Call Trace: [] [] []
Code: 8b 44 82 18 89 42 14 83 f8 ff 75 05 8b 02 89 43 08 56 9d 89
>>EIP; c0125ef0<=
Trace; c01162e6
Trace; c010944f
Trace; c010aa03
Code; c0125ef0
<_EIP>:
Code; c0125ef0<=
0: 8b 44 82 18 mov0x18(%edx,%eax,4),%eax <=
Code; c0125ef4
4: 89 42 14 mov%eax,0x14(%edx)
Code; c0125ef7
7: 83 f8 ff cmp$0x,%eax
Code; c0125efa
a: 75 05 jne11 <_EIP+0x11> c0125f01
Code; c0125efc
c: 8b 02 mov(%edx),%eax
Code; c0125efe
e: 89 43 08 mov%eax,0x8(%ebx)
Code; c0125f01
11: 56push %esi
Code; c0125f02
12: 9dpopf
Code; c0125f03
13: 89 00 mov%eax,(%eax)
[6.] A small shell script or example program which triggers the
problem (if possible)
swapoff -a
cat manyping.pl
#!/usr/bin/perl -w
@ip = (1 .. 255);
foreach (@ip) {
system("ping -c 40 -s 5000 192.168.0.$_ &");
}
I was backgrounding the above program (./manyping.pl &), and running it
with several (15?) instances at the same time.
[7.] Environment
This is an up-to-date Debian Woody system.
[7.1.] Software (add the output of the ver_linux script here)
Linux toy 2.4.0-test12-pre3 #1 Wed Nov 29 11:53:59 EST 2000 i586 unknown
Kernel modules 2.3.21
Gnu C 2.95.2
Gnu Make 3.79.1
Binutils 2.10.1.0.2
Linux C Library> libc.2.2
Dynamic linker ldd (GNU libc) 2.2
Procps 2.0.6
Mount 2.10q
Net-tools 2.05
Console-tools 0.2.3
Sh-utils 2.0i
Modules Loaded rtc es1371 ac97_codec ne 8390
[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 8
model name : AMD-K6(tm) 3D processor
stepping: 12
cpu MHz : 400.901
cache size : 64 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
features: fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
bogomips: 799.54
[7.3.] Module information (from /proc/modules):
rtc 5280 0 (autoclean)
es1371 24400 0
ac97_codec 7504 0 [es1371]
ne 6352 1
83906064 0 [ne]
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
toy:~# cat /proc/ioports
-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
0280-029f : eth0
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(set)
0cf8-0cff : PCI conf1
5c20-5c3f : PCI device
PROBLEM: 240t12p3: Reproducable Oops
think to be relevant): This happened originally when I was in X. I rebooted, and was able to reproduce it on the console before any DRI stuff loaded. [X.] Other notes, patches, fixes, workarounds: I am on LK, but please CC replys to me. Thank you! -- Burton Windle [EMAIL PROTECTED] Linux: the "grim reaper of innocent orphaned children." from /usr/src/linux/init/main.c:1384 - 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/
2.4.0-test10 Oops
97_codec 7440 0 [es1371]
ne 7072 1
83906128 0 [ne]
[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
0170-0177 : ide1
01f0-01f7 : ide0
0280-029f : NE2000
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(set)
0cf8-0cff : PCI conf1
5c20-5c3f : PCI device 10b9:7101
d000-d00f : PCI device 10b9:5229
d400-d4ff : PCI device 121a:0005
d800-d83f : PCI device 1274:1371
d800-d83f : es1371
-0009fbff : System RAM
0009fc00-0009 : reserved
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-06ff : System RAM
0010-00225427 : Kernel code
00225428-00237d03 : Kernel data
dc00-ddff : PCI device 121a:0005
e000-e3ff : PCI device 10b9:1541
e600-e7ff : PCI device 121a:0005
- : reserved
[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1541 (rev 04)
00:01.0 PCI bridge: Acer Laboratories Inc. [ALi] M5243 (rev 04)
00:03.0 Bridge: Acer Laboratories Inc. [ALi] M7101 PMU
00:07.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA Bridge
[Aladdin IV] (rev c3)
00:09.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06)
00:0b.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev
01)
00:0f.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c1)
[7.6.] SCSI information (from /proc/scsi/scsi)
n/a
[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):
I was on tty1 when the oops happened. I was running the beta Debian XF4 at
the time, and most likely had the tdfx module loaded.
Thank you
--
Burton Windle [EMAIL PROTECTED]
Linux: the "grim reaper of innocent orphaned children."
from /usr/src/linux/init/main.c:1384
-
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/
2.4.0-test10 Oops
: no
sep_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mmx 3dnow
bogomips: 799.54
[7.3.] Module information (from /proc/modules):
es1371 24144 0
ac97_codec 7440 0 [es1371]
ne 7072 1
83906128 0 [ne]
[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
0170-0177 : ide1
01f0-01f7 : ide0
0280-029f : NE2000
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(set)
0cf8-0cff : PCI conf1
5c20-5c3f : PCI device 10b9:7101
d000-d00f : PCI device 10b9:5229
d400-d4ff : PCI device 121a:0005
d800-d83f : PCI device 1274:1371
d800-d83f : es1371
-0009fbff : System RAM
0009fc00-0009 : reserved
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-06ff : System RAM
0010-00225427 : Kernel code
00225428-00237d03 : Kernel data
dc00-ddff : PCI device 121a:0005
e000-e3ff : PCI device 10b9:1541
e600-e7ff : PCI device 121a:0005
- : reserved
[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1541 (rev 04)
00:01.0 PCI bridge: Acer Laboratories Inc. [ALi] M5243 (rev 04)
00:03.0 Bridge: Acer Laboratories Inc. [ALi] M7101 PMU
00:07.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA Bridge
[Aladdin IV] (rev c3)
00:09.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06)
00:0b.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev
01)
00:0f.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c1)
[7.6.] SCSI information (from /proc/scsi/scsi)
n/a
[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):
I was on tty1 when the oops happened. I was running the beta Debian XF4 at
the time, and most likely had the tdfx module loaded.
Thank you
--
Burton Windle [EMAIL PROTECTED]
Linux: the "grim reaper of innocent orphaned children."
from /usr/src/linux/init/main.c:1384
-
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/
[drm:drm_release] *ERROR* Process 256 dead
Sorry if this is user-error, but after about 20min of using 2.4.0-test10-pre5, my Debian Woody system dropped out of X with this message in syslog: [drm:drm_release] *ERROR* Process 256 dead, freeing lock for context 1 I've never seen this before; I had been using test10-pre4 for several days without error. Is this a kernel bugglet/error, or X? -- Burton Windle [EMAIL PROTECTED] Linux: the "grim reaper of innocent orphaned children." from /usr/src/linux/init/main.c:1384 - 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/
[drm:drm_release] *ERROR* Process 256 dead
Sorry if this is user-error, but after about 20min of using 2.4.0-test10-pre5, my Debian Woody system dropped out of X with this message in syslog: [drm:drm_release] *ERROR* Process 256 dead, freeing lock for context 1 I've never seen this before; I had been using test10-pre4 for several days without error. Is this a kernel bugglet/error, or X? -- Burton Windle [EMAIL PROTECTED] Linux: the "grim reaper of innocent orphaned children." from /usr/src/linux/init/main.c:1384 - 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/
