Re: Intel Corporation 82578DC Gigabit NIC support
On Fri, Mar 4, 2011 at 1:10 PM, Chris Turner wrote: > On 03/03/11 22:47, Siju George wrote: >> >> OpenBSD detects it as em0 but dragonfly does not detect it :-( >> Is there any thing I need to do like kernel configurations etc? >> Or should I wait till the driver is ported? > > knowing nothing about the driver itself - > a quick check of our manual vs their manual > and it does look like the same driver > > I'd suggest hacking pcidevs and seeing what happens when you build it.. > it might just work > Thaks for your reply :-) Which files should I edit for this? > (or not, depending) > > basically pciconf -lv will show the device hex stuff, > and you can hack the general pcidevs file, > and the driver stuff that matches it > > when that's all in place, the driver should try to attach, > and either work, not work, or cause a panic :D > > after that well.. it's a matter of giving up or trying > to see what the differences are > > of course if someone else has this hw working, this is all moot. > FreeBSD on the same machine has got this working. em0: port 0xdc00-0xdc1f mem 0xfbbc-0xfbbd,0xfbbf6000-0xfbbf6fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] pciconf -lv on FreeBSD shows this output . $ pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x04011025 chip=0x00408086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x04011025 chip=0x00428086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0: class=0x078000 card=0x04011025 chip=0x3b648086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = simple comms atapci0@pci0:0:22:2:class=0x010185 card=0x04011025 chip=0x3b668086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA none1@pci0:0:22:3: class=0x070002 card=0x04011025 chip=0x3b678086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = simple comms subclass = UART em0@pci0:0:25:0:class=0x02 card=0x80001025 chip=0x10f08086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ehci0@pci0:0:26:0: class=0x0c0320 card=0x04011025 chip=0x3b3c8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB none2@pci0:0:27:0: class=0x040300 card=0x04011025 chip=0x3b568086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = multimedia subclass = HDA ehci1@pci0:0:29:0: class=0x0c0320 card=0x04011025 chip=0x3b348086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB pcib1@pci0:0:30:0: class=0x060401 card=0x04011025 chip=0x244e8086 rev=0xa6 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x04011025 chip=0x3b088086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci1@pci0:0:31:2:class=0x01018f card=0x04011025 chip=0x3b208086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'IBEX SATA Controller' class = mass storage subclass = ATA none3@pci0:0:31:3: class=0x0c0500 card=0x04011025 chip=0x3b308086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus atapci2@pci0:0:31:5:class=0x010185 card=0x04011025 chip=0x3b268086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'IBEX SATA Controller' class = mass storage subclass = ATA
Re: ad8: FAILURE - READ_DMA48 status=51 error=10 LBA=809594688
On Sun, May 29, 2011 at 12:54 PM, Francois Tigeot wrote: > >> >> ad8: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=809594688 >> ad8: FAILURE - READ_DMA48 status=51 >> error=10 LBA=809594688 > > Your hard-disk may be dying or you may have a problem with the cable/the > controller. > > What sort of disk is this ? If it's an old IDE model, is your ribbon cable > a 80-wire one ? > It may be worth it to change it. You may also want to reduce DMA speed as > a workaround (you should be able to do it from the BIOS). > Thanks a lot Francois for the reply :-) This error appears only some times. I refitted the cables of all hard disks once again and this error does not seem to occor for some time. The Disk is SATA disk scheduler: set policy of ad8 to noop ad8: 476940MB at ata4-master SATA150 disk scheduler: set policy of ad8 to noop ad8: 476940MB at ata4-master SATA150 What should I do to find out if the disk is working right? Is a # smartctl -t long /dev/ad8 enough? Also will this type of error affect the Integrity of hammer File System? Should I do some thing to Check the integrity of the file system ? My versions are dfly-bkpsrv# hammer version /Backup3 min=1 wip=none max=6 current=4 description="New undo/flush, faster flush/sync (DragonFly 2.5+)" available versions: I plan to upgrade to hammer v6 soon. Kernel is DragonFly v2.11.0.247.gda17d9-DEVELOPMENT #36: Mon May 23 12:57:37 IST 2011 Also How do I map ad8 etc to their sernos? The answer i got from this list earlier was to ls /dev/ and /dev/serno and match according to the order found there it was ok before there was ad10. Now ad10 shows up first even before ad4. so I am a bit confused. dfly-bkpsrv# cd /dev/ dfly-bkpsrv# ls acd0ad4s1g ad8s1 consolectl kmem psm0ttyd0 ttyv9 udev acpiad4s1h ad8s1d crypto log ptmxttyid0 ttyva urandom ad10ad6 apm cuaa0 lpt0 pts ttyld0 ttyvb usb ad10s1 ad6s1 ata cuaia0 lpt0.ctlrandom ttyv0 ttyvc usb0 ad10s1d ad6s1a bpf cuala0 md0 serno ttyv1 ttyvd usb1 ad4 ad6s1b bpf0devctl md0s0 sg0 ttyv2 ttyve usb2 ad4s1 ad6s1d bpf1devfs mem sga ttyv3 ttyvf xpt0 ad4s1a ad6s1e bpf2fd null stderr ttyv4 tun zero ad4s1b ad6s1f bpf3io part-by-uuidstdin ttyv5 tun0 ad4s1d ad6s1g bpsm0 kbd0pass0 stdout ttyv6 tun1 ad4s1e ad6s1h cd0 kbd1pci sysmousettyv7 tun2 ad4s1f ad8 console klogppi0 tty ttyv8 tun3 dfly-bkpsrv# cd /dev/serno/ dfly-bkpsrv# ls 9QMAS4SZ9QMAS4SZ.s1b9QMAS4SZ.s1f9QMATBHX 9QMATBHX.s1b9QMATBHX.s1f9VMRFDSY9VMRG202 9QMAS4SZ.s1 9QMAS4SZ.s1d9QMAS4SZ.s1g9QMATBHX.s1 9QMATBHX.s1d9QMATBHX.s1g9VMRFDSY.s1 9VMRG202.s1 9QMAS4SZ.s1a9QMAS4SZ.s1e9QMAS4SZ.s1h9QMATBHX.s1a 9QMATBHX.s1e9QMATBHX.s1h9VMRFDSY.s1d9VMRG202.s1d Thanks --Siju
Re: ad8: FAILURE - READ_DMA48 status=51 error=10 LBA=809594688
Hi, On Thu, May 26, 2011 at 03:45:59PM +0530, Siju George wrote: > > I am getting plenty of the following error. > My Kernel Version is DragonFly v2.11.0.247.gda17d9-DEVELOPMENT #36: > Mon May 23 12:57:37 IST 2011 GENERIC > > What could be the trouble? > > ad8: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=809594688 > ad8: FAILURE - READ_DMA48 status=51 > error=10 LBA=809594688 Your hard-disk may be dying or you may have a problem with the cable/the controller. What sort of disk is this ? If it's an old IDE model, is your ribbon cable a 80-wire one ? It may be worth it to change it. You may also want to reduce DMA speed as a workaround (you should be able to do it from the BIOS). -- Francois Tigeot
