atom feed14 messages in org.freebsd.freebsd-armRe: Guruplug Server Plus working to s...
FromSent OnAttachments
Milan ObuchOct 20, 2010 2:09 pm.guruplugplus, .dts, .guruplugplus
Gary JennejohnOct 21, 2010 1:43 am 
Milan ObuchOct 21, 2010 2:18 am 
Milan ObuchOct 21, 2010 2:12 pm 
Kristof ProvostOct 24, 2010 4:14 am 
Milan ObuchOct 24, 2010 2:22 pm 
Kristof ProvostOct 25, 2010 1:16 pm 
Milan ObuchOct 26, 2010 12:59 pm.dmesg
Kristof ProvostOct 26, 2010 2:19 pm 
Milan ObuchOct 27, 2010 7:55 am 
Rafal JaworowskiOct 27, 2010 9:43 am 
Milan ObuchOct 27, 2010 1:58 pm.h, .c, .c, 1 more
Rafal JaworowskiOct 30, 2010 6:02 am 
Milan ObuchNov 2, 2010 2:42 pm 
Subject:Re: Guruplug Server Plus working to some extent...
From:Milan Obuch (free@dino.sk)
Date:Oct 26, 2010 12:59:29 pm
List:org.freebsd.freebsd-arm
Attachments:
dmesg - 4k

On Monday 25 October 2010 22:17:27 Kristof Provost wrote:

On 2010-10-24 23:22:34 (+0200), Milan Obuch <free@dino.sk> wrote:

Well, it may be. I am no expert in this area, but what I do not understand is how bad PHY assignment could affect sending frames but nor receiving. I would expect with wrong assignment failing both, but, again, I am no expert here...

I'm not exactly an expert myself, I could be mistaken. I suspected the PHY because that's the bit which caused trouble on my board. Looking deeper the fact it's unable to probe the MAC address for the second interface is quite suspicious too.

Was there anything suspicious in the boot log? Perhaps something related to simplebus? It might also be a good idea to rebuild your kernel with 'DEBUG' set and to take another look at the boot output then.

I don't think I can say more without a device to play around with.

Regards, Kristof

Well, 'makeoptions DEBUG' just creates kernel.symbols, nothing else... there must be some other way to create more debug output, but I did not find it. If I could convert elf-structured ubldr to binary ubldr.bin, maybe I can boot kernel with verbose output... but I did not find the way to do it. (Any hint on this?)

There is absolutely nothing suspicious in boot log - see attached dmesg...

Regards, Milan

KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #3: Tue Oct 26 21:49:55 CEST 2010 ro@wind.dino.sk:/tmp/guruplug/obj/arm.arm/data/src9/sys/GURUPLUGPLUS2 arm WARNING: DIAGNOSTIC option enabled, expect reduced performance. CPU: Feroceon 88FR131 rev 1 (Marvell core) DC enabled IC enabled WB enabled EABT branch prediction enabled 16KB/32B 4-way Instruction cache 16KB/32B 4-way write-back-locking-C Data cache real memory = 536870912 (512 MB) avail memory = 520613888 (496 MB) SOC: Marvell 88F6281 rev A0, TClock 200MHz simplebus0: <Flattened device tree simple bus> on fdtbus0 ic0: <Marvell Integrated Interrupt Controller> mem 0xf1020200-0xf102023b on
simplebus0 timer0: <Marvell CPU Timer> mem 0xf1020300-0xf102032f irq 1 on simplebus0 Event timer "CPUTimer0" frequency 200000000 Hz quality 1000 Timecounter "CPUTimer1" frequency 200000000 Hz quality 1000 gpio0: <Marvell Integrated GPIO Controller> mem 0xf1010100-0xf101011f irq
35,36,37,38,39,40,41 on simplebus0 rtc0: <Marvell Integrated RTC> mem 0xf1010300-0xf1010307 on simplebus0 mge0: <Marvell Gigabit Ethernet controller> mem 0xf1072000-0xf1073fff irq
12,13,14,11,46 on simplebus0 mge0: Ethernet address: f0:ad:4e:00:16:33 miibus0: <MII bus> on mge0 e1000phy0: <Marvell 88E1149 Gigabit PHY> PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto mge1: <Marvell Gigabit Ethernet controller> mem 0xf1076000-0xf1077fff irq
16,17,18,15,47 on simplebus0 mge1: Ethernet address: f0:ad:4e:00:16:34 miibus1: <MII bus> on mge1 e1000phy1: <Marvell 88E1149 Gigabit PHY> PHY 1 on miibus1 e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto uart0: <16550 or compatible> mem 0xf1012000-0xf101201f irq 33 on simplebus0 uart0: console (1056,n,8,1) uart1: <16550 or compatible> mem 0xf1012100-0xf101211f irq 34 on simplebus0 ehci0: <Marvell Integrated USB 2.0 controller> mem 0xf1050000-0xf1050fff irq
48,19 on simplebus0 usbus0: EHCI version 1.0 usbus0: stop timeout usbus0: set host controller mode usbus0: <Marvell Integrated USB 2.0 controller> on ehci0 sata0: <Marvell Integrated SATA Controller> mem 0xf1080000-0xf1085fff irq 21 on
simplebus0 ata0: <Marvell Integrated SATA Channel> on sata0 ata1: <Marvell Integrated SATA Channel> on sata0 Timecounters tick every 1.000 msec usbus0: 480Mbps High Speed USB v2.0 WARNING: DIAGNOSTIC option enabled, expect reduced performance. Root mount waiting for: usbus0 ugen0.1: <Marvell> at usbus0 uhub0: <Marvell EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0 uhub0: 1 port with 1 removable, self powered Root mount waiting for: usbus0 ugen0.2: <vendor 0x05e3> at usbus0 uhub1: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/77.63, addr 2> on usbus0 Root mount waiting for: usbus0 uhub1: 4 ports with 4 removable, self powered ugen0.3: <vendor 0x05e3> at usbus0 umass0: <vendor 0x05e3 USB Storage, class 0/0, rev 2.00/99.09, addr 3> on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0000 Root mount waiting for: usbus0 Root mount waiting for: usbus0 umass0:0:0:-1: Attached to scbus0 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <Generic STORAGE DEVICE 9909> Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ufs/ARMroot []... mountroot: waiting for device /dev/ufs/ARMroot ... (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0 (probe0:umass-sim0:0:0:1): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:1): SCSI status: Check Condition (probe0:umass-sim0:0:0:1): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to
ready change, medium may have changed) da1 at umass-sim0 bus 0 scbus0 target 0 lun 1 da1: <Generic STORAGE DEVICE 9909> Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 974MB (1995776 512 byte sectors: 64H 32S/T 974C)