On Sat, 10 Aug 2013, Adrian Chadd wrote:
On 10 August 2013 19:19, AN wrote:
Hi All:
I am having a major problem on current at the moment, and I could really use
some help. I am at R253966 on amd64, my problem is the machine is panicing
with: ffs_valloc: dup alloc
I have booted into single
On 10 August 2013 19:19, AN wrote:
> Hi All:
>
> I am having a major problem on current at the moment, and I could really use
> some help. I am at R253966 on amd64, my problem is the machine is panicing
> with: ffs_valloc: dup alloc
>
> I have booted into single user mode and run fsck, it reports
Hi All:
I am having a major problem on current at the moment, and I could really
use some help. I am at R253966 on amd64, my problem is the machine is
panicing with: ffs_valloc: dup alloc
I have booted into single user mode and run fsck, it reports that it has
fixed the file system but I st
On Sat, Aug 10, 2013 at 7:07 PM, Sam Fourman Jr. wrote:
> On Sat, Apr 27, 2013 at 6:31 PM, Paul Webster
> wrote:
>> Just got this link on IRC, (freenode/##freebsd) was so funny I thought
>> I would see if I could get any of you guys to spit out you're coffee
>> :)
>>
>> http://antibsd.wordpress.c
On Sat, Apr 27, 2013 at 6:31 PM, Paul Webster
wrote:
> Just got this link on IRC, (freenode/##freebsd) was so funny I thought
> I would see if I could get any of you guys to spit out you're coffee
> :)
>
> http://antibsd.wordpress.com/
> ___
Sorry I am
On Fri, Aug 09, 2013 at 09:56:48PM -0600, Scott Long wrote:
> All,
>
> Subversion rev 250418 affected approximately 63 drivers by making them
> vulnerable to resource allocation failures on motherboards with buggy BIOSes.
> The revision itself is good, but it needs to address these drivers and
On Fri, Aug 9, 2013 at 1:33 PM, Hans Petter Selasky wrote:
> Hi,
>
> For those of you that want to make sure your USB mass storage device
> behaves correctly when using FreeBSD, typically for critical applications,
> I've just added an advanced USB testing tool to the FreeBSD source tree. It
> ca
On 8/10/2013 1:21 PM, Konstantin Belousov wrote:
> On Sat, Aug 10, 2013 at 08:45:47PM +0300, Konstantin Belousov wrote:
>> On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote:
>>> On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote:
On 8/10/2013 11:44 AM, Bryan Drewer
Hi,
I can reproduce it locally, purely by booting an unchanged amd64 GENERIC.
Are you testing it against an _unmodified_ GENERIC, on amd64?
If it doesn't panic for you but it does panic for me (and I'll go and
get the svn version once I reboot to the old kernel and test) then
there may be a hidd
On 8/10/2013 12:45 PM, Konstantin Belousov wrote:
> On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote:
>> On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote:
>>> On 8/10/2013 11:44 AM, Bryan Drewery wrote:
On 8/10/2013 6:24 AM, Joel Dahl wrote:
> panic: witness
After updating -CURRENT from a one or two-month old checkout, I get the
following messages when /etc/rc.d/initrandom is run:
Entropy harvesting:sysctl: unknown oid 'kern.random.sys.harvest.interrupt':
No such file or directory
interruptssysctl: unknown oid 'kern.random.sys.harvest.ethernet':
Konstantin Belousov writes:
> The right fix looks to be just what the panic message told, please try
> this:
The patch managed to fix the crash here at least.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
On 2013-08-10 15:02, Konstantin Belousov wrote:
Try this.
diff --git a/sys/dev/cpuctl/cpuctl.c b/sys/dev/cpuctl/cpuctl.c
index 742ef0db..4e5abb2 100644
--- a/sys/dev/cpuctl/cpuctl.c
+++ b/sys/dev/cpuctl/cpuctl.c
@@ -346,8 +346,7 @@ update_intel(int cpu, cpuctl_update_args_t *args,
struct thr
On Sat, Aug 10, 2013 at 02:06:10PM -0500, Larry Rosenman wrote:
> I'm getting the following @R254183:
> when I try to run the microcode_update.
>
> Just started with yesterday's -CURRENT.
> (kgdb) #0 doadump (textdump=) at pcpu.h:236
> #1 0x8051d6f0 in kern_reboot (howto=260)
> at
On Sat, Aug 10, 2013 at 02:11:52PM -0400, Glen Barber wrote:
> On Sat, Aug 10, 2013 at 01:09:20PM -0500, Dan Mack wrote:
> > It looks like you are doing the first [! -z '"${svnversion}"' ]
> > before $svnversion is being set. In the old version, this was
> > being set via:
> >
> > if [ -x /usr/b
On Sat, Aug 10, 2013 at 08:45:47PM +0300, Konstantin Belousov wrote:
> On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote:
> > On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote:
> > > On 8/10/2013 11:44 AM, Bryan Drewery wrote:
> > > > On 8/10/2013 6:24 AM, Joel Dahl wr
On Sat, Aug 10, 2013 at 01:09:20PM -0500, Dan Mack wrote:
> It looks like you are doing the first [! -z '"${svnversion}"' ]
> before $svnversion is being set. In the old version, this was
> being set via:
>
> if [ -x /usr/bin/svnliteversion ] ; then
> svnversion=/usr/bin/svnliteversion
>
Here's the before and after looks like FWIW:
'
+ LC_ALL=C
+ export LC_ALL
+ [ ! -r version ]
+ echo 0
+ touch version
+ cat version
+ pwd
+ hostname
+ date
+ v=0 u=root d=/usr/src/sys/conf h=borg.macktronics.com t='Sat Aug 10
12:59:21 CDT 2013'
+ make -V KERN_IDENT
+ i=''
+ make -V CC
+ grep v
Same problems here ... sometime after 10.0-CURRENT r253918 ...
Two other systems stopped working and they have a mixture of svn /
svnlite version combinations:
working system:
#1: ports svn installed at newer version
root@borg:/usr/src # svnversion ; svnversion --version | head -1
253918
svnve
On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote:
> On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote:
> > On 8/10/2013 11:44 AM, Bryan Drewery wrote:
> > > On 8/10/2013 6:24 AM, Joel Dahl wrote:
> > >> panic: witness_init: pending locks list is too small, increase
>
On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote:
> On 8/10/2013 11:44 AM, Bryan Drewery wrote:
> > On 8/10/2013 6:24 AM, Joel Dahl wrote:
> >> panic: witness_init: pending locks list is too small, increase
> >> WITNESS_PENDLIST
> > I also get this. The last stable revision for me was
I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2.
https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1
https://github.com/lichray/nvi2
The goal was to update the multibyte handling in nvi-1.79 (the one we
have in our tree) in such a way we could import
On 8/10/2013 11:44 AM, Bryan Drewery wrote:
> On 8/10/2013 6:24 AM, Joel Dahl wrote:
>> panic: witness_init: pending locks list is too small, increase
>> WITNESS_PENDLIST
> I also get this. The last stable revision for me was r254150
r254150 stable, r254171 panic.
backtrace: https://dl.dropboxuse
On 8/10/2013 6:24 AM, Joel Dahl wrote:
> Hi,
>
> I just rebuilt a fresh current on my laptop. It panics on boot with:
>
> panic: witness_init: pending locks list is too small, increase
> WITNESS_PENDLIST
>
> I'm in a hurry right now so I can't gather much more info at the moment, but I
> thought
Hello, Glen.
You wrote 10 августа 2013 г., 18:13:24:
GB> Hmm. I suspect r254094 is to blame here, although I did extensive
GB> testing with different svn versions before the commit. :(
GB> I'll take another look at this, in case I missed an edge case.
It doesn't look like edge case...
Sources
Hello, Lev.
You wrote 10 августа 2013 г., 15:01:57:
LS> Hello, Current.
LS> I've make simple mistake (DOS-style EOL) in /boot/device.hints and
LS> /boot/loader.conf was skipped too with strange (device.hints-related)
LS> message:
LS> FreeBSD/x86 bootstrap loader, Revision 1.1
LS> (r...@fbsd-c-64
Hmm. I suspect r254094 is to blame here, although I did extensive
testing with different svn versions before the commit. :(
I'll take another look at this, in case I missed an edge case.
Glen
On Sat, Aug 10, 2013 at 07:03:29AM -0700, Adrian Chadd wrote:
> Try running the svnlite version of svn
Try running the svnlite version of svn upgrade.
(svnlite upgrade)
-adrian
On 10 August 2013 07:02, Lev Serebryakov wrote:
> Hello, Freebsd-current.
> You wrote 10 августа 2013 г., 15:18:46:
>
> LS>> Latest revisions of -CURRENT built with "nanobsd" script haven't
> revision
> LS>> in "unam
Hello, Freebsd-current.
You wrote 10 августа 2013 г., 15:18:46:
LS>> Latest revisions of -CURRENT built with "nanobsd" script haven't revision
LS>> in "uname -a" output:
LS>> FreeBSD gateway.home.serebryakov.spb.ru 10.0-CURRENT FreeBSD
LS>> 10.0-CURRENT #0: Sat Aug 10 14:17:32 MSK 2013
LS>>
On Sat, 10 Aug 2013 15:39:48 +0200
Gary Jennejohn wrote:
> On Sat, 10 Aug 2013 14:59:22 +0200
> "O. Hartmann" wrote:
>
> > On Sat, 10 Aug 2013 11:31:19 +0200
> > Gary Jennejohn wrote:
> >
> > > On Sat, 10 Aug 2013 11:10:40 +0200
> > > Rainer Hurling wrote:
> > >
> > > > Yes, I can confirm,
On Sat, 10 Aug 2013 14:59:22 +0200
"O. Hartmann" wrote:
> On Sat, 10 Aug 2013 11:31:19 +0200
> Gary Jennejohn wrote:
>
> > On Sat, 10 Aug 2013 11:10:40 +0200
> > Rainer Hurling wrote:
> >
> > > Yes, I can confirm, that it builds, installs and runs fine for me.
> > >
> > > The patch should be
On Sat, Mar 28, 2009 at 11:00:32AM +0100, Hans Petter Selasky wrote:
> On Saturday 28 March 2009, Lars Engels wrote:
> > Hi all,
> >
> > yesterday I bought a shiny new hama usb bluetooth dongle but I am having
> > some problems using it:
> >
> > before loading ng_ubt:
> > usb2_alloc_device:1480:
On Sat, 10 Aug 2013 11:31:19 +0200
Gary Jennejohn wrote:
> On Sat, 10 Aug 2013 11:10:40 +0200
> Rainer Hurling wrote:
>
> > Yes, I can confirm, that it builds, installs and runs fine for me.
> >
> > The patch should be placed as
> > x11/nvidia-driver/files/patch-src__nvidia_subr.c, shoudn't it
Hi,
I just rebuilt a fresh current on my laptop. It panics on boot with:
panic: witness_init: pending locks list is too small, increase
WITNESS_PENDLIST
I'm in a hurry right now so I can't gather much more info at the moment, but I
thought I'd mention it.
--
Joel
__
Hello, Lev.
You wrote 10 августа 2013 г., 15:08:49:
LS> Latest revisions of -CURRENT built with "nanobsd" script haven't revision
LS> in "uname -a" output:
LS> FreeBSD gateway.home.serebryakov.spb.ru 10.0-CURRENT FreeBSD
LS> 10.0-CURRENT #0: Sat Aug 10 14:17:32 MSK 2013
LS>
r...@fbsd-c-64.
Hello, Freebsd-embedded.
Latest revisions of -CURRENT built with "nanobsd" script haven't revision
in "uname -a" output:
FreeBSD gateway.home.serebryakov.spb.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #0:
Sat Aug 10 14:17:32 MSK 2013
r...@fbsd-c-64.vm.home.serebryakov.spb.ru:/data/obj.nano/gate
Hello, Current.
I've make simple mistake (DOS-style EOL) in /boot/device.hints and
/boot/loader.conf was skipped too with strange (device.hints-related)
message:
FreeBSD/x86 bootstrap loader, Revision 1.1
(r...@fbsd-c-64.vm.home.serebryakov.spb.ru, Sat Aug 10 14:02:41 MSK 2013)
Loading /boot/defa
Not sure that it did :)
I tried it once early on, and it concerned me enough I never tried
again. It was clearly in a violently erroneous state!
At one point, X *could* resume the display. This makes me think the
problem is solved via the graphics "chip" state, but it could be an
acpi thing.
I c
On Sat, 10 Aug 2013 11:10:40 +0200
Rainer Hurling wrote:
> Yes, I can confirm, that it builds, installs and runs fine for me.
>
> The patch should be placed as
> x11/nvidia-driver/files/patch-src__nvidia_subr.c, shoudn't it?
>
> Many thanks for this work.
>
Thanks for testing.
Yes, putting t
Am 10.08.2013 10:37, schrieb Gary Jennejohn:
> On Fri, 9 Aug 2013 10:12:37 -0700
> David Wolfskill wrote:
>
>> On Fri, Aug 09, 2013 at 07:32:51AM +0200, O. Hartmann wrote:
>>> ...
> On 8 August 2013 11:10, O. Hartmann
> wrote:
>> The most recent CURRENT doesn't work with the x11/nvid
On Fri, 9 Aug 2013 10:12:37 -0700
David Wolfskill wrote:
> On Fri, Aug 09, 2013 at 07:32:51AM +0200, O. Hartmann wrote:
> > ...
> > > > On 8 August 2013 11:10, O. Hartmann
> > > > wrote:
> > > > > The most recent CURRENT doesn't work with the x11/nvidia-driver
> > > > > (which is at 319.25 in th
41 matches
Mail list logo
