[ANN] unionfs patchset-14 release
Hi Guys! It is my pleasure and honor to announce the availability of the unionfs patchset-14. Patchset-14: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p14.diff For 6.x http://people.freebsd.org/~daichi/unionfs/unionfs6-p14.diff Changes in unionfs-p14.diff - Added a patch of mount_unionfs.8. It means that this patchset is ready to be merged to FreeBSD base system. (hrs contributed it, thanks) - Fixed a problem that sets EXTATTR(ACL, MAC) information to lower layer files and directories. - Removed the third terms of the BSD License to get more easy to handle for FreeBSD. The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) We think that patchset-14 is ready to be merged to FreeBSD base system with the production level high quality :) Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help? 6.1-S: Fatal trap 12: page fault while in kernel mode
On Thu, Jun 15, 2006 at 04:22:40PM -0700, David Wolfskill wrote: I had one of these [kernel panics] a couple of weeks ago or so... ...[upgrade to -STABLE as of 15 June; repeat panic]... The message to which I'm replying (posted to -stable) has the particulars about the panic in question, and the machine in question is still sitting at the DDB prompt, if anyone wishes to work with me on that. But the reason for this message is to report that I upgraded the other test machines -- identical confguration: 2x3 GHz Xeons w/ 4 GB RAM; kernel config is called SMP_PAE_DDB for a fairly good reason -- to today's -CURRENT, then started the same test that cause -STABLE to crash burn within a couple of minutes. That was 30 minutes ago; the test is still running on FreeBSD localhost 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Fri Jun 16 07:28:18 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP_PAE_DDB i386 As I commented in email to some colleagues, color me surprised. I've suggested to the vendor (the program under test on the box is from a vendor, built under for FreeBSD 5.x; I'm using the misc/compat5x port) that they consider trying this themselves, and perhaps also take advantage of John Birrell's work to date on the FreeBSD port of DTrace. I'm still not too keen to run a production workload on a -CURRENT platform. I don't know if whatever is causing -CURRENT to keep running while -STABLE dies is an MFC candidate, but it seems to me that identifying the salient change(s) would be helpful in figuring that out. Any suggestions for how to go about doing that? Thanks! Peace, david -- David H. Wolfskill [EMAIL PROTECTED] Doing business with spammers only encourages them. Please boycott spammers. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpZ2XoMmc93k.pgp Description: PGP signature
Re: Help? 6.1-S: Fatal trap 12: page fault while in kernel mode
On Fri, 16 Jun 2006, 08:45-0700, David Wolfskill wrote: On Thu, Jun 15, 2006 at 04:22:40PM -0700, David Wolfskill wrote: I had one of these [kernel panics] a couple of weeks ago or so... ...[upgrade to -STABLE as of 15 June; repeat panic]... The message to which I'm replying (posted to -stable) has the particulars about the panic in question, and the machine in question is still sitting at the DDB prompt, if anyone wishes to work with me on that. But the reason for this message is to report that I upgraded the other test machines -- identical confguration: 2x3 GHz Xeons w/ 4 GB RAM; kernel config is called SMP_PAE_DDB for a fairly good reason -- to today's -CURRENT, then started the same test that cause -STABLE to crash burn within a couple of minutes. That was 30 minutes ago; the test is still running on FreeBSD localhost 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Fri Jun 16 07:28:18 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP_PAE_DDB i386 As I commented in email to some colleagues, color me surprised. I've suggested to the vendor (the program under test on the box is from a vendor, built under for FreeBSD 5.x; I'm using the misc/compat5x port) that they consider trying this themselves, and perhaps also take advantage of John Birrell's work to date on the FreeBSD port of DTrace. I'm still not too keen to run a production workload on a -CURRENT platform. I don't know if whatever is causing -CURRENT to keep running while -STABLE dies is an MFC candidate, but it seems to me that identifying the salient change(s) would be helpful in figuring that out. Any suggestions for how to go about doing that? trace in ddb would be good start. Do you really need PAE? -- Maxim Konovalov ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help? 6.1-S: Fatal trap 12: page fault while in kernel mode
On Fri, Jun 16, 2006 at 07:58:05PM +0400, Maxim Konovalov wrote: On Fri, 16 Jun 2006, 08:45-0700, David Wolfskill wrote: On Thu, Jun 15, 2006 at 04:22:40PM -0700, David Wolfskill wrote: I had one of these [kernel panics] a couple of weeks ago or so... ...[upgrade to -STABLE as of 15 June; repeat panic]... The message to which I'm replying (posted to -stable) has the particulars about the panic in question, and the machine in question is still sitting at the DDB prompt, if anyone wishes to work with me on that. But the reason for this message is to report that I upgraded the other test machines -- identical confguration: 2x3 GHz Xeons w/ 4 GB RAM; kernel config is called SMP_PAE_DDB for a fairly good reason -- to today's -CURRENT, then started the same test that cause -STABLE to crash burn within a couple of minutes. That was 30 minutes ago; the test is still running on FreeBSD localhost 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Fri Jun 16 07:28:18 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP_PAE_DDB i386 As I commented in email to some colleagues, color me surprised. I've suggested to the vendor (the program under test on the box is from a vendor, built under for FreeBSD 5.x; I'm using the misc/compat5x port) that they consider trying this themselves, and perhaps also take advantage of John Birrell's work to date on the FreeBSD port of DTrace. I'm still not too keen to run a production workload on a -CURRENT platform. I don't know if whatever is causing -CURRENT to keep running while -STABLE dies is an MFC candidate, but it seems to me that identifying the salient change(s) would be helpful in figuring that out. Any suggestions for how to go about doing that? trace in ddb would be good start. Do you really need PAE? The real problem is that trace does not work. Original message contains the details. It is either NULL-pointer function call (most likely), or stack array overflow. I already sent the OP the instructions how to proceed. And waiting for response. pgpK2htKKngei.pgp Description: PGP signature
sysinstall question
Hello All, I am working on building a FreeBSD 6.1 Jumpstart. One issue I ran into is with sysinstall editing the rc.conf file that I add from a package . The issue is that my options are perpended with the string #REMOVED . My questions is, Is there a preferred way to add a custom rc.conf, and does anyone know why I am getting the #REMOVED added in the first place ? -- Mark Saad [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
adm1026 support
Hi, I want to use healthd to monitor values exported by an adm1026 chip, using the smbus interface. Here's the data sheet for this chip: http://www.analog.com/UploadedFiles/Data_Sheets/779263102ADM1026_a.pdf This chip is smbus iic compatible. I am thinking I will have to write an adm1026 specific kernel module to interface with the iicbus module, but am not sure. Can someone please let me know what exactly needs to be done? Thanks! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: adm1026 support
Hello! On Tue, 13 Jun 2006, Franklin Donan wrote: I want to use healthd to monitor values exported by an adm1026 chip, using the smbus interface. Here's the data sheet for this chip: http://www.analog.com/UploadedFiles/Data_Sheets/779263102ADM1026_a.pdf This chip is smbus iic compatible. I am thinking I will have to write an adm1026 specific kernel module to interface with the iicbus module, but am not sure. Can someone please let me know what exactly needs to be done? There's no need in kernel module, all you want is a small piece of chip-specific userland code for healthd itself. Take a look at my patch: ftp://external.atlantis.dp.ua/FreeBSD/healthd/0.7.9/patch-IntelDeskBoards.v04 It adds support for several chips including ADM1025. Unfortunately I have neither ADM1026-based motherboard nor spare time to help you, but I hope you'll get an idea - code is very simple indeed. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
