On Mon, Sep 01, 2003 at 01:16:00PM +0200, Soren Schmidt 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: GEOM: create disk ad0 dp=0xc409ee70 ad0: 19546MB <FUJITSU MPF3204AT> [39714/16/63] at ata0-master UDMA66 GEOM: create disk ad1 dp=0xc409ed70 ad1: 39093MB <FUJITSU MPG3409AH EF> [79428/16/63] at ata0-slave UDMA66 acd0: CDROM <CD-540E> at ata1-master UDMA33 acd1: CDRW <CD-W540E> at ata1-slave UDMA33 cd0 at ata1 bus 0 target 0 lun 0 cd0: <TEAC CD-540E 1.0A> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [348277 x 2048 byte records] cd1 at ata1 bus 0 target 1 lun 0 cd1: <TEAC CD-W540E 1.0C> Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: cd present [1 x 0 byte records] (this funny phantom CD inside of my drives is still there ;) I don't have any idea why this thing was not working in the begining. I did not touch anything, I swear. ;) 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.. greets, -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- w_at_dream.vg --- w_at_303.krakow.pl --===-- 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 --
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:21 UTC