On Tue, Sep 02, 2003 at 10:23:02AM +0200, Jan Srzednicki wrote: > > I've gone over the probe code once again. > > > > Please test, and in case it fails to detect or misdetects anything, > > mail me the output of dmesg from a verbose boot, and state what > > devices actually are there. > > Hello, > > The new stuff still failed to detect properly my hardware. Whole dmesg is > attached. But, mysteriously, after two reboots the problem vanished, and > I can see my HW as I should:
OK, the drive did not get detected once again. This seems to be pretty random. > Anyway, > On the new kernel, reboot (after waiting for all the fsck's to finish) > resulted in panic when syncer was called to flush everything. This has > happened only once, I cannot reproduce it, yet the syncer problem > (giving up on 1 buffer) persist. It is not a problem with the aio > module, as I have removed it, and it still happens. Willing to provide > more feedback, if I knew how.. I've found this thing is related to ext2fs, as I stated in different thread. -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --=< Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! >=-- Queen -- _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
