Trying to build today's current I get the following:
cc -O2 -pipe -DATJOB_DIR=\"/var/at/jobs/\" -
DLFILE=\"/var/at/jobs/.lockfile\" -DLOADAVG_MX=1.5 -
DATSPOOL_DIR=\"/var/at/spool\" -DVERSION=\"2.9\" -DDAEMON_UID=1 -
DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' -
DPERM_
On Wed, Aug 24, 2011 at 12:08 AM, Beech Rintoul wrote:
> Trying to build today's current I get the following:
Please update to HEAD and read UPDATING @ 20110815. There are
several references in the archives last week and the week before to
this build failure.
Cheers,
-Garrett
On Tuesday 23 August 2011 23:43:14 Garrett Cooper wrote:
> On Wed, Aug 24, 2011 at 12:08 AM, Beech Rintoul wrote:
> > Trying to build today's current I get the following:
> Please update to HEAD and read UPDATING @ 20110815. There are
> several references in the archives last week and the week
On Tuesday 23 August 2011 23:24:30 Conrad J. Sabatier wrote:
> On Tue, 23 Aug 2011 23:08:17 -0800
>
> Beech Rintoul wrote:
> > Trying to build today's current I get the following:
> >
> > cc -O2 -pipe -DATJOB_DIR=\"/var/at/jobs/\" -
> > DLFILE=\"/var/at/jobs/.lockfile\" -DLOADAVG_MX=1.5 -
> >
On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek wrote:
> On Tue, Aug 23, 2011 at 04:11:20PM -0400, Rick Macklem wrote:
> > Pawel Jakub Dawidek wrote:
> > > On Tue, Aug 23, 2011 at 10:09:41AM -0400, Rick Macklem wrote:
> > > > Ok, I'll admit I wasn't very fond of a fixed table that wou
Kostik Belousov wrote
in <20110824082119.gj17...@deviant.kiev.zoral.com.ua>:
ko> On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek wrote:
ko> > On Tue, Aug 23, 2011 at 04:11:20PM -0400, Rick Macklem wrote:
ko> > > Pawel Jakub Dawidek wrote:
ko> > > > On Tue, Aug 23, 2011 at 10:09:41
On Wed, Aug 24, 2011 at 09:34:58PM +0900, Hiroki Sato wrote:
> Kostik Belousov wrote
> in <20110824082119.gj17...@deviant.kiev.zoral.com.ua>:
>
> ko> On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek wrote:
> ko> > On Tue, Aug 23, 2011 at 04:11:20PM -0400, Rick Macklem wrote:
> ko>
Kostik Belousov wrote:
> On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek wrote:
> > On Tue, Aug 23, 2011 at 04:11:20PM -0400, Rick Macklem wrote:
> > > Pawel Jakub Dawidek wrote:
> > > > On Tue, Aug 23, 2011 at 10:09:41AM -0400, Rick Macklem wrote:
> > > > > Ok, I'll admit I wasn't ve
Kostik Belousov wrote:
> On Wed, Aug 24, 2011 at 09:34:58PM +0900, Hiroki Sato wrote:
> > Kostik Belousov wrote
> > in <20110824082119.gj17...@deviant.kiev.zoral.com.ua>:
> >
> > ko> On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek
> > wrote:
> > ko> > On Tue, Aug 23, 2011 at 04:11:
On Wed, Aug 24, 2011 at 09:36:37AM -0400, Rick Macklem wrote:
> Kostik Belousov wrote:
> > On Wed, Aug 24, 2011 at 09:34:58PM +0900, Hiroki Sato wrote:
> > > Kostik Belousov wrote
> > > in <20110824082119.gj17...@deviant.kiev.zoral.com.ua>:
> > >
> > > ko> On Tue, Aug 23, 2011 at 11:23:03PM +020
Hi,
I upgraded a fresh RELENG_8_2 to CURRENT and nearly everything works fine. I
only have to wait about 3 minutes during boot. In dmesg I have many messages
like this: arcmsr1: scsi id 17 lun 0 cmd=0x12 srb='0xff8462bd9780' ccb
command time out!
http://ugrohnwaldt.web02.lando.us/FBSD/dmesg-2
Oh shit guys!
http://pastebin.com/dyKLRr0v
___
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"
Does Someone know if this was fixed?
On Wed, Aug 24, 2011 at 11:57 AM, Victor Detoni wrote:
> Oh shit guys!
>
> http://pastebin.com/dyKLRr0v
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsu
After this messages there are no visible disks. A camcontrol rescan all
leads tot he same timeouts.
> -Ursprüngliche Nachricht-
> Von: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] Im Auftrag von Uwe Grohnwaldt
> Gesendet: Mittwoch, 24. August 2011 16:37
>
On (24/08/2011 21:34), Hiroki Sato wrote:
> Kostik Belousov wrote
> in <20110824082119.gj17...@deviant.kiev.zoral.com.ua>:
>
> ko> On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek wrote:
> ko> > On Tue, Aug 23, 2011 at 04:11:20PM -0400, Rick Macklem wrote:
> ko> > > Here's the patc
On Wed, Aug 24, 2011 at 11:59:01AM -0300, Victor Detoni wrote:
> Does Someone know if this was fixed?
>
> On Wed, Aug 24, 2011 at 11:57 AM, Victor Detoni wrote:
>
> > Oh shit guys!
> >
> > http://pastebin.com/dyKLRr0v
> >
>
It is already one year old... and it was fixed before this pastebin:
http
On 24.08.2011 16:59, Victor Detoni wrote:
> Does Someone know if this was fixed?
>
> On Wed, Aug 24, 2011 at 11:57 AM, Victor Detoni wrote:
>
>> Oh shit guys!
>>
>> http://pastebin.com/dyKLRr0v
>>
http://security.freebsd.org/advisories/FreeBSD-SA-10:07.mbuf.asc
Isn't this the one?
//Svein
--
Gleb Kurtsou wrote
in <20110824150235.GA46460@tops>:
gl> On (24/08/2011 21:34), Hiroki Sato wrote:
gl> > Kostik Belousov wrote
gl> > in <20110824082119.gj17...@deviant.kiev.zoral.com.ua>:
gl> >
gl> > ko> On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek wrote:
gl> > ko> > On Tue,
Rick Macklem wrote
in <920337541.272757.1314192294772.javamail.r...@erie.cs.uoguelph.ca>:
rm> Kostik Belousov wrote:
rm> > On Tue, Aug 23, 2011 at 11:23:03PM +0200, Pawel Jakub Dawidek wrote:
rm> > > On Tue, Aug 23, 2011 at 04:11:20PM -0400, Rick Macklem wrote:
rm> > > > Pawel Jakub Dawidek wro
On Thu, 25 Aug 2011, Hiroki Sato wrote:
My opinion is using a hash function which occurs no collision in the
well-known names is sufficient for our purpose because the number of
file systems on a running system is small anyway and not changed
frequently in most cases. I am not sure which func
On Wed, Aug 24, 2011 at 04:41:25PM +0300, Kostik Belousov wrote:
> On Wed, Aug 24, 2011 at 09:36:37AM -0400, Rick Macklem wrote:
> > Well, doesn't this result in the same issue as the fixed table?
> > In other words, the developer has to supply the "suggested byte" for
> > fsid and make sure that i
Pawel Jakub Dawidek wrote:
> On Wed, Aug 24, 2011 at 04:41:25PM +0300, Kostik Belousov wrote:
> > On Wed, Aug 24, 2011 at 09:36:37AM -0400, Rick Macklem wrote:
> > > Well, doesn't this result in the same issue as the fixed table?
> > > In other words, the developer has to supply the "suggested byte
Pawel Jakub Dawidek wrote:
> On Wed, Aug 24, 2011 at 04:41:25PM +0300, Kostik Belousov wrote:
> > On Wed, Aug 24, 2011 at 09:36:37AM -0400, Rick Macklem wrote:
> > > Well, doesn't this result in the same issue as the fixed table?
> > > In other words, the developer has to supply the "suggested byte
On Wed, 24 Aug 2011, Rick Macklem wrote:
"afs"
The current OpenAFS codebase uses the all-caps "AFS". Judging by the
omitted text, perhaps this should change. (We also don't use VFS_SET to
set it, which I filed a bug about.)
and here is my current rendition of the patch. (I took Gleb's
Hi Fellow NFS'ers,
I believe I have found the problem we've been having with read locks
while attaching to a FreeBSD NFS server.
In sys/nlm/nlm_prot_impl.c, function nlm_get_vfs_state(), there is a call
to VOP_ACCESS() as follows:
/*
* Check cred.
*/
NLM_D
Hello,
I have an older Dell 4150 laptop that takes forever to build
world, so I don't update it that often. The last time I
updated it was March 1, 2010. I just updated the system
yesterday and ath0 (a Linksys PCCard) no longer attaches.
The interesting thing is that ath0 is detected at differ
I ran into the panic shown below because it appears that some
array indexing went off into the weeds. I haven't seen this happen but
once though when running a buildworld last night using r225089 on
i386.
This begs the question - is it wise to compile if_ath without
ath_hal support today? I
On 25 August 2011 08:19, Daniel Eischen wrote:
> I have an older Dell 4150 laptop that takes forever to build
> world, so I don't update it that often. The last time I
> updated it was March 1, 2010. I just updated the system
> yesterday and ath0 (a Linksys PCCard) no longer attaches.
>
> The i
Hi,
On 25 August 2011 12:49, Garrett Cooper wrote:
> I ran into the panic shown below because it appears that some
> array indexing went off into the weeds. I haven't seen this happen but
> once though when running a buildworld last night using r225089 on
> i386.
> This begs the question -
29 matches
Mail list logo
