Re: cd writer recommendation?
At 07:42 PM 08/17/1999 -0400, Kevin S. Brackett wrote: >Oh, well then, :) I'm glad I said something before I actually bought one >(I saw the atapi RW drives were rather cheap now (~US$125)) Computergeeks has a Phillips Model: CDD-3600 2x2x6 SCSI CD-RW Kit for $139 http://www.compgeeks.com/cgi-bin/details.asp?cat=MultiMedia&sku=205-2620 Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current Kernel build broken
With current source tree as of 9 am pacific, I can no longer build a kernel : cc -c -O2 -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_glob al.h -elf ../../dev/dpt/dpt_scsi.c ../../dev/dpt/dpt_scsi.c: In function `dpt_get_conf': ../../dev/dpt/dpt_scsi.c:389: warning: cast discards `volatile' from pointer tar get type ../../dev/dpt/dpt_scsi.c: In function `dpt_detect_cache': ../../dev/dpt/dpt_scsi.c:496: warning: cast discards `volatile' from pointer tar get type ../../dev/dpt/dpt_scsi.c: In function `dpt_init': ../../dev/dpt/dpt_scsi.c:1187: warning: cast discards `volatile' from pointer ta rget type ../../dev/dpt/dpt_scsi.c: In function `dpt_attach': ../../dev/dpt/dpt_scsi.c:1410: warning: implicit declaration of function `EVENTH ANDLER_REGISTER' ../../dev/dpt/dpt_scsi.c:1410: `shutdown_final' undeclared (first use in this fu nction) ../../dev/dpt/dpt_scsi.c:1410: (Each undeclared identifier is reported only once ../../dev/dpt/dpt_scsi.c:1410: for each function it appears in.) ../../dev/dpt/dpt_scsi.c:1411: `SHUTDOWN_PRI_DEFAULT' undeclared (first use in t his function) *** Error code 1 Stop in /usr/src/sys/compile/pro2. = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Newpcm is broken again for mpg123 (ESS 1868 isa sound card)
At 04:52 AM 1/1/00 +, Cameron Grant wrote: > > Donn> "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS > > Donn> 1868, of course. Well, I (wisely) saved my old kernel as > > Donn> /kernel.good and just booted into that. > > > > Donn> Could you also say what was fixed if you get around to it? I'd > > Donn> to learn a little more about the sound driver. > > > The following things were in the recent mail of mine: > > > > - All ioctl(2)s go to see the secondary buffer(if I have forget nothing). > > - chn_setblocksize() changes the size of the secondary buffer. > > - chn_mmap() maps the secondary buffer. > > - chn_poll() invokes DMA. > > - chn_wrintr() performs DMA emulation for pcm devices with no DMA > > functionality(requested by nyan). > > - SNDCTL_DSP_SETFRAGMENT handles the count correctly. > > - GETI/OSPACE returns the number of fragments. > > - DMA transfer keeps running upon underrun. Some DSPs seem to end up > > with an unpredictable result if the DMA gets stopped followed by > > immediate restart. This revokes the change in >sys/dev/sound/pcm/channel.c > > rev 1.12. > > - chn_write() and chn_read() returns EAGAIN for nonblocking if there > > are no space to write or data to read. > >the ess problem was a result of me reducing the buffer size to 8k instead of >64k to see what would happen. only ess cards seem to have problems, so it's >back to 64k for them but 8k for other isa cards. > > - cameron I have the same problem with a motherboard with built in Crystal Audio : pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x120-0x127 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 It works fine with revision 1.14 of channel.c and 1.12 of dsp.c and the corresponding header files. The new versions break sound. Example using the rsynth port With old version #say happy new year I get "happy new year" out of spaekers With new version : #say happy new year all that comes out of speakers is "happy" Also other problems occur with new version when playing au files. Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
At 08:20 PM 1/2/00 -0800, David Greenman wrote: > >He is just expressing his point. From what I can tell someone removed him > >from the list with no reason and now he is angry. I probably would be too. > >That is not at all what happend. Karl went off the deep end about phk >recommending a Motorola GPS to do timekeeping. Then, after a pile of >insulting messages from Karl, Karl made an accusation that someone removed >him from three of the mailing lists. For at least two of those lists, he >was simply wrong. For the third (freebsd-current), there is no evidence >to support his claim. > > >Also, I can tell that someone is doing some good covering up. Its ashame to > >see leaders do this. > >How can you tell that? There is no evidence to support that. *I'm* >certainly not covering anything up and I've seen no reason to believe that >anyone else is, either. > >-DG PLEASE STOP THIS There are things that need fixing and this is going nowhere. You are all very talented people. Enough Enough Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: isa_dmastart: bad bounce buffer
At 03:08 AM 1/5/00 +, Cameron Grant wrote: >the panics should be fixed now with sb.c rev 1.47, mss.c rev 1.43. > > - cameron > Cameron The panics are stopped But any sound out of speakers is truncated. If I try to play a au file it just repeats the first part of it over and over. The sound card is a built in Crystal Audio on a Intel PR440FX mother board. Here is the dmesg output: pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 bus_dmamap_load: Too many segs! buf_len = 0xdf00 bus_dmamap_load: Too many segs! buf_len = 0xdf00 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x120-0x127 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 The sound worked fine on a kernel built with sources current as of 12/28/1999 Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: isa_dmastart: bad bounce buffer
At 04:05 AM 1/5/00 +, Cameron Grant wrote: > > bus_dmamap_load: Too many segs! buf_len = 0xdf00 > > bus_dmamap_load: Too many segs! buf_len = 0xdf00 > >argh, forgot something. try mss.c rev 1.44, sb.c rev 1.48. > > - cameron Now the au files play great !!! there is still something amiss with /usr/ports/audio/rsynth #say hello world comes out as "hel" this might be a problem with the port although it worked last week Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: hak.lan.Awfulhak.org daily run output
At 10:23 AM 1/8/00 -0800, David O'Brien wrote: >On Fri, Jan 07, 2000 at 08:32:19AM +, Brian Somers wrote: > > Anyone know what's changed with `calendar' ? I suspect it's the > > recent cpp changes. > >Please test this patch. I was having the same problem and the patch worked for me Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile
At 12:50 PM 1/17/00 -0800, Kris Kennaway wrote: >On Mon, 17 Jan 2000, Jim Bloom wrote: > > > Add lynx-ssl to the list of ports which are broken on current. This was > > as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make > > world. > >Well, that makes a list of one. Can you provide more information (e.g. a >transcript?) Are you using openssl-rsaref, or openssl with no RSA (the >latter will break many ports, the former has a restrictive license). > >Kris Here is another one apache13-php3 when compiled with modssl . I'm using RSA. It builds and installs fine but when starting the server with ssl : #apachectl startssl the following error occurs : Syntax error on line 240 of /usr/local/etc/apache/apache.conf: Cannot load /usr/local/libexec/apache/libssl.so into server: /usr/lib/libcrypto.so.1: Undefined symbol "R_RandomUpdate" /usr/local/sbin/apachectl startssl: httpd could not be started It can be fixed by adding -L/usr/local/lib -lrsaref to the SSL_LIBS= line in /usr/ports/www/apache13-php3/work/apache_1.3.9/src/modules/ssl/Makefile Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new nexus.c breaks kernel build
The new version of nexus.c (1.23) breaks current kernel build : cc -c -O2 -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/nexus.c ../../i386/i386/nexus.c: In function `nexus_deactivate_resource': ../../i386/i386/nexus.c:341: `rv' undeclared (first use in this function) ../../i386/i386/nexus.c:341: (Each undeclared identifier is reported only once ../../i386/i386/nexus.c:341: for each function it appears in.) ../../i386/i386/nexus.c:345: warning: passing arg 1 of `pmap_unmapdev' makes integer from pointer without a cast *** Error code 1 Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loader.rc: unknown command
At 02:50 PM 1/30/00 +0900, Daniel C. Sobral wrote: >Jean-Marc Zucconi wrote: > > > > With a new installed world I get this message at boot: > > > > > \ Loader.rc > > Loader.rc: unknown command > > > > Fortunately this does not prevent the machine to boot :-) > > Any clue? > >The \ command is not working correctly, resulting in the "Loader.rc" >comment being executed instead of ignored. > >Why? I don't have a clue. Is *ANYONE* being able to reproduce this >problem? If so, please contact me ASAP, since we have almost no time to >fix this before 4.0-RELEASE. > >Jean, I need more information about your setup. What was it running >before? How did you install this new world? Did you ever touch any file >in /boot? Can you give me a date of your world source? I'm seeing the same thing here with current world build as of a few minutes ago. I blew away /boot/* and reinstalled fresh still the same Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Will the real libcrypto please stand up?
At 02:20 PM 2/3/00 -0500, bush doctor wrote: >I'm a bit confused about the libcrypto situation and need some >clarification :) >I'm running -current and rebuilt the apache13-php3 port recently. The port >depends on /usr/local/lib/libcrypto.so.1, however when starting the ssl >version >I get the following: > >ikhala.tcimet.net:root> apachectl startssl >Syntax error on line 240 of /usr/local/etc/apache/apache.conf: >Cannot load /usr/local/libexec/apache/libssl.so into server: >/usr/lib/libcrypto.so.1: Undefined symbol "ERR_load_RSAREF_strings" >/usr/local/sbin/apachectl startssl: httpd could not be started > >My question is simply what is the "correct" fix so all apps needing libcrypto >will find the one it needs? Should there be only one? I know I'm missing >something simple. > >Thanxs I had to add -L/usr/local/lib -lrsaref -lRSAglue to the SSL_LIBS= line of /usr/ports/www/apache13-php3/work/apache_1.3.11/src/modules/ssl/Makefile then it works fine. Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mod_ssl & current
At 12:00 PM 2/29/2000 -0800, Sean-Paul Rees wrote: >I'm having a problem getting Apache setup to work with modssl; I'm running >apache1.3.12+php4+mod_ssl2.6.0 > >[root@valiant]-~# apachectl startssl >/usr/local/sbin/apachectl startssl: httpd could not be started > >No other info whatsoever. (helpful, huh? :-) > >I'm using the stock configuration file with just hostname changes throughout. > >Any ideas? I'm running current from 2/26/2000. > >-- >Cheers, >Sean I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile and install the recompiled libssl.so in /usr/local/libexec/apache. Works fine Note this is for the apache13-php3 port but I bet it will work for the apache13-php4 port Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mod_ssl & current
At 07:56 PM 2/29/2000 -0800, you wrote: >On Tue, 29 Feb 2000, Manfred Antar wrote: > > > I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in > > /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile > > and install the recompiled libssl.so in /usr/local/libexec/apache. > > Works fine > > Note this is for the apache13-php3 port but I bet it will work for the >apache13-php4 port > >This may work, but I doubt this is necessary. -lRSAglue is an empty >library which only exists to keep legacy ports happy, and -lrsaUSA will be >automatically dlopen()ed if you have a recent libcrypto.so. > >As with the other guy, please make sure your libcrypto.so is up to date - >I haven't seen evidence from either of you yet that this is the case :-) > >Kris My world is built and installed 5 hours ago and ls -l /usr/lib/libcrypt* -r--r--r-- 1 root wheel 1088060 Feb 29 17:22 libcrypto.a lrwxr-xr-x 1 root wheel 14 Feb 29 17:22 libcrypto.so@ -> libcrypto.so.1 -r--r--r-- 1 root wheel 651156 Feb 29 17:22 libcrypto.so.1 The only reason I added -lRSAglue is awhile back before openssl was imported you needed that to get the modssl to work I'll try it without it and see if it works Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mod_ssl & current
At 07:56 PM 2/29/2000 -0800, Kris Kennaway wrote: >On Tue, 29 Feb 2000, Manfred Antar wrote: > > > I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in > > /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile > > and install the recompiled libssl.so in /usr/local/libexec/apache. > > Works fine > > Note this is for the apache13-php3 port but I bet it will work for the >apache13-php4 port > >This may work, but I doubt this is necessary. -lRSAglue is an empty >library which only exists to keep legacy ports happy, and -lrsaUSA will be >automatically dlopen()ed if you have a recent libcrypto.so. > >As with the other guy, please make sure your libcrypto.so is up to date - >I haven't seen evidence from either of you yet that this is the case :-) > >Kris Kris it works with just -lrsaUSA added : Without -lrsaUSA : (/root)502}apachectl startssl /usr/local/sbin/apachectl startssl: httpd could not be started With -lrsaUSA : (/root)503}apachectl startssl Apache/1.3.12 mod_ssl/2.6.1 (Pass Phrase Dialog) Some of your private key files are encrypted for security reasons. In order to read them you have to provide us with the pass phrases. Server pozo.com:443 (RSA) Enter pass phrase: Ok: Pass Phrase Dialog successful. /usr/local/sbin/apachectl startssl: httpd started I'll do another make world and try it again without Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: another newpcm casualty
I'm having a similar problem with the newpcm stuff. I have a Intel PR440FX motherboard with builtin sound (Crystal Sound System) It worked fine until the recent changes in pnp. I can get it to work with the Voxware drivers no problem. Here is the relevant part of my kernel config : controller pnp0 device pcm0 at isa? port ? irq 5 flags 0x03 Here is part of dmesg : pcm0: at irq 5 flags 0x3 on isa0 unknown0: on isa0 pcm1: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown1: at port 0x200-0x207 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 Some how it's being recognized as a SoundBlaster card and it's not. Here is pnpinfo : Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CSC0b36 (0x360b630e), Serial Number 0x PnP Version 1.0, Vendor Version 1 Device Description: CS4236 Audio Logical Device ID: CSC 0x630e #0 Device Description: WSS/SB TAG Start DF Good Configuration DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 - only one type (true/edge) I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x220, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Acceptable Configuration DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x260, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x3f8, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x300, alignment 0x20, len 0x10 [16-bit addr] TAG End DF Logical Device ID: CSC0001 0x0100630e #1 Device Description: GAME TAG Start DF Good Configuration I/O Range 0x200 .. 0x200, alignment 0x8, len 0x8 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x208 .. 0x208, alignment 0x8, len 0x8 [16-bit addr] TAG End DF Logical Device ID: CSC0010 0x1000630e #2 Device Description: CTRL I/O Range 0x120 .. 0xff8, alignment 0x8, len 0x8 [16-bit addr] Logical Device ID: CSC0003 0x0300630e #3 Device Description: MPU TAG Start DF Good Configuration IRQ: 9 - only one type (true/edge) I/O Range 0x330 .. 0x330, alignment 0x8, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 9 11 12 15 - only one type (true/edge) I/O Range 0x300 .. 0x3f8, alignment 0x8, len 0x2 [16-bit addr] TAG End DF End Tag Successfully got 44 resources, 4 logical fdevs -- card select # 0x0001 CSN CSC0b36 (0x360b630e), Serial Number 0x Logical device #0 IO: 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 IRQ 5 0 DMA 1 0 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #3 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 9 0 DMA 4 4 IO range check 0x00 activate 0x01 Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: another newpcm casualty
At 07:45 AM 09/06/99 +0200, Ollivier Robert wrote: >According to Manfred Antar: > > I have a Intel PR440FX motherboard with builtin sound (Crystal Sound > System) > > It worked fine until the recent changes in pnp. > >I have the same m/b with the same audio chip and > >controller pnp0 >device pcm0 > >finds the card just fine: > >unknown0: on isa0 >pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 >on isa0 >unknown1: at port 0x200-0x207 on isa0 >unknown2: at port 0x330-0x331 irq 9 on isa0 > >FreeBSD Audio Driver (newpcm) Sep 4 1999 22:38:12 >Installed devices: >pcm0: at io 0x534 irq 5 drq 1:0 (1/1 channels duplex) I get the same at boot up but the card is unusable. When I try to use it I get a kernel msg : dsp sync but no output. Is there anything else I need to change ? I've wiped out the snd devices in /dev and did a MAKEDEV snd0 The IRQ's in the bios are mapped to I/O apic not legacy should I change this. is the any thing else I need to put in my kernel file besides the above 2 lines ? Any help would be appreciated. Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: another newpcm casualty
At 08:56 AM 09/06/99 +0100, Doug Rabson wrote: >On Sun, 5 Sep 1999, Manfred Antar wrote: > > > I'm having a similar problem with the newpcm stuff. > > I have a Intel PR440FX motherboard with builtin sound (Crystal Sound > System) > > It worked fine until the recent changes in pnp. > > I can get it to work with the Voxware drivers no problem. > > Here is the relevant part of my kernel config : > > > > controller pnp0 > > device pcm0 at isa? port ? irq 5 flags 0x03 > >Change this to: > > device pcm0 I tried that and still no go. This is what comes up: unknown0: on isa0 pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown1: at port 0x200-0x207 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 But it is unusable. Ollivier Robert has the same motherboard and It works for him. All I can think of is there must be a conflict with one of the other cards on the board. Matrox Millenium or the DPT Raid controller. Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNP problems
At 01:49 PM 09/07/99 -0700, Randy Bush wrote: >i am in a similar position. so i did as you say. > > controller pnp0# PnP support for ISA > ... > # pcm: Luigi's sound driver > #device pcm0 at isa? port ? irq 5 drq 1 flags 0x0 > device pcm0 > >now, although pcm0 shows up in dmesg, i get > > % xmix > Error opening mixer device /dev/mixer: Device not configured > >and similar whinging. xmix worked before the change. It's probably looking for mixer at mixer1 instead of mixer0. #cd /dev #sh MAKEDEV snd0 you don't need any of the snd1 devices with the new pnp, whereas the old style you did Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BEWARE: CAM changes broke AHC!
At 06:03 AM 10/02/99 +0800, Peter Wemm wrote: >If you boot with a -current kernel: > >(da0:ahc0:0:0:0) data overrun detected in Data-In phase. Tag = 0x8 >(da0:ahc0:0:0:0) Have seen Data Phase. Length = 0, NumSGs = 1 > >Backing out the following sys/cam/scsi change set: Something also happened on my system with a DPT controller and builtin adaptec scsi on mother board. (Intel PR440FX) The system just hangs right after mounting the swap. A kernel from yesterday works fine. The boot disk is on the DPT controller (Raid Type 1) Nothing on the adaptec but a CDROM. Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc failure while updating from pre-signal-change
At 01:19 PM 10/02/99 +0200, Poul-Henning Kamp wrote: >Ok, I've committed what I belive is a fix for the problem. It was not >the locking as Bruce suggested, although his suggestion still has a point, >it was si_iosize_max which was uninitialized, which confuses minphys >and subsequently various other stuff. My problem with locking up on startup is now gone Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proftpd problem
At 12:25 AM 10/23/99 +0400, Ilya Naumov wrote: >Hello, > >recently i've got the following problem with proftpd. > >this daemon (pre8) worked ok until one of recent "make world"s. after >that it started to deny any non-anonymous logins with the following >diags: > >Oct 23 00:18:11 camel proftpd[76540]: PAM(camel): Authentication failure >Oct 23 00:18:11 camel proftpd[76540]: USER camel: incorrect password >from 192.168.2.2 [192.168.2.2] to xxx.xxx.xxx.xxx:21 >Oct 23 00:18:00 camel proftpd[76540]: FTP session closed. > >entries in pam.conf related to ftp are correct and proftpd.conf is >ok too (i guess :). > >so, is it a problem connected to changes in PAM or anything else? >thank you. > I had the same problem and hacked at it for few hours. the only way I could get it to work was to put PersistentPasswdOn in the /usr/local/etc/proftpd.conf file. It stopped working about last weekend. With the above line added it works fine. Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
At 04:10 PM 11/15/99 -0500, Forrest Aldrich wrote: >Same here, no problems. > > >_F > > >At 03:36 PM 11/15/99 -0500, Kenneth Wayne Culver wrote: > >I just successfully compiled the world and the kernel (defaut > >optimizations on everything) with gcc 2.95.2, and so far all is well :-) I did the same and everything works. But XFree86 from the ports collection will not build. Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
At 01:06 PM 11/16/99 +0200, Sheldon Hearn wrote: >On Mon, 15 Nov 1999 13:22:23 PST, Manfred Antar wrote: > > > I did the same and everything works. > > But XFree86 from the ports collection will not build. > >By the way, I just tested the build using gcc-2.95.2 both with and >without the threads support. So you really are going to need to provide >more information. > >Ciao, >Sheldon. Did it build for you ? I get Full build of XFree86 done or something like that at the end of the build but it only took 20 minutes. It usually takes about 1 hour. I have to go to work but I'll start another build and see if I can get some of the errors listed Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
At 04:50 PM 11/16/99 +0200, Sheldon Hearn wrote: >On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote: > > > Did it build for you ? > >Yes. > >Ciao, >Sheldon. Ok Sheldon here are some of the Errors I get when building XFee86 with the new compiler A few of these : cc -c -O -I../.. -I../../exports/include -DSERVERNAME=\"rstartd\" -DDEFAULT_CONFIG=\"/usr/ X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c server.c: In function `putenv': server.c:790: argument `s' doesn't match prototype /usr/include/stdlib.h:117: prototype declaration *** Error code 1 (continuing) cc -c -O -I../.. -I../../exports/include-DNOPUTENV util.c util.c: In function `putenv': util.c:673: argument `s' doesn't match prototype /usr/include/stdlib.h:117: prototype declaration *** Error code 1 (continuing) Many of these errors about /lib/cpp: /lib/cpp -DCONFIGDIRSPEC='"'"-I/usr/X11R6/lib/X11/config"'"' xmkmf /lib/cpp: not found And at the end I get this : Full build of Release 6.3 of the X Window System complete. Now when I try to Install the "Full Build" I get install -c proxymngr /usr/X11R6/bin/proxymngr install -c -m 0444 pmconfig /usr/X11R6/lib/X11/proxymngr/pmconfig install in programs/proxymngr done installing in programs/rstart... rm -f server.o cc -c -O -I../.. -I../../exports/include -DSERVERNAME=\"rstartd\" -DDEFAULT_CONFIG=\"/usr/ X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c server.c: In function `putenv': server.c:790: argument `s' doesn't match prototype /usr/include/stdlib.h:117: prototype declaration *** Error code 1 Stop in /usr/ports/x11/XFree86/work/xc/programs/rstart. *** Error code 1 Stop in /usr/ports/x11/XFree86/work/xc/programs. *** Error code 1 Stop in /usr/ports/x11/XFree86/work/xc. *** Error code 1 Stop in /usr/ports/x11/XFree86/work/xc. *** Error code 1 Stop in /usr/ports/x11/XFree86. *** Error code 1 Stop in /usr/ports/x11/XFree86. *** Error code 1 Stop in /usr/ports/x11/XFree86. This is a build with Just the XF86SVGAServer and XF86VGA16Server plus all the security stuff xdm, Wraphelp.c, no Kerberos or Thread Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
At 05:14 PM 11/16/99 -0800, Manfred Antar wrote: >At 04:50 PM 11/16/99 +0200, Sheldon Hearn wrote: > > >>On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote: >> >> > Did it build for you ? >> >>Yes. >> >>Ciao, >>Sheldon. > >Ok Sheldon here are some of the Errors I get when building XFee86 with the >new compiler >A few of these : > >cc -c -O -I../.. >-I../../exports/include -DSERVERNAME=\"rstartd\" -DDEFAULT_CONFIG=\"/usr/ >X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c >server.c: In function `putenv': >server.c:790: argument `s' doesn't match prototype >/usr/include/stdlib.h:117: prototype declaration >*** Error code 1 (continuing) Someone Just put a broken tag in the makefile. = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
At 09:35 PM 11/16/99 -0500, Bill Fumerola wrote: >On Tue, 16 Nov 1999, Manfred Antar wrote: > > > -DDEFAULT_CONFIG=\"/usr/ > > X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c > > server.c: In function `putenv': > > server.c:790: argument `s' doesn't match prototype > > /usr/include/stdlib.h:117: prototype declaration > > *** Error code 1 (continuing) > >There are a _lot_ of things broken with this port. I've already >marked it broken for the above reason. There is the /lib/cpp problem, >the -lcrypto problem, it doesn't build the servers you tell it to. > >Ugh. > >-- >- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - >- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - I think this is all related to the compiler update as I did a good build Friday or Saturday before the change. Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
At 09:50 PM 11/16/99 -0500, Bill Fumerola wrote: >On Tue, 16 Nov 1999, Manfred Antar wrote: > > > I think this is all related to the compiler update as I did a good > > build Friday or > > Saturday before the change. > >If it is, then some thing wierd is going on. Maybe it's something else, there might of been some other changes to the src tree that I didn't notice.My date for the last clean build of XFree86 is Saturday at midnight (with threads) The build machine was current at that point with a make world done some time Sat morning. Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New vfs_conf.c panic
Mike I get a panic on current smp-kernel with the new version of vfs_conf.c . The system is current as of this morning If I back out to version 1.44 it boots fine. It seems to panic at the swapon part of the boot process. I get : Fatal trap 12: page fault while in kernel mode mp_lock = 0102; cpuid = 1; lapic.id = 0c00 fault virtual address = 0x2b fault code = supervisor read, page not present instruction pointer = 0x8:0xc014a79a stack pointer = 0x10:0xc0311f34 frame pointer = 0x10:0xc0311f34 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 = 0 (swapper) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0102; cpuid = 1; lapic.id = 0c00 boot() callled on cpu#1 syncing disks .. = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New vfs_conf.c panic
At 12:26 PM 11/29/99 -0800, Matthew Dillon wrote: >:Mike >:I get a panic on current smp-kernel with the new version >:of vfs_conf.c . >:The system is current as of this morning >:If I back out to version 1.44 it boots fine. >:It seems to panic at the swapon part of the boot process. >:I get : >:Fatal trap 12: page fault while in kernel mode >:mp_lock = 0102; cpuid = 1; lapic.id = 0c00 >:fault virtual address = 0x2b >:fault code = supervisor read, page not present > > Is the panic occuring with version 1.45 of vfs_conf.c or > 1.46? I just committed 1.46 a moment ago along with > i386/i386/autoconf.c which fixes BOOTP boots. Prior > to that BOOTP boots would panic. > > A 'trace' would be helpful if you have DDB enabled or, > if you are using BOOTP, the problem should now be fixed > once the commit propogates. > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> Version 1.46 works fine Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New vfs_conf.c panic
At 09:29 PM 11/29/99 +0100, Poul-Henning Kamp wrote: >Manfred, > >Could you send the 10 lines surrounding the address 0xc014a79a >from the output of "nm -n /this_kernel" ? OK This kernel was striped -g do you need a debug compiled kernel ? Here is what i get c014a1c8 T set_timecounter c014a234 t switch_timecounter c014a2b8 t sync_other_counter c014a340 t tco_forward c014a464 t sysctl_kern_timecounter_hardware c014a4f8 T pps_ioctl c014a5dc T pps_init c014a604 T pps_event c014a758 T chrtoblk c014a758 t gcc2_compiled. > this is the closest I got c014a794 T devsw c014a7b0 T cdevsw_add c014a8ac T cdevsw_remove c014a8f8 T major c014a90c T minor c014a920 T lminor c014a940 T makebdev c014a95c T makedev c014aa48 T freedev c014aad0 T dev2udev = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New vfs_conf.c panic
At 09:55 PM 11/29/99 +0100, Poul-Henning Kamp wrote: >Do you have /dev/sd* in your /etc/fstab ? > >It should be changed to /dev/da* This is what I have # DeviceMountpoint FStype Options DumpPass# /dev/rda0s1bnoneswapsw 0 0 /dev/rda0s1a/ ufs rw 1 1 /dev/rda0s1e /var ufsrw 2 2 /dev/rda0s1f/usrufs rw 2 2 /dev/rda0s1g /usr/obj ufsrw2 2 proc/proc procfs rw0 0 /dev/cd0a /cdrom cd9660 ro,noauto 0 0 Should I change cd0a to rcd0a ? Any way it boots now with version 1.46 of vfs_conf.c that Mike just committed Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New vfs_conf.c panic
At 10:23 PM 11/29/99 +0100, Poul-Henning Kamp wrote: >Ahh, Ok. > >Bruce (a little hasty in my mind) removed a compat shim we had, >please change the 'rda' to 'da' again and all should be fine. > >Poul-Henning Done Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current kernel compile fails
I think this happened when mbuf.h was changed : linking kernel.debug uipc_mbuf.o: In function `m_mballoc_wait': /sys/compile/pro2/../../kern/uipc_mbuf.c(.text+0x2cb): undefined reference to `m_mballoc_wakeup' uipc_mbuf.o: In function `m_clalloc_wait': /sys/compile/pro2/../../kern/uipc_mbuf.c:349: undefined reference to `m_clalloc_wakeup' *** Error code 1 Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** location of sendmail.cf changed
At 10:21 AM 12/20/99 +1300, Joe Abley wrote: >On Sun, Dec 19, 1999 at 12:05:43PM -0800, David O'Brien wrote: > > On your next CVSup, /usr/sbin/sendmail will look for sendmail.cf in > > /etc/mail/ , not /etc/. > > > > Then change was made because the current offical Sendmail Inc. version > > uses /var/mail/ and when we upgrade our repository to that version, we > >s/var/etc/ presunably. /etc/rc needs to have the location of sendmail.cf changed also. Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New SMP changes
I just noticed something with a new kernel with a Fresh world as of 1 hour ago. I'm running 2 setiathome's one for each CPU (Pentium pro) and the machine has suddenly turned into a slug It's worse than a 286 machine I used to own. It's amazing !!! It worked with this setup before the changes fine and if I kill the setiathome's everything is back to normal. Top: PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 539 nobody 66 1 15092K 14336K CPU1 1 0:45 97.87% 90.62% setiathome 536 nobody -6 1 15092K 14336K RUN0 0:50 97.45% 90.23% setiathome I did a make world with the new changes an it worked fine. I running setiathome version 2 Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: All PCI DPT adapter users!
At 10:53 PM 4/6/2000 -0400, Matthew N. Dodd wrote: >I've just updated the DPT PCI front end to be 'newbus' compliant but lack >the hardware to test my changes. It should work just fine but I'd >appriciate a quick 'it works!' from someone with hardware just to be sure. It hangs here :( the boot gets to: dpt0 port 0xff80-0xff9f irq 16 at device11.0 on pci0 and just stalls. The controller is a DPT PM2124 with 2 4gig seagate drives in a RAID 1 setup. The motherboard is an Intel PR440FX Dual pentium pro with 2 200mhz cpu's I can't get to the debugger it just freezes. I removed the line optionsCOMPAT_OLDPCI from my config file before I built the kernel that doesn't work Here is what comes up an my old kernel: dpt0: port 0xff80-0xff9f irq 16 at device 11.0 on pci0 dpt0: DPT PM2124A/9X-R FW Rev. 07CK, 1 channel, 64 CCBs dpt0: driver is using old-style compatability shims Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: All PCI DPT adapter users!
At 10:53 PM 4/6/2000 -0400, Matthew N. Dodd wrote: >I've just updated the DPT PCI front end to be 'newbus' compliant but lack >the hardware to test my changes. It should work just fine but I'd >appriciate a quick 'it works!' from someone with hardware just to be sure. It hangs here :( the boot gets to: dpt0 port 0xff80-0xff9f irq 16 at device11.0 on pci0 and just stalls. The controller is a DPT PM2124 with 2 4gig seagate drives in a RAID 1 setup. The motherboard is an Intel PR440FX Dual pentium pro with 2 200mhz cpu's I can't get to the debugger it just freezes. I removed the line optionsCOMPAT_OLDPCI from my config file before I built the kernel that doesn't work Here is what comes up an my old kernel: dpt0: port 0xff80-0xff9f irq 16 at device 11.0 on pci0 dpt0: DPT PM2124A/9X-R FW Rev. 07CK, 1 channel, 64 CCBs dpt0: driver is using old-style compatability shims Manfred As a footnote A new kernel with: optionsCOMPAT_OLDPCI does the same thing -- freezes. = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world left me with an unbootable system
At 03:55 PM 4/20/2000 -0400, Adam wrote: >Last night around midnight EST I cvsupped and did make buildworld, config >-r'ed my kernel, compiled it, installed the kernel and did make >installworld. I rebooted expecting the system to come up fine but it >failed with "Invalid partition table". This was just after removing 2 of >3 of my dimm's becauseI thought they were causing a seperate >problem. The system is not overclocked, but SMP. Attempting to boot >kernel.old left me with the exact same problem. Here is what my screen >says: > >Verifying DMI Pool Data ... > >BTX loader 1.00 BTX version is 1.01 >Console: internal video/keyboard >BIOS drive A: is disk0 >BIOS drive C: is disk1 >BIOS drive D: is disk2 >BIOS drive E: is disk3 >BIOS 639k/130048kB available memory > >FreeBSD/i386 bootstrap loader, Revision 0.7 >([EMAIL PROTECTED], Thu Apr 20 01:30:00 EDT 2000) >Loading /boot/defaults/loader.conf >/kernel > text=0x186b9f data=0x3b81c+0x1b33c syms=[0x4+0x26000+0x4+0x2ac6c] >- >Hit [Enter] to boot immediately, or any other key for command prompt. >Booting [kernel]... >Invalid partition table_ > >where _ is the blinking cursor > > >I am not afraid of using the fixit disk if I have to, but I also have a >spare 5g disk I could toss in and install freebsd on if that would be the >easiest way of fixing this. ANY suggestions or insight to the problem is >appreciated! Yesterday I built a new loader (/boot/loader) after there were some changes made to the src tree for the loader. When I rebooted the machine hung with some error messages. I used the fixit disk and mounted the root partition and copied /boot/loader.old to /boot/loader Then everything worked. Try that Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
At 09:18 PM 5/13/2000 +0200, Poul-Henning Kamp wrote: >In message <[EMAIL PROTECTED]>, Jeroen Ruigrok van der Werv >en writes: > >-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: > >>I get this in boot mesgs and I don't know how to fix it. > >>Device char-major=13 minor=0 opened in block mode, convert to char mode > >>with /dev/MAKEDEV before 2000-07-01 > > > >There is a bug somewhere in the rootmount code. > > > >I just lack the expertise to find out where it is. > >Actually I think this is an indication of really old boot blocks. > >The old bootblocks passed in a Bmajor number for the root device. > >Could you try to update your bootblocks with the disklabel >program and see if that stops the warning Manfred ? I did a disklabel -B da0 and it still happens Another thing is this is a RAID 1 disk <2 disk mirror> on a DPT RAID controller I don't know if that make a difference. Which is the dev I'm supposed to be using : rda0a, da0a, da0s1a ?? Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MAKEDEV Warning ???
I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 I've run MAKEDEV all I have a simple fstab: # DeviceMountpoint FStype Options DumpPass# /dev/rda0b noneswapsw 0 0 /dev/da0a / ufs rw 1 1 /dev/rda0e/varufs rw 2 2 /dev/rda0f /usrufs rw 2 2 /dev/rda0g/usr/obj ufs rw 2 2 proc/proc procfs rw 0 0 If i change /dev/da0a to /dev/rda0a it won't mount. If i use this I still get the same message: # DeviceMountpoint FStype Options DumpPass# /dev/da0b noneswapsw 0 0 /dev/da0a / ufs rw 1 1 /dev/da0e/varufs rw 2 2 /dev/da0f /usrufs rw 2 2 /dev/da0g/usr/obj ufs rw 2 2 proc/proc procfs rw 0 0 This also causes the same message: /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1e/varufs rw 2 2 /dev/da0s1f /usrufs rw 2 2 /dev/da0s1g/usr/obj ufs rw 2 2 proc/proc procfs rw 0 0 Which is correct ?? Also I've tried changing the ROOTDEV option in my kernel config to no avail Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
At 09:54 PM 5/13/2000 +0200, Assar Westerlund wrote: >Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> writes: > > -On [20000513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: > > >I get this in boot mesgs and I don't know how to fix it. > > >Device char-major=13 minor=0 opened in block mode, convert to char mode > > >with /dev/MAKEDEV before 2000-07-01 > > > > There is a bug somewhere in the rootmount code. > >The following patch fixed the problem for me. For extra points, >rename the function. > >/assar > >--- vfs_subr.c~ Sat May 6 00:08:38 2000 >+++ vfs_subr.c Sat May 13 21:47:08 2000 >@@ -1296,7 +1296,7 @@ > return (error); > } > vp = nvp; >- vp->v_type = VBLK; >+ vp->v_type = VCHR; > addalias(vp, dev); > *vpp = vp; > return (0); That works for me too . Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV Warning ???
At 10:28 PM 5/13/2000 +0200, Jeroen Ruigrok van der Werven wrote: >-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote: > >Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use > >rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? > >The /dev/da0s1a would be the correct one to use, example: > > ># DeviceMountpoint FStype Options DumpPass# >/dev/da0s1b noneswapsw 0 0 >/dev/da0s1a / ufs rw 1 1 >/dev/da0s1e /tmpufs rw 2 2 >/dev/da0s1g /usrufs rw 2 2 >/dev/da0s1f /varufs rw 2 2 >/dev/da0s1h /work ufs rw 2 2 >/dev/cd0c /cdrom cd9660 ro,noauto 0 0 >proc/proc procfs rw 0 0 >/dev/fd0/diskette msdos rw,noauto 0 0 > >-- >Jeroen Ruigrok van der Werven Network- and systemadministrator ><[EMAIL PROTECTED]>VIA Net.Works The Netherlands >BSD: Technical excellence at its best http://www.via-net-works.nl >I walk, I walk alone, into the promised land... OK Thats what I was using before. MAKEDEV doesn't automatically create the s1a devices so I switched thinking that what was causing the error Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current SMP kernel panics y/n [y]
A current kernel just built after a current make world comes up with this and stops booting: Programming 24 pins in IOAPIC #0 AP #1 (PHY# 12) failed! panic y/n [y] If I type n the kernel boots fine. doing mptable cause a panic though Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Not to change the subject ,but mptable causes a panic on my machine running current. If I revert back to a kernel compiled on the 13th of May everything works fine. I think there were some changes made to the SMP code on the 14th or 15th also the binutils were upgraded and I'm not sure what caused it. With a current kernel I get this when booting: Programming 24 pins in IOAPIC #0 AP #1 (PHY# 12) failed! panic y/n [y] panic: bye-bye mp_lock = 0001; cpuid = 0; lapic.id = Uptime: 0s I'm going to check out a sys tree from the 14th and try rebuilding a kernel and see if that works. The kernel I have >>> Sun May 14 15:39:19 PDT 2000 works fine Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
At 09:00 PM 5/23/2000 +0200, Vallo Kallaste wrote: >On Tue, May 23, 2000 at 11:06:38AM -0700, Manfred Antar <[EMAIL PROTECTED]> wrote: > >> Not to change the subject ,but >> mptable causes a panic on my machine running current. >> If I revert back to a kernel compiled on the 13th of May everything works >> fine. I think there were some changes made to the SMP code on the 14th or 15th >> also the binutils were upgraded and I'm not sure what caused it. >> With a current kernel I get this when booting: >> >> Programming 24 pins in IOAPIC #0 >> AP #1 (PHY# 12) failed! >> panic y/n [y] panic: bye-bye >> mp_lock = 0001; cpuid = 0; lapic.id = >> Uptime: 0s > >I've just completed world and compiled new kernel and found that my >system reboots right after showing about seven lines of usual boot >messages. I've found that UP GENERIC works and UP custom kernel works >but SMP is broken. It has to do something with last three days of >commits, because my last working SMP kernel is from Friday 19'th. >Running mptable on the UP kernel doesn't cause crash for my system. >Reboot is totally silent so I don't have any other info, sorry, I've >only thought it happens about same time as the APIC probe. >-- I'm backing out to kernel sources as of the 13th and am building a kernel now. I'm running SMP. It's funny I had a kernel from Sunday 5/21 and it boot's fine and works in the SMP mode but mptable causes a panic. I just booted one from sources from the 13th same thing. I think this has something to do with the new binutils as a kernel built on the 14th and restored via tape works fine but if i check out the sys tree from the 14th and build a kernel it panics at the APIC probe. Or maybe I need to rebuild some library too from the 14th, I'm not sure if the kernel links to any library. I guess a good test would be to make world from before the binutil change and try a kernel built from that Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mpboot.s patch
At 04:33 AM 5/24/2000 +0200, [EMAIL PROTECTED] wrote: >> >> With a current kernel I get this when booting: >> >> >> >> Programming 24 pins in IOAPIC #0 >> >> AP #1 (PHY# 12) failed! >> >> panic y/n [y] panic: bye-bye >> >> mp_lock = 0001; cpuid = 0; lapic.id = >> >> Uptime: 0s > >[...] > >> I think this has something to do >> with the new binutils as a kernel built on the 14th and restored via tape works >fine but if i >> check out the sys tree from the 14th and build a kernel it panics at the APIC probe. > >Try the enclosed patch. > >- Tor Egge Tor Works great The patch didn't apply I think there is a "data32" in the patch that isn't in the mpboot.s file but when I applied the patch manually an added the data32 the kernel built fine and boots both cpu's without a problem. although mptable still causes a panic : panic: pmap_enter: attempted pmap_enter on 4MB page mp_lock = 0002; cpuid = 0; lapic.id = boot() called on cpu#0 Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
At 01:20 AM 6/14/2000 -0700, Peter Wemm wrote: >Peter Wemm wrote: > >> # update /boot/loader.conf >> cd src/sys/boot; make obj depend all install > >Of course, it would be just my luck that there is a loader bug right now, >and this command will throw you into the fire. ;-( If your loader >complains about not being version 0.3+ or later and aborting, comment the >version tests out of /boot/loader.4th as an interim. > >I have also just committed a last-minute introduced bug that prevented >static hints files with full-line comments in them from working properly. > >Cheers, >-Peter Peter I got this to work after some tweaking. I was getting syntax errors from the hints file when booting. I cut and pasted out of GENERIC.hints into my.hints and now it seems to boot without any errors. I noticed I now have a new link in the / directory :: lrwxr-xr-x 1 root wheel 10 Jun 14 11:18 ttyv0@ -> /dev/ttyv0 is this normal ? Also it seems that there is a order in the hints file that needs to be followed. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anybody notice? Was:Re: çÃà êîìñòâî
At 07:51 PM 6/24/2000 -0500, Joe wrote: >Anybody notice that this guy is sending a trojan as an attachment? > >-Joe > >On Sun, Jun 25, 2000 at 04:29:51AM +0300, [EMAIL PROTECTED] wrote: >> >>J nikogda ne pytalas% poznakomit%sJ v internete, no resilas% poprobyvat%. Zivu >v Moskve, ucus%. >>Mne 19 let. Ne znaj, cego mne ne hvataet, mozet prosto obseniJ , a mozet laski i >vnimaniJ. >>J daze ne znaj, cto o sebe napisat%, vrode ne dura, a ne mogu. J dostatocno >kriticno (to est% >> sebe ne nravljs%) otnosus% k svoej vnesnosti, no predostavlj tebe ocenit% ee.(ehe- >jto slajd sou) >> Yes I've had it picked up by Norton Anti Virus twice today. == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Anybody notice? Was:Re: çÃà ê îìñòâî
At 09:52 PM 6/24/2000 -0400, Brian Hechinger wrote: i just got three more, that makes like 5 or 6 today. is it possible to filter this guy on the mailing list server? he's obviously not going to ever post anything of any value. -brian I just put a filter in my mail program. == ||  [EMAIL PROTECTED]   || ||  Ph. (415) 681-6235  || ==
Re: ahc lockups in -current
At 06:07 PM 7/23/2000 -0500, Mike Meyer wrote: >It seems that the last changes to the ahc drivers (committed on the >18th) are causing my system to lock up. I'd check the aic7890 specific >changes first, but that's just me. > >The problem is that when I start doing I/O to two drives, the system >hangs. The SCSI controller and both drives(*) turn on their "I'm busy" >LED, so I assume the scsi bus is hung. They OS is still there, but >trying to do anything that touches the drives causes the process to >lock up. I get no core dump and no messages to the console indicating >any problems. > >With this version, I *do* get the following message at boot time that >I didn't get before: > >(noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > >The system configuration is: I get the same hang when doing a dump to an Exabyte 8505 connected to on board aic7880 My disks are hooked up to an internal DPT Raid controller and no problem there. Any time I try to access the tape drive it panics. Sorry I don't have the panic message as I'm running this machine headless at the moment. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fatal trap 12 on kernel from sometime Nov. 30.
At 07:12 PM 12/1/2001 -0800, Edwin Culp wrote: >Andrew, > >Thanks. Now my problem is that I can't cvsup. Any ideas on how to update my >sources? >Maybe someone could email me a patch and I could take it over with a floppy. Right >now >I have no access to the network with the machine that has the fatal trap. > >Thanks, > >ed > Do you have a /boot/kernel.old/kernel that works ? Always save a working kernel !!! with current. If you have a good /boot/kernel.old/kernel Then when the machine is booting stop it at the OK prompt. OK unload OK load boot/kernel.old/kernel OK boot then recvsup == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New mail dumps core on current
mail dumps core on current with latest /usr/src/usr.bin/mail updates: (root)502}mail manfred Subject: test test test EOT Segmentation fault (core dumped) (root)503} This is from a current built today, although i think the changes were made yesterday. I noticed that I did not get mail from the daily periodic output. If I run periodic daily from shell i get: (root)503}periodic daily Segmentation fault - core dumped This happens on two different machines. one is an SMP box, the other is a laptop. world current as of noon today same with kernel. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release broken
At 07:51 AM 1/12/2002 +0200, John Hay wrote: >Hi, > >Make release of -current has been broken here for the past few days. I had >a look on the Japanese snapshot site and theirs break with the same error. >Do anybody have an idea about what is going wrong? > ># >touch release.5 >rm -rf /R/stage/dists >mkdir -p /R/stage/dists >rolling bin/bin tarball >tar: dev/mdctl: minor number too large; not dumped >tar: dev/acd0t32: minor number too large; not dumped >tar: dev/acd0t33: minor number too large; not dumped >tar: dev/acd0t34: minor number too large; not dumped >... >tar: dev/acd1t100: minor number too large; not dumped >tar: dev/sa0.ctl: minor number too large; not dumped >mtree: line 0: .exists: No such file or directory >*** Error code 1 > >Stop in /usr/src/release. >*** Error code 1 > >Stop in /usr/src/release. >*** Error code 1 > >Stop in /home/src/release. ># I can confirm that the same thing has been happening to me for about the past week. Don't know about any thing earlier. The last time I did a make release was in November and it worked. == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Pam problems today
At 09:49 PM 1/31/2002 -0600, David W. Chapman Jr. wrote: >I cvsuped a few hours ago, did the normal buildworld and >installworld, new kernel and mergemaster, but when I rebooted I could >not login, I had to comment a few lines in /etc/pam.d/login > >#accountrequiredpam_login_access.so >#accountrequiredpam_securetty.so > >#sessionrequiredpam_lastlog.so > >are the lines I had to comment out. I checked and I don't have >pam_login_access.so. I know that there have been a bunch of changes >recently, so if this is a known problem I apologize. > >-- >David W. Chapman Jr. >[EMAIL PROTECTED] Raintree Network Services, Inc. >[EMAIL PROTECTED] FreeBSD Committer > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message Same thing happened to me yesterday after a make install world and mergemaster. Took awhile to figure out. Building and installing libpam does not install pam_login_access.so Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
At 03:36 PM 2/17/2001 -0800, Matthew Jacob wrote: >One system got stuck in the current __sF bork... I'm not stuck with: > >cc -o make_hash -O -pipe -I. -I/usr/src/lib/libncurses >-I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses >-I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE >-DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -DMAIN_PROGRAM >/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c >/usr/lib/libgcc.so: undefined reference to `__sF' >*** Error code 1 > >Stop in /usr/src/lib/libncurses. >*** Error code 1 > >Stop in /usr/src. >*** Error code 1 > >Stop in /usr/src. >*** Error code 1 > >Stop in /usr/src. > > >Any advice? What is the date of your system (libc) ? Before Feb 10 or between the 10th and the 16th ? If before Feb 10 I would resup , remove /usr/obj and try again. If in the period between the 10th and 16th , you might need to restore from tape or other means then try again.I just did a make world from a system from the 10th and current src and it built fine Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
At 08:17 PM 2/17/2001 -0400, The Hermit Hacker wrote: >I just got hurt by this, in a sense ... buildworld and installworld all >worked great, but as soon as I tried to a 'startx', it told me that >libm.so.2 had an unresolved symbol __sF ... I just rebuilt my X, figure >just the result of the bump in libm.so.n major ... > > I don't think any of the libs were bumped recently except for libc and that was backed out. There was a patch posted that bumped some of the libs but that was withdrawn. I think you might have libs built from some of the stuff that was backed or not a totally current source. I'm using X compiled on the 8th of Feb with a current world as of 2 hours ago and no problem Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
At 07:00 PM 2/17/2001 -0700, Warner Losh wrote: >What version of src/lib/libc/stdio/findfp.c do you have? > >I'm using 1.15 here w/o any problems: >static const char rcsid[] = > "$FreeBSD: src/lib/libc/stdio/findfp.c,v 1.15 2001/02/16 21:09:49 imp Exp $"; > >Warner > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message There was a time when current ( a couple of days earlier this week) was volatile !! I had a system running for awhile with the new libc.so.5. I started recompiling all the ports and gave up as it didn't look like the new libc.so.5XXX was go to stay around and I didn't want to do this twice. I ended up newfs my hard drive and restoring from Feb 9 and then bringing the sources up to current (after the libc and stdio changes were backed out and modified) and doing a make world . Everything seems to be working fine since then. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
At 11:03 PM 2/17/2001 -0400, The Hermit Hacker wrote: >On Sat, 17 Feb 2001, Warner Losh wrote: > >> In message <[EMAIL PROTECTED]> The Hermit >Hacker writes: >> : On Sat, 17 Feb 2001, Warner Losh wrote: >> : >> : > In message <[EMAIL PROTECTED]> The Hermit >Hacker writes: >> : > : static const char rcsid[] = >> : > : "$FreeBSD: src/lib/libc/stdio/findfp.c,v 1.15 2001/02/16 21:09:49 imp >> : > : Exp $"; >> : > >> : > Then I don't understand the error at all. __sF should be defined in >> : > libc.so.5. What does ldconfig have to say? >> : >> : > ldconfig -r | grep libc. >> : 0:-lcom_err.2 => /usr/lib/libcom_err.so.2 >> : 2:-lcrypt.2 => /usr/lib/libcrypt.so.2 >> : 11:-lc.4 => /usr/lib/libc.so.4 >> : 12:-lc_r.4 => /usr/lib/libc_r.so.4 >> : 13:-lcalendar.2 => /usr/lib/libcalendar.so.2 >> : 14:-lcam.2 => /usr/lib/libcam.so.2 >> : 43:-lcipher.2 => /usr/lib/libcipher.so.2 >> : 44:-lcrypto.1 => /usr/lib/libcrypto.so.1 >> : 56:-lc.5 => /usr/lib/libc.so.5 >> : 57:-lc_r.5 => /usr/lib/libc_r.so.5 >> >> OK. This looks good. What does ldd say for the binary complaining? >> And what does libc.so point to? > >> ls -lt libc.* >-r--r--r-- 1 root wheel 599916 Feb 17 17:00 libc.so.5 >lrwxr-xr-x 1 root wheel9 Feb 17 17:00 libc.so -> libc.so.5 >-r--r--r-- 1 root wheel 1240424 Feb 17 17:00 libc.a >-r--r--r-- 1 root wheel 599116 Feb 15 21:10 libc.so.5.20010213 >-r--r--r-- 1 root wheel 581944 Nov 9 01:45 libc.so.4 > >All looks well here ... > > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message I don't think you want that libc.so.5.20010213 around it's evil :) == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
What ??
Dmesg: ---===> Happy Birthday Peter!!! <===--- :) Happy Birthday Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current SMP kernel won't build
I haven't been able to build a SMP kernel for a day. I just did a make world and tried again, no luck I keep getting this error: linking kernel.debug cam_periph.o: In function `cam_periph_mapmem': /usr/src/sys/compile/pro2/../../cam/cam_periph.c(.text+0xa42): undefined reference to `_mtx_assert' cam_periph.o: In function `cam_periph_unmapmem': /usr/src/sys/compile/pro2/../../cam/cam_periph.c(.text+0xc02): undefined reference to `_mtx_assert' /usr/src/sys/compile/pro2/../../cam/cam_periph.c(.text+0xd86): undefined reference to `_mtx_assert' /usr/src/sys/compile/pro2/../../cam/cam_periph.c(.text+0xeee): undefined reference to `_mtx_assert' yarrow.o: In function `reseed': /usr/src/sys/compile/pro2/../../dev/random/yarrow.c(.text+0x54f): undefined reference to `_mtx_assert' yarrow.o:/usr/src/sys/compile/pro2/../../dev/random/yarrow.c:417: more undefined references to `_mtx_assert' follow *** Error code 1 Stop in /usr/src/sys/compile/pro2 Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP kernel won't build
At 02:28 PM 2/25/2001 -0800, you wrote: >> cam_periph.o: In function `cam_periph_mapmem': >> /usr/src/sys/compile/pro2/../../cam/cam_periph.c(.text+0xa42): undefined refe >> rence to `_mtx_assert' > >Try putting, > >options INVARIANT_SUPPORT > >in your kernel config. I think jhb recently made mtx_assert >conditional on that option. Either that, or take out "options >INVARIANTS". > >Dima Dorfman >[EMAIL PROTECTED] That did it Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Using serial console to debug system hangs ...
At 01:48 PM 3/4/2001 -0400, The Hermit Hacker wrote: >On Sun, 4 Mar 2001, John Baldwin wrote: > >> >> On 04-Mar-01 The Hermit Hacker wrote: >> > On Sat, 3 Mar 2001, John Baldwin wrote: >> > >> >> >> >> On 04-Mar-01 The Hermit Hacker wrote: >> >> > >> >> > Wow, that was painful ... after 2 hrs, I got as far as: >> >> >> >> Yeah, it spews out a lot of crap. :-/ You prolly want to use a 115200 >> >> serial >> >> console if at all possible. Should've mentioned that earlier.. >> > >> > Okay, reading NOTES, it says that 9600 is the default ... does that mean I >> > should be able to attach at 115200 and it should auto-upgrade, or do I >> > have to recompile kernel iwth CONSPEED=115200 for this? >> >> Either recompile or use the loader tunable 'machdep.conspeed' I think. >> However, you'll probably want the bootstrap to work on teh serial console as >> well, in which case you need to set the speed in make.conf (see >> /etc/defaults/make.conf) and recompile and reinstall boot2 and the loader. > >Okay, now you are going beyond my experiences :( > >First, I changed CONSPEED to 115200, but sysctl is still registering 9600: > >thelab# sysctl machdep.conspeed >machdep.conspeed: 9600 > >manually doing 'sysctl -w machdep.conspeed=115200' appears to work though >... > >But, after modifying my make.conf, what do I have to recompile? Are we >just talking a rebuild and install of the kernel itself? I'm going to try >that ... > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message You have to recompile the boot stuff also, after changing the line in make.conf: # The default serial console speed is 9600. Set the speed to a larger value # for better interactive response. # BOOT_COMCONSOLE_SPEED= 57600 Then cd /sys/boot ; make depend all install. I forget if you then need to relabel the disk or not. ie : disklabel -B da0 == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Using serial console to debug system hangs ...
At 05:49 PM 3/4/2001 -0700, Warner Losh wrote: >In message <[EMAIL PROTECTED]> Manfred Antar writes: >: Then cd /sys/boot ; make depend all install. >: I forget if you then need to relabel the disk or not. >: ie : >: disklabel -B da0 > >I've noticed in the past that FreeBSD uss the com speed of the boot >blocks. > >Warner Yes I thought so. There is a web page some where that tell's exactly how to set this up. I just found it: http://www.freebsd.org:80/handbook/serialconsole-setup.html Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Touch pad problem on HP n5470 Laptop
At 09:31 PM 6/28/2001 -0700, Edwin Culp wrote: >I can't get the mouse working on a new HP Pavilion 5470 laptop. I just >installed and cvsuped, made world and get this in my dmesg. It's my guess >that the second atkbd0/psm1 are the problem. Does anyone have an idea what >I should do? > >atkbdc0: at port 0x60,0x64 on isa0 >atkbd0: flags 0x1 irq 1 on atkbdc0 >kbd0 at atkbd0 >psm0: irq 12 on atkbdc0 >psm0: model Generic PS/2 mouse, device ID 0 >atkbd1: flags 0x1 irq 1 on atkbdc0 >kbd1 at atkbd1 >psm1: unable to allocate the IRQ resource (12). > >The BIOS has an auto/both option for the touch pad and/or an external >mouse. Unfortunately there is no touch pad only option. > >Thanks, > >ed I'm have the same problem on a dual pentium pro machine. Intel PR440FX Something has changed in the psm code. I must admit today was the first time I tried using the mouse. I mostly access this machine over the network or com port, so I can't say when this started. I don't remember ever seeing reference to "psm1" I only have 1 mouse on this machine and there is only 1 in the kernel config file. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Touch pad problem on HP n5470 Laptop
At 08:08 AM 6/29/2001 +0200, Ollivier Robert wrote: >According to Manfred Antar: >> this started. I don't remember ever seeing reference to "psm1" I only have 1 >> mouse on this machine and there is only 1 in the kernel config file. > >Re-read messages in -current a few weeks ago, the problem was mentionned and >the solution was too. Remove the atkbd and psm hints from either >/boot/device.hints or in your kernel config file. >-- >Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] >FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message I did this and now I have no keyboard or mouse. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Touch pad problem on HP n5470 Laptop
At 04:22 PM 6/29/2001 +0200, Ollivier Robert wrote: >According to Manfred Antar: >> I did this and now I have no keyboard or mouse. > >You have to remove the « hints » only, not all the lines about atkbd/psm if >you had them in the kernel config. file... >-- >Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] >FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message Ollivier I got it working. I'm not sure what was wrong. I had my kernel config setup to statically compile in the hints. once I removed this. It worked. Also I had 2 device hints files both identical, one in /boot and one in /sys/i386/conf. I removed the one in /sys/i386/conf. I'm going to try to see if I can go back to statically compile in the hints. This hint's thing is confusing;) Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
netpbm broken on current crtn.o new binutils ?
The port netpbm builds and installs fine on current. When trying to build the docs in /usr/docs the program peps calls /usr/local/bin/pnmtopng This is from the netpbm port. (/usr/local/bin)505}./pnmtopng /usr/libexec/ld-elf.so.1: /usr/lib/crtn.o: unsupported file type (/usr/local/bin)506} ldd ./pnmtopng ./pnmtopng: libpnm.so.1 => /usr/local/lib/libpnm.so.1 (0x2806c000) libppm.so.1 => /usr/local/lib/libppm.so.1 (0x28073000) libpgm.so.1 => /usr/local/lib/libpgm.so.1 (0x2807c000) libpbm.so.1 => /usr/local/lib/libpbm.so.1 (0x2807f000) libpng.so.4 => /usr/local/lib/libpng.so.4 (0x2808d000) libm.so.2 => /usr/lib/libm.so.2 (0x280ad000) libc.so.5 => /usr/lib/libc.so.5 (0x280c9000) =>crtn.o (0x0) libz.so.2 => /usr/lib/libz.so.2 (0x2817d000) Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libpam build broken in current
libpam will not build if you don't have the stock ssh installed. I use ssh from ports. (libpam)502}make ===> modules ===> modules/pam_deny ===> modules/pam_ftp ===> modules/pam_nologin ===> modules/pam_opie ===> modules/pam_permit ===> modules/pam_radius ===> modules/pam_rootok ===> modules/pam_securetty ===> modules/pam_ssh building shared library pam_ssh.so /usr/libexec/elf/ld: cannot find -lssh *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_ssh. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 Stop in /usr/src/lib/libpam. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: devfs
At 11:17 AM 8/20/2001 -0400, Brandon D. Valentine wrote: >On Mon, 20 Aug 2001, David W. Chapman Jr. wrote: > >>The only problem is devfs is mounted and I can't seem to get around >>that. > >I haven't had much time lately to fool with my -CURRENT box but >it seems that booting singleuser oughta help? > >-- >"Never put off until tomorrow what you can do today. There might be a >law against it by that time." -- /usr/games/fortune, 07/30/2001 > >Brandon D. Valentine > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message I couldn't do this from single user. I forget the error somthing about moving a mount point. What worked for me was to boot off the CDROM and go into the fixit mode then mount the / partition on /mnt. cd /mnt/dev/ rm -r * Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
md.c broken in current
From sources this morning when trying to build a kernel: (pro2)502}make cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../../dev/md/md.c ../../../dev/md/md.c: In function `mddetach': ../../../dev/md/md.c:814: `MD_PRELOAD_COMPRESSED' undeclared (first use in this function) ../../../dev/md/md.c:814: (Each undeclared identifier is reported only once ../../../dev/md/md.c:814: for each function it appears in.) *** Error code 1 Stop in /usr/src/sys/i386/compile/pro2. (pro2)503} Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dirty buffers on reboot..
At 11:59 AM 9/9/2000 -0400, Robert Watson wrote: >On Fri, 8 Sep 2000, John Baldwin wrote: > >> Ok, an update on the dirty buffers on reboot: >> >> If you use the reboot command, you will get dirty buffers. If you use >> 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a >> workaround for now, use the shutdown command to reboot your box until we >> can track this down. > >Um. Nope. :-) I only use shutdown -r now, and I still get dirty >buffers. I too only use "shutdown -r now" and still get dirty buffers. Tor Egge posted a patch and with the patch to kern_shutdown.c I no longer have the problem. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New Fatal trap in Current SMP (random.dev changes ??)
>From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time Although the first occurrence happened this morning after compiling a kernel after the random dev changes. The system boots and mounts disks. When it gets to this point: Additional routing options: TCP extensions=NO TCP keepalive=YES. routing daemons:. I think the random dev kicks in at this point Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0c00 fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc014f280 stack pointer = 0x10:0xc9a74f84 frame pointer = 0x10:0xc9a74f9c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1,def 32 1,gran 1 processor flags = interrupt enabled, resume, IOPL = 0 current process = 2 (random) trap number = 12 panic: page fault cpuid = 1; lapic.id = 0x00 boot() called on cpu#1 syncing disks... The machine then is frozen and needs a reset to work again the debugger is unavailable Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New Fatal trap in Current SMP (random.dev changes ??)
At 08:16 PM 9/10/2000 -0700, John Baldwin wrote: >Manfred Antar wrote: >> >From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time >> Although the first occurrence happened this morning after compiling a kernel >> after the random dev changes. >> The system boots and mounts disks. When it gets to this point: >> Additional routing options: TCP extensions=NO TCP keepalive=YES. >> routing daemons:. >> I think the random dev kicks in at this point >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; lapic.id = 0c00 >> fault virtual address = 0x2c >> fault code= supervisor read, page not present >> instruction pointer = 0x8:0xc014f280 >> stack pointer = 0x10:0xc9a74f84 >> frame pointer = 0x10:0xc9a74f9c >> code segment = base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1,def 32 1,gran 1 >> processor flags = interrupt enabled, resume, IOPL = 0 >> current process = 2 (random) >> trap number = 12 >> panic: page fault >> cpuid = 1; lapic.id = 0x00 >> boot() called on cpu#1 >> >> syncing disks... >> >> The machine then is frozen and needs a reset to work again >> the debugger is unavailable I backed out to the old versions of the random dev files: /sys/dev/randomdev: harvest.c randomdev.c yarrow.c yarrow.h /sys/sys: random.h And the panic goes away Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current periodic change
periodic is broken in current # /usr/sbin/periodic daily /usr/sbin/periodic: 43: Syntax error: ")" unexpected (expecting ";;") == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Entropy file problem
When setting entropy_file="/var/db/entropy" in rc.conf This error happens: No entropy file, trying other sources After a few minutes the machine continues booting /var is mounted on a separate partition from / Setting to : entropy_file="/tmp/entropy" This happens: Reading entropy file rm: /tmp/entropy: Read-only file system machine boots normally except for the above error Setting to: entropy_file="NO" the machine hangs at: setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib. break to debugger and reboot is needed. Then have to boot -s and edit rc.conf and set entropy file to something. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel trap 12 with interrupts disabled
With current kernel I'm getting alot of : kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled Kernel from yesterday did not do this. Everything seems to work fine although I think it hung on a "shutdown -r now" I don't have a monitor hooked up to the machine right now, so I have no further info. I'm in process of hooking up a serial console. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: sys/i386/i386/machdep.c:cpu_idle() changes causes this Was:
At 01:21 PM 10/20/2000 -0700, John Baldwin wrote: >On 20-Oct-00 Valentin Chopov wrote: >> I found that if I remove #ifndef SMP /#endif in: > >Errr, this doesn't really make sense, and if anything is probably >hiding the problem. Also, this change will potentially increase >interrupt latency even further on SMP machines. > >-- John Do you have any idea what's causing this ? Oct 20 21:20:36 pozo last message repeated 17 times Oct 20 21:30:00 pozo last message repeated 4 times Oct 20 21:30:00 pozo last message repeated 4 times Oct 20 21:41:26 pozo last message repeated 9 times Oct 20 21:41:26 pozo last message repeated 9 times Oct 20 21:50:01 pozo last message repeated 13 times Oct 20 21:50:01 pozo last message repeated 13 times #dmesg kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled this is a very truncated version there are probably 301 messages like this in a SMP machine that has only been up about 4 hours with very little activity , just a few cvsups and mail. If I build a kernel then the messages really increase. If there is any thing I can do Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current Kernel build broken
From latest sources: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../ufs/ufs/ufs_vfsops.c ../../ufs/ufs/ufs_vfsops.c: In function `ufs_quotactl': ../../ufs/ufs/ufs_vfsops.c:119: warning: implicit declaration of function `suser_xxx' ../../ufs/ufs/ufs_vfsops.c:119: `PRISON_ROOT' undeclared (first use in this function) ../../ufs/ufs/ufs_vfsops.c:119: (Each undeclared identifier is reported only once ../../ufs/ufs/ufs_vfsops.c:119: for each function it appears in.) *** Error code 1 == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current kernel build failure -- >>cam_periph.c
I've been trying to build a current kernel from current sources for a day now
and I keep getting this:
cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../i386/i386/locore.s
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../cam/cam_periph.c
../../cam/cam_periph.c: In function `cam_periph_unmapmem':
../../cam/cam_periph.c:687: internal error--unrecognizable insn:
(insn/i 376 1397 377 (parallel[
(set (mem/s/v:SI (plus:SI (reg:SI 0 %eax)
(const_int 284 [0x11c])) 0)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f;pushl %2;
pushl %3; callmtx_exit_hard; addl$8,%%esp;1:# exitlock_norecurse")
("=m") 0[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(set (reg:SI 0 %eax)
(asm_operands/v (" lock ; cmpxchgl %4,%0; jz 1f;pushl %2;
pushl %3; callmtx_exit_hard; addl$8,%%esp;1:# exitlock_norecurse")
("=a") 1[
(const_int 0 [0x0])
(reg/v:SI 4 %esi)
(reg:SI 5 %edi)
(mem/s/v:SI (plus:SI (reg:SI 3 %ebx)
(const_int 284 [0x11c])) 0)
(reg:SI 0 %eax)
]
[
(asm_input:SI ("gi"))
(asm_input:SI ("g"))
(asm_input:SI ("r"))
(asm_input:SI ("0"))
(asm_input:SI ("1"))
] ("../../sys/mutex.h") 601))
(clobber (reg:QI 1 %dl))
(clobber (reg:QI 2 %cl))
(clobber (mem:BLK (scratch) 0))
] ) -1 (insn_list 375 (nil))
(nil))
*** Error code 1
Stop in /usr/src/sys/compile/pro2
I did a make world last night from current sources
and still no go
Thanks
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- >>cam_periph.c
At 05:49 PM 12/6/2000 -0800, you wrote: >On 07-Dec-00 Manfred Antar wrote: >> >> >> I've been trying to build a current kernel from current sources for a day now >> and I keep getting this: > >I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() >compiles in dozens of other places just fine (and has for months now). > >-- > >John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ >PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message Yes It's a different kind of error. I've never seen this building a kernel before. The same kernel config without SMP enabled builds fine ! == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- >>cam_periph.c
At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: >On 07-Dec-00 John Baldwin wrote: >> >> On 07-Dec-00 Manfred Antar wrote: >>> >>> >>> I've been trying to build a current kernel from current sources for a day >>> now >>> and I keep getting this: >> >> I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() >> compiles in dozens of other places just fine (and has for months now). > >Nope, it was a sublte bug in the 486 optimized mutex operations, which had >invalid register constraints probably dating back to several older revisions in >BSD/OS before we got the code. It should be fixed now. > John It compiles now fine but panics on booting: Doing initial network setup: hostname. panic: mutex sched lock owned at ../../kern/kern_mutex.c:322 cpuid = 0; lapic.id = boot() called on cpu#0 syncing disks... Fatal double fault: eip = 0xc02b0e7d esp = 0xcafce000 ebp = 0xcafce020 cpuid = 0; lapic.id = I built another one and got a different panic: Initial rc.i386 panic: spin lock sched lock held by 0x0xc0390a01 for > 5 seconds cpuid = 1; lapic.id = 0c00 boot() called on cpu#1 syncing disks... Just frozen at this point Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New PCM changes cause panic
New changes to the sound system PCM cause a panic on current kernel when using the rsynth port. Fatal trap 18: integer divide fault while in kernel mode cpuid = 1; lapic.id = 0c00 instruction pointer = 0x8:0xc01714d1 stack pointer = 0x10:0xcb06fd90 frame pointer = 0x10:0xcb06fdb0 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 = 295 (say) trap number = 18 panic: integer divide fault cpuid = 1; lapic.id = 0c00 boot() called on cpu#1 syncing disks... Machine is frozen at this point. Manual reset needed Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fatal trap while printing under SMP
When trying to print using a current SMP kernel, I get the following: Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0c00 fault virtual address = 0xe1810412 fault code = supervisor write, page not present instruction pointer = 0x8:0xcb0a7977 stack pointer = 0x10:0xcb08cf84 frame pointer = 0x10:0xcb08cf9c 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 = 30652 (irq7: lpt0) trap number = 12 panic: page fault cpuid = 1; lapic.id = 0c00 boot() called on cpu#1 syncing disks... Printing works fine with a current non SMP kernel. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Continuing Fatal Trap 12
Jake
I applied the patch:
#define LPT_DEBUG
--- lpt.c Thu Dec 7 17:33:12 2000
+++ lpt.c.hack Thu Jan 4 00:46:41 2001
@@ -394,6 +394,7 @@
/* retrieve the ppbus irq */
BUS_READ_IVAR(ppbus, dev, PPBUS_IVAR_IRQ, &irq);
+#if 0
if (irq > 0) {
/* declare our interrupt handler */
sc->intr_resource = bus_alloc_resource(dev, SYS_RES_IRQ,
@@ -403,9 +404,12 @@
sc->sc_irq = LP_HAS_IRQ | LP_USE_IRQ | LP_ENABLE_IRQ;
device_printf(dev, "Interrupt-driven port\n");
} else {
+#endif
sc->sc_irq = 0;
device_printf(dev, "Polled port\n");
+#if 0
}
+#endif
lprintf(("irq %x %x\n", irq, sc->sc_irq));
lpt_release_ppbus(dev);
And now printing seems to work fine under SMP
Just alot of debbuging stuff when I print :
Jan 4 21:52:45 pozo /boot/kernel/kernel:
ppp
Jan 4 21:52:45 pozo /boot/kernel/kernel: pclosed.
Jan 4 21:52:45 pozo /boot/kernel/kernel: pclosed.
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
libc_r broken
libc_r won't compile since changes made last night. (libc_r)504}make cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_accept.c -o uthread_accept.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c -o uthread_aio_suspend.o /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' *** Error code 1 Stop in /usr/src/lib/libc_r. This also has other ramifications if you build the new libc from last night and are using a threaded version of perl Kernel build directory is ../../compile/pro2 rm -f *.o *.so *.So *.ko *.s eddep errs kernel.debug kernel linterrs makelinks param.c setdef[01].c setdefs.h tags vers.c vnode_if.c vnode_if.h device_if.c bus_if.c linker_if.c pci_if.c pcib_if.c ppbus_if.c ac97_if.c channel_if.c feeder_if.c mixer_if.c isa_if.c device_if.h bus_if.h linker_if.h pci_if.h pcib_if.h ppbus_if.h ac97_if.h channel_if.h feeder_if.h mixer_if.h isa_if.h aicasm aicasm_gram.c aicasm_scan.c y.tab.h aic7xxx_seq.h aic7xxx_reg.h cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/genassym.c sh ../../kern/genassym.sh genassym.o > assym.s rm -f param.c cp ../../conf/param.c . perl5 ../../kern/vnode_if.pl -h ../../kern/vnode_if.src /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol "__sys__exit" *** Error code 1 Stop in /usr/src/sys/compile/pro2. Output from perl -version: (libc_r)506}perl -version This is perl, v5.6.0 built for i386-freebsd-thread (with 1 registered patch, see perl -V for more detail) Copyright 1987-2000, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5.0 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page. /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol "__sys__exit" Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc_r broken
At 02:02 PM 1/29/2001 -0500, Daniel Eischen wrote: >On Mon, 29 Jan 2001, Manfred Antar wrote: >> libc_r won't compile since changes made last night. >> (libc_r)504}make >> cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include >-DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread >-I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c >/usr/src/lib/libc_r/uthread/uthread_accept.c -o uthread_accept.o >> cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include >-DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread >-I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c >/usr/src/lib/libc_r/uthread/uthread_aio_suspend.c -o uthread_aio_suspend.o >> /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': >> /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of >`__sys_aio_suspend' discards qualifiers from pointer target type >> /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for >argument 3 of `__sys_aio_suspend' >> *** Error code 1 >> >> Stop in /usr/src/lib/libc_r. > >Sorry, I committed (I think) the wrong copy of pthread_private.h. >I just committed a fix for this. I'm away from my -current box >right now, so let me know if this doesn't work. > >-- >Dan Eischen Dan It works now with the new pthread_private.h. Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current SMP Kernel panics
A current kernel built 10 mins ago form fresh cvsup panics: APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 IPsec: Initialized Security Association Processing. panic: mutex sched lock not owned at ../../kern/kern_synch.c:175 cpuid = 0; lapic.id = syncing disks... done Uptime: 0s dpt0: Shutting down (mode 100) HBA. Please wait... dpt0: Controller was warned of shutdown and is now disabled Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP Kernel panics
At 04:20 PM 2/10/2001 +0100, Jeroen Ruigrok/Asmodai wrote:
>-On [20010210 06:26], Manfred Antar ([EMAIL PROTECTED]) wrote:
>>APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0
>>IPsec: Initialized Security Association Processing.
>>panic: mutex sched lock not owned at ../../kern/kern_synch.c:175
>
>Me too.
>
>166 static void
>167 roundrobin(arg)
>168 void *arg;
>169 {
>170 #ifndef SMP
>171 struct proc *p = curproc; /* XXX */
>172 #endif
>173
>174 #ifdef SMP
>175 need_resched();
>176 forward_roundrobin();
>177 #else
>178 if (p == PCPU_GET(idleproc) || RTP_PRIO_NEED_RR(p->p_rtprio.type)
> )
>179 need_resched();
>180 #endif
>181
>182 callout_reset(&roundrobin_callout, sched_quantum, roundrobin, NUL
>L);
>183 }
>
>Should it become:
>
>#ifdef SMP
>mtx_lock_spin(&sched_lock);
>need_resched();
>forward_roundrobin();
>mtx_unlock_spin(&sched_lock);
>#else
>
>?
>
>I cannot test it yet, need to reanimate my testbox first.
>
I tried the above and the machine just hangs when it comes to:
SMP: AP CPU # 1 Launched!
:(
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: installworld gotchas
At 11:47 AM 2/12/2001 -0500, Garrett Wollman wrote: >< said: > >> The major number has already been bumped, I thought. If this is true >> then we've only broken compatibility with older versions of -current >> after the version number was bumped but before this change, right? > >However, this may turn out to be so painful that we need to bump it >again. > >-GAWollman > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message I just did a make build world on current and was looking forward to rebuilding all the ports :) Should I wait until the version bump then try again. I realize that if I do a install world now I'll have to rebuild almost everything X,apache.bind,etc,etc. I just don't want to do it twice in two days. I guess I'll wait. I already experienced some of the ramifications from just installing a current libc.so.5. Fortunately i kept a backup copy of the old one :) Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic @r207433: "System call fork returning with the following locks held"
At 02:21 PM 4/30/2010, K. Macy wrote: >On Fri, Apr 30, 2010 at 12:38 PM, K. Macy wrote: >>> Sadly, it doesn't do it for me .. lockd start-up causes a panic on a >>> "sleeping thread". Do I need to do a buildworld as well as kernel? >>> >> >> We're calling vm_pageout_flush with the page queue lock held in >> vm_object_page_collect_flush. I'll have a fix in soon. > >Please try updating to 207451 > >Thanks, >Kip >___ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > >-- >This message has been scanned for viruses and >dangerous content by MailScanner, and is >believed to be clean. I'm getting this from just rebuilt kernel: Starting dbus. Starting hald. Configuring syscons: blanktime. Starting clamav_clamd. Starting clamav_freshclam. Waiting for clamd socket.. Starting clamav_milter. Waiting for clamav-milter socket.. 60.. Starting denyhosts. Sleeping thread (tid 100058, pid 19) owns a non-sleepable lock sched_switch(c7174d80,0,104,a3b9b2bc,5b,...) at sched_switch+0x1df mi_switch(104,0,c7174d80,0,db35b4f4,...) at mi_switch+0x12a sleepq_switch(c7174d80,0,c0b157ee,260,0,...) at sleepq_switch+0xcb sleepq_wait(db317b94,4c,c0b18293,0,0,...) at sleepq_wait+0x39 _sleep(db317b94,c70066dc,4c,c0b18293,0,...) at _sleep+0x2a2 bwait(db317b94,4c,c0b18293,db317b94,db35b5a0,...) at bwait+0x8f bufwait(db317b94,0,0,0,0,...) at bufwait+0x28 breadn(c7836220,1,0,4000,0,...) at breadn+0xf3 bread(c7836220,1,0,4000,0,...) at bread+0x4c ffs_balloc_ufs2(c7836220,6000,0,1000,c700bc00,...) at ffs_balloc_ufs2+0xe71 ffs_write(db35b930,c0bbb1ec,0,0,db35b874,...) at ffs_write+0x3f5 VOP_WRITE_APV(c0b87ae0,db35b930,0,0,2000,...) at VOP_WRITE_APV+0xa6 vnode_pager_generic_putpages(c7836220,db35ba40,1000,c,db35b9f0,...) at vnode_pager_generic_putpages+0x300 vop_stdputpages(db35b9a0,db35b9cc,c08e75e9,c0b87ae0,db35b9a0,...) at vop_stdputpages+0x30 VOP_PUTPAGES_APV(c0b87ae0,db35b9a0,c066dc10,c7261c5c,c0b9ce00,...) at VOP_PUTPAGES_APV+0x47 vnode_pager_putpages(c7835c38,db35ba40,1,c,db35b9f0,...) at vnode_pager_putpages+0xa9 vm_pageout_flush(db35ba40,1,c,c08dd65c,0,...) at vm_pageout_flush+0x1c7 vm_object_page_collect_flush(c,6,0,82b,c7836220,...) at vm_object_page_collect_flush+0x5f3 vm_object_page_clean(c7835c38,0,0,0,0,...) at vm_object_page_clean+0x2ef vfs_msync(c7414ca8,2,2,c0b9cca0,c7489550,...) at vfs_msync+0x21a sync_fsync(db35bc74,db35bc94,c071062d,c0b76640,db35bc74,...) at sync_fsync+0x22a VOP_FSYNC_APV(c0b76640,db35bc74,c0b19a0d,6a5,c063e92e,...) at VOP_FSYNC_APV+0x42 sync_vnode(c0bbe4b4,c0bbe4a0,3e8,c73f8550,4e20,...) at sync_vnode+0x1bd sched_sync(0,db35bd38,fffa7f7f,,d6fbf6ad,...) at sched_sync+0x2c2 fork_exit(c0710760,0,db35bd38) at fork_exit+0x90 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xdb35bd70, ebp = 0 --- panic: sleeping thread KDB: enter: panic [ thread pid 1789 tid 100114 ] Stopped at kdb_enter+0x3a: movl$0,kdb_why db> == || n...@pozo.com || || Ph. (415) 681-6235 || == -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Changes to ahc driver broke kernel
There were some changes made to ahc driver made on 1/13/99 And i can no longer boot a current kernel A kernel from 1/12/99 works fine When booting after : SMP: AP CPU #1 Launched It stalls for awhile and then I get these messages (probe4:ahc0:0:4:0) SCB 0x5 timed out in message phase SEQADDR == 0x155 (probe4:ahc0:0:4:0) BDR message in message buffer ahc0: Issued Channel A Bus Reset. 3 SCBs aborted and on and on This is a Intel PR440FX with builtin adaptec scsi and dual PPro processors Also on board is a DPT SCSI PM2124A Raid controller (no RAID drives). The adaptec usually has a cdrom hooked to it, sometime a exabyte and aux harddrive FreeBSD is installed on the disk controlled by the DPT Thanks Manfred = ||man...@netcom.com|| ||p...@infinex.com || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
At 10:34 AM 1/23/99 +0800, Peter Wemm wrote:
>Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
>lost):
>
>panic: found dirty cache page 0xf046f1c0
>mp_lock = 0101; cpuid = 1; lapic.id = 0100
>Debugger("panic")
>Stopped at Debugger+0x37: movl$0,in_Debugger
>db> trace
>Debugger(f01f1806) at Debugger+0x37
>panic(f01fbb50,f046f1c0,0,80,f45cbb20) at panic+0xa4
>vm_page_alloc(f45f6f68,80,3,0,80) at vm_page_alloc+0x114
>vm_page_grab(f45f6f68,80,83,0,80) at vm_page_grab+0x8d
>_pmap_allocpte(f45cbb20,80,201df000,201df000,2a86000) at _pmap_allocpte+0x19
>pmap_allocpte(f45cbb20,201df000,f02c4df4,201df000,f45cbac0) at
>pmap_allocpte+0x53
>pmap_enter(f45cbb20,201df000,2a86000,5,0) at pmap_enter+0x3d
>vm_fault(f45cbac0,201df000,1,0,f4195180) at vm_fault+0x891
>trap_pfault(f45f9fbc,1,201df236) at trap_pfault+0xf2
>trap(27,27,,5,efbfad38) at trap+0x1c2
>calltrap() at calltrap+0x3c
>--- trap 0xc, eip = 0x201df236, esp = 0xefbfac4c, ebp = 0xefbfad38 ---
>db> c
>boot() called on cpu#1
>
>syncing disks... 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232
>232
> 232 232 232 232 giving up
>1: dev:, flags:20020034, blkno:1057008, lblkno:0
>[..]
>
>This was compiled two houts ago from absolute latest -current:
>FreeBSD spinner.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #385:
>Sat Jan 23 08:38:42 WST 1999
>pe...@spinner.netplex.com.au:/home/src/sys/compile/SPINNER i386
>
>My other SMP machine (2xPPro200) seems to be running fine:
>FreeBSD beast.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #267:
>Thu Jan 21 21:39:45 WST 1999
>pe...@beast.netplex.com.au:/home/src/sys/compile/BEAST i386
>
>Cheers,
>-Peter
>
I just got the same thing doing a make -j8 world
Machine is a dual pentium pro Intel PR440FX
This must be from the recent vm changes as I could make -j8 world
continually a
few days ago without problem. This is the second time it happened to me
the first time I was running X so I couldn't see the debugger message .
This time without X I got the :
panic: found dirty cache page
Manfred
=
||man...@netcom.com||
||p...@infinex.com ||
||Ph. (415) 681-6235||
=
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! (kernel thread support)
At 06:41 PM 1/25/99 -0800, Julian Elischer wrote: >The Linuxthreads changes in the system that have been optioned out for a >while have been enabled after testing by many people. > >this will require a recompile of at least PS and probably the usual >culprits, (libkvm etc) (unless of course you've already been running with >the support turned on.) > >julian > Does this mean I can take -DCOMPAT_LINUX_THREADS out of /etc/make.conf ? Thanks Manfred = ||man...@netcom.com|| ||p...@infinex.com || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gcc
At 01:28 PM 3/1/99 -0800, Jordan K. Hubbard wrote: I can generally build a kernel with EGCS, if I change how the .text and .data are laid out for initialized data. It seems that the initialization code makes assumptions about the order or layout of the initialization data. Once the stuff is made to act more like the version of GCC that FreeBSD uses, the kernel will most often build and work. It really does appear to be a simple matter of first making egcs "take over" the system compiler: # cd /usr/ports/lang/egcs # make all install PREFIX=/usr # ln -fs /usr/bin/eg++ /usr/bin/c++ # ln -fs /usr/bin/egcc /usr/bin/cc # cd /usr/src remove cc from /usr/src/gnu/usr.bin/Makefile SUBDIR list remove libstdc++ and libobjc from /usr/src/gnu/lib/Makefile SUBDIR list Then make the world and the kernel. I also haven't noticed that the executables are any smaller or larger either way, and I've captured a fair amount of "cc -v" output to ensure that egcs is, in fact, the compiler being used. :) - Jordan Doesn't this just rebuild the standard gcc compiler in /usr/obj/usr/tmp/bin as part of the tools build, then use that compiler to build world. The first builds are done with egcs then it moves over to gcc to build the world. by removing the above from the Makfiles just prevents them from getting built and installed in the final build. when I do /usr/obj/usr/src/tmp/bin/cc --version it comes out gcc 2.7.2.1 Or am I missing something here ?? = ||man...@pacbell.net || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: X problems using egcs as compiler
At 04:28 PM 4/3/99 -0800, David O'Brien wrote: Better yet, can we just run with this today instead of tomorrow? Can someone with a FAST machine do a CVSup from Freefall and `make world' to verify that it is not broken? My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make world'. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message I started a Make world about 1 hour ago with current as of then sources. It should be done in about 30min's. The only thing is I don't build xntpd but every thing else is built. I'll post when completed Manfred = ||man...@pacbell.net || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: bge0 does not work anymore
At 09:06 AM 10/17/2010, Rainer Hurling wrote: >I am using FreeBSD 9.0-CURRENT (amd64) on a DELL Latitude D630. With todays >kernel the driver 'bge0' does not work anymore. With kernel from October 9th >it does. > >The network controller is a Broadcom NetXtreme Gigabit Ethernet, ASIC rev. >0x00a002; CHIP ID 0xa0002; ASIC REV 0x0a; CHIP REV 0xa0; PCI-E. > >The entry in /etc/rc.conf is 'ifconfig_bge0="DHCP". > >Does anyone else observe this behaviour? Is there something I can try? > >Thanks in advance, >Rainer Hurling Same here, the last time it worked was Oct 14. with Current source. uname -a : FreeBSD pozo.com 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Thu Oct 14 14:13:47 PDT 2010 r...@pozo.com:/sys/i386/compile/COMPAQ i386 i have ifconfig_bge0="inet 192.168.0.5 netmask 255.255.255.0" in rc.conf == || n...@pozo.com || || Ph. (415) 681-6235 || == -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can't buildworld since Clang update
At 07:07 AM 2/21/2011, Dimitry Andric wrote:
>On 2011-02-21 11:33, Olivier Smedts wrote:
>>I can't buildworld with Clang since the last update.
>...
>>%cat /etc/src.conf
>>.if !defined(CC) || ${CC} == "cc"
>>CC=clang
>>.endif
>>.if !defined(CXX) || ${CXX} == "c++"
>>CXX=clang++
>>.endif
>># Don't die on warnings
>>NO_WERROR=
>>WERROR=
>
>Try putting these lines in /etc/make.conf instead. Unfortunately, due
>to the way src.conf is read, it isn't usable for the few cases we need
>to disable clang's integrated assembler, using the '-no-integrated-as'
>option.
>
>
>>/tmp/cc-VUyvc6.s:6:1: warning: ignoring directive for now
>>.intel_syntax noprefix
>>^
>
>I too am having trouble with buildworld
>I switched back to standard /usr/bin/cc, but make buildworld stops here:
>
>c++ -O2 -pipe
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I.
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
> -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
>-D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"i386-undermydesk-freebsd9.0\"
>-I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -c
>/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/system_error.cpp
>building static llvmsupport library
>ranlib libllvmsupport.a
>===> lib/clang/libllvmsystem (obj,depend,all,install)
>cd: can't cd to /usr/src/lib/clang/libllvmsystem
>*** Error code 2
>
>Stop in /usr/src.
>*** Error code 1
>
>Stop in /usr/src.
>*** Error code 1
>
>Stop in /usr/src.
>
>Last night i deleted /usr/src and did a fresh cvsup
>Still same problem
>
>==
>|| n...@pozo.com ||
>|| Ph. (415) 681-6235 ||
>==
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can't buildworld since Clang update
At 07:07 AM 2/21/2011, Dimitry Andric wrote:
>On 2011-02-21 11:33, Olivier Smedts wrote:
>>I can't buildworld with Clang since the last update.
>...
>>%cat /etc/src.conf
>>.if !defined(CC) || ${CC} == "cc"
>>CC=clang
>>.endif
>>.if !defined(CXX) || ${CXX} == "c++"
>>CXX=clang++
>>.endif
>># Don't die on warnings
>>NO_WERROR=
>>WERROR=
>
>Try putting these lines in /etc/make.conf instead. Unfortunately, due
>to the way src.conf is read, it isn't usable for the few cases we need
>to disable clang's integrated assembler, using the '-no-integrated-as'
>option.
>
>
>>/tmp/cc-VUyvc6.s:6:1: warning: ignoring directive for now
>>.intel_syntax noprefix
>>^
>
>I too am having trouble with buildworld
>I switched back to standard /usr/bin/cc, but make buildworld stops here:
>
>c++ -O2 -pipe
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I.
>-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
> -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
>-D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"i386-undermydesk-freebsd9.0\"
>-I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -c
>/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/system_error.cpp
>building static llvmsupport library
>ranlib libllvmsupport.a
>===> lib/clang/libllvmsystem (obj,depend,all,install)
>cd: can't cd to /usr/src/lib/clang/libllvmsystem
>*** Error code 2
>
>Stop in /usr/src.
>*** Error code 1
>
>Stop in /usr/src.
>*** Error code 1
>
>Stop in /usr/src.
>
>Last night i deleted /usr/src and did a fresh cvsup
>Still same problem
Turns out that cvsup10.us.freebsd.org which i was using is not up to date.
I'm using cvsup.us.freebsd.org now and am getting many new updates.
>==
>|| n...@pozo.com ||
>|| Ph. (415) 681-6235 ||
>==
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: make buildworld broken in telnetd
At 01:03 AM 09/04/2003 +0900, Shin-ichi Yoshimoto wrote: >Subject: make buildworld broken in telnetd, >On Wed, 3 Sep 2003 19:14:10 +0900, Shin-ichi Yoshimoto wrote: >> make buildworld broken in libexec/telnetd. > >I tried to backout share/bsd.lib.mk from rev.1.152 to rev 1.151, >buildworld is ok. Is the rev.1.152 anything wrong ? > >-- >Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]> >http://diary.waishi.jp/~yosimoto/diary/ >___ >[EMAIL PROTECTED] mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "[EMAIL PROTECTED]" I think 1.152 is broken. I did a make world and install world. I rebooted and login and sshd couldn't find pam_nologin.so and it was right there in /usr/lib. I had to restore the pam libs and sshd and login from tape before I could login to the machine. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can't log in! openpam_load_module failures on strcpy, cgetclose
At 01:35 PM 09/06/2003 -0700, Aaron Smith wrote: >Hi everyone. login and sshd are both failing for me after a make world on >current. I have mergemaster'd, rebuilt world, ad infinitum. I've compared >/etc/pam.d with the source tree version and they're the same. > >I instrumented openpam_dynamic, and login is failing on 'strcpy': > >login: in openpam_dynamic(): pam_nologin.so: /usr/lib/pam_nologin.so: >Undefined symbol "strcpy" >login: in openpam_load_module(): no pam_nologin.so found >login: pam_start(): system error > >for sshd the failure is on 'cgetclose': > >sshd: in openpam_dynamic(): pam_nologin.so: /usr/lib/pam_nologin.so: >Undefined symbol "cgetclose" >sshd: in openpam_load_module(): no pam_nologin.so found >sshd: fatal: PAM: initialisation failed > >Now, there are T symbols for both of these in the respective binaries, >according to nm (at least before they are stripped). So just in case >stripping was an issue I figured I'd try unstripped binaries and rebuilt >them. No luck. > >Can anyone help me out? > >Thanks, >--Aaron >___ >[EMAIL PROTECTED] mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "[EMAIL PROTECTED]" What version of bsd.lib.mk are you using ? There was a problem with version 1.152 From CVS log: Emergency backout of rev 1.152. This is a 100% guaranteed way to totally hose your system. You end up with just about everything statically linked (except for libpam.so), which then causes all the pam users to fail. eg: login, sshd, su etc all stop working because dlopen no longer works because there is no libc.so in memory anymore. gcc passes -L/usr/lib to ld. The /usr/lib/libxxx.so symlink is *not* a compatability link. It is actually the primary link. There should be no symlinks in /lib at all. Only /lib/libXX.so.Y. [EMAIL PROTECTED]:27pm]/usr/bin-104> file yppasswd yppasswd: setuid ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.1.1, dynamically linked (uses shared libs), stripped [EMAIL PROTECTED]:27pm]/usr/bin-105> ldd yppasswd yppasswd: libpam.so.2 => /usr/lib/libpam.so.2 (0x280d1000) [EMAIL PROTECTED]:28pm]/usr/bin-106> Note no libc.so.5. Hence libpam.so.2 has unresolved dependencies. I believe this is also the cause of the recent buildworld failures when pam_krb5.so references -lcrypto stuff etc and when librpcsvc.so references des_setparity() etc. This change could not possibly have worked, unless there are other missing changes to the gcc configuration. It won't work with ports versions of gcc either. You need to get 1.151 or 1.153 and rebuild world == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
