On Wed, 7 Mar 2001, Gregory Neil Shapiro wrote:
> root> I am using the standard freebsd.mc created during a buildworld. I
> root> have started noticing that I am missing/rejecting a lot of emails
> root> from places like: yahoogroups.com.
>
> It would be helpful to show the actual log message
On Wed, Mar 07, 2001 at 08:50:23PM +1100, Bruce Evans wrote:
> > > dump.8 and dump(8) both refer explicitly to nsa0 and nrsa0 whereas
> > > sa0 and nsa0 are the actual device names in -current.
>
> The dump sources also refer to only the 'r' devices (_PATH_DEFTAPE
> is still "/dev/rsa0").
Fixed.
Yesterday -current:
# mount /msdos
Acquring duplicate lock of same type: "lockmgr interlock"
1st @ ../../kern/kern_lock.c:239
2nd @ ../../kern/kern_lock.c:239
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor write, page not prese
Hi,
As I reported earlier, starting from about a months ago I'm having strange
problems with building 5-current world on 4-stable system. As long as
nobody confirmed this problem in the similar setups I investigated
further and found that problem is due to my non-standard directory layout.
Usuall
Matthew Jacob <[EMAIL PROTECTED]> writes:
>> > My FreeBSD-alpha PC164 lost it's IDE disk for 4.2 somehow- which I'd
>> > just loaded the 4.2 kernel from- so it decided to run off of da0
>> > instead, which was -current. Truly a startling turn of
>> > events. Shouldn't one stop and ask if the root
> As suggested, if the correct root device can't be found, the boot
> _should_ offer you a choice of running off others that appear to be
> bootable.
The "appear to be bootable" criterion is almost impossible (and unsafe to
attempt) to determine.
Also, I certainly can see instances
On 08-Mar-01 Andrea Campi wrote:
> Yesterday -current:
>
># mount /msdos
>
> Acquring duplicate lock of same type: "lockmgr interlock"
> 1st @ ../../kern/kern_lock.c:239
> 2nd @ ../../kern/kern_lock.c:239
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x0
> fault
Bruce Evans <[EMAIL PROTECTED]> writes:
>I think I prefer the old behaviour. The names preserved by the kernel
>can't possibly remain valid until unmount in all cases. Examples:
>- pathnames relative to the current directory work. These only remain
> valid if the process that does the mount al
The Portland Group's linux Fortran compiler used to work
without a problem, but something has changed that I haven't
track down. The script(1) log below suggests two possibilities:
(1) the translation of linux syscalls to FreeBSD syscalls isn't
working; or (2) the linux ld command (see log) needs
I did a buildworld/installworld on an alpha yesterday, and now I'm left with:
start_init: trying /sbin/init
Entropy harvesting: interrupts ethernet.
And this is even with booting from an older kernel. Umm... anyone gotta clue
on this one?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
I'm having a small problem with sound output not sounding quite right
under FreeBSD 5.0-CURRENT.
The sound mostly works. I can play MP3s using mpg123/x11amp/xmms...
The problem is that when I start moving the mouse around a lot, the
sound distorts and the kernel occasionally spits out a message
kernel: type 12 trap, code=0
Stopped at 0: kernel: type 12 trap, code=0
db> trace
kernel: type 12 trap, code=0
db> panic
panic: from debugger
Debugger("panic")
Stopped at 0:kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual addres
<[EMAIL PROTECTED]> writes:
> The sound mostly works. I can play MP3s using mpg123/x11amp/xmms...
> The problem is that when I start moving the mouse around a lot, the
> sound distorts and the kernel occasionally spits out a message like:
>
> Mar 8 16:07:17 choplifter /boot/kernel/kernel: pcm1:
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> db> trace
> kernel: type 12 trap, code=0
Blah. Here's what gdb says:
(kgdb) where
#0 dumpsys () at ../../kern/kern_shutdown.c:478
#1 0xc019131b in boot (howto=260) at ../../kern/kern_shutdown.c:321
#2 0xc01916e5 in panic (fmt=0xc02940b4 "from
> > Mar 8 16:07:17 choplifter /boot/kernel/kernel: pcm1: hwptr went
> > backwards 536 - > 444
>
> This has been a known problem for several months now. Please do not
> run -CURRENT unless you follow the freebsd-current mailing list
> closely.
Sorry -- I forgot to mention that I did search the arc
On Mon, 5 Mar 2001, Steve Kargl wrote:
> Matthew Jacob wrote:
> >
> > On Mon, 5 Mar 2001, Steve Kargl wrote:
> >
> > > What are the names of the tape devices under devfs?
> > >
> > > Should dump(8) use /dev/sa0 for the rewind device and
> > > /dev/nsa0 for no rewind device? Should /etc/rc.d
On 08-Mar-01 Andrea Campi wrote:
> Yesterday -current:
It seems modules are broken with witness right now. Before you were ok as long
as you didn't unload the darn things, now they seem to be toast altogether, so
you will want to use a static kernel for now until this is fixed.
--
John Baldw
17 matches
Mail list logo
