Matthew Dillon said:
> :There're a couple of places in swtch.s where code looks like this,
> :
> :#ifdef VM86
> :btrl%esi, _private_tss
> :je 3f
> : ...
> :3:
> :#endif
> :
> :The conditional jump statement doesn't seem right, according to manual,
> :btrl instruction mo
:There're a couple of places in swtch.s where code looks like this,
:
:#ifdef VM86
:btrl%esi, _private_tss
:je 3f
: ...
:3:
:#endif
:
:The conditional jump statement doesn't seem right, according to manual,
:btrl instruction modifies CF flag but not Z, so the jump sho
There're a couple of places in swtch.s where code looks like this,
#ifdef VM86
btrl%esi, _private_tss
je 3f
...
3:
#endif
The conditional jump statement doesn't seem right, according to manual,
btrl instruction modifies CF flag but not Z, so the jump should be jae
There're a couple places in swtch.s with code like,
#ifdef VM86
btrl%esi, _private_tss
je 3f
...
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Kazutaka YOKOTA wrote in message ID
<199903170241.laa28...@zodiac.mech.utsunomiya-u.ac.jp>:
> It was in machine/console.h and renamed to keyent_t.
>
> I don't remember when this `#ifdef __i386__' bit came in...
revision 1.23
date: 1999/03/10 10:36:51; author: yokota; state: Exp; lines: +12 -33
David Greenman writes:
>If the remaining userland issues are dealt with, then perhaps. It is
> currently necessary to rebuild certain utilities after changing this,
> however, so making it a simple kernel compile time option isn't sufficient.
Are these crash-and-burn-class problems, or is it
On 17-Mar-99 Mikhail Teterin wrote:
> => > The bug is on the web site, not in the kernel.
> I'd consider the web-site a "spec" and the kernel -- "implementation".
> By this logic, the kernel needs fixing...
I think its a little too rapidly evolving for that, especially -current.
> =Probably.
>"Daniel O'Connor" writes:
>> On 17-Mar-99 Dag-Erling Smorgrav wrote:
>> > The bug is on the web site, not in the kernel. David Greenman
>> > committed a patch to better support large memory configurations.
>> > Unfortunately, it seems this was not possible to achieve without
>> > breaking BSD
=> > The bug is on the web site, not in the kernel.
I'd consider the web-site a "spec" and the kernel -- "implementation".
By this logic, the kernel needs fixing...
=> > David Greenman committed a patch to better support large memory
=> > configurations. Unfortunately, it seems this was not po
Output from dmesg:
usbd_match
usb0:
usbd_attach
usbd_new_device bus=0xc09b9000 depth=0 lowspeed=0
usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=0, protocol=0,
maxpacket=64, ls=0
usbd_new_device: new dev (addr 1), dev=0xc09b7b00, parent=0xc09b5040
uhub0 at usb0
uhub0: Intel UHC
>===> usr.sbin/kbdcontrol
>cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/kbdcontr
>ol/kbdcontrol.c
>gzip -cn /usr/src/usr.sbin/kbdcontrol/kbdcontrol.1 > kbdcontrol.1.gz
>lex -t /usr/src/usr.sbin/kbdcontrol/lex.l > lex.c
>cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c
"Daniel O'Connor" writes:
> On 17-Mar-99 Dag-Erling Smorgrav wrote:
> > The bug is on the web site, not in the kernel. David Greenman
> > committed a patch to better support large memory configurations.
> > Unfortunately, it seems this was not possible to achieve without
> > breaking BSDI comp
On Tuesday, 16 March 1999 at 22:41:22 +0300, Mikhail A. Sokolov wrote:
> Hello,
> the box is the same as in previous mail of mine which described ufs_dirbad()
> panics on 4.0-C. Panics are reproducable (run squid 2.1-pl2 with some
> 30 requests/second).
These two crashes both tend to suggest a fil
On Tuesday, 16 March 1999 at 22:36:38 +0300, Mikhail A. Sokolov wrote:
> Hello,
>
> we're experiencing repeated 4.0-C (as of today, something around 12:00
> GMT, 1999-03-16) ufs_dirbad() panics, which are the
> following (below), which usually occur when squid is running. The box
> doesn't have cc
What's your memory configuration and what's your kernel configuration?
df
dmesg
cat /usr/src/sys/i386/conf/YOURKERNELCONFIG
In general, the more information you include in the email, the easier
it is on the list.
-Matt
On 17-Mar-99 Dag-Erling Smorgrav wrote:
> > that bladeenc does not run, the problem is that a BSDI executable
> > does not run. Which breaks a promise from
> The bug is on the web site, not in the kernel. David Greenman
> committed a patch to better support large memory configurations.
> Unfort
===> usr.sbin/kbdcontrol
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/usr.sbin/kbdcontrol/kbdcontrol.c
gzip -cn /usr/src/usr.sbin/kbdcontrol/kbdcontrol.1 > kbdcontrol.1.gz
lex -t /usr/src/usr.sbin/kbdcontrol/lex.l > lex.c
cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c lex.c
Mikhail Teterin writes:
> Does not seem a better solution to me at all. The problem is not
> that bladeenc does not run, the problem is that a BSDI executable
> does not run. Which breaks a promise from
> http://www.freebsd.org/features.html
The bug is on the web site, not in the kernel. Da
I seem to be able to repeat this panic, every time I make a certain change
to a file and save it out this happens. It's a NFS mounted file from my i386
box to my alpha, both running pretty much current. It's the alpha that
panics.
Stopped at Debugger..ng+0x24: ldq ra,0(sp)
<0xfe0
On 16-Mar-99 Andreas Klemm wrote:
> No AFAIK two CPU's has to be there, so that the SMP kernel boots
> successfully.
Yes this is true. You have to make a UP kernel (ie remove the SMP lines)..
I have 2 kernels on my SMP box, they are the same except one has SMP in it :)
---
Daniel O'Connor soft
Søren Schmidt wrote:
> So here I am with our new boot code and a new device, how the
> @Â$ am I supposed to boot from that with the glory new
> boot blocks, forth and what have we ???
>
> If my suspicion is right, the glory fades pretty damn fast...
This is a bit on the incoherent side, Soren
Coda Distributed File System, version 5.2
Coda is a distributed file system like NFS and AFS. It is freely
available under the GPL. It functions somewhat like AFS in being a
"stateful" file system. Coda and AFS cache files on your local
machine to improve performance. But Coda goes a step further
nope, gone one month ago, FS's rebuilt since then
On Tue, Mar 16, 1999 at 02:16:59PM -0800, Julian Elischer wrote:
# Mikhail A. Sokolov wrote:
# >
# > Hello,
# >
# > we're experiencing repeated 4.0-C (as of today, something around 12:00
# > GMT, 1999-03-16) ufs_dirbad() panics, which are the
#
Mikhail A. Sokolov wrote:
>
> Hello,
>
> we're experiencing repeated 4.0-C (as of today, something around 12:00
> GMT, 1999-03-16) ufs_dirbad() panics, which are the
> following (below), which usually occur when squid is running. The box
> doesn't have ccd, nor vinum nor anything fancy in it's c
> Is the panic reproduceable? What is the CCD configuration?
not ccd, cd. old atapi stuff if I remember correctly. Machine has not
crashed since, sorry, switched on dumpdev however, so I can send you the
core file (and kernel and whatever else) if it happens agains if you
like.
Nick
>
>
On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote:
> A.. And if you make those AMD mounts normal nfs mounts it doesn't
> fry? If so, then we have a bug in AMD somewhere.
I tried the cp several times again on a regular NFS mount, to make
sure, and no, it doesn't seem to
:
:On Tue, Mar 16, 1999 at 11:11:44AM -0800, Matthew Dillon wrote:
:>(cnp->cn_flags & NOCROSSMOUNT) == 0) {
:> if (vfs_busy(mp, 0, 0, p))
:> continue;
:...
:> You shouldn't be crossing a mount point. Are you by chance doing a
:> rec
Mikhail A. Sokolov wrote...
> On Tue, Mar 16, 1999 at 01:14:52PM -0700, Kenneth D. Merry wrote:
> # Mikhail A. Sokolov wrote...
> # > Hello,
> # >
> # I have no idea why you're getting a panic, but I do have a question...
> #
> # > syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 givi
On Tue, Mar 16, 1999 at 11:11:44AM -0800, Matthew Dillon wrote:
>(cnp->cn_flags & NOCROSSMOUNT) == 0) {
> if (vfs_busy(mp, 0, 0, p))
> continue;
...
> You shouldn't be crossing a mount point. Are you by chance doing a
> recursive cop
On Tue, Mar 16, 1999 at 11:26:33PM +0300, Mikhail A. Sokolov wrote:
# # Are you *sure* you're running -current as of today? Justin put code in to
# # silence Illegal request error messages from the sync cache command.
# #
# # What revision of scsi_da.c do you have, and has it been modified?
#
#
On Tue, Mar 16, 1999 at 01:14:52PM -0700, Kenneth D. Merry wrote:
# Mikhail A. Sokolov wrote...
# > Hello,
# >
# I have no idea why you're getting a panic, but I do have a question...
#
# > syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up
# > (da1:ahc1:0:1:0): SYNCHRONIZE CA
On Mon, Mar 15, 1999 at 08:39:17PM +0100, Thomas Schuerger wrote:
> Hi!
>
> Will an SMP Kernel of 4.0-Current for two processors also run on
> one processor? I'd like to check whether the SMP-kernel runs stable
> on my Asus P2B-DS with two processors, but I'd like to be able to
> switch back to t
So here I am with our new boot code and a new device, how the
@Â$ am I supposed to boot from that with the glory new
boot blocks, forth and what have we ???
If my suspicion is right, the glory fades pretty damn fast...
-Søren
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscri
Mikhail A. Sokolov wrote...
> Hello,
>
> we're experiencing repeated 4.0-C (as of today, something around 12:00
> GMT, 1999-03-16) ufs_dirbad() panics, which are the
> following (below), which usually occur when squid is running. The box
> doesn't have ccd, nor vinum nor anything fancy in it's
On Tue, 16 Mar 1999 19:32:48 GMT, Karl Pielorz wrote:
> I know about the command line/environment variables that can be used to
> override this - but it's still annoying (see below)...
Taken off-line.
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd
Hello,
the box is the same as in previous mail of mine which described ufs_dirbad()
panics on 4.0-C. Panics are reproducable (run squid 2.1-pl2 with some
30 requests/second).
/var/crash# gdb -k kernel.2 vmcore.2
panicstr: ffs_blkfree: freeing free frag
panic messages:
---
panic: ffs_blkfree: fre
Hello,
we're experiencing repeated 4.0-C (as of today, something around 12:00
GMT, 1999-03-16) ufs_dirbad() panics, which are the
following (below), which usually occur when squid is running. The box
doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either.
Squid's spool is
Sheldon Hearn wrote:
> See the ftp(1) manpage for an explanation.
I know about the command line/environment variables that can be used to
override this - but it's still annoying (see below)...
> In future, please refer general questions related to FreeBSD to the
> freebsd-questions mailing list
It seems Pete Mckenna wrote:
> Soren,
>
> Here's what Aiwa has to say;
> BOLT utilizes an ATAPI (IDE) interface. It connects to an existing IDE
> interface
> as either master or slave. To configure, simply enter a single jumper
> setting.
> AIWA BOLT uses Travan drive hardware and records on Tr
On Tue, 16 Mar 1999 18:14:25 GMT, Karl Pielorz wrote:
> Is there any way to stop the FTP client from either taking _ages_, or
> just dying stone dead (i.e. CTRL-\ is the only way out - forcing a
> core dump) when connecting through Firewalls that only allow Passive
> FTP?
alias ftp='ftp -p'
Soren,
Here's what Aiwa has to say;
BOLT utilizes an ATAPI (IDE) interface. It connects to an existing IDE interface
as either master or slave. To configure, simply enter a single jumper setting.
AIWA BOLT uses Travan drive hardware and records on Travan 3 cartridges,
although with a different fo
Is the panic reproduceable? What is the CCD configuration?
-Matt
Matthew Dillon
:In case someone who is interested in the following panic:
:
:Occurred under a lightly loa
:On Mon, Mar 15, 1999 at 01:24:46PM -0800, Matthew Dillon wrote:
:> Compile up a kernel with 'options DDB' and get a backtrace when
:> it panics next ( 'trace' command from DDB prompt ).
:
:Ok, here goes. The kernel is compiled without -g for the moment,
:but I've provided the function offs
I have run into this in the past too, when a bad file was encountered on the
CD (home burned CDR). The system did not shut down though, it just kept on
working.
Tom Veldhouse
ve...@visi.com
-Original Message-
From: Nick Hibma
To: FreeBSD current mailing list
Date: Tuesday, March 16, 19
This may have been covered before (searching the archives for 'ftp' wasn't
such a hot idea :)
Is there any way to stop the FTP client from either taking _ages_, or just
dying stone dead (i.e. CTRL-\ is the only way out - forcing a core dump) when
connecting through Firewalls that only allow Passiv
It seems Pete Mckenna wrote:
> Do the AIWA bolt and Sony superstation tape drives work with the new
> ATA/ATAPI driver or the old drivers ?
> I've been following Soren's posting on the new driver but haven't seen mention
> of this, and saw on linux lists that they seemed to be writting specific
>
In case someone who is interested in the following panic:
Occurred under a lightly loaded system that was not doing anything apart
from reading a CD (dd if=/dev/cd0c of=/dev/null bs=512).
Kernel current as of yesterday.
No core file is available unfortunately.
panic: vm_fault: fault on nofault
On Tue, 16 Mar 1999, Daniel C. Sobral wrote:
> Mikhail Teterin wrote:
> >
> > for that missing piece... The other part of the package is usenetfs
> > -- file system to improve performance of large article directories.
> > Could this raise some interest?
>
> News servers are one of FreeBSD niche
Do the AIWA bolt and Sony superstation tape drives work with the new
ATA/ATAPI driver or the old drivers ?
I've been following Soren's posting on the new driver but haven't seen mention
of this, and saw on linux lists that they seemed to be writting specific drivers
for these drives. Are they non-s
Mikhail Teterin wrote:
>
> for that missing piece... The other part of the package is usenetfs
> -- file system to improve performance of large article directories.
> Could this raise some interest?
News servers are one of FreeBSD niches. I'd say this would
definitely generate interest.
Frankly,
The name of the old wd.c and atapi.c based CDROM driver has been changed
back to wcd. So update your config file to use "device wcd" instead of
"device acd".
This is to avoid confusion with the new ATA/ATAPI system.
MAKEDEV has also been changed to reflect this, and to support
the device nodes o
Hi,
I seem to remember someone requesting cryptfs. It's available outside
the US on my webserver:
http://wit395301.student.utwente.nl/~gelderen/fist/. It will go to
replay soon.
Cheers,
Jeroen
--
Jeroen C. van Gelderen - gelde...@mediaport.org - 0xC33EDFDE
To Unsubscribe: send mail to majord..
Hi Tord!
I maintain an port of bladeenc for FreeBSD
(see http://www.se.freebsd.org/ports/audio.html#bladeenc-0.76 for details).
Unfortunally the latest FreeBSD version isn't able to execute
BSDI binaries, even not if they are statically linked.
So it would be really be nice to have a native Free
On Mon, Mar 15, 1999 at 01:24:46PM -0800, Matthew Dillon wrote:
> Compile up a kernel with 'options DDB' and get a backtrace when
> it panics next ( 'trace' command from DDB prompt ).
Ok, here goes. The kernel is compiled without -g for the moment,
but I've provided the function offsets if
54 matches
Mail list logo
