2.6.3-mm4 / 2.5 Gb memory / sym53c8xx_2 won't boot
After upgrading my memory from 1 Gb to 2.5 Gb my 2.6.3-mm4 kernel wouldn't boot anymore.
It hang when detecting the scsi-chip.
I had in my .config:
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
the default value.
The scsi bus kept resetting before detecting any devices. Interestingly, 2.6.3-mm1 did boot with that .config setting. Once I recompiled 2.6.3-mm4 with
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
it booted (and worked) fine.
So, something regressed in 2.6.3-mm4 versus 2.6.3-mm1, so the default setting didn't work correctly anymore.
If there is anything I can test, please let me know.
Kind regards,
Jurriaan
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
00:0a.0 SCSI storage controller: LSI Logic / Symbios Logic 53c860 (rev 13)
00:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
00:0d.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
00:0e.0 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
00:0e.1 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)
00:0a.0 SCSI storage controller: LSI Logic / Symbios Logic 53c860 (rev 13)
Subsystem: LSI Logic / Symbios Logic: Unknown device 1000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 16000ns max), Cache Line Size: 0x10 (64 bytes)
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at a000 [size=256]
Region 1: Memory at de000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Linux version 2.6.3-mm4 (jurriaan@middle) (gcc version 3.3.3 (Debian)) #4 Tue Mar 2 19:32:33 CET 2004 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000009fff0000 (usable)
BIOS-e820: 000000009fff0000 - 000000009fff3000 (ACPI NVS)
BIOS-e820: 000000009fff3000 - 00000000a0000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
1663MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f5aa0
<snip>
sym0: <860> rev 0x13 at pci 0000:00:0a.0 irq 18
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
<here the kernel hang previously, ABORT timed out and it kept resetting>
scsi0 : sym-2.1.18f
Vendor: TOSHIBA Model: DVD-ROM SD-M1401 Rev: 1007 Type: CD-ROM ANSI SCSI revision: 02 Vendor: PLEXTOR Model: CD-ROM PX-32TS Rev: 1.02 Type: CD-ROM ANSI SCSI revision: 02
st: Version 20040213, fixed bufsize 32768, s/g segs 256 sym0:1: FAST-20 SCSI 20.0 MB/s ST (50.0 ns, offset 8)
sr0: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray Attached scsi CD-ROM sr0 at scsi0, channel 0, id 1, lun 0 sym0:2: FAST-20 SCSI 20.0 MB/s ST (50.0 ns, offset 8)
sr1: scsi-1 drive
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 2, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 1, lun 0, type 5 Attached scsi generic sg1 at scsi0, channel 0, id 2, lun 0, type 5matroxfb_crtc2: secondary head of fb0 was registered as fb1
.configCONFIG_X86=yCONFIG_MMU=yCONFIG_UID16=yCONFIG_GENERIC_ISA_DMA=yCONFIG_EXPERIMENTAL=yCONFIG_BROKEN=yCONFIG_BROKEN_ON_SMP=yCONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSCTL=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_KALLSYMS=yCONFIG_FUTEX=yCONFIG_EPOLL=yCONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_AS=yCONFIG_IOSCHED_DEADLINE=yCONFIG_IOSCHED_CFQ=yCONFIG_MODULES=yCONFIG_MODULE_UNLOAD=yCONFIG_OBSOLETE_MODPARM=yCONFIG_KMOD=yCONFIG_X86_PC=yCONFIG_MK7=yCONFIG_X86_CMPXCHG=yCONFIG_X86_XADD=yCONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_X86_GOOD_APIC=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_X86_USE_3DNOW=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_PREEMPT=yCONFIG_X86_UP_APIC=yCONFIG_X86_UP_IOAPIC=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_TSC=yCONFIG_X86_MCE=yCONFIG_X86_MCE_NONFATAL=yCONFIG_HIGHMEM4G=yCONFIG_HIGHMEM=yCONFIG_HIGHPTE=yCONFIG_MTRR=yCONFIG_HAVE_DEC_LOCK=yCONFIG_PM=yCONFIG_ACPI=yCONFIG_ACPI_BOOT=yCONFIG_ACPI_INTERPRETER=yCONFIG_ACPI_SLEEP=yCONFIG_ACPI_SLEEP_PROC_FS=yCONFIG_ACPI_AC=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_FAN=yCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_THERMAL=yCONFIG_ACPI_DEBUG=yCONFIG_ACPI_BUS=yCONFIG_ACPI_EC=yCONFIG_ACPI_POWER=yCONFIG_ACPI_PCI=yCONFIG_ACPI_SYSTEM=yCONFIG_ACPI_RELAXED_AML=yCONFIG_PCI=yCONFIG_PCI_GOANY=yCONFIG_PCI_BIOS=yCONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_NAMES=yCONFIG_ISA=yCONFIG_BINFMT_ELF=yCONFIG_BINFMT_AOUT=yCONFIG_BINFMT_MISC=yCONFIG_PARPORT=yCONFIG_PARPORT_PC=yCONFIG_PARPORT_PC_CML1=yCONFIG_PARPORT_1284=yCONFIG_BLK_DEV_FD=yCONFIG_BLK_DEV_LOOP=yCONFIG_IDE=yCONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_BLK_DEV_IDECD=yCONFIG_BLK_DEV_IDESCSI=yCONFIG_IDE_GENERIC=yCONFIG_BLK_DEV_IDEPCI=yCONFIG_IDEPCI_SHARE_IRQ=yCONFIG_BLK_DEV_IDEDMA_PCI=yCONFIG_IDEDMA_PCI_AUTO=yCONFIG_BLK_DEV_ADMA=yCONFIG_BLK_DEV_AMD74XX=yCONFIG_BLK_DEV_HPT366=yCONFIG_BLK_DEV_PDC202XX_OLD=yCONFIG_BLK_DEV_VIA82CXXX=yCONFIG_BLK_DEV_IDEDMA=yCONFIG_IDEDMA_AUTO=yCONFIG_SCSI=yCONFIG_SCSI_PROC_FS=yCONFIG_BLK_DEV_SD=yCONFIG_CHR_DEV_ST=yCONFIG_BLK_DEV_SR=yCONFIG_CHR_DEV_SG=yCONFIG_SCSI_MULTI_LUN=yCONFIG_SCSI_REPORT_LUNS=yCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_SYM53C8XX_2=yCONFIG_SCSI_QLA2XXX=yCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_LINEAR=yCONFIG_MD_RAID0=yCONFIG_MD_RAID1=yCONFIG_MD_RAID5=yCONFIG_NET=yCONFIG_PACKET=yCONFIG_UNIX=yCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_SYN_COOKIES=yCONFIG_IPV6_SCTP__=yCONFIG_NETDEVICES=yCONFIG_DUMMY=yCONFIG_NET_ETHERNET=yCONFIG_MII=yCONFIG_NET_TULIP=yCONFIG_TULIP=yCONFIG_TULIP_MWI=yCONFIG_TULIP_MMIO=yCONFIG_NET_PCI=yCONFIG_E100=yCONFIG_8139CP=yCONFIG_8139TOO=yCONFIG_VIA_RHINE=yCONFIG_VIA_RHINE_MMIO=y
# ISDN subsystemCONFIG_INPUT=yCONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_SOUND_GAMEPORT=yCONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=yCONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ATKBD=yCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_INPUT_MISC=yCONFIG_INPUT_PCSPKR=yCONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_CORE=yCONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_PRINTER=yCONFIG_WATCHDOG=yCONFIG_SOFT_WATCHDOG=yCONFIG_RTC=yCONFIG_AGP=yCONFIG_AGP_VIA=yCONFIG_DRM=yCONFIG_DRM_MGA=yCONFIG_RAW_DRIVER=yCONFIG_I2C=mCONFIG_I2C_CHARDEV=mCONFIG_I2C_ALGOBIT=mCONFIG_I2C_ISA=mCONFIG_I2C_VIAPRO=mCONFIG_I2C_SENSOR=mCONFIG_SENSORS_EEPROM=mCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_W83781D=mCONFIG_FB=yCONFIG_VIDEO_SELECT=yCONFIG_FB_MATROX=yCONFIG_FB_MATROX_G450=yCONFIG_FB_MATROX_G100=yCONFIG_VGA_CONSOLE=yCONFIG_DUMMY_CONSOLE=yCONFIG_FRAMEBUFFER_CONSOLE=yCONFIG_PCI_CONSOLE=yCONFIG_FONTS=y
CONFIG_FONT_SUN12x22=yCONFIG_LOGO=yCONFIG_LOGO_LINUX_MONO=yCONFIG_LOGO_LINUX_VGA16=yCONFIG_LOGO_LINUX_CLUT224=yCONFIG_SOUND=yCONFIG_SND=yCONFIG_SND_SEQUENCER=yCONFIG_SND_OSSEMUL=yCONFIG_SND_MIXER_OSS=yCONFIG_SND_PCM_OSS=yCONFIG_SND_SEQUENCER_OSS=yCONFIG_SND_RTCTIMER=yCONFIG_SND_EMU10K1=yCONFIG_SND_CMIPCI=yCONFIG_SND_INTEL8X0=yCONFIG_SND_VIA82XX=y
# Open Sound SystemCONFIG_USB=yCONFIG_USB_DEVICEFS=yCONFIG_USB_EHCI_HCD=yCONFIG_USB_UHCI_HCD=yCONFIG_USB_PRINTER=yCONFIG_USB_HID=yCONFIG_USB_HIDINPUT=yCONFIG_EXT2_FS=yCONFIG_EXT3_FS=yCONFIG_EXT3_FS_XATTR=yCONFIG_JBD=yCONFIG_FS_MBCACHE=yCONFIG_REISERFS_FS=yCONFIG_XFS_FS=yCONFIG_ISO9660_FS=yCONFIG_JOLIET=yCONFIG_UDF_FS=yCONFIG_FAT_FS=yCONFIG_VFAT_FS=yCONFIG_NTFS_FS=yCONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_RAMFS=yCONFIG_NFS_FS=yCONFIG_NFS_V3=yCONFIG_LOCKD=yCONFIG_LOCKD_V4=yCONFIG_SUNRPC=yCONFIG_MSDOS_PARTITION=yCONFIG_NLS=yCONFIG_NLS_CODEPAGE_437=yCONFIG_NLS_ISO8859_1=yCONFIG_DEBUG_KERNEL=yCONFIG_EARLY_PRINTK=yCONFIG_MAGIC_SYSRQ=yCONFIG_FRAME_POINTER=yCONFIG_X86_FIND_SMP_CONFIG=yCONFIG_X86_MPPARSE=yCONFIG_CRC32=yCONFIG_X86_BIOS_REBOOT=yCONFIG_PC=y
Signature · 3 lines
That is the key to the desert. Nothing lasts. And nothing changes. Michelle West - Sea of Sorrows Debian (Unstable) GNU/Linux 2.6.3-mm4 3940 bogomips 0.42 0.19
Quoted 15 lines · Jurriaan
After upgrading my memory from 1 Gb to 2.5 Gb my 2.6.3-mm4 kernel wouldn't boot anymore.
It hang when detecting the scsi-chip.
I had in my .config:
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1the default value.
The scsi bus kept resetting before detecting any devices. Interestingly, 2.6.3-mm1 did boot with that .config setting. Once I recompiled 2.6.3-mm4 with
Quoted 6 lines
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0it booted (and worked) fine.
So, something regressed in 2.6.3-mm4 versus 2.6.3-mm1, so the default setting didn't work correctly anymore.
I don't know what caused this - there are a few patches in there which touch the DMA and BIO highmem areas. Plus always the latest scsi development tree.
Quoted 1 line
If there is anything I can test, please let me know.
Could you test Linus's current tree? The first link at
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/.
If this bug hasn't hit Linus's tree yet, it will soon do so...
From: Andrew Morton <[email protected]>
Date: Tue, Mar 02, 2004 at 02:47:57PM -0800
Quoted 27 lines
Quoted 15 lines · Jurriaan
After upgrading my memory from 1 Gb to 2.5 Gb my 2.6.3-mm4 kernel wouldn't boot anymore.
It hang when detecting the scsi-chip.
I had in my .config:
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1the default value.
The scsi bus kept resetting before detecting any devices. Interestingly, 2.6.3-mm1 did boot with that .config setting. Once I recompiled 2.6.3-mm4 with
Quoted 6 lines
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0it booted (and worked) fine.
So, something regressed in 2.6.3-mm4 versus 2.6.3-mm1, so the default setting didn't work correctly anymore.
I don't know what caused this - there are a few patches in there which touch the DMA and BIO highmem areas. Plus always the latest scsi development tree.
Quoted 7 lines
Quoted 1 line
If there is anything I can test, please let me know.
Could you test Linus's current tree? The first link at
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/.If this bug hasn't hit Linus's tree yet, it will soon do so...
It probably will, since it's not in Linus's tree as of
cset-20040303_0509.txt
ie 2.6.4-rc1-mm1 + cset-20040303_0509 does boot with CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1, and 2.6.3-mm4 doesn't.
Kind regards,
Jurriaan
Signature · 4 lines
HORROR FILM WISDOM: 9. If your car runs out of gas at night, do not go to the nearby deserted-looking house to phone for help. Debian (Unstable) GNU/Linux 2.6.3-mm4 3940 bogomips 0.00 0.00
Quoted 11 lines · Jurriaan
Quoted 6 lines
Could you test Linus's current tree? The first link at
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/.If this bug hasn't hit Linus's tree yet, it will soon do so...
It probably will, since it's not in Linus's tree as of
cset-20040303_0509.txt
ie 2.6.4-rc1-mm1 + cset-20040303_0509 does boot with
You meant 2.6.4-rc1, I assume?
Quoted 1 line
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1, and 2.6.3-mm4 doesn't.
I continue to be stumped. Could you please test a Linus tree, plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.4-rc1/2.6.4-rc1-mm2/broken-out/bk-scsi.patch
and
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.4-rc1/2.6.4-rc1-mm2/broken-out/dma_sync_for_device-cpu.patch
?
From: Andrew Morton <[email protected]>
Date: Wed, Mar 03, 2004 at 03:38:30PM -0800
Quoted 17 lines
Quoted 11 lines · Jurriaan
Quoted 6 lines
Could you test Linus's current tree? The first link at
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/.If this bug hasn't hit Linus's tree yet, it will soon do so...
It probably will, since it's not in Linus's tree as of
cset-20040303_0509.txt
ie 2.6.4-rc1-mm1 + cset-20040303_0509 does boot with
You meant 2.6.4-rc1, I assume?Quoted 1 line
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1, and 2.6.3-mm4 doesn't.
Quoted 8 lines
I continue to be stumped. Could you please test a Linus tree, plus
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.4-rc1/2.6.4-rc1-mm2/broken-out/bk-scsi.patch
and
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.4-rc1/2.6.4-rc1-mm2/broken-out/dma_sync_for_device-cpu.patch
I'm now stumped also. I tested
2.6.4-rc2 CONFIG.*DMA.*MODE=1: ok 2.6.4-rc2+bk-scsi CONFIG.*DMA.*MODE=1: ok 2.6.4-rc2+bk-scsi+dma_sync CONFIG.*DMA.*MODE=1: ok
then I recompiled a fresh 2.6.3-mm4 kernel from source with CONFIG.*DMA.*MODE=1, and it booted also.
So it appears to (have) be(en) a Heisenbug. It was there, when I recompiled, it was gone.
Oh well,
Jurriaan
Signature · 6 lines
You aren't going to do anything about it then?
Of course I am.
What?
I'm going to ignore it.
David Eddings - The Sapphire Rose
Debian (Unstable) GNU/Linux 2.6.3-mm4 3940 bogomips 1.91 0.84