Sil3112 dma errors
Hi all, recently I upgraded my kernel to the last version ( Aug 28 now, before was runing Aug 5 version ), and I startet to get error like this: Aug 27 17:03:23 pilkishome kernel: ad4: WARNING - WRITE_DMA recovered from missing interrupt Aug 27 17:03:23 pilkishome kernel: ad4: WARNING - WRITE_DMA soft error (ECC corrected)ad4: FAILURE - WRITE_DMA status=ff error=0... ad4: WARNING - WRITE_DMA recovery from missing interupt ad4: timeout sending command=ca ad4: error issuing DMA command after where is coming dma timeout, but in the syslog already nothing, system becomes unresponsible here is my uname and dmesg FreeBSD pilkishome.spo-tripoli.local 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Thu Aug 28 14:37:53 EEST 2003 root@:/usr/obj/usr/src/sys/GENERIC i386 upport enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=255d8086) pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f2320 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs slot 6 10A 0x60 3 4 5 7 9 10 11 12 slot 6 10B 0x61 3 4 5 7 9 10 11 12 embedded0 29A 0x60 3 4 5 7 9 10 11 12 embedded0 29B 0x63 3 4 5 7 9 10 11 12 embedded0 29C 0x62 3 4 5 7 9 10 11 12 embedded0 29D 0x6b 3 4 5 7 9 10 11 12 embedded0 31A 0x62 3 4 5 7 9 10 11 12 embedded0 31B 0x61 3 4 5 7 9 10 11 12 slot 1 20A 0x69 3 4 5 7 9 10 11 12 slot 1 20B 0x6a 3 4 5 7 9 10 11 12 slot 1 20C 0x6b 3 4 5 7 9 10 11 12 slot 1 20D 0x68 3 4 5 7 9 10 11 12 slot 2 21A 0x6a 3 4 5 7 9 10 11 12 slot 2 21B 0x6b 3 4 5 7 9 10 11 12 slot 2 21C 0x68 3 4 5 7 9 10 11 12 slot 2 21D 0x69 3 4 5 7 9 10 11 12 slot 3 22A 0x6b 3 4 5 7 9 10 11 12 slot 3 22B 0x68 3 4 5 7 9 10 11 12 slot 3 22C 0x69 3 4 5 7 9 10 11 12 slot 3 22D 0x6a 3 4 5 7 9 10 11 12 slot 4 26A 0x68 3 4 5 7 9 10 11 12 slot 4 26B 0x69 3 4 5 7 9 10 11 12 slot 4 26C 0x6a 3 4 5 7 9 10 11 12 slot 4 26D 0x6b 3 4 5 7 9 10 11 12 slot 5 27A 0x62 3 4 5 7 9 10 11 12 slot 5 27B 0x63 3 4 5 7 9 10 11 12 slot 5 27C 0x60 3 4 5 7 9 10 11 12 slot 5 27D 0x61 3 4 5 7 9 10 11 12 embedded25A 0x62 3 4 5 7 9 10 11 12 embedded23A 0x61 3 4 5 7 9 10 11 12 embedded24A 0x69 3 4 5 7 9 10 11 12 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 3, max = 3, width = 0 ACPI timer looks BAD min = 3, max = 1060, width = 1057 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks BAD min = 3, max = 1055, width = 1052 ACPI timer looks GOOD min = 3, max = 3, width = 0 ACPI timer looks BAD min = 3, max = 1055, width = 1052 ACPI timer looks GOOD min = 3, max = 3, width = 0 ACPI timer looks BAD min = 3, max = 1055, width = 1052 ACPI timer looks GOOD min = 3, max = 3, width = 0 ACPI timer looks BAD min = 3, max = 1052, width = 1049 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.0 \\_SB_.LNKD irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.1 \\_SB_.LNKC irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.2 \\_SB_.LNKH irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.3 \\_SB_.LNKC irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.0 \\_SB_.LNKB irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.1 before setting priority for links before fixup boot-disabled links - after fixup boot-disabled links -- arbitrated configuration - \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.0 \\_SB_.LNKD irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.1 \\_SB_.LNKC irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.2 \\_SB_.LNKH irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.3 \\_SB_.LNKC irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.0 \\_SB_.LNKB irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.1 pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base f800, size 26, enab
Re: Sil3112 dma errors
1. It's written only Advance Peripherals , looks like this http://www7.alternate.de/prodpic/200x200/f/fpba03.jpg 2. Nope , network is connected only to 100 mbit switch, and most often the problem occurs when there is higher i/o with disk ( like kernel compiling or make buildworld ) which I usually do over ssh remotely, but same thing happened via console and even when booting on the starting up services. - Original Message - From: Soren Schmidt To: Putinas Cc: [EMAIL PROTECTED] Sent: Thursday, August 28, 2003 13:43 PM Subject: Re: Sil3112 dma errors It seems Putinas wrote: > Hi all, > recently I upgraded my kernel to the last version ( Aug 28 now, before was > runing Aug 5 version ), and I startet to get error like this: > Aug 27 17:03:23 pilkishome kernel: ad4: WARNING - WRITE_DMA recovered from > missing interrupt > Aug 27 17:03:23 pilkishome kernel: ad4: WARNING - WRITE_DMA soft error (ECC > corrected)ad4: FAILURE - WRITE_DMA > status=ff error=0... > > ad4: WARNING - WRITE_DMA recovery from missing interupt > ad4: timeout sending command=ca > ad4: error issuing DMA command > > after where is coming dma timeout, but in the syslog already nothing, system > becomes unresponsible Hmm two things: what kind of SATA->PATA dongles are you using ? Do you have any significant traffic on the gigE interface ? -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sony vaio pcg-gr390
Hi all, I tried to check might be my problem with choppy sound is fixed on my notebook ( definitly has problems with interupts and acpi , because sound becomes more or less acceptable if I make ping -f something outside - sound card and network uses same interupt ). I upgraded to latest src, compile GENERIC, reboot... and whops: hanging where initializing pcmcia ( or the something what goes after this ? ) this is if I boot with ACPI enabled. If I boot with acpi disabled - panic and debuging screen ... So just to pay developers attention to this problem .. because I saw already to mails about notebooks and acpi ... Best regards, Putinas Piliponis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sil3112 dma errors
I did, inserted intel pro 100, disabled gig in bios, I booted up, removed icmp limit in sysctl from 200 to 0 , started ping -f from other server, cd /usr/src; make buildworld and lockup instantly ... I saw just one line rm -rf something and dma errors are coming. I am sure this would happen and without ping -f from other server, but just makes things faster... I have cvsup'ed again and will try to rebuild world again tonight. - Original Message - From: Soren Schmidt To: Putinas Cc: [EMAIL PROTECTED] Sent: Thursday, August 28, 2003 14:58 PM Subject: Re: Sil3112 dma errors It seems Putinas wrote: > 1. It's written only Advance Peripherals , looks like this > http://www7.alternate.de/prodpic/200x200/f/fpba03.jpg OKies, not much to say about those, probably marvell based.. > 2. Nope , network is connected only to 100 mbit switch, and most often the > problem occurs when there is higher i/o with disk ( like kernel compiling or > make buildworld ) which I usually do over ssh remotely, but same thing > happened via console and even when booting on the starting up services. Hmm, I cant reproduce anything like this here, could you try to exchange the gigE card with something else ? (I've seen a fair amount of problems with bge based cards lately)... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sony vaio pcg-gr390
vices Device configuration finished. procfs registered Timecounter "TSC" frequency 1193108906 Hz quality 800 Timecounters tick every 10.000 msec lo0: bpf attached Current DB 0 ch = 0 Current OP KEY INT BR len Addr Depend Stat: Cnt 1f02c000 OUTL ST2 ALL ALL12 1f02c080 8411:0009 RUN,ACTIVE, ack complete(11) 0x00e0 0x0045 0xffba 0x acpi_cmbat0: battery initialization start acpi_cmbat0: battery initialization done, tried 1 times acpi_cmbat1: battery initialization start acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times cbb0: Unsupported card type detected cbb1: Unsupported card type detected ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad0: setting UDMA100 on Intel ICH3 chip ad0: ATA-5 disk at ata0-master ad0: 28615MB (58605120 sectors), 58140 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ar: FreeBSD check1 failed ata1-master: pio=0x0c wdma=0x22 udma=0x42 cable=40pin acd0: setting PIO4 on Intel ICH3 chip acd0: CDRW drive at ata1 as master acd0: read 1722KB/s (4134KB/s) write 1377KB/s (1377KB/s), 2048KB buffer, PIO4 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc [0] f:00 typ:7 s(CHS):0/1/1 e(CHS):1023/5/63 s:63 l:8385867 [1] f:00 typ:7 s(CHS):1023/255/63 e(CHS):1023/11/63 s:8385993 l:8385867 [2] f:80 typ:165 s(CHS):1023/255/63 e(CHS):1023/1/63 s:16771860 l:8385930 [3] f:00 typ:7 s(CHS):1023/255/63 e(CHS):1023/15/63 s:25157790 l:33447330 GEOM: Configure ad0s1, start 32256 length 4293563904 end 4293596159 GEOM: Configure ad0s2, start 4293628416 length 4293563904 end 8587192319 GEOM: Configure ad0s3, start 8587192320 length 4293596160 end 12880788479 GEOM: Configure ad0s4, start 12880788480 length 17125032960 end 30005821439 GEOM: Configure ad0s3a, start 0 length 134217728 end 134217727 GEOM: Configure ad0s3b, start 134217728 length 268435456 end 402653183 GEOM: Configure ad0s3c, start 0 length 4293596160 end 4293596159 GEOM: Configure ad0s3e, start 402653184 length 268435456 end 671088639 GEOM: Configure ad0s3f, start 671088640 length 268435456 end 939524095 GEOM: Configure ad0s3g, start 939524096 length 3354072064 end 4293596159 bus_explore done sbp_post_explore (sbp_cold=2) (probe1:sbp0:0:0:0): error 22 (probe1:sbp0:0:0:0): Unretryable Error (probe4:sbp0:0:3:0): error 22 (probe4:sbp0:0:3:0): Unretryable Error (probe5:sbp0:0:4:0): error 22 (probe5:sbp0:0:4:0): Unretryable Error (probe6:sbp0:0:5:0): error 22 (probe6:sbp0:0:5:0): Unretryable Error (probe7:sbp0:0:6:0): error 22 (probe7:sbp0:0:6:0): Unretryable Error (probe2:sbp0:0:1:0): error 22 (probe2:sbp0:0:1:0): Unretryable Error (probe3:sbp0:0:2:0): error 22 (probe3:sbp0:0:2:0): Unretryable Error (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present Unretryable error (probe0:umass-sim0:0:0:0): error 6 (probe0:umass-sim0:0:0:0): Unretryable Error Mounting root from ufs:/dev/ad0s3a WARNING: / was not properly dismounted start_init: trying /sbin/init WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted - Original Message - From: Andre Guibert de Bruet To: Putinas Cc: [EMAIL PROTECTED] Sent: Friday, August 29, 2003 22:28 PM Subject: Re: sony vaio pcg-gr390 On Fri, 29 Aug 2003, Putinas wrote: > I tried to check might be my problem with choppy sound is fixed on my notebook ( definitly has problems with interupts and acpi , because sound becomes more or less acceptable if I make ping -f something outside - sound card and network uses same interupt ). > I upgraded to latest src, compile GENERIC, reboot... and whops: > hanging where initializing pcmcia ( or the something what goes after this ? ) this is if I boot with ACPI enabled. > If I boot with acpi disabled - panic and debuging screen ... > > So just to pay developers attention to this problem .. because I saw already to mails about notebooks and acpi ... Could you boot -v with acpi enabled and post the log somewhere? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng probe updated please test
looks like and my problem with sil 3112 which still exist... - Original Message - From: Daniel Rock To: Soren Schmidt Cc: [EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 16:15 PM Subject: Re: ATAng probe updated please test Just an additional notice: Booting in PIO mode (by setting hw.ata.ata_dma=0 in /boot/loader.conf): [...] GEOM: create disk ad0 dp=0xc10b3b70 ad0: 9671MB [20960/15/63] at ata0-master PIO4 GEOM: create disk ad1 dp=0xc10b3470 ad1: 1221MB [2482/16/63] at ata1-master PIO4 Waiting 2 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0a But if I try to set DMA mode later via atacontrol, the problem reappears: # atacontrol mode 0 udma2 udma2 Master = UDMA33 Slave = BIOSPIO # atacontrol mode 1 udma2 udma2 Master = WDMA2 Slave = BIOSPIO ad0: WARNING - WRITE_DMA recovered from missing interrupt ad1: WARNING - READ_DMA recovered from missing interrupt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Entropy harvesting: interrupts ethernet point_to_point
Hi all, on the recent src with custom compiled kernel ( generic minus some stuff what I don't need ) with firewall compiled in kernel , system infinitely hangs on boot unless I press ctrl-c at this point: Entropy harvesting: interrupts ethernet point_to_point Same things happens on two different computers with nearly similar custom kernel configuration Could you tell me, what's causing the problem ? * If needed I can submit my kernel configuration * Regards, Putinas Piliponis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Entropy harvesting: interrupts ethernet point_to_point
load: 0.95 cmd: sysctl 110 [running] 2.51m(micro) 12.00s 0% 436k ( here is output from ctrl-t ) I did like sugested before , hanging point is: [ -w /dev/random ] feed_dev_random /entropy [ -f /entropy -a -r /entropy -a -s /entropy ] cat /entropy dd of=/dev/random bs=8k dd of=/dev/random bs=8k ps -fauxww sysctl -a Actually what I forgot to tell in my previous mail what sysctl -a stoped working for me, but now I see what this is actually and IS the problem. if I do sysctl -a from console the last things what its output is: net.inet.ipf.fr_minttl: 3 net.inet.ipf.fr_minttllog: 1 thats it , here I have to press ctrl-c and also part of my custom kernel, I tried to commend RANDOM_IP_ID, PFIL_HOOKS but I got same results : options INCLUDE_CONFIG_FILE options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default options IPV6FIREWALL#firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT#divert sockets options IPFILTER#ipfilter support options IPFILTER_LOG#ipfilter logging options IPSTEALTH #support for stealth forwarding options PFIL_HOOKS options TCPDEBUG options RANDOM_IP_ID options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options DUMMYNET options BRIDGE options DEVICE_POLLING - Original Message - From: Mark Murray To: Putinas Cc: [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 12:40 PM Subject: Re: Entropy harvesting: interrupts ethernet point_to_point "Putinas" writes: > Hi all, > on the recent src with custom compiled kernel ( generic minus some stuff > what I don't need ) with firewall compiled in kernel , system infinitely > hangs on boot unless I press ctrl-c at this point: > Entropy harvesting: interrupts ethernet point_to_point > Same things happens on two different computers with nearly similar custom > kernel configuration > Could you tell me, what's causing the problem ? > * If needed I can submit my kernel configuration * When it hangs, please press -T, and report back the status line that you get in response. Thanks! M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Entropy harvesting: interrupts ethernet point_to_point
But I wonder, what sysctl has to do with hardware ? - Original Message - From: Doug Barton To: Putinas Cc: [EMAIL PROTECTED] ; Mark Murray Sent: Thursday, September 04, 2003 18:30 PM Subject: Re: Entropy harvesting: interrupts ethernet point_to_point -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've seen this problem on my compaq evo n610c as well, but didn't realize it was affecting other hardware as well. I tried to stir up interest in getting the acpi problem fixed, but wasn't successful. Mark, ok with you if I nuke the sysctl -a line in rc.d/initrandom? I hate to lose that source (no matter how small), but if the "can't finish sysctl -a" cancer is spreading... Doug - -- This .signature sanitized for your protection -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/V2i4yIakK9Wy8PsRAj9xAKDln9La1f89JUzxNm4Q9OlQbFD5PgCgyUuO A8HcT5QFudf0ohwrpDebZTE= =qrg7 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cosmetic bug in newsyslog ?
Hi all, maybe not really proper mailling list, I just cvsuped 4.9 prerelease and funny thing with syslog this is newsyslog.conf /var/log/httpd-referer.log 644 20*$M1D0 BZ /var/run/httpd.pid 30 this is newsyslog -v output /var/log/httpd-referer.log <20Z>: --> will trim at Mon Sep 1 00:00:00 2003 and this is date today: Sun Sep 7 11:34:48 EET 2003 If I would believe the output, the log rotation would NEVER hapen :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: My current box still got panic after ATAng
I started to get panic in ufs after few system crashes, and what I found what to run fsck once is not enough. After crash I had to run 3 times fsck -y until it stoped saying about any error ( only 4th pass was ok ). I just was wondering is it meant to be like this ? - Original Message - From: "Shin-ichi Yoshimoto" <[EMAIL PROTECTED]> To: "Soren Schmidt" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, September 09, 2003 10:45 AM Subject: Re: My current box still got panic after ATAng > Subject: Re: My current box still got panic after ATAng, > On Tue, 9 Sep 2003 09:19:01 +0200 (CEST), Soren Schmidt wrote: > > Hmm, have you run fsck on that filesystem lately ? > > Yes, every panic. > > -- > Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]> > http://diary.waishi.jp/~yosimoto/diary/ > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA drive lock-up
Since Adapted 1210SA is based on Sil3112A controller I still also have same problem what I reported few weeks before with my onboard sil3112a controller. tested tonight with fresh kernel - Original Message - From: "Soren Schmidt" <[EMAIL PROTECTED]> To: "Derek Ragona" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 20, 2003 10:07 AM Subject: Re: SATA drive lock-up It seems Derek Ragona wrote: > I have a single SATA drive on an Adaptec 1210SA card. > > The drive will give a write error warning a few times, then will repeatedly > give: > ad4: timeout sending command=ca > > The only recovery is the reset switch, reboot single-user fsck, and then > come back up in multiuser. > > These errors occur with disk access, but not with a predictable nature (not > on large files, or small files, etc.) And you are on an uptodate -current ? If so I'd suspect HW ... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA drive lock-up
Hi all, Inspired with all the FreeBSD is free software , windows and buggy hardware and blabla I realize what maybe I could do more to help solve this problem. I made small research on my computer and I find out what till the cvsup date 2003.08.24.00.00.00 till ATAng commitment to the source my SATA Sil3112A working fine. After this date I always get WRITE_DMA recovered from missing interrupt error after more or less intensive input output with harddisk subsystem , and after I/O error and so on ... My bet is what in this case buggy is not hardware .. at least this bug didn't show up until 25 August Best regards, Putinas - Original Message - From: "Soren Schmidt" <[EMAIL PROTECTED]> To: "Derek Ragona" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 20, 2003 10:07 Subject: Re: SATA drive lock-up > It seems Derek Ragona wrote: > > I have a single SATA drive on an Adaptec 1210SA card. > > > > The drive will give a write error warning a few times, then will repeatedly > > give: > > ad4: timeout sending command=ca > > > > The only recovery is the reset switch, reboot single-user fsck, and then > > come back up in multiuser. > > > > These errors occur with disk access, but not with a predictable nature (not > > on large files, or small files, etc.) > > And you are on an uptodate -current ? > > If so I'd suspect HW ... > > -Søren > > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fw: SATA drive lock-up
my verbose dmesg is in attached zip file, from today. my disks are connected with sata - pata converter based on marvel 88i8030 and one more question about ata3 and cable 40 wires, the cable actually is serial ata cable, not the 40 wires pata cable. and why it doesn't say then same thing about ata4 ? actually it's exactly same device like ata3? and to be strict ata1 is also 80 pins cable not 40 pins. ad4: setting UDMA100 on SiI 3112 chip GEOM: create disk ad4 dp=0xc6262670 ad4: ATA-5 disk at ata2-master ad4: 117800MB (241254720 sectors), 239340 C, 16 H, 63 S, 512 B ad4: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad4 ata3-master: pio=0x0c wdma=0x22 udma=0x45 cable=40pin - Original Message - From: "Soren Schmidt" <[EMAIL PROTECTED]> To: "Derek Ragona" <[EMAIL PROTECTED]> Cc: "Putinas" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 09:32 Subject: Re: SATA drive lock-up It seems Derek Ragona wrote: > Søren, > > My setup is as follows: > Maxtor 6Y120MO 120GB SATA drive > Adaptec Serial ATA RAID 1210SA > Intel® Desktop Board D845GEBV2 > 1GB RAM > 1.7 GHz Celeron CPU Ok, I'll try to get something semialr setup here and try to reproduce. > If there is some way to get more debugging information, please let me > know. If you want the ATA subsystem rebuilt differently for more > debugging, I'm happy to do that as well. If you want access to the box, I > will give you that too. Hmm debugging this kind of problems most often requires "hands on" access to the HW, in some cases the ability to hook up measuring/test equipment greatly enhances the problem hunting (or is the only way to catch it). -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" dmesg.zip Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sata stripe & dual boot
Hello, Just a quick question, I have setup SATA stripe from two disks, and I have 3 partitions 4Gb each and the rest for data storing. If I boot in freebsd from cdrom, I see two empty disks ad4 and ad6 and I guess if I create something I will mess up with my raid setup. Only one way what I could think off it would be to use atacontrol _before_ the installation to create exactly same stripe, and probably then I would see real filesystems on ar0. Or maybe there is any other way of easy ( or not ) doing this ? Regards, Putinas Piliponis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sata stripe & dual boot
Yes this what I tried , just a question shouldn't it be good idea to add ability use atacontrol from sysinstall ? ( lets say if I have two normal disks ad0 and ad2 and I want to use them in stripe configuration ? ) without downloading fixit cd image that not possible, because on fixit floppy there is no atacontrol... - Original Message - From: "Doug White" <[EMAIL PROTECTED]> To: "Putinas" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, October 14, 2003 18:18 PM Subject: Re: sata stripe & dual boot > On Tue, 14 Oct 2003, Putinas wrote: > > > Just a quick question, I have setup SATA stripe from two disks, and I have > > 3 partitions 4Gb each and the rest for data storing. If I boot in freebsd > > from cdrom, I see two empty disks ad4 and ad6 and I guess if I create > > something I will mess up with my raid setup. > > How did you set up the stripe? It sounds like your SATA RAID controller's > format is not currently supported. > > > Only one way what I could think off it would be to use atacontrol > > _before_ the installation to create exactly same stripe, and probably > > then I would see real filesystems on ar0. Or maybe there is any other > > way of easy ( or not ) doing this ? > > 1. Boot into sysinstall and drop into fixit mode with the CD. That gets > you atacontrol. Atacontrol away. > 2. Reboot and sysinstall should see your ar* devices. > > -- > Doug White| FreeBSD: The Power to Serve > [EMAIL PROTECTED] | www.FreeBSD.org > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl5.8andlibiconv 1.9.1_3
if you use portupgrade and you want to pass make arguments you should look at
/usr/local/etc/pkgtools.conf
my example :
MAKE_ARGS = {
'irc/bitchx-*' => 'WITH_SSL=1 WITH_IPV6=1',
'net/samba*' => 'WITHOUT_CUPS=1',
'databases/mysql323-server*' => 'SKIP_INSTALL_DB=1',
'ftp/proftpd*' => 'WITHOUT_PAM=1',
}
after you setup it for your needs - your life become pretty easy with portupgrading ...
- Original Message -
From: "Scott Wegener, Roadster Performance" <[EMAIL PROTECTED]>
To: "Joe Marcus Clarke" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Scott W" <[EMAIL PROTECTED]>
Sent: Wednesday, October 22, 2003 07:34 AM
Subject: Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl5.8andlibiconv
1.9.1_3
> Joe Marcus Clarke wrote:
>
> >On Wed, 2003-10-22 at 01:14, Scott W wrote:
> >
> >
> >>Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv
> >>were recompiled. I saved the log output and noticed several oddities I
> >>was wondering if anyone can explain?
> >>
> >>1..several settings come up as undefined during the Perl build, namely:
> >>$i_malloc
> >>$d_setegid
> >>$d_seteuid
> >>$i_iconv
> >>
> >>These don't look troubling by themselves dur to 'autoconf magic,' but
> >>the next one for libiconv is more bothersome:
> >>
> >> From libiconv 1.9.1_3 configure:
> >>checking if libtool supports shared libraries... yes
> >>
> >>*** Warning: the command libtool uses to detect shared libraries,
> >>*** /usr/bin/file, produces output that libtool cannot recognize.
> >>*** The result is that libtool may fail to recognize shared libraries
> >>*** as such. This will affect the creation of libtool libraries that
> >>*** depend on shared libraries, but programs linked with such libtool
> >>*** libraries will work regardless of this problem. Nevertheless, you
> >>*** may want to report the problem to your system manager and/or to
> >>*** [EMAIL PROTECTED]
> >>
> >>Any ideas?
> >>
> >>
> >
> >This is a byproduct of the new dynamic root layout in -CURRENT.
> >Basically, older versions of libtool try to do file on
> >/usr/lib/libc.so. Recent versions of -CURRENT put libc.so in /lib.
> >Therefore, this fails. I haven't noticed any real problems because of
> >this, but I have reported it to the libtool maintainer, [EMAIL PROTECTED]
> >
> >
> Great. That makes sense, as file will return symbolic link rather than
> an ELF executable, should be a minor adjustment by the maintainer. Also
> makes sense on libc in /lib - always disturbs me when I see 'important'
> system binaries mounted on the /usr filesystem!
>
> >>Also, is there a way to pass configure options to portupgrade, or should
> >>I run make clean && ./configure for each port in an 'upgrade chain' and
> >>then force portupgrade to not make clean prior to building/installing?
> >>
> >>
> >
> >Configure arguments? No. However, you can use the -m option to pass
> >make arguments (e.g. -DWITH_FOO). To pass configure arguments, you'd
> >have to edit the port Makefiles directly.
> >
> >Joe
> >
> >
>
> Actually, it _looks_ like there's somewhat of a standard in place within
> the port Makefiles defining CONFIGURE_ARGS, but I haven't searched
> through all of them- anyone know if this is a 'freeBSD Makefile
> standard' that can (generally) be counted on? If so, at least for
> specific ports builds, you should be able to define it on the command
> line to make (as Joe stated) or via passing the parameter to make for
> portupgradealthough that change doesn't get saved anywhere and will
> be clobbered by the next cvsup- any clean way to avoid this? I need to
> build apache for this system at some point, and somehow I'm not just
> seeing the defaults as likely to 'fit everyone' on that one?
>
> Thanks again,
>
> Scott
>
> >>Thanks,
> >>
> >>Scott
> >>
> >>___
> >>[EMAIL PROTECTED] mailing list
> >>http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >>To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> >>
> >>
>
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> ___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sony usb floppy drive problems
Hi all, I had today to format a lot of floppy disks and wanted to speed up things with connecting second floppy disk drive to my desktop, but with no sucsess ... Here is what I got when I try to fdformat /dev/da0 , detach, attach device : ( in case you need full dmesg is attached ) (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) GEOM: create disk da0 dp=0xc6b39850 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 -> 6 Mounting root from ufs:/dev/ar0s3a lock order reversal 1st 0xc6b6ea90 rtentry (rtentry) @ /usr/src/sys/net/route.c:182 2nd 0xc6a0617c radix node head (radix node head) @ /usr/src/sys/net/route.c:544 Stack backtrace: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: at uhub2 port 2 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry GEOM: destroy disk da0 dp=0xc6b39850 umass0: detached umass0: Sony USB Floppy Drive, rev 1.10/4.01, addr 2 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) GEOM: create disk da0 dp=0xc695a050 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C) umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 umass0: Unsupported UFI command 0x35 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi status == 0x0 Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Mon Oct 27 10:44:04 EET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a2d000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a2d26c. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2715.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff real memory = 1073725440 (1023 MB) avail memory = 1033555968 (985 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR ta
Re: Problem with motherboard se7505VB2(onboard SATA RAID Sil 3112A) andFreeBSD 5.1
You can use a freebsd-current snapshot ( ftp://current.freebsd.org ) or wait for 5.2-RELEASE. Maybe this will be supported in coming 4.9-RELEASE but this I don't know. - Original Message - From: "Anton Savoschik" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 27, 2003 13:20 PM Subject: Problem with motherboard se7505VB2(onboard SATA RAID Sil 3112A) andFreeBSD 5.1 > Hello! > I can't install FreeBSD 5.1(4.8) on Intel motherboard SE7505VB2 with > onboard Sil 3112A SATA Raid, also I can't find any information in > Hardware Notes for FreeBSD 5.1(4.8). Then SATA RAID disabled all works > fine(then I use ATA harddisk). In my opinion, it's a problem with Sil 3112A SATA > Raid. What can I do? Please help. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Software RAID
I do software raid with atacontrol, and I believe it will boot even if one hard disk fails. here are my disk configuration: ar0: 57241MB [7297/255/63] status: READY subdisks: 0 READY ad0: 57241MB [116301/16/63] at ata0-master UDMA100 1 READY ad2: 57241MB [116301/16/63] at ata1-master UDMA100 Mounting root from ufs:/dev/ar0s1a my here is my IDE controller: atapci1: port 0x8800-0x880f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 nothing special and of course no any hardware support for raid :) to create such raid just type atacontrol create RAID1 ad0 ad2 that's it :) - Original Message - From: "Steve Lee" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 31, 2003 02:22 AM Subject: Software RAID > Does FreeBSD support Software RAID ? > if so, what can it do ? > RAID 0, 1, 5 ?? > > also would it be able to mirror the root parition ? > > Thanks. > > any advice would be cool. > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cant compile GENERIC kernel from today source
Hi, I just cvsuped and when I do make buildkernel I get this: cc -c -O -pipe -march=pentium4 -Wall -Wredundant-decls -Wnested-externs -Wst rict -prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -ffo rmat -extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/con trib /dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath - I/us r/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -in clud e pt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-alig n -long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/ dev/xe/if_xe.c /usr/src/sys/dev/xe/if_xe.c:1832: warning: `xe_reg_dump' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. pilkishome# ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
