Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
I've been having similar problems on 5.4-RELEASE. I have a brand new board back from the factory (a RMA) and had a thread going on freebsd-questions about this. I currently have six Maxtor 7200RPM ATA133 hard drives that I've been trying on and off and with various configurations in my 5.4-RELEASE amd64 machine. The only thing I have done thus far to reproduce the READ and WRITE errors (there have been more WRITE than READ) is copy data between the drives. All the drives check out just fine through PowerMax (Maxtor's utility), and work in other FreeBSD 4.x machines in the same placement that causes errors on my 5.4 box. The cables are also brand new. However, note that if I turn the drives speed down to UDMA100, the errors seem to go away. Has anyone else tried this for their problems? I've read the entire thread and so far there has been no mention of any nForce chipsets doing this, but I've got a Giga-Byte K8NS Pro motherboard with a nForce3 chipset. I've been troubleshooting this for almost two weeks now on my end, and up until last night I didn't see any "FAILURE" messages. They were all just WARNINGS. I've only seen the FAILURE on one of the six hard drives, and that was last night when I was trying to fdisk it. Right when I hit "w" to write the fdisk information my screen flooded with WARNINGS and FAILURES, so indeed that particular drive might be going. This problem did not happen with any of the other drives. My whole reason for bringing back this thread is to see if my problems could be a result of the problem discussed here, and in fact is really not my hardware. As I said, the board is brand new, the cables are brand new, and two of the hard drives are even brand new. I've been pulling my hair out trying to narrow this problem down, and as of yesterday I was just going to run all my drives in UDMA100 mode to save me the hassle (since they seem to run fine in 100). Then, I found this thread and thought I'd ask if anyone here might think anything other than hardware problems. Granted, I'm not using FreeBSD 5-STABLE, but I could certainly give it a shot if you guys think it would help anything. I just chose RELEASE hoping for the least problems. My dmesg is below. Note that I only have three of the drives in there currently. Thanks -Mark --- DMESG: FreeBSD 5.4-RELEASE #0: Sun May 8 07:00:26 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (2009.79-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 Features=0x78bfbff AMD Features=0xe0500800 real memory = 1610547200 (1535 MB) avail memory = 1543139328 (1471 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf0-0xcf3,0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfc002000-0xfc002fff irq 22 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xfc003000-0xfc003fff irq 21 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered pci0: at device 2.2 (no driver attached) atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xe400-0xe40f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 22 at device 10.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pcib1: at device 11.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 14.0 on pci0 pci2: on pcib2 pci2: at device 9.0 (no driver attached) pci2: at device 9.1 (no driver attached) fwohci0: <1394 Open Host Controller Interface> mem 0xfb004000-0xfb007fff,0xfb00d000-0xfb00d7ff irq 18 at device 9.2 on pci2 fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:02:3c:00:91:01:6c:20 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:02:3c:01:6c:20 fwe0: Ethernet address: 02:02:3c:01:6c:20 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) skc0: port 0xa800-0xa8ff mem 0xfb00-0xfb003fff irq
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Mike Tancsa wrote: Yes, I have had Maxtor drives in the past where they would not work properly at certain bus speeds-- even back in the RELENG_4 days. Also, doesnt UDMA133 assume no slave ? I would just run them at 100. I dont think you would see much of a difference anyways. Perhaps Soeren could comment ? OK well I just tried adding some atacontrol commands to /etc/rc.local to force them all to 100 and it appeared to execute them upon boot. In various tests this evening I was getting errors even when trying to mount a drive while another one was on the same channel. However the atacontrol to rc.local seemed to do the trick for now, and I hope it continues to workunless there is a better way to do that for all my drives upon boot. I'm not too worried about any 133 performance increase at this point. I just want the stuff to work. Here is how I had planned my configuration to be: Primary IDE Master - Maxtor 200GB (FreeBSD) Secondary IDE Master - TDK VeloCD Burner Secondary IDE Slave - Sony DRU500A RAID 0 Master - Maxtor 200GB (Storage) RAID 0 Slave - Maxtor 160GB (Storage) RAID 1 Master - Maxtor 80GB (Storage) RAID 1 Slave - Maxtor 80GB (Storage) I do have a tall Antec case, and have both 200's and the 160 in 5 1/4 inch trays so the cables for those are long (36 inches IIRC). Would it be OK to have that setup, or would it be better to isolate them all on their own cables/channels and get a Promise card or something for the other two? I'm not going to be doing huge file copying a whole lot, but I'd like the most performance I can get with no errors. Thanks for the replies. -Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Mark Kirkwood wrote: Mark Kane wrote: I do have a tall Antec case, and have both 200's and the 160 in 5 1/4 inch trays so the cables for those are long (36 inches IIRC). Hmm - 36 inch cable, makes me wonder if that is what is causing the problem in UDMA133 mode. IIRC the ATA spec says 18 inches, but most cables seem to be ok at 24 inches. 36 inches may just be tipping things over the edge... Oh sorry I should have mentioned that my testing was done with standard length cables and there was still all the problems. I just got the 36 inch for the final placement of the drives, and there seems to be no change when I switch the cables. I'm glad that it looks like running it at 100 will solve this. Thanks for the replies. I was probably going to go through all the hassle of getting an Asus board to replace this because I was almost certain it was hardware, but I don't think it's worth it as long as this works :) -Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Mark Kane wrote: I'm glad that it looks like running it at 100 will solve this. Thanks for the replies. I was probably going to go through all the hassle of getting an Asus board to replace this because I was almost certain it was hardware, but I don't think it's worth it as long as this works :) I guess I spoke too soon. I was running things in 100 mode all day while doing some things to get it ready for my use. I copied 31GB of data from one drive (ad10) to another (ad9) with no WRITE errors from what I can see. Then I went to use cksfv to check the data against the source. This is what I get: ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=157308607 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=157308607 ad9: FAILURE - READ_DMA status=51 error=84 LBA=157308607 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=157308639 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=157308639 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=195346815 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=195714111 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=196459199 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=197213503 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=110345151 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=110345151 ad9: FAILURE - READ_DMA status=51 error=84 LBA=110345151 ad9: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=110345183 Here are the current drives in the system: ad0: 194481MB [395136/16/63] at ata0-master UDMA133 ad8: 156334MB [317632/16/63] at ata4-master UDMA133 ad9: 194481MB [395136/16/63] at ata4-slave UDMA133 ad10: 58643MB [119147/16/63] at ata5-master UDMA133 (They say 133 in the dmesg but atacontrol says 100 for all of them) Now Is this the problem that was described earlier on in the thread, or is this crappy controllers on the motherboard and I really do need to try to go through the hassle of exchanging it for that Asus board? -Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of Flash 9 on stable
On Tue, Oct 14, 2008, at 22:28:58 +0200, Tijl Coosemans wrote: > Patches have been committed to CURRENT and should have been MFC'ed > last weekend, but haven't for some reason. > > The port has a PR waiting for maintainer feedback: > http://www.freebsd.org/cgi/query-pr.cgi?pr=127839 > > The relevant thread on emulation@ is: > http://lists.freebsd.org/pipermail/freebsd-emulation/2008-September/005311.html > (continues in October archives) Hi. I'm using RELENG_7 as of yesterday which appears to have the linprocfs fixes from CURRENT, and I also updated linux-flashplayer9 with the patch from the above PR. When trying to use Flash 9 in linux-opera a few Flash items work (such as Adobe's test page which confirms it is using version 9 and sound does work on the rollovers there), but most things including YouTube videos or videos from other sites either do not play at all and lock up immediately or play for a few seconds and then lock up: opera: Plug-in 90514 is not responding. It will be closed. opera: Define environment variable OPERA_KEEP_BLOCKED_PLUGIN to keep blocked plug-ins. Trying with linux-firefox and linux-firefox-devel gives similar results except Firefox crashes entirely on most Flash sites. I was using linux_base-fc4 and 2.4.2 however I updated to linux_base-f8 and 2.6.16 since I saw others in the above emulation@ thread having success with f8. There doesn't seem to be any change with f8. Is this still the expected behavior? I'm not sure if these fixes were supposed to fix everything related to Flash 9 or if there are still things to be done, so I'm just giving it a try and posting the results. I am running amd64 by the way. Thanks very much in advance, -Mark FreeBSD 7.1-PRERELEASE #14: Thu Oct 16 00:12:09 CDT 2008 amd64 -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of Flash 9 on stable
On Thu, Oct 16, 2008, at 23:05:26 +0300, Kostik Belousov wrote: > On Thu, Oct 16, 2008 at 02:25:37PM -0500, Mark Kane wrote: > > Hi. > > > > I'm using RELENG_7 as of yesterday which appears to have the > > linprocfs fixes from CURRENT, and I also updated linux-flashplayer9 > > with the patch from the above PR. > > > > When trying to use Flash 9 in linux-opera a few Flash items work > > (such as Adobe's test page which confirms it is using version 9 and > > sound does work on the rollovers there), but most things including > > YouTube videos or videos from other sites either do not play at all > > and lock up immediately or play for a few seconds and then lock up: > > > > > > opera: Plug-in 90514 is not responding. It will be closed. > > opera: Define environment variable OPERA_KEEP_BLOCKED_PLUGIN to keep > > blocked plug-ins. > > > > > > Trying with linux-firefox and linux-firefox-devel gives similar > > results except Firefox crashes entirely on most Flash sites. > > > > I was using linux_base-fc4 and 2.4.2 however I updated to > > linux_base-f8 and 2.6.16 since I saw others in the above emulation@ > > thread having success with f8. There doesn't seem to be any change > > with f8. > > > > Is this still the expected behavior? I'm not sure if these fixes > > were supposed to fix everything related to Flash 9 or if there are > > still things to be done, so I'm just giving it a try and posting > > the results. I am running amd64 by the way. > > > > Thanks very much in advance, > > Hmm, finaly I noted this thread. There is one more patch in the > pipeline for 7 that is needed, as I was told. Testing of that patch > seems to be stalled, so I am interested in the feedback. Hi. Thanks for the patch. I just tested Flash 9 with it applied however there does not seem to be much change. YouTube videos now show up for one second in linux-opera but then the plugin hangs like before with the same "plugin not responding" message on the terminal. On another site with Flash it hung linux-opera up in the "pipdwc" state according to top. linux-firefox and linux-firefox-devel both still crash. I also tried nspluginwrapper this time with native Firefox 3 as J.R. said. It doesn't crash like the Linux Firefoxes but hangs the browser for a couple minutes (eventually does recover, but Flash doesn't play) and these appear on the terminal: - *** NSPlugin Wrapper *** ERROR: NPP_DestroyStream() wait for reply: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_URLNotify() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_Destroy() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NP_Shutdown() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_Write() wait for reply: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_DestroyStream() invoke: Message timeout - Thanks again, -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of Flash 9 on stable
On Thu, Oct 16, 2008, at 16:52:35 -0500, Sean C. Farley wrote: > I had something like that until I smacked my forehead after a few > hours and realized I had not added linprocfs to /etc/fstab. That may > be your problem at least with nspluginwrapper. > > Sean linprocfs was indeed not mounted, sorry about that. With it mounted native Firefox 3 with nspluginwrapper and both Linux Firefoxes do not crash/hang anymore and everything appears to be playing good and smooth so far :). linux-opera still does the "plugin not responding" on Flash and doesn't play. Not sure if this issue should be in a separate thread, but here's a little ktrace data from when the hang is happening in case it's helpful. This repeats for the entire kdump file after running ktrace for ~30 seconds during the hang: -- 9151 operaCALL compat.gethostid(0x6d,0xb35c,0,0,0xb3e4) 9151 operaRET compat.gethostid 0 9151 operaCALL mincore(0xb3e4,0) 9151 operaRET mincore 0 9151 operaCALL kill(0x286b,SIG 0) 9151 operaRET kill 0 9151 operaCALL compat.gethostid(0x6d,0xb35c,0,0,0xb3e4) 9151 operaRET compat.gethostid 0 9151 operaCALL mincore(0xb3e4,0) 9151 operaRET mincore 0 9151 operaCALL kill(0x286b,SIG 0) 9151 operaRET kill 0 -- Thanks! -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath based card
On Thu, Sep 28, 2006, at 18:30:52 +0200, Zoran Kolic wrote: > Hi all! > I would like to hear opinion of pc card > choice for laptop and atheros chip: > netgear wag511 > d-link dwl-ag650 > linksys wpc55ag > Good and bad. Prior to make idiot of me > and buy wrong. > > Zoran Hi. I've got the Netgear WG511T and it works pretty well. Sometimes it does "lock up" and become unusable after using Kismet or dstumbler (can't remember which one), but my old 550MHz laptop runs one of the 6.0 BETAs...so things may have improved in 6.1 or the upcoming 6.2 if it is a software issue. For general use (surfing/email/IRC/SSH/streaming audio) it works pretty well. Personally I prefer the Netgear or Linksys brands over D-Link. -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Machine hangs when loading snd_emu10k1
Hi everyone. I rebooted my machine today and when it came back up and I tried to load the snd_emu10k1 kernel module, the machine hung without returning to the prompt. I tried waiting 5-10+ minutes and it was totally irrecoverable. At that point, nothing had changed since the last reboot so it was weird that it would happen all of a sudden. Last week I did cvsup to RELENG_6 after 6.2 BETA 2 was out and built world/kernel with the intent to update and use it, but I never got around to finishing the process (I had not installed anything either, so it was just sitting all built). So tonight when the hanging of emu10k1 happened, I did the installkernel/installworld process as normal thinking something might have been fixed between my previous cvsup (September 21 I believe) and my current one from Oct 5. Unfortunately there was no change in behavior -- it hung again and I waited at least 10 minutes before hard rebooting. I'm currently running: FreeBSD amd64.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #15: Thu Oct 5 17:52:05 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMD643000 amd64 With a Sound Blaster Augidy 2 Platinum: [EMAIL PROTECTED]:8:0: class=0x040100 card=0x10021102 chip=0x00041102 rev=0x04 hdr=0x00 vendor = 'Creative Labs' device = 'SoundBlaster Audigy Audigy Audio Processor' class= multimedia subclass = audio [EMAIL PROTECTED]:8:1: class=0x098000 card=0x00601102 chip=0x70031102 rev=0x04 hdr=0x00 vendor = 'Creative Labs' device = 'EMU10K2 Audigy Gameport' class= input device [EMAIL PROTECTED]:8:2: class=0x0c0010 card=0x00101102 chip=0x40011102 rev=0x04 hdr=0x00 vendor = 'Creative Labs' device = 'EMU10K2 Audigy IEEE1394 Firewire Controller' class= serial bus subclass = FireWire Later on tonight I can try to cvsup to RELENG_6 and rebuild again to see if it has been fixed already, but I need my CPU power for some encoding at the moment. Also, I'd rather not have to do a third hard reboot with an hour long fsck for seven hard drives, so I wanted to post here first in case it's known already or if anyone has any suggestions before doing it again. Thanks in advance. -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) dmesg.boot Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Machine hangs when loading snd_emu10k1
On Fri, Oct 13, 2006, at 19:32:39 -0500, Mark Kane wrote: > Hi everyone. > > I rebooted my machine today and when it came back up and I tried to > load the snd_emu10k1 kernel module, the machine hung without returning > to the prompt. I tried waiting 5-10+ minutes and it was totally > irrecoverable. At that point, nothing had changed since the last > reboot so it was weird that it would happen all of a sudden. > > Last week I did cvsup to RELENG_6 after 6.2 BETA 2 was out and built > world/kernel with the intent to update and use it, but I never got > around to finishing the process (I had not installed anything either, > so it was just sitting all built). So tonight when the hanging of > emu10k1 happened, I did the installkernel/installworld process as > normal thinking something might have been fixed between my previous > cvsup (September 21 I believe) and my current one from Oct 5. > Unfortunately there was no change in behavior -- it hung again and I > waited at least 10 minutes before hard rebooting. > > I'm currently running: > > FreeBSD amd64.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #15: Thu > Oct 5 17:52:05 CDT 2006 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMD643000 amd64 > > With a Sound Blaster Augidy 2 Platinum: > > [EMAIL PROTECTED]:8:0: class=0x040100 card=0x10021102 chip=0x00041102 > rev=0x04 hdr=0x00 vendor = 'Creative Labs' > device = 'SoundBlaster Audigy Audigy Audio Processor' > class= multimedia > subclass = audio > [EMAIL PROTECTED]:8:1: class=0x098000 card=0x00601102 chip=0x70031102 > rev=0x04 hdr=0x00 vendor = 'Creative Labs' > device = 'EMU10K2 Audigy Gameport' > class= input device > [EMAIL PROTECTED]:8:2: class=0x0c0010 card=0x00101102 chip=0x40011102 > rev=0x04 hdr=0x00 vendor = 'Creative Labs' > device = 'EMU10K2 Audigy IEEE1394 Firewire Controller' > class= serial bus > subclass = FireWire > > Later on tonight I can try to cvsup to RELENG_6 and rebuild again to > see if it has been fixed already, but I need my CPU power for some > encoding at the moment. Also, I'd rather not have to do a third hard > reboot with an hour long fsck for seven hard drives, so I wanted to > post here first in case it's known already or if anyone has any > suggestions before doing it again. > > Thanks in advance. > > -Mark I cvsupped to RELENG_6 last night at about 3 AM Eastern and rebuilt world/kernel. I tried again this morning loading the snd_emu10k1 module manually after booting and the machine hung as before. I heard the usual brief crack/pop out of the sound card as if it had loaded, but then it does not return to prompt or respond to SSH/any keyboard input anymore. I let it sit a bit longer this time, over 15 minutes...would not recover. After the hard reboot and fsck, I compiled "device sound" and "device snd_emu10k1" into my kernel which is working fine now. So it's only a problem when loading the module. I can open a PR if needed, but I don't really have any data or debugging info (no errors on the screen, or in /var/log/messages). I only know that after the system was up since the last rebuild and I rebooted it yesterday, the system hangs indefinitely upon loading the snd_emu10k1 module even though I had not changed any system configuration in that time. I did have a new world/kernel built before yesterday's reboot, but not installed. Thanks -Mark FreeBSD amd64.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #17: Sat Oct 14 13:58:30 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMD643000 amd64 -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Machine hangs when loading snd_emu10k1
On Sun, Oct 15, 2006, at 12:38:58 +0200, Joel Dahl wrote: > So, loading snd_emu10k1 worked before the last rebuild? Could you > perhaps do a binary search and try to narrow it down to a specific > commit? On September 21, I rebuilt world/kernel and did the normal update procedure. The module loaded fine that time after rebooting with the new build. Then on October 5 after the 6.2-BETA2 announcement, I cvsupped/rebuilt, but never installed kernel or world. So when I rebooted a couple days ago, I was actually booting into the version from September 21, and that reboot from Friday is when the problem started. I'm not sure why it didn't happen after the initial boot from updating back on September 21 though. So in other words, I was running RELENG_6 from September 21 and after rebooting on October 13 without changing or updating anything, the problem of hanging indefinitely when loading snd_emu10k1 started. I know it sounds weird that it would start happening after the second boot since updating and not on the first boot with the new world/kernel, but I'm very sure I didn't update anything in the time between the reboots (Sept 21 - Oct 13). Could you describe more about what you want me to do? I'd be glad to help however I can to track the problem down, but I don't really know what to look for as far as commits go, and I'm not sure the date of my cvsup/rebuild before Sept 21 so I wouldn't know how far back to look either. Thanks -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Daily Panics on 6.2-STABLE (page fault/Fatal trap 12)
Hi everyone.
I'm getting kernel panics daily or even multiple times a day on a new
machine. When it's running everything works well, but over the last day
or two I've been getting multiple panics per day at seemingly random
times.
When the first panic happened, all I did was open up a new tab in my
graphical terminal. The second one I had VNC open to another FBSD box
and was maximizing the VNC window here to continue working on it. The
third one I was running a simple command via SSH on another machine (in
a graphical terminal). The fourth one was just pulling a website up in
my browser. The latest one was also working on another machine via SSH
in a graphical terminal. I had just switched terminal tabs and then it
panicked.
The CPU is nowhere near loaded at the times it panics, and since it
has happened several different times while doing different things each
time, I'm not exactly sure of one single event that triggers it. The
programs I have open when it panics are XChat, Opera or Firefox, XMMS,
a Terminal with some tabs, sometimes mplayer playing audio, and Claws
Mail. I've tested my RAM (brand new) with three passes of memtest86+
and there were zero errors. I have included some kgdb output, a dmesg,
and my kernel configuration.
This is the first real panicking problem I've ever experienced with
FreeBSD, so please let me know if there is any additional information I
can provide.
Thanks very much in advance.
-Mark
KGDB OUTPUT
[GDB will not be able to debug user-mode
threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x30
fault code = supervisor write data, page not present
instruction pointer = 0x8:0x803b7db4
stack pointer = 0x10:0xb4eee6d0
frame pointer = 0x10:0x0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1638 (xmms)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 2h6m25s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 2047MB (523984 pages) 2031 2015 1999 1983 1967 1951 1935
1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711
1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487
1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263
1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039
1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767
751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479
463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191
175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:172
172 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) list *0x803b7db4
0x803b7db4 is in devfs_open
(/usr/src/sys/fs/devfs/devfs_vnops.c:798).
793 * the file *.
794 */
795 fp = ap->a_td->td_proc->p_fd->fd_ofiles[ap->a_fdidx];
796 KASSERT(fp->f_ops == &badfileops,
797 ("Could not vnode bypass device on fdops %p",
fp->f_ops));
798 fp->f_ops = &devfs_ops_f;
799 fp->f_data = dev;
800 return (error);
801 }
802
(kgdb) backtrace
#0 doadump () at pcpu.h:172
#1 0x0004 in ?? ()
#2 0x804194d7 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#3 0x80419b71 in panic (fmt=0xff004bff4260 "X�eb")
at /usr/src/sys/kern/kern_shutdown.c:565
#4 0x8063588f in trap_fatal (frame=0xff004bff4260,
eva=18446742975848768344) at /usr/src/sys/amd64/amd64/trap.c:668
#5 0x80635c0c in trap_pfault (frame=0xb4eee620,
usermode=0) at /usr/src/sys/amd64/amd64/trap.c:580
#6 0x80635ec3 in trap (frame=
{tf_rdi = -1097447831552, tf_rsi = -1098236607904, tf_rdx = 7,
tf_rcx = 4, tf_r8 = 1, tf_r9 = -1098342836736, tf_rax = 0, tf_rbx =
-1098236607904, tf_rbp = 0, tf_r10 = -1098486072152, tf_r11 = 7, tf_r12
= 0, tf_r13 = -1098486072320, tf_r14 = -1097860783272, tf_r15 =
-1097447831552, tf_trapno = 12, tf_addr = 48, tf_flags =
-1098236607904, tf_err = 2, tf_rip = -2143584844, tf_cs = 8, tf_rflags
= 66118, tf_rsp = -1259411744, tf_ss = 16})
at /usr/src/sys/amd64/amd64/trap.c:353
#7 0x806210ab in calltrap ()
at /usr/src/sys/amd64/am
Re: Daily Panics on 6.2-STABLE (page fault/Fatal trap 12)
On Tue, Feb 20, 2007, at 22:14:50 -0600, Mark Kane wrote: > Hi everyone. > > I'm getting kernel panics daily or even multiple times a day on a new > machine. When it's running everything works well, but over the last > day or two I've been getting multiple panics per day at seemingly > random times. > > When the first panic happened, all I did was open up a new tab in my > graphical terminal. The second one I had VNC open to another FBSD box > and was maximizing the VNC window here to continue working on it. The > third one I was running a simple command via SSH on another machine > (in a graphical terminal). The fourth one was just pulling a website > up in my browser. The latest one was also working on another machine > via SSH in a graphical terminal. I had just switched terminal tabs > and then it panicked. > > The CPU is nowhere near loaded at the times it panics, and since it > has happened several different times while doing different things each > time, I'm not exactly sure of one single event that triggers it. The > programs I have open when it panics are XChat, Opera or Firefox, XMMS, > a Terminal with some tabs, sometimes mplayer playing audio, and Claws > Mail. I've tested my RAM (brand new) with three passes of memtest86+ > and there were zero errors. I have included some kgdb output, a dmesg, > and my kernel configuration. > > This is the first real panicking problem I've ever experienced with > FreeBSD, so please let me know if there is any additional information > I can provide. > > Thanks very much in advance. > > -Mark > > [Debug info snipped -- see:] > http://lists.freebsd.org/pipermail/freebsd-stable/2007-February/033199.html Hi all. Unfortunately these panics are still happening. One thing I have noticed from all kgdb outputs is the "current process" listed _every time_ is XMMS. I know that for most of those times, XMMS wasn't even playing any files but was rather just sitting open. A bad combination seems to be XMMS and vncviewer open at the same time which often results in a panic, although not always. Sometimes it happens with just XMMS running and maybe a browser, IRC, and email. Recently I thought it was improving. I cvsupped last week, rebuilt world and kernel and it ran for about a week with no problems. Now it's panicked two times since last night. Note that it's the same exact kgdb output every time. Below is another kgdb output with a "bt full" this time. I'm trying to rule out any software issues before I start looking at hardware (even though it's all brand new with the exception of the sound card). If it is thought to be hardware, any pointers on what to check first would be much appreciated also. Thanks again, -Mark FreeBSD 6.2-STABLE #5: Tue Mar 13 17:09:00 CDT 2007 === KGDB OUTPUT === [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x30 fault code = supervisor write data, page not present instruction pointer = 0x8:0x803bd154 stack pointer = 0x10:0xb529a6d0 frame pointer = 0x10:0x0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4692 (xmms) trap number = 12 panic: page fault cpuid = 1 Uptime: 11h33m35s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (523984 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 pcpu.h: No such file or directory. in pcpu.h (kgdb) list *0x803bd154 0x803bd154 is in devfs_op
Re: Release Schedule for 2006
Bill Nicholls wrote: > Let me add my voice to this discussion. I have been a happy user of > FreeBSD from 4.0 thru 4.11, but have stumbled repeatedly on 5.x and now > 6.0. > > For some reason, I can get these (5 & 6) installed, but not stable or > running KDE, yet 4.11 runs solid for months. In addition, not being able > to run KDE from Generic has been an additional headache. > > This has become such a problem that I finally loaded Suse Linux 10 on my > alternate disk so I can move ahead. I use dual 9G disks and alternate > installs, stairstepping from one release to the next, with the ability > to boot back to an older release. This has worked well until now. > > This is particularly bad timing because FreeBSD is my *preferred* OS for > significant parts of my work, and it was planned to host an important > DB project on another machine bought for that purpose. > > I was hoping that 6.0 would enable me to move ahead on my FreeBSD > workstation, and then on my DB project. Instead I am stalled and forced > to go to a less preferred solution. > > I don't know what, if anything, I am doing wrong. I gave away an > expensive SOYO MB because FreeBSD would not install, later found out > that the advanced SOYO ACPI was the problem, apparently solved later. > > Color me frustrated. For me the issue is very simple - I need to install > release X.Y, install KDE, configure X and get to work. Becoming an > internals expert or even small time developer is not what I need to do > even though I have done that kind of work in the past. Now I concentrate > on getting applications into production, with OS maintenence limited to > chasing glitches. > > Color me very frustrated. I've been used to great stability on FreeBSD, > less frequent changes than Linux, and fewer problems. The system just > *worked*. No longer. > > I don't blame anybody on the team for this issue because from my POV, > the attention on getting better SMP and generally upgrading the kernel > quality was and is a good objective. However, along the way, a few less > obvious characteristics have lost out. > > When it gets to the point that I am forced to use something else despite > my efforts, then attention needs to be spent making FreeBSD work 'Out of > the Box' again. Simple is good - you can always get complicated if that > is your preference, but for a lot of us, FreeBSD is a tool, not a career. > > Again, this is not a flame but a plea to make the system simply work. I do not know your situation or what you have tried in order to resolve your problems, but I do know that I have several FreeBSD machines as desktops and they all work great. My main desktop is an Athlon64 3000+ running FreeBSD 5.4-RELEASE [amd64]. I am not sure why you have not been able to get X and KDE running. I don't use KDE anymore, but it was extremely simple to get X and my window manager (Xfce) up and running. I installed the Xorg and Xfce4 metaports and it was as simple as that. I did the "Xorg -configure" steps outlined in the handbook, copied the configuration file to the proper place, and I was up and running. I cannot code anything but I had the system up and running in only the time it took to compile things and modify a few config files. I've also setup FreeBSD as a desktop on my Athlon XP 2000+ (FreeBSD 5.4-RELEASE) which did run KDE before, my Athlon XP 1800+ (FreeBSD 5.4-RELEASE), and my 533MHz Compaq Laptop (FreeBSD 6.0-RC1). All of those were able to get X and my window manager of choice (Xfce on two, and fvwm on laptop) installed very quickly and easily through ports (and packages on laptop). I have not used 6.0-RELEASE at all yet, and only use my laptop with RC1 of 6.0 a little. So far there have been no issues with any of my machines except one random reboot on my amd64 that I have yet to track down. However, my point is that most people do not have problems that prevent them from getting a working machine or have the need to modify code as you said you do. That's the beauty of the ports system. You can install things easily that were "ported" to work with FreeBSD. Whether applications require special configure arguments, code changes, or other settings, the ports system is there to automate that whole process and build things so they do work right. I'm not blaming it on you or saying it's your error, but without knowing the actual issues I must say it sounds very weird and isolated. Just one thing to keep in mind though: If you have issues, why not ask the very helpful FreeBSD community? Mailing lists like freebsd-questions have great people who are willing to help people out with questions and issues like yours. I've gotten help there when I've had some weird problems and I also try to help whenever I can. In other words, if it was me, I would try my best to solve it first before switching operating systems...especially since I love FreeBSD so much. Again, I don't know your particular issues/problems, but I am certain there would be some help ava
Re: Link for the FreeBSD 6.1 Schedule?
Tobias Kilb wrote: Hi guys, has anyone the link for the FreeBSD 6.1 Schedule Page (Open Tasks, Bugs, etc...). I can't find the link thanks, Tobias Here it is: http://www.freebsd.org/releases/6.1R/ -Mark -- GnuPG Public Key: http://www.mkproductions.org/mk_pubkey.asc Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Failure Introduced between 6.0 and 6.1-RC1
Jared wrote: Hi -stable! I'd like to bring something to the attention of -stable that was posted to -amd64 but has not yet being resolved: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/95554 I'm unable to test to see if this occurs on i386 aswell so am unsure if this is the right list to post to. But it appears to me that it would be something that should be addressed prior to 6.1-RELEASE. Hi all. This does indeed occur on i386 also. I had a drive die in a machine this past week and replaced it with two brand new Seagate 80GB SATA 300 drives to do mirroring, but 6.1-RELEASE only detects one of the drives (and only the one on the primary SATA channel even if I switch them around). Upon finding this PR, I tried 6.0-RELEASE and it detected both drives on the install, so I went ahead and installed 6.0 to use until there is a fix since this is a production workstation. Unfortunately, I forgot that I was running 6.1-PRERELEASE on the previous install because none of the controllers on my board (MSI K8NGM2 - nForce4) are detected in 6.0, and instead run as "GENERIC" at UDMA33. I don't have the latest BIOS since it requires Windows to update, but the summary for all updates show mainly CPU things...nothing related to ATA/SATA/RAID. I'm trying to decide if I should use 6.0 with the "GENERIC" controller and reduced speeds since it needs to be operational, or try the nve patches to fix the onboard LAN so I can free up a PCI slot and then put in a known working SATA controller that would be recognized and at full speeds. Not meant as pressure in any to the developers, but I'm wondering if you guys think it will be a while before this is fixed so I can make an informed decision on hardware purchases or not and get this machine back up. Thanks in advance! -Mark I am experiencing the same problem as described in the original PR, but with Western Digital hard drives and the latest BIOS version (1001) which is known to fix the ACPI DSDT bugs that have plagued these boards. I have not liased with the mailling lists before if you need any more information please ask and I'll supply what I can as best I can. But the original PR is well written. I will also see if RC-2 resolves this when cvsup has RC2 and I can build an RC2 world/kernel. Cheers and Thanks for a great operating system Jared ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- GnuPG Public Key: http://www.mkproductions.org/mk_pubkey.asc Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: quota and snapshots in 6.1-RELEASE
Mike Jakubik wrote: Rong-en Fan wrote: On 5/23/06, Dmitriy Kirhlarov <[EMAIL PROTECTED]> wrote: Hi, list. Some time ago quota and, AFAIR, snapshots in 6.1-RELEASE has deadlock problems. What the current situation with this? I'm ready to test patches, if needed. WBR IIRC, there are some quota and snapshots changes merged in 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want to try that. Thats correct. I have been meaning to test these, but not had the time to do so yet. If you can, update to -STABLE and give it a test. I had a motherboard die in a server on Sunday. It is running FreeBSD 5.4-RELEASE and the only hardware they had to replace it with was an Athlon64 CPU and a motherboard with an ATI chipset. With that board and 5.4, it will only boot in Safe Mode, but then the hard drives are running at very slow speeds. It completely locked up earlier today and they had to do a hard reboot (with no errors on the screen or in /var/log/messages). My plan was to have them fully upgrade the server tonight to a new box (with the same Athlon64 and mobo with ATI chipset since that's all they have), and do a fresh install of 6.1-RELEASE because a very similar board with the same chipset was reported to work in 6.0. Every machine I have or work on runs FreeBSD, but this is the only one that needs quotas because it runs cPanel for customers. I am not sure all the details about the problems with quotas, so will running 6.1-RELEASE with quotas cause problems for sure? If so, any suggestions on what to do given my situation? Would 6.0 be any better? I'd like to have the latest version because doing updates properly remotely is difficult, but if it is not going to work then I may have to use 6.0 if that will work or figure something else out hardware wise. Thanks -Mark -- GnuPG Public Key: http://www.mkproductions.org/mk_pubkey.asc Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
