Re: 6.0-REL && ports/devel/subversion



On Fri, 30 Dec 2005 23:33:21 -0800 Kent Stewart escribio

> On Friday 30 December 2005 11:04 pm, guru@xxxxxxxx wrote:
> > ...
> >
> > with the PANIC's I still have to work out, what's going on; I can
> > now reproduce them by:
> >
> > - booting into normal runlevel
> > - login as root and than
> > # kldload kqemu
> > # kldstat
> > # su - user --> PANIC
> >
> > Any hints on that?
>
> Boot to single user and fsck your system. It sounds like you have some
> bad sectors. If the fsck removed anything you just added such as header
> files, you could have problems like you saw. FreeBSD will do a
> background fsck but sometimes you need to do it in the foreground.

I think I did one of the fsck in foreground because it was unable
to repair the file system and asked me to do it manualy; but I'll
do it again in single user; I also have now fetched sysutils/memtest
and will stress the memory because the 1st PANIC occured before
I had build qemu, ie. I don't think that this is related to that
kernel module itself; after the memtest I'll do a complete reinstall
from scratch of the 6.0-RELEASE from CD;

> With a release, any panic is important. They just don't happen unless
> something is wrong. Portupgrade or portmanage can reduce the chances of
> building modules out of order. If you build them manually out of order,
> problems like the one you saw with neon can happen.

I did not do that, I've just installed 6.0-RELEASE from the distribution
CD-ROM and after the primary installation procedure I went to
/usr/ports/x11/kde3 to make the desktop KDE and meanwhile that I
was copying my files from my home dir of the old notebook (only userland
files, nothing in kernel) and this gave the first PANIC after some
hours;

>
> If it is software, you can back out ports that you load until you don't
> have problems.

this time after the installation of 6.0-RELEASE I'll only make
/usr/ports/emulators/qemu to see if I can reproduce the PANIC
with the above procedure; we will see...

I'm not in hurry, because the old notebook is still alive...

Thanks for your hints so far. ¡Qué tengas buen Fin del Año!

Matthias
--
Matthias Apitz / Sisis Informationssysteme GmbH
http://www.sisis.de/~guru/
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: File System crash
    ... > My linux installation is a Debian Woody (just downloaded the image files ... > After running fsck Debian started fine again, ... I suspect that at some level disk addresses beyond 128 GiB ... so I would check your kernel version. ...
    (Debian-User)
  • Re: [SLE] Booting Problem
    ... Please repair manually and reboot. ... except rebooting during the installation. ... > 'fsck failed' again. ... that normally it is NOT a problem with a partition gone bad. ...
    (SuSE)
  • Re: Murphy hits (Kernel 2.6, ext2, "check=strict"): corrupted filesystem
    ... >> installation. ... There is a minor bug in the forementioned ... it actually saved me once when I was hitting fsck bug. ... The other stupid thing that doesn't belong to this list is: RPM v4 ...
    (Linux-Kernel)
  • Re: [SLE] Booting Problem
    ... CONTROL-D will exit from this shell and REBOOT the system. ... except rebooting during the installation. ... 'fsck failed' again. ... writes and reads to every block on the partition. ...
    (SuSE)
  • Re: [SLE] Booting Problem
    ... CONTROL-D will exit from this shell and REBOOT the system. ... except rebooting during the installation. ... 'fsck failed' again. ... writes and reads to every block on the partition. ...
    (SuSE)