2.2.18 dies on my 486..

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* 2.2.18 dies on my 486..
@ 2000-12-28  1:05 Mike A. Harris
  2000-12-28  1:13 ` Andreas Dilger
  2000-12-28  2:35 ` Alan Cox
  0 siblings, 2 replies; 6+ messages in thread
From: Mike A. Harris @ 2000-12-28  1:05 UTC (permalink / raw)
  To: Linux Kernel mailing list

I just upgraded my 486 firewall's kernel to pure 2.2.18 from
2.2.17, with no other changes, and now it dies with all sorts
of hard disk failures.

I get:

hdb: lost interrupt

And stuff about DRQ lost...

Totally frozen box after that.



----------------------------------------------------------------------
      Mike A. Harris  -  Linux advocate  -  Open source advocate
          This message is copyright 2000, all rights reserved.
  Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------


If you're interested in computer security, and want to stay on top of the
latest security exploits, and other information, visit:

http://www.securityfocus.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.2.18 dies on my 486..
  2000-12-28  1:05 2.2.18 dies on my 486 Mike A. Harris
@ 2000-12-28  1:13 ` Andreas Dilger
  2000-12-28  2:15   ` Mike A. Harris
  2000-12-28  2:35 ` Alan Cox
  1 sibling, 1 reply; 6+ messages in thread
From: Andreas Dilger @ 2000-12-28  1:13 UTC (permalink / raw)
  To: Mike A. Harris; +Cc: Linux Kernel mailing list

Mike Harris writes:
> I just upgraded my 486 firewall's kernel to pure 2.2.18 from
> 2.2.17, with no other changes, and now it dies with all sorts
> of hard disk failures.
> 
> I get:
> 
> hdb: lost interrupt
> 
> And stuff about DRQ lost...

Is it possible you compiled the kernel with gcc 2.95.2?  I've been having
a similar problem, but I'm having trouble tracking it down.  Because I
normally use a very heavily modified 2.2.18 kernel, I'm trying to isolate
just where the problem is - I have no problems with a stock 2.2.18 kernel.
If I compile with gcc 2.7.2.3 it works fine.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.2.18 dies on my 486..
  2000-12-28  1:13 ` Andreas Dilger
@ 2000-12-28  2:15   ` Mike A. Harris
  0 siblings, 0 replies; 6+ messages in thread
From: Mike A. Harris @ 2000-12-28  2:15 UTC (permalink / raw)
  To: Andreas Dilger; +Cc: Linux Kernel mailing list

On Wed, 27 Dec 2000, Andreas Dilger wrote:

>Mike Harris writes:
>> I just upgraded my 486 firewall's kernel to pure 2.2.18 from
>> 2.2.17, with no other changes, and now it dies with all sorts
>> of hard disk failures.
>>
>> I get:
>>
>> hdb: lost interrupt
>>
>> And stuff about DRQ lost...
>
>Is it possible you compiled the kernel with gcc 2.95.2?  I've been having
>a similar problem, but I'm having trouble tracking it down.

Absolutely not possible.  ;o)  Compiled with kgcc on Red Hat 7
(egcs 2.91.66).  I've been building kernels with egcs since Red
Hat 5.0 was released, no problems.

I've never used gcc 2.95.x at all, so I can't comment on it at
all..

It seems my hard disk may be failing...

>Because I normally use a very heavily modified 2.2.18 kernel,
>I'm trying to isolate just where the problem is - I have no
>problems with a stock 2.2.18 kernel. If I compile with gcc
>2.7.2.3 it works fine.

Hmm.. must be a different problem than I'm having.  I've tracked
my problem down to disk accesses to hdb.  hda/hdc work fine, as
does the machine sitting idling doing its job.  If I do a copy
from hdb to hdc it explodes.  Very odd..  ;o(

----------------------------------------------------------------------
    Mike A. Harris  -  Linux advocate  -  Free Software advocate
          This message is copyright 2000, all rights reserved.
  Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------

[Quote: Linus Torvalds - Aug 27, 2000 - linux-kernel mailing list]
"And I'm right.  I'm always right, but in this case I'm just a bit more
right than I usually am." -- Linus Torvalds

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.2.18 dies on my 486..
  2000-12-28  1:05 2.2.18 dies on my 486 Mike A. Harris
  2000-12-28  1:13 ` Andreas Dilger
@ 2000-12-28  2:35 ` Alan Cox
  2000-12-29  0:09   ` Mike A. Harris
  1 sibling, 1 reply; 6+ messages in thread
From: Alan Cox @ 2000-12-28  2:35 UTC (permalink / raw)
  To: Mike A. Harris; +Cc: Linux Kernel mailing list

> I just upgraded my 486 firewall's kernel to pure 2.2.18 from
> 2.2.17, with no other changes, and now it dies with all sorts
> of hard disk failures.
> 
> I get:
> 
> hdb: lost interrupt
> And stuff about DRQ lost...

What hardware config, what hdparm tuning options ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.2.18 dies on my 486..
  2000-12-28  2:35 ` Alan Cox
@ 2000-12-29  0:09   ` Mike A. Harris
  2000-12-29  8:14     ` Vid Strpic
  0 siblings, 1 reply; 6+ messages in thread
From: Mike A. Harris @ 2000-12-29  0:09 UTC (permalink / raw)
  To: Alan Cox; +Cc: Linux Kernel mailing list

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

On Thu, 28 Dec 2000, Alan Cox wrote:

>> I just upgraded my 486 firewall's kernel to pure 2.2.18 from
>> 2.2.17, with no other changes, and now it dies with all sorts
>> of hard disk failures.
>>
>> I get:
>>
>> hdb: lost interrupt
>> And stuff about DRQ lost...
>
>What hardware config, what hdparm tuning options ?

AMD 486-DX2/66 12Mb RAM, ALi 14xx chipset.  Using 2.2.18 stock
and also 2.2.18+IDE.

hdparm settings:

pts/3 root@gw:~# hdparm -iv /dev/hd[abc]

/dev/hda:
 multcount    = 16 (on)
 I/O support  =  1 (32-bit)
 unmaskirq    =  0 (off)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 929/16/48, sectors = 713472, start = 0

 Model=DSAA-3360, FwRev=25505120, SerialNo=PABP2020102
 Config={ SoftSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=929/16/48, TrkSize=59400, SectSize=550, ECCbytes=16
 BuffType=3(DualPortCache), BuffSize=96kB, MaxMultSect=16, MultSect=16
 DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
 CurCHS=929/16/48, CurSects=-486539254, LBA=yes, LBAsects=713472
 tDMA={min:240,rec:240}, DMA modes: sword0 sword1 sword2 mword0 mword1
 IORDY=yes, tPIO={min:240,w/IORDY:240}, PIO modes:


/dev/hdb:
 multcount    =  8 (on)
 I/O support  =  1 (32-bit)
 unmaskirq    =  0 (off)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 827/32/63, sectors = 1667232, start = 0

 Model=Maxtor 7850 AR, FwRev=UA7X6059, SerialNo=P60133LS
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>5Mbs FmtGapReq }
 RawCHS=1654/16/63, TrkSize=0, SectSize=0, ECCbytes=11
 BuffType=3(DualPortCache), BuffSize=64kB, MaxMultSect=8, MultSect=8
 DblWordIO=yes, OldPIO=2, DMA=yes, OldDMA=1
 CurCHS=1654/16/63, CurSects=1889533977, LBA=yes, LBAsects=1667232
 tDMA={min:150,rec:150}, DMA modes: sword0 sword1 *sword2 *mword0
 IORDY=on/off, tPIO={min:240,w/IORDY:180}, PIO modes: mode3

/dev/hdc:
 multcount    =  0 (off)
 I/O support  =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 524/255/63, sectors = 8418816, start = 0

 Model=QUANTUM FIREBALL SE4.3A, FwRev=API.0A00, SerialNo=334734916263
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=14848/9/63, TrkSize=32256, SectSize=512, ECCbytes=4
 BuffType=3(DualPortCache), BuffSize=80kB, MaxMultSect=16, MultSect=off
 DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
 CurCHS=14848/9/63, CurSects=1979711616, LBA=yes, LBAsects=8418816
 tDMA={min:120,rec:120}, DMA modes: sword0 sword1 sword2 mword0 mword1 *mword2
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
 UDMA modes: mode0 mode1 mode2


No messages in syslog, but it died numerous times with "hdb
interrupt lost" and DRQ failed or something like that.  It seems
to work fine if I access any one drive, but if I copy from hdb ->
hdc the machine dies within seconds.

.config attached

I am thinking possible hardware failure, but I havent spent time
yet trying to narrow it down.

No special lilo options or any tweaking going on on this machine
other than hdparm..



----------------------------------------------------------------------
    Mike A. Harris  -  Linux advocate  -  Free Software advocate
          This message is copyright 2000, all rights reserved.
  Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------

Are you an open source developer?  Need web space?  Your own project mailing
lists?  Bug tracking software?  CVS Repository?  Build environments?
Head over to http://sourceforge.net for all of that, and more, for free!

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

#
# Automatically generated by make menuconfig: don't edit
#

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Processor type and features
#
# CONFIG_M386 is not set
CONFIG_M486=y
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M686 is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_1GB=y
# CONFIG_2GB is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
# CONFIG_SMP is not set

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

#
# General setup
#
CONFIG_NET=y
# CONFIG_PCI is not set
# CONFIG_MCA is not set
# CONFIG_VISWS is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
# CONFIG_BINFMT_JAVA is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_OTHER is not set
# CONFIG_APM is not set
# CONFIG_TOSHIBA is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_XD is not set
CONFIG_PARIDE_PARPORT=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_HD is not set

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_FIREWALL=y
CONFIG_FILTER=y
CONFIG_UNIX=m
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
# CONFIG_IP_TRANSPARENT_PROXY is not set
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_MASQUERADE_MOD=y
CONFIG_IP_MASQUERADE_IPAUTOFW=m
CONFIG_IP_MASQUERADE_IPPORTFW=m
CONFIG_IP_MASQUERADE_MFW=m
# CONFIG_IP_ROUTER is not set
CONFIG_NET_IPIP=m
# CONFIG_NET_IPGRE is not set
CONFIG_IP_ALIAS=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_RARP is not set
# CONFIG_SKB_LARGE is not set
# CONFIG_IPV6 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_LLC 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
# CONFIG_CPU_IS_SLOW is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_POLICE is not set

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

#
# SCSI support
#
# CONFIG_SCSI 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_SCSI is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

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

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
CONFIG_EL2=m
CONFIG_ELPLUS=m
# CONFIG_EL16 is not set
CONFIG_EL3=m
CONFIG_3C515=m
CONFIG_VORTEX=m
# CONFIG_LANCE is not set
CONFIG_NET_VENDOR_SMC=y
CONFIG_WD80x3=m
# CONFIG_ULTRA is not set
# CONFIG_ULTRA32 is not set
# CONFIG_SMC9194 is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_RTL8139 is not set
# CONFIG_RTL8139TOO is not set
CONFIG_NET_ISA=y
# CONFIG_AT1700 is not set
# CONFIG_E2100 is not set
# CONFIG_DEPCA is not set
# CONFIG_EWRK3 is not set
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_FMV18X is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_HP100 is not set
# CONFIG_ETH16I is not set
CONFIG_NE2000=m
# CONFIG_SEEQ8005 is not set
# CONFIG_SK_G16 is not set
CONFIG_NET_EISA=y
# CONFIG_PCNET32 is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
# CONFIG_DM9102 is not set
CONFIG_DE4X5=m
CONFIG_DEC_ELCP=m
CONFIG_DEC_ELCP_OLD=m
# CONFIG_DGRS is not set
# CONFIG_EEXPRESS_PRO100 is not set
# CONFIG_LNE390 is not set
# CONFIG_NE3210 is not set
CONFIG_NE2K_PCI=m
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SIS900 is not set
# CONFIG_ES3210 is not set
# CONFIG_EPIC100 is not set
# CONFIG_ZNET 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=m
# CONFIG_SLIP is not set
# 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_HOSTESS_SV11 is not set
# CONFIG_COSA is not set
# CONFIG_SEALEVEL_4021 is not set
# CONFIG_SYNCLINK_SYNCPPP is not set
# CONFIG_LANMEDIA is not set
# CONFIG_COMX is not set
# CONFIG_HDLC is not set
# CONFIG_DLCI is not set
# CONFIG_XPEED is not set
# CONFIG_SBNI 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

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_EXTENDED=y
# CONFIG_SERIAL_MANY_PORTS is not set
# CONFIG_SERIAL_SHARE_IRQ is not set
CONFIG_SERIAL_DETECT_IRQ=y
# CONFIG_SERIAL_MULTIPORT is not set
# CONFIG_HUB6 is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=32
CONFIG_PRINTER=m
# CONFIG_PRINTER_READBACK is not set
# CONFIG_MOUSE is not set

#
# Joysticks
#
# CONFIG_JOYSTICK is not set
# CONFIG_QIC02_TAPE is not set
# CONFIG_WATCHDOG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set

#
# Video For Linux
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DTLK is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Filesystems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=m
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_MINIX_FS=m
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=m
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_EFS_FS is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_NCP_FS is not set

#
# Partition Types
#
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MAC_PARTITION is not set
# CONFIG_SMD_DISKLABEL is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="cp437"
# 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_874 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_950 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_8 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set

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

#
# Sound
#
# CONFIG_SOUND is not set

#
# Kernel hacking
#
CONFIG_MAGIC_SYSRQ=y

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.2.18 dies on my 486..
  2000-12-29  0:09   ` Mike A. Harris
@ 2000-12-29  8:14     ` Vid Strpic
  0 siblings, 0 replies; 6+ messages in thread
From: Vid Strpic @ 2000-12-29  8:14 UTC (permalink / raw)
  To: Linux Kernel mailing list

On Thu, Dec 28, 2000 at 07:09:34PM -0500, Mike A. Harris wrote:
> On Thu, 28 Dec 2000, Alan Cox wrote:
> >What hardware config, what hdparm tuning options ?
> AMD 486-DX2/66 12Mb RAM, ALi 14xx chipset.  Using 2.2.18 stock
> and also 2.2.18+IDE.
> 
> hdparm settings:
> 
> /dev/hdb:
>  multcount    =  8 (on)
>  I/O support  =  1 (32-bit)
>  unmaskirq    =  0 (off)
>  using_dma    =  0 (off)
>  keepsettings =  0 (off)
>  nowerr       =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
>  geometry     = 827/32/63, sectors = 1667232, start = 0
> 
>  Model=Maxtor 7850 AR, FwRev=UA7X6059, SerialNo=P60133LS
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>5Mbs FmtGapReq }
>  RawCHS=1654/16/63, TrkSize=0, SectSize=0, ECCbytes=11
>  BuffType=3(DualPortCache), BuffSize=64kB, MaxMultSect=8, MultSect=8
>  DblWordIO=yes, OldPIO=2, DMA=yes, OldDMA=1
>  CurCHS=1654/16/63, CurSects=1889533977, LBA=yes, LBAsects=1667232
>  tDMA={min:150,rec:150}, DMA modes: sword0 sword1 *sword2 *mword0
>  IORDY=on/off, tPIO={min:240,w/IORDY:180}, PIO modes: mode3
> 
> I am thinking possible hardware failure, but I havent spent time
> yet trying to narrow it down.

I think it's probably a hardware issue, yes.  I've seen several Maxtors
doing just this kind of stuff before ... I have one @ork which gives
this kind of errors if I put the box sideways - if it stays upright, no
problems :)

> No special lilo options or any tweaking going on on this machine
> other than hdparm..

Well, have you tried setting 32-bit support to '0'?  Just for hdb,
first, if that doesn't help, for hda and hdc also.

It happened to me on one machine (486 also, just one Quantum) but
inexplainably sometimes.  On other occasions all is well.

-- 
    ))       Vid Strpic, IRC:Martin, strpic@bofhlet.net, /bin/zsh.
    ((         (I don't speak for my employer, just for myself.)
  C|~~|     UNIX fundamentalist - and an average chauvinistic male.
   `--'
  C>N>K   Never anger a dragon, for you are crunchy and good with ketchup.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2000-12-29  9:15 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-12-28  1:05 2.2.18 dies on my 486 Mike A. Harris
2000-12-28  1:13 ` Andreas Dilger
2000-12-28  2:15   ` Mike A. Harris
2000-12-28  2:35 ` Alan Cox
2000-12-29  0:09   ` Mike A. Harris
2000-12-29  8:14     ` Vid Strpic

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox