Linux 2.4.3

Linux 2.4.3

[Richard B. Johnson]

Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results
in **MASSIVE** file-system destruction. I have (had) all SCSI
disks, using the BusLogic controller.

There is something **MAJOR** going on BAD, BAD, BAD, even disks
that were not mounted got trashed.

This is (was) a 400MHz SMP machine with 256 Mb of RAM. I don't
know what else to say, since I have nothing to mount. I can
"get back" but it will take several days. I have to install a
minimum system then restore everything from tapes.

I   -- S T R O N G L Y -- suggest that nobody use this kernel with
a BusLogic SCSI controller until this problem is fixed.

This is being sent from another machine, not on the list (actually
from home where I am trying to see what happened -- I brought all
4 of my disks home). It looks like some kind of a loop. I have
a pattern written throughout one of the disks.

Cheers,

Dick Johnson

Re: Linux 2.4.3

[Mike Fedyk]

"Richard B. Johnson" wrote:
> 
> Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results

...

> I   -- S T R O N G L Y -- suggest that nobody use this kernel with
> a BusLogic SCSI controller until this problem is fixed.
> 
> This is being sent from another machine, not on the list (actually
> from home where I am trying to see what happened -- I brought all
> 4 of my disks home). It looks like some kind of a loop. I have
> a pattern written throughout one of the disks.
> 
Have you been able to recover any kernel messages or oops?

Re: Linux 2.4.2-ac12

[Scott M. Hoffman]

On Mon, 5 Mar 2001, Richard B. Johnson wrote:
>
> Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results
> in **MASSIVE** file-system destruction. I have (had) all SCSI
> disks, using the BusLogic controller.
>
> There is something **MAJOR** going on BAD, BAD, BAD, even disks
> that were not mounted got trashed.
<snip>
>
> I   -- S T R O N G L Y -- suggest that nobody use this kernel with
> a BusLogic SCSI controller until this problem is fixed.
>
> This is being sent from another machine, not on the list (actually
> from home where I am trying to see what happened -- I brought all
> 4 of my disks home). It looks like some kind of a loop. I have
> a pattern written throughout one of the disks.
>
> Cheers,
>
> Dick Johnson

 It may not be related, but out of five boot attempts, only one got past
the IDE driver stage(ie, below from 2.4.2 :
  VP_IDE: IDE controller on PCI bus 00 dev 39
  VP_IDE: chipset revision 16
  VP_IDE: not 100% native mode: will probe irqs later
  ide: Assuming 33MHz system bus speed for PIO modes; override with
  idebus=xx
  VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
      ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
      ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA)
  I've had 2.4.2 running great for the past 10 days. Need any more info?

Scott Hoffman
scott1021@mediaone.net

Re: Linux 2.4.2-ac12

[Linus Torvalds]

In article <Pine.LNX.4.32.0103052121180.1029-100000@nic-31-c31-100.mn.mediaone.net>,
Scott M. Hoffman <scott1021@mediaone.net> wrote:
>
> It may not be related, but out of five boot attempts, only one got past
>the IDE driver stage(ie, below from 2.4.2 :
>  VP_IDE: IDE controller on PCI bus 00 dev 39
>  VP_IDE: chipset revision 16
>  VP_IDE: not 100% native mode: will probe irqs later
>  ide: Assuming 33MHz system bus speed for PIO modes; override with
>  idebus=xx
>  VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
>      ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
>      ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA)
>
>  I've had 2.4.2 running great for the past 10 days. Need any more info?

I'd love to hear anything you can come up with. What's the next step in
your boot process, ie what's the part that normally shows up but doesn't
with 2.4.2-ac12? Is this using IDE-SCSI, for example?

One thing that both 2.4.3-pre3 and -ac12 do is to not have allocate a
result buffer for TEST_UNIT_READY. I don't see why that should matter,
but can you try un-doing the patch to "scsi_error.c" and see if that
makes a difference. I'm worried about this report, and the buslogic
corruption thing.. 

Justin: there's another "2.4.3-pre2 corrupts all disks on a buslogic
controller" report. The interesting part is that 2.4.3-pre2 doesn't
actually contain any buslogic changes. The only generic-scsi changes
were yours. Ideas?

		Linus

Re: Linux 2.4.2-ac12

[God]

On Mon, 5 Mar 2001, Scott M. Hoffman wrote:

> On Mon, 5 Mar 2001, Richard B. Johnson wrote:
> >
> > I   -- S T R O N G L Y -- suggest that nobody use this kernel with
> > a BusLogic SCSI controller until this problem is fixed.
> >
> > Dick Johnson
> 
>  It may not be related, but out of five boot attempts, only one got past
> the IDE driver stage(ie, below from 2.4.2 :
>   VP_IDE: IDE controller on PCI bus 00 dev 39
>   VP_IDE: chipset revision 16
>   VP_IDE: not 100% native mode: will probe irqs later
>   ide: Assuming 33MHz system bus speed for PIO modes; override with
>   idebus=xx
>   VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
>       ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
>       ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA)
>   I've had 2.4.2 running great for the past 10 days. Need any more info?

heh... I had (probably still do), the same problem.  Took me a few boots
before it would get passed the drives (this was right after upgrading to
2.4.2).  

PIIX4: IDE controller on PCI bus 00 dev 21
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALL CX6.4A, ATA DISK drive
hdb: ST33210A, ATA DISK drive
hdc: WDC AC2340F, ATA DISK drive
hdd: ATAPI CD-ROM DRIVE 40X MAXIMUM, ATAPI CD/DVD-ROM drive


Other then the fact that as I look down at the drive activity light on the
case, it's lit ... things from a IO standpoint seem to be ok .. (and I
hope it stays that way) ...

btw, for the curious:


# iostat
Linux 2.4.2 (scotch)    03/06/2001

tty:     tin       tout   avg-cpu:  %user   %nice    %sys   %idle  %iowait
           0          0              1.09    0.00    0.69    0.00   98.22
Disks:         tps   Blk_read/s   Blk_wrtn/s   Blk_read   Blk_wrtn
hdisk0        0.00         0.00         0.00          0          0
hdisk1        0.00         0.00         0.00          0          0
hdisk2        0.00         0.00         0.00          0          0

# hdparm -I /dev/hdd
hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdd: drive_cmd: error=0x04

/dev/hdd:
hdd: drive_cmd: status=0x58 { DriveReady SeekComplete DataRequest }
 HDIO_DRIVE_CMD(identify) failed: Input/output error


Doesn't matter what I have hdparm do to the drive, after running a
function the drive / bus activity light turns off ...


Thoughts?

Re: Linux 2.4.2-ac12

[Scott M. Hoffman]

On Tue, 6 Mar 2001, God wrote:

> On Mon, 5 Mar 2001, Scott M. Hoffman wrote:
>
> > On Mon, 5 Mar 2001, Richard B. Johnson wrote:
> > >
> > > I   -- S T R O N G L Y -- suggest that nobody use this kernel with
> > > a BusLogic SCSI controller until this problem is fixed.
> > >
> > > Dick Johnson
> >
> >  It may not be related, but out of five boot attempts, only one got past
> > the IDE driver stage(ie, below from 2.4.2 :
> >   VP_IDE: IDE controller on PCI bus 00 dev 39
> >   VP_IDE: chipset revision 16
> >   VP_IDE: not 100% native mode: will probe irqs later
> >   ide: Assuming 33MHz system bus speed for PIO modes; override with
> >   idebus=xx
> >   VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
> >       ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
> >       ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA)
> >   I've had 2.4.2 running great for the past 10 days. Need any more info?
>
> heh... I had (probably still do), the same problem.  Took me a few boots
> before it would get passed the drives (this was right after upgrading to
> 2.4.2).
>
> PIIX4: IDE controller on PCI bus 00 dev 21
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
>     ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
> hda: QUANTUM FIREBALL CX6.4A, ATA DISK drive
> hdb: ST33210A, ATA DISK drive
> hdc: WDC AC2340F, ATA DISK drive
> hdd: ATAPI CD-ROM DRIVE 40X MAXIMUM, ATAPI CD/DVD-ROM drive
>
>
> Other then the fact that as I look down at the drive activity light on the
> case, it's lit ... things from a IO standpoint seem to be ok .. (and I
> hope it stays that way) ...
>
> btw, for the curious:
>
>
> # iostat
> Linux 2.4.2 (scotch)    03/06/2001
>
> tty:     tin       tout   avg-cpu:  %user   %nice    %sys   %idle  %iowait
>            0          0              1.09    0.00    0.69    0.00   98.22
> Disks:         tps   Blk_read/s   Blk_wrtn/s   Blk_read   Blk_wrtn
> hdisk0        0.00         0.00         0.00          0          0
> hdisk1        0.00         0.00         0.00          0          0
> hdisk2        0.00         0.00         0.00          0          0
>
> # hdparm -I /dev/hdd
> hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdd: drive_cmd: error=0x04
>
> /dev/hdd:
> hdd: drive_cmd: status=0x58 { DriveReady SeekComplete DataRequest }
>  HDIO_DRIVE_CMD(identify) failed: Input/output error
>
>
> Doesn't matter what I have hdparm do to the drive, after running a
> function the drive / bus activity light turns off ...
>
>
> Thoughts?

 I have not had problems with 2.4.2, just tried 2.4.2-ac12.  About the IDE
stage it just reboots.
 As for your iostat output, which version do you have?  The stock one with
RH7 needs to be upgraded to work with 2.4 kernels.  I'm using 3.3.5 now,
which seems to work.

Re: Linux 2.4.2-ac12

[Alan Cox]

>  I have not had problems with 2.4.2, just tried 2.4.2-ac12.  About the IDE
> stage it just reboots.

Does ac11 also reboot like that. -ac is currently testing versions of the new
VIA IDE driver so knowing if the latest update did that would be very 
useful

Re: Linux 2.4.2-ac12

[Scott M. Hoffman]

On Tue, 6 Mar 2001, Alan Cox wrote:

> >  I have not had problems with 2.4.2, just tried 2.4.2-ac12.  About the IDE
> > stage it just reboots.
>
> Does ac11 also reboot like that. -ac is currently testing versions of the new
> VIA IDE driver so knowing if the latest update did that would be very
> useful
>
 I won't be able to try ac11 until late tonight as that is my home PC that
has the VIA chips.  I'll let you know
 Also, these patches should be applied to 2.4.2, right? I'm using a 2.4.1
tree patched to 2.4.2, then applied ac12.

Scott Hoffman

Re: Linux 2.4.2-ac12

[Alan Cox]

>  I won't be able to try ac11 until late tonight as that is my home PC that
> has the VIA chips.  I'll let you know
>  Also, these patches should be applied to 2.4.2, right? I'm using a 2.4.1
> tree patched to 2.4.2, then applied ac12.

Yep you applied it right by the sounds of it.

Re: Linux 2.4.2-ac12

[Wayne Whitney]

In mailing-lists.linux-kernel, you wrote:

> -ac is currently testing versions of the new VIA IDE driver 

What is the relationship between the version 3.21 in -ac12 and the
version 4.3 that was distributed on this list a week or two ago?

Cheers, Wayne

Re: Linux 2.4.2-ac12, ac11 no good either

[Scott M. Hoffman]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 626 bytes --]

On Tue, 6 Mar 2001, Alan Cox wrote:

> >  I have not had problems with 2.4.2, just tried 2.4.2-ac12.  About the IDE
> > stage it just reboots.
>
> Does ac11 also reboot like that. -ac is currently testing versions of the new
> VIA IDE driver so knowing if the latest update did that would be very
> useful
>
 Okay, I was able to get home early and tried ac11.  Thought it was
working, until it got to about starting GPM mouse services, and rebooted.
Tried it again at run level s, and it got about 40% through fsck before
rebooting again.
  I attached my .config from ac11, which did not change from the ac12
compile.

Scott


[-- Attachment #2: Type: TEXT/PLAIN, Size: 17421 bytes --]

#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y

#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PM=y
# CONFIG_ACPI is not set
# CONFIG_APM is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_FTP is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
# CONFIG_IP_NF_MATCH_MAC is not set
# CONFIG_IP_NF_MATCH_MARK is not set
# CONFIG_IP_NF_MATCH_MULTIPORT is not set
# CONFIG_IP_NF_MATCH_TOS is not set
# CONFIG_IP_NF_MATCH_TCPMSS is not set
CONFIG_IP_NF_MATCH_STATE=m
# CONFIG_IP_NF_MATCH_UNCLEAN is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
# CONFIG_IP_NF_TARGET_MIRROR is not set
# CONFIG_IP_NF_NAT is not set
# CONFIG_IP_NF_MANGLE is not set
CONFIG_IP_NF_TARGET_LOG=m
# CONFIG_IP_NF_TARGET_TCPMSS is not set
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD7409 is not set
# CONFIG_AMD7409_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_PIIX_TUNING is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_BLK_DEV_OSB4 is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y

#
# SCSI support
#
CONFIG_SCSI=m
# CONFIG_BLK_DEV_SD is not set
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=m
CONFIG_SCSI_DEBUG_QUEUES=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_NCR53C8XX is not set
CONFIG_SCSI_SYM53C8XX=m
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=4
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_PQS_PDS is not set
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_DEBUG is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
CONFIG_TULIP=m
# CONFIG_DE4X5 is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_EEPRO100_PM is not set
# CONFIG_LNE390 is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Input core support
#
# CONFIG_INPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set

#
# Joysticks
#
# CONFIG_JOYSTICK is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_I810 is not set
CONFIG_AGP_VIA=y
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_ALI is not set
CONFIG_DRM=y
CONFIG_DRM_TDFX=m
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_MGA is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=m
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_TMPFS is not set
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_MINIX_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_SYSV_FS_WRITE is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_NFS_FS is not set
# CONFIG_NFS_V3 is not set
# CONFIG_ROOT_NFS is not set
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_SUNRPC is not set
# CONFIG_LOCKD is not set
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VIDEO_SELECT is not set
# CONFIG_MDA_CONSOLE is not set

#
# Frame-buffer support
#
# CONFIG_FB is not set

#
# Sound
#
CONFIG_SOUND=m
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
CONFIG_SOUND_ES1371=m
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set
# CONFIG_SOUND_TVMIXER is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_BUGVERBOSE is not set

Re: Linux 2.4.2-ac12

[God]

On Tue, 6 Mar 2001, Alan Cox wrote:

> >  I have not had problems with 2.4.2, just tried 2.4.2-ac12.  About the IDE
> > stage it just reboots.
> 
> Does ac11 also reboot like that. -ac is currently testing versions of the new
> VIA IDE driver so knowing if the latest update did that would be very 
> useful
> 


Stock 2.4.2 kernel.  It (so far), hasn't happened again .. the drive led
is still screwed though.   It's weird, the other drives seem to seek at
odd times too (like when they aren't even mounted).

Re: Linux 2.4.2-ac12

[God]

On Tue, 6 Mar 2001, Scott M. Hoffman wrote:

> On Tue, 6 Mar 2001, God wrote:
> 
> > # iostat
> > Linux 2.4.2 (scotch)    03/06/2001

> 
>  I have not had problems with 2.4.2, just tried 2.4.2-ac12.  About the IDE
> stage it just reboots.

Same chipset/mb? 

>  As for your iostat output, which version do you have?  The stock one with
> RH7 needs to be upgraded to work with 2.4 kernels.  I'm using 3.3.5 now,
> which seems to work.


Version of?

Re: Linux 2.4.3

[Linus Torvalds]

In article <Pine.LNX.4.21.0103052124250.1132-100000@groveland.analogic.com>,
Richard B. Johnson <johnson@groveland.analogic.com> wrote:
>
>I   -- S T R O N G L Y -- suggest that nobody use this kernel with
>a BusLogic SCSI controller until this problem is fixed.

Ho humm..

Anybody who has any ideas or input, please holler.  There are no actual
BusLogic controller changes in the current 2.4.3-pre kernels at all, so
there's something else going on.

There's a new aic7xxx driver there - did you enable support for that? I
wonder if there could be some inter-action: the aic7xxx driver tries to
probe every PCI SCSI controller because they are basically hard to ID
any other way (no single vendor/id combination, or even a simple
pattern).  But it has some rather careful internal logic to filter out
all non-aic7xxx controllers, so this really doesn't look likely.

If you didn't compile aic7xxx in, the only other SCSI change (apart from
a lot of spelling fixes in comments etc) is some trivial error handling,
like changing scsi_test_unit_ready to not have a result buffer (because
it doesn't have a result except for the regular sense buffer).  Which
again certainly shouldn't be able to matter at all. 

Ideas?

		Linus

Re: Linux 2.4.3

[Krzysztof Halasa]

"Richard B. Johnson" <johnson@groveland.analogic.com> writes:

> Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results
> in **MASSIVE** file-system destruction. I have (had) all SCSI
> disks, using the BusLogic controller.
> 
> There is something **MAJOR** going on BAD, BAD, BAD, even disks
> that were not mounted got trashed.

What gcc version did you use to compile it?
-- 
Krzysztof Halasa
Network Administrator

Re: Linux 2.4.3

[David Weinehall]

On Mon, Mar 05, 2001 at 09:35:30PM -0500, Richard B. Johnson wrote:
> 
> Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results
> in **MASSIVE** file-system destruction. I have (had) all SCSI
> disks, using the BusLogic controller.
> 
> There is something **MAJOR** going on BAD, BAD, BAD, even disks
> that were not mounted got trashed.
> 
> This is (was) a 400MHz SMP machine with 256 Mb of RAM. I don't
> know what else to say, since I have nothing to mount. I can
> "get back" but it will take several days. I have to install a
> minimum system then restore everything from tapes.
> 
> I   -- S T R O N G L Y -- suggest that nobody use this kernel with
> a BusLogic SCSI controller until this problem is fixed.
> 
> This is being sent from another machine, not on the list (actually
> from home where I am trying to see what happened -- I brought all
> 4 of my disks home). It looks like some kind of a loop. I have
> a pattern written throughout one of the disks.

Anything new on this? It sounds rather strange considering your
unmounted disks got trashed too, so either it's a problem with the
SCSI subsystem (or the driver; it might be a bug that got triggered
by something else) or some sort of hardware failure.

What kind of pattern was repeated on the disk, by the way? Maybe this
could shed some light unto what happened.


/David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

Re: Linux 2.4.3

[Richard B. Johnson]

On Thu, 8 Mar 2001, David Weinehall wrote:

> On Mon, Mar 05, 2001 at 09:35:30PM -0500, Richard B. Johnson wrote:
> > 
> > Attempts to run linux-2.4.3-pre2 on chaos.analogic.com results
> > in **MASSIVE** file-system destruction. I have (had) all SCSI
> > disks, using the BusLogic controller.
> > 
> > There is something **MAJOR** going on BAD, BAD, BAD, even disks
> > that were not mounted got trashed.
> > 
> > This is (was) a 400MHz SMP machine with 256 Mb of RAM. I don't
> > know what else to say, since I have nothing to mount. I can
> > "get back" but it will take several days. I have to install a
> > minimum system then restore everything from tapes.
> > 
> > I   -- S T R O N G L Y -- suggest that nobody use this kernel with
> > a BusLogic SCSI controller until this problem is fixed.
> > 
> > This is being sent from another machine, not on the list (actually
> > from home where I am trying to see what happened -- I brought all
> > 4 of my disks home). It looks like some kind of a loop. I have
> > a pattern written throughout one of the disks.
> 
> Anything new on this? It sounds rather strange considering your
> unmounted disks got trashed too, so either it's a problem with the
> SCSI subsystem (or the driver; it might be a bug that got triggered
> by something else) or some sort of hardware failure.
> 
> What kind of pattern was repeated on the disk, by the way? Maybe this
> could shed some light unto what happened.
> 

Here is the pattern: Repeated at 0x1000 intervals. It looks like
the first page of the kernel, matched here at 0x00100000.

The "Unknown interrupt" text was a dead giveaway.


00100000 FC B8 18 00 00 00 8E D8 8E C0 8E E0 8E E8 66 09 ..............f.
00100010 DB 74 17 83 3D AC 53 25 00 00 74 26 0F 20 E0 0B .t..=.S%..t&. ..
00100020 05 AC 53 25 00 0F 22 E0 EB 18 BF 00 20 10 00 B8 ..S%.."..... ...
00100030 07 00 00 00 AB 05 00 10 00 00 81 FF 00 40 10 00 .............@..
00100040 75 F2 B8 00 10 10 00 0F 22 D8 0F 20 C0 0D 00 00 u.......".. ....
00100050 00 80 0F 22 C0 EB 00 B8 5E 00 10 C0 FF E0 0F B2 ..."....^.......
00100060 25 30 02 10 C0 66 09 DB 74 05 6A 00 9D EB 5C 31 %0...f..t.j...\1
00100070 C0 BF F0 E8 23 C0 B9 50 76 27 C0 29 F9 F3 AA E8 ....#..Pv'.)....
00100080 76 01 00 00 6A 00 9D BF 00 40 10 C0 B9 00 02 00 v...j....@......
00100090 00 FC F3 A5 31 C0 B9 00 02 00 00 F3 AB 8B 35 28 ....1.........5(
001000A0 42 10 C0 21 F6 75 18 66 81 3D 20 00 09 00 3F A3 B..!.u.f.= ...?.
001000B0 75 19 0F B7 35 22 00 09 00 81 C6 00 00 09 00 BF u...5"..........
001000C0 00 48 10 C0 B9 00 02 00 00 F3 A5 C7 05 88 2C 21 .H............,!
001000D0 C0 FF FF FF FF C7 05 80 2C 21 C0 03 00 00 00 9C ........,!......
001000E0 58 89 C1 35 00 00 04 00 50 9D 9C 58 31 C8 25 00 X..5....P..X1.%.
001000F0 00 04 00 74 79 C7 05 80 2C 21 C0 04 00 00 00 89 ...ty...,!......

00100100 C8 35 00 00 20 00 50 9D 9C 58 31 C8 51 9D 25 00 .5.. .P..X1.Q.%.
00100110 00 20 00 74 4A 31 C0 0F A2 A3 88 2C 21 C0 89 1D . .tJ1.....,!...
00100120 90 2C 21 C0 89 15 94 2C 21 C0 89 0D 98 2C 21 C0 .,!....,!....,!.
00100130 09 C0 74 2B B8 01 00 00 00 0F A2 88 C1 80 E4 0F ..t+............
00100140 88 25 80 2C 21 C0 24 F0 C0 E8 04 A2 82 2C 21 C0 .%.,!.$......,!.
00100150 80 E1 0F 88 0D 83 2C 21 C0 89 15 8C 2C 21 C0 0F ......,!....,!..
00100160 20 C0 25 11 00 00 80 0D 22 00 05 00 EB 0D 51 9D  .%.....".....Q.
00100170 0F 20 C0 25 11 00 00 80 83 C8 02 0F 22 C0 E8 4F . .%........"..O
00100180 00 00 00 FE 05 D1 01 10 C0 0F 01 15 7A 02 10 C0 ............z...
00100190 0F 01 1D 72 02 10 C0 EA 9E 01 10 C0 10 00 B8 18 ...r............
001001A0 00 00 00 8E D8 8E C0 8E E0 8E E8 B8 18 00 00 00 ................
001001B0 8E D0 31 C0 0F 00 D0 FC 8A 0D D1 01 10 C0 80 F9 ..1.............
001001C0 01 74 07 E8 78 B7 12 00 EB 05 E8 11 66 12 00 EB .t..x.......f...
001001D0 FE 02 C6 05 86 2C 21 C0 00 0F 06 DB E3 9B DF E0 .....,!.........
001001E0 3C 00 74 0C 0F 20 C0 83 F0 04 0F 22 C0 C3 89 F6 <.t.. ....."....
001001F0 C6 05 86 2C 21 C0 01 DB E4 C3 8D 15 50 02 10 C0 ...,!.......P...

00100200 B8 00 00 10 00 66 89 D0 66 BA 00 8E 8D 3D 00 A0 .....f..f....=..
00100210 23 C0 B9 00 01 00 00 89 07 89 57 04 83 C7 08 49 #.........W....I
00100220 75 F5 C3 8D B6 00 00 00 00 8D BC 27 00 00 00 00 u..........'....
00100230 00 54 FF D3 18 00 00 00 55 6E 6B 6E 6F 77 6E 20 .T......Unknown 
00100240 69 6E 74 65 72 72 75 70 74 0A 00 90 8D 74 26 00 interrupt....t&.
00100250 FC 50 51 52 06 1E B8 18 00 00 00 8E D8 8E C0 68 .PQR...........h
00100260 38 02 10 C0 E8 B7 67 01 00 58 1F 07 5A 59 58 CF 8.....g..X..ZYX.
00100270 00 00 FF 07 00 A0 23 C0 00 00 5F 04 80 11 21 C0 ......#..._...!.
00100280 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00100290 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
001002A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
001002B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
001002C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
001002D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
001002E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
001002F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................


This get triggered if:

(1)	The machine is booted via initrd.
(2)	An attempt is made to use the RAM disk after it's booted.
(3)	A BusLogic controller.


Now, if I use /dev/ram1, instead of /dev/ram0 (1:1 instead of 1:0), the
problem doesn't show up. It appears as though change_root() leaves
something dangling so that a write to what used to be the root file-
system, results in some pointer/code/whatever corruption. Ultimately
this leads to unexpected SCSI writes.


Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

Re: Linux 2.4.2-ac12

[Scott M. Hoffman]

On Mon, 5 Mar 2001, Linus Torvalds wrote:

> In article <Pine.LNX.4.32.0103052121180.1029-100000@nic-31-c31-100.mn.mediaone.net>,
> Scott M. Hoffman <scott1021@mediaone.net> wrote:
> >
> > It may not be related, but out of five boot attempts, only one got past
> >the IDE driver stage(ie, below from 2.4.2 :
> >  VP_IDE: IDE controller on PCI bus 00 dev 39
> >  VP_IDE: chipset revision 16
> >  VP_IDE: not 100% native mode: will probe irqs later
> >  ide: Assuming 33MHz system bus speed for PIO modes; override with
> >  idebus=xx
> >  VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
> >      ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
> >      ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA)
> >
> >  I've had 2.4.2 running great for the past 10 days. Need any more info?
>
> I'd love to hear anything you can come up with. What's the next step in
> your boot process, ie what's the part that normally shows up but doesn't
> with 2.4.2-ac12? Is this using IDE-SCSI, for example?
>
> One thing that both 2.4.3-pre3 and -ac12 do is to not have allocate a
> result buffer for TEST_UNIT_READY. I don't see why that should matter,
> but can you try un-doing the patch to "scsi_error.c" and see if that
> makes a difference. I'm worried about this report, and the buslogic
> corruption thing..
>
> Justin: there's another "2.4.3-pre2 corrupts all disks on a buslogic
> controller" report. The interesting part is that 2.4.3-pre2 doesn't
> actually contain any buslogic changes. The only generic-scsi changes
> were yours. Ideas?
>
> 		Linus
>

  Just trying 2.4.3-pre2 now. It appears to be working fine. I used the
same config from my ac11-12 attempts. My systems problem with ac11-12 must
not be something common between them.  Hope this helps.

Scott

Re: Linux 2.4.2-ac12

[Alan Cox]

>   Just trying 2.4.3-pre2 now. It appears to be working fine. I used the
> same config from my ac11-12 attempts. My systems problem with ac11-12 must
> not be something common between them.  Hope this helps.

It helps a lot. I now know not to submit the VIA ide driver to Linus until
further investigation is completed.

Re: Linux 2.4.2-ac12

[Andre Hedrick]

On Tue, 6 Mar 2001, Alan Cox wrote:

> >   Just trying 2.4.3-pre2 now. It appears to be working fine. I used the
> > same config from my ac11-12 attempts. My systems problem with ac11-12 must
> > not be something common between them.  Hope this helps.
> 
> It helps a lot. I now know not to submit the VIA ide driver to Linus until
> further investigation is completed.

Now you know why I pawned it off the VIA-core to Vojtech ;-)
It is a mess!

Andre Hedrick
Linux ATA Development