A stack trace would be helpful.
Thanks,
--Will.
On Tue, Mar 26, 2013 at 4:27 PM, AN wrote:
> Hello:
>
> I have identified svn Revision 248649 as causing my system to panic during
> boot up.
> http://svnweb.freebsd.org/**base?view=revision&revision=**248649<http://svnweb
Hello:
I have identified svn Revision 248649 as causing my system to panic during
boot up. http://svnweb.freebsd.org/base?view=revision&revision=248649
I have verified this by doing the following:
svn up -r 248648 - buildkernel, installkernel, reboot = boot successful
svn up -r 24
On Sat, Mar 09, 2013 at 10:39:20AM +0100, Joel Dahl wrote:
> Hi,
>
> Just updated to the latest CURRENT. Got this during boot:
> (sorry for the large image)
>
> http://mirror.vnode.se/upload/r248090_panic.jpg
This is fixed with r248093.
--
Joel
___
f
Hi,
Just updated to the latest CURRENT. Got this during boot:
(sorry for the large image)
http://mirror.vnode.se/upload/r248090_panic.jpg
--
Joel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
on 23/06/2010 10:28 Nicholas Mills said the following:
> I was afraid someone would say that, because it's been very difficult to
> reproduce the issue. Happens maybe 1 out of every 8 reboots. I'll give
> it a look tomorrow and see what I can find.
>
> Just to be clear, I should send you the outpu
I was afraid someone would say that, because it's been very difficult to
reproduce the issue. Happens maybe 1 out of every 8 reboots. I'll give it a
look tomorrow and see what I can find.
Just to be clear, I should send you the output of the "where" command in
ddb?
On Wed, Jun 23, 2010 at 3:15 AM
on 23/06/2010 10:09 Nicholas Mills said the following:
> http://www.parl.clemson.edu/~nlmills/Screenshot.png
Ah, no stack trace. Unfortunately, this looks undebuggable as it is.
Custom kernel with debug options is needed.
--
Andriy Gapon
___
freebsd-c
I've since disabled the cdrom drive in Parallels as it was causing all sorts
of errors.
On Wed, Jun 23, 2010 at 2:15 AM, Andriy Gapon wrote:
> on 23/06/2010 02:41 Nicholas Mills said the following:
> > Hey all,
> >
> > Screenshot of panic message is attached. Machine is a VM running under
> > Pa
on 23/06/2010 02:41 Nicholas Mills said the following:
> Hey all,
>
> Screenshot of panic message is attached. Machine is a VM running under
> Parallels Server Bare Metal 4. The cdrom device was enabled but not
> connected during boot. System was attempting to boot into single user mode.
> This oc
Hey all,
Screenshot of panic message is attached. Machine is a VM running under
Parallels Server Bare Metal 4. The cdrom device was enabled but not
connected during boot. System was attempting to boot into single user mode.
This occurred after a fresh install of 8.0-RELEASE.
Let me know how I can
Just in case anyone didnt know already ;)
Jeffrey Katcher wrote:
You have to set:
hw.pci.allow_unsupported_io_range="1"
at startup initially and then in /boot/loader.conf for subsequent boots
I had the same problem, now I'm happily running 5.1-Current/5.2-Beta.
Finnur Guðmundsson wrote:
Hi th
and i am waiting for you guys to tell me the tp40 works with
-current before i upgrade from a limping -stable.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED
Hi there! ;)
I´ve been trying to install FreeBSD-CURRENT and FreeBSD 5.2-BETA on my
Thinkpad for awile
The problem is this:
When i try to boot 5.1-Current (first cd i tried was from 5 Oct 2003
and the latest one was 5.2-BETA) i get this error:
---CUT---
Memory modified after free 0x20e1
I cvsuped just a couple of hours ago and built world and then built a
kernel. That kernel always dies on startup. First it shows a Fatal Trap 9
and then a Fatal Trap 12 and then give me the debugger prompt. Is there some
easy way to get the information from the debugger into an email short of
writ
On Sun, 13 Oct 2002, Steve Kargl wrote:
> I haven't seen this type of panic before. What type
> of memory are you using and can you change the clock
> timing for refresh?
That's an interesting question. I just bought a new DIMM a few weeks ago,
to replace one that had gone bad. I now have two
On Sat, 12 Oct 2002, Steve Kargl wrote:
> On Sat, Oct 12, 2002 at 05:21:01PM -0700, Alex Varju wrote:
> > Hi there,
> >
> > For the last few days, I have been unable to build a bootable kernel. I
> > have gone back to GENERIC, and it still doesn't work. When I try to boot,
> > it panics almost im
Hi there,
For the last few days, I have been unable to build a bootable kernel. I
have gone back to GENERIC, and it still doesn't work. When I try to boot,
it panics almost immediately. Can anybody offer any suggestions for where
to start diagnosing this?
Thanks,
Alex.
This is the output grab
On Sat, Oct 12, 2002 at 05:21:01PM -0700, Alex Varju wrote:
> Hi there,
>
> For the last few days, I have been unable to build a bootable kernel. I
> have gone back to GENERIC, and it still doesn't work. When I try to boot,
> it panics almost immediately. Can anybody offer any suggestions for w
I thought I'd give this a whirl on a spare disk on a test machine, so I
nabbed the ISO from ftp.freebsd.org and burnt to CD. I've tried booting from
the CD directly and creating floppies from the kern/mfsroot.flp, both result
in identical panics at exactly the same point.
ed1:
real memory = 402
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
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
This is a
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) ?
>
> 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 tra
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 bu
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) ?
Julian has done that I think..
-Archie
___
Arch
> 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 star
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 ch
World and kernel of approx 1100 GMT Sunday 21st May:
Console (re-typed):
ad0: 1999MB [4334/15/63] at ata0-master using UDMA33
ad1: 499MB [1083/15/63] at ata0-slave using UDMA33
Mounting root from ufs: /dev/ad0s1a
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x2a6
f
28 matches
Mail list logo
