Re: Strange behavior on new machine (ioapic, nfs)

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Wed, Jul 21, 2010 at 06:27:29PM +0100, Patrick Welche wrote:
> Just had the opportunity to try some other switches - server and client
> running with code from 19th and 21st July 2010 respectively:
> (bge0 as above, wm0 02901I mobile (AMT) LAN Controller, rev 3)
> 
> Works:
>  server nfe0 <---> netgear gigabit <---> 3com 2824 <---> netboot client wm0
>                1G                    1G              1G
> 
> Fails:
>  server nfe0 <---> netgear gigabit <---> 3com 4400 <---> netboot client wm0
>                1G                   100M           100M
> 
>  server nfe0 <---> netgear gigabit <---> 3com 3300 <---> netboot client wm0
>                1G                   100M           100M
> 
>  server nfe0 <--->   3com 2824     <---> 3com 3300 <---> netboot client wm0
>                1G                   100M           100M
> 
> I didn't retest the previous failures (4400 has a 1G module):
>  server nfe0 <---> netgear gigabit <---> 3com 4400 <---> netboot client wm0
>  server nfe0 <---> netgear gigabit <---> 3com 4400 <---> netboot client bge0
>                1G                   100M             1G
> 
> Again the failure is after 12 megabytes of kernel are successfully
> downloaded, and as it tries to mount its root partition. The dhcp request
> with the root partition details is received, then
> 
>   lookup fh for dev OK
>   lookup fh for console fails (fair enough, init makes a tmpfs /dev)
>   lookup fh for sbin OK
>   lookup fh for init OK, access attr, getattr OK
>   read 30736 bytes of init (init is that long) gets
> 
> IP (tos 0x0, ttl 64, id 15, offset 0, flags [none], proto UDP (17), length 
> 132) client.2479824598 > server.nfs: 104 read fh 18,36/6081646 30736 bytes @ 0
> IP (tos 0x0, ttl 64, id 4860, offset 0, flags [+], proto UDP (17), length 
> 1500, bad cksum 0 (->d27d)!) server.nfs > client.2479824598: reply ok 1472 
> read REG 555 ids 0/0 sz 30736 nlink 1 rdev 3313/5896 fsid 1224 fileid 5ccc6e 
> a/m/ctime 1279731571.984613442 1279639970.000000 1279642650.115731470 30736 
> bytes EOF
> IP (tos 0x0, ttl 64, id 4860, offset 1480, flags [+], proto UDP (17), length 
> 1500, bad cksum 0 (->d1c4)!) server> client: udp
> 
> The last line repeats, and the client doesn't boot.

Just checking the content of those udp packets:

The nfs server keeps sending /sbin/init - handy having "catatonia" at the
end of the file...

Client sits there - the last thing on its screen is
init: copying out path '/sbin/init' 11

In the working all-gigabit case, the client would then do
lookup fh 18,36/5777417 "libexec"

What is the client waiting for?

Cheers,

Patrick