Re: Kernel panic on MSI K8T
Op maandag 27 december 2004 06:31, schreef Kyuu Eturautti:
> I was hoping someone here might have some recommendations as to where
> the problem might be concerning a repeating kernel panic. I haven't had
> issues on any other Athlon 64+Debian-AMD64 systems I have.
>
> What I have here is an MSI K8T (MS 6702 ver 1.0) with an Athlon64 3000+
> running Pure64 and 2.6.9 (similar problems with all older kernels, .deb
> and source compiled). As all the other hardware bits have either been
> verified (memtest86 for the memory) or replaced for testing (including
> newest BIOS upgrade), I don't believe the other details are that
> important. I'm using the integrated r8169 LAN and there are no add-on
> card except an old ATI Rage 128 for console use.
>
> Problem is this - when I upload a larger amount of data onto it, the
> whole thing crashes. I can copy a few megabytes or even larger amounts
> when the speed is low (ADSL), but when I start transferring hundreds of
> megs through the LAN, it always crashes within minutes - or sometimes
> seconds.
>
> As I had several USB "issues" with the system (as discussed here a few
> months ago), I tried using only PS/2 devices as well, but it didn't have
> any effect in the end. Seems like an r8169 issue, but I'll let someone
> else make a better guess. I took a picture of the kernel panic message:
> http://vekotin.org/shared/yue_panic.jpg
>
> lspci -v output:
> 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP]
> Host Bridge (rev 01)
> Subsystem: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge
> Flags: bus master, 66MHz, medium devsel, latency 8
> Memory at d0000000 (32-bit, prefetchable) [size=256M]
> Capabilities: <available only to root>
>
> 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge
> [K8T800 South] (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: 0000c000-0000cfff
> Memory behind bridge: cfe00000-cfefffff
> Prefetchable memory behind bridge: c7d00000-cfcfffff
> Capabilities: <available only to root>
>
> 0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8169 Gigabit Ethernet (rev 10)
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 702c
> Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
> I/O ports at ec00 [size=256]
> Memory at cfffff00 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at cffa0000 [disabled] [size=128K]
> Capabilities: <available only to root>
>
> 0000:00:0f.0 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> (prog-if 8a [Master SecP PriP])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 7020
> Flags: bus master, medium devsel, latency 32, IRQ 20
> I/O ports at fc00 [size=16]
> Capabilities: <available only to root>
>
> 0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1 Controller (rev 81) (prog-if 00 [UHCI])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 7020
> Flags: bus master, medium devsel, latency 32, IRQ 21
> I/O ports at dc00 [size=32]
> Capabilities: <available only to root>
>
> 0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1 Controller (rev 81) (prog-if 00 [UHCI])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 7020
> Flags: bus master, medium devsel, latency 32, IRQ 21
> I/O ports at e000 [size=32]
> Capabilities: <available only to root>
>
> 0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1 Controller (rev 81) (prog-if 00 [UHCI])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 7020
> Flags: bus master, medium devsel, latency 32, IRQ 21
> I/O ports at e400 [size=32]
> Capabilities: <available only to root>
>
> 0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1 Controller (rev 81) (prog-if 00 [UHCI])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 7020
> Flags: bus master, medium devsel, latency 32, IRQ 21
> I/O ports at e800 [size=32]
> Capabilities: <available only to root>
>
> 0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
> (prog-if 20 [EHCI])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 7020
> Flags: bus master, medium devsel, latency 32, IRQ 21
> Memory at cffffd00 (32-bit, non-prefetchable) [size=256]
> Capabilities: <available only to root>
>
> 0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge
> [K8T800 South]
> Subsystem: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South]
> Flags: bus master, stepping, medium devsel, latency 0
> Capabilities: <available only to root>
>
> 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
> Flags: fast devsel
> Capabilities: <available only to root>
>
> 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
> Flags: fast devsel
>
> 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
> Flags: fast devsel
>
> 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
> Flags: fast devsel
>
> 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128
> PF/PRO AGP 4x TMDS (prog-if 00 [VGA])
> Subsystem: ATI Technologies Inc Rage Fury Pro
> Flags: bus master, stepping, 66MHz, medium devsel, latency 32,
> IRQ 16
> Memory at c8000000 (32-bit, prefetchable) [size=64M]
> I/O ports at c800 [size=256]
> Memory at cfefc000 (32-bit, non-prefetchable) [size=16K]
> Expansion ROM at cfec0000 [disabled] [size=128K]
> Capabilities: <available only to root>
>
>
>
> Kyuu 'Vekotin' Eturautti
Well, I had the same kind of motherboard and had the same problems and some
more.I just ditched it for a gigabyte K8-Triton GA-K8V800 and all my problems
were over.I even just switched the harddisk without reinstalling and
everything went fine.The msi-board is just crap,not one single Linux is
working on it,they all gave problems:harddisk,network,cdrom,usb,PS-2;if not
all at the same time,at least one out of the catalog.As I can see on other
forums the problem is a general one,it's a monday-morning design :)
M.Cuppens
Reply to: