Re: Linux 2.4.2-ac12
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). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
> 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
On Mon, 5 Mar 2001, Linus Torvalds wrote: > In article <[EMAIL PROTECTED]>, > Scott M. Hoffman <[EMAIL PROTECTED]> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12, ac11 no good either
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 # # 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
Re: Linux 2.4.2-ac12
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
> 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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.090.000.690.00 98.22
> Disks: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
> hdisk00.00 0.00 0.00 0 0
> hdisk10.00 0.00 0.00 0 0
> hdisk20.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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.090.000.690.00 98.22
Disks: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
hdisk00.00 0.00 0.00 0 0
hdisk10.00 0.00 0.00 0 0
hdisk20.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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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.090.000.690.00 98.22
Disks: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
hdisk00.00 0.00 0.00 0 0
hdisk10.00 0.00 0.00 0 0
hdisk20.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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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.090.000.690.00 98.22
Disks: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
hdisk00.00 0.00 0.00 0 0
hdisk10.00 0.00 0.00 0 0
hdisk20.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12, ac11 no good either
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 # # 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 #
Re: Linux 2.4.2-ac12
On Mon, 5 Mar 2001, Linus Torvalds wrote: In article [EMAIL PROTECTED], Scott M. Hoffman [EMAIL PROTECTED] 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
In article <[EMAIL PROTECTED]>, Scott M. Hoffman <[EMAIL PROTECTED]> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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. > > 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 [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
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 [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2-ac12
In article [EMAIL PROTECTED], Scott M. Hoffman [EMAIL PROTECTED] 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
