Re: devd/devctl
In message: [EMAIL PROTECTED] Suleiman Souhlal [EMAIL PROTECTED] writes: : I was wondering if it would be a good idea to modify devd and : devctl for them to handle other events than attaching and detaching : devices.. For example, they could be used to mark a network : interface as down, when the network cable is pulled out, and run : dhclient when it is put back in. I think there are other : applications too. Yes. that has been the plan for some time now. However, dhclient is really lame in a lot of ways. Martin Blapp has made it a lot better of lates. In geral, I tend to believe that I shouldn't fix bugs in dhclient with devd things. However, a more general trend to more event types would be good because a device arriving isn't quite the same as a network interface arriving... Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GCC tickling obscure hardware bug or...?
On Fri, 2003-09-12 at 12:56, [EMAIL PROTECTED] wrote: Quoting Scott Reese [EMAIL PROTECTED]: Hello all, I'm rephrasing my previous question to reflect new findings in my situation in the hopes that someone may have an idea of what's going on here (see thread Internal compiler error in reload_cse_simplify_operands from earlier this week). In a nutshell, I have upgraded my machine to a PIV 2.4 GHz processor on a VIA P4B 400 motherboard with 512 MB Samsung 2700 DDRAM. I have a 300 Watt power supply with a ball-bearing fan and a Seagate 40 GB HD. The problem I'm having that I did not see with my PIII is that I'm getting intermittent internal compiler errors when attempting to compile anything (again, see previous thread for an example). I even did a fresh install of the system yesterday in order to rule out something random getting hosed causing problems with my compiler. Through experimentation, I've found that toggling the CFLAGS from -O to -O2 or vice-versa works around the problem (actually, I've had greater success leaving my CFLAGS set to -O2 -pipe and occasionally bringing them back to -O -pipe when I run into an ICE and then setting them back again). My hunch is that some hardware bug is being tickled by gcc somehow. I don't think it's the standard broken hardware thing because I've not received any signal 11/7/4 errors at all and the system runs wonderfully. So far it's been up for over 24 hours, compiling ports and running without a hitch. The only strangeness is the compiler's behavior. Also, I should mention that I added options DISABLE_PSE options DISABLE_PG_G to my kernel config but the ICE's still persist, though they seem to be less frequent now. Attached is my dmesg, please let me know if anyone would like any more information about this or if you have any idea what might be going on here. Thank you, Scott Whenever I've had problems like this, it's been either bad memory, or bad memory settings in bios. I'd check both of those things. Sonofagun...I just tweaked the RAM settings yet another time and turned the speed down to 133 (recommended 166 in the mobo manual) and that seems to be working so far. Sorry for the noise, folks. These are known problems in 5.1-RELEASE but have been dealt with in -current, I'm waiting for 5.2 too in order to remove both the options DISABLE_PSE and DISABLE_PG_G. Furthermore GCC have been also improved and should more correctly support P4 with optimization levels higher than -O. Please check this mailing-list archives for more information. Anthony. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB da(4) quirks deprecated
Andrew Thompson wrote this message on Sat, Sep 13, 2003 at 16:33 +1200: I have just got around to trying this pen-drive again and have been trying tracking down data corruptions. If I mount the drive, write a file, umount/mount again the file is different. Using cmp I have found that there are consistent blocks of nulls in the written file where data should be. The block is always 0xfff bytes long and starts at 0x3000. I have tried many files and the offsets are always the same. All the other data in the file is correct and at the right location. 0x3000 - 0x3fff 0x7000 - 0x7fff 0xb000 - 0xbfff 0xf000 - 0x 0x13000 - 0x13fff ... and so on until the end of the file ... Any suggestions? Is this on an ohci controller? I'm trying to track down mbr's problem also that appears to do the same thing. Have you tried doing an fstat before umounting the fs? (There is a bug in msdosfs that doesn't sync the disk before unmount completes.) This is wierd in that it's the second page of the second transfer. The ohci can do up to 8k transfers in one TD, and then chain the TD's together if a larger block sized is used. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng interrupt storm and bogus interrupt stormproofing
On Tue, 9 Sep 2003, Bruce Evans wrote: ATAng generates an interrupt storm deterministically on 1 system here. This should lock up the system, but bugs in interrupt handler scheduling prevent the lockup except in my version of -current where the bugs are different. ... Bugs in interrupt handler scheduling: Ignoring level-sensitive interrupts should result in their thread being switched to endlessly (except for switches to higher priority threads and possibly for switches to equal priority threads). But there is some bug in interrupt handler scheduling that results in low priority threads running while the high priority interrupt storm thread is runnable. This allows the thread that issued the ATA_ATAPI_IDENTIFY command to run eventually, and it or another thread clears the storm as a side effect of issuing another command. I suspect that the scheduling bug is related to the old one of just setting the TDF_NEEDRESCHED flag when a switch can't be done immediately. TDF_NEEDRESCHED has no effect on kernel threads since it is only examined on return to user mode. ... The scheduling bug is indeed related to that. Here is a quick fix. See the too-large comments in the last hunk of it for details. The early return for the interrupts case is older code. It is more needed and perhaps essential witht the main part of the patch. The debugging code should not report any problems now. This depends on a recently committed fix to stop ddb calling cpu_unpend() via DELAY(). %%% Index: critical.c === RCS file: /home/ncvs/src/sys/i386/i386/critical.c,v retrieving revision 1.11 diff -u -2 -r1.11 critical.c --- critical.c 12 Aug 2003 23:24:04 - 1.11 +++ critical.c 12 Sep 2003 23:07:36 - @@ -37,4 +37,5 @@ #include sys/pcpu.h #include sys/proc.h +#include sys/resourcevar.h #include sys/sysctl.h #include sys/ucontext.h @@ -56,4 +57,6 @@ #endif +#include ddb/ddb.h + void i386_unpend(void);/* NOTE: not static, called from assembly */ @@ -67,8 +70,32 @@ register_t eflags; struct thread *td; +#ifdef DDB + static int traced; + + if (db_active !traced) { + traced = 1; + printf(cpu_unpend: naughty db\n); + backtrace(); + } +#endif + + /* +* CPU interrupts can be masked here (e.g., if we are called (nested) +* from code that does intr_disable(); critical_enter(); ... +* critical_exit();), and interrupts can even be pending then (e.g., +* if we are called (nested) from Xintr* as part of ICU locking in +* the SMP case after Xintr* has interrupted critical_enter() after +* the latter decremented td-td_intr_nesting_level to 0 but before it +* called us). If so, don't unpend interrupts now. +*/ + if ((read_eflags() PSL_I) == 0) + return; td = curthread; +more: eflags = intr_disable(); if (PCPU_GET(int_pending)) { + if (td-td_intr_nesting_level != 0) + Debugger(cpu_unpend: intr_nesting_level != 0); ++td-td_intr_nesting_level; i386_unpend(); @@ -76,4 +103,50 @@ } intr_restore(eflags); + + /* +* We kept td_critnest 0 in i386_unpend() to prevent context +* switches away from us. This results in ithread_schedule() +* being called in an abnormal environment so it doesn't switch +* context to hardware interrupt handlers in the normal way. It +* sets TDF_NEEDRESCHED, but that is only intended for use in +* ast(). Use it here too to ensure running the highest priority +* thread. +* +* Prenting context switches away from us is probably not needed +* except possibly as an optimization. We have to do it if we +* use the int_pending lock since it prevents other threads +* doing any unpending, but letting the other threads do the +* unpending should be safe if we are careful enough. The calls +* to i386_unpend() from Xfastintr* need special care since they +* also have interrupts masked in the CPU. Our check of +* TDF_NEEDRESCHED doesn't help for these calls. +* +* td_critnest 0 also prevents swi_sched() actually switching +* context. It is normal and probably even correct for swi_sched() +* to not switch immediately, but this shows that swi_sched() +* is broken as designed. It should just schedule the scheduling +* of a SWI; actual scheduling should not occur until a switch is +* possible. swi_sched() inherits the scheduling bug from +* ithread_schedule() -- in cases where a switch is not possible, +* it sets TDF_NEEDRESCHED but only ast() and now here checks this +* flag. +* +* XXX don't switch when cold -- can't
Re: usb flashkey disk copy error
Barney Wolff wrote this message on Fri, Sep 12, 2003 at 15:52 -0400: Patch below had some problems. Needed #ifdef USB_DEBUG around the ref to ohcidebug to compile, and either BROKEN_OHCI added to the list of valid options or (as I did) kludged to 1. Worse, trying to mount_msdosfs my camera caused an instant panic: Length went negative: -4096. If that's not enough info, I imagine I can recreate the panic. Yeh, I ran across this when testing on a system. But you can ignore this patch. With this patch applied the USB device would stop working even after I fixed the #ifdef and -4096 problems.. (btw, I never intended for the patch to compile w/o USB_DEBUG, but since the modules don't inherit the kernel config's make files, it breaks).. Just to restate my particular problem, I get the wrong data on read of an existing file from the memory stick on the camera. I have not dared to try writing to it since reads don't work. Ok, I have a system that I'm going to be looking at tomorrow that has a similar issue. Could you file an add in to kern/54982 that includes the dmesg output of your usb messages (ohci/uhci/umass/etc.) I tried using my 128meg CF in the same reader/machine that was having problems reading, and it worked. So it looks like reads are broken for only some devices, not all. :( On Sun, Sep 07, 2003 at 01:39:08PM -0700, John-Mark Gurney wrote: Barney Wolff wrote this message on Sun, Sep 07, 2003 at 15:48 -0400: I can't do more detailed diagnosis right now, but could in a few days. When you get a chance (or anyone else who has this problem), try the attached patch, and add options BROKEN_OHCI to your kernel config file. Please set hw.usb.ohci.debug=1, and send me the dmesg output of the writes. (When you copy the data to the media.) Hmmm. I just thought of something. Now is the data corrupt still correupt on another system? What I mean is did the data get written properly, but just isn't being read back from the media correctly. Unless you are coping a file larger than memory size, the cmp just pulls it from memory, not from the media. The umount/mount forces a flush of the cache, and so attempts to read from the media. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
re: usb flashkey
hello all, I tested the flashkey with and without fsync. Infortunately the result is the same in all cases: a random write fault for one byte at each time, repeated at random places. With a 32Mb (old model i think) flashkey, all is correct and repeated writes are ok. Reading operations are correct (a bad file is always bad for current and for XP. The flashkey runs quite well on XP (verifyed a big number of times on writing). errors occur at any place on the flashkey (msdos-sys) as attested by a partial copy of the flashkey done by dd: (bootmbr fats directory, and of file). Writing errors are not systematic, and sometimes all goes fine. At my sense, it looks like a time problem or as mentionned by Bruce Evans or an interrupt problem. Hope this can help. Best regards. raoul [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do put an ATA disk into sleep/standby mode?
Darren Pilgrim wrote this message on Thu, Sep 11, 2003 at 17:55 -0700: In my workstation, running 5.1-R, I have two disks, one containing FreeBSD, the other Windows. Since the Windows disk isn't used at all when in FreeBSD, I would like to put it into standby or sleep mode (whichever is necessary) to make it spin down, reducing heat and noise production--both of which have become a real problem. This is at least technically possible, since spinning down a disk is part of the APM sleep mode. The capabilities list atacontrol reports for the disk in question shows power management and advanced power management as being supported, and I've gotten Windows to spin down this disk. I haven't had any luck figuring out how to do this in FreeBSD, though. So how do I accomplish this? Well, in -current, sos has commited a frame work that will let a userland utility to send arbitrary commands to the disks, and so this will be possible from a utility. I wanted this feature too, and I happen to be browsing around the ata spec and noticed that you can include a spin down time as part of the disk idle command.. The disk idle command appears to be quite harmless as it just asks the drive to go to idle (if it was doing a read ahead or something else). So, I have this patch. I originally did this against 4.2-R I believe, but I think I have updated it to a more recent version.. (the revisions it's against are in the patch).. hope this helps you. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. Index: ata-all.h === RCS file: /home/ncvs/src/sys/dev/ata/ata-all.h,v retrieving revision 1.26.2.4 diff -u -r1.26.2.4 ata-all.h --- ata-all.h 2000/10/30 09:41:28 1.26.2.4 +++ ata-all.h 2002/07/23 20:02:25 @@ -74,6 +74,7 @@ #defineATA_C_READ_DMA 0xc8/* read w/DMA command */ #defineATA_C_WRITE_DMA 0xca/* write w/DMA command */ #defineATA_C_WRITE_DMA_QUEUED 0xcc/* write w/DMA QUEUED command */ +#defineATA_C_IDLE 0xe3/* idle command */ #defineATA_C_FLUSHCACHE0xe7/* flush cache to disk */ #defineATA_C_ATA_IDENTIFY 0xec/* get ATA params */ #defineATA_C_SETFEATURES 0xef/* features command */ Index: ata-disk.c === RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.60.2.9 diff -u -r1.60.2.9 ata-disk.c --- ata-disk.c 2000/11/04 23:04:52 1.60.2.9 +++ ata-disk.c 2002/07/23 20:44:15 @@ -174,6 +174,10 @@ printf(ad%d: disabling service interrupt failed\n, adp-lun); } +/* set standbye timer for 10 minutes */ +if (ata_command(adp-controller, adp-unit, ATA_C_IDLE, 0, 0, 0, 120, 0, ATA_WAIT_INTR)) +printf(ad%d: failed to set standby timer.\n, adp-lun); + devstat_add_entry(adp-stats, ad, adp-lun, DEV_BSIZE, DEVSTAT_NO_ORDERED_TAGS, DEVSTAT_TYPE_DIRECT | DEVSTAT_TYPE_IF_IDE, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shared object libintl.so.4 not found
On Fri, Sep 12, 2003 at 09:26:03PM -0700, Kevin Oberman wrote: Please don't give bogus advice. The solution is to update everything that depends upon gettext, e.g. by using portupgrade. Kris Maybe, but this bit me and the solution was to re-build gmake. Like I said, the solution is to update everything that depends upon gettext (which includes gmake). The changes in what routines are in libc cause this problem. I can't quite parse this, but the problem we're discussing has nothing whatsoever to do with libc. It's just a run-of-the-mill port update where a library major version was bumped. Obviously, if you remove the old library version while other software still expects to find it, that software will not be able to run. Kris pgp0.pgp Description: PGP signature
Re: How do put an ATA disk into sleep/standby mode?
On 2003.09.13 01:16:16 -0700, John-Mark Gurney [EMAIL PROTECTED] wrote: Darren Pilgrim wrote this message on Thu, Sep 11, 2003 at 17:55 -0700: In my workstation, running 5.1-R, I have two disks, one containing FreeBSD, the other Windows. Since the Windows disk isn't used at all when in FreeBSD, I would like to put it into standby or sleep mode(whichever is necessary) to make it spin down, reducing heat and noise production--both of which have become a real problem. This is at least technically possible, since spinning down a disk is part of the APM sleep mode. The capabilities list atacontrol reports for the disk in question shows power management and advanced power management as being supported, and I've gotten Windows to spin down this disk. I haven't had any luck figuring out how to do this in FreeBSD, though. So how do I accomplish this? Well, in -current, sos has commited a frame work that will let a userland utility to send arbitrary commands to the disks, and so this will be possible from a utility. I may just wait for 5.2 to work on this, then. I wanted this feature too, and I happen to be browsing around the ata spec and noticed that you can include a spin down time as part of the disk idle command.. The disk idle command appears to be quite harmless as it just asks the drive to go to idle (if it was doing a read ahead or something else). So, I have this patch. I originally did this against 4.2-R I believe, but I think I have updated it to a more recent version.. (the revisions it's against are in the patch).. hope this helps you. It does, in that it confirms that it's at least possible to spin down disks without suspending the entire machine. What I was thinking of, though, was a program or extension to atacontrol that would send the standby or sleep signal and detach the device to avoid having an unresponsive device entry. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
mysql-client compiler error
After building world as of late last night I decided to portupgrade -rRaf, mainly due to having the libintl.so.4 missing problem when I tried to start X. Everything compiled perfectly fine (and X is now working fine) except for databases/mysql40-client. I get this error: checking for C compiler default output... configure: error: C compiler cannot create executables configure: error: could not configure Berkeley DB I just wish to know is this something wrong with my system in general or is this just due to the -pthread discussions that have been occuring and that this port is one example of those that no longer works on -current? It is not a problem as I have the previously compiled/installed version still on the system but I just wish to confirm if the problem is likely to be down to the pthreads changes, and if I should report it to the port maintainer etc? Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng - delay probing for non-existent drive
On Fri, 12 Sep 2003, Bryan Liesner wrote: The last change to ata-lowlevel (rev 1.11) causes a 10-15 second delay probing for a drive that's not there: ata2: at 0xb400 on atapci0 ata2: [MPSAFE] hangs here for about 15 seconds ata3: at 0xa800 on atapci0 ata3: [MPSAFE] I can confirm this delay, but I haven't yet tried to revert ata-lowlevel.c to rev. 1.10. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng - delay probing for non-existent drive
Bryan Liesner [EMAIL PROTECTED] writes: The last change to ata-lowlevel (rev 1.11) causes a 10-15 second delay probing for a drive that's not there: [...] Same symptoms here... DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Bad performance
hi, i recently switched from mandrake to freebsd. i used a second system, to install freebsd 5.1 (release) on a 15 gb western digital disk. i installed the whole system without problems and managed to start gdm and gnome2. everything worked fine and performance (launching gdm, gnome2 and firebird) was really good (better then mdk :) then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) board, NVidia GeForce2 grafic card (using nvidia native driver for x11), AMD Duron 750 MHz, 512 mb ram. everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. i checked the ata settings; the drive is running in udma66 (as expected). cause i am new to *bsd i do not really know where to start or what further information to provide. any hint/idea would be great ! thx for ur help seb ps: the system i used to installed fbsd first is: AMD Duron 800 MHz, VIA VT8363/8365 [KT133/KM133] board, old SIS 8MB pci video card, 256 mb ram ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng - delay probing for non-existent drive
On Sat, 13 Sep 2003 14:28:03 +0200 [EMAIL PROTECTED] (Dag-Erling Smørgrav) wrote: Bryan Liesner [EMAIL PROTECTED] writes: The last change to ata-lowlevel (rev 1.11) causes a 10-15 second delay probing for a drive that's not there: [...] Same symptoms here... and here. cu kob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
On Saturday 13 September 2003 14:52, sebastian ssmoller wrote: hi, i recently switched from mandrake to freebsd. i used a second system, to install freebsd 5.1 (release) on a 15 gb western digital disk. i installed the whole system without problems and managed to start gdm and gnome2. everything worked fine and performance (launching gdm, gnome2 and firebird) was really good (better then mdk :) then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) board, NVidia GeForce2 grafic card (using nvidia native driver for x11), AMD Duron 750 MHz, 512 mb ram. everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. i checked the ata settings; the drive is running in udma66 (as expected). cause i am new to *bsd i do not really know where to start or what further information to provide. any hint/idea would be great ! thx for ur help seb ps: the system i used to installed fbsd first is: AMD Duron 800 MHz, VIA VT8363/8365 [KT133/KM133] board, old SIS 8MB pci video card, 256 mb ram Some things you might want to check: 1) Is your hostname set? It has to be set in /etc/rc.conf. 2) Is your hostname properly configure in /etc/hosts? It should look something like this: 127.0.0.1 localhost localhost.my.domain 127.0.0.1 hostname hostname.my.domain 127.0.0.1 hostname.my.domain. (note the dot after the last line. hostname.my.domain should be the output of 'hostname', and hostname the output of 'hostname -s') 3) Are you using IPv6? If not, try disabling it in your kernel. Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
On Sat, 2003-09-13 at 15:08, Arjan van Leeuwen wrote: On Saturday 13 September 2003 14:52, sebastian ssmoller wrote: hi, i recently switched from mandrake to freebsd. i used a second system, to install freebsd 5.1 (release) on a 15 gb western digital disk. i installed the whole system without problems and managed to start gdm and gnome2. everything worked fine and performance (launching gdm, gnome2 and firebird) was really good (better then mdk :) then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) board, NVidia GeForce2 grafic card (using nvidia native driver for x11), AMD Duron 750 MHz, 512 mb ram. everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. i checked the ata settings; the drive is running in udma66 (as expected). cause i am new to *bsd i do not really know where to start or what further information to provide. any hint/idea would be great ! thx for ur help seb ps: the system i used to installed fbsd first is: AMD Duron 800 MHz, VIA VT8363/8365 [KT133/KM133] board, old SIS 8MB pci video card, 256 mb ram Some things you might want to check: 1) Is your hostname set? It has to be set in /etc/rc.conf. is set correcly 2) Is your hostname properly configure in /etc/hosts? It should look something like this: 127.0.0.1 localhost localhost.my.domain 127.0.0.1 hostname hostname.my.domain 127.0.0.1 hostname.my.domain. (note the dot after the last line. hostname.my.domain should be the output of 'hostname', and hostname the output of 'hostname -s') seems to be correct too. btw. i use a DNS server (freebsd's std bind) which seems to work correctly too (responses ok, performance ok). firebird and gaim performance is ok when running, the bad perf. occurs on startup :( so currently i think it could be a problem with ide controler oder disk/drive settings (?) 3) Are you using IPv6? If not, try disabling it in your kernel. i do not need IPv6 but is still enabled. i will disable it. do u think this could have such an incluence on performace ? thx for ur hints seb Arjan ___ [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] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
On 13 Sep 2003 14:52:29 +0200 sebastian ssmoller [EMAIL PROTECTED] wrote: then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) board, NVidia GeForce2 grafic card (using nvidia native driver for x11), AMD Duron 750 MHz, 512 mb ram. everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. ps: the system i used to installed fbsd first is: AMD Duron 800 MHz, VIA VT8363/8365 [KT133/KM133] board, old SIS 8MB pci video card, 256 mb ram Is the system connected to a network, and if yes, does the network cards on both systems differ? If yes, have a look at the output of dmesg and try to find you network card. If you have it modify /etc/rc.conf (ifconfig_interface_name line). This sounds to me like a DNS problem, please check your default gateway (rc.conf: gateway line) too. Bye, Alexander. -- Weird enough for government work. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote: I have my own *working* driver, which is for 4-STABLE. It works with SK-9521 V2.0 (for me, at least) and it should work with 3C940. Note: This driver is ported from Nathan L. Binkert's OpenBSD driver. Note: This is completely independent from Stuart Walsh's work. ;-) Note: You must recompile MII driver and dependent network drivers. It's worth noting my patch was a port of Natan's patch also(which is actually Bill's driver technically speaking ;), so I'd be interested to see where i went wrong. But if it works then great, I'll get on with something else :) It's somewhat difficult to fine tune a driver when you dont actually own the hardware in question. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bikeshed
I missed BSDcon 03, what's a bikeshed got to do with anything, anyway? (besides bikes). Jay Sern Liew [EMAIL PROTECTED],ieee}.org gpg --keyserver pgp.mit.edu --recv-keys 0xA115A33F ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bikeshed
Liew Jay Sern wrote: I missed BSDcon 03, what's a bikeshed got to do with anything, anyway? (besides bikes). Let's see if I remember the story correctly: If you were building a nuclear reactor, your board of directors would likely agree with you on just about anything you tried to do, since a nuclear reactor is a complex, dangerous, difficult-to-build thing, that none of them wants to get into the dirty details, and there's enough for everyone to do anyway. If you were building a bikeshed, it's so simple, that having a number of people involved would cause endless arguments over things such as the color, or exact location of the bikeshed, since a bikeshed is simple enough that everyone understands it, and there's not really enough work for many people to be involved. The theory (I guess) being that people like to get involved. In a business atmosphere, the lesson is don't assign too many people to a project, it doesn't speed it up, it slows it down. In a volunteer project, where everyone is free to do what they want, it's too easy for too many people to focus on the easy parts, thus discussing petty details into the ground. Thus building a bikeshed has become a euphamism for discussing relatively unimportant details into the ground. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bikeshed
* Liew Jay Sern [EMAIL PROTECTED] [2003-09-13 17:07]: I missed BSDcon 03, what's a bikeshed got to do with anything, anyway? (besides bikes). See the Handbook here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#BIKESHED-PAINTING Regards -Thorsten -- You can't carve your way to success without cutting remarks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bikeshed
Bill Moran wrote: Thus building a bikeshed has become a euphamism for discussing relatively unimportant details into the ground. Just to point out a few examples, whenever someone wants to tweak with the rc scripts, or discuss what sysinstall should or shouldn't do, or even if we should bundle sendmail or not, everyone pipes in and nothing gets done. When someone recently discussed a major restructuring of inet's forwarding and routing methods, a single person piped in (well, besides the ones who cheered, like me :). Now, whether we bundle sendmail or not is essentially irrelevant. Even if you abhor whatever we do, it is a most trivial thing for a sysadmin to replace whatever it is with something else. The forwarding and routing changes, on the other hand, will affect every single system that uses IPv4. It will most assuredly result in a modification of the performances tradeoffs (eg, workstations with a single route vs heavy routers with thousands), it _will_ change the speed with which each packet is sent out of a host, and will even change things like MTU Path Discovery (if I read that right :). And there's *nothing* any sysadmin will be able to do about it, except chose another OS. Now, before I scare everyone, it is my belief that any measurable changes in performance will be positive. :-) But this illustrates quite well the bikeshed thingy. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Steele: Aha! We've finally got you talking jargon too! Stallman: What did he say? Steele: Bob just used canonical in the canonical way. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
On Sat, 2003-09-13 at 16:34, Alexander Leidinger wrote: On 13 Sep 2003 14:52:29 +0200 sebastian ssmoller [EMAIL PROTECTED] wrote: then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) board, NVidia GeForce2 grafic card (using nvidia native driver for x11), AMD Duron 750 MHz, 512 mb ram. everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. ps: the system i used to installed fbsd first is: AMD Duron 800 MHz, VIA VT8363/8365 [KT133/KM133] board, old SIS 8MB pci video card, 256 mb ram Is the system connected to a network, and if yes, does the network cards on both systems differ? If yes, have a look at the output of dmesg and try to find you network card. If you have it modify /etc/rc.conf (ifconfig_interface_name line). the system has two realtek network cards. both seem to work correctly - i've no connection problems - connection performance is ok. This sounds to me like a DNS problem, please check your default gateway (rc.conf: gateway line) too. dns seems to be ok. all requests are resolved correctly ... default gateway should not be the problem cause without ppp (dsl) this system is the default gw for the rest of the intranet and with ppp the default gw seems to be ok too. as mentioned: really bad performace occurs when lauching mozilla, gaim, gnome2, etc. ... when mozilla is running the perfomance seems to be ok ... possibly a bit too slow but i do not know how to proof this (?) i suppose a udma/disk/controller problem. i found out that the southbridge i use (VIA 82C686B) has some bugs. but in fbsd 5.0 release notes i found a bugfix for that so i am not sure about it ... thx regards, seb Bye, Alexander. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
On Sat, 2003-09-13 at 16:34, Alexander Leidinger wrote: On 13 Sep 2003 14:52:29 +0200 sebastian ssmoller [EMAIL PROTECTED] wrote: then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) board, NVidia GeForce2 grafic card (using nvidia native driver for x11), AMD Duron 750 MHz, 512 mb ram. everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. ps: the system i used to installed fbsd first is: AMD Duron 800 MHz, VIA VT8363/8365 [KT133/KM133] board, old SIS 8MB pci video card, 256 mb ram Is the system connected to a network, and if yes, does the network cards on both systems differ? If yes, have a look at the output of dmesg and try to find you network card. If you have it modify /etc/rc.conf (ifconfig_interface_name line). the system has two realtek network cards. both seem to work correctly - i've no connection problems - connection performance is ok. This sounds to me like a DNS problem, please check your default gateway (rc.conf: gateway line) too. dns seems to be ok. all requests are resolved correctly ... default gateway should not be the problem cause without ppp (dsl) this system is the default gw for the rest of the intranet and with ppp the default gw seems to be ok too. as mentioned: really bad performace occurs when lauching mozilla, gaim, gnome2, etc. ... when mozilla is running the perfomance seems to be ok ... possibly a bit too slow but i do not know how to proof this (?) i suppose a udma/disk/controller problem. i found out that the southbridge i use (VIA 82C686B) has some bugs. but in fbsd 5.0 release notes i found a bugfix for that so i am not sure about it ... thx regards, seb Bye, Alexander. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB da(4) quirks deprecated
On Sat, 13 Sep 2003, John-Mark Gurney wrote: Andrew Thompson wrote this message on Sat, Sep 13, 2003 at 16:33 +1200: I have just got around to trying this pen-drive again and have been trying tracking down data corruptions. If I mount the drive, write a file, umount/mount again the file is different. Using cmp I have found that there are consistent blocks of nulls in the written file where data should be. The block is always 0xfff bytes long and starts at 0x3000. I have tried many files and the offsets are always the same. All the other data in the file is correct and at the right location. 0x3000 - 0x3fff 0x7000 - 0x7fff 0xb000 - 0xbfff 0xf000 - 0x 0x13000 - 0x13fff ... and so on until the end of the file ... Any suggestions? This almost certainly has nothing to do with quirks. Is this on an ohci controller? I'm trying to track down mbr's problem also that appears to do the same thing. Have you tried doing an fstat before umounting the fs? I think you mean fsync? (There is a bug in msdosfs that doesn't sync the disk before unmount completes.) This is wierd in that it's the second page of the second transfer. The ohci can do up to 8k transfers in one TD, and then chain the TD's together if a larger block sized is used. Maybe you can provide him a patch that limits transfers to a single page as multi-page descriptors might be broken on his controller. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shared object libintl.so.4 not found
* Kevin Oberman [EMAIL PROTECTED] [030913 00:26]: From: Kris Kennaway [EMAIL PROTECTED] Please don't give bogus advice. The solution is to update everything that depends upon gettext, e.g. by using portupgrade. Maybe, but this bit me and the solution was to re-build gmake. The changes in what routines are in libc cause this problem. The reason you had to rebuild gmake is that it, too, depends on gettext. When the port was first built it linked against libintl.so.4. If you upgraded gettext w/out saving the old libraries (in /usr/local/lib/compat/pkg, if I remember right), the gmake broke. There are basically two ways to solve the problem: o As Kris (and others) have said since gettext was first upgraded, you should do this: portupgrade -rf gettext o Keep libintl.so.4 around somewhere, such as portupgrade's compatibility directory. Since libintl.so.4 is not part of the base system, only part of the ports tree, I'm not sure there's any need to warn anyone upgrading from 4.x - 5.x of anything. There's nothing special about gettext other than the fact that many ports, including GNU make, depend on it. Any other ports which install shared libraries are going to have the same issue, which is why portupgrade saves the old libraries for you to begin with. --Mike pgp0.pgp Description: PGP signature
Re: Bad performance
On Saturday 13 September 2003 18:05, sebastian ssmoller wrote: On Sat, 2003-09-13 at 16:34, Alexander Leidinger wrote: On 13 Sep 2003 14:52:29 +0200 sebastian ssmoller [EMAIL PROTECTED] wrote: then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) board, NVidia GeForce2 grafic card (using nvidia native driver for x11), AMD Duron 750 MHz, 512 mb ram. everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. ps: the system i used to installed fbsd first is: AMD Duron 800 MHz, VIA VT8363/8365 [KT133/KM133] board, old SIS 8MB pci video card, 256 mb ram Is the system connected to a network, and if yes, does the network cards on both systems differ? If yes, have a look at the output of dmesg and try to find you network card. If you have it modify /etc/rc.conf (ifconfig_interface_name line). the system has two realtek network cards. both seem to work correctly - i've no connection problems - connection performance is ok. This sounds to me like a DNS problem, please check your default gateway (rc.conf: gateway line) too. dns seems to be ok. all requests are resolved correctly ... default gateway should not be the problem cause without ppp (dsl) this system is the default gw for the rest of the intranet and with ppp the default gw seems to be ok too. as mentioned: really bad performace occurs when lauching mozilla, gaim, gnome2, etc. ... when mozilla is running the perfomance seems to be ok ... possibly a bit too slow but i do not know how to proof this (?) i suppose a udma/disk/controller problem. i found out that the southbridge i use (VIA 82C686B) has some bugs. but in fbsd 5.0 release notes i found a bugfix for that so i am not sure about it ... I have the same southbridge and a very fast system. That can't be the problem - and it really does sound like a network problem. It looks like it's looking for a host that it can't find. Possibly your own hostname. Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
I have the same southbridge and a very fast system. That can't be the problem - and it really does sound like a network problem. It looks like it's looking for a host that it can't find. Possibly your own hostname. I've seen a problem somewhat like that one if portmap/rpcbind is not running. Some software (most browsers, for example) hang at startup if it's not running or if they can't connect to it (firewall?). Fred -- It's really quite a simple choice: Life, Death, or Los Angeles. pgp0.pgp Description: PGP signature
Re: ACPI problems with this morning's -CURRENT
The post you reference shows the user with a kernel that has both APM and ACPI installed, apparently. This is not valid. Please report your kernel config. If GENERIC in 2003/9/6 booted fine with ACPI and then your rebuilt kernel from 2003/9/7 fails, it is almost certainly the devices you included. There were no ACPI-related commits in that timeframe. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
page fault while in kernel mode: AcpiNsMapHandleToNode + 0x20
Got today's (CVSup between 03:47 - 03:55 US/Pacific, 7 hrs. W of GMT) -CURRENT built on the laptop (i5000e) without incident -- after having built from similarly-updated source on my build machine without incident. On reboot, saw (hand-transcribed, so there may be transcription errors): ... Starting cron. Local package initialization:Setting the mixer vol from 75:75 to 25:25. apache (skipping ntop.sh, not executable)acpi_tz0: _AC1: temperature 73.8 = setpoint 73.8 Fatal trap 12: page fault while in kjernel mode fault virtual address = 0x88001fff fault code = supervisor read, page not present instruction pointer = 0x8:0xc068b460 stack pointer = 0x10:0xcd5a8bdc frame pointer = 0x10:0xcd5a8bdc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 prcessor eflags = interrupt enabled, resume, IOPL = 0 current process = 24 (acpi_thermal) kernel: type 12 trap, code=0 Stopped at AcpiNsMapHandleToNode+0x20: cmpb$0xaa,0(%edx) db tr AcpiNsMapHandleToNode(88001fff, 88001fff, cd5a8c04,c069ea0b,0) at AcpiNsMapHandleToNode+0x20 AcpiGetHandle(88001fff,c06a942c,cd5a8c5c,a,cd5a8c28,0,0) at AcpiGetHandle+0x4d acpi_pwr_switch_consumer(88001fff,0,cd5a8c5c,a,cd5a8ca8) at acpi_pwr_switch_consumer+0xf1 acpi_tz_switch_cooler_on(c2618ed0,c0ebb200,0,c0ebb200,1) at acpi_tz_switch_cooler_on+0x38 acpi_ForeachPAckageObject(c2618e40,c06a0400,c03bb200,49,8) at acpi_ForeachPAckageObject+0x3d acpi_tz_monitor(c0ebb200,0,cd5a8d08,c06a0986,c0ebb200) at acpi_tz_monitor+0x2ab acpi_tz_timeout(c0ebb200,cd5a8cfc,cd5a8d00,337,bb8) at acpi_tz_timeout+0x28 acpi_tz_thread(0,cd5a8d48,c04be5c3,314,1d368964) at acpi_tz_thread+0xc6 fork_exit(c06a08c0,0,cd5a8d48) at fork_exit+0xcf fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcd5a8d7c, ebp = 0 --- db I'm not too clear on what else would be useful here; I tried getting a panic dump, but that attempt yielded Fatal trap 3: breakpoint instruction fault while in kernel mode, and I need to actually use the laptop for some stuff I promised to deliver to someone this afternoon. FWIW, the previous few daily -CURRENT builds boots on the laptop have been without incident I have not modified anything with respect to ACPI, though I do have the tools to do so (as well as to dump what is there). Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] If you want true virus-protection for your PC, install a non-Microsoft OS on it. Plausible candidates include FreeBSD, Linux, NetBSD, OpenBSD, and Solaris (in alphabetical order). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ps: kvm_getprocs: No such file or directory
Hi I just updated my FreeBSD 5.1 system to HEAD, to see if the NFS problems had been fixed. I've done {build|install}world, built a new kernel (with my config from 5.1), and mergemaster -i. Running ps with the -a option produces this error: ps: kvm_getprocs: No such file or directory Have I done something wrong in the install? It doesn't say which file it can't open. :| Thanks for your time. :) Cheers, Jay -- http://www.evilrealms.net/ - Systems Administrator Developer http://www.ic.ac.uk/ - Imperial College, 2nd year CS student ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ps: kvm_getprocs: No such file or directory
On Sat, Sep 13, 2003 at 08:42:42PM +0100, Jay Cornwall wrote: Hi I just updated my FreeBSD 5.1 system to HEAD, to see if the NFS problems had been fixed. I've done {build|install}world, built a new kernel (with my config from 5.1), and mergemaster -i. Running ps with the -a option produces this error: ps: kvm_getprocs: No such file or directory Have I done something wrong in the install? It doesn't say which file it can't open. :| Thanks for your time. :) If you did it exactly like you describe, then you forgot to install and boot with the new kernel. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: Bad performance
as mentioned: really bad performace occurs when lauching mozilla, gaim, gnome2, etc. ... when mozilla is running the perfomance seems to be ok ... possibly a bit too slow but i do not know how to proof this (?) i suppose a udma/disk/controller problem. i found out that the southbridge i use (VIA 82C686B) has some bugs. but in fbsd 5.0 release notes i found a bugfix for that so i am not sure about it ... I have the same southbridge and a very fast system. That can't be the problem do u have enabled/disabled anything special ? (kernel, io, net, ...) I have all debugging options in the kernel disabled, and I have a non-debugging malloc (ln -s aj /etc/malloc.conf), but this is disabled by default on 5.1-RELEASE I think (are you running -RELEASE or -CURRENT?). - and it really does sound like a network problem. It looks like it's looking for a host that it can't find. Possibly your own hostname. ok. but what i do not understand is that when i do some tests manually everything seems to be ok (e.g. ping). any ideas what i may test to figure out whether it is network problem or not ? btw. i did a simple io test: (ufs2 softupdates) time dd if=/dev/zero of=./out bs=1024k count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 20.389193 secs (13165575 bytes/sec) real0m20.401s user0m0.000s sys 0m6.732s For the record, this is my output: 256+0 records in 256+0 records out 268435456 bytes transferred in 7.681891 secs (34943929 bytes/sec) dd if=/dev/zero of=./out bs=1024k count=256 0.00s user 3.66s system 47% cpu 7.772 total OK, so it's a little more than twice as fast, but I probably have a faster machine and a faster hard drive. This seems to me like it has nothing to do with the ultra-long startup times in GNOME. I've seen them before, and they were all related to network issues. Maybe you can try writing a small C program that does a gethostbyname on the output of gethostname and a gethostbyaddr on the output of gethostbyname and see if it works. when i did this under linux it finished in no time. i do not know whether that has to say anything but i found that rather interesting. They probably have different ways to write zeroes :). Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ps: kvm_getprocs: No such file or directory
Ruslan Ermilov wrote: If you did it exactly like you describe, then you forgot to install and boot with the new kernel. Oh. *blushes* :) I can't believe I forgot to do 'make install'. Thanks Rus. ;) -- Cheers, Jay http://www.evilrealms.net/ - Systems Administrator Developer http://www.ic.ac.uk/ - Imperial College, 2nd year CS student ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
mystery kernel spew
Howdy list, For some time now I've have an issue with a dell laptop I use. It spews a bunch of kernel junk after init is spawned, and the spew causes my dmesg to become too full to actually produce a file I can send to the list that is meaningfull. But I'm tired of the spew, so I've decided to proved the info I have at hand. Hopefully somebody will understand what the mystery kernel spew is and give me a clue. Later on I'll see if I can do the old ctrl+alt+esc debuger trick while it spews to get a backtrace thingy. In the mean time does anybody know how to increase the buffer used by dmesg so I can have it include the entire kerenel output? Thanks in advance =) __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| [EMAIL PROTECTED] http://wifibsd.org dmesg.boot Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
i guess portmapper is not runing. whats the name of the rc.d script on fbsd ? i looked for portmap (as under linux) but haven't found in /etc/rc.d ... If you're running 4.x, it's portmap. If it's 5.x, it's rpcbind. To have it loaded at boot-time, just put rpcbind_enable=YES into your /etc/rc.conf. other question: is there a good/realistic benchmark wich i could use so we could check/compare whether the system is really that slow or not ? I haven't used any benchmarking tools, but there's a whole category on this under the ports-tree (ports/benchmarks/). Maybe someone else with experience with it can point out something specific for you. Fred -- If all men were brothers, would you let one marry your sister? pgp0.pgp Description: PGP signature
Re: devd/devctl
On Sat, 13 Sep 2003, M. Warner Losh wrote: Yes. that has been the plan for some time now. However, dhclient is really lame in a lot of ways. Martin Blapp has made it a lot better of lates. In geral, I tend to believe that I shouldn't fix bugs in dhclient with devd things. However, a more general trend to more event types would be good because a device arriving isn't quite the same as a network interface arriving... In dhclient's defense, it's really designed to provide functionality on a wide variety of platforms, with a wide variety of dhcpd's, so it has issues. I think Martin did a good job of defining an improvement that applies to all/most platforms (only try to broadcast if we have link). That functionality is being ported back to the vendor, if it hasn't been already. If we want really cool whizbang features that are more specific to us, we _should_ be looking at stuff like devd. The trick is definig which problem space we're addressing at any given moment. :) Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd/devctl
In message: [EMAIL PROTECTED] Doug Barton [EMAIL PROTECTED] writes: : That functionality is being ported back to the vendor, if it hasn't been : already. If we want really cool whizbang features that are more specific : to us, we _should_ be looking at stuff like devd. The trick is definig : which problem space we're addressing at any given moment. :) You can't do it in devd. You must be able to either (a) tell a running dhclient about arrival/departures of interfaces or (b) run multiple dhclients. Make dhclient do one or the other. devd can't help you here until one or the other of these work. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi_cd or atapicam crash in current.
Hello, here camcontrol still shows bogus numbers when there's no CD: #camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 -791621424 -791621424 No boot crashes, though, only the usual ones due to cdrecord usage which nobody seem to care about :-( On Fri, 12 Sep 2003, Kenneth D. Merry wrote: What happens when you do: camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 That should give you the media size and blocksize of the CD in the drive, or an error if you don't have any media. If you're getting bogus values for the media/blocksize, or if it says there's a disk there when there isn't one, then you've got a problem either with the ATAPI or atapicam code. Ken Regards, Vladimir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd/devctl
On Sat, 13 Sep 2003, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Doug Barton [EMAIL PROTECTED] writes: : That functionality is being ported back to the vendor, if it hasn't been : already. If we want really cool whizbang features that are more specific : to us, we _should_ be looking at stuff like devd. The trick is definig : which problem space we're addressing at any given moment. :) You can't do it in devd. You must be able to either (a) tell a running dhclient about arrival/departures of interfaces Ok, maybe I misunderstand, but wouldn't _this_ be the right thing for devd to do? In other words, devd should be able to notice this, and devd.conf should be able to define what I want to do with this like sending a signal to dhclient. Then we can move to the dhclient problem space, and define behavior in dhclient that says when X happens, I need to do Y. One way to do this would be to define multiple interfaces in dhclient.conf, and add an optional flag to each interface stanza. Then when dhclient receives a signal, it rescans the list of interfaces it knows about looking for link. This is just a conceptual example of course, other solutions might well be possible. or (b) run multiple dhclients. This is evil, and basically undoable with the current state of things, but it might be possible down the road, although I still think it's evil for other reasons. Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi_cd or atapicam crash in current.
On Sun, 14 Sep 2003, Vladimir Kushnir wrote: Hello, here camcontrol still shows bogus numbers when there's no CD: #camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 -791621424 -791621424 No boot crashes, though, only the usual ones due to cdrecord usage which nobody seem to care about :-( I too have problems similar to this. On one box, the kernel panics (see message posted Sep 10, subject Panic with ATAng + atapicam). With or without atapicam, a CD is detected as being present when it is not. On another box (Dell Inspiron 4150 laptop), an atapicam kernel doesn't crash, but I still get the same bogus CD detection: ad0: 28615MB FUJITSU MHS2030AT [58140/16/63] at ata0-master UDMA100 acd0: CDRW HL-DT-STCD-RW/DVD-ROM GCC-4240N at ata1-master UDMA33 cd0 at ata1 bus 0 target 0 lun 0 cd0: HL-DT-ST RW/DVD GCC-4240N D110 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [3737169375 x 3737169374 byte records] I also get the 15-20 second delay which other folks started to see. camcontrol on this box gives the same results that you have: # camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 -791621424 -791621424 I think it is the ATAPI code; removing atapicam from the kernel still shows false CD detection. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
On Sat, Sep 13, 2003 at 02:52:29PM +0200, sebastian ssmoller wrote: then i moved the disk from the hardware used during install into the production environment which includes VIA 82C8363 (Apollo KT133A) ... everything worked fine again. BUT: launching gdm needs a lot of time, same for gnome2. when i start moz-firebird i am unabled to use it for minutes (!) until it reacts on user events (typing inet adress into address bar), same for gaim. I agree with the general concensus that this shows all the symptoms of a network or DNS problem - though the switch from SIS to nVidia may have disturbed X. Did you change any system configuration (hostname etc) when you moved the disk? Is the 'production' environment identical network-wise to your test environment? Have you re-configured X to use the different video card? How are you starting gdm, gnome2 etc? I gather gdm isn't started via /etc/ttys but manually from a vty. I presume you are using gdm to start X. Can you log in from a second system? If so, what is happening during the startup delay? Does top show the system is very heavily loaded or doing nothing (all processes waiting)? Before you start gdm, can you ping your system by hostname? Are there any other hostname mentioned in your gdm configuration file? Can you ping them all? Have you checked your /etc/nsswitch.conf and /etc/resolv.conf? Is the output from 'ifconfig -a' and 'netstat -r' correct? Have a look through all the files in /var/log that have been updated recently and check for errors - especially XFree86.0.log, daemon and messages. Have a look in the gdm log file (I'm not sure where this is by default). Are there any messages on either the console or vty from which you started gdm? (Use Ctrl-Alt-Fn to get from X to vtyn and then Alt-Fn to switch between vtys. You can use ScrollLock and PgUp/PgDn/Up/Down to scroll back. Press ScrollLock again to get back to normal). Is any part of your system NFS-mounted? Is X using a fontserver? Are all these servers responding? Are you running a GENERIC or custom kernel? Do you have any firewall functions enabled? Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd/devctl
In message: [EMAIL PROTECTED] Doug Barton [EMAIL PROTECTED] writes: : On Sat, 13 Sep 2003, M. Warner Losh wrote: : : In message: [EMAIL PROTECTED] : Doug Barton [EMAIL PROTECTED] writes: : : That functionality is being ported back to the vendor, if it hasn't been : : already. If we want really cool whizbang features that are more specific : : to us, we _should_ be looking at stuff like devd. The trick is definig : : which problem space we're addressing at any given moment. :) : : You can't do it in devd. You must be able to either (a) tell a : running dhclient about arrival/departures of interfaces : : Ok, maybe I misunderstand, but wouldn't _this_ be the right thing for : devd to do? In other words, devd should be able to notice this, and : devd.conf should be able to define what I want to do with this like : sending a signal to dhclient. Then we can move to the dhclient problem : space, and define behavior in dhclient that says when X happens, I need : to do Y. You misundestand. devd *CANNOT* do this. I have a laptop that has a builtin rl0 interface. I plug in a wi0 interface. somehow we gotta deal. and you cannot tell dhclient that interfaces have arrived. : or (b) run multiple dhclients. : : This is evil, and basically undoable with the current state of things, : but it might be possible down the road, although I still think it's evil : for other reasons. why is this evil? dhclient can and does run on mulitple interfaces. it fails now because it specifically precludes it, but for no other good reasons. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd/devctl
On Sat, 2003-09-13 at 18:49, M. Warner Losh wrote: and you cannot tell dhclient that interfaces have arrived. dhclient(8) seems to think otherwise, although it doesn't explain quite how (I assume it wants you to pause and resume via OMAPI/omshell(8) since it doesn't appear to support interface objects according to the documentation). -- brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED] system administrator [WAY too many hats][EMAIL PROTECTED] electrical and computer engineering, carnegie mellon univ. KF8NH URGENT! E-xpedient nuked APK subdomains; kf8nh.apk.net is DEAD. Sorry. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
SOS: ATAng: Broke my ATA (ICH3).
I have a ICH3 controller, and a 9/9 kernel works just fine, but a today kernel hangs(!) after printing ata0: [MPSAFE] Here is the GOOD dmesg: $ dmesg|grep ata atapci0: Intel ICH3 UDMA100 controller port 0x1c20-0x1c2f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xe010-0xe01003ff at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 57231MB FUJITSU MHS2060AT [116280/16/63] at ata0-master UDMA100 acd0: CDRW SONY CD-RW CRX800E at ata1-master WDMA2 cd0 at ata1 bus 0 target 0 lun 0 $ Any ideas? LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: page fault while in kernel mode: AcpiNsMapHandleToNode + 0x20
Your backtrace shows that your acpi_tz_monitor() thread is hitting an invalid pointer. It would be interesting to see what package that is (i.e. the _ALx values). Please send a URL to the output of: acpidump -t -d -o david.dsdt david.asl -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SOS: ATAng: Broke my ATA (ICH3).
--On Saturday, September 13, 2003 18:09:21 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: I have a ICH3 controller, and a 9/9 kernel works just fine, but a today kernel hangs(!) after printing ata0: [MPSAFE] Here is the GOOD dmesg: $ dmesg|grep ata atapci0: Intel ICH3 UDMA100 controller port 0x1c20-0x1c2f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xe010-0xe01003ff at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 57231MB FUJITSU MHS2060AT [116280/16/63] at ata0-master UDMA100 acd0: CDRW SONY CD-RW CRX800E at ata1-master WDMA2 cd0 at ata1 bus 0 target 0 lun 0 $ Any ideas? LER For the record, I also pulled atapicam out of the kernel, and the same thing happens. Where to, folks? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: ATAng suspend/resume support broken
On Mon, 1 Sep 2003, Soren Schmidt wrote: It seems Nate Lawson wrote: This worked with old ATA. For now I've supped sys/dev/ata back to 2003/8/23. Ideas? Not really, it does work on my laptop hmm.. I'll try to get it onto a few other laptops at work, see if I can reproduce the problem.. I cvsupped to the 2003/9/13 (today) and built a kernel. It still has some problems: 1. Panic on uninitialized FD data fixed, thank you 2. Resume still fails/hangs with the drive light on. 3. Message on console when rebooting that ata slave missed interrupt Dmesg is below: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sat Sep 13 16:01:05 PDT 2003 [EMAIL PROTECTED]:/home/nate/src/sys/i386/compile/LAPTOP Preloaded elf kernel /boot/kernel.bad/kernel at 0xc04bc000. Preloaded elf module /boot/kernel.bad/acpi.ko at 0xc04bc27c. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz (999.16-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 402063360 (383 MB) avail memory = 385294336 (367 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IBMTP-1Aon motherboard acpi_ec0: embedded controller: ECDT, GPE 0x1c, GLK port 0x66,0x62 on acpi0 pcibios: BIOS version 2.10 Using $PIR table, 14 entries at 0xc00fdeb0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_ec0: info: new max delay is 35 us acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTB is routed to irq 11 pcib0: slot 29 INTC is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1800-0x181f irq 11 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x1820-0x183f irq 11 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x1840-0x185f irq 11 at device 29.2 on pci0 usb2: Intel 82801CA/CAM (ICH3) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib2: slot 0 INTA is routed to irq 11 pcib2: slot 0 INTB is routed to irq 11 pcib2: slot 2 INTA is routed to irq 11 pcib2: slot 8 INTA is routed to irq 11 cbb0: TI1420 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb0: [MPSAFE] cbb1: TI1420 PCI-CardBus Bridge mem 0x5100-0x51000fff irq 11 at device 0.1 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 cbb1: [MPSAFE] pci2: simple comms at device 2.0 (no driver attached) pci2: network, ethernet at device 8.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 UDMA100 controller port 0x1860-0x186f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ichsmb0: Intel 82801CA (ICH3) SMBus controller port 0x1880-0x189f irq 11 at device 31.3 on pci0 smbus0: System Management Bus on ichsmb0 pci0: multimedia, audio at device 31.5 (no driver attached) atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x378-0x37f irq 7 on
Re: page fault while in kernel mode: AcpiNsMapHandleToNode + 0x20
Date: Sat, 13 Sep 2003 16:26:58 -0700 (PDT) From: Nate Lawson [EMAIL PROTECTED] To: David Wolfskill [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: page fault while in kernel mode: AcpiNsMapHandleToNode + 0x20 Your backtrace shows that your acpi_tz_monitor() thread is hitting an invalid pointer. That doesn't sound especially auspicious. :-} It would be interesting to see what package that is (i.e. the _ALx values). Please send a URL to the output of: acpidump -t -d -o david.dsdt david.asl OK; they're in http://www.catwhisker.org/~david/FreeBSD/debug; I've (finally!) enabled indexing on that directory, so folks can see what's available. In addition to the output from acpidump, I've provided a copy of the kernel config file (LAPTOP_30W). The acpidump output may be accessed either as david.* (per above) or i5000e.* -- they're hard links. Regarding acpidump: when I tried running it under (today's) -STABLE, it whined about the -t and -d flags, so I booted up today's -CURRENT, but given my experience this morning, I kept it in single-user mode, which seems to have worked OK. Running the same acpidump binary (which had been built under -STABLE), the -t and -d flags were accepted. I also have available the output from acpidump from 05 Oct 2002 (on the same machine, but evidently with an earlier version of acpidump). If that's wanted, please let me know. Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] If you want true virus-protection for your PC, install a non-Microsoft OS on it. Plausible candidates include FreeBSD, Linux, NetBSD, OpenBSD, and Solaris (in alphabetical order). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd/devctl
On Sat, Sep 13, 2003 at 06:59:21PM -0400, Brandon S. Allbery KF8NH wrote: On Sat, 2003-09-13 at 18:49, M. Warner Losh wrote: and you cannot tell dhclient that interfaces have arrived. One way for it to tell that this has happened automatically is to get it to listen on a PF_ROUTE socket and check periodically for RTM_IFINFO messages. On another note, if I can sit down and play with it I may be able to get rid of the requirement for BPF from our port/import of isc-dhcp. IP_ONESBCAST means it shouldn't need to use raw sockets or BPF to transmit an undirected broadcast datagram. IP_RECVIFADDR/IP_SENDSRCADDR means it shouldn't need a socket per interface. BMS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATAng ate my hampster...
Hiya, I recently upgraded my -current box, only to have my Serial ATA device move from ar0 to ad6, making things cry. Here's the relevant information currently in dmesg, my main concern is not the name change, but more the reporting of the disk as UDMA133, which it clearly isn't! Soren, if I can give you any more useful information, please let me know. atapci0: Promise PDC20376 SATA150 controller port 0xcc00-0xcc7f,0xc800-0xc80f, 0xc400-0xc43f mem 0xee00-0xee01,0xee02-0xee020fff irq 11 at device 1 1.0 on pci1 atapci0: [MPSAFE] ata2: at 0xee02 on atapci0 ata2: [MPSAFE] ata3: at 0xee02 on atapci0 ata3: [MPSAFE] ata4: at 0xee02 on atapci0 ata4: [MPSAFE] atapci1: nVidia nForce2 UDMA133 controller port 0xf000-0xf00f at device 9.0 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci1 ata1: [MPSAFE] GEOM: create disk ad6 dp=0xc625b570 ad6: 76319MB ST380023AS [155061/16/63] at ata3-master UDMA133 -- [+CrtxReavr] ashp, some supposedly skilled unix developer where I work hosed a box (Solaris for Intel) by doing a 'chmod -R 447 /etc'. [+CrtxReavr]: When I confronted him about he he claimed that Intel architecture was 'little-endian.' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB da(4) quirks deprecated
Nate Lawson wrote: On Sat, 13 Sep 2003, John-Mark Gurney wrote: Andrew Thompson wrote this message on Sat, Sep 13, 2003 at 16:33 +1200: I have just got around to trying this pen-drive again and have been trying tracking down data corruptions. If I mount the drive, write a file, umount/mount again the file is different. Is this on an ohci controller? Yes, on a Compaq N1000v laptop (nothing but trouble) usb0: OHCI version 1.0, legacy support usb0: NEC uPD 9210 USB controller on ohci0 usb0: USB revision 1.0 This is wierd in that it's the second page of the second transfer. The ohci can do up to 8k transfers in one TD, and then chain the TD's together if a larger block sized is used. Maybe you can provide him a patch that limits transfers to a single page as multi-page descriptors might be broken on his controller. I have now tried the unit on my desktop at home and it works perfect, no corruptions. It seems to be related to my laptop usb controller as Nate suggests. Andy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'cd /usr/src/etc; make distribute' broken.
At Fri, 12 Sep 2003 20:01:36 + (UTC), Kris Kennaway wrote: This used to work fine, but now it is dying with the following: install -o root -g wheel -m 644 /a/asami/portbuild/amd64/5/src/etc/sendmail/freebsd.mc /a/asami/portbuild/amd64/5/src/etc/sendmail/freebsd.cf //var/chroot/etc/mail install: /a/asami/portbuild/amd64/5/src/etc/sendmail/freebsd.cf: No such file or directory *** Error code 71 Stop in /a/asami/portbuild/amd64/5/src/etc/sendmail. *** Error code 1 Indeed, freebsd.cf does not appear to be built anywhere. Does anyone know what is going on? Hmm, on my environment, freebsd.cf is built correctly. Is there freebsd.submit.cf in the same directory? -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA problems(unlean fs) on recent cvsup
Hello list, I've recently cvsup'd current (14th of Sep). After a build and install world/kernel I rebooted to find some new and interesting kernel messages about ata? MPSAFE. Well as the booting continued I notcied the machine was going through more disk activity then usal. It was also taking alot longer to actully start. Eventully the kernel dropped into single user mode. It appears my filesystem is playing up for some reason. I haven't had any power failures for random hangs/reboots. After the recent cvsup my /usr fs appears to be coruppt or something. In single user mode I'm unable fix the problem with fsck. At first when I had softupdates /usr fsck would give me messages like UNEXPECTED SOFT UPDATE INCONSISTENCY I turned of softupate to see if it would help...it didn't. I still can't fix the fs. I get output like CANNOT WRITE BLK: xxx and I'm always unable to salvage blks and what not. Anyway my dmesg is as follows: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sun Sep 14 12:59:35 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel.GENERIC/kernel at 0xc076. Preloaded elf module /boot/modules/acpi.ko at 0xc076024c. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 536854528 (511 MB) avail memory = 513466368 (489 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4S8Xon motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 agp0: SiS 648 host to AGP bridge mem 0xe000-0xe7ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 fwohci0: vendor=1039, dev=7007 fwohci0: 1394 Open Host Controller Interface mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 if_fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0a:83:4c sbp0: SBP2/SCSI over firewire on firewire0 fwohci0: Initiate bus reset atapci0: SiS 963 UDMA133 controller port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: multimedia, audio at device 2.7 (no driver attached) ohci0: SiS 5571 USB controller mem 0xde00-0xde000fff irq 9 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/2.42, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. ohci1: SiS 5571 USB controller mem 0xdd80-0xdd800fff irq 9 at device 3.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: SiS 5571 USB controller on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ohci2: SiS 5571 USB controller mem 0xdd00-0xdd000fff irq 9 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: SiS 5571 USB controller on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 3.3 (no driver attached) pci0: multimedia, audio at device 9.0 (no driver attached) pci0: input device at device 9.1 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0x8800-0x88ff