RE: snd_emu10k1.ko after 6.2 to 6.3 upgrade
> What does 'nm /boot/kernel/sound.ko | grep midi' show? sound.ko seems to be OK as it was properly updated by freebsd-update: [EMAIL PROTECTED] ~]# ls -l /boot/kernel/sound.ko -r-xr-xr-x 1 root wheel 139075 Jan 21 15:42 /boot/kernel/sound.ko [EMAIL PROTECTED] ~]# sha256 /boot/kernel/sound.ko SHA256 (/boot/kernel/sound.ko) = a61572cc74e3b00088a824765d7291c91d4ff52fe8709aa77abcade626fbece8 [EMAIL PROTECTED] ~]# nm /boot/kernel/sound.ko | grep midi snd_emu10k1.ko however was not updated for some reason and it has some dependencies: [EMAIL PROTECTED] ~]# ls -l /boot/kernel/snd_emu10k1.ko -r-xr-xr-x 1 root wheel 30008 Feb 20 2007 /boot/kernel/snd_emu10k1.ko [EMAIL PROTECTED] ~]# sha256 /boot/kernel/snd_emu10k1.ko SHA256 (/boot/kernel/snd_emu10k1.ko) = 13a0e7f03d354f57517d17ea52b5c7fa5a3c153cefcbf2cf8831d91204f0b2a3 [EMAIL PROTECTED] ~]# nm /boot/kernel/snd_emu10k1.ko | grep midi 4a04 r __set_modmetadata_set_sym__mod_metadata_md_snd_emu10k1_on_midi 5090 d _mod_metadata_md_snd_emu10k1_on_midi 50a0 d _snd_emu10k1_depend_on_midi When I compile new GENERIC-based snd_emu10k1.ko, it shows no such depends: [EMAIL PROTECTED] ~]# nm /sys/i386/compile/GENERIC/modules/usr/src/sys/modules/sou nd/driver/emu10k1/snd_emu10k1.ko | grep midi Petr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.3-stable and if_re - stability problems?
On Mon, Jan 28, 2008 at 09:43:12PM +0100, Torfinn Ingolfsen wrote: > On Mon, 28 Jan 2008 17:22:16 +0900 > Pyun YongHyeon <[EMAIL PROTECTED]> wrote: > > > I think re(4) in CURRENT have fixed these issues. > > Would you try re(4) in CURRENT? > > Perhaps I was being unclear; under FreeBSD 7.x (RELENG_7) re(49 works > fine. > It is only &.3 that has problems with re(4). Ah, ok. I'll make sure to MFC the changes to RELENG_6 after more testing. > -- > Regards, > Torfinn Ingolfsen > -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fwd: [EMAIL PROTECTED]: results of the 20080125 bugathon]
Here's a repost of the message I just sent to [EMAIL PROTECTED] Followups there, please. Thanks. mcl - Forwarded message from Mark Linimon <[EMAIL PROTECTED]> - Over 30 people participated in this bugathon. Thanks to all who participated! During the 3 days, we closed around 120 PRs, and probably 50 more were set to feedback. Of course, during this time about 80 PRs came in (including some ports PRs). While the net reduction doesn't look that large, it does constitute positive progress -- a large number of stale PRs were indeed closed, and a few were committed. For our next bugathon we'll try to be more focussed on committing some of the PRs that we've already identified, and also to keep a count of PRs busted by category (which we had done before, but forgotten to get a volunteer for this time.) As part of the run-up to the bugathon, several new wiki pages were created: http://wiki.freebsd.org/Bugathons/January2008 http://wiki.freebsd.org/Bugathons/January2008/InterestingBugs http://wiki.freebsd.org/BugBusting/Resources http://wiki.freebsd.org/Bugbusting/TipsAndTricks http://wiki.freebsd.org/BugBusting/Volunteers http://wiki.freebsd.org/KernelBugTriage Please take a look at these if you're interested in coming up to speed with what we're up to. Thanks! mcl - End forwarded message - ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
Quoting Mark Linimon <[EMAIL PROTECTED]>: On Mon, Jan 28, 2008 at 04:55:01PM -0800, Jeremy Chadwick wrote: I don't agree with any port creating a file in /usr/bin, and it's safe to say others will not agree with it either. In particular, portmgr will mark such a port as BROKEN :-) or perhaps REQUIRES+= compat-6 || compat-5 :) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
On Mon, Jan 28, 2008 at 04:55:01PM -0800, Jeremy Chadwick wrote: > I don't agree with any port creating a file in /usr/bin, and it's safe > to say others will not agree with it either. In particular, portmgr will mark such a port as BROKEN :-) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
On Mon, Jan 28, 2008 at 02:41:56PM -0800, Chris H. wrote: >> Continued make deinstalls and tweaking and make && make installs >> all still fail with the same errors. I have noticed a couple of >> threads that relate to this. One indicates that copying >> www/apache13/files/patch-ae to www/apache-ssl/files/patch-az worked. >> Didn't work for me. Second one indicated that creating /usr/bin/objformat >> with the contents of objformat being >> >> #!/bin/sh >> echo elf >> >> worked for them. I'm about to try that, since it isn't possible to >> build from source a working version. I'll report back if it does. > > Whoo Hoo! Yep! That did it. > > In case you're wondering, objformat /is/ required - at leas for > www/apache13-ssl. > > So the trick is to create the following /usr/bin/objformat: > > #!/bin/sh > echo elf > > Make sure to set perms to +r +x -w > > Should I initiate a sendpr? > > Thanks to all for your comments/suggestions/advice. I don't agree with any port creating a file in /usr/bin, and it's safe to say others will not agree with it either. This needs to be fixed at the core of the port build or port configure. This should go to the freebsd-ports list, or to Clement Laforet (maintainer) directly. I've CC'd him on this matter. A PR would help and be official, but again, creating /usr/bin/objformat is a no-no. Additional point: I understand your need for 1.3, but I strongly urge you to consider 2.2 or at least 2.0 -- solely *because* of the insanities involving getting SSL to work on 1.3. We (as a hosting provider) didn't start offering SSL capability until migrating to 2.0, simply because I had dealt with getting SSL to work on 1.3 and did not want to bother with all the hackery. Take the time some day to migrate your configs to 2.0 or 2.2 and enjoy the benefits of such. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Apache13-ssl fails on 7-PRERELEASE [SOLVED]
Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Greetings, On an SMP system (2 CPU) running 7 cvsupped on 2008-01-15 with a build/install world/kernel on the same. D'ho! Forgot to mention this is on an i386. I built/installed www/apache13-ssl. It built/installed expected. However, after testing with an httpsdctl configtest, apache emitted the following: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" Commenting the offending module only caused apache to complain about the next one in the list. This is a terrible loss to the FreeBSD ports. Has anyone a suggestion/patch for this? Has anyone else experienced this problem? All of our other servers have built/ ran this version without complaint/trouble. All the conf files have been carefully crafted over many yrs. and I have no interest in using a newer version of Apache, so as to have to re-craft the configs. Thank you for all your time and consideration in this matter. P.S. I realize that this should normally be directed to apache-freebsd@ and I /did/ do so. However, after having been on the list for quite some time. It appears that I am the only one subscribed to it. Further, as this is on CURRENT, I felt that there must be some difference. As I had no trouble with this on a 6-CURRENT box/install. Thanks again. OK. After much research and trials and errors. I was able to find a solution. In spite of the man page information regarding objformat being obsolete and discontinued. It is still required (at least for a few things). As it happens, it is quite easy to overcome the problem building a /working/ www/apache13-ssl from recent src on a FreeBSD 7.0-PRERELEASE i386 box. It is a matter of creating: /usr/bin/objformat eg; # touch /usr/bin/objformat Edit /usr/bin/objformat and add the following: #!/bin/sh echo elf Now perform the following: # chmod +r +x -w /usr/bin/objformat You're done. :) Happy building! --Chris H D'OH! Forgot to add [SOLVED] to the Subject. :) --Chris H -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: vm_fault: fault on nofualt entry, addr: 81423000
On Monday 28 January 2008 01:03:45 pm Pete French wrote: > o.k., done some investigative work, and I think i have actually tracke > dodnw what is going wrong, though i do not know how to fix it. mapping > the header calls madt_map_table, which in turn calls madt_map > to do the actual mapping: > > madt_map called with pa 0x7fec7f40, offset 1, length 60 > 'off' becomes 3904, and the rounded length 4096 > pmap_kenter_temporary called with pa 0x7fec7000, offset 1 > gives va of 0x8142300 > returns 0x81423f40 > > thus the header is ending up in page 0x8142300 if I read that correctly. this > is importnat for later on. meanwhile, back at the table scanning code... > > rsdt mapped at 0x81423f40 > table offset at 0x81423f64 > count is 6 > table offset address and their contents > 0 0x81423f64 0x7fec7fe8 > 1 0x81423f68 0x7fec805c > 2 0x81423f6c 0x7fec80c4 > 3 0x81423f70 0x7fec8127 > 4 0x81423f74 0x7fec8163 > 5 0x81423f78 0x7fec8195 > > so, it probes the first table, held at 0x7fec7fe8 as indicated by > the address in 0x81423f64. this calls madt_map to map the table > > madt_map called with pa 0x7fec7fe8, offset 0, length 36 > 'off' becomes 4072, and the rounded length 8192 > pmap_kenter_temporary called with pa 0x7fec7000, offset 0 > pmap_kenter called with va 0x8142300, pa 0x7fec8000 > gives va of 0x8142200 > returns 0x81422fe8 > > code is looking for a signature of 'APIC', but this table has 'FACP', so > a call is made to madt_unmap before returning > > madt_unmap called with data 0x81422fe8, length 36 > 'off' becomes 4072, and the rounded length 8192 > pmap_kremove called with 0x81422000 > pmap_kremove called with 0x81423000 > > the function then returns 0, and the loop goes round again to look > at table entry 1. the address of the table is stored at 0x81423f68 > as you can see from the list above, and it is when it tries to access > that address that it panics. > > now preseumably the panic is correct - 0x81423f68 is in page 0x81423000, > and didn't we just unmap that ? now I dont really understand this fully, > but why is page 0x81423000 being touched at all ? shouldnt the mapped > pages be 0x81421000 and 0x81422000 instead so they don't clash with > the already mapped 0x81423000 ? The unmap function is quite correctly doing > the reverse of the map function, but maybe theres something simply going > wrong in the algorithm working out which pages to map ? I think the problem is that the header for the FACP table crossed a page boundary so we had to map 2 pages to map the header, but the code assumes only 1 page is needed so when the second page was mapped, it overlapped with the page holding the XSDT. Here's a fix: Index: madt.c === RCS file: /usr/cvs/src/sys/i386/acpica/madt.c,v retrieving revision 1.28 diff -u -r1.28 madt.c --- madt.c 11 Sep 2007 22:54:09 - 1.28 +++ madt.c 28 Jan 2008 21:25:03 - @@ -109,9 +109,11 @@ /* * Code to abuse the crashdump map to map in the tables for the early * probe. We cheat and make the following assumptions about how we - * use this KVA: page 0 is used to map in the first page of each table - * found via the RSDT or XSDT and pages 1 to n are used to map in the - * RSDT or XSDT. The offset is in pages; the length is in bytes. + * use this KVA: pages 0 and 1 are used to map in the header of each + * table found via the RSDT or XSDT and pages 2 to n are used to map + * in the RSDT or XSDT. We have to use 2 pages for the table headers + * in case a header spans a page boundary. The offset is in pages; + * the length is in bytes. */ static void * madt_map(vm_paddr_t pa, int offset, vm_offset_t length) @@ -232,7 +234,7 @@ printf("MADT: RSDP failed extended checksum\n"); return (ENXIO); } - xsdt = madt_map_table(rsdp->XsdtPhysicalAddress, 1, + xsdt = madt_map_table(rsdp->XsdtPhysicalAddress, 2, ACPI_SIG_XSDT); if (xsdt == NULL) { if (bootverbose) @@ -246,7 +248,7 @@ break; madt_unmap_table(xsdt); } else { - rsdt = madt_map_table(rsdp->RsdtPhysicalAddress, 1, + rsdt = madt_map_table(rsdp->RsdtPhysicalAddress, 2, ACPI_SIG_RSDT); if (rsdt == NULL) { if (bootverbose) -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snd_emu10k1.ko after 6.2 to 6.3 upgrade
On Friday 25 January 2008 05:30:34 pm Petr Holub wrote: > > Did you kldload sound.ko before snd_emu10k1.ko? It maybe that > freebsd-upgrade > > didn't run kldxref on your kernel dir to update the > /boot/kernel/linker.hints > > file that is used to autoload dependencies. > > Yes I did, sound.ko is loaded. Actually, I can use sound.ko from the > freebsd-update'd tree together with snd_emu10k1.ko built from source > and it works without any apparent problem. What does 'nm /boot/kernel/sound.ko | grep midi' show? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Apache13-ssl fails on 7-PRERELEASE
Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Greetings, On an SMP system (2 CPU) running 7 cvsupped on 2008-01-15 with a build/install world/kernel on the same. D'ho! Forgot to mention this is on an i386. I built/installed www/apache13-ssl. It built/installed expected. However, after testing with an httpsdctl configtest, apache emitted the following: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" Commenting the offending module only caused apache to complain about the next one in the list. This is a terrible loss to the FreeBSD ports. Has anyone a suggestion/patch for this? Has anyone else experienced this problem? All of our other servers have built/ ran this version without complaint/trouble. All the conf files have been carefully crafted over many yrs. and I have no interest in using a newer version of Apache, so as to have to re-craft the configs. Thank you for all your time and consideration in this matter. P.S. I realize that this should normally be directed to apache-freebsd@ and I /did/ do so. However, after having been on the list for quite some time. It appears that I am the only one subscribed to it. Further, as this is on CURRENT, I felt that there must be some difference. As I had no trouble with this on a 6-CURRENT box/install. Thanks again. OK. After much research and trials and errors. I was able to find a solution. In spite of the man page information regarding objformat being obsolete and discontinued. It is still required (at least for a few things). As it happens, it is quite easy to overcome the problem building a /working/ www/apache13-ssl from recent src on a FreeBSD 7.0-PRERELEASE i386 box. It is a matter of creating: /usr/bin/objformat eg; # touch /usr/bin/objformat Edit /usr/bin/objformat and add the following: #!/bin/sh echo elf Now perform the following: # chmod +r +x -w /usr/bin/objformat You're done. :) Happy building! --Chris H --Chris H -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting Daniel Eischen <[EMAIL PROTECTED]>: On Mon, 28 Jan 2008, Chris H. wrote: Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: On Mon, Jan 28, 2008 at 09:33:49AM -0800, Chris H. wrote: Hello, After a failed install of www/apache-ssl - dies with the following error: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" I did a little research, and wondered if the fact that I am missing: /usr/bin/objformat has anything to do with it. Very unlikely. Are you using the binary package of www/apache-ssl, rather than building the port from source? Building from source that was cvsupped 2008-01-18 Have you at any time migrated from Apache 1.3.x Nope. It's a brand new install. Why don't you use a newer version of Apache, as opposed to 1.3.x? Because I have over 50 conf files carefully crafted from years of refining. So I have no interest in starting over. From your error messages, it seems obvious, though you never state it, that you are using apache13. Sorry, my bad. It's easy to overlook a detail sometimes, and given that this thread was primarily a question of /usr/bin/objformat didn't help me to think of asserting the apache version either. :) So, for the record; it's a build from the source in www/apache13-ssl Continued make deinstalls and tweaking and make && make installs all still fail with the same errors. I have noticed a couple of threads that relate to this. One indicates that copying www/apache13/files/patch-ae to www/apache-ssl/files/patch-az worked. Didn't work for me. Second one indicated that creating /usr/bin/objformat with the contents of objformat being #!/bin/sh echo elf worked for them. I'm about to try that, since it isn't possible to build from source a working version. I'll report back if it does. Whoo Hoo! Yep! That did it. In case you're wondering, objformat /is/ required - at leas for www/apache13-ssl. So the trick is to create the following /usr/bin/objformat: #!/bin/sh echo elf Make sure to set perms to +r +x -w Should I initiate a sendpr? Thanks to all for your comments/suggestions/advice. --Chris H --Chris H -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting Daniel Eischen <[EMAIL PROTECTED]>: On Mon, 28 Jan 2008, Chris H. wrote: Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: On Mon, Jan 28, 2008 at 09:33:49AM -0800, Chris H. wrote: Hello, After a failed install of www/apache-ssl - dies with the following error: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" I did a little research, and wondered if the fact that I am missing: /usr/bin/objformat has anything to do with it. Very unlikely. Are you using the binary package of www/apache-ssl, rather than building the port from source? Building from source that was cvsupped 2008-01-18 Have you at any time migrated from Apache 1.3.x Nope. It's a brand new install. Why don't you use a newer version of Apache, as opposed to 1.3.x? Because I have over 50 conf files carefully crafted from years of refining. So I have no interest in starting over. From your error messages, it seems obvious, though you never state it, that you are using apache13. Sorry, my bad. It's easy to overlook a detail sometimes, and given that this thread was primarily a question of /usr/bin/objformat didn't help me to think of asserting the apache version either. :) So, for the record; it's a build from the source in www/apache13-ssl Continued make deinstalls and tweaking and make && make installs all still fail with the same errors. I have noticed a couple of threads that relate to this. One indicates that copying www/apache13/files/patch-ae to www/apache-ssl/files/patch-az worked. Didn't work for me. Second one indicated that creating /usr/bin/objformat with the contents of objformat being #!/bin/sh echo elf worked for them. I'm about to try that, since it isn't possible to build from source a working version. I'll report back if it does. --Chris H -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting Daniel Eischen <[EMAIL PROTECTED]>: On Mon, 28 Jan 2008, Chris H. wrote: Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: On Mon, Jan 28, 2008 at 09:33:49AM -0800, Chris H. wrote: Hello, After a failed install of www/apache-ssl - dies with the following error: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" I did a little research, and wondered if the fact that I am missing: /usr/bin/objformat has anything to do with it. Very unlikely. Are you using the binary package of www/apache-ssl, rather than building the port from source? Building from source that was cvsupped 2008-01-18 Have you at any time migrated from Apache 1.3.x Nope. It's a brand new install. Why don't you use a newer version of Apache, as opposed to 1.3.x? Because I have over 50 conf files carefully crafted from years of refining. So I have no interest in starting over. From your error messages, it seems obvious, though you never state it, that you are using apache13. Sorry, my bad. It's easy to overlook a detail sometimes, and given that this thread was primarily a question of /usr/bin/objformat didn't help me to think of asserting the apache version either. :) So, for the record; it's a build from the source in www/apache13-ssl Continued make deinstalls and tweaking and make && make installs all still fail with the same errors. I have noticed a couple of threads that relate to this. One indicates that copying www/apache13/files/patch-ae to www/apache-ssl/files/patch-az worked. Didn't work for me. Second one indicated that creating /usr/bin/objformat with the contents of objformat being #!/bin/sh echo elf worked for them. I'm about to try that, since it isn't possible to build from source a working version. I'll report back if it does. Whoo Hoo! Yep! That did it. In case you're wondering, objformat /is/ required - at leas for www/apache13-ssl. So the trick is to create the following /usr/bin/objformat: #!/bin/sh echo elf Make sure to set perms to +r +x -w Should I initiate a sendpr? Thanks to all for your comments/suggestions/advice. --Chris H --Chris H -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
Quoting Daniel Eischen <[EMAIL PROTECTED]>: On Mon, 28 Jan 2008, Chris H. wrote: Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: On Mon, Jan 28, 2008 at 09:33:49AM -0800, Chris H. wrote: Hello, After a failed install of www/apache-ssl - dies with the following error: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" I did a little research, and wondered if the fact that I am missing: /usr/bin/objformat has anything to do with it. Very unlikely. Are you using the binary package of www/apache-ssl, rather than building the port from source? Building from source that was cvsupped 2008-01-18 Have you at any time migrated from Apache 1.3.x Nope. It's a brand new install. Why don't you use a newer version of Apache, as opposed to 1.3.x? Because I have over 50 conf files carefully crafted from years of refining. So I have no interest in starting over. From your error messages, it seems obvious, though you never state it, that you are using apache13. Sorry, my bad. It's easy to overlook a detail sometimes, and given that this thread was primarily a question of /usr/bin/objformat didn't help me to think of asserting the apache version either. :) So, for the record; it's a build from the source in www/apache13-ssl Continued make deinstalls and tweaking and make && make installs all still fail with the same errors. I have noticed a couple of threads that relate to this. One indicates that copying www/apache13/files/patch-ae to www/apache-ssl/files/patch-az worked. Didn't work for me. Second one indicated that creating /usr/bin/objformat with the contents of objformat being #!/bin/sh echo elf worked for them. I'm about to try that, since it isn't possible to build from source a working version. I'll report back if it does. --Chris H -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
On Mon, 28 Jan 2008, Chris H. wrote: Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: On Mon, Jan 28, 2008 at 09:33:49AM -0800, Chris H. wrote: Hello, After a failed install of www/apache-ssl - dies with the following error: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" I did a little research, and wondered if the fact that I am missing: /usr/bin/objformat has anything to do with it. Very unlikely. Are you using the binary package of www/apache-ssl, rather than building the port from source? Building from source that was cvsupped 2008-01-18 Have you at any time migrated from Apache 1.3.x Nope. It's a brand new install. Why don't you use a newer version of Apache, as opposed to 1.3.x? From your error messages, it seems obvious, though you never state it, that you are using apache13. -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: On Mon, Jan 28, 2008 at 09:33:49AM -0800, Chris H. wrote: Hello, After a failed install of www/apache-ssl - dies with the following error: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" I did a little research, and wondered if the fact that I am missing: /usr/bin/objformat has anything to do with it. Very unlikely. Are you using the binary package of www/apache-ssl, rather than building the port from source? Building from source that was cvsupped 2008-01-18 Have you at any time migrated from Apache 1.3.x Nope. It's a brand new install. to Apache 2.x or vice-versa without cleaning out old ports or rebuilding other ports? The problem seems to stem from the fact that the Apache 1.3.x module format is completely different than 2.x. Thanks, I also read that. :) The advice seen posted previously is to rebuild all related Apache modules from source. The last time I saw this reported was in late 2007... http://lists.freebsd.org/pipermail/freebsd-ports/2007-August/043136.html Yep. I read that too. But as mentioned above, this is a fresh install from ports. :) Doesn't this add an elf format to libraries? Do I need it? All of my 6-CURRENT boxes have this. But this is a 7-PRERELEASE ( FreeBSD 7.0-PRERELEASE i386 ) using 2 CPU's. If I /do/ need it, how do I create it? You don't. :-) Look at /usr/src/usr.bin/objformat/objformat.sh for some details (see comments at top of file). objformat allowed a script or surrounding program to determine whether or not the executable format was ELF or (ancient) a.out. Kewl. I /did/ take the time to do a man objformat, && man brandelf. Where I see all of this is to become/has already obsolete. But given that all of my /working/ web servers have /usr/bin/objformat and this /non/ working box doesn't, I had to ask. :) But I'd /really/ like to get the web server working. So I'm looking under everything in hopes of finding the "golden egg". :) Thank you very much for taking the time to respond. --Chris H -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.3-stable and if_re - stability problems?
On Mon, 28 Jan 2008 17:22:16 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote: > I think re(4) in CURRENT have fixed these issues. > Would you try re(4) in CURRENT? Perhaps I was being unclear; under FreeBSD 7.x (RELENG_7) re(49 works fine. It is only &.3 that has problems with re(4). -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/bin/objformat is missing
On Mon, Jan 28, 2008 at 09:33:49AM -0800, Chris H. wrote: > Hello, > After a failed install of www/apache-ssl - dies with the > following error: > Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: > Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: > /usr/local > /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" > > I did a little research, and wondered if the fact that I am > missing: /usr/bin/objformat has anything to do with it. Very unlikely. Are you using the binary package of www/apache-ssl, rather than building the port from source? Have you at any time migrated from Apache 1.3.x to Apache 2.x or vice-versa without cleaning out old ports or rebuilding other ports? The problem seems to stem from the fact that the Apache 1.3.x module format is completely different than 2.x. The advice seen posted previously is to rebuild all related Apache modules from source. The last time I saw this reported was in late 2007... http://lists.freebsd.org/pipermail/freebsd-ports/2007-August/043136.html > Doesn't this add an elf format to libraries? Do I need it? All of my > 6-CURRENT boxes have this. But this is a 7-PRERELEASE ( FreeBSD > 7.0-PRERELEASE i386 ) using 2 CPU's. If I /do/ need it, how do I > create it? You don't. :-) Look at /usr/src/usr.bin/objformat/objformat.sh for some details (see comments at top of file). objformat allowed a script or surrounding program to determine whether or not the executable format was ELF or (ancient) a.out. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: vm_fault: fault on nofualt entry, addr: 81423000
o.k., done some investigative work, and I think i have actually tracke dodnw what is going wrong, though i do not know how to fix it. mapping the header calls madt_map_table, which in turn calls madt_map to do the actual mapping: madt_map called with pa 0x7fec7f40, offset 1, length 60 'off' becomes 3904, and the rounded length 4096 pmap_kenter_temporary called with pa 0x7fec7000, offset 1 gives va of 0x8142300 returns 0x81423f40 thus the header is ending up in page 0x8142300 if I read that correctly. this is importnat for later on. meanwhile, back at the table scanning code... rsdt mapped at 0x81423f40 table offset at 0x81423f64 count is 6 table offset address and their contents 0 0x81423f64 0x7fec7fe8 1 0x81423f68 0x7fec805c 2 0x81423f6c 0x7fec80c4 3 0x81423f70 0x7fec8127 4 0x81423f74 0x7fec8163 5 0x81423f78 0x7fec8195 so, it probes the first table, held at 0x7fec7fe8 as indicated by the address in 0x81423f64. this calls madt_map to map the table madt_map called with pa 0x7fec7fe8, offset 0, length 36 'off' becomes 4072, and the rounded length 8192 pmap_kenter_temporary called with pa 0x7fec7000, offset 0 pmap_kenter called with va 0x8142300, pa 0x7fec8000 gives va of 0x8142200 returns 0x81422fe8 code is looking for a signature of 'APIC', but this table has 'FACP', so a call is made to madt_unmap before returning madt_unmap called with data 0x81422fe8, length 36 'off' becomes 4072, and the rounded length 8192 pmap_kremove called with 0x81422000 pmap_kremove called with 0x81423000 the function then returns 0, and the loop goes round again to look at table entry 1. the address of the table is stored at 0x81423f68 as you can see from the list above, and it is when it tries to access that address that it panics. now preseumably the panic is correct - 0x81423f68 is in page 0x81423000, and didn't we just unmap that ? now I dont really understand this fully, but why is page 0x81423000 being touched at all ? shouldnt the mapped pages be 0x81421000 and 0x81422000 instead so they don't clash with the already mapped 0x81423000 ? The unmap function is quite correctly doing the reverse of the map function, but maybe theres something simply going wrong in the algorithm working out which pages to map ? cheers, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/usr/bin/objformat is missing
Hello, After a failed install of www/apache-ssl - dies with the following error: Syntax error on line 208 of /usr/local/etc/apache/httpsd.conf: Cannot load /usr/local/libexec/apache/mod_mmap_static.so into server: /usr/local /libexec/apache/mod_mmap_static.so: Undefined symbol "ap_null_cleanup" I did a little research, and wondered if the fact that I am missing: /usr/bin/objformat has anything to do with it. Doesn't this add an elf format to libraries? Do I need it? All of my 6-CURRENT boxes have this. But this is a 7-PRERELEASE ( FreeBSD 7.0-PRERELEASE i386 ) using 2 CPU's. If I /do/ need it, how do I create it? Thank you for all your time and consideration in this matter. --Chris H -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: vm_fault: fault on nofualt entry, addr: 81423000
> That isn't page-aligned which is unexpected, though it should still > work fine. I am wondering if the non page alignment is what is causing the trouble here. I discovered my printfs were causing panics themselves, so am re-doing a lot of my results as I have been generating some red herrings. I will have some more results to email you later, but it looks to me as if the problem of the first table entry results in unmapping part of the header, and hence access to the second tbale entry crashes. At least the address reported in the panic is one I can see was unmapped just before the panic. I am doing a full compile against the latest stable and will actually see if I can track this down in a lot more detail and send you the results, cheers, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1
Richard Todd wrote: Workaround: always make sure you run /etc/rc.d/hostid start in single-user before doing any ZFS tinkering. Good advice -- thank you. But it still sounds like Jeremy's assessment, "it's a bug", is accurate. ZFS could certainly check for zero hostid. If zero, it should /definitely/ display a diagnostic which encourages the admin to use /etc/rc.d/hostid (or a printout of it). If zero, it /might/ additionally do some reads in case a likely-looking /etc/rc.d/hostid is available, and display the hostid, perhaps even speculatively start using it. It would save some needless "no datasets available" hair pulling. Cheers, JH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1
it should /definitely/ display a diagnostic which encourages the admin to use /etc/rc.d/hostid Ahhh, rather, display a diagnostic which encourages the use of "zpool import -a". --JH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: T7200 CPU not detected by est
Greetings, Krassimir Slavchev wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Smith wrote: On Fri, 25 Jan 2008, John Baldwin wrote: > On Wednesday 23 January 2008 02:42:52 am Krassimir Slavchev wrote: > > John Baldwin wrote: > > > On Monday 21 January 2008 11:16:06 am Gerrit Kühn wrote: > > >> Hi folks, > > >> > > >> I have several systems using T7200 mobile CPUs running under 7-stable. > > >> However, EST does not recognize the cpus. When loading cpufreq I get: > > > > > > You can try this patch. It won't add support for all of the levels, but it > > > will support the current level and the highest level (IIRC). > > > > > > > > > It works now on my T7700: > > > > dev.est.0.%desc: Enhanced SpeedStep Frequency Control > > dev.est.0.%driver: est > > dev.est.0.%parent: cpu0 > > dev.est.0.freq_settings: 2401/35000 2400/35000 2000/28000 1600/22000 > > 1200/16000 > > dev.est.1.%desc: Enhanced SpeedStep Frequency Control > > dev.est.1.%driver: est > > dev.est.1.%parent: cpu1 > > dev.est.1.freq_settings: 2401/35000 2400/35000 2000/28000 1600/22000 > > 1200/16000 > > Odd, it shouldn't have provided that many settings. It also doesn't > provide power info. I wonder if you are getting the settings from > ACPI. Assuming so, wouldn't this seem to be an instance needing the recent: kern/114722: [acpi] [patch] Nearly duplicate p-state entries reported http://www.freebsd.org/cgi/query-pr.cgi?pr=114722 With this patch the result is the same. Patched src/sys/kern/kern_cpu.c is already in RELENG_7_0. It was submitted 8 days ago. Are you sure your sources are newer then this? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.3-stable and if_re - stability problems?
On Sun, Jan 27, 2008 at 01:48:36PM +0100, Torfinn Ingolfsen wrote: > Hello! > > Is anybody having stability problems with if_re under FreeBSD > 6.3-stable? > I know about PR kern/118719[1] but it doesn't look like the problem I'm > having - at least my machine doesn't panic. > My machine[2] runs FreeBSD 6.3-stable / amd64: > [EMAIL PROTECTED] uname -a > FreeBSD kg-vm.kg4.no 6.3-STABLE FreeBSD 6.3-STABLE #1: Sun Jan 27 02:10:15 > CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP amd64 > > The machine has an if_re interface: > [EMAIL PROTECTED] pciconf -lv | grep -B 4 network > subclass = VGA > [EMAIL PROTECTED]:0:0: class=0x02 card=0x81aa1043 chip=0x816810ec > rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > > It looks like the interface works, because it gets the ip > address and other dhcp parameters right. But when I try to pass traffic > over it, trsffic often just stops. Examples: ping by ip address, > csup'ing the ports. also ssh connections to the machine randomly hangs, or > closes. > I think re(4) in CURRENT have fixed these issues. Would you try re(4) in CURRENT? > Ouch! The machine just rebooted. Perhaps this is kern/118719 after all. > Anything I can do to diagnose this problem further? > FWIW, I have FreeBSD 7.0 (RELENG_7) installed on another slice and that > works nicely. > > References: > 1) PR kern/118719 http://www.freebsd.org/cgi/query-pr.cgi?pr=118719 > 2) my machine http://tingox.googlepages.com/asus_m2a-vm_hdmi_freebsd > -- > Regards, > Torfinn Ingolfsen > -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"