Menu
▾
▴
mkdump-devel — discuss mkdump development
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(16) |
Feb
|
Mar
(3) |
Apr
(6) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(8) |
Mar
|
Apr
|
May
(11) |
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(2) |
Nov
|
Dec
(3) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Itsuro O. <od...@va...> - 2006-05-24 22:53:16
|
松島さん、 VA Linux 小田です。お世話になっております。 .configの送付、ありがとうございます。 > bzImageではなくvmlinuxを使う、というのは大丈夫です。 若干、この書き方に不安を覚えたのですが、vmlinux と vmlinux.bin は別物です。（参考: OSM 2006.3 Linuxカーネル2.6解読室 図2) あと、initrdを使用しないのであれば、メモリは、8MB あれば十分 です。 よろしくお願いします。 -- Itsuro ODA <od...@va...> |
|
From: Hiromichi M. <hir...@so...> - 2006-05-24 08:50:25
|
Hi, Mr.Oda and Fernando.
#sorry, it has japanese.
松島＠オープンソースマガジンです。
こちらこそ、いつもお世話になっております。
bzImageではなくvmlinuxを使う、というのは大丈夫です。
RHELの問題かと思いdebianでも試したのですが、やはり同様に
"Starting mini kernel"で止まるので、やはり問題はカーネルのビルド
設定
でしょうか。
再度試してみます。
I tried with debian GNU/Linux 3.1 + mkexec patch + mkexec modules,
but result was the same too...
Are there some points to configure kernel?
Configration files is here.
# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 63
model name : AMD Athlon(tm) 64 Processor 3200+
stepping : 2
cpu MHz : 2009.554
cache size : 512 KB
fdiv_bug : no
hlt_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 pae mce cx8 apic mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm
3dnowext 3dnow pni
bogomips : 4022.20
# cat /proc/iomem
00000000-0009f7ff : System RAM
0009f800-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cf7ff : Video ROM
000d4000-000d57ff : Adapter ROM
000d6000-000d6fff : Adapter ROM
000f0000-000fffff : System ROM
00100000-3ffeffff : System RAM
00100000-003117cb : Kernel code
003117cc-003b8bff : Kernel data
3fff0000-3fff2fff : ACPI Non-volatile Storage
3fff3000-3fffffff : ACPI Tables
e0000000-efffffff : PCI Bus #01
e0000000-efffffff : 0000:01:00.0
f0000000-f7ffffff : 0000:00:00.0
f0000000-f7ffffff : aperture
f8000000-f9ffffff : PCI Bus #01
f8000000-f8ffffff : 0000:01:00.0
fa000000-fbffffff : PCI Bus #02
fb000000-fb01ffff : 0000:02:07.0
fb000000-fb01ffff : e100
fb020000-fb0207ff : 0000:02:0c.0
fb021000-fb0210ff : 0000:02:0d.0
fb021000-fb0210ff : r8169
fb022000-fb022fff : 0000:02:07.0
fb022000-fb022fff : e100
fc000000-fc000fff : 0000:00:06.0
fc000000-fc000fff : NVidia CK8S
fc002000-fc002fff : 0000:00:02.0
fc002000-fc002fff : ohci_hcd
fc003000-fc003fff : 0000:00:02.1
fc003000-fc003fff : ohci_hcd
fc004000-fc0040ff : 0000:00:02.2
fc004000-fc0040ff : ehci_hcd
fec00000-fec00fff : reserved
fee00000-feefffff : reserved
fefffc00-feffffff : reserved
ffff0000-ffffffff : reserved
# lspci
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge
(rev a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management
(rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0
Controller (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb
AC'97 Audio Controller (rev a1)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA
Controller (v2.5) (rev a2)
00:09.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller
(v2.5) (rev a2)
00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller
(v2.5) (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI
Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI
Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce
FX 5200] (rev a1)
02:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet
Pro 100] (rev 0d)
02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 46)
02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
Gigabit Ethernet (rev 10)
mini kernel's .config file:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9
# Wed May 24 17:16:36 2006
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_SWAP is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HOTPLUG=y
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
# CONFIG_MODULES is not set
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
#
# Firmware Drivers
#
CONFIG_EDD=y
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_REGPARM is not set
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
# CONFIG_PM_DEBUG is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BLACKLIST_YEAR=2001
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_LEGACY_PROC=y
# CONFIG_PCI_NAMES is not set
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_YENTA=y
CONFIG_CARDBUS=y
CONFIG_PD6729=y
# CONFIG_I82092 is not set
CONFIG_TCIC=y
#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
CONFIG_HOTPLUG_PCI_COMPAQ=y
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
CONFIG_HOTPLUG_PCI_PCIE=y
# CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
CONFIG_HOTPLUG_PCI_SHPC=y
# CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set
# CONFIG_HOTPLUG_PCI_SHPC_PHPRM_LEGACY is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CONCAT=y
CONFIG_MTD_REDBOOT_PARTS=y
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
CONFIG_MTD_CMDLINE_PARTS=y
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
CONFIG_FTL=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
# CONFIG_INFTL is not set
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
CONFIG_MTD_JEDECPROBE=y
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_AMDSTD_RETRY=3
CONFIG_MTD_CFI_STAA=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=y
CONFIG_MTD_ABSENT=y
#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PNC2000 is not set
CONFIG_MTD_SC520CDP=y
CONFIG_MTD_NETSC520=y
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_ELAN_104NC is not set
CONFIG_MTD_SCx200_DOCFLASH=y
# CONFIG_MTD_AMD76XROM is not set
CONFIG_MTD_ICHXROM=y
# CONFIG_MTD_SCB2_FLASH is not set
# CONFIG_MTD_NETtel is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_L440GX is not set
# CONFIG_MTD_PCI is not set
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
CONFIG_MTD_MTDRAM=y
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTDRAM_ABS_POS=0
# CONFIG_MTD_BLKMTD is not set
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=y
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_IDS=y
# CONFIG_MTD_NAND_DISKONCHIP is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
CONFIG_BLK_CPQ_DA=y
CONFIG_BLK_CPQ_CISS_DA=y
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=y
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
CONFIG_BLK_DEV_SX8=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_INITRD=y
CONFIG_LBD=y
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECS=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_ATIIXP=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=y
CONFIG_BLK_DEV_CY82C693=y
CONFIG_BLK_DEV_CS5520=y
CONFIG_BLK_DEV_CS5530=y
CONFIG_BLK_DEV_HPT34X=y
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=y
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=y
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
# CONFIG_NET is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
# CONFIG_SCTP_HMAC_MD5 is not set
# CONFIG_NET_SCH_CLK_JIFFIES is not set
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
#
# ISDN subsystem
#
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
# CONFIG_SERIO_RAW is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
CONFIG_SYNCLINK=y
CONFIG_SYNCLINKMP=y
CONFIG_N_HDLC=y
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
CONFIG_STALDRV=y
# CONFIG_STALLION is not set
# CONFIG_ISTALLION is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_CS=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_MULTIPORT=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
#
# IPMI
#
CONFIG_IPMI_HANDLER=y
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=y
CONFIG_IPMI_SI=y
CONFIG_IPMI_WATCHDOG=y
CONFIG_IPMI_POWEROFF=y
#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=y
CONFIG_ACQUIRE_WDT=y
CONFIG_ADVANTECH_WDT=y
CONFIG_ALIM1535_WDT=y
CONFIG_ALIM7101_WDT=y
CONFIG_SC520_WDT=y
CONFIG_EUROTECH_WDT=y
CONFIG_IB700_WDT=y
CONFIG_WAFER_WDT=y
CONFIG_I8XX_TCO=y
CONFIG_SC1200_WDT=y
# CONFIG_SCx200_WDT is not set
# CONFIG_60XX_WDT is not set
CONFIG_CPU5_WDT=y
CONFIG_W83627HF_WDT=y
CONFIG_W83877F_WDT=y
CONFIG_MACHZ_WDT=y
#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=y
CONFIG_WDTPCI=y
CONFIG_WDT_501_PCI=y
CONFIG_HW_RANDOM=y
CONFIG_NVRAM=y
CONFIG_RTC=y
CONFIG_DTLK=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
CONFIG_AGP_ALI=y
CONFIG_AGP_ATI=y
CONFIG_AGP_AMD=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_INTEL_MCH=y
CONFIG_AGP_NVIDIA=y
CONFIG_AGP_SIS=y
CONFIG_AGP_SWORKS=y
CONFIG_AGP_VIA=y
CONFIG_AGP_EFFICEON=y
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
CONFIG_DRM_R128=y
CONFIG_DRM_RADEON=y
CONFIG_DRM_I810=y
CONFIG_DRM_I830=y
# CONFIG_DRM_I915 is not set
CONFIG_DRM_MGA=y
# CONFIG_DRM_SIS is not set
#
# PCMCIA character devices
#
CONFIG_SYNCLINK_CS=y
# CONFIG_MWAVE is not set
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=8192
CONFIG_HANGCHECK_TIMER=y
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=y
#
# Video For Linux
#
#
# Video Adapters
#
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
#
# Radio Adapters
#
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
#
# Digital Video Broadcasting Devices
#
#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS_XATTR=y
CONFIG_DEVPTS_FS_SECURITY=y
CONFIG_TMPFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
#
# Native Language Support
#
# CONFIG_NLS is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_INFO=y
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_KPROBES=y
CONFIG_DEBUG_STACK_USAGE=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_4KSTACKS=y
# CONFIG_SCHEDSTATS is not set
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC32 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
----end of .config file----
On 2006/05/24, at 16:43, Itsuro Oda wrote:
> From: Itsuro Oda <od...@va...>
> Date: 2006/05/24 16:40:19
> ----
> #sorry, it is Japanese
>
> 松島さん、
>
> VA Linux 小田です。お世話になっております。
>
>> "Starting mini kernel" were printed, but nothing like boot message
>> was shown
>> thereafter, and there's no HDD access.)
>
> ミニカーネルに制御が渡っていないか、ミニカーネルのしょっぱなで
> 落ちて
> いますね。
>
> 見たところ、ロードまでは正常にできていますので、一番あるのは、
>
>> path: /boot/vmlinux.bin-2.6.9-mkdump
>
> これがちゃんとできているかどうかです。
> arch/i386/boot/compressed/vmlinux.bin(bzImageではなく)を
> 使っているか、
> というところについては、多分大丈夫ですよね。
> あと、ミニカーネルが大きすぎると何か問題があるかもしれません。
> なるべく
> 小さくなるようにしてみてください。
>
> 2.6.9-34.EL ではまだやったことがないので、もしかしたら何かある
> かもしれ
> ません。こっちでも試して見ます。(2.6.9-5.EL、
> 2.6.9-11.EL は実績あり)
> ミニカーネル作成時の.config をいただけますか。合わせて
> やってみたいと
> 思います。
>
> On Wed, 24 May 2006 16:11:52 +0900
> Hiromichi MATSUSHIMA <hir...@so...> wrote:
>
>> Hello, all.
>>
>> I'm interested in mkdump, and now I'm testing it on my desktop PC.
>> But, it doesn't work fine...
>>
>> Mini kernel looks booting correctly with stand-alone, but configure
>> mkexec and
>> try"echo 2 > /proc/mkexec/stat", can't get dump. (Kernel panic
>> messages and
>> "Starting mini kernel" were printed, but nothing like boot message
>> was shown
>> thereafter, and there's no HDD access.)
>>
>> My PC's environment is here.
>>
>> OS: RHEL 4（kernel 2.6.9-34.EL） + mkexec kernel module
>> (use mkexec-module-3.0.tar)
>> MEMORY: 1024MB
>>
>> # uname -a
>> Linux localhost.localdomain 2.6.9-34.EL #1 Wed Mar 8 00:07:35 CST
>> 2006 i686
>> athlon i386 GNU/Linux
>>
>> /etc/mkexec/mkexec:
>> ### mkdump configuration file
>> # for mkd_load
>> MKDUMP_DEV=/dev/hda3 # dump device
>> MKDUMP_VMLINUX=/boot/vmlinux.bin-2.6.9-mkdump # mini kernel binary
>> MKDUMP_MEM=64M # memory size of mini kernel
>> MKDUMP_PARAM="ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-
>> hlt"
>> # mini kernel (extra) parameter
>> #MKDUMP_INITRD="/boot/initrd-minik.img" # initrd image file path
>> MKDUMP_TYPE="standard" # mkexec load type
>> # for mkd_save
>> MKDUMP_DIR=/var/dump # dump save directory
>> MKDUMP_LIMIT=2 # max number of dump saved
>> MKDUMP_PREFORMAT=n # specify format or not a
>> dump device
>>
>> # ls -l /dev/hda3
>> brw-rw---- 1 root disk 3, 3 May 24 2006 /dev/hda3
>>
>> /proc/mkexec/*'s infomation:
>> # for i in *;do echo -n "$i: "; cat $i;done
>> dumpdev: 0x300003
>> initrd:
>> mem: 64
>> parameter: ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-hlt
>> path: /boot/vmlinux.bin-2.6.9-mkdump
>> stats: 1
>>
>> Mini kernel is based on kernel.org's kernel 2.6.9
>> (linux-2.6.9.tar.bz2), and compiled
>> it following the instruction of "README-v3". And, "minik_dump.o" is
>> static linked.
>> (use minik-module-3.0.tar).
>>
>> I have no idea which has problem mkexec kernel or mini kernel.
>> Will you give me some suggestions for it?
>>
>> Thanks.
>>
>> ----
>> Hiromichi MATSUSHIMA
>>
>>
>>
>> -------------------------------------------------------
>> All the advantages of Linux Managed Hosting--Without the Cost and
>> Risk!
>> Fully trained technicians. The highest number of Red Hat
>> certifications in
>> the hosting industry. Fanatical Support. Click to learn more
>> http://sel.as-us.falkag.net/sel?
>> cmd=lnk&kid=107521&bid=248729&dat=121642
>> _______________________________________________
>> Mkdump-devel mailing list
>> Mkd...@li...
>> https://lists.sourceforge.net/lists/listinfo/mkdump-devel
>
> --
> Itsuro ODA <od...@va...>
>
>
|
|
From: Fernando L. V. C. <fer...@in...> - 2006-05-24 08:03:16
|
On Wed, 2006-05-24 at 16:40 +0900, Itsuro Oda wrote: > #sorry, it is Japanese >=20 > =E6=9D=BE=E5=B3=B6=E3=81=95=E3=82=93=E3=80=81 >=20 > VA Linux =E5=B0=8F=E7=94=B0=E3=81=A7=E3=81=99=E3=80=82=E3=81=8A=E4=B8=96= =E8=A9=B1=E3=81=AB=E3=81=AA=E3=81=A3=E3=81=A6=E3=81=8A=E3=82=8A=E3=81=BE=E3= =81=99=E3=80=82 >=20 > > "Starting mini kernel" were printed, but nothing like boot message =20 > > was shown > > thereafter, and there's no HDD access.) >=20 > =E3=83=9F=E3=83=8B=E3=82=AB=E3=83=BC=E3=83=8D=E3=83=AB=E3=81=AB=E5=88=B6= =E5=BE=A1=E3=81=8C=E6=B8=A1=E3=81=A3=E3=81=A6=E3=81=84=E3=81=AA=E3=81=84=E3= =81=8B=E3=80=81=E3=83=9F=E3=83=8B=E3=82=AB=E3=83=BC=E3=83=8D=E3=83=AB=E3=81= =AE=E3=81=97=E3=82=87=E3=81=A3=E3=81=B1=E3=81=AA=E3=81=A7=E8=90=BD=E3=81=A1= =E3=81=A6 > =E3=81=84=E3=81=BE=E3=81=99=E3=81=AD=E3=80=82 >=20 > =E8=A6=8B=E3=81=9F=E3=81=A8=E3=81=93=E3=82=8D=E3=80=81=E3=83=AD=E3=83=BC= =E3=83=89=E3=81=BE=E3=81=A7=E3=81=AF=E6=AD=A3=E5=B8=B8=E3=81=AB=E3=81=A7=E3= =81=8D=E3=81=A6=E3=81=84=E3=81=BE=E3=81=99=E3=81=AE=E3=81=A7=E3=80=81=E4=B8= =80=E7=95=AA=E3=81=82=E3=82=8B=E3=81=AE=E3=81=AF=E3=80=81 >=20 > > path: /boot/vmlinux.bin-2.6.9-mkdump >=20 > =E3=81=93=E3=82=8C=E3=81=8C=E3=81=A1=E3=82=83=E3=82=93=E3=81=A8=E3=81=A7= =E3=81=8D=E3=81=A6=E3=81=84=E3=82=8B=E3=81=8B=E3=81=A9=E3=81=86=E3=81=8B=E3= =81=A7=E3=81=99=E3=80=82 > arch/i386/boot/compressed/vmlinux.bin(bzImage=E3=81=A7=E3=81=AF=E3=81=AA= =E3=81=8F)=E3=82=92=E4=BD=BF=E3=81=A3=E3=81=A6=E3=81=84=E3=82=8B=E3=81=8B= =E3=80=81 > =E3=81=A8=E3=81=84=E3=81=86=E3=81=A8=E3=81=93=E3=82=8D=E3=81=AB=E3=81=A4= =E3=81=84=E3=81=A6=E3=81=AF=E3=80=81=E5=A4=9A=E5=88=86=E5=A4=A7=E4=B8=88=E5= =A4=AB=E3=81=A7=E3=81=99=E3=82=88=E3=81=AD=E3=80=82 > =E3=81=82=E3=81=A8=E3=80=81=E3=83=9F=E3=83=8B=E3=82=AB=E3=83=BC=E3=83=8D= =E3=83=AB=E3=81=8C=E5=A4=A7=E3=81=8D=E3=81=99=E3=81=8E=E3=82=8B=E3=81=A8=E4= =BD=95=E3=81=8B=E5=95=8F=E9=A1=8C=E3=81=8C=E3=81=82=E3=82=8B=E3=81=8B=E3=82= =82=E3=81=97=E3=82=8C=E3=81=BE=E3=81=9B=E3=82=93=E3=80=82=E3=81=AA=E3=82=8B= =E3=81=B9=E3=81=8F > =E5=B0=8F=E3=81=95=E3=81=8F=E3=81=AA=E3=82=8B=E3=82=88=E3=81=86=E3=81=AB= =E3=81=97=E3=81=A6=E3=81=BF=E3=81=A6=E3=81=8F=E3=81=A0=E3=81=95=E3=81=84=E3= =80=82 >=20 > 2.6.9-34.EL =E3=81=A7=E3=81=AF=E3=81=BE=E3=81=A0=E3=82=84=E3=81=A3=E3=81= =9F=E3=81=93=E3=81=A8=E3=81=8C=E3=81=AA=E3=81=84=E3=81=AE=E3=81=A7=E3=80=81= =E3=82=82=E3=81=97=E3=81=8B=E3=81=97=E3=81=9F=E3=82=89=E4=BD=95=E3=81=8B=E3= =81=82=E3=82=8B=E3=81=8B=E3=82=82=E3=81=97=E3=82=8C > =E3=81=BE=E3=81=9B=E3=82=93=E3=80=82=E3=81=93=E3=81=A3=E3=81=A1=E3=81=A7= =E3=82=82=E8=A9=A6=E3=81=97=E3=81=A6=E8=A6=8B=E3=81=BE=E3=81=99=E3=80=82(= 2.6.9-5.EL=E3=80=812.6.9-11.EL =E3=81=AF=E5=AE=9F=E7=B8=BE=E3=81=82=E3=82= =8A) 2.6.9-11.ELsmp=E3=82=82=E5=AE=9F=E7=B8=BE=E3=81=82=E3=82=8A=E3=80=82 > =E3=83=9F=E3=83=8B=E3=82=AB=E3=83=BC=E3=83=8D=E3=83=AB=E4=BD=9C=E6=88=90= =E6=99=82=E3=81=AE.config =E3=82=92=E3=81=84=E3=81=9F=E3=81=A0=E3=81=91=E3= =81=BE=E3=81=99=E3=81=8B=E3=80=82=E5=90=88=E3=82=8F=E3=81=9B=E3=81=A6=E3=82= =84=E3=81=A3=E3=81=A6=E3=81=BF=E3=81=9F=E3=81=84=E3=81=A8 > =E6=80=9D=E3=81=84=E3=81=BE=E3=81=99=E3=80=82 =E3=81=93=E3=81=A1=E3=82=89=E3=81=A7=E3=82=82=E8=A9=A6=E3=81=97=E3=81=A6=E8= =A6=8B=E3=81=BE=E3=81=99=E3=80=82 > On Wed, 24 May 2006 16:11:52 +0900 > Hiromichi MATSUSHIMA <hir...@so...> wrote: >=20 > > Hello, all. > >=20 > > I'm interested in mkdump, and now I'm testing it on my desktop PC. > > But, it doesn't work fine... > >=20 > > Mini kernel looks booting correctly with stand-alone, but configure =20 > > mkexec and > > try"echo 2 > /proc/mkexec/stat", can't get dump. (Kernel panic =20 > > messages and > > "Starting mini kernel" were printed, but nothing like boot message =20 > > was shown > > thereafter, and there's no HDD access.) > >=20 > > My PC's environment is here. > >=20 > > OS: RHEL 4=EF=BC=88kernel 2.6.9-34.EL=EF=BC=89 + mkexec kernel module > > (use mkexec-module-3.0.tar) > > MEMORY: 1024MB > >=20 > > # uname -a > > Linux localhost.localdomain 2.6.9-34.EL #1 Wed Mar 8 00:07:35 CST =20 > > 2006 i686 > > athlon i386 GNU/Linux > >=20 > > /etc/mkexec/mkexec: > > ### mkdump configuration file > > # for mkd_load > > MKDUMP_DEV=3D/dev/hda3 # dump device > > MKDUMP_VMLINUX=3D/boot/vmlinux.bin-2.6.9-mkdump # mini kernel binar= y > > MKDUMP_MEM=3D64M # memory size of mini kernel > > MKDUMP_PARAM=3D"ro console=3Dtty0 console=3DttyS0,9600n8 lpj=3D236748= 8 no-hlt" > > # mini kernel (extra) parameter > > #MKDUMP_INITRD=3D"/boot/initrd-minik.img" # initrd image file path > > MKDUMP_TYPE=3D"standard" # mkexec load type > > # for mkd_save > > MKDUMP_DIR=3D/var/dump # dump save directory > > MKDUMP_LIMIT=3D2 # max number of dump saved > > MKDUMP_PREFORMAT=3Dn # specify format or not a =20 > > dump device > >=20 > > # ls -l /dev/hda3 > > brw-rw---- 1 root disk 3, 3 May 24 2006 /dev/hda3 > >=20 > > /proc/mkexec/*'s infomation: > > # for i in *;do echo -n "$i: "; cat $i;done > > dumpdev: 0x300003 > > initrd: > > mem: 64 > > parameter: ro console=3Dtty0 console=3DttyS0,9600n8 lpj=3D2367488 no-= hlt > > path: /boot/vmlinux.bin-2.6.9-mkdump > > stats: 1 > >=20 > > Mini kernel is based on kernel.org's kernel 2.6.9 =20 > > (linux-2.6.9.tar.bz2), and compiled > > it following the instruction of "README-v3". And, "minik_dump.o" is =20 > > static linked. > > (use minik-module-3.0.tar). > >=20 > > I have no idea which has problem mkexec kernel or mini kernel. > > Will you give me some suggestions for it? > >=20 > > Thanks. > >=20 > > ---- > > Hiromichi MATSUSHIMA > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > All the advantages of Linux Managed Hosting--Without the Cost and Ris= k! > > Fully trained technicians. The highest number of Red Hat certificatio= ns in > > the hosting industry. Fanatical Support. Click to learn more > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D107521&bid=3D248729&d= at=3D121642 > > _______________________________________________ > > Mkdump-devel mailing list > > Mkd...@li... > > https://lists.sourceforge.net/lists/listinfo/mkdump-devel >=20 > --=20 > Itsuro ODA <od...@va...> >=20 >=20 >=20 > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications= in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D107521&bid=3D248729&dat= =3D121642 > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel |
|
From: Fernando L. V. C. <fer...@in...> - 2006-05-24 07:56:22
|
Hi Hiromichi, Thank you for your interest in mkdump! I will try to reproduce your problem in one of my machines too, but first I would like to know some more details about the specs of your machine. Could you please send me the output of the commands below? # cat /proc/iomem # cat /proc/cpuinfo # lspci Best regards, Fernando On Wed, 2006-05-24 at 16:11 +0900, Hiromichi MATSUSHIMA wrote: > Hello, all. >=20 > I'm interested in mkdump, and now I'm testing it on my desktop PC. > But, it doesn't work fine... >=20 > Mini kernel looks booting correctly with stand-alone, but configure =20 > mkexec and > try"echo 2 > /proc/mkexec/stat", can't get dump. (Kernel panic =20 > messages and > "Starting mini kernel" were printed, but nothing like boot message =20 > was shown > thereafter, and there's no HDD access.) >=20 > My PC's environment is here. >=20 > OS: RHEL 4=EF=BC=88kernel 2.6.9-34.EL=EF=BC=89 + mkexec kernel module > (use mkexec-module-3.0.tar) > MEMORY: 1024MB >=20 > # uname -a > Linux localhost.localdomain 2.6.9-34.EL #1 Wed Mar 8 00:07:35 CST =20 > 2006 i686 > athlon i386 GNU/Linux >=20 > /etc/mkexec/mkexec: > ### mkdump configuration file > # for mkd_load > MKDUMP_DEV=3D/dev/hda3 # dump device > MKDUMP_VMLINUX=3D/boot/vmlinux.bin-2.6.9-mkdump # mini kernel binary > MKDUMP_MEM=3D64M # memory size of mini kernel > MKDUMP_PARAM=3D"ro console=3Dtty0 console=3DttyS0,9600n8 lpj=3D2367488 = no-hlt" > # mini kernel (extra) parameter > #MKDUMP_INITRD=3D"/boot/initrd-minik.img" # initrd image file path > MKDUMP_TYPE=3D"standard" # mkexec load type > # for mkd_save > MKDUMP_DIR=3D/var/dump # dump save directory > MKDUMP_LIMIT=3D2 # max number of dump saved > MKDUMP_PREFORMAT=3Dn # specify format or not a =20 > dump device >=20 > # ls -l /dev/hda3 > brw-rw---- 1 root disk 3, 3 May 24 2006 /dev/hda3 >=20 > /proc/mkexec/*'s infomation: > # for i in *;do echo -n "$i: "; cat $i;done > dumpdev: 0x300003 > initrd: > mem: 64 > parameter: ro console=3Dtty0 console=3DttyS0,9600n8 lpj=3D2367488 no-hl= t > path: /boot/vmlinux.bin-2.6.9-mkdump > stats: 1 >=20 > Mini kernel is based on kernel.org's kernel 2.6.9 =20 > (linux-2.6.9.tar.bz2), and compiled > it following the instruction of "README-v3". And, "minik_dump.o" is =20 > static linked. > (use minik-module-3.0.tar). >=20 > I have no idea which has problem mkexec kernel or mini kernel. > Will you give me some suggestions for it? >=20 > Thanks. >=20 > ---- > Hiromichi MATSUSHIMA >=20 >=20 >=20 > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications= in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D107521&bid=3D248729&dat= =3D121642 > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel |
|
From: Itsuro O. <od...@va...> - 2006-05-24 07:40:22
|
#sorry, it is Japanese 松島さん、 VA Linux 小田です。お世話になっております。 > "Starting mini kernel" were printed, but nothing like boot message > was shown > thereafter, and there's no HDD access.) ミニカーネルに制御が渡っていないか、ミニカーネルのしょっぱなで落ちて いますね。 見たところ、ロードまでは正常にできていますので、一番あるのは、 > path: /boot/vmlinux.bin-2.6.9-mkdump これがちゃんとできているかどうかです。 arch/i386/boot/compressed/vmlinux.bin(bzImageではなく)を使っているか、 というところについては、多分大丈夫ですよね。 あと、ミニカーネルが大きすぎると何か問題があるかもしれません。なるべく 小さくなるようにしてみてください。 2.6.9-34.EL ではまだやったことがないので、もしかしたら何かあるかもしれ ません。こっちでも試して見ます。(2.6.9-5.EL、2.6.9-11.EL は実績あり) ミニカーネル作成時の.config をいただけますか。合わせてやってみたいと 思います。 On Wed, 24 May 2006 16:11:52 +0900 Hiromichi MATSUSHIMA <hir...@so...> wrote: > Hello, all. > > I'm interested in mkdump, and now I'm testing it on my desktop PC. > But, it doesn't work fine... > > Mini kernel looks booting correctly with stand-alone, but configure > mkexec and > try"echo 2 > /proc/mkexec/stat", can't get dump. (Kernel panic > messages and > "Starting mini kernel" were printed, but nothing like boot message > was shown > thereafter, and there's no HDD access.) > > My PC's environment is here. > > OS: RHEL 4（kernel 2.6.9-34.EL） + mkexec kernel module > (use mkexec-module-3.0.tar) > MEMORY: 1024MB > > # uname -a > Linux localhost.localdomain 2.6.9-34.EL #1 Wed Mar 8 00:07:35 CST > 2006 i686 > athlon i386 GNU/Linux > > /etc/mkexec/mkexec: > ### mkdump configuration file > # for mkd_load > MKDUMP_DEV=/dev/hda3 # dump device > MKDUMP_VMLINUX=/boot/vmlinux.bin-2.6.9-mkdump # mini kernel binary > MKDUMP_MEM=64M # memory size of mini kernel > MKDUMP_PARAM="ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-hlt" > # mini kernel (extra) parameter > #MKDUMP_INITRD="/boot/initrd-minik.img" # initrd image file path > MKDUMP_TYPE="standard" # mkexec load type > # for mkd_save > MKDUMP_DIR=/var/dump # dump save directory > MKDUMP_LIMIT=2 # max number of dump saved > MKDUMP_PREFORMAT=n # specify format or not a > dump device > > # ls -l /dev/hda3 > brw-rw---- 1 root disk 3, 3 May 24 2006 /dev/hda3 > > /proc/mkexec/*'s infomation: > # for i in *;do echo -n "$i: "; cat $i;done > dumpdev: 0x300003 > initrd: > mem: 64 > parameter: ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-hlt > path: /boot/vmlinux.bin-2.6.9-mkdump > stats: 1 > > Mini kernel is based on kernel.org's kernel 2.6.9 > (linux-2.6.9.tar.bz2), and compiled > it following the instruction of "README-v3". And, "minik_dump.o" is > static linked. > (use minik-module-3.0.tar). > > I have no idea which has problem mkexec kernel or mini kernel. > Will you give me some suggestions for it? > > Thanks. > > ---- > Hiromichi MATSUSHIMA > > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel -- Itsuro ODA <od...@va...> |
|
From: Hiromichi M. <hir...@so...> - 2006-05-24 07:12:03
|
Hello, all.
I'm interested in mkdump, and now I'm testing it on my desktop PC.
But, it doesn't work fine...
Mini kernel looks booting correctly with stand-alone, but configure
mkexec and
try"echo 2 > /proc/mkexec/stat", can't get dump. (Kernel panic
messages and
"Starting mini kernel" were printed, but nothing like boot message
was shown
thereafter, and there's no HDD access.)
My PC's environment is here.
OS: RHEL 4（kernel 2.6.9-34.EL） + mkexec kernel module
(use mkexec-module-3.0.tar)
MEMORY: 1024MB
# uname -a
Linux localhost.localdomain 2.6.9-34.EL #1 Wed Mar 8 00:07:35 CST
2006 i686
athlon i386 GNU/Linux
/etc/mkexec/mkexec:
### mkdump configuration file
# for mkd_load
MKDUMP_DEV=/dev/hda3 # dump device
MKDUMP_VMLINUX=/boot/vmlinux.bin-2.6.9-mkdump # mini kernel binary
MKDUMP_MEM=64M # memory size of mini kernel
MKDUMP_PARAM="ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-hlt"
# mini kernel (extra) parameter
#MKDUMP_INITRD="/boot/initrd-minik.img" # initrd image file path
MKDUMP_TYPE="standard" # mkexec load type
# for mkd_save
MKDUMP_DIR=/var/dump # dump save directory
MKDUMP_LIMIT=2 # max number of dump saved
MKDUMP_PREFORMAT=n # specify format or not a
dump device
# ls -l /dev/hda3
brw-rw---- 1 root disk 3, 3 May 24 2006 /dev/hda3
/proc/mkexec/*'s infomation:
# for i in *;do echo -n "$i: "; cat $i;done
dumpdev: 0x300003
initrd:
mem: 64
parameter: ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-hlt
path: /boot/vmlinux.bin-2.6.9-mkdump
stats: 1
Mini kernel is based on kernel.org's kernel 2.6.9
(linux-2.6.9.tar.bz2), and compiled
it following the instruction of "README-v3". And, "minik_dump.o" is
static linked.
(use minik-module-3.0.tar).
I have no idea which has problem mkexec kernel or mini kernel.
Will you give me some suggestions for it?
Thanks.
----
Hiromichi MATSUSHIMA
|
|
From: Hiromichi M. <hir...@so...> - 2006-05-24 06:58:12
|
Hello, all.
I'm interested in mkdump, and now I'm testing it on desktop PC.
But, it doesn't work fine...
Mini kernel looks booting correctly with stand-alone, but configure
mkexec and try "echo 2 > /proc/mkexec/stat", can't get dump.
(Kernel panic messages and "Starting mini kernel" were printed,
but nothing like boot message was shown thereafter, and
there's no HDD access.)
My PC's environment is here.
OS:
RHEL 4（kernel 2.6.9-34.EL） + mkexec kernel module
(use mkexec-module-3.0.tar)
MEMORY: 1024MB
# uname -a
Linux localhost.localdomain 2.6.9-34.EL #1 Wed Mar 8 00:07:35
CST 2006 i686 athlon i386 GNU/Linux
/etc/mkexec/mkexec:
### mkdump configuration file
# for mkd_load
MKDUMP_DEV=/dev/hda3 # dump device
MKDUMP_VMLINUX=/boot/vmlinux.bin-2.6.9-mkdump # mini kernel binary
MKDUMP_MEM=64M # memory size of mini kernel
MKDUMP_PARAM="ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-hlt"
# mini kernel (extra) parameter
#MKDUMP_INITRD="/boot/initrd-minik.img" # initrd image file path
MKDUMP_TYPE="standard" # mkexec load type
# for mkd_save
MKDUMP_DIR=/var/dump # dump save directory
MKDUMP_LIMIT=2 # max number of dump saved
MKDUMP_PREFORMAT=n # specify format or not a
dump device
# ls -l /dev/hda3
brw-rw---- 1 root disk 3, 3 May 24 2006 /dev/hda3
/proc/mkexec/*'s infomation:
# for i in *;do echo -n "$i: "; cat $i;done
dumpdev: 0x300003
initrd:
mem: 64
parameter: ro console=tty0 console=ttyS0,9600n8 lpj=2367488 no-hlt
path: /boot/vmlinux.bin-2.6.9-mkdump
stats: 1
Mini kernel is based on kernel.org's kernel 2.6.9
(linux-2.6.9.tar.bz2), and
compiled it following the instruction of "README-v3". And,
"minik_dump.o" is
static linked.(use minik-module-3.0.tar).
I have no idea which has problem mkexec kernel or mini kernel.
Will you give me some suggestions for it?
Thanks.
----
Hiromichi MATSUSHIMA
|
|
From: Itsuro O. <od...@va...> - 2006-02-23 02:23:35
|
Hi, > Will the version 1 of mkdump work on Linux 2.4.32? I think the best way is to port version 1 for vanilla 2.4.27 to 2.4.32. (I have not trid yet though.) > this one running as back-end servers, and they don't crash. When the > system "dies", the console is black and does not respond to keyboard input > (screen blanking on the console is disabled), serial console gets no > output, a process that we have running on the system capturing a "ps" > every minute stops running. However, the system is pingable, and while it > does not respond to ssh/telnet, we notice that an nmap of the server still > lists the ports running services (and though you can connect to any of the > ports, you don't get back anything). We were really hoping to be able to Oops. Maybe someone (in the kernel functions) is into infinite loop (but still interrupt is enable). A crash dump tool may not be usefull becase the hook which calls dump caputuring function is not called in this case. (If this were infinite loop with interrupt disable case, nmi_watchdog is usefull.) Thanks. -- Itsuro ODA <od...@va...> |
|
From: Jason K. <ja...@cs...> - 2006-02-23 01:20:50
|
Will the version 1 of mkdump work on Linux 2.4.32? I'm faced with a problem where-by one of our Linux systems running 2.4.32 is crashing either every day (somtimes more than once in the day) or every second or third day. We replaced the hardware with an almost identical box while we did testing on the original hardware. We found the original hardware to be free from problems, and to our surprise the replacement hardware exhibited the same crashing behaviour! We have several other boxes running exactly the same kernel with slightly different hardware, and they don't seem to be crashing. This box is a time sharing server, so many users are running their programs here. We have identical boxes to this one running as back-end servers, and they don't crash. When the system "dies", the console is black and does not respond to keyboard input (screen blanking on the console is disabled), serial console gets no output, a process that we have running on the system capturing a "ps" every minute stops running. However, the system is pingable, and while it does not respond to ssh/telnet, we notice that an nmap of the server still lists the ports running services (and though you can connect to any of the ports, you don't get back anything). We were really hoping to be able to use mkdump somehow to solve our problems. The documentation for mkdump seemed to imply at least some compatibility with vanilla 2.4.27 which isn't much different from 2.4.32. If you, or anyone else has any suggestions on what we might do to resolve this problem, or how we could use any version of mkdump to do that, we would really appreciate it! Jason. On Thu, 23 Feb 2006, Itsuro Oda wrote: > Hi, > >> The comment: /* only support RHEL currently */ > right. > >> Will mkexec not work on stock 2.4.32? > no. > > Thanks. > > On Wed, 22 Feb 2006 14:44:52 -0500 > Jason Keltz <ja...@cs...> wrote: > >> Hi. >> I'm running Linux Kernel 2.4.32, and I would like to use mkdump to >> analyze why my system is crashing on a regular basis. I've downloaded >> the 2.1 package and got to the point where I'm building the mkexec >> kernel module, and I'm running into a problem where-by the code in >> mkexec_main.c in the mkexec_unload function ends up doing... >> >> #ifdef MKEXEC_NO_PATCH >> /* only support RHEL currently */ >> cmpxchg(&netdump_func, (unsigned long)do_minik_dump, (unsigned >> long)NULL >> ); >> >> ... but there is no netdump_func on the system. >> >> The comment: /* only support RHEL currently */ >> >> Will mkexec not work on stock 2.4.32? >> >> jas. >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 >> _______________________________________________ >> Mkdump-devel mailing list >> Mkd...@li... >> https://lists.sourceforge.net/lists/listinfo/mkdump-devel > > -- > Itsuro ODA <od...@va...> > > |
|
From: Itsuro O. <od...@va...> - 2006-02-22 23:19:09
|
Hi, > The comment: /* only support RHEL currently */ right. > Will mkexec not work on stock 2.4.32? no. Thanks. On Wed, 22 Feb 2006 14:44:52 -0500 Jason Keltz <ja...@cs...> wrote: > Hi. > I'm running Linux Kernel 2.4.32, and I would like to use mkdump to > analyze why my system is crashing on a regular basis. I've downloaded > the 2.1 package and got to the point where I'm building the mkexec > kernel module, and I'm running into a problem where-by the code in > mkexec_main.c in the mkexec_unload function ends up doing... > > #ifdef MKEXEC_NO_PATCH > /* only support RHEL currently */ > cmpxchg(&netdump_func, (unsigned long)do_minik_dump, (unsigned > long)NULL > ); > > ... but there is no netdump_func on the system. > > The comment: /* only support RHEL currently */ > > Will mkexec not work on stock 2.4.32? > > jas. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel -- Itsuro ODA <od...@va...> |
|
From: Jason K. <ja...@cs...> - 2006-02-22 19:44:55
|
Hi.
I'm running Linux Kernel 2.4.32, and I would like to use mkdump to
analyze why my system is crashing on a regular basis. I've downloaded
the 2.1 package and got to the point where I'm building the mkexec
kernel module, and I'm running into a problem where-by the code in
mkexec_main.c in the mkexec_unload function ends up doing...
#ifdef MKEXEC_NO_PATCH
/* only support RHEL currently */
cmpxchg(&netdump_func, (unsigned long)do_minik_dump, (unsigned
long)NULL
);
... but there is no netdump_func on the system.
The comment: /* only support RHEL currently */
Will mkexec not work on stock 2.4.32?
jas.
|
|
From: Fernando L. V. C. <fer...@in...> - 2006-02-17 10:23:17
|
Hi Jeong-Sang, I have a machine with specs very similar to yours so I will test whether mkdump works as expected there with the config file you sent me. Unfortunately I will not have access to that machine until Monday. I will let you know then and hope we can fix the problem in your environment. Sorry for the trouble. Best regards, Fernando On Thu, 2006-02-16 at 21:12 +0900, Jeong-Sang Ohn wrote: > Hi Fernando, > > First of all, I'm really appreciating your help. Thank You! :D > > I'll put my answers below. > > > On 2/16/06, Fernando Luis Vazquez Cao <fer...@in...> > wrote: > Hi Jeong-Sang, > > Thank you for the prompt reply. > > On Thu, 2006-02-16 at 18:36 +0900, Jeong-Sang Ohn wrote: > > > But after patching the kernel with the mkdump > > > patch(minik-patch-2.6.9-1.2), the > > > kernel won't boot. (Also tried to boot with this > kernel stand-alone, > > > but it > > > won't boot either.)Cannot see anything printing. > And after a few secs, > > > the > > > system reboots. > I have a hunch that what is happening is something like this: > > - The second kernel boots normally but nothing is sent to the > serial > console because it is not configured properly. (see below) > ----> Oh, sorry. That was a typo... the console parameter part is > actually, > "console=ttyS1,115200n8" > And it's working fine on the unpatched 2.6.9 kernel. > > > - The second kernel is not able to find the specified dump > device (see > below) and, consequently, reboots the machine (this is the > default > behavior when the device is not found). > ----> my dump device is /dev/hde2 (which is connected via PCI > IDE controller)[root@255_63_63_DPSA root]# fdisk -l > Disk /dev/hde: 40.0 GB, 40007761920 bytes > 16 heads, 63 sectors/track, 77520 cylinders > Units = cylinders of 1008 * 512 = 516096 bytes > > Device Boot Start End Blocks Id System > /dev/hde1 * 1 203 101872+ 83 Linux > /dev/hde2 203 73460 36921840 83 Linux > /dev/hde3 73461 77520 2046120 82 Linux swap > [root@255_63_63_DPSA root]# ls -al /dev/hde2 > brw-rw---- 1 root disk 33, 2 Jan 25 > 23:30 /dev/hde2 > > > /dev/hde2 is currently an empty partition made for the mkdump > test. > > And even though this part got wrong, I think I should still > see some messages > during the initialization of the mini-kernel. > > it looks like this (load is complete & haven't wrote > '2' to /proc/mkexec/stats yet): > > [ root@255_63_63_DPSA root]# cat /proc/mkexec/mem > > 16 > This is a valid value. > > > [root@255_63_63_DPSA root]# cat /proc/mkexec/dumpdev > > 0x2100002 > Are you sure this is a correct values? Could you show the > output of ls > -l /dev/your_dump_device? > > > [root@255_63_63_DPSA root]# > cat /proc/mkexec/parameter > > console=console=ttyS1,115200n8 lpj=2392060 no-hlt > > mkdump_reboot=halt dump_delay=0 > Regarding the console settings, you want either > "console=tty0 console=ttyS1,115200n8" > or > "console=ttyS1,115200n8". > > "console=console=ttyS1,115200n8" seems to be invalid. > > > [root@255_63_63_DPSA root]# cat /proc/mkexec/path > > /boot/vmlinux.bin > I assume this was copied from > "arch/i386/boot/compressed/vmlinux.bin". > Correct? > ----> Yes. that's the one I've used. > > > [root@255_63_63_DPSA root]# cat /proc/mkexec/stats > > 1 > This looks good. > > Could you make the aforementioned changes and try again? > Thanks in advance. > > Regards, > > Fernando > > > Well, in conclusion I can't find anything to change yet. > Could the relatively large RAM size(8GB) be a problem? > > And, I've also tested the mkdump on an Intel Pentium3 PC (256MB > RAM) in the same manner and it just works fine. > > Maybe my kernel configuration could inform you a bit. > I'll attatch my .config file for the mini-kernel. > > Thank you. > > |
|
From: Fernando L. V. C. <fer...@in...> - 2006-02-16 11:06:54
|
Hi Jeong-Sang, Thank you for the prompt reply. On Thu, 2006-02-16 at 18:36 +0900, Jeong-Sang Ohn wrote: > > But after patching the kernel with the mkdump > > patch(minik-patch-2.6.9-1.2), the > > kernel won't boot. (Also tried to boot with this kernel stand-alone, > > but it > > won't boot either.)Cannot see anything printing. And after a few secs, > > the > > system reboots. I have a hunch that what is happening is something like this: - The second kernel boots normally but nothing is sent to the serial console because it is not configured properly. (see below) - The second kernel is not able to find the specified dump device (see below) and, consequently, reboots the machine (this is the default behavior when the device is not found). > it looks like this (load is complete & haven't wrote '2' to /proc/mkexec/stats yet): > [root@255_63_63_DPSA root]# cat /proc/mkexec/mem > 16 This is a valid value. > [root@255_63_63_DPSA root]# cat /proc/mkexec/dumpdev > 0x2100002 Are you sure this is a correct values? Could you show the output of ls -l /dev/your_dump_device? > [root@255_63_63_DPSA root]# cat /proc/mkexec/parameter > console=console=ttyS1,115200n8 lpj=2392060 no-hlt > mkdump_reboot=halt dump_delay=0 Regarding the console settings, you want either "console=tty0 console=ttyS1,115200n8" or "console=ttyS1,115200n8". "console=console=ttyS1,115200n8" seems to be invalid. > [root@255_63_63_DPSA root]# cat /proc/mkexec/path > /boot/vmlinux.bin I assume this was copied from "arch/i386/boot/compressed/vmlinux.bin". Correct? > [root@255_63_63_DPSA root]# cat /proc/mkexec/stats > 1 This looks good. Could you make the aforementioned changes and try again? Thanks in advance. Regards, Fernando |
|
From: Fernando L. V. C. <fer...@in...> - 2006-02-16 08:37:13
|
Hi Jeong-Sang, Thank you for your interest in mkdump! On Thu, 2006-02-16 at 16:50 +0900, Jeong-Sang Ohn wrote: > Hello, > > I'm currently tyring to do the mini kernel dump on my system. > > Unpatched(original) 2.6.9 kernel with the default > configuration(kernel/arch/i386/defconfig) boots fine. I guess you are using a kernel from kernel.org, right? > But after patching the kernel with the mkdump > patch(minik-patch-2.6.9-1.2), the > kernel won't boot. (Also tried to boot with this kernel stand-alone, > but it > won't boot either.)Cannot see anything printing. And after a few secs, > the > system reboots. Where did you download "minik-patch-2.6.9-1.2" from? Did you mean minik-2.6.9-1.0-update1.patch perhaps? Could you show me the content of the files below? /proc/mkexec/mem /proc/mkexec/dumpdev /proc/mkexec/parameter /proc/mkexec/path /proc/mkexec/stats You can find a detailed explanation of the meaning of this files in: http://prdownloads.sourceforge.net/mkdump/README.mkdump?download > I've used the default configuration(kernel/arch/i386/defconfig) with > the new > mkdump options enabled, and the SMP option disabled. (no other > changes) Is CONFIG_DUMP_MINI_KERNEL also enabled? > ----------------------------- > The system I'm working on is: > Intel P4 XEON (dual) > 8GB DDR RAM > MCH: E7501 > ICH: ICH3 > S/IO: PC87417 > ----------------------------- > Any solutions to this problem? > Suggestions appreciated! Once again, thanks for trying mkdump. I hope I can help you. Best regards, Fernando |
|
From: Jeong-Sang O. <on...@gm...> - 2006-02-16 07:50:42
|
Hello, I'm currently tyring to do the mini kernel dump on my system. Unpatched(original) 2.6.9 kernel with the default configuration(kernel/arch/i386/defconfig) boots fine. But after patching the kernel with the mkdump patch(minik-patch-2.6.9-1.2), the kernel won't boot. (Also tried to boot with this kernel stand-alone, but it won't boot either.)Cannot see anything printing. And after a few secs, the system reboots. I've used the default configuration(kernel/arch/i386/defconfig) with the ne= w mkdump options enabled, and the SMP option disabled. (no other changes) ----------------------------- The system I'm working on is: Intel P4 XEON (dual) 8GB DDR RAM MCH: E7501 ICH: ICH3 S/IO: PC87417 ----------------------------- Any solutions to this problem? Suggestions appreciated! Thank you. |
|
From: Jan K. <la...@va...> - 2005-05-13 05:18:36
|
Hi, Patch update: * Ported i386 also to x86_64. * Fixed incompatibility with some x86_64 possibly affecting also i386. (APIC/IO-APIC state was saved too late) (intact original announcement below) ------------------------------------------------------------------------------ kexec patch uses APIC+IO-APIC reprogramming back to the original mode: http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc3/2.6.12-rc3-mm2/broken-out/x86-apic-virtwire-on-shutdown.patch http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc3/2.6.12-rc3-mm2/broken-out/x86_64-apic-virtwire-on-shutdown.patch kexec locks up the child 'minik' kernel during: Calibrating delay loop... if the parent 'mkexec' kernel is SMP running on VA-Linux-1220 machine. FYI this machine has some broken BIOS IO-APIC settings. mkexec uses modified patches above and it works fine even for VA-Linux-1220. Still I do not understand the reasons. kexec solution looks right to me as if IOAPIC is set to VirtualWire mode APIC LVT0 could get disabled. Unfortunately not on VA-Linux-1220. Legacy (PIC or VirtualWire) interrupts can be set in many ways by the BIOS and I believe the most safe way is just to restore their state. Implemented in the attached patch for LAPIC + IO-APIC by suspend/resume functions. Currently not yet ready for non-i386, maybe on Friday. Could you run it in some UP LAPIC-only / UP LAPIC+IO-APIC / SMP modes? Or are there any affirmations that the current 'mkexec' double-way interrupts are safe? APIC/IO-APIC doc pages 25-31: ftp://download.intel.com/design/pentium/datashts/24201606.pdf Attached patches for 2.6.11 (in any order). To be applied on top of current mkexec-module + linux-mkexecpatch; linux-mkexecpatch downloadable by: cvs -q -z3 -d:pserver:anonymous:@cvs.sourceforge.net:/cvsroot/mkdump rdiff -u -r bp_linux-2_6-mkexecpatch -r linux-2_6-mkexecpatch linux according to http://mkdump.sourceforge.net/cvs.html Thanks, Lace |
|
From: Jan K. <la...@va...> - 2005-05-02 10:46:57
|
Hi, kexec patch uses APIC+IO-APIC reprogramming back to the original mode: http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc3/2.6.12-rc3-mm2/broken-out/x86-apic-virtwire-on-shutdown.patch http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc3/2.6.12-rc3-mm2/broken-out/x86_64-apic-virtwire-on-shutdown.patch kexec locks up the child 'minik' kernel during: Calibrating delay loop... if the parent 'mkexec' kernel is SMP running on VA-Linux-1220 machine. FYI this machine has some broken BIOS IO-APIC settings. mkexec uses modified patches above and it works fine even for VA-Linux-1220. Still I do not understand the reasons. kexec solution looks right to me as if IOAPIC is set to VirtualWire mode APIC LVT0 could get disabled. Unfortunately not on VA-Linux-1220. Legacy (PIC or VirtualWire) interrupts can be set in many ways by the BIOS and I believe the most safe way is just to restore their state. Implemented in the attached patch for LAPIC + IO-APIC by suspend/resume functions. Currently not yet ready for non-i386, maybe on Friday. Could you run it in some UP LAPIC-only / UP LAPIC+IO-APIC / SMP modes? Or are there any affirmations that the current 'mkexec' double-way interrupts are safe? APIC/IO-APIC doc pages 25-31: ftp://download.intel.com/design/pentium/datashts/24201606.pdf Attached patches for 2.6.11 (in any order). To be applied on top of current mkexec-module + linux-mkexecpatch; linux-mkexecpatch downloadable by: cvs -q -z3 -d:pserver:anonymous:@cvs.sourceforge.net:/cvsroot/mkdump rdiff -u -r bp_linux-2_6-mkexecpatch -r linux-2_6-mkexecpatch linux according to http://mkdump.sourceforge.net/cvs.html Thanks, Lace |
|
From: Jan K. <la...@va...> - 2005-04-26 04:31:48
|
Hi, On Mon, 25 Apr 2005 21:58:20 +0900, skunk wrote: ... > there is 1gb ram on the server and the swap partitition has the same size... > the resulting compressed file is 345mb, where should i upload it? OK, thanks for the upload. Your swap size is slightly smaller than your physical RAM and the dump is not complete there. Attached a small patch to hack to leave zeroed pages there instead although such crash report may not be of much use. You can temporarily limit your memory by some mem=984M (rather even a bit smaller) but I understand it is a pain. TODO item: mkdump should check if the requested device is big enough to hold the full dump. Thanks for pinpointing this problem. Regards, Lace |
|
From: skunk <sk...@le...> - 2005-04-25 12:58:49
|
On Monday 25 April 2005 14:21, Jan Kratochvil wrote: >=20 > Do you still have the partition intact (with the expected crash dump)? >=20 yes > Some quick check - there should be a header "MINIK_DUMP": >=20 > $ head -qc10 /dev/sda6;echo > MINIK_DUMP > $ _ >=20 i get the above header > Is this problem reproducible? >=20 > If you got the header id above: > Can you upload it somewhere for me offlist? > If it is too big, upload just its first part a bit larger than your > physical memory (such as 512MB): > head -qc 520m /dev/sda6|bzip2 >/tmp/send-me.mkd.bz2 >=20 there is 1gb ram on the server and the swap partitition has the same size... the resulting compressed file is 345mb, where should i upload it? thank you! sk |
|
From: Jan K. <la...@va...> - 2005-04-25 12:21:50
|
Hi, > > On Fri, 22 Apr 2005 18:14:01 +0200 > > skunk <sk...@le...> wrote: ... > > > # ./minik_dump_i386 /dev/sda6 dump > > > > > > but no "dump" file was created... Do you still have the partition intact (with the expected crash dump)? Some quick check - there should be a header "MINIK_DUMP": $ head -qc10 /dev/sda6;echo MINIK_DUMP $ _ Is this problem reproducible? If you got the header id above: Can you upload it somewhere for me offlist? If it is too big, upload just its first part a bit larger than your physical memory (such as 512MB): head -qc 520m /dev/sda6|bzip2 >/tmp/send-me.mkd.bz2 If you did not get the header id above and the problem is reproducible: What are the last messages during the attempted crash dump? The messages can be caught by one of: null-modem serial console, ethernet console, VMware, QEMU in this order of preference. Thanks, Lace |
|
From: skunk <sk...@le...> - 2005-04-25 08:45:40
|
yes, i did... On Monday 25 April 2005 01:08, Itsuro Oda wrote: > Hi, >=20 > Did you do this before "swap on" ? >=20 > Thanks. >=20 > On Fri, 22 Apr 2005 18:14:01 +0200 > skunk <sk...@le...> wrote: >=20 > > hi, > >=20 > > ok, i've got a crash and after the "automatic reboot" i've tried to get= a lkcd dump from the swap partitition which i > > used for the "raw dump" using the mkd2lkcd tool this way: > >=20 > > # ./minik_dump_i386 /dev/sda6 dump > >=20 > > but no "dump" file was created... > > please let me know if i'm missing something about the correct tool util= isation or if this is because there is nothing useful in the dump. > >=20 > > thank you >=20 |
|
From: Itsuro O. <od...@va...> - 2005-04-24 23:08:33
|
Hi, Did you do this before "swap on" ? Thanks. On Fri, 22 Apr 2005 18:14:01 +0200 skunk <sk...@le...> wrote: > hi, > > ok, i've got a crash and after the "automatic reboot" i've tried to get a lkcd dump from the swap partitition which i > used for the "raw dump" using the mkd2lkcd tool this way: > > # ./minik_dump_i386 /dev/sda6 dump > > but no "dump" file was created... > please let me know if i'm missing something about the correct tool utilisation or if this is because there is nothing useful in the dump. > > thank you -- Itsuro ODA <od...@va...> |
|
From: skunk <sk...@le...> - 2005-04-22 16:14:50
|
hi, ok, i've got a crash and after the "automatic reboot" i've tried to get a lkcd dump from the swap partitition which i used for the "raw dump" using the mkd2lkcd tool this way: # ./minik_dump_i386 /dev/sda6 dump but no "dump" file was created... please let me know if i'm missing something about the correct tool utilisation or if this is because there is nothing useful in the dump. thank you |
|
From: skunk <sk...@ip...> - 2005-03-09 09:59:01
|
hi, On Wednesday 09 March 2005 07:24, panxj wrote: > Hi: > I think you can use the swap partition to dump the panic kernel. But you= may try it first, type" echo 2>/proc/mkexec/stats". If it works, you may s= ee some messages on the console. unfortunately i can't do that because it's a production server and i should= avoid any downtime... however i think i'll notice if it works at next kernel panic when analyzing= the dump if any... > The developer of mkdump says that the tool to analyse the dump is on dev= elopment. However, the attach is a tool that can convert the mkdump-format = to lkcd format(thanks to Dr. Itsuro Oda). Then you may use the lkcd tools t= o catch the reason of the panic. thank you! >=20 > On Tue, 08 Mar 2005 20:13:46 -0800 > mkd...@li... wrote: >=20 > > Send Mkdump-devel mailing list submissions to > > mkd...@li... > >=20 > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.sourceforge.net/lists/listinfo/mkdump-devel > > or, via email, send a message with subject or body 'help' to > > mkd...@li... > >=20 > > You can reach the person managing the list at > > mkd...@li... > >=20 > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Mkdump-devel digest..." > >=20 > >=20 > > Today's Topics: > >=20 > > 1. dumping on swap device (skunk) > >=20 > > --__--__-- > >=20 > > Message: 1 > > From: skunk <sk...@le...> > > To: mkd...@li... > > Date: Wed, 9 Mar 2005 03:30:53 +0100 > > Subject: [Mkdump-devel] dumping on swap device > >=20 > > --nextPart1444948.uKbXQOB4Ti > > Content-Type: text/plain; > > charset=3D"us-ascii" > > Content-Transfer-Encoding: 7bit > > Content-Disposition: inline > >=20 > > hi all! > >=20 > > i'm having some troubles with a isp server and want to get a kernel bac= ktrace to work on... > > i don't have free disk space for an extra dump partitition, so i specif= ied the swap partitition in /proc/mkexec/dumpdev > > and commented out the swap partitition from /etc/fstab so it won't auto= matically activated at boot time... > > is there something wrong with this setup? will i get a useful dump at n= ext kernel panik? > > where can i find the tools necessary for extracting the dump from my sw= ap partitition? > >=20 > > thank you! > >=20 > > --nextPart1444948.uKbXQOB4Ti > > Content-Type: application/pgp-signature > >=20 > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.6 (GNU/Linux) > >=20 > > iD8DBQBCLl/hfmQMMfkPYy4RAkHFAKCV2ZGffCQT2xuKYWc3MDSUyU+BDACgufXC > > BVau4gUdbLEVCvWBO4f/3xQ=3D > > =3DPDFe > > -----END PGP SIGNATURE----- > >=20 > > --nextPart1444948.uKbXQOB4Ti-- > >=20 > >=20 > >=20 > > --__--__-- > >=20 > > _______________________________________________ > > Mkdump-devel mailing list > > Mkd...@li... > > https://lists.sourceforge.net/lists/listinfo/mkdump-devel > >=20 > >=20 > > End of Mkdump-devel Digest > >=20 >=20 |
|
From: panxj <xue...@io...> - 2005-03-09 06:23:40
|
Hi: I think you can use the swap partition to dump the panic kernel. But you may try it first, type" echo 2>/proc/mkexec/stats". If it works, you may see some messages on the console. The developer of mkdump says that the tool to analyse the dump is on development. However, the attach is a tool that can convert the mkdump-format to lkcd format(thanks to Dr. Itsuro Oda). Then you may use the lkcd tools to catch the reason of the panic. On Tue, 08 Mar 2005 20:13:46 -0800 mkd...@li... wrote: > Send Mkdump-devel mailing list submissions to > mkd...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/mkdump-devel > or, via email, send a message with subject or body 'help' to > mkd...@li... > > You can reach the person managing the list at > mkd...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mkdump-devel digest..." > > > Today's Topics: > > 1. dumping on swap device (skunk) > > --__--__-- > > Message: 1 > From: skunk <sk...@le...> > To: mkd...@li... > Date: Wed, 9 Mar 2005 03:30:53 +0100 > Subject: [Mkdump-devel] dumping on swap device > > --nextPart1444948.uKbXQOB4Ti > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > hi all! > > i'm having some troubles with a isp server and want to get a kernel backtrace to work on... > i don't have free disk space for an extra dump partitition, so i specified the swap partitition in /proc/mkexec/dumpdev > and commented out the swap partitition from /etc/fstab so it won't automatically activated at boot time... > is there something wrong with this setup? will i get a useful dump at next kernel panik? > where can i find the tools necessary for extracting the dump from my swap partitition? > > thank you! > > --nextPart1444948.uKbXQOB4Ti > Content-Type: application/pgp-signature > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.6 (GNU/Linux) > > iD8DBQBCLl/hfmQMMfkPYy4RAkHFAKCV2ZGffCQT2xuKYWc3MDSUyU+BDACgufXC > BVau4gUdbLEVCvWBO4f/3xQ= > =PDFe > -----END PGP SIGNATURE----- > > --nextPart1444948.uKbXQOB4Ti-- > > > > --__--__-- > > _______________________________________________ > Mkdump-devel mailing list > Mkd...@li... > https://lists.sourceforge.net/lists/listinfo/mkdump-devel > > > End of Mkdump-devel Digest > |
1 message has been excluded from this view by a project administrator.
