From: Nicolas Mailhot <Nicolas.Mailhot@laposte.net>
To: linux-kernel@vger.kernel.org
Cc: david-b@pacbell.net, jgarzik@pobox.com, mingo@elte.hu,
andrew.grover@intel.com
Subject: [Resend]2.5 usb + rt8139too + io-apic + acpi UP problem
Date: 07 Nov 2002 15:46:48 +0100 [thread overview]
Message-ID: <1036680407.3504.2.camel@ulysse.olympe.o2t> (raw)
[-- Attachment #1: Type: text/plain, Size: 5596 bytes --]
[ Resend since the first one seems to have been lost somewhere ; apologies if it did get through ]
[ Please CC me any reply as I'm not on the list ]
Hi
I'm trying to move from an pure usb hid + acpi + io-apic UP 2.4 system
to a 2.5 one. Hardware is via kt400 based. The problem is :
* 2.5 io-apic kills usb input
device not accepting address", see
http://linux-usb.sourceforge.net/FAQ.html#ts6
* without io-apic build-in rt8139too do not work with acpi :
nov 5 20:50:30 rousalka ifup:
nov 5 20:50:30 rousalka ifup: Définition des informations IP pour eth0.
Nov 5 20:50:30 rousalka kernel: eth0: Setting 100mbps full-duplex based
on auto-negotiated partner ability 41e1.
Nov 5 20:50:36 rousalka dhclient: DHCPREQUEST on eth0 to
255.255.255.255 port 67
Nov 5 20:50:45 rousalka last message repeated 3 times
Nov 5 20:50:53 rousalka dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8
Nov 5 20:50:54 rousalka kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Nov 5 20:50:54 rousalka kernel: eth0: Setting 100mbps full-duplex based
on auto-negotiated partner ability 41e1.
Nov 5 20:51:01 rousalka dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 12
Nov 5 20:51:13 rousalka dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Nov 5 20:51:20 rousalka dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 15
Nov 5 20:51:30 rousalka kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Nov 5 20:51:30 rousalka kernel: eth0: Setting 100mbps full-duplex based
on auto-negotiated partner ability 41e1.
Nov 5 20:51:35 rousalka dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 10
Nov 5 20:51:45 rousalka dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 9
Nov 5 20:51:54 rousalka dhclient: No DHCPOFFERS received.
Nov 5 20:51:54 rousalka dhclient: Trying recorded lease 81.65.232.223
nov 5 20:51:57 rousalka ifup: PING 81.65.232.1 (81.65.232.1) from
81.65.232.223 : 56(84) bytes of data.
nov 5 20:51:57 rousalka ifup:
nov 5 20:51:57 rousalka ifup: --- 81.65.232.1 ping statistics ---
nov 5 20:51:57 rousalka ifup: 3 packets transmitted, 0 received, +3
errors, 100% loss, time 1999ms
nov 5 20:51:57 rousalka ifup: , pipe 3
nov 5 20:51:57 rousalka ifup: échoué.
nov 5 20:51:57 rousalka network: Montage de l'interface eth0 : failed
* without acpi and io-apic network and usb works, but obviously
not acpi:(
So right now on 2.5 i have to choose between broken input, broken
network or broken acpi:((.
Here are /proc/interrupts contents for various configurations on this
system, I don't find them all that enlightening but maybe someone here
can interpret them.
2.4.20-pre10-ac1 uhci, io-apic, acpi
CPU0
0: 4024 IO-APIC-edge timer
1: 4 IO-APIC-edge keyboard
2: 0 XT-PIC cascade
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-edge acpi
14: 37 IO-APIC-edge ide0
15: 2782 IO-APIC-edge ide1
18: 62 IO-APIC-level cs46xx, eth0
21: 233 IO-APIC-level usb-uhci, usb-uhci, usb-uhci
NMI: 0
LOC: 3974
ERR: 0
MIS: 0
2.5.46-bk2 uhci, io-apic, acpi
CPU0
0: 68555 IO-APIC-edge timer
2: 0 XT-PIC cascade
7: 0 IO-APIC-edge uhci-hcd
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
10: 0 IO-APIC-edge uhci-hcd
11: 0 IO-APIC-edge uhci-hcd
14: 42 IO-APIC-edge ide0
15: 2992 IO-APIC-edge ide1
18: 105 IO-APIC-level CS46XX, eth0
NMI: 0
LOC: 68478
ERR: 0
MIS: 0
2.5.46-bk2 ehci, io-apic, acpi
CPU0
0: 67659 IO-APIC-edge timer
2: 0 XT-PIC cascade
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
12: 0 IO-APIC-edge ehci-hcd
14: 42 IO-APIC-edge ide0
15: 2880 IO-APIC-edge ide1
18: 44 IO-APIC-level CS46XX, eth0
NMI: 0
LOC: 67575
ERR: 0
MIS: 0
2.5.46-bk2 uhci, no io-apic, no acpi
CPU0
0: 39606 XT-PIC timer
2: 0 XT-PIC cascade
7: 0 XT-PIC uhci-hcd
8: 1 XT-PIC rtc
10: 262 XT-PIC uhci-hcd
11: 48 XT-PIC uhci-hcd, CS46XX, eth0
14: 41 XT-PIC ide0
15: 2615 XT-PIC ide1
NMI: 0
ERR: 0
2.5.46-bk2 uhci, no io-apic, no acpi
CPU0
0: 38133 XT-PIC timer
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
11: 112 XT-PIC CS46XX, eth0
12: 149 XT-PIC ehci-hcd
14: 41 XT-PIC ide0
15: 2679 XT-PIC ide1
NMI: 0
ERR: 0
2.5.46-bk2 uhci, no io-apic, no acpi
CPU0
0: 47925 XT-PIC timer
2: 0 XT-PIC cascade
7: 0 XT-PIC uhci-hcd
8: 1 XT-PIC rtc
10: 0 XT-PIC uhci-hcd
11: 102 XT-PIC uhci-hcd, CS46XX, eth0
12: 278 XT-PIC ehci-hcd
14: 41 XT-PIC ide0
15: 2479 XT-PIC ide1
NMI: 0
ERR: 0
Regards,
--
Nicolas Mailhot
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2002-11-07 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1036680407.3504.2.camel@ulysse.olympe.o2t \
--to=nicolas.mailhot@laposte.net \
--cc=andrew.grover@intel.com \
--cc=david-b@pacbell.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®