I posted a bug report and patch in kern/29104 and Dima Dorfman also mentioned
this in July/August, but it still has not been resolved. The method of
triggering it that I detailed in my bug report no longer seems to work,
but I've managed to create another one.
# mdconfig -a -t swap -s 32m -u 10
> Forgot to mention, I had to make kcheckpass setuid root to make kcheckpass
> itself work (just verified this on -stable).
Yes - this is documented. :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROT
Dear Ladies & Gentlemen,
Welcome to the GREATEST SEX SHOW on the ENTIRE NET !
We now offer you to ENTER the World´s No.1 voted SEX-SERVER on the WEB !
By far the largest and most incredible content of LIVE SEX is now served to users
WORLDWIDE!
EVERYTHING is offered 100% ANONOMOUSLY & you don
Sounds like the bug is the md driver cloning "md10ec" which it shouldn't
do. This bug must naturally be in md_clone(), but I don't have the
minutes right now to hunt it down.
Should be quite simple to nail, it's just some string handling code.
Poul-Henning
In message <[EMAIL PROTECTED]>, Chad
On 19-Oct-01 Chad David wrote:
> I posted a bug report and patch in kern/29104 and Dima Dorfman also mentioned
> this in July/August, but it still has not been resolved. The method of
> triggering it that I detailed in my bug report no longer seems to work,
> but I've managed to create another o
On Fri, Oct 19, 2001 at 08:24:57AM -0700, John Baldwin wrote:
>
> On 19-Oct-01 Chad David wrote:
> > I posted a bug report and patch in kern/29104 and Dima Dorfman also mentioned
> > this in July/August, but it still has not been resolved. The method of
> > triggering it that I detailed in my bu
Fresh -current kernel on an DS10 Alpha box:
System shutdown time has arrived
Writing entropy file:.
lock order reversal
1st 0xfc7574b0 clk @ ../../../alpha/alpha/clock.c:702
2nd 0xfc7526b0 callout @ ../../../kern/kern_timeout.c:225
witness_lock
Stopped at Debugger+0x34: za
On Fri, Oct 19, 2001 at 05:00:16PM +0200, Poul-Henning Kamp wrote:
>
> Sounds like the bug is the md driver cloning "md10ec" which it shouldn't
> do. This bug must naturally be in md_clone(), but I don't have the
> minutes right now to hunt it down.
>
> Should be quite simple to nail, it's just
Maxim Sobolev wrote:
>
> Mike Smith wrote:
>
> > This just isn't going to work. The _CRS data stream stops at byte 0x17,
> > and these extra items are simply mis-aimed.
> >
> > The 0x19 should really be 0x11, and the 0x1c should really be 0x14, ie.
> > this is a BIOS bug, and should be reported
This is -current from yesterday, with the recent patches to ansi.h to
get it to compile, and vmware2 with kse patches build today.
I did a
rm /compat/linux/dev/vmnet1;ln -s /dev/vmnet1 /compat/linux/dev
(see kse-patches announcement) and this seems to be working.
I tried bridged (us
On Thu, 18 Oct 2001, Terry Lambert wrote:
TL>To expand a little...
TL>
TL>> That said, it's probably a good idea to never ARP for 0.0.0.0,
TL>> since a "who has" in that case is a really dumb idea, since,
TL>> as weas pointed out, it's intended to mean "this host", in the
TL>> absence of an IP ad
On Fri, Oct 19, 2001 at 11:12:48AM +0200, Harti Brandt wrote:
> I have run tcpdump all night to find out what happens. The host receives
> an ARP request with a source address of 0.0.0.0:
>
> 18:33:51.222688 arp who-has hydra tell 0.0.0.0
> 0001 0800 0604 0001 0030 65c6 a
On 19-Oct-01 Wilko Bulte wrote:
> Fresh -current kernel on an DS10 Alpha box:
I have untested patches to fix this. Unfortunately they involve fixing the
locking in teh clock code and I've only done i386 and alpha so far, but the
same changes need to be replicated into all the otehr arch's. Alt
I'm trying to upgrade -current on one of our machines. This box is a Compaq
Presario 900 Mhz Athlon. It errors on the NIC. I can't disable PnP in the
bios, that feature doesn't exist in the compaq bios. I have tried several
NIC's and pci slots with the same results.
Also, I tried both "unset
> I'm trying to upgrade -current on one of our machines. This box is a Compaq
> Presario 900 Mhz Athlon. It errors on the NIC. I can't disable PnP in the
> bios, that feature doesn't exist in the compaq bios. I have tried several
> NIC's and pci slots with the same results.
>
> Also, I tried
On Fri, Oct 19, 2001 at 04:58:21PM -0700, Mark Peek wrote:
> At 11:23 AM +0200 10/18/01, Harti Brandt wrote:
> >On Thu, 18 Oct 2001, Max Khon wrote:
> >
> >MK>hi, there!
> >MK>
> >MK>On Thu, Oct 18, 2001 at 12:00:52AM +0200, Jose M. Alcaide wrote:
> >MK>
> >MK>> On Wed, Oct 17, 2001 at 12:11:45PM
On Thu, Oct 18, 2001 at 09:33:09PM +0200, Riccardo Torrini wrote:
> Is a real need for ports under -CURRENT to require (from a
> week or two, I don't remember) XFree86-libraries?
Yes.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Warner Losh wrote:
> Yup. I've done things like creating a chroot area and mounting a 3.5
> or 2.2.8 cdrom and then mounting another fs in that chroot area to
> access the sources and then building it there. But as you go back in
> time in FreeBSD it gets much harder to have ports be supported..
On 19 Oct, Dag-Erling Smorgrav wrote:
> [EMAIL PROTECTED] writes:
>> The error
>>
>> Could not get address for /dev/vmnet1: argument is invalid
>> Failed to configure ethernet0
>>
>> is all I get... (this is the host-only case, for bridged it says
>> something like could not get bri
Le 2001-10-14, Paul van der Zwan écrivait :
> I am using -current box as a homedir server for my Solaris clients and
> have noticed a wierd problem.
Other problems here, with Solaris 2.[68] as clients, and -CURRENT of
yesterday as server. ls works, but ls -l issues a 'NFS getacl failed'
message
[EMAIL PROTECTED] writes:
> Has anyone seen similar problem on recent -current or has someone an
> idea why vmware is issuing a SIOCGIFCONF ioctl without providing an
> interface name?
>
> Oct 19 18:04:53 mp /boot/kernel/kernel: linux_ioctl_socket(): ioctl 35093 on
To clarify, this is from debug
At 9:14 PM -0500 10/19/01, Jonathan Lemon wrote:
>Below is the patch that I've sent to the people who reported the
>problem, I'm waiting to hear back from them that it works.
Thanks for the real patch. It appears to work fine on my system. No
log messages and arps look good so far.
Mark
To Uns
hi, there!
> Same here. My -CURRENT system is replying to those ARP request which carry
> 0.0.0.0 as sender IP address:
>
> 14:43:33.706099 arp who-has 158.227.48.193 (ff:ff:ff:ff:ff:ff) tell 0.0.0.0
> 14:43:33.706152 arp reply 0.0.0.0 is-at 0:d0:b7:3e:a0:fb
>
> > I think this is because I have
I know that some people are complaining about the performance of current and
all, but breaking nice so that we can't make processes run slower is just going
too far. :)
> nice -20 buildworld
setpriority: Permission denied.
Any ideas?
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.o
On 19-Oct-01 John Baldwin wrote:
> I know that some people are complaining about the performance of current and
> all, but breaking nice so that we can't make processes run slower is just
> going
> too far. :)
>
>> nice -20 buildworld
> setpriority: Permission denied.
>
> Any ideas?
Idea #1: P
At 11:23 AM +0200 10/18/01, Harti Brandt wrote:
>On Thu, 18 Oct 2001, Max Khon wrote:
>
>MK>hi, there!
>MK>
>MK>On Thu, Oct 18, 2001 at 12:00:52AM +0200, Jose M. Alcaide wrote:
>MK>
>MK>> On Wed, Oct 17, 2001 at 12:11:45PM -0700, Julian Elischer wrote:
>MK>> > I've seen this when DHCP fails to all
26 matches
Mail list logo
