Re: cvs commit: src/sys/dev/sound/pci ich.c
In message: [EMAIL PROTECTED] Mark Santcroos [EMAIL PROTECTED] writes: : On Mon, Oct 13, 2003 at 09:47:45AM -0700, Nate Lawson wrote: : It looks like you are resetting the BARs on resume. If that's all that's : needed, I believe Warner was working on code to do this in the general : case. : : Exactly, the thread[*] went on about pci power transitions in general. Warner : also responded to it. : : Without complaining too much, this subject needs to be opened up. : Every time someone does something in this area we are told to hold off : because something is coming. : (Last month I've been inactive, so if something has popped up, please : discard this message) Things have happened in p4. We're trying to work out some details. But you are right a snapshot might be in order. Warner ___ [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: boot hang: ata1: resetting devices .. done (5.1-CURRENT, IBMT30)
Dnia Mon, Oct 13, 2003 at 02:51:43PM -0700, Lee Damon napisal: Anyone tried going forward to 1.8? I just tried 1.8, it did not fix the problem. Symtoms are still the same, I use 1.8 and is working without problem. -- Jacek Serwatynski [EMAIL PROTECTED] | PGP_key: www.trynet.eu.org/pub.key -- PGP_finger: 5E30 D9C4 976C E9B1 9920 B155 962A 737B 1EFA 5987 -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
LOR (tcp_input.c:654 tcp_usrreq.c:621).
Hello. I'm not sure if this was reported already. lock order reversal 1st 0xc51046ec inp (inp) @ /usr/src/sys/netinet/tcp_input.c:654 2nd 0xc0642cac tcp (tcp) @ /usr/src/sys/netinet/tcp_usrreq.c:621 Stack backtrace: backtrace(c05d0e2c,c0642cac,c05d63bc,c05d63bc,c05d76ab) at backtrace+0x17 witness_lock(c0642cac,8,c05d76ab,26d,74) at witness_lock+0x671 _mtx_lock_flags(c0642cac,0,c05d76ab,26d,74) at _mtx_lock_flags+0xba tcp_usr_rcvd(c5574400,80,c05d1437,db70ca84,3b9aca00) at tcp_usr_rcvd+0x30 soreceive(c5574400,db70cac0,db70cacc,db70cac4,0) at soreceive+0x7ff nfsrv_rcv(c5574400,c7a79480,4,c5105de8,18) at nfsrv_rcv+0x87 sowakeup(c5574400,c557444c,c05d6dc0,446,108) at sowakeup+0x89 tcp_input(c1bfc800,14,c06428d4,c05f066c,db70cc48) at tcp_input+0xed1 ip_input(c1bfc800,0,c05d5bfc,89,0) at ip_input+0x81f netisr_processqueue(c0641350,0,c05d5bfc,e5,c1bc8100) at netisr_processqueue+0x8e swi_net(0,0,c05cb58d,215,c1bda974) at swi_net+0x8c ithread_loop(c1bd8d80,db70cd48,c05cb3ff,314,c1bd8d80) at ithread_loop+0x172 fork_exit(c047d9e0,c1bd8d80,db70cd48) at fork_exit+0xc0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xdb70cd7c, ebp = 0 --- -- Pawel Jakub Dawidek [EMAIL PROTECTED] UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net pgp0.pgp Description: PGP signature
Re: panic: softdep_deallocate_dependencies: dangling deps
Jeff Roberson wrote: When are your sources from? My last cvs up is two days ago. Regards, Oliver Fischer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
GEOM Gate.
Hello hackers... Ok, GEOM Gate is ready for testing. For those who don't know what it is, they can read README: http://garage.freebsd.pl/geom_gate.README and presentation from WIP/BSDCon03 session: http://garage.freebsd.pl/GEOM_Gate.pdf After compliation (cd geom_gate; make; make install) you should run regression tests: # regression/runtests.sh If everything will went ok you can play with GEOM Gate and report any bugs. I've spend some time to made GEOM Gate force-remove-safe so using '-f' option with ggc(8) should be always safe. Ah! Four manual pages are added, so feel free to read them first (gg(4), geom_gate(4), ggc(8), ggd(8)) http://garage.freebsd.pl/geom_gate.tbz Enjoy! -- Pawel Jakub Dawidek [EMAIL PROTECTED] UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net pgp0.pgp Description: PGP signature
ata problem with 13/10/2003 current
After having update my -CURRENT box to yesterday afternoon (Central Europe Time) sources, I can't get it to boot. It stops probing ata1: GEOM: create disk ad0 dp=0xc4536a70 ad0: 57259MB MAXTOR 6L060J3 [116336/16/63] at ata0-master UDMA133 GEOM: create disk ad1 dp=0xc4915a70 ad1: 38172MB QUANTUM FIREBALLP AS40.0 [77557/16/63] at ata0-slave \ UDMA100 ata1: resetting devices .. acd0: FAILURE - SETFEATURES status=51 READY,DSC,ERROR error=4ABORTED done acd0: FAILURE - SETFEATURES device lockup-removed And it stops here. On ata1 there are a Liteon CD-ReWriter 48x12x48x (acd0) and a LG DVD-ROM Drive DRD-8160B (acd1) I never had problem with ATAng before, so it is probably related to a recent commit. Best Regards -- Rionda aka Matteo Riondato GUFI Staff Member (http://www.gufi.org) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with 13/10/2003 current
It seems Matteo Riondato wrote:
After having update my -CURRENT box to yesterday afternoon (Central
Europe Time) sources, I can't get it to boot. It stops probing ata1:
GEOM: create disk ad0 dp=0xc4536a70
ad0: 57259MB MAXTOR 6L060J3 [116336/16/63] at ata0-master UDMA133
GEOM: create disk ad1 dp=0xc4915a70
ad1: 38172MB QUANTUM FIREBALLP AS40.0 [77557/16/63] at ata0-slave \
UDMA100
ata1: resetting devices ..
acd0: FAILURE - SETFEATURES status=51 READY,DSC,ERROR error=4ABORTED
done
acd0: FAILURE - SETFEATURES device lockup-removed
And it stops here.
On ata1 there are a Liteon CD-ReWriter 48x12x48x (acd0)
and a LG DVD-ROM Drive DRD-8160B (acd1)
I never had problem with ATAng before, so it is probably related to a
recent commit.
Could you try this patch please:
Index: ata-queue.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v
retrieving revision 1.8
diff -u -r1.8 ata-queue.c
--- ata-queue.c 12 Oct 2003 12:38:03 - 1.8
+++ ata-queue.c 13 Oct 2003 13:05:01 -
@@ -315,20 +315,21 @@
static void
ata_timeout(struct ata_request *request)
{
+struct ata_channel *ch = request-device-channel;
+int quiet = request-flags ATA_R_QUIET;
+
/* clear timeout etc */
request-timeout_handle.callout = NULL;
-#if 0
-/* call interrupt to try finish up the command */
-request-device-channel-hw.interrupt(request-device-channel);
-if (request-device-channel-running == NULL) {
- if (!(request-flags ATA_R_QUIET))
+/* call hw.interrupt to try finish up the command */
+ch-hw.interrupt(request-device-channel);
+if (ch-running != request) {
+ if (!quiet)
ata_prtdev(request-device,
WARNING - %s recovered from missing interrupt\n,
ata_cmd2str(request));
return;
}
-#endif
/* if this was a DMA request stop the engine to be on the safe side */
if (request-flags ATA_R_DMA) {
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [ALTQ/FreeBSD] Re: if_tun not altq enabled in pfaltq patch?
Hello Michael, Tuesday, October 14, 2003, 2:03:51 PM, you wrote: I see it's patched and contains altq-code, but trying to apply the classic ack-prioritizing ruleset gives me pfctl: tun0: driver does not support altq. Is this expected? MN Okay, it seems pf didn't like the fact that my if_tun was a module. In-kernel MN seems to work. Yes, that is a general problem: We'd have to extensively patch all if_* module Makefiles to propagate the new option. There is: ++ |Issue| Status | Responsible |Description | |-+---+-+| | | | | Kernel modules are | | | | | currently built| | | | | independently from | | | | | a kernel | | | | | configuration, and | | | | | independently from | | | | | one another, | | | | | resulting in | | | | | substantially | | | | | redundant | | | | | compilation of | | | | | objects, as well | | | | | as the inability | | | | | to easily manage | | | | | compile-time | | | | | options for kernel | | | | | objects (such as | | | | | MAC, PAE, etc) | | Revised kld build | --| -- | that may require | | infrastructure | | | conditional| | | | | compilation in the | | | | | kernel modules. In | | | | | order to improve | | | | | build performance | | | | | and better support | | | | | options of this| | | | | sort, the KLD | | | | | build | | | | | infrastructure | | | | | needs to be| | | | | revamped. Peter| | | | | Wemm has done some | | | | | initial| | | | | prototyping, and | | | | | should be | | | | | contacted before | | | | | starting on this | | | | | work. | |-+---+-+| this topic from the 5.2-Release TODO applies here! If you are planning to investigate in that area, I could offer some starting points. I am unsure how to do this right so I didn't start anything myself, but I have some ideas ... If anybody is going to put his head into it, feel free to contact me for support. -- Best regards, Maxmailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with 13/10/2003 current
Il Mar, 2003-10-14 alle 15:09, Soren Schmidt ha scritto: It seems Matteo Riondato wrote: I never had problem with ATAng before, so it is probably related to a recent commit. Could you try this patch please:I Index: ata-queue.c === I cannot patch my system: kaiser# cd /usr/src/sys/dev/ata/ kaiser# patch /home/rionda/ata-patch.patch Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: ata-queue.c |=== |RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v |retrieving revision 1.8 |diff -u -r1.8 ata-queue.c |--- ata-queue.c 12 Oct 2003 12:38:03 - 1.8 |+++ ata-queue.c 13 Oct 2003 13:05:01 - -- Patching file ata-queue.c using Plan A... Hunk #1 failed at 315. 1 out of 1 hunks failed--saving rejects to ata-queue.c.rej done kaiser# -Søren Regards -- Rionda aka Matteo Riondato G.U.F.I Staff Member (http://www.gufi.org) BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda) GPG key at: http://www.riondabsd.net/riondagpg.asc Sent from: kaiser.sig11.org running FreeBSD-5.1-CURRENT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with 13/10/2003 current
From: Soren Schmidt [EMAIL PROTECTED] Could you try this patch please: Index: ata-queue.c === RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v retrieving revision 1.8 diff -u -r1.8 ata-queue.c --- ata-queue.c 12 Oct 2003 12:38:03 - 1.8 +++ ata-queue.c 13 Oct 2003 13:05:01 - ---SNIP--- Happy to say that this patch fixes the resetting devices... problem I'd encountered. Thanks. -- Rob | What part of no was it you didn't understand? _ Sign-up for a FREE BT Broadband connection today! http://www.msn.co.uk/specials/btbroadband ___ [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
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]
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]
sata + vinum + Asus p4p800 = :(
Hi, I had a -CURRENT setting with an Abit BE7-S and two SATA disks with vinum configuration. It worked very well until a power failure, and the mainboard died. Yesterday I got a replacement mainboard, the only type met the requirements (eg. two SATA ports) in the store: an Asus P4P800. My only problem is with the disks. I can use all USB ports (8; what a server could do with eight USB ports?), the 3C940 Gigabit Ethernet port (I disabled the sound subsystem), and everything works until the first fsck, when the kernel paniced. Here is the dmesg: GEOM: create disk ad0 dp=0xc6b4bb70 ad0: 4028MB Maxtor 90422D2 [8184/16/63] at ata0-master UDMA33 acd0: CDROM GCR-8523B at ata0-slave PIO4 GEOM: create disk ad4 dp=0xc6b4b070 ad4: 117246MB Maxtor 6Y120M0 [238216/16/63] at ata2-master UDMA133 GEOM: create disk ad6 dp=0xc6b4b170 ad6: 117246MB Maxtor 6Y120M0 [238216/16/63] at ata3-master UDMA133 Mounting root from ufs:/dev/vinum/root panic: ata_dmasetup: transfer active on this device! I did further investigation: I booted from ata0-master, and mounted /dev/vinum/root as /mnt. A simple fsck -f -B /mnt killed the system. I did the same with /dev/ad4s1a (this is the boot hack partition from the handbook), then I switched off softupdates. No win. I tried to boot with safe mode either, but it hung with page fault. What can I do? Besides, why my SATA interfaces are recognized as UDMA133? -- jul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's up with the IP stack?
Kevin Oberman wrote: When I see this I can reach some LAN hosts, but not others. I can always seem to reach the access point. I can usually, but not always, reach most other systems on the LAN, but not the gateway router, a Sonic Wall firewall. I have logged onto another system and then connected to the firewall, so it looks like the physical path is OK. The problem is intermittent and I have only scattered data. I've been seeing it sice about the beginning of October. I was blaming it on hardware, but now that I see these reports, maybe it's not. (I just replaced my Apple Airport AP with a D-Link, so there is something to suspect.) In may case things just start working again. The pause can vary from a few seconds to about 10 minutes. netstat -rnf inet and arp -a output both look to be fine. What about your IP address and default route? I've seen wireless cards, especially IBM ones, fail to get good signal, leaving you with a link.local address, or a valid address, but no default route. This may be your problem here. You might want to just put the AirPort back... -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with 13/10/2003 current
Il Mar, 2003-10-14 alle 15:09, Soren Schmidt ha scritto: It seems Matteo Riondato wrote: After having update my -CURRENT box to yesterday afternoon (Central Europe Time) sources, I can't get it to boot. It stops probing ata1: GEOM: create disk ad0 dp=0xc4536a70 I never had problem with ATAng before, so it is probably related to a recent commit. Could you try this patch please: Index: ata-queue.c = It works perfectly and solves my problem. Thanks. Do you plan to commit it? Best Regards -- Rionda aka Matteo Riondato G.U.F.I Staff Member (http://www.gufi.org) BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda) GPG key at: http://www.riondabsd.net/riondagpg.asc Sent from: kaiser.sig11.org running FreeBSD-5.1-CURRENT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's up with the IP stack?
Date: Tue, 14 Oct 2003 09:56:47 -0700 From: Terry Lambert [EMAIL PROTECTED] Kevin Oberman wrote: When I see this I can reach some LAN hosts, but not others. I can always seem to reach the access point. I can usually, but not always, reach most other systems on the LAN, but not the gateway router, a Sonic Wall firewall. I have logged onto another system and then connected to the firewall, so it looks like the physical path is OK. The problem is intermittent and I have only scattered data. I've been seeing it sice about the beginning of October. I was blaming it on hardware, but now that I see these reports, maybe it's not. (I just replaced my Apple Airport AP with a D-Link, so there is something to suspect.) In may case things just start working again. The pause can vary from a few seconds to about 10 minutes. netstat -rnf inet and arp -a output both look to be fine. What about your IP address and default route? I've seen wireless cards, especially IBM ones, fail to get good signal, leaving you with a link.local address, or a valid address, but no default route. This may be your problem here. You might want to just put the AirPort back... The problem is that the Airport died. Looks like a power supply issue or a bad cap as it fails whenever it's moving lots of data and then recovers after several quite seconds. My wife's laptop link dies at the same time, so that's why I bought the Linksys. (Sorry for saying D-Link. I get them confused too often.) No. I am monitoring signal strength and it is excellent. I use a static address and gateway and they're fine, too. Both 'arp -a' and 'netstat -rnf inet' show what I would expect including the proper MAC address for the firewall and the hub. I've been using this card for about a year and a half and this problem has just shown up in the past few weeks. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with 13/10/2003 current
It seems Matteo Riondato wrote: It works perfectly and solves my problem. Thanks. Do you plan to commit it? Already done :) -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
How to create distribution for later NFS sysinstall on other box?
Some of my systems are 5.1-CURRENT but I still have some older 4.x boxes. I'd like to upgrade them to the same OS as my 5.1 boxes. It seems stupid to feed them boot floppies then FTP the OS across the WAN from freebsd.org or mirrors. I expect there's a way to build a distribution on my main 5.1 system then use sysinstall on the target 4.x to install via NFS (or FTP or...) over the LAN. I have not found any pointers on doing this in the Handbook or a couple quick Googles (perhaps I'm searching on the wrong terms). Seems it should be something like this on the server: cd /usr/src make distribution I'd like to make the distribution based on my 5.1-CURRENT, rather than copying/creating a 5.1-RELEASE image so I won't have to do a subsequent update to get it CURRENT. Any pointers? If I'm missing obvious docs, just tell me where to RTFM. :-) Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX Halted (AMD 5x86 133MHz)
* John Baldwin ([EMAIL PROTECTED]) wrote: Could there be a typo or other error in one of /boot/loader's scripts? Warning -- Unmatched control word: leave would be generated by resolveAbsBranch() in sys/boot/ficl/words.c. Given that no one else has reported such a warning and that some of the registers in his dump had weird values, I would really chalk this up to hardware. Bad hardware confirmed. I've replaced the memory and tried another hard disk with a FreeBSD install, no luck. It must be the mother-board. Thanks for the help, -- Giovanni P. Tirloni gpt at tirloni.org Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt statistics?
On Mon, 13 Oct 2003, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Nate Lawson [EMAIL PROTECTED] writes: : Given that, my biggest concern now is IO corruption. Are there any : devices that have a low interrupt rate (or bus mastering rate) that cannot : handle a few hundred us latency added to their handler startup? I'm : thinking something like a floppy drive where the time between interrupts : is great enough that cpu_idle() is called but that need to be serviced : quickly or data is over/underrun. sio/uart At 115200 baud, you have 173us to service the interrupt when the FIFO interrupt level is set to HI. At 460800 at HI you have 43us. With the more conservative MED settings, these numbers are 4 times better (670us and 173us). 200us is smack dab in the middle of these times. This is inbound data, so things could be idle and there be issues. Not sure about other devices. Ok, I've instrumented the driver and found that most of the time, sleeps are 2-6 ms. Once in a while, they are a few hundred us. Rarely, they are tens of us. I'll test the driver with periodic serial IO to see if there is any data loss. I assume it's ok to tell people who are running high serial port speeds to disable the lowest sleep states. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with 13/10/2003 current
Hi, I'd like to give a try for this new code solving lost interrupts but current code still doesn't find all my slave disks. Is there anything what might help on this? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
GEOM_BDE
Hi I have problem with compiling my kernel. I wanted to play with gbde so i added options GEOM_BDE.I have been doing cvsup at Tue Oct 14 20:43:17 2003 CEST My config kernel: machine i386 cpu I686_CPU ident BSD5m makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options SC_PIXEL_MODE options IPFIREWALL options IPDIVERT options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPFIREWALL_FORWARD options TCP_DROP_SYNFIN options PFIL_HOOKS options QUOTA options EXT2FS options MAXCONS=20 options SC_HISTORY_SIZE=5000 options CPU_ENABLE_SSE options GEOM_BDE options SCHED_4BSD #4BSD scheduler options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big options COMPAT_43 #Compatible with BSD 4.3 [KEEP options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV options AHC_REG_PRETTY_PRINT options AHD_REG_PRETTY_PRINT options DDB #Enable the kernel debugger options CONSPEED=115200 device isa device pci device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support device sc device npx device sio # 8250, 16[45]50 based serial ports device ppc device ppbus # Parallel port bus (required) device loop# Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device bpf # Berkeley packet filter Errors during compile: cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common - finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror vers.c g_bde_crypt.o: In function `g_bde_kkey': /usr/src/sys/geom/bde/g_bde.h:189: undefined reference to `rijndael_makeKey' g_bde_crypt.o: In function `g_bde_crypt_read': /usr/src/sys/geom/bde/g_bde.h:180: undefined reference to `rijndael_cipherInit' /usr/src/sys/geom/bde/g_bde.h:207: undefined reference to `rijndael_blockDecrypt' /usr/src/sys/geom/bde/g_bde.h:189: undefined reference to `rijndael_makeKey' /usr/src/sys/geom/bde/g_bde.h:207: undefined reference to `rijndael_blockDecrypt' g_bde_crypt.o: In function `g_bde_crypt_write': /usr/src/sys/geom/bde/g_bde.h:180: undefined reference to `rijndael_cipherInit' /usr/src/sys/geom/bde/g_bde.h:189: undefined reference to `rijndael_makeKey' /usr/src/sys/geom/bde/g_bde.h:198: undefined reference to `rijndael_blockEncrypt' /usr/src/sys/geom/bde/g_bde.h:198: undefined reference to `rijndael_blockEncrypt' g_bde_crypt.o: In function `g_bde_crypt_delete': /usr/src/sys/geom/bde/g_bde.h:180: undefined reference to `rijndael_cipherInit' /usr/src/sys/geom/bde/g_bde.h:189: undefined reference to `rijndael_makeKey' /usr/src/sys/geom/bde/g_bde.h:198: undefined reference to `rijndael_blockEncrypt' g_bde_lock.o: In function `g_bde_hash_pass': /usr/src/sys/geom/bde/g_bde_lock.c:81: undefined reference to `SHA512_Init' /usr/src/sys/geom/bde/g_bde_lock.c:82: undefined reference to `SHA512_Update' /usr/src/sys/geom/bde/g_bde_lock.c:83: undefined reference to `SHA512_Final' g_bde_lock.o: In function `g_bde_keyloc_encrypt': /usr/src/sys/geom/bde/g_bde.h:180: undefined reference to `rijndael_cipherInit' /usr/src/sys/geom/bde/g_bde.h:189: undefined reference to `rijndael_makeKey' /usr/src/sys/geom/bde/g_bde.h:198:
Re: boot hang: ata1: resetting devices .. done (5.1-CURRENT, IBMT30)
Anyone tried going forward to 1.8? I just tried 1.8, it did not fix the problem. Symtoms are still the same, I noticed that ata-queue.c had a .rej so in a fit of lets make sure everything is validness I deleted my /usr/src tree and re-sup'd the entire thing, then built. Between that and the 1.9 version of ata-queue.c, both of the problems (the hang with ata1: resetting and the hang if atapicam is defined in the kernel) I had been reporting have been cleared up. Now if I could just get this darned T30 to sleep properly, all would be wonderful. :) nomad --- - Lee nomad Damon - \ play: [EMAIL PROTECTED]or castle!nomad \ work: [EMAIL PROTECTED] \ /\ Seneschal, Castle PAUS./ \ Celebrate Diversity /\ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic with -current kernel ata_timeout
Help! Am I alone with this? I cvsuped again today built world,kernel. Still this panic. Soeren, do you get this also? You have the Motherboard P4S8X which I donated a couple of months ago. It does not happen with an Oct 5 kernel. On Sun, Oct 12, 2003 at 01:52:40PM +0200, C. Kukulies wrote: with a -current cvsup I'm getting a kernel panic during boot: ata0 resetting devices is happening right before that ata_timout soft_clock ithread fork_exit fork_trampoline __trap 0x1 -- Chris Christoph Kukulies kuku_at_physik.rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic with -current kernel ata_timeout
It seems Christoph P. Kukulies wrote: Help! Am I alone with this? I cvsuped again today built world,kernel. Still this panic. Soeren, do you get this also? You have the Motherboard P4S8X which I donated a couple of months ago. Nope, I dont see this at all. No problems whatsoever with the P3S8X... Are you sure you have rev 1.9 of ata-queue.c ? That has the lost interrupt recover code redone... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt statistics?
On Tue, 14 Oct 2003, Nate Lawson wrote: On Mon, 13 Oct 2003, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Nate Lawson [EMAIL PROTECTED] writes: : Given that, my biggest concern now is IO corruption. Are there any : devices that have a low interrupt rate (or bus mastering rate) that cannot : handle a few hundred us latency added to their handler startup? I'm : thinking something like a floppy drive where the time between interrupts : is great enough that cpu_idle() is called but that need to be serviced : quickly or data is over/underrun. sio/uart At 115200 baud, you have 173us to service the interrupt when the FIFO interrupt level is set to HI. At 460800 at HI you have 43us. With the more conservative MED settings, these numbers are 4 times better (670us and 173us). 200us is smack dab in the middle of these times. This is inbound data, so things could be idle and there be issues. Not sure about other devices. Ok, I've instrumented the driver and found that most of the time, sleeps are 2-6 ms. Once in a while, they are a few hundred us. Rarely, they are 5 ms would be average with HZ=100. tens of us. I'll test the driver with periodic serial IO to see if there is any data loss. I assume it's ok to tell people who are running high serial port speeds to disable the lowest sleep states. I thought that serial devices weren't being considered because you asked about devices with a low interrupt rate. As I understand it, devices with a fast interrupt rate will prevent any sleeping by interrupting often. If they are a problem, then the above numbers need adjustments: At 115200 bps (no bauds please), you have (86.8 * (rx_fifo_size - rx_fifo_trigger_level)) us to service the interrupt. With unbuffered UARTs or with buffered UARTS and the trigger level set to 1 less than the size, you have 86.8 us. At 3686400 bps you have 2.713 us worst case (I've tested 3686400 bps on a Celeron366 but can't quite get it to work; 921600 bps works well enough to not lose interrupts). That is for one port. For multiple ports, the time between interrupts may be much shorter than the inter-character time, but it can't be much shorter or the system would overload. The conservative MEDH settings are the default for FreeBSD, but at 921600 bps they only give half as much time as the HI settings do at 115200 bps, so they should not be needed unless there are many active ports (else 921600 bps and unbuffered 115200 bps won't work). the more conservative MED settings, these numbers are 4 times better (670us and 173us). 200us is smack dab in the middle of these times. This is inbound data, so things could be idle and there be issues. sio actually has more problems with outbound data at 921600 bps. Output interrupts normally occur just 1 character time before the output completes, so at 921600 bps there is only 10.8 us to respond before missing opportunities to send, and it is easy to be doing something else for 10.8 usec (e.g., reading the input fifo for the same UART or filling the output fifo for another UART, not to mention other system activity). Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sata + vinum + Asus p4p800 = :(
On Tuesday, 14 October 2003 at 18:46:44 +0200, Balazs Nagy wrote: Hi, I had a -CURRENT setting with an Abit BE7-S and two SATA disks with vinum configuration. It worked very well until a power failure, and the mainboard died. Yesterday I got a replacement mainboard, the only type met the requirements (eg. two SATA ports) in the store: an Asus P4P800. My only problem is with the disks. I can use all USB ports (8; what a server could do with eight USB ports?), the 3C940 Gigabit Ethernet port (I disabled the sound subsystem), and everything works until the first fsck, when the kernel paniced. Here is the dmesg: GEOM: create disk ad0 dp=0xc6b4bb70 ad0: 4028MB Maxtor 90422D2 [8184/16/63] at ata0-master UDMA33 acd0: CDROM GCR-8523B at ata0-slave PIO4 GEOM: create disk ad4 dp=0xc6b4b070 ad4: 117246MB Maxtor 6Y120M0 [238216/16/63] at ata2-master UDMA133 GEOM: create disk ad6 dp=0xc6b4b170 ad6: 117246MB Maxtor 6Y120M0 [238216/16/63] at ata3-master UDMA133 Mounting root from ufs:/dev/vinum/root panic: ata_dmasetup: transfer active on this device! I did further investigation: I booted from ata0-master, and mounted /dev/vinum/root as /mnt. A simple fsck -f -B /mnt killed the system. I did the same with /dev/ad4s1a (this is the boot hack partition from the handbook), then I switched off softupdates. No win. I tried to boot with safe mode either, but it hung with page fault. What can I do? Provide a dump? Analyse the problem yourself? This *is* -CURRENT, after all. Besides, why my SATA interfaces are recognized as UDMA133? It sounds like this could be an issue with ATA compatibility issues with this mother board. You should be able to mount your root file system from the underlying UFS partition, thus disabling Vinum; at least that would help you track down the problem. Greg -- See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: Unable to boot cvsup 20031011
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 12 Oct 2003, Anish Mistry wrote: I finally recvsupped today as some problems with my ata stuff was fixed. Went through the normal buildworld/kernel progress and on reboot of loading the new kernel, it loads the kernel and modules and then as it starts booting it just causes my machine to restart. It doesn't have a serial port so I can't get any debug info that way. I can still boot in with an old kernel, so i can get debug info that way if needed. Old dmesg and pciconf attached. - -- Anish Mistry hi. i'm having the same problem and my pciconf output is the same as yours. you have a fujitsu lifebook p2120, right? i tried the same source (world and kernel) on one of my desktop machines and it is able to boot just fine. looks like this is a tm crusoe issue. maybe something with the acpi or longrun stuff. i'm not too proficient with freebsd kernel hacking, so hopefully someone else will be able to tackle this. - --- Brian J. Creasy -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/jIaZWMKWjLymTUYRArVrAJ454d0I3V3GvA+9FkNqpz6EL3y1KQCgt9Vk ArLxKFm9nNsfgiSe2ZpYPWs= =zLwX -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
multicast panic
I'm trying to compile a multicast application and the system panics every time I run configure: Oct 14 13:46:11 groggy su: dave to root on /dev/ttyp0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x68 fault code = supervisor read, page not present instruction pointer = 0x8:0xc053ddd2 stack pointer = 0x10:0xc9241bd4 frame pointer = 0x10:0xc9241be4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1143 (conftest) kernel: type 12 trap, code=0 Stopped at _mtx_lock_sleep+0x192: movl0x68(%ecx),%edx db trace _mtx_lock_sleep(c075a580,0,0,0) at _mtx_lock_sleep+0x192 get_sg_cnt(c9241c60) at get_sg_cnt+0x34 X_mrt_ioctl(c0147210,c9241c60,c9241c34,c056d632,c0147210) at X_mrt_ioctl+0x2e rtioctl(c0147210,c9241c60,0,c0147210,c9241cec) at rtioctl+0x18 soo_ioctl(c1cebbf4,c0147210,c9241c60,c1deb380,c1cbfe40) at soo_ioctl+0x152 ioctl(c1cbfe40,c9241d14,3,0,206) at ioctl+0x4be syscall(2f,2f,2f,bfbffa88,bfbffa74) at syscall+0x27b Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280be37f, esp = 0xbfbffa5c, ebp = 0xbfbffaac --- db ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to boot cvsup 20031011
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi. i'm having the same problem and my pciconf output is the same as yours. you have a fujitsu lifebook p2120, right? P2110. I'm at least glad to hear that I'm not alone. i tried the same source (world and kernel) on one of my desktop machines and it is able to boot just fine. looks like this is a tm crusoe issue. maybe something with the acpi or longrun stuff. i'm not too proficient with freebsd kernel hacking, so hopefully someone else will be able to tackle this. When was the last good cvsup that you did? I think we will have to track down ourselves which commit broke since no one else is having this problem. I don't remember when I did mine since I let a friend borrow it for a couple of weeks. I hope that someone with more knowledge can point where to start looking. It isn't ACPI since it still doesn't work when unloaded from the boot loader. --- Brian J. Creasy - -- Anish Mistry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/jJdBxqA5ziudZT0RAhjdAJwJyo4t0aPF14fW5zH7i6SU+N3T+gCg3dJD 8CZc2ypG6VYchDSuPVWKEt8= =AQay -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.1 stability
I would just like to take this moment to congratulate all the people here who have made FreeBSD 5 the success that it is, and have put in all the hard work and effort to make it such a reliable and stable workhorse. I am not sure what sort of uptimes people have had with -CURRENT as it is a work in progress, but here is an uptime of a 5.1 box that has just passed 100 days. Unfortunately this machine has to move now which means shutting down so the uptime will be lost (and i have cvsup'd her just a few minutes ago), but it shows the reliability that we now have in FreeBSD 5. This box is a Dual CPU system with SCSI and IDE drives, two NIC's, and gets thrashed quite heavily at times. Keep up the good work people! :) Martin. diablo:~ uname -a FreeBSD diablo.diskiller.net 5.1-CURRENT FreeBSD 5.1-CURRENT #5: Thu Jun 12 20:19:23 CST 2003 [EMAIL PROTECTED]:/junk/src/sys/i386/compile/DIABLO i386 diablo:~ uptime 10:21AM up 101 days, 17:12, 1 user, load averages: 0.33, 0.58, 0.44 diablo:~ date Wed Oct 15 10:21:40 CST 2003 diablo:~ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to boot cvsup 20031011
On 12 Oct, Anish Mistry wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I finally recvsupped today as some problems with my ata stuff was fixed. Went through the normal buildworld/kernel progress and on reboot of loading the new kernel, it loads the kernel and modules and then as it starts booting it just causes my machine to restart. It doesn't have a serial port so I can't get any debug info that way. I can still boot in with an old kernel, so i can get debug info that way if needed. Old dmesg and pciconf attached. What version of sys/i386/i386/pmap.c do you have? If you are getting the pmap_zero_page: CMAP3 busy, it should be fixed by version 1.446, which phk checked in 2003/10/12 10:55:45. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to boot cvsup 20031011
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 14 Oct 2003, Anish Mistry wrote: hi. i'm having the same problem and my pciconf output is the same as yours. you have a fujitsu lifebook p2120, right? P2110. I'm at least glad to hear that I'm not alone. as am i. i tried the same source (world and kernel) on one of my desktop machines and it is able to boot just fine. looks like this is a tm crusoe issue. maybe something with the acpi or longrun stuff. i'm not too proficient with freebsd kernel hacking, so hopefully someone else will be able to tackle this. When was the last good cvsup that you did? I think we will have to track down ourselves which commit broke since no one else is having this problem. I don't remember when I did mine since I let a friend borrow it for a couple of weeks. I hope that someone with more knowledge can point where to start looking. It isn't ACPI since it still doesn't work when unloaded from the boot loader. --- Brian J. Creasy -- Anish Mistry the last good cvsup i did was quite a while ago. july 13th. i got a little hung up with the semester starting back up. there isn't a way to tell cvsup a specific date to roll back to, is there? - --- Brian J. Creasy -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/jKCkWMKWjLymTUYRAg5tAJwNE3LxAxd+UNC+5hxKuYzLEZ5YTQCbBB7y rQ7JmenMscCERiZmAL3djCY= =UoI8 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
samba 3 on CURRENT and net.inet.tcp.blackhole
Hello, I have a problem with samba 3.0. I had to reinstall FreeBSD-CURRENT after known problems with ATAng and atapicam (beginning of September(?)), since then I can't set net.inet.tcp.blackhole=2 in /etc/sysctl.conf. If I add the option to sysctl then samba will hung until I press ^C. If I boot without this option then samba starts fine. However running now sysctl net.inet.tcp.blackhole=2 prevent smbclient from running. I still will be able to connect to smb shere from another computer. It seems that this is local problem but it never occurred before FreeBSD re-instal with samba 3.0. I do not see any errors in log files. I also contacted mantainer of samba but he was unable to help. I dont think that it is the issue with samba because samba 3 (devel) worked with previous snaps. So there must be something particular with my configuration of FreeBSD I would appreciate any help Michal ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with XFree86-4
Hi, I'm running 5.1-CURRENT (sources/ports from Oct/13) and the X package isn't compiling: FeaNoR# make package === Installing for XFree86-4.3.0,1 === XFree86-4.3.0,1 depends on executable: xvinfo - not found ===Verifying package for xvinfo in /usr/ports/x11/XFree86-4-clients === Building for XFree86-clients-4.3.0_3 making all in lib/lbxutil/lbx_zlib... making all in lib/lbxutil/delta... making all in lib/lbxutil/image... making all in programs/appres... making all in programs/bdftopcf... make: don't know how to make /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop *** Error code 2 Stop in /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/programs. *** Error code 1 Stop in /home/FreeBSD/ports/x11/XFree86-4-clients. *** Error code 1 Stop in /home/FreeBSD/ports/x11/XFree86-4. I had this same error a week ago, someone have a clue? Rossam. -- Das Leben auf Erden ist ein gemeiner Krieg. Wir spielen, wir kämpfen, wir setzen alles auf Sieg. Megaherz -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to boot cvsup 20031011
On Tue, Oct 14, 2003 at 09:19:10PM -0400, Brian J. Creasy wrote: the last good cvsup i did was quite a while ago. july 13th. i got a little hung up with the semester starting back up. there isn't a way to tell cvsup a specific date to roll back to, is there? There is... please to be RTFMing... it's in the manual page. BMS pgp0.pgp Description: PGP signature
Re: Unable to boot cvsup 20031011
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 14 Oct 2003, Don Lewis wrote: On 12 Oct, Anish Mistry wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I finally recvsupped today as some problems with my ata stuff was fixed. Went through the normal buildworld/kernel progress and on reboot of loading the new kernel, it loads the kernel and modules and then as it starts booting it just causes my machine to restart. It doesn't have a serial port so I can't get any debug info that way. I can still boot in with an old kernel, so i can get debug info that way if needed. Old dmesg and pciconf attached. What version of sys/i386/i386/pmap.c do you have? If you are getting the pmap_zero_page: CMAP3 busy, it should be fixed by version 1.446, which phk checked in 2003/10/12 10:55:45. __FBSDID($FreeBSD: src/sys/i386/i386/pmap.c,v 1.447 2003/10/13 03:28:31 alc Exp $); unfortunately, we are not getting any errors. the system just restarts after it starts booting the kernel. - --- Brian J. Creasy -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/jKNUWMKWjLymTUYRAq21AJ0TCECQQNrc7L1LZu6PJ/Xeq0ydxgCeIcoz 2TPzvP2MV/3/K6GmAJIFeHc= =4jHZ -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with XFree86-4
On Tue, 2003-10-14 at 17:21, Rossam Souza Silva wrote: Hi, I'm running 5.1-CURRENT (sources/ports from Oct/13) and the X package isn't compiling: FeaNoR# make package === Installing for XFree86-4.3.0,1 === XFree86-4.3.0,1 depends on executable: xvinfo - not found ===Verifying package for xvinfo in /usr/ports/x11/XFree86-4-clients === Building for XFree86-clients-4.3.0_3 making all in lib/lbxutil/lbx_zlib... making all in lib/lbxutil/delta... making all in lib/lbxutil/image... making all in programs/appres... making all in programs/bdftopcf... make: don't know how to make /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop *** Error code 2 Stop in /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/programs. *** Error code 1 Stop in /home/FreeBSD/ports/x11/XFree86-4-clients. *** Error code 1 Stop in /home/FreeBSD/ports/x11/XFree86-4. I had this same error a week ago, someone have a clue? Fixed yesterday. cvsup and try again. (The fix is in XFree86-4-libraries/files/ and XFree86-4-clients/scripts -- you need to cvs update both before rebuilding -clients) -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
pmap_enter: attempted pmap_enter on 4MB page
I've been getting subject panics lately. A sure way to provoke them is to portupgrade -ap. Sooner or later, panic. With the latest build: FreeBSD lab.databus.com 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Tue Oct 14 01:41:23 EDT 2003 it seemed to last longer (almost 30 min!) before failing. HW is Asus A7M266-D with 2xAthlon 2200+, 1GB, Adaptec 39160, 2x10k disks, em0, fxp0. I have (with a slightly older build) tried DISABLE_PSE and DISABLE_PG_G with no visible effect. I believe this started about 10/4/03, but the first few panics were PTE vanished. With builds in the last couple of days, the panic changed to the 4MB page one. I cannot rule out hardware, since this system has also lately been getting sig11's on buildworld - but mbmon shows no excessive temp and sensible rpms volts. Before 10/4, this system was rock solid. One oddity is that I can't get a UP kernel to boot - possibly because the bios is set to apic interrupts. If needed, I can make it happen again and get a traceback, or build an older kernel. I've been hoping for a magical fix, without success so far. Thanks for any advice, Barney ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
GEOM_BDE
Hi I have problem with compiling my kernel. I wanted to play with gbde so i added options GEOM_BDE.I have been doing cvsup at Tue Oct 14 20:43:17 2003 CEST My config kernel: /usr/src/sys/geom/bde/g_bde.h:180: undefined reference to `rijndael_cipherInit' /usr/src/sys/geom/bde/g_bde.h:207: undefined reference to `rijndael_blockDecrypt' I had same problem until I added device random to kernel config file. -- ___ Get your free Verizonmail at www.verizonmail.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: samba 3 on CURRENT and net.inet.tcp.blackhole
net.inet.tcp.blackhole changes the behaviour of refused incoming TCP connections and it doesn't seem possible it's the cause this problem. I'd sugest increasing the log level in smb.conf. Thanks for suggestion about logging. I know what net.inet.tcp.blackhole seting is for (and I would like to continue to use it). And this is why I do not understand what is wrong. I have run smbd -D -d10 and checked log.smbd but I could not find anything informative. Michal ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GEOM Gate.
Ok, GEOM Gate is ready for testing. For those who don't know what it is, they can read README: Aaargh! It's the return of nd(4) from SunOS. (Sorry about that.) -- Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: GEOM Gate.
From: Richard Tobin [mailto:[EMAIL PROTECTED] Ok, GEOM Gate is ready for testing. For those who don't know what it is, they can read README: Aaargh! It's the return of nd(4) from SunOS. Excuse me? # uname -a SunOS galaxy 4.1.4 18 sun4m # man nd No manual entry for nd. # Helge ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GEOM Gate.
On Tue, Oct 14, 2003 at 10:44:14PM +0200, Oldach, Helge wrote: From: Richard Tobin [mailto:[EMAIL PROTECTED] Ok, GEOM Gate is ready for testing. For those who don't know what it is, they can read README: Aaargh! It's the return of nd(4) from SunOS. Excuse me? # uname -a SunOS galaxy 4.1.4 18 sun4m Too new.. # man nd No manual entry for nd. # -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
libkse process stats breakage (Re: cvs commit: src/sys/amd64/amd64 exception.S trap.c src/sys/amd64/include frame.h signal.h ucontext.h)
On Wed, Oct 15, 2003 at 11:10:43AM +0800, David Xu wrote: The change you made to ucontext.h breaks libkse. :-( Speaking of libkse breakage: 10427 root 200 10500K 8380K kserel 6:44 0.00% 0.00% python2.3 10424 root 200 9292K 7280K kserel 4:43 0.00% 0.00% python2.3 3523 kris 200 50924K 40996K kserel 2:32 0.00% 0.00% MozillaFirebird-bin Those are threaded processes using libkse via libmap.conf, which are using CPU but do not have any CPU% listed. Scheduler is 4BSD, kernel was built yesterday. Kris pgp0.pgp Description: PGP signature
Re: Serial debug broken in recent -CURRENT?
On Wednesday, 8 October 2003 at 2:08:55 +1000, Bruce Evans wrote: On Tue, 30 Sep 2003, Sam Leffler wrote: It reliably locks up for me when you break into a running system; set a breakpoint; and then continue. Machine is UP+HTT. Haven't tried other machines. This seems to be because rev.1.75 of db_interface.c disturbed some much larger bugs related to the ones that it fixed. It takes miracles for entering ddb to even sort of work in the SMP case. Ah, interesting. I hadn't thought that it might be related to SMP. If one of multiple CPUs in kdb_trap() somehow stops the others, then the others face different problems when they restart. They can't just return because debugger traps are not restartable (by just returning). They can't just proceed because the first CPU may changed the state in such a way as to make proceeding in the normal way not work (e.g., it may have deleted a breakpoint). These problems are not correctly or completely fixed in: Index: db_interface.c === RCS file: /home/ncvs/src/sys/i386/i386/db_interface.c,v retrieving revision 1.75 diff -u -2 -r1.75 db_interface.c --- db_interface.c7 Sep 2003 13:43:01 - 1.75 +++ db_interface.c7 Oct 2003 14:11:35 - ... This is supposed to stop the other CPUs either in kdb_trap() or normally. The timeouts are hopefully long enough for all the CPUs to stop in 1 of these ways. But it doesn't always work. 1 possible problem is that stop and start IPIs may be delivered out of order, so CPUs stopped in kdb_trap() may end up stopped (since we don't wait for them to see the stop IPI). Correct. This patch doesn't fix the problem on my system. I've built a single processor kernel (comment out SMP and APIC_IO), and that *does* work with remote gdb, so it's almost certainly an SMP issue. I have a dump of a partially hanging system if that's of any help. Greg -- See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
FreeBSD-CURRENT telnet can't disable autologin
Some people don't want auto login but are being frustrated when they try to disable it
as below.
What is the correct way to disable this feature?
fuzz: {1016} ls -l ~/.telnetrc
-rw-r- 1 thyerm scis 38 Oct 15 13:11 /home/thyerm/.telnetrc
fuzz: {1017} cat ~/.telnetrc
unset autologin
fuzz: {1018} telnet
telnet display
will flush output when sending interrupt characters.
won't send interrupt characters in urgent mode.
will send login name and/or authentication information.- * NOTE
won't skip reading of ~/.telnetrc file.
won't map carriage return on output.
will recognize certain control characters.
won't turn on socket level debugging.
won't print hexadecimal representation of network traffic.
won't print user readable output for netdata.
won't show option processing.
won't print hexadecimal representation of terminal traffic.
echo[^E]
escape [^]]
rlogin [off]
tracefile (standard output)
flushoutput [^O]
interrupt [^C]
quit[^\]
eof [^D]
erase [^H]
kill[^U]
lnext [^V]
susp[^Z]
reprint [^R]
worderase [^W]
start [^Q]
stop[^S]
forw1 [off]
forw2 [off]
ayt [^T]
telnet
Matthew Thyer Phone: +61 8 8259 7249
Science Corporate Information Systems Fax:+61 8 8259 5537
Defence Science and Technology Organisation, Edinburgh
PO Box 1500 EDINBURGH South Australia 5111
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the
CRIMES ACT 1914. If you have received this email in error, you are
requested to contact the sender and delete the email.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libkse process stats breakage (Re: cvs commit:src/sys/amd64/amd64 ucontext.h)
On Tue, 14 Oct 2003, Kris Kennaway wrote: On Wed, Oct 15, 2003 at 11:10:43AM +0800, David Xu wrote: The change you made to ucontext.h breaks libkse. :-( Speaking of libkse breakage: 10427 root 200 10500K 8380K kserel 6:44 0.00% 0.00% python2.3 10424 root 200 9292K 7280K kserel 4:43 0.00% 0.00% python2.3 3523 kris 200 50924K 40996K kserel 2:32 0.00% 0.00% MozillaFirebird-bin Those are threaded processes using libkse via libmap.conf, which are using CPU but do not have any CPU% listed. Scheduler is 4BSD, kernel was built yesterday. Other than stats being off, do the processes seem to be working correctly? Oh, and is this an SMP or UP system? -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 stability
Martin Minkus wrote: I would just like to take this moment to congratulate all the people here who have made FreeBSD 5 the success that it is, and have put in all the hard work and effort to make it such a reliable and stable workhorse. snip Keep up the good work people! :) Martin. diablo:~ uname -a FreeBSD diablo.diskiller.net 5.1-CURRENT FreeBSD 5.1-CURRENT #5: Thu Jun 12 20:19:23 CST 2003 [EMAIL PROTECTED]:/junk/src/sys/i386/compile/DIABLO i386 diablo:~ uptime 10:21AM up 101 days, 17:12, 1 user, load averages: 0.33, 0.58, 0.44 diablo:~ date Wed Oct 15 10:21:40 CST 2003 diablo:~ [EMAIL PROTECTED] uname -a FreeBSD don.domen 5.1-RELEASE FreeBSD 5.1-RELEASE #3: Sat Jun 14 11:53:13 EEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DON i386 [EMAIL PROTECTED] uptime 8:22 up 112 days, 17:14, 1 user, load averages: 1,34 1,69 1,72 The reson of last reboot was absence of power. Relativly heavy loaded Oracle 9.1 server. Dual Intel Pentium III (933.08-MHz 686-class CPU) Intel motherboard, ServerWorks chipset, Adaptec aic7899 Ultra160 SCSI adapter Valera. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 stability
On 2003-10-15 11:01, Martin Minkus [EMAIL PROTECTED] wrote: Keep up the good work people! :) Martin. diablo:~ uname -a FreeBSD diablo.diskiller.net 5.1-CURRENT FreeBSD 5.1-CURRENT #5: Thu Jun 12 20:19:23 CST 2003 [EMAIL PROTECTED]:/junk/src/sys/i386/compile/DIABLO i386 diablo:~ uptime 10:21AM up 101 days, 17:12, 1 user, load averages: 0.33, 0.58, 0.44 diablo:~ date Wed Oct 15 10:21:40 CST 2003 diablo:~ Heh, nice uptime. Upgrading to a more recent -CURRENT shouldn't be too hard too. Last night before, after a long absense from home, I upgraded a 5.1 installation from Jun 15 to the latest -CURRENT. Everything was smooth and worked fine -- both during and after the installation :) aolMe thanks the developers too./aol - Giorgos ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
