기존 이솝 임베디드 포럼의 지식인 서비스가 게시판 형태로 변경되었습니다.
다른분 질문에도 비슷한 증상이 있더군요. 일단 제 증상으로 다시 한번 질문해 봅니다.
저는 외부 network을 희생하고 노트북과 aesop6410보드를 crosscable로 서로 연결하면 잘 작동합니다. 하지만 외부 network도 사용하기 위해 switch hub에 aesop6410보드와 노트북을 연결했을 경우에는 tftp로 boot image를 잘 받아와서 부팅도 잘 하지만 중간에 nfs: server 192.168.0.77 not responding, still trying 메시지와 함께 부팅이 멈춥니다. virtualbox ubuntu linux에서 192.168.0.102를 계속 ping을 해 보면 eth0: link up, 100Mbps, half-duplex, lpa 0x45E1직후에 ping에 응답을 하지만 Starting GPE display manager: gpe-dm이후에 ping에 응답을 멈추고 nfs: server 192.168.0.77 not responding, still trying상태에 빠집니다. 혹시 부팅 후반부에 network설정이 변경되는지요.
그리고 신기한 점은 원인은 모르겠지만 nfs: server 192.168.0.77 not responding, still trying상태에 빠지지 않고 부팅이 성공한 적도 있었습니다.
cable문제라면 ping에 대한 응답도 불안정해야 될 듯 한데, 부팅 중간과정부터 ping에 잘 응답하다가 부팅 후반부에 가서 ping에 응답을 하지 않는 상태로 빠지는게 다소 마음에 걸립니다. crosscable을 사용하지 않고 정상적으로 부팅시키는 방법이 없을까요? 저와같은 문제도 cable 불량으로 단정하는 것인 가능한지 궁금합니다. 지금까지 별 문제 없이 잘 써 오던 cable이라 찝찝하군요.
log message를 첨부합니다.
U-Boot 1.1.6 (Mar 21 2009 - 20:54:42) for AESOP6410
CPU: S3C6410@666MHz
Fclk = 666MHz, Hclk = 133MHz, Pclk = 66MHz, Serial = CLKUART (ASYNC Mod
e)
Board: AESOP-S3C6410
DRAM: 128 MB
Flash: 0 kB
NAND: 256 MB
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
smc911x: initializing
smc911x: detected LAN9215 controller
smc911x: phy initialized
smc911x: MAC 00:40:5c:26:0a:5b
TFTP from server 192.168.0.77; our IP address is 192.168.0.102
Filename 'zImage-aESOP6410'.
Load address: 0xc0008000
Loading: T #################################################################
#################################################################
###########################################################T ######
#################################################################
#################################################################
##############
done
Bytes transferred = 1733380 (1a7304 hex)
Boot with zImage
Starting kernel ...
Uncompressing Linux.............................................................
......................................................... done, booting the kern
el.
Linux version 2.6.21.5-cfs-v19 (root@build) (gcc version 4.2.4) #1 Sat Mar 21 20
:52:07 KST 2009
CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv6TEJ), cr=00c5387f
Machine: AESOP6410
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
CPU S3C6410 (id 0x36410101)
S3C6400: core 666.000 MHz, memory 133.000 MHz, peripheral 66.500 MHz
S3C6400: EPLL 192.000 MHz
S3C24XX Clocks, (c) 2004 Simtec Electronics
CPU0: D VIPT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists. Total pages: 28956
Kernel command line: root=/dev/nfs rw nfsroot=192.168.0.77:/opt/RootFS-aESOP6410
ip=192.168.0.102:192.168.0.77:192.168.0.1:255.255.255.0::eth0:off console=ttySA
C0,115200n81 ethaddr=00:40:5c:26:0a:5c
ethaddr_setup()
mac[0] = 0x00
mac[1] = 0x40
mac[2] = 0x5C
mac[3] = 0x26
mac[4] = 0x0A
mac[5] = 0x5C
Trying to install chained interrupt handler for IRQ0
Trying to install chained interrupt handler for IRQ1
Trying to install chained interrupt handler for IRQ32
Trying to install chained interrupt handler for IRQ33
PID hash table entries: 512 (order: 9, 2048 bytes)
timer tcon=00600000, tcnt 103c3, tcfg 00000400,00000000, usec 00001340
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 114MB = 114MB total
Memory: 111744KB available (3100K code, 445K data, 272K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
s3c6410: Initialising architecture
S3C DMA-pl080 Controller Driver, (c) 2006-2007 Samsung Electronics
Total 32 DMA channels will be initialized.
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
yaffs Mar 21 2009 20:47:44 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
LCD TYPE :: S3C_LMS350DF01 LCD will be initialized
S3C_LCD clock got enabled :: 133.000 Mhz
Window[0]- FB1 : map_video_memory: clear ff600000:0004b000
FB1 : map_video_memory: dma=57000000 cpu=ff600000 size=0004b000
lcd_clock = 133000000, LCD_PIXEL_CLOCK=9896640
Console: switching to colour frame buffer device 40x30
fb-1069855844: frame buffer device
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
s3c-uart.0: s3c_serial0 at MMIO 0x7f005000 (irq = 37) is a S3C
s3c-uart.1: s3c_serial1 at MMIO 0x7f005400 (irq = 38) is a S3C
s3c-uart.2: s3c_serial2 at MMIO 0x7f005800 (irq = 39) is a S3C
s3c-uart.3: s3c_serial3 at MMIO 0x7f005c00 (irq = 40) is a S3C
RAMDISK driver initialized: 8 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
eth0: LAN9215 (rev 0) at 0xc780a000 IRQ 67
eth0: Ethernet addr: 00:40:5c:26:0a:5c
Linux video capture interface: v2.00
Request irq 3 for codec
Request irq 4 for preview
S3C FIMC v3.0
AESOP NOR-Flash Driver, (c) 2006 AESOP Embedded
aesop-flash: map_probe() failed
S3C NAND Driver, (c) 2007 Samsung Electronics
S3C NAND Driver is using hardware ECC.
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bi
t)
Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00200000 : "Kernel"
0x00200000-0x10000000 : "File System"
usbmon: debugfs is not available
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 47, io mem 0x74300000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Loaded s3c-udc version Mar 21 2009 (Slave Mode)
ether gadget: using random self ethernet address
ether gadget: using random host ethernet address
usb0: Ethernet Gadget, version: May Day 2005
usb0: using s3c-udc, OUT ep1-bulk IN ep2-bulk STATUS ep3-int
usb0: MAC ca:2e:d4:d1:bc:e7
usb0: HOST MAC ee:08:38:27:63:9d
usb0: RNDIS ready
Registered gadget driver 'ether'
mice: PS/2 mouse device common for all mice
aesop_keypad_init
input: aesop-keypad as /class/input/input0
aesop_keypad_open
Aesop Keypad Initialized!!
platform_driver_register 0
S3C Touchscreen driver, (c) 2007 Samsung Electronics
s3c TouchScreen got loaded successfully : 12 bits
input: s3c TouchScreen as /class/input/input1
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
res->start : 7e005000 res->end : 7e0050ff<6>s3c2410-rtc s3c2410-rtc: rtc disable
d, re-enabling
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
S3C PWM Driver, (c) 2006-2007 Samsung Electronics
i2c /dev entries driver
s3c2410-i2c s3c2410-i2c: slave address 0x10
pdata c0394540, freq 200000 0..200000
clockin 66500
s3c2410-i2c s3c2410-i2c: bus frequency set to 129 KHz
Parent clock for Camera = 266000000, CAMDIV = 14
s3c2410-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
[s3c_hsmmc_probe]: s3c-hsmmc.0: at 0xc7812000 with irq 56. clk src: sclk_DOUTmpl
l_mmc0
s3c-hsmmc channel-0(EXT): card inserted.
[s3c_hsmmc_probe]: s3c-hsmmc.1: at 0xc7814000 with irq 57. clk src: sclk_DOUTmpl
l_mmc1
Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50
2007 UTC).
ASoC version 0.13.2
WM9713/WM9714 SoC Audio Codec 0.12
asoc: AC97 HiFi <-> s3c6400-ac97 mapping ok
ALSA device list:
#0: SMDK6400 (WM9713)
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
s3c2410-rtc s3c2410-rtc: setting the system clock to 2009-03-17 07:31:27 (123727
5087)
mmc1: host does not support reading read-only switch. assuming write-enable.
mmc: major= 254, minor= 0
mmcblk0: mmc1:8fe4 SD04G 3979776KiB
mmcblk0:<7>mmc1: starting CMD7 arg 8fe40000 flags 00000015
p1
eth0: link down
IP-Config: Complete:
device=eth0, addr=192.168.0.102, mask=255.255.255.0, gw=192.168.0.1,
host=192.168.0.102, domain=, nis-domain=(none),
bootserver=192.168.0.77, rootserver=192.168.0.77, rootpath=
Looking up port of RPC 100003/2 on 192.168.0.77
eth0: link up, 100Mbps, half-duplex, lpa 0x45E1
Looking up port of RPC 100005/1 on 192.168.0.77
VFS: Mounted root (nfs filesystem).
Freeing init memory: 272K
udevd version 124 started
INIT: Entering runlevel: 5
Starting Dropbear SSH server: dropbear.
Starting system message bus: dbus.
Starting syslogd/klogd: done
Starting Connection Manager
Starting GPE display manager: gpe-dm
nfs: server 192.168.0.77 not responding, still trying
nfs: server 192.168.0.77 not responding, still trying
nfs: server 192.168.0.77 not responding, still trying
nfs: server 192.168.0.77 not responding, still trying
혹시 10M bps짜리 허브인지? 아니면 100M hub인지요?
네트워크 설정때문에 그럴 가능성이 높은데, 일단 그 부분만 확인해 주시기 바랍니다.