[coreboot] (no subject)

[mbertens]

On Sat, 2010-05-22 at 18:04 -0400, Gregg Levine wrote:
> On Sat, May 22, 2010 at 5:08 PM, Joseph Smith <joe at settoplinux.org> wrote:
> >
> >
> >
> > On Sat, 22 May 2010 19:20:31 +0200, mbertens <mbertens at xs4all.nl> wrote:
> >> On Sat, 2010-05-22 at 09:53 -0400, Joseph Smith wrote:
> >>
> >>> On 05/22/2010 02:39 AM, mbertens wrote:
> >>> > hi all,
> >>> >
> >>> > I have a question about the PCI api and howto set registers on PCI
> >>> > devices. My system a Nokia IP530 has a BX440 northbridge and a 82371
> >>> > southbrigde.
> >>> >
> >>> > The system has;
> >>> > - Dual IDE contoller (working)
> >>> > - Super I/O (Serial, keyb and flash-enable working)
> >>> > - 4 onboard NIC's 21143PD (1 NIC working)
> >>> > - PCMCIA controller dual slot PCI1225.
> >>> >
> >>> > I want to set the GPIOs of the SB to specific values to see if i can
> >> get
> >>> > the NICs and PCMCIA to work. All NICs get an IRQ assingment. So there
> >>> > must be some thing else that prevents them from working properly.
> >>> >
> >>> > Or if anyone has any good ideas for this problem let me known.
> >>> >
> >>> Hello Marc,
> >>> Are the LED's on your NIC's lighting up?
> >>
> >> Yes the lights are lighting up
> >>
> >> Linux Tulip driver version 1.1.15-NAPI (Feb 27, 2007)
> >> PCI: setting IRQ 10 as level-triggered
> >> PCI: Assigned IRQ 10 for device 0000:00:0d.0
> >> PCI: Sharing IRQ 10 with 0000:0a:04.0
> >> PCI: Sharing IRQ 10 with 0000:0a:05.0
> >> tulip0:  EEPROM default media type Autosense.
> >> tulip0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY
> >> (2) block.
> >> tulip0:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial
> >> PHY (2) block.
> >> tulip0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY
> >> (4) block.
> >> tulip0:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM
> >> PHY (4) block.
> >> eth0: Digital DS21142/43 Tulip rev 65 at Port 0x2000, 00:a0:8e:36:c2:70,
> >> IRQ 10.
> >> PCI: setting IRQ 11 as level-triggered
> >> PCI: Assigned IRQ 11 for device 0000:00:0e.0
> >> PCI: Sharing IRQ 11 with 0000:00:07.2
> >> tulip1:  EEPROM default media type Autosense.
> >> tulip1:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY
> >> (2) block.
> >> tulip1:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial
> >> PHY (2) block.
> >> tulip1:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY
> >> (4) block.
> >> tulip1:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM
> >> PHY (4) block.
> >> eth1: Digital DS21142/43 Tulip rev 65 at Port 0x2080, 00:a0:8e:36:c2:71,
> >> IRQ 11.
> >> PCI: Found IRQ 10 for device 0000:0a:04.0
> >> PCI: Sharing IRQ 10 with 0000:00:0d.0
> >> PCI: Sharing IRQ 10 with 0000:0a:05.0
> >> tulip2:  EEPROM default media type Autosense.
> >> tulip2:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY
> >> (2) block.
> >> tulip2:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial
> >> PHY (2) block.
> >> tulip2:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY
> >> (4) block.
> >> tulip2:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM
> >> PHY (4) block.
> >> eth2: Digital DS21142/43 Tulip rev 65 at Port 0x1000, 00:a0:8e:36:c2:72,
> >> IRQ 10.
> >> PCI: Found IRQ 10 for device 0000:0a:05.0
> >> PCI: Sharing IRQ 10 with 0000:00:0d.0
> >> PCI: Sharing IRQ 10 with 0000:0a:04.0
> >> tulip3:  EEPROM default media type Autosense.
> >> tulip3:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY
> >> (2) block.
> >> tulip3:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial
> >> PHY (2) block.
> >> tulip3:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY
> >> (4) block.
> >> tulip3:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM
> >> PHY (4) block.
> >> eth3: Digital DS21142/43 Tulip rev 65 at Port 0x1080, 00:a0:8e:36:c2:73,
> >> IRQ 10.
> >>
> >> so it seems that the devices are comming up.
> >> in DMESG i get the following error on pinging with the device
> >>
> >>
> >> Oct 14 22:44:00 debian kernel: [  740.024488] NETDEV WATCHDOG: eth3:
> >> transmit timed out
> >> Oct 14 22:44:00 debian kernel: [  740.024508] eth3: 21140 transmit timed
> >> out, status f0260000, SIA 000000c6 ffff0000 fffbff7f 8ff04008,
> > resetting...
> >> Oct 14 22:44:00 debian kernel: [  740.024542] ------------[ cut here
> >> ]------------
> >> Oct 14 22:44:00 debian kernel: [  740.024549] WARNING: at
> >> net/sched/sch_generic.c:222 dev_watchdog+0x8f/0xdc()
> >> Oct 14 22:44:00 debian kernel: [  740.024556] Modules linked in: ipv6
> > loop
> >> evdev pcmcia firmware_class snd_pcsp serio_raw snd_pcm snd_timer
> > i2c_piix4
> >> snd soundcore i2c_core psmouse yenta_socket rsrc_nonstatic pcmcia_core
> >> snd_page_alloc intel_agp agpgart shpchp pci_hotplug ext3 jbd mbcache
> >> ide_disk ata_generic libata scsi_mod dock uhci_hcd piix ide_pci_generic
> >> tulip usbcore ide_core thermal_sys [last unloaded: scsi_wait_scan]
> >> Oct 14 22:44:00 debian kernel: [  740.024632] Pid: 0, comm: swapper Not
> >> tainted 2.6.26-2-686 #1
> >> Oct 14 22:44:00 debian kernel: [  740.024646]  [<c01225f7>]
> >> warn_on_slowpath+0x40/0x66
> >> Oct 14 22:44:00 debian kernel: [  740.024679]  [<c01319f1>]
> >> autoremove_wake_function+0xd/0x2d
> >> Oct 14 22:44:00 debian kernel: [  740.024703]  [<c01184d1>]
> >> __wake_up_common+0x2e/0x58
> >> Oct 14 22:44:00 debian kernel: [  740.024728]  [<c011a6bb>]
> >> __wake_up+0x29/0x39
> >> Oct 14 22:44:00 debian kernel: [  740.024747]  [<c012f167>]
> >> insert_work+0x58/0x5c
> >> Oct 14 22:44:00 debian kernel: [  740.024759]  [<c012f455>]
> >> __queue_work+0x1c/0x28
> >> Oct 14 22:44:00 debian kernel: [  740.024770]  [<c012f4b0>]
> >> queue_work+0x33/0x3c
> >> Oct 14 22:44:00 debian kernel: [  740.024781]  [<d081deb0>]
> >> tulip_tx_timeout+0xea/0x275 [tulip]
> >> Oct 14 22:44:00 debian kernel: [  740.024820]  [<d081e00e>]
> >> tulip_tx_timeout+0x248/0x275 [tulip]
> >> Oct 14 22:44:00 debian kernel: [  740.024838]  [<c0129b64>]
> >> lock_timer_base+0x19/0x35
> >> Oct 14 22:44:00 debian kernel: [  740.024858]  [<c026727a>]
> >> dev_watchdog+0x0/0xdc
> >> Oct 14 22:44:00 debian kernel: [  740.024873]  [<c0267309>]
> >> dev_watchdog+0x8f/0xdc
> >> Oct 14 22:44:00 debian kernel: [  740.024884]  [<c012970c>]
> >> run_timer_softirq+0x11a/0x17c
> >> Oct 14 22:44:00 debian kernel: [  740.024895]  [<c026727a>]
> >> dev_watchdog+0x0/0xdc
> >> Oct 14 22:44:00 debian kernel: [  740.024910]  [<c012662d>]
> >> __do_softirq+0x66/0xd3
> >> Oct 14 22:44:00 debian kernel: [  740.024922]  [<c01266df>]
> >> do_softirq+0x45/0x53
> >> Oct 14 22:44:00 debian kernel: [  740.024932]  [<c0126996>]
> >> irq_exit+0x35/0x69
> >> Oct 14 22:44:00 debian kernel: [  740.024940]  [<c0110131>]
> >> smp_apic_timer_interrupt+0x6b/0x76
> >> Oct 14 22:44:00 debian kernel: [  740.024952]  [<c010265b>]
> >> default_idle+0x0/0x53
> >> Oct 14 22:44:00 debian kernel: [  740.024967]  [<c0104368>]
> >> apic_timer_interrupt+0x28/0x30
> >> Oct 14 22:44:00 debian kernel: [  740.024979]  [<c010265b>]
> >> default_idle+0x0/0x53
> >> Oct 14 22:44:00 debian kernel: [  740.024992]  [<c013007b>]
> >> search_exception_tables+0x11/0x22
> >> Oct 14 22:44:00 debian kernel: [  740.025006]  [<c0114d78>]
> >> native_safe_halt+0x2/0x3
> >> Oct 14 22:44:00 debian kernel: [  740.025029]  [<c0102688>]
> >> default_idle+0x2d/0x53
> >> Oct 14 22:44:00 debian kernel: [  740.025039]  [<c01025d3>]
> >> cpu_idle+0xb0/0xd0
> >> Oct 14 22:44:00 debian kernel: [  740.025051]  =======================
> >> Oct 14 22:44:00 debian kernel: [  740.025058] ---[ end trace
> >> 33d3b6b29c3f7701 ]---
> >> Oct 14 22:44:03 debian kernel: [  743.026003] 0000:0a:04.0:
> >> tulip_stop_rxtx() failed (CSR5 0xf0260000 CSR6 0xb3862002)
> >> Oct 14 22:44:08 debian kernel: [  748.024713] NETDEV WATCHDOG: eth3:
> >> transmit timed out
> >> Oct 14 22:44:08 debian kernel: [  748.024734] eth3: 21140 transmit timed
> >> out, status f0260000, SIA 000020c6 ffff0001 fffbffff 8ff14000,
> > resetting...
> >> Oct 14 22:44:08 debian kernel: [  748.026177] 0000:0a:04.0:
> >> tulip_stop_rxtx() failed (CSR5 0xf0260000 CSR6 0xb3862002)
> >>
> >> Oct 14 22:53:02 debian kernel: [ 1282.039486] NETDEV WATCHDOG: eth4:
> >> transmit timed out
> >> Oct 14 22:53:02 debian kernel: [ 1282.039506] eth4: 21140 transmit timed
> >> out, status f0218116, SIA 000020c6 ffff0001 fffbffff 8ff10000,
> > resetting...
> >> Oct 14 22:53:03 debian kernel: [ 1283.045232] 0000:0a:05.0:
> >> tulip_stop_rxtx() failed (CSR5 0xf0200116 CSR6 0xb3860000)
> >>
> >>
> > Ok, at first glace this could be a IRQ routing issue. Looks like 3 of the
> > NIC's are sharing the same IRQ..... are those the three that are not
> > working? FYI, commonly IRQ 10 is supposed to be reserved for PS2 keyboard.
> >
> > Can you post: cat /proc/interrupts ?
> >
> > --
> > Thanks,
> > Joseph Smith
> > Set-Top-Linux
> > www.settoplinux.org
> >
> >
> > --
> > coreboot mailing list: coreboot at coreboot.org
> > http://www.coreboot.org/mailman/listinfo/coreboot
> >
> 
> Hello!
> Just for fun, where could I track down one of these things? I confess
> that these problems are interesting, and worthy of my interest.
They can be found in ebay and these kind of sites. They are discontinued
by the manufacturer. And so therefore should not cost alot.


> 
> Joe, I still haven't forgotten my interests in tracking down one of
> the set top boxes that we've discussed in the past, especially with
> the announcements of Google to create a set top box presence for
> themselves.
> -- 
> -----
> Gregg C Levine gregg.drwho8 at gmail.com
> "This signature fought the Time Wars, time and again."
> 

Marc Bertens