Mike Silbersack wrote:
On Tue, 26 Feb 2002, Peter Wemm wrote:
Mike Silbersack wrote:
_
Hm, sounds like UP got optimized out.
Gah! That would be a first. :(
Well, until I can build a working kernel, I'll just assume that it's a
feature.
FWIW, turning off PG_G see_ms to help.
On Tue, 26 Feb 2002, Peter Wemm wrote:
FWIW, turning off PG_G see_ms to help. Change in pmap.c:
#if !defined(SMP) || defined(ENABLE_PG_G)
to:
#if /*!defined(SMP) ||*/ defined(ENABLE_PG_G)
and see how you go. This got me past atkbd0, but it is a very worrying
sign. I now get a vnode
On Wed, 27 Feb 2002, Mike Silbersack wrote:
Disabling PG_G allows it to work here again as well. Given the problems
we're experiencing, backing out the pmap changes of the last two days
seems like a good idea.
Mike Silby Silbersack
Well, I sorta take that back. The box has been up for
boot.]
Anyway, I now have my first panic on boot from -CURRENT since setting
up the serial console; modulo cut/paste damage, the following ought to
be fairly accurate. :-}
Sources are as of about 3:50 AM PST (8 hrs. west of GMT), from cvsup14.
Here are the boot messages, which start showing some
Date: Wed, 21 Nov 2001 08:05:18 -0800 (PST)
From: David Wolfskill [EMAIL PROTECTED]
Anyway, I now have my first panic on boot from -CURRENT since setting
up the serial console; modulo cut/paste damage, the following ought to
be fairly accurate. :-}
Eh, well... my laptop came up OK after
Hi all,
From: Brian Somers [EMAIL PROTECTED]
Date: Fri, 12 Oct 2001 01:15:38 +0100
::Hi,
::
::I was wondering if anybody has any suggestions about why this might
::be happening in -current:
cut
::pccbb1: RF5C478 PCI-CardBus Bridge irq 0 at device 10.1 on pci0
::pccbb1: PCI Memory allocated:
Hi, Intel folks. I've just found the bug in rsutils.c which double
free(); AcpiUtRemoveReference() and ACPI_MEM_FREE(). Here is a fix.
Index: rsutils.c
===
RCS file: /home/ncvs/src/sys/contrib/dev/acpica/rsutils.c,v
retrieving
From: Mitsuru IWASAKI [EMAIL PROTECTED]
Date: Mon, 15 Oct 2001 00:46:57 +0900 (JST)
::Hi, Intel folks. I've just found the bug in rsutils.c which double
::free(); AcpiUtRemoveReference() and ACPI_MEM_FREE(). Here is a fix.
::
::Index: rsutils.c
Hi,
I was wondering if anybody has any suggestions about why this might
be happening in -current:
Booting [/boot/kernel/kernel]...
/boot/kernel/acpi.ko text=0x32f34 data=0xf9c+0x1028 syms=[0x4+0x49c0+0x4+0x61a]-
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979,
Hello current,
the recent changes in current to auoload th acpi.ko module make my
system crash in an early state. With a pmap_mapdev: Couldn't alloc
kernel virtual memory panic. Without the acpi-module the system works fine.
Any hints?
Michael
This is the output with the panic:
ok boot -v
My SMP box, running current from about 24 hours ago, panics on a cold boot,
but only if I don't touch a key. If I use the keyboard to do anything,
whether to skip the loader twiddler, or to skip the BIOS disk probing, or
just to bang my head against it, it boots fine. It will reboot fine once
Hello Jim,
On Sun, Mar 25, 2001 at 07:20:04PM -0500, Jim Bloom wrote:
I get a slightly different backtrace, but was able to use my palm pilot as the
serial console. I have had this same problem for quit a while (about a month).
I suspect a locking issue related to Seigo Tanimura's commit on
Hello folks,
I have tried it with today's -CURRENT, and as soon as I try to boot a
kernel with the options (this has occured also earlier but wanted to make
sure that I try today's sources first)
device midi
device seq
(my sound card is a ISAPnP SB 64 AWE)
I use device sbc too.
the kernel
I get a slightly different backtrace, but was able to use my palm pilot as the
serial console. I have had this same problem for quit a while (about a month).
I suspect a locking issue related to Seigo Tanimura's commit on Feb 25. My last
cvsup was within the past 24 hours and the kernel was
On Mon, Mar 12, 2001 at 04:38:50PM +0100, Szilveszter Adam wrote:
I wonder if this is known? If not, I can certainly provide more
information. The offending sound hw is a Creative SB 64 AWE ISAPnP card. It
works fine otherwise. (as it always has)
Yup I'm seeing this too. SMP kernel, AWE64
On Wed, 14 Mar 2001 00:49:53 -0800,
Alex Zepeda [EMAIL PROTECTED] said:
Alex On Mon, Mar 12, 2001 at 04:38:50PM +0100, Szilveszter Adam wrote:
I wonder if this is known? If not, I can certainly provide more
information. The offending sound hw is a Creative SB 64 AWE ISAPnP card. It
works
Hello everybody,
I had been away for two weeks and after upgrading to the latest -CURRENT I
noticed that leaving
device midi
(and maybe device seq, I did not test separately)
in my kernel config file causes a Trap 12 with interrupts disabled on
_mtx_lock_sleep+0x29a: movl 0x1a0(%edx),%eax
Hi.
With latest 5-current kernel, it will always panic.
My HDD does not support DMA mode. So with old kernel(maybe before
sos's latest ata changes), it fallback to PIO mode(see attached
text).
Do only I have this problem?
Thank you.
---
MIHIRA, Sanpei Yoshiro
Yokohama, Japan.
=
Using a freshly supped -current source tree (2 hours ago) I'm getting a panic on
boot:
trap entry = 0x4 (unaligned access fault)
a0 = 0xfc590a33
a1 = 0x2c
a2 = 0x2
pc = 0xfc3a970c
ra = 0xfc3a96b8
curproc = 0
Interesting. I've also been seeing this on alphas.
Do you have sys/dev/randomdev/randomdev.c v1.5?
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, 30 Jun 2000, Mark Murray wrote:
Interesting. I've also been seeing this on alphas.
Do you have sys/dev/randomdev/randomdev.c v1.5?
Now I do. Better.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hello,
I am running -CURRENT from June 27, 2000 (started cvsup around 19:05)
on a PII 266 MHz with 32MB RAM and one IDE disk.
Initially, I noticed that while syncing disks during a reboot, the
system would always give up before finishing. To capture the output,
I configured the kernel to use a
Hi
I fixed this yesterday; please re-cvsup and reboot.
You should have sys/dev/randomdev/randomdev.c v1.5 to fix this.
M
I am running -CURRENT from June 27, 2000 (started cvsup around 19:05)
on a PII 266 MHz with 32MB RAM and one IDE disk.
Initially, I noticed that while syncing disks
Interesting. I've also been seeing this on alphas.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Brian Somers wrote:
In article [EMAIL PROTECTED], Archie Cobbs
[EMAIL PROTECTED] writes
Brian Somers writes:
Also (Mark sits beside me at work), is there anyone else out there
that actually runs FreeBSD-current under VMWare (irrespective of the
host OS) ?
This problem has now
In article [EMAIL PROTECTED], Archie Cobbs
[EMAIL PROTECTED] writes
Brian Somers writes:
Also (Mark sits beside me at work), is there anyone else out there
that actually runs FreeBSD-current under VMWare (irrespective of the
host OS) ?
This problem has now been traced down to a bug in the
In article [EMAIL PROTECTED], Archie Cobbs
[EMAIL PROTECTED] writes
Brian Somers writes:
Also (Mark sits beside me at work), is there anyone else out there
that actually runs FreeBSD-current under VMWare (irrespective of the
host OS) ?
This problem has now been traced down to a bug
In article [EMAIL PROTECTED], Mark Knight [EMAIL PROTECTED]
writes
World and kernel of approx 1100 GMT Sunday 21st May:
Sorry to reply to my own thread, but new world and kernel/modules of
24th May 22:00 GMT still exhibit this behaviour...
Any ideas appreciated before I start the 'binary chop'.
In article [EMAIL PROTECTED], Mark Knight [EMAIL PROTECTED]
writes
World and kernel of approx 1100 GMT Sunday 21st May:
Sorry to reply to my own thread, but new world and kernel/modules of
24th May 22:00 GMT still exhibit this behaviour...
Any ideas appreciated before I start the
World and kernel of approx 1100 GMT Sunday 21st May:
Console (re-typed):
ad0: 1999MB VMware Virtual IDE Hard Drive [4334/15/63] at ata0-master using UDMA33
ad1: 499MB VMware Virtual IDE Hard Drive [1083/15/63] at ata0-slave using UDMA33
Mounting root from ufs: /dev/ad0s1a
Fatal trap 12: page
2000, Jeroen Ruigrok van der Werven wrote:
-On [2430 11:50], Leif Neland ([EMAIL PROTECTED]) wrote:
In a freshly cvsup'ed current, I get a panic at boot, if both ports are
enabled in userconfig.
If only one or the other is enabled, it works.
I have narrowed it down to it panics
called ppbus_attach in there, please write down
its arguments as well.
Nick
On Sun, 30 Apr 2000, Jeroen Ruigrok van der Werven wrote:
-On [2430 11:50], Leif Neland ([EMAIL PROTECTED]) wrote:
In a freshly cvsup'ed current, I get a panic at boot, if both ports are
enabled in userconfig
Could you compile a debugging kernel with the kernel debugger included
and make it bomb again, and write down the function names that the trace
command on the DDB command line gives you and the exact trap message?
Thanks in advance.
Nik
On Fri, 28 Apr 2000, Leif Neland wrote:
Sorry not to
On Wed, 3 May 2000, Nick Hibma wrote:
Could you compile a debugging kernel with the kernel debugger included
and make it bomb again, and write down the function names that the trace
command on the DDB command line gives you and the exact trap message?
I don't know what happened, but I
On Fri, 28 Apr 2000, Leif Neland wrote:
Sorry not to have details at hand but anyways:
Current cvsupped today.
I have 2 parallel ports in use.
I have had no problems with kernels dated 2 weeks or older, but since a few
days ago, the system crashes at boot while probing the parallel
In a freshly cvsup'ed current, I get a panic at boot, if both ports are
enabled in userconfig.
If only one or the other is enabled, it works.
I have narrowed it down to it panics the second time ppbconf calls
bus_generic_probe:
trap 12: page fault while in kernel mode
bus_generic_probe+0x25
-On [2430 11:50], Leif Neland ([EMAIL PROTECTED]) wrote:
In a freshly cvsup'ed current, I get a panic at boot, if both ports are
enabled in userconfig.
If only one or the other is enabled, it works.
I have narrowed it down to it panics the second time ppbconf calls
bus_generic_probe:
trap
Sorry not to have details at hand but anyways:
Current cvsupped today.
I have 2 parallel ports in use.
I have had no problems with kernels dated 2 weeks or older, but since a few
days ago, the system crashes at boot while probing the parallel ports. "Page
fault while in supervisor mode", (I
Background:
---
Work recently assigned me a Gateway GP7-500 (PIII-500mhz, 96M RAM) to
replace my older 333mhz PII that's been running FreeBSD 3.2.. Of course,
as my testing machine, I wanted to run FreeBSD 4.0-CURRENT on it, and
installed the 19990806 snapshot without a problem, and then
See my earlier post today, it is due to the PnP probe.
If you boot a kernel which is older than Mikes commit,
you can boot the new kernel after a soft reboot...
Poul-Henning
In message [EMAIL PROTECTED], Thomas Stromberg writes:
Background:
---
Work recently assigned me a Gateway
This appears to be due to our PnP BIOS invocation not being
sufficiently bug-compatible with some BIOSsen. I'm going to need to do
some more work on this, and if you have time I'd like to get you
involved in the testing process.
Meanwhile I'll be disabling the PnP BIOS scan which should
I was wondering, I've been spending all my time recently on a research
task, and I might have missed this: I just rebuilt world, then
reinstalled a new kernel, and it won't mount root. Luckily, my old
kernel is just fine, and uses my new modules fine, but it won't mount
root. I noticed in the
301 - 342 of 342 matches
Mail list logo
