From: <joerg.beyer-htSm2yLGOjU@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: trouble with medion 9788 DE notebook
Date: Tue, 20 Aug 2002 20:22:34 +0200 [thread overview]
Message-ID: <200208201822.g7KIMYX01424@mailgate5.cinetic.de> (raw)
Hi,
I have a medion 9877 DE notebook, which is a Athon 1.Ghz machine, simmilar to
this onhttp://rguerin.free.fr/medion/ .
without your acpi patch I cant use the nic. I understand that this is not a problem with the
nic, but a problem with the IRQs. Ok I used several versions of your patches, e.g.
acpi-20020815-2.4.20-pre3.diff.gz with the respective linux kernel. I still get _a_lot_
errors on the network interface, and also disk access is _very_ slow. It takes minutes
to untar something like the linux kernel tarball.
This is what lspci tells about the machine:
linux:/home/joerg # lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:06.0 Communication controller: Ambient Technologies Inc: Unknown device 4000 (rev 02)
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 1a)
00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 50)
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10)
00:0c.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
00:0c.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
01:00.0 VGA compatible controller: S3 Inc.: Unknown device 8d02 (rev 01)
and these are the errors I have on the nic.
linux:/home/joerg # ifconfig eth0
eth0 Protokoll:Ethernet Hardware Adresse 00:07:CA:00:AC:A3
inet Adresse:10.0.0.30 Bcast:10.255.255.255 Maske:255.0.0.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3584 errors:26602 dropped:730 overruns:26602 frame:0
TX packets:3564 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:100
RX bytes:5169122 (4.9 Mb) TX bytes:268991 (262.6 Kb)
Interrupt:10 Basisadresse:0x1000
/var/log/messages tells me, this:
Aug 20 22:05:52 linux kernel: eth0: Too much work at interrupt, IntrStatus=0x0040.
Aug 20 22:06:23 linux last message repeated 8 times
Aug 20 22:07:24 linux last message repeated 571 times
Aug 20 22:08:25 linux last message repeated 558 times
Aug 20 22:08:45 linux last message repeated 190 times
Does anybody has an idea/suggestion hwo to fix this?
TIA
Joerg
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
next reply other threads:[~2002-08-20 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 18:22 joerg.beyer-htSm2yLGOjU [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-20 21:07 trouble with medion 9788 DE notebook joerg.beyer-htSm2yLGOjU
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=200208201822.g7KIMYX01424@mailgate5.cinetic.de \
--to=joerg.beyer-htsm2ylgoju@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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