* 8240 booting:bootp time out and hd lost interrupt
@ 2002-01-15 10:22 邹涛
2002-01-15 12:03 ` Neil Horman
0 siblings, 1 reply; 3+ messages in thread
From: 邹涛 @ 2002-01-15 10:22 UTC (permalink / raw)
To: linuxppc-embedded@lists.linuxppc.org
Hello:
I'm a newer to PowerPC. when i port linux to PowerPC 8240,i met some problem.anyone give me advices will be appreciate.
i use board sandpoint 3, the cpu board is mpc8240.
I mark the line i wish you pay attention to.i have two questions: one is why the hdc lost the interrupt. the other is why the bootp time out. i test the host dhcp configuration with win98 as client.
The dip switch on cpu board is set to : sw2 01111,sw3 11011 (1 means ON)
BTW,who could tell me every bit of the two dip switch mean? I couldn't find document about it.
The dip switch on main board is set to: sw1 11111010 ,sw2 11111111.
The type of main board is "ppceval-sp3 rev x3". the CPU board is
"m98ppmc8240 rev x2" .linux kernel is Mvista Hard Hat Linux 2.0 for
ppc 82xx. My hard disk type is "Quantum fireball 3.5series 30.0GB".
the following is bootup message:
DINK32_KAHLUA >>dl -k
#>ascii-xfr -svn -l 10 vmlinuz-motolola-sandpoint.srec>/dev/ttyS0
DINK32_KAHLUA >>go 900000
loaded at: 00900000 009091B8
relocated to: 00800000 008091B8
zimage at: 00906000 00998F41
avail ram: 00400000 00800000
Linux/PPC load:
Uncompressing Linux...done.
Now booting the kernel
Total memory = 32MB; using 0kB for hash table (at 00000000)
Linux version 2.4.2_hhl20 (root@tony) (gcc version 2.95.3 20010315 (release/Mon1Motorola SPS Sandpoint Test Platform
Sandpoint port (C) 2000, 2001 MontaVista Software, Inc. (source@mvista.com)
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line:
OpenPIC Version 1.2 (1 CPUs and 24 IRQ sources) at f7fd0000
OpenPIC timer frequency is 100.000000 MHz
time_init: decrementer frequency = 24.752286 MHz
Calibrating delay loop... 131.89 BogoMIPS
Memory: 30596k available (1048k kernel code, 440k data, 88k init, 0k highmem)
Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 2048 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
pty: 256 Unix98 ptys configured
block: queued sectors max/low 20256kB/6752kB, 64 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
W82C105: IDE controller on PCI bus 00 dev 59
W82C105: chipset revision 5
W82C105: 100% native mode on irq 17
ide0: BM-DMA at 0xbfffd0-0xbfffd7, BIOS settings: hda:pio, hdb:pio
SL82C105 command word: 5
IDE timing: 00000909, resetting to PIO0 timing
ide1: BM-DMA at 0xbfffd8-0xbfffdf, BIOS settings: hdc:pio, hdd:pio
SL82C105 command word: 5
IDE timing: 000003e4, resetting to PIO0 timing
hdc: QUANTUM FIREBALLP AS30.0, ATA DISK drive
ide1 at 0xbfffe8-0xbfffef,0xbfffe6 on irq 15
hdc: 58633344 sectors (30020 MB) w/1902KiB Cache, CHS=58168/16/63
/*******************************************************************************
Partition check:
hdc:hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
[PTBL] [3649/255/63] hdc1 <hdc: lost interrupt
hdc: lost interrupt
hdc5hdc: lost interrupt
hdc: lost interrupt
hdc6 >
*******************************************************************************/
loop: loaded (max 8 devices)
Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI endttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 2048)
/*******************************************************************************
Sending BOOTP requests.......<6>NETDEV WATCHDOG: eth0: transmit timed out
....<6>NETDEV WATCHDOG: eth0: transmit timed out .. timed out!
********************************************************************************/
IP-Config: No network devices available.
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
request_module[block-major-2]: Root fs not mounted
VFS: Cannot open root device "" or 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00
and I use tcpdump to listen to the eth0, and receive something like that:
14:34:27.591370 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc6c3f016 secs:88 [|bootp] (DF)
14:34:27.591925 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc: xid:0xc6c3f016 secs:88 Y:192.168.10.100 S:192.168.10.13 ether 0:e0:4c:45:56:af [|bootp] (DF)
14:34:27.595609 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:28.591256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:29.591256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:30.591402 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:30.591402 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:32.601383 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:33.601256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:34.601256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:35.601276 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:35.601276 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:37.612096 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:38.611257 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:39.611257 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:40.611278 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:40.611278 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:42.621330 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:43.621256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:44.621256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:45.621277 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:45.621277 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:47.633769 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:48.631263 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:49.631256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:50.631277 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:50.631277 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:52.641343 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:53.641271 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:54.641268 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
14:34:55.641289 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:55.641289 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
14:34:55.711924 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc6c3f016 secs:117 [|bootp] (DF)
14:34:55.712391 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc: xid:0xc6c3f016 secs:117 Y:192.168.10.100 S:192.168.10.13 ether 0:e0:4c:45:56:af [|bootp] (DF)
14:35:25.712515 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc6c3f016 secs:147 [|bootp] (DF)
14:35:25.713052 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc: xid:0xc6c3f016 secs:147 Y:192.168.10.100 S:192.168.10.13 ether 0:e0:4c:45:56:af [|bootp] (DF)
It seems that the host ack the target's require, but target did't accept . So the target has no right IP address.
regards.
stone
stone@pocketix.com
2002-01-15
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: 8240 booting:bootp time out and hd lost interrupt
2002-01-15 10:22 8240 booting:bootp time out and hd lost interrupt 邹涛
@ 2002-01-15 12:03 ` Neil Horman
2002-01-15 12:50 ` Jerry Van Baren
0 siblings, 1 reply; 3+ messages in thread
From: Neil Horman @ 2002-01-15 12:03 UTC (permalink / raw)
To: ×ÞÌÎ; +Cc: linuxppc-embedded@lists.linuxppc.org
Hello-
Not sure if these are going to be you're exact answers, but I've
recently tackled both problems on a custom MPC860P based board:
1)
> I mark the line i wish you pay attention to.i have two questions: one is >why the hdc lost the interrupt.
I had the same error when trying to build a 2.4.14 kernel to use
the 860 PCMCIA interface populated with a CompactFlash card as an ide
device. My problem was that I actaully had no interrupt connected to
the PCMCIA interface, so I naturally was loosing interrupts. My
solution (and this may not be perfect for you as you appear to have
multiple ide devices was to modify the ide_timer_expiry function so that
it simply called the appropriate interrupt handler, converting this
non-interruptable device into a polled device of sorts. In fact, there
should be a case in ide_timer_expiry that calls the interrupt handler in
the case that an interrupt got raised just as the timer was expiring. I
used that as my guideline. From there its just a matter of adjusting
the timer timeout value in in ide_set_handler such that you can get
decent performance out of it. Of course, this may well not be your
problem, but you may want to check, just in case.
2)
>the other is why the bootp time out. i test the host dhcp configuration with >win98 as client.
It looks to me as though you don't have your bootp server set up
properly. Looking at your tcpdump, I see you sending out bootp requests
(eth0 B 0.0.0.0 >....), but I see no responsees. The 192.168.10.13
address appears multiple times in your tcpdump prior to your bootp
requests being sent (even on the lo interface which is odd), so it looks
like that may be a configuration error (perhaps something you passed in
on the kernel command line?). The fact that you can boot a Win98 client
with your DHCP server just means that it serves DHCP requests well,
which are close to, but not bootp requests. I use the ISC DHCP server
here under red hat 7.1, and to use it to serve bootp requires that I add
a special bootp entry for every address I wish to serve, like this:
host <name>:
{
hardware ethernet <MAC>;
fixed address <IP>;
};
Hope that helps!
Neil Horman
×ÞÌÎ wrote:
>
> Hello:
> I'm a newer to PowerPC. when i port linux to PowerPC 8240,i met some problem.anyone give me advices will be appreciate.
> i use board sandpoint 3, the cpu board is mpc8240.
> I mark the line i wish you pay attention to.i have two questions: one is why the hdc lost the interrupt. the other is why the bootp time out. i test the host dhcp configuration with win98 as client.
> The dip switch on cpu board is set to : sw2 01111,sw3 11011 (1 means ON)
> BTW,who could tell me every bit of the two dip switch mean? I couldn't find document about it.
> The dip switch on main board is set to: sw1 11111010 ,sw2 11111111.
> The type of main board is "ppceval-sp3 rev x3". the CPU board is
> "m98ppmc8240 rev x2" .linux kernel is Mvista Hard Hat Linux 2.0 for
> ppc 82xx. My hard disk type is "Quantum fireball 3.5series 30.0GB".
> the following is bootup message:
>
> DINK32_KAHLUA >>dl -k
> #>ascii-xfr -svn -l 10 vmlinuz-motolola-sandpoint.srec>/dev/ttyS0
> DINK32_KAHLUA >>go 900000
> loaded at: 00900000 009091B8
> relocated to: 00800000 008091B8
> zimage at: 00906000 00998F41
> avail ram: 00400000 00800000
>
> Linux/PPC load:
> Uncompressing Linux...done.
> Now booting the kernel
> Total memory = 32MB; using 0kB for hash table (at 00000000)
> Linux version 2.4.2_hhl20 (root@tony) (gcc version 2.95.3 20010315 (release/Mon1Motorola SPS Sandpoint Test Platform
> Sandpoint port (C) 2000, 2001 MontaVista Software, Inc. (source@mvista.com)
> On node 0 totalpages: 8192
> zone(0): 8192 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line:
> OpenPIC Version 1.2 (1 CPUs and 24 IRQ sources) at f7fd0000
> OpenPIC timer frequency is 100.000000 MHz
> time_init: decrementer frequency = 24.752286 MHz
> Calibrating delay loop... 131.89 BogoMIPS
> Memory: 30596k available (1048k kernel code, 440k data, 88k init, 0k highmem)
> Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Inode-cache hash table entries: 2048 (order: 2, 16384 bytes)
> POSIX conformance testing by UNIFIX
> PCI: Probing PCI hardware
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Starting kswapd v1.8
> pty: 256 Unix98 ptys configured
> block: queued sectors max/low 20256kB/6752kB, 64 slots per queue
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> W82C105: IDE controller on PCI bus 00 dev 59
> W82C105: chipset revision 5
> W82C105: 100% native mode on irq 17
> ide0: BM-DMA at 0xbfffd0-0xbfffd7, BIOS settings: hda:pio, hdb:pio
> SL82C105 command word: 5
> IDE timing: 00000909, resetting to PIO0 timing
> ide1: BM-DMA at 0xbfffd8-0xbfffdf, BIOS settings: hdc:pio, hdd:pio
> SL82C105 command word: 5
> IDE timing: 000003e4, resetting to PIO0 timing
> hdc: QUANTUM FIREBALLP AS30.0, ATA DISK drive
> ide1 at 0xbfffe8-0xbfffef,0xbfffe6 on irq 15
> hdc: 58633344 sectors (30020 MB) w/1902KiB Cache, CHS=58168/16/63
> /*******************************************************************************
> Partition check:
> hdc:hdc: lost interrupt
> hdc: lost interrupt
> hdc: lost interrupt
> hdc: lost interrupt
> hdc: lost interrupt
> [PTBL] [3649/255/63] hdc1 <hdc: lost interrupt
> hdc: lost interrupt
> hdc5hdc: lost interrupt
> hdc: lost interrupt
> hdc6 >
> *******************************************************************************/
> loop: loaded (max 8 devices)
> Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI endttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 2048 bind 2048)
> /*******************************************************************************
> Sending BOOTP requests.......<6>NETDEV WATCHDOG: eth0: transmit timed out
> ....<6>NETDEV WATCHDOG: eth0: transmit timed out .. timed out!
> ********************************************************************************/
> IP-Config: No network devices available.
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> request_module[block-major-2]: Root fs not mounted
> VFS: Cannot open root device "" or 02:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 02:00
>
> and I use tcpdump to listen to the eth0, and receive something like that:
>
> 14:34:27.591370 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc6c3f016 secs:88 [|bootp] (DF)
> 14:34:27.591925 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc: xid:0xc6c3f016 secs:88 Y:192.168.10.100 S:192.168.10.13 ether 0:e0:4c:45:56:af [|bootp] (DF)
> 14:34:27.595609 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:28.591256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:29.591256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:30.591402 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:30.591402 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:32.601383 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:33.601256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:34.601256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:35.601276 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:35.601276 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:37.612096 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:38.611257 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:39.611257 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:40.611278 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:40.611278 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:42.621330 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:43.621256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:44.621256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:45.621277 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:45.621277 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:47.633769 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:48.631263 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:49.631256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:50.631277 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:50.631277 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:52.641343 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:53.641271 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:54.641268 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13 (0:e0:4c:3b:f6:ca)
> 14:34:55.641289 lo > 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:55.641289 lo < 192.168.10.13 > 192.168.10.13: icmp: host 192.168.10.1 unreachable [tos 0xc0]
> 14:34:55.711924 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc6c3f016 secs:117 [|bootp] (DF)
> 14:34:55.712391 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc: xid:0xc6c3f016 secs:117 Y:192.168.10.100 S:192.168.10.13 ether 0:e0:4c:45:56:af [|bootp] (DF)
> 14:35:25.712515 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc6c3f016 secs:147 [|bootp] (DF)
> 14:35:25.713052 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc: xid:0xc6c3f016 secs:147 Y:192.168.10.100 S:192.168.10.13 ether 0:e0:4c:45:56:af [|bootp] (DF)
>
> It seems that the host ack the target's require, but target did't accept . So the target has no right IP address.
>
> regards.
> stone
>
> ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡stone@pocketix.com
> ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-01-15
>
--
/***************************************
*Neil Horman
*Master of Software Feng Shui
*Lvl7 Systems
*(919)-865-2915
***************************************/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: 8240 booting:bootp time out and hd lost interrupt
2002-01-15 12:03 ` Neil Horman
@ 2002-01-15 12:50 ` Jerry Van Baren
0 siblings, 0 replies; 3+ messages in thread
From: Jerry Van Baren @ 2002-01-15 12:50 UTC (permalink / raw)
To: linuxppc-embedded
On the bootp time out, you appear to be sending ARP packets and not getting
a response. Is your BOOTP server properly configured? To be specific, is
it configured to be 192.168.10.1? Your etherdump trace (ARP with no
response and ICMP "unreachable" error packets) implies not. Ping it to
check, preferably from your custom MPC860P board.
Are you sniffing the ethernet from a different machine than your custom
MPC860P board? You should be: otherwise you don't know if the packet
actually gets transmitted on the ethernet. This could also cause the "no
ARP response" symptoms you show.
It probably isn't significant, and could just be my ignorance, but there
also appears to be a missmatch with the MAC address used: your bootp line
shows 0:e0:4c:45:56:af but your ARP request appears to be using
0:e0:4c:3b:f6:ca.
gvb
At 07:03 AM 1/15/2002 -0500, Neil Horman wrote:
>Hello-
> Not sure if these are going to be you're exact answers, but I've
>recently tackled both problems on a custom MPC860P based board:
[snip]
>2)
> >the other is why the bootp time out. i test the host dhcp configuration
> with >win98 as client.
> It looks to me as though you don't have your bootp server set up
>properly. Looking at your tcpdump, I see you sending out bootp requests
>(eth0 B 0.0.0.0 >....), but I see no responsees. The 192.168.10.13
>address appears multiple times in your tcpdump prior to your bootp
>requests being sent (even on the lo interface which is odd), so it looks
>like that may be a configuration error (perhaps something you passed in
>on the kernel command line?). The fact that you can boot a Win98 client
>with your DHCP server just means that it serves DHCP requests well,
>which are close to, but not bootp requests. I use the ISC DHCP server
>here under red hat 7.1, and to use it to serve bootp requires that I add
>a special bootp entry for every address I wish to serve, like this:
>host <name>:
>{
>hardware ethernet <MAC>;
>fixed address <IP>;
>};
>
>Hope that helps!
>Neil Horman
>
>
>
>
>×ÞÌÎ wrote:
> >
> > Hello:
> > I'm a newer to PowerPC. when i port linux to PowerPC 8240,i met some
> problem.anyone give me advices will be appreciate.
> > i use board sandpoint 3, the cpu board is mpc8240.
> > I mark the line i wish you pay attention to.i have two questions: one
> is why the hdc lost the interrupt. the other is why the bootp time out. i
> test the host dhcp configuration with win98 as client.
> > The dip switch on cpu board is set to : sw2 01111,sw3 11011 (1 means ON)
> > BTW,who could tell me every bit of the two dip switch mean? I
> couldn't find document about it.
> > The dip switch on main board is set to: sw1 11111010 ,sw2 11111111.
> > The type of main board is "ppceval-sp3 rev x3". the CPU board is
> > "m98ppmc8240 rev x2" .linux kernel is Mvista Hard Hat Linux 2.0 for
> > ppc 82xx. My hard disk type is "Quantum fireball 3.5series 30.0GB".
> > the following is bootup message:
> >
[snip]
> > loop: loaded (max 8 devices)
> > Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ
> SERIAL_PCI endttyS00 at 0x03f8 (irq = 4) is a 16550A
> > ttyS01 at 0x02f8 (irq = 3) is a 16550A
> > NET4: Linux TCP/IP 1.0 for NET4.0
> > IP Protocols: ICMP, UDP, TCP
> > IP: routing cache hash table of 512 buckets, 4Kbytes
> > TCP: Hash tables configured (established 2048 bind 2048)
> >
> /*******************************************************************************
> > Sending BOOTP requests.......<6>NETDEV WATCHDOG: eth0: transmit timed out
> > ....<6>NETDEV WATCHDOG: eth0: transmit timed out .. timed out!
> >
> ********************************************************************************/
> > IP-Config: No network devices available.
> > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> > Root-NFS: No NFS server available, giving up.
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > request_module[block-major-2]: Root fs not mounted
> > VFS: Cannot open root device "" or 02:00
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on 02:00
> >
> > and I use tcpdump to listen to the eth0, and receive something like
> that:
> >
> > 14:34:27.591370 eth0 B 0.0.0.0.bootpc >
> 255.255.255.255.bootps: xid:0xc6c3f016 secs:88 [|bootp] (DF)
> > 14:34:27.591925 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc:
> xid:0xc6c3f016 secs:88 Y:192.168.10.100 S:192.168.10.13 ether
> 0:e0:4c:45:56:af [|bootp] (DF)
> > 14:34:27.595609 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:28.591256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:29.591256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:30.591402 lo > 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:30.591402 lo < 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:32.601383 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:33.601256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:34.601256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:35.601276 lo > 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:35.601276 lo < 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:37.612096 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:38.611257 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:39.611257 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:40.611278 lo > 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:40.611278 lo < 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:42.621330 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:43.621256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:44.621256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:45.621277 lo > 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:45.621277 lo < 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:47.633769 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:48.631263 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:49.631256 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:50.631277 lo > 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:50.631277 lo < 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:52.641343 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:53.641271 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:54.641268 eth0 > arp who-has 192.168.10.1 tell 192.168.10.13
> (0:e0:4c:3b:f6:ca)
> > 14:34:55.641289 lo > 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:55.641289 lo < 192.168.10.13 > 192.168.10.13: icmp: host
> 192.168.10.1 unreachable [tos 0xc0]
> > 14:34:55.711924 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0xc6c3f016 secs:117 [|bootp] (DF)
> > 14:34:55.712391 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc:
> xid:0xc6c3f016 secs:117 Y:192.168.10.100 S:192.168.10.13 ether
> 0:e0:4c:45:56:af [|bootp] (DF)
> > 14:35:25.712515 eth0 B 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0xc6c3f016 secs:147 [|bootp] (DF)
> > 14:35:25.713052 eth0 > 192.168.10.13.bootps > 255.255.255.255.bootpc:
> xid:0xc6c3f016 secs:147 Y:192.168.10.100 S:192.168.10.13 ether
> 0:e0:4c:45:56:af [|bootp] (DF)
> >
> > It seems that the host ack the target's require, but target did't
> accept . So the target has no right IP address.
> >
> > regards.
> >
> stone
> >
> > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡stone@pocketix.com
> > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-01-15
> >
>
>--
>/***************************************
>*Neil Horman
>*Master of Software Feng Shui
>*Lvl7 Systems
>*(919)-865-2915
>***************************************/
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-01-15 12:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-15 10:22 8240 booting:bootp time out and hd lost interrupt 邹涛
2002-01-15 12:03 ` Neil Horman
2002-01-15 12:50 ` Jerry Van Baren
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).