11.0: Fatal trap 12: page fault while in kernel mode
http://eis.bris.ac.uk/~mexas/core.txt.9 vmcore.9 is >450MB: http://cmplx.uk/pic/vmcore.9 Thanks Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
webcamd panic - is it just me?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215000 I think this started after moving from 10.3 to 11.0. Does nobody else see this panic? Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: net-im/skype4 under FreeBSD 10.3
>Has anybody tried net-im/skype4 under FreeBSD 10.3(-BETA[0-9])?? >Seems like net-im/skype4 missing some dependencies and if it's >satisfied net-im/skype4 hangs after start. >linprocfs mounting doesn't help. >I installed them all from the ports tree. >Any experience? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202780 Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 10-stable about r292594: rescue crunchide *.lo unknown executable format
>From j...@baldwin.cx Sat Jan 30 02:00:53 2016 > >While ia64 is mostly abandoned, this build failure was fixed a few weeks ago: > > >r292885 | emaste | 2015-12-29 12:36:11 -0800 (Tue, 29 Dec 2015) | 4 lines > >crunchide: Restore IA-64 support accidentally lost in r292421 mismerge > >Reported by:ngie John, thank you, but I think it's time to say goodbye to FreeBSD/ia64 for me. Thanks Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 10-stable about r292594: rescue crunchide *.lo unknown executable format
>From mar...@xcllnt.net Thu Jan 28 06:17:28 2016 > >Hi Anton, > >I haven=E2=80=99t done anything with ia64 for over a year and frankly I = >lack the time >to catch up and fix stuff. So, yeah, maybe just consider ia64 abandoned. Marcel, thanks. I'll power it down then... See you Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ia64 10-stable about r292594: rescue crunchide *.lo unknown executable format
I asked about this already in stable@ and ia64@. Got no reply. Perhaps ia64 has been abandoned in 10-stable too? If so, I'd like to know. If not, I'm getting: # pwd /usr/obj/usr/src/rescue/rescue # crunchide -k _crunched_chio_stub cat.lo cat.lo: unknown executable format # crunchide -k _crunched_chio_stub chflags.lo chflags.lo: unknown executable format # crunchide -k _crunched_chio_stub chio.lo chio.lo: unknown executable format # file *lo cat.lo: ELF 64-bit LSB relocatable, IA-64, version 1 (FreeBSD), not stripped chflags.lo: ELF 64-bit LSB relocatable, IA-64, version 1 (FreeBSD), not stripped chio.lo:ELF 64-bit LSB relocatable, IA-64, version 1 (FreeBSD), not stripped # file /usr/bin/crunchide /usr/bin/crunchide: ELF 64-bit LSB executable, IA-64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 10.2 (1002504), stripped # This is on 10.2-STABLE #20 r292594. I tried to buildworld up to r294823, and back to r291000, all with the same error. I cannot even build the same revision as the one I'm running now. I've deleted /usr/obj completely,- still the same. Please advise Thanks Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
r294085 10-stable ia64: cat.lo: unknown executable format
Updating ia64 following recent multiple SA: r294085 10-stable buildworld: cc -O2 -pipe -c chown_stub.c -o chown_stub.o cc -O2 -pipe -c iscsid_stub.c -o iscsid_stub.o ld -dc -r -o cat.lo cat_stub.o /usr/obj/usr/src/rescue/rescue//usr/src/bin/cat/cat.o crunchide -k _crunched_cat_stub cat.lo cat.lo: unknown executable format *** [cat.lo] Error code 1 make[5]: stopped in /usr/obj/usr/src/rescue/rescue 1 error Thanks Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: urtwn regression(?) from 10.2 to current r291431
>From h...@selasky.org Sun Dec 6 14:41:27 2015 > >On 12/06/15 15:14, Anton Shterenlikht wrote: >> I posted this about a week ago: >> >> http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html >> >> The problem is that urtwn stopped >> working in current r291431. >> >> I did more testing with the same revision, >> and sometimes it would work, but extremely >> slowly, and sometimes seemingly associate >> but get an address of 0.0.0.0. >> >> I now installed 10.2-RELEASE-p8 and >> the urtwn works fine, no issues at all. >> >> Does this look like a bug at some recent >> current revision? Should I file a PR? >> >> I's just I recall there have been major >> chages to wlan, so perphaps I'm forgetting >> to change the config in recent current? >> >> Please advise >> >> Anton > >Hi, > >There is work ongoing in the WLAN drivers. Did you try the latest -current? > >--HPS r291431 was about a week ago. Will try latest -current later today. Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
urtwn regression(?) from 10.2 to current r291431
I posted this about a week ago: http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html The problem is that urtwn stopped working in current r291431. I did more testing with the same revision, and sometimes it would work, but extremely slowly, and sometimes seemingly associate but get an address of 0.0.0.0. I now installed 10.2-RELEASE-p8 and the urtwn works fine, no issues at all. Does this look like a bug at some recent current revision? Should I file a PR? I's just I recall there have been major chages to wlan, so perphaps I'm forgetting to change the config in recent current? Please advise Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ia64: pcpu.h: No such file or directory
On ia64 10.2-STABLE #17 r289997 I get a panic as soon as I start poudriere bulk I see in core.txt: http://eis.bris.ac.uk/~mexas/core.txt Reading symbols from /boot/kernel/nullfs.ko.symbols...done. Loaded symbols for /boot/kernel/nullfs.ko.symbols #0 doadump (textdump=18810336) at pcpu.h:85 85 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=18810336) at pcpu.h:85 If I remember correctly poudriere loads nullfs. Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ia64 10.2-stable r289997: fatal kernel trap
I haven't finished the dump yet, but in case this is a known issue, I updated ia64 to 10.2-STABLE #16 r289997. On reboot in multi-user mode: Starting file system checks: /dev/da0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p2: clean, 10613586 free (169426 frags, 1305520 blocks, 1.0% fragmentation) Mounting local file systems:. Writing entropy file:. Setting hostname: fatal kernel trap (cpu 0): trap vector = 0x14 (Page Not Present) cr.iip = 0xa1e72830 cr.ipsr = 0x1210080a6018 (ac,mfl,ic,i,dt,dfh,rt,cpl=0,it,ri=1,bn) cr.isr = 0xa04 (code=0,vector=0,r,ei=1,ed) cr.ifa = 0x101a40001 curthread = 0xe000122716d0 pid = 173, comm = kldload panic: trap cpuid = 0 KDB: stack backtrace: Uptime: 9s Dumping 8172 MB (25 chunks) chunk 0: 1 pages ... ok chunk 1: 159 pages ... ok chunk 2: 256 pages ... ok chunk 3: 7680 pages ... ok chunk 4: 8192 pages ... ok chunk 5: 239734 pages ... ok chunk 6: 748 pages ... ok chunk 7: 533 pages ... ok chunk 8: 21 pages ... ok chunk 9: 1048574 pages / Thanks Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel
>From mar...@xcllnt.net Thu Sep 3 17:20:42 2015 > >To be clear: with the limits and without my patch you >can=E2=80=99t even boot right? yes, this is right. >> If I remove these, then I can boot. >>=20 >> If I try booting with -s, then I get to a hang at >> "Entering /boot/kernel=E2=80=9D: > >Is this with or without limits? >And is this with or without patch? It seems the patch made no difference. With the limits I cannot boot with or without the patch. Without the limits I can boot with or without the patch. >> /boot/kernel.old/kernel text=3D0x1110710 data=3D0xdfce8+0xa54f8 = >syms=3D[0x8+0xc29e8+0x8+0xb78f6] >> ?[37m?[44mBooting...?[m >> Entering /boot/kernel.old/kernel at 0x9ffc00010500... >> *** >> * ROM Version : 04.29 >> * ROM Date: 11/30/2007 >> * BMC Version : 04.04 > >This is not a hang. This is a machine check. After this line Entering /boot/kernel.old/kernel at 0x9ffc00010500... The machine is not responding. I've left it for hours, just to be sure. The following line appears only after a power cycle. >> Is it worth investigating what limit value will boot? > >I=E2=80=99m inclined to say that it=E2=80=99s best to remove the limits >altogether and just work with the default. If you need >different default, add them to your kernel configuration. >Set MAXTSIZ, DFLDSIZ, MAXDSIZ, DFLSSIZ and MAXSSIZ >accordingly. > >Since you lower maxdsiz and maxssiz from 1G to 512M, >you can safely leave them as is (unless you tend to have >runaway processes :-) > >You increase maxssiz from 256M to 512M, which you >probably want to keep doing to make sure you can run >the same set of processes as you do now. > >At this point in time, the only fix I=E2=80=99m willing to make >is for the size of the array that holds relocations. If >it made things better, I=E2=80=99ll commit it. If it didn=E2=80=99t, = >then >I=E2=80=99m not going to commit it. No, I don't think it made any difference. >Anything more involved will take more time than I=E2=80=99m >willing to put into ia64 at this time... sure, no problem. Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel
The kernel limits I have in /boot/loader.conf are following this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156900 #kern.dfldsiz=536748032 # default soft limit for process data #kern.dflssiz=536748032 # default soft limit for stack # hard limits #kern.maxdsiz=536748032 # hard limit for process data #kern.maxssiz=536748032 # hard limit for stack #kern.maxtsiz=536748032 # hard limit for text size If I leave these in, then with Marcel's patch I get to mountroot> prompt, and then panic. If I remove these, then I can boot. If I try booting with -s, then I get to a hang at "Entering /boot/kernel": /boot/kernel.old/kernel text=0x1110710 data=0xdfce8+0xa54f8 syms=[0x8+0xc29e8+0x8+0xb78f6] ?[37m?[44mBooting...?[m Entering /boot/kernel.old/kernel at 0x9ffc00010500... *** * ROM Version : 04.29 * ROM Date: 11/30/2007 * BMC Version : 04.04 Is it worth investigating what limit value will boot? Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel
>From mar...@xcllnt.net Fri Aug 28 23:15:06 2015 > > >> On Aug 28, 2015, at 3:35 AM, Konstantin Belousov = >wrote: >>=20 >> Might be, try the latest stable/10 kernel with the problematic = >revision >> r286316 reversed ? This might add more points to the Marcel' note = >about >> some static relocation table processed early. > >I built a kernel off of revision 286315 and got this: > > eris% objdump -R kernel | grep FPTR64LSB | wc -l > 5377 > >We only reserve room for 4096 relocations, so we=E2=80=99re over >as it is. > >A kernel off of revision 286316 gave me this: > eris% objdump -R kernel | grep FPTR64LSB | wc -l > 5377 > >Same. Odd, but ok. It=E2=80=99s possible that the memory layout >changed such that we now scribble over something that=E2=80=99s >important. > >To be sure: Anton can you apply the following patch and >tell me if it makes a difference. It doubles the space >we set aside for relocations. > >Index: sys/ia64/ia64/locore.S >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >--- sys/ia64/ia64/locore.S (revision 286316) >+++ sys/ia64/ia64/locore.S (working copy) >@@ -357,5 +357,5 @@ > .align 16 > .global fptr_storage > fptr_storage: >- .space 4096*16 // XXX >+ .space 8192*16 // XXX > fptr_storage_end: So, 286316 boots ok without the patch if I remove everything from /boot/loader.conf. With the patch, and with kern.dfldsiz=536748032 # default soft limit for process data kern.dflssiz=536748032 # default soft limit for stack # hard limits kern.maxdsiz=536748032 # hard limit for process data kern.maxssiz=536748032 # hard limit for stack kern.maxtsiz=536748032 # hard limit for text size First time round I got: da1: Command Queueing enabled da1: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) Loader variables: Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> And following an auto-reboot: OK boot -s ?[37m?[44mBooting...?[m Entering /boot/kernel/kernel at 0x9ffc00010500... I'll do a few more tries now. Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel
>From me...@bristol.ac.uk Fri Aug 28 11:34:20 2015 > >What about my loader.conf: > ># cat /boot/loader.conf >zfs_load="YES" ># soft limits >kern.dfldsiz=536748032 # default soft limit for process data >kern.dflssiz=536748032 # default soft limit for stack ># hard limits >kern.maxdsiz=536748032 # hard limit for process data >kern.maxssiz=536748032 # hard limit for stack >kern.maxtsiz=536748032 # hard limit for text size ># processes may not exceed these limits. ># > >My memory: > >real memory = 8589934592 (8192 MB) >avail memory = 8387649536 (7999 MB) > >I'll try disabling all these settings in loader.conf >and see if makes a difference. >But these settings have been there for a few years >with no problems. > >Anton yes, this does help: # uname -a FreeBSD 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #12 r286316: Thu Aug 27 11:03:44 BST 2015 r...@mech-as28.men.bris.ac.uk:/usr/obj/usr/src/sys/GENERIC ia64 # I guess I now need to check if it's zfs of the limits. Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel
>From kostik...@gmail.com Thu Aug 27 18:22:37 2015 > >On Thu, Aug 27, 2015 at 01:12:16PM +0100, Anton Shterenlikht wrote: >> ia64 stable/10 r286315 boots, but >> r286316 hangs at "Entering /boot/kernel/kernel". >> >> Please advise > >To state an obvious thing. The commit which you pointed to, changes >the code which is not executed at that early kernel boot stage. The >revision cannot cause the consequences you described. yes, I'm surprised too. >I think that you either have build-environment issue which randomly pops >up, or there is some other boot-time issue which is sporadic. The only >suggestion I have, try many boots with kernels which look either good >or bad, I would be not surprised if statistic would be completely >different from binary good/bad outcome. > >Otherwise, I do not have an idea. > I doubt it's a random or a sporadic issue. I did a bisection, as suggested, during which I built world/kernel on 7 revisions, and when I narrowed it down to <50, a further 4 kernels. All kernels <=286315 boot, all kernels >= 286316 do not. I think if it were something random, it wouldn't be such a clear cut picture. What about my loader.conf: # cat /boot/loader.conf zfs_load="YES" # soft limits kern.dfldsiz=536748032 # default soft limit for process data kern.dflssiz=536748032 # default soft limit for stack # hard limits kern.maxdsiz=536748032 # hard limit for process data kern.maxssiz=536748032 # hard limit for stack kern.maxtsiz=536748032 # hard limit for text size # processes may not exceed these limits. # My memory: real memory = 8589934592 (8192 MB) avail memory = 8387649536 (7999 MB) I'll try disabling all these settings in loader.conf and see if makes a difference. But these settings have been there for a few years with no problems. Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel
ia64 stable/10 r286315 boots, but r286316 hangs at "Entering /boot/kernel/kernel". Please advise Thanks Anton P.S. This is a continuation of http://lists.freebsd.org/pipermail/freebsd-stable/2015-August/083203.html However, since I now found the revision that broke the boot, I decided to start a new thread. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 regression from r285809 to 286952: kernel does not boot
>From s...@zxy.spb.ru Mon Aug 24 14:49:31 2015
>On Mon, Aug 24, 2015 at 01:53:52PM +0100, Anton Shterenlikht wrote:
>
>> narrowed down a bit:
>>
>> good: r285809
>> bad: r286380
>>
>> Any hint to augment bisection?
>
>r285863
>r285951
>r285967
>r286055
>r286145
>r286193
>r286216
>r286306
>r286322
>r286362
No:
good: r286315
bad: r286316
# svn diff -r 286315:286316
Index: sys/netinet6/in6.c
===
--- sys/netinet6/in6.c (revision 286315)
+++ sys/netinet6/in6.c (revision 286316)
@@ -2651,6 +2651,7 @@
if (!(lle->la_flags & LLE_IFADDR) || (flags & LLE_IFADDR)) {
LLE_WLOCK(lle);
lle->la_flags |= LLE_DELETED;
+ EVENTHANDLER_INVOKE(lle_event, lle, LLENTRY_DELETED);
#ifdef DIAGNOSTIC
log(LOG_INFO, "ifaddr cache = %p is deleted\n", lle);
#endif
Index: .
===
--- . (revision 286315)
+++ . (revision 286316)
Property changes on: .
___
Modified: svn:mergeinfo
Merged /head:r285710
#
I'll now double check this conclusion.
Anton
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 regression from r285809 to 286952: kernel does not boot
narrowed down a bit: good: r285809 bad: r286380 Any hint to augment bisection? Thanks Anton On 23/08/2015, Marcel Moolenaar wrote: > >> On Aug 23, 2015, at 7:51 AM, Anton Shterenlikht wrote: >> >> I'm not sure if ia64 list is still operational, so >> post here. >> >> ia64 r285809 10-STABLE works fine. >> I updated to r286952, buildworld, buildkernel, installkernel, >> reboot, boot -s, and I get stuck with: >> >> FreeBSD/ia64 EFI boot, Revision 3.0 >> (r...@mech-cluster241.men.bris.ac.uk, Thu May 5 11:18:40 BST 2011) >> Loading /boot/defaults/loader.conf >> /boot/kernel/kernel text=0x11107f0 data=0xdfd68+0xa54f8 >> syms=[0x8+0xc2a78+0x8+0xb7965] >> - >> Hit [Enter] to boot immediately, or any other key for command prompt. >> Booting [/boot/kernel/kernel]... >> Entering /boot/kernel/kernel at 0x9ffc00010500… > > Do you have options DDB in your kernel configuration? > If yes, can you boot without it? > > -- > Marcel Moolenaar > mar...@xcllnt.net > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ia64 regression from r285809 to 286952: kernel does not boot
>From mar...@xcllnt.net Sun Aug 23 20:40:48 2015 > >> On Aug 23, 2015, at 7:51 AM, Anton Shterenlikht = >wrote: >>=20 >> I'm not sure if ia64 list is still operational, so >> post here. >>=20 >> ia64 r285809 10-STABLE works fine. >> I updated to r286952, buildworld, buildkernel, installkernel, >> reboot, boot -s, and I get stuck with: >>=20 >> FreeBSD/ia64 EFI boot, Revision 3.0 >> (r...@mech-cluster241.men.bris.ac.uk, Thu May 5 11:18:40 BST 2011) >> Loading /boot/defaults/loader.conf >> /boot/kernel/kernel text=3D0x11107f0 data=3D0xdfd68+0xa54f8 = >syms=3D[0x8+0xc2a78+0x8+0xb7965] >> - >> Hit [Enter] to boot immediately, or any other key for command prompt. >> Booting [/boot/kernel/kernel]... >> Entering /boot/kernel/kernel at 0x9ffc00010500=E2=80=A6 > >Do you have options DDB in your kernel configuration? >If yes, can you boot without it? This is a GENERIC kernel, so no. Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ia64 regression from r285809 to 286952: kernel does not boot
I'm not sure if ia64 list is still operational, so post here. ia64 r285809 10-STABLE works fine. I updated to r286952, buildworld, buildkernel, installkernel, reboot, boot -s, and I get stuck with: FreeBSD/ia64 EFI boot, Revision 3.0 (r...@mech-cluster241.men.bris.ac.uk, Thu May 5 11:18:40 BST 2011) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x11107f0 data=0xdfd68+0xa54f8 syms=[0x8+0xc2a78+0x8+0xb7965] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0x9ffc00010500... Have to do a power reset. Thanks Anton ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: troubles with buildworld/sendmail/sasl/clang
Kimmo Paasiala writes: > > =buildworld=== > > > > /usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/usersmtp.c:1864:8: > > error: incompatible pointer types passing 'void ()' to parameter of type > > 'void (*)(char *, bool, MAILER *, struct mailer_con_info *, ENVELOPE *)' > > [-Werror,-Wincompatible-pointer-types] > >getsasldata, NULL, XS_AUTH); > >^~~ > > /usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/sendmail.h:2519:67: note: > > passing argument to parameter here > > extern int reply __P((MAILER *, MCI *, ENVELOPE *, time_t, void > > (*)__P((char *, bool, MAILER *, MCI *, ENVELOPE *)), char **, int)); > > ^ > > /usr/obj/usr/src/tmp/usr/include/sys/cdefs.h:129:21: note: expanded from > > macro '__P' > > #define __P(protos) protos /* full-blown ANSI C */ > > ^ > > 3 errors generated. > > *** [usersmtp.o] Error code 1 > > > I can not help with the error but I really have to make this question: > Does FreeBSD really have to support pre-ANSI C compilers in 2013? I have been getting this also for at least the last two months. (There is no src.conf; make.conf is appended. Current system is: FreeBSD 10.0-CURRENT #0: Sun Dec 30 12:52:09 EST 2012 amd64 and I have cyrus-sasl-2.1.26_2 installed and working with that installation.) Respectfully, Robert Huff me too, also on amd64 -current no src.conf # cat /etc/make.conf SENDMAIL_CFLAGS+= -I/usr/local/include -DSASL=2 SENDMAIL_LDFLAGS+= -L/usr/local/lib SENDMAIL_LDADD+=-lsasl2 WITH_PKGNG=yes PERL_VERSION=5.16.2 Anton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
