Re: r209240 ia64 -> buildworld -> undefined reference to `lzma_physmem'

2010-06-25 Thread Anton Shterenlikht
On Thu, Jun 24, 2010 at 05:50:59PM +0200, Dag-Erling Smørgrav wrote: > Anton Shterenlikht writes: > > Dag-Erling Smørgrav writes: > > > I expect this to produce the same error as before; if not, there is > > > something seriously wrong. > > the error is different... > > > > echo fsck_ffs: /usr/li

Re: using cupsd instead of base lpr [was Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1 (solved)]

2010-06-25 Thread Gary Jennejohn
On Thu, 24 Jun 2010 09:54:45 -0700 Ted Faber wrote: > On Thu, Jun 24, 2010 at 08:29:57AM -0700, Ted Faber wrote: > > On Thu, Jun 24, 2010 at 09:40:00AM +0100, Tom Evans wrote: > > > I also have this in make.conf: > > > CUPS_OVERWRITE_BASE=yes > > > WITHOUT_LPR=yes > > > > > > which print/cups-ba

Re: r209240 ia64 -> buildworld -> undefined reference to `lzma_physmem'

2010-06-25 Thread Dag-Erling Smørgrav
Anton Shterenlikht writes: > So, just for me to be clear, I need to proceed with the buildworld, > until I get the error, and then, without cleaning anything, do > > % cd /usr/src > % make buildenv > % cd rescue/rescue > % make > > Is that correct? Yes. Then you take the cc comand line that fail

panic in deadlkres

2010-06-25 Thread Anton Yuzhaninov
I've got panic on 9-current from Jun 25 2010 May be this is bug in deadlock resolver panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/kern/kern_clock.c:203 db> show alllocks Process 0 (kernel) thread 0xc4dcd270 (100047) shared sx allproc (allproc) r = 0 (0xc0885ebc) locked @

Re: panic in deadlkres

2010-06-25 Thread Anton Yuzhaninov
On Fri, 25 Jun 2010 09:50:40 + (UTC), Anton Yuzhaninov wrote: AY> I've got panic on 9-current from Jun 25 2010 It's wrong date. The system is: FreeBSD 9.0-CURRENT #0: Fri May 28 23:47:37 MSD 2010 AY> AY> May be this is bug in deadlock resolver AY> AY> panic: blockable sleep lock (sleep mute

Use of boot0cfg to set boot slice broke between r209459 and r209502

2010-06-25 Thread David Wolfskill
Well, one one of my machines -- I realize that there are some machines for which it's been problematic for a while. And all of the machines I'm using run FreeBSD/i386. But it had been working on my build machine since I acquired it (a few months ago) in daily use. Of course, I didn't notice the

Re: Use of boot0cfg to set boot slice broke between r209459 and r209502

2010-06-25 Thread John Baldwin
On Friday 25 June 2010 7:40:11 am David Wolfskill wrote: > Well, one one of my machines -- I realize that there are some > machines for which it's been problematic for a while. And all of > the machines I'm using run FreeBSD/i386. 209469 perhaps? -- John Baldwin

HEADS UP: removal of acpi_aiboost(4)

2010-06-25 Thread Rui Paulo
Hi, In about a month, acpi_aiboost(4) will be removed. You should start using acpi_aibs(4) starting today. Regards, -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, sen

Re: iSCSI boot driver version 0.1.1 for iBFT

2010-06-25 Thread Daisuke Aoyama
Sorry, isboot-0.1.1 was broken under i386 kernel + loader. The version 0.1.2 is uploaded in my blog. Also I uploaded isboot integrated FreeBSD 7.3 disc1, 8.1-RC1 dics1 and making script. Use at your own risk. You need only iBFT supported NIC and iSCSI target. Please see Intel's site about iBFT s

Re: Use of boot0cfg to set boot slice broke between r209459 and r209502

2010-06-25 Thread David Wolfskill
On Fri, Jun 25, 2010 at 08:37:36AM -0400, John Baldwin wrote: > On Friday 25 June 2010 7:40:11 am David Wolfskill wrote: > > Well, one one of my machines -- I realize that there are some > > machines for which it's been problematic for a while. And all of > > the machines I'm using run FreeBSD/i38

Re: panic in deadlkres

2010-06-25 Thread pluknet
On 25 June 2010 13:50, Anton Yuzhaninov wrote: > I've got panic on 9-current from Jun 25 2010 > > May be this is bug in deadlock resolver > > panic: blockable sleep lock (sleep mutex) process lock @ > /usr/src/sys/kern/kern_clock.c:203 > > db> show alllocks > Process 0 (kernel) thread 0xc4dcd270 (

Re: iSCSI boot driver version 0.1.1 for iBFT

2010-06-25 Thread Vincent Hoffman
On 25/06/2010 17:32, Daisuke Aoyama wrote: > Sorry, isboot-0.1.1 was broken under i386 kernel + loader. > The version 0.1.2 is uploaded in my blog. > Also I uploaded isboot integrated FreeBSD 7.3 disc1, 8.1-RC1 dics1 and > making script. Use at your own risk. > > You need only iBFT supported NIC an

Re: I need reply in Embedded FreeBSD Kernel Theme

2010-06-25 Thread Mohammed Farrag
hi sorry for being late in reply but I had some problems in the last week. I hope u still remeber what I was talking about :) @chargen Thanx for ur reply. Embedded computer systems permeate all aspects of our daily lives. Alarm clocks, coffee makers, digital watches, cell phones, and automobiles ar

HEADS-UP: object directory name change

2010-06-25 Thread M. Warner Losh
I recently committed a change that changes the name of the object tree where things are built to if you are cross compiling. Rather than /usr/obj/$TARGET_ARCH, it is now /usr/obj/$TARGET.$TARGET_ARCH. The reason for the change is so that embedded platforms with multiple endians can compile into t

Re: I need reply in Embedded FreeBSD Kernel Theme

2010-06-25 Thread Matt Thyer
On 24 June 2010 11:06, Mohammed Farrag wrote: > @ Matt > Thanx for ur reply Matt. > / > FreeBSD is already a very modular system and the traditional way (a > traditional way) to build for embedded systems is to follow the > NanoBSD build method (