Re: Easy Guide / new tarball
Roland McGrath <roland@frob.com> wrote:
> Use `ps -MA'. The -M flag avoids messages to processes' message ports,
> which can hang if things are in a bad state. (You will see less
> information this way.)
Thanks.
> > Is this normal Hurd behavior these days?
>
> Many people are seeing lossage like this. I have not seen it myself so as
> to attempt to debug it.
Do you live near Cambridge, Mass.? You're welcome to come and have a
look.
Pentium 60MHz
3c509
24 MB RAM
4.3 GB hd0
hd0s1 /linux ext2 readonly 250MB at offset 0
hd0s2 / ext2 250MB at offset 250MB
hd0s5 /install ext2 350MB
hd0s6 /jtobey ext2 350MB
hd0s8 Linuxy swap 100MB
2 NFS mounts, one readonly
Running several rshd + xterm pairs, some with cwd on nfs.
> > btw, I saw a failed assertion in libdiskfs about an unexpected fault,
>
> Tell us what it said!!
>
> > and just now I saw 50 or so like this:
> >
> > memory_object_data_request(0x0, 0x0, 0x17000, 0x1000, 0x1) failed, 268435459
> > ^^^^^^^ only this varies
>
> These messages (from the kernel) are normal fallout from an external pager
> dying (the filesystem servers are external pagers). So whatever you saw
> before this is most likely the interesting part.
Well, it scrolled by pretty fast with the kernel messages appearing,
but I believe it was libdiskfs/disk-pager.c:93 `env && "unexpected
fault on disk image"'. I saw this with the last hurd (19990923?) too.
Hope this helps.
-John
Reply to: