From: "David D.W. Downey" <pgpkeys@hislinuxbox.com>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: David Raufeisen <david@fortyoz.org>, linux-kernel@vger.kernel.org
Subject: Re: VT82C686A corruption with 2.4.x
Date: Tue, 30 Jan 2001 18:04:42 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.21.0101301755330.3205-200000@ns-01.hislinuxbox.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101301716490.3105-100000@ns-01.hislinuxbox.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3771 bytes --]
OK, just completed the upgrade to 2.4.1-pre12 + via82cxxxx.diff.
SYSTEM SPECS CHANGES
===================
Shut off ACPI
Shut off 2nd IDE controller in BIOS
Shut off APM
Disabled UDMA support in BIOS
Removed 256MB RAM (768M total RAM) *
Everything is running stabler now. Here's what I've got set up right now.
VIA SUPPORT
============
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev c4)
Flags: bus master, medium devsel, latency 0
Memory at d0000000 (32-bit, prefetchable)
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00009000-00009fff
Memory behind bridge: d4000000-d7ffffff
Prefetchable memory behind bridge: d8000000-d9ffffff
Capabilities: [80] Power Management version 2
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at a000
Capabilities: [c0] Power Management version 2
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
Flags: medium devsel
Capabilities: [68] Power Management version 2
00:0c.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown device 0d30 (rev 02)
Subsystem: Promise Technology, Inc.: Unknown device 4d33
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at ac00
I/O ports at b000
I/O ports at b400
I/O ports at b800
I/O ports at bc00
Memory at db000000 (32-bit, non-prefetchable)
Capabilities: [58] Power Management version 1
00:0e.0 SCSI storage controller: Advanced System Products, Inc ABP940-UW
Flags: bus master, medium devsel, latency 32, IRQ 15
I/O ports at c000
Memory at db020000 (32-bit, non-prefetchable)
00:10.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
Subsystem: Netgear FA310TX
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at c400
Memory at db021000 (32-bit, non-prefetchable)
01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) (prog-if 00 [VGA])
Subsystem: 3Dfx Interactive, Inc. Voodoo3 AGP
Flags: 66Mhz, fast devsel
Memory at d4000000 (32-bit, non-prefetchable)
Memory at d8000000 (32-bit, prefetchable)
I/O ports at 9000
Capabilities: [54] AGP version 1.0
Capabilities: [60] Power Management version 1
PROMISE SUPPORT
===============
PDC20265: IDE controller on PCI bus 00 dev 60
PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
DMESG - VIA
==============
PCI: Using IRQ router VIA [1106/0686] at 00:07.0
System Vendor: VIA Technologies, Inc..
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
[drm] AGP 0.99 on VIA Apollo Pro @ 0xd0000000 64MB
[drm] AGP 0.99 on VIA Apollo Pro @ 0xd0000000 64MB
[drm] AGP 0.99 on VIA Apollo Pro @ 0xd0000000 64MB
DD TESTING
==========
[root@timberwolf /root]# dd if=/dev/hda7 of=/tmp/testing.img bs=1024k count=20002000+0 records in
2000+0 records out
[root@timberwolf /root]# ls -al /tmp/testing.img
-rw-r--r-- 1 root root 2097152000 Jan 29 17:54 /tmp/testing.img
[root@timberwolf /root]# ls -alh /tmp/testing.img
-rw-r--r-- 1 root root 2.0G Jan 29 17:54 /tmp/testing.img
[root@timberwolf /root]#
I'm also attaching a ksyms dump.
David D.W. Downey
[-- Attachment #2: Type: TEXT/plain, Size: 2711 bytes --]
Address Symbol Defined by
f286a060 advansys_proc_info [advansys]
f286a060 __insmod_advansys_S.text_L60896 [advansys]
f286caf0 advansys_reset [advansys]
f286c770 advansys_abort [advansys]
f286c660 advansys_command [advansys]
f286a58c advansys_detect [advansys]
f286d084 advansys_biosparam [advansys]
f287b0e0 __insmod_advansys_S.data_L15488 [advansys]
f287ef00 __insmod_advansys_S.bss_L128 [advansys]
f2878e60 __insmod_advansys_S.rodata_L8808 [advansys]
f286c350 advansys_release [advansys]
f286c698 advansys_queuecommand [advansys]
f286a000 __insmod_advansys_O/lib/modules/2.4.1-pre12/kernel/drivers/scsi/advansys.o_M3A761A3A_V132097 [advansys]
f286c444 advansys_info [advansys]
f286d10c advansys_setup [advansys]
f2862344 tulip_debug [tulip]
f28626e0 t21040_csr13 [tulip]
f285ba98 tulip_mdio_write [tulip]
f285a29c t21142_start_nway [tulip]
f2862348 tulip_tbl [tulip]
f28626f0 t21041_csr13 [tulip]
f28626fa t21041_csr14 [tulip]
f2862704 t21041_csr15 [tulip]
f285d160 comet_timer [tulip]
f2862a44 tulip_max_interrupt_work [tulip]
f285b288 tulip_interrupt [tulip]
f285a060 __insmod_tulip_S.text_L23186 [tulip]
f285a000 __insmod_tulip_O/lib/modules/2.4.1-pre12/kernel/drivers/net/tulip/tulip.o_M3A761A39_V132097 [tulip]
f2862a40 tulip_rx_copybreak [tulip]
f285a790 tulip_parse_eeprom [tulip]
f285d118 mxic_timer [tulip]
f285c710 pnic_do_nway [tulip]
f285bbf0 tulip_select_media [tulip]
f2861784 medianame [tulip]
f285b930 tulip_mdio_read [tulip]
f28629c0 __insmod_tulip_S.bss_L136 [tulip]
f285c568 tulip_check_duplex [tulip]
f285a060 t21142_timer [tulip]
f285a3b0 t21142_lnk_change [tulip]
f28620ca t21142_csr14 [tulip]
f285fb80 __insmod_tulip_S.rodata_L9522 [tulip]
f285ad58 tulip_read_eeprom [tulip]
f286198c tulip_media_cap [tulip]
f285c840 pnic_lnk_change [tulip]
f28620c0 __insmod_tulip_S.data_L1664 [tulip]
f285c914 pnic_timer [tulip]
f285cb60 tulip_timer [tulip]
next prev parent reply other threads:[~2001-01-31 2:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10101301743180.30535-100000@coffee.psychology.mcmaster.ca>
2001-01-31 1:18 ` David D.W. Downey
2001-01-31 2:04 ` David D.W. Downey [this message]
2001-01-31 7:36 ` Vojtech Pavlik
2001-01-31 7:55 ` David Raufeisen
2001-01-31 9:48 ` safemode
2001-01-31 11:43 ` Vojtech Pavlik
2001-01-31 12:54 ` Mark Hahn
2001-01-31 19:58 ` David Riley
2001-02-01 12:51 ` David D.W. Downey
2001-01-31 20:01 ` safemode
2001-01-31 22:04 ` Tobias Ringstrom
2001-01-31 22:40 ` safemode
2001-01-31 22:46 ` Alan Cox
2001-01-31 22:57 ` safemode
2001-02-01 6:31 ` Vojtech Pavlik
2001-02-01 0:46 ` Byron Stanoszek
2001-02-01 1:52 ` safemode
2001-02-01 6:52 ` Vojtech Pavlik
2001-02-01 11:32 ` safemode
2001-02-01 16:46 ` Byron Stanoszek
2001-02-01 18:06 ` Vojtech Pavlik
2001-02-01 18:20 ` Byron Stanoszek
2001-02-01 20:51 ` Vojtech Pavlik
2001-02-01 21:51 ` safemode
2001-02-01 21:56 ` Alan Chandler
2001-02-01 6:39 ` Vojtech Pavlik
2001-01-31 11:39 ` Vojtech Pavlik
2001-01-31 15:41 ` David D.W. Downey
2001-01-30 13:40 Nicholas Knight
2001-01-30 15:03 ` Tobias Ringstrom
2001-01-30 19:51 ` David D.W. Downey
2001-01-30 20:53 ` David Raufeisen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0101301755330.3205-200000@ns-01.hislinuxbox.com \
--to=pgpkeys@hislinuxbox.com \
--cc=david@fortyoz.org \
--cc=hahn@coffee.psychology.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®