the
panic on boot.
Thanks for the quick response as ever.
Great, thanks for testing! Randall, do you have any thoughts on these
patches?
Vince
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
Hi again,
The 2nd patch (to if.h and if_gif.c) also fixes the
panic on boot.
Thanks for the quick response as ever.
Vince
On 20/06/2012 13:12, John Baldwin wrote:
On Tuesday, June 19, 2012 8:05:36 pm Vincent Hoffman wrote:
Full dump info at http://unsane.co.uk/crash
It seems
On Thursday, June 21, 2012 12:41:59 pm Vincent Hoffman wrote:
Hi again,
The 2nd patch (to if.h and if_gif.c) also fixes the
panic on boot.
Thanks for the quick response as ever.
Great, thanks for testing! Randall, do you have any thoughts on these
patches?
Vince
On 20
On Tuesday, June 19, 2012 8:05:36 pm Vincent Hoffman wrote:
Full dump info at http://unsane.co.uk/crash
It seems to have popped up between r236905 (working kernel) and r237264
(this panic)
the gif config I have in rc.conf is for a HE ipv6 tunnel
Looks like this was broken in r236951 by
The patch to gif.c does fix it.
I'll try the second patch later when I get a chance.
Thanks,
Vince
On 20/06/2012 13:12, John Baldwin wrote:
On Tuesday, June 19, 2012 8:05:36 pm Vincent Hoffman wrote:
Full dump info at http://unsane.co.uk/crash
It seems to have popped up between r236905
Full dump info at http://unsane.co.uk/crash
It seems to have popped up between r236905 (working kernel) and r237264
(this panic)
the gif config I have in rc.conf is for a HE ipv6 tunnel
cloned_interfaces=gif0
ifconfig_gif0=tunnel 85.233.185.162 216.66.80.26
ifconfig_gif0_ipv6=inet6
1. It's in the dump file.
2. In BEASTIE.
3. As I wrote before, 9.0-BETA1, but I had used this kernel with 8.2-RELEASE
and 8.2-STABLE (only did slight modifications for 9.0).
4. I'm not really into it, what exactly do you mean?
BEASTIE
Description: Binary data
dump
Description: Binary data
On 2 September 2011 15:41, Piotr Kubaj freebsd.current.l...@gmail.com wrote:
1. It's in the dump file.
2. In BEASTIE.
3. As I wrote before, 9.0-BETA1, but I had used this kernel with 8.2-RELEASE
and 8.2-STABLE (only did slight modifications for 9.0).
4. I'm not really into it, what exactly do
On Fri, Sep 2, 2011 at 1:49 PM, Sergey Kandaurov pluk...@gmail.com wrote:
On 2 September 2011 15:41, Piotr Kubaj freebsd.current.l...@gmail.com
wrote:
1. It's in the dump file.
2. In BEASTIE.
3. As I wrote before, 9.0-BETA1, but I had used this kernel with
8.2-RELEASE
and 8.2-STABLE
I've upgraded today to beta 2 (with the newest sources atm). The procedure was
as described in the handbook: make buildworld -j3; make buildkernel -j3
KERNCONF=MYKERNEL; make installkernel KERNCONF=MYKERNEL (the kernel I used was
the same as for beta 1, for which it worked flawlessly); reboot
On Thu, Sep 1, 2011 at 4:06 PM, Piotr Kubaj
freebsd.current.l...@gmail.com wrote:
I've upgraded today to beta 2 (with the newest sources atm). The procedure
was as described in the handbook: make buildworld -j3; make buildkernel -j3
KERNCONF=MYKERNEL; make installkernel KERNCONF=MYKERNEL (the
Please help! Can't load system after update on r224468
mount partition is UFS, no startup settings changed,
no CONF file changed.
make buildworld buildkernel installworld installkernel
now I loaded old r221725.
___
freebsd-current@freebsd.org mailing
Sorry for panic. I have another HDD with partition s1a, after update, HDD
renumerated.
vfs.root.mountfrom in loader.conf solved my problem
28 июля 2011, 01:02 от Andrey Smagin samsp...@mail.ru:
Please help! Can't load system after update on r224468
mount partition is UFS, no startup settings
Hello list,
here is a digital camera pic of a panic that happened while booting
yesterdays Source tree
http://www.puffybsd.com/IMG_4136.JPG
here is a dmesg from a older current
http://www.puffybsd.com/amddmesg.txt
--
Sam Fourman Jr.
Fourman Networks
http://www.fourmannetworks.com
On Sun, Nov 7, 2010 at 10:02 AM, Sam Fourman Jr. sfour...@gmail.com wrote:
Hello list,
here is a digital camera pic of a panic that happened while booting
yesterdays Source tree
http://www.puffybsd.com/IMG_4136.JPG
here is a dmesg from a older current
http://www.puffybsd.com/amddmesg.txt
On Sun, Nov 7, 2010 at 1:29 PM, Garrett Cooper gcoo...@freebsd.org wrote:
On Sun, Nov 7, 2010 at 10:02 AM, Sam Fourman Jr. sfour...@gmail.com wrote:
Hello list,
here is a digital camera pic of a panic that happened while booting
yesterdays Source tree
http://www.puffybsd.com/IMG_4136.JPG
On Sun, Nov 7, 2010 at 12:42 PM, Sam Fourman Jr. sfour...@gmail.com wrote:
On Sun, Nov 7, 2010 at 1:29 PM, Garrett Cooper gcoo...@freebsd.org wrote:
On Sun, Nov 7, 2010 at 10:02 AM, Sam Fourman Jr. sfour...@gmail.com wrote:
Hello list,
here is a digital camera pic of a panic that happened
I saw the ACPI warning on top so I blamed ACPI...
maybe I was wrong, this stuff is not my strong suit
It's ok :) (one thing to note is that the ACPI warning is present
in both cases)... It would be interesting to note what modules you
load (in particular the geom ones), and what GEOM
Qemu 0.11.1 installed from port with -CURRENT as host, emulating 8 CPU
on a 8-way box
makes my FreeBSD -CURRENT guest kernel, panic with this bt at boot:
panic: sched_priority: invalid priority 230: nice 0, ticks 2289712
ftick 353 ltick 1363 tick pri 50
cpuid = 7
KDB: stack backtrace
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
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 a...@icyb.net.ua 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
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
___
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: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 output of
Howdy,
I tried upgrading from r209351 to r209434 and got a panic related to the
timer stuff while booting. You can see the panic and the backtrace here:
http://people.freebsd.org/~dougb/timer-panic-1.jpg
http://people.freebsd.org/~dougb/timer-panic-2.jpg
On 06/22/10 12:55, Doug Barton wrote:
Howdy,
I tried upgrading from r209351 to r209434 and got a panic related to the
timer stuff while booting. You can see the panic and the backtrace here:
http://people.freebsd.org/~dougb/timer-panic-1.jpg
Doug Barton wrote:
On 06/22/10 12:55, Doug Barton wrote:
Howdy,
I tried upgrading from r209351 to r209434 and got a panic related to the
timer stuff while booting. You can see the panic and the backtrace here:
http://people.freebsd.org/~dougb/timer-panic-1.jpg
On 06/22/10 13:10, Alexander Motin wrote:
Doug Barton wrote:
On 06/22/10 12:55, Doug Barton wrote:
Howdy,
I tried upgrading from r209351 to r209434 and got a panic related
to the timer stuff while booting. You can see the panic and the
backtrace here:
Doug Barton wrote:
On 06/22/10 13:10, Alexander Motin wrote:
Doug Barton wrote:
On 06/22/10 12:55, Doug Barton wrote:
Howdy,
I tried upgrading from r209351 to r209434 and got a panic related
to the timer stuff while booting. You can see the panic and the
backtrace here:
On 06/22/10 14:17, Alexander Motin wrote:
Run `sysctl kern.eventtimer.timer2=i8254`, then after few seconds check
messages to see if system liked this timer (it should fall back
automatically if it's not),
Seems ok. Here is what I got on the console, no error messages in
/var/log/all.
sysctl
Doug Barton wrote:
On 06/22/10 14:17, Alexander Motin wrote:
Run `sysctl kern.eventtimer.timer2=i8254`, then after few seconds check
messages to see if system liked this timer (it should fall back
automatically if it's not),
Seems ok. Here is what I got on the console, no error messages in
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
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
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
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
George Hartzell writes:
I've been trying to install something 5-ish on a Sony PCG-GRX570
laptop.
I started off trying to boot off of the 5.1 release CD, normally,
w/out acpi, and safe. Every option panic-ed, with essentially the
same message (see below), although it followed a
I've been trying to install something 5-ish on a Sony PCG-GRX570
laptop.
I started off trying to boot off of the 5.1 release CD, normally,
w/out acpi, and safe. Every option panic-ed, with essentially the
same message (see below), although it followed a different driver
depending on how it was
On Tue, 26 Aug 2003, Kenneth Culver wrote:
I think some people are already tracking this down related to the recent
update of the ata drivers.
It would be nice if those people would post regarding their progress. A
lot of people depend on atapicam.
Doug
--
This .signature sanitized for
last night's sources:
free_hcb()
atapi_action()
xpt_run_dev_sendq()
xpt_action()
probe_start()
...
appears to be a memory access error.
-Alfred
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
free_hcb()
atapi_action()
xpt_run_dev_sendq()
xpt_action()
probe_start()
...
I think some people are already tracking this down related to the recent
update of the ata drivers.
Ken
___
[EMAIL PROTECTED] mailing list
On Thu, Jul 03, 2003 at 10:34:34AM -0400, John Baldwin wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 0100
fault virtual address = 0xdf119fec
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc030b254
stack
On 03-Jul-2003 Kris Kennaway wrote:
Anyone's ears burning? :)
Kris
Booting [/boot/kernel/kernel]...
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights
Anyone's ears burning? :)
Kris
Booting [/boot/kernel/kernel]...
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #22: Wed Jul 2
On Thu, Jul 03, 2003 at 01:56:02AM +, Daniel Flickinger wrote:
I have not been able to boot a kernel since 13 Jun; my
Tyan 2642 with SMP, AMD 1.2s, and SCSI only gets as far as:
What versions of the BIOS? I have 2 of these systems and both boot a
June 30th kernel just fine.
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
With 5.1-RELEASE and all recent SNAP's a Compaq Proliant 1850R I have
here will panic during boot. The symptoms are consistent with the
report mailed in by Ventsislav Velkov [EMAIL PROTECTED] on March 31st
about other Compaq hardware, so it is within the realm of imagination
that the machine
In message [EMAIL PROTECTED], Bryan Liesner writes:
Revision 1.20 / (download) - annotate - [select for diffs], Mon Mar 10 23:41:41
2003 UTC (5 days, 5 hours ago) by phk
Branch: MAIN
CVS Tags: HEAD
Changes since 1.19: +5 -0 lines
Diff to previous 1.19 (colored)
If we run out of
On Sun, 16 Mar 2003, Poul-Henning Kamp wrote:
I think Poul-Henning will have enough information to go with now...
You guys _way_ overestimate my abilities here.
Right now I have a hard time imagining what geom's eventhandling
for withering geoms can possibly have to do with any non-geom
On Sun, 16 Mar 2003, Poul-Henning Kamp wrote:
One thing I'd like you to try is to remove any trace of USB from your
systems. USB does some ugly VOP_REVOKES which I am not happy about, and
I would like to exclude them from the list of suspects.
You can remove USB from your list, I tried
list, I tried building without USB in the
kernel, and the panic remains...
Which of these flags have you been using?:
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
I normally use only the 686 flag, but when I included the 586 my
panic-on-boot changed to a panic
USB from your list, I tried building without USB in the
kernel, and the panic remains...
Which of these flags have you been using?:
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
I normally use only the 686 flag, but when I included the 586 my
panic-on-boot changed
On Sun, Mar 16, 2003 at 09:29:15AM +0100, Poul-Henning Kamp wrote:
I don't think I'll stand a chance on this one until I can reproduce it
on one of my machines :-(
I'm not sure if that helps, but on my machine it it enough to take
GENERIC kernconf file, add all GEOM_ options and comment out
In message [EMAIL PROTECTED], Krzysztof Parz
yszek writes:
On Sun, Mar 16, 2003 at 09:29:15AM +0100, Poul-Henning Kamp wrote:
I don't think I'll stand a chance on this one until I can reproduce it
on one of my machines :-(
I'm not sure if that helps, but on my machine it it enough to take
On 15-Mar-2003 Bryan Liesner wrote:
On Fri, 14 Mar 2003, Conrad Sabatier wrote:
Now, really, am I the only one experiencing this?
No, you're not. I've been unable to get a bootable kernel running for the
last few days also.
Booting in verbose mode, I see the last thing that occurs just
cheer! wilma heeft het door.
guest werkt.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Conrad Sabatier
Sent: zaterdag 15 maart 2003 13:22
To: Bryan Liesner
Cc: [EMAIL PROTECTED]
Subject: Re: panic on boot (devfs_find)
On 15-Mar-2003 Bryan Liesner wrote
whoops wrong list...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Bug
Sent: zaterdag 15 maart 2003 13:25
To: Conrad Sabatier; Bryan Liesner
Cc: [EMAIL PROTECTED]
Subject: RE: panic on boot (devfs_find)
cheer! wilma heeft het door.
guest werkt
--- Conrad Sabatier [EMAIL PROTECTED] wrote:
Booting in verbose mode, I see the last thing that occurs just before the panic
is mounting root and then starting (or trying to start) /sbin/init. After an
initial hang, it drops into ddb.
--
I found the same problem for the last two days.
On 15-Mar-2003 Shizuka Kudo wrote:
--- Conrad Sabatier [EMAIL PROTECTED] wrote:
Booting in verbose mode, I see the last thing that occurs just before the
panic is mounting root and then starting (or trying to start) /sbin/init.
After an initial hang, it drops into ddb.
--
I found
On 15-Mar-2003 Shizuka Kudo wrote:
I found the same problem for the last two days. However, it seems that this
problem doesn't appear in the GENERIC kernel. I have tried putting the
INVARIANTS stuffs back to my custom config file and it works as well. Very
strange...
I just built a
--- Bryan Liesner [EMAIL PROTECTED] wrote:
I was able to get a kernel up and running (strangely) on 3/12, but
commits after that cause an immediate panic as soon as init starts.
If I build a kernel from sources cut off at 3/10/2003 at 12:00,
everything works fine.
It is related to the
On Sat, 15 Mar 2003, Shizuka Kudo wrote:
--- Bryan Liesner [EMAIL PROTECTED] wrote:
I was able to get a kernel up and running (strangely) on 3/12, but
commits after that cause an immediate panic as soon as init starts.
If I build a kernel from sources cut off at 3/10/2003 at 12:00,
I made posts here recently describing some panics which are somehow
related to disappearing/never created device nodes. I am unable to
produce a core dump at all, as it panics before / is mounted.
The documented kern.dumpdev (unknown oid) doesn't exist and
setting dumpdev=ad0s1b in loader.conf
In message [EMAIL PROTECTED], Bryan Liesner writes:
I made posts here recently describing some panics which are somehow
related to disappearing/never created device nodes. I am unable to
produce a core dump at all, as it panics before / is mounted.
The documented kern.dumpdev (unknown oid)
On Fri, 14 Mar 2003, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Bryan Liesner writes:
I made posts here recently describing some panics which are somehow
related to disappearing/never created device nodes. I am unable to
produce a core dump at all, as it panics before / is
On 14-Mar-2003 Bryan Liesner wrote:
I made posts here recently describing some panics which are somehow
related to disappearing/never created device nodes. I am unable to
produce a core dump at all, as it panics before / is mounted.
The documented kern.dumpdev (unknown oid) doesn't exist
On Fri, 14 Mar 2003, Conrad Sabatier wrote:
Now, really, am I the only one experiencing this?
No, you're not. I've been unable to get a bootable kernel running for the last
few days also.
Booting in verbose mode, I see the last thing that occurs just before the panic
is mounting root and
--- walt [EMAIL PROTECTED] wrote:
04:00 GMT Mar 12:
Just cvsup'd and rebuilt with same result as 12 hours ago --
I see a kernel panic page fault while in kernel mode just
after attempting to mount the root filesystem.
The kernel from yesterday works fine and when I reboot the
oops, didn't cc this to the list
-- Forwarded message --
Date: Wed, 12 Mar 2003 15:50:01 -0500 (EST)
From: Bryan Liesner [EMAIL PROTECTED]
To: Shizuka Kudo [EMAIL PROTECTED]
Subject: Re: Still getting panic on boot.
On Wed, 12 Mar 2003, Shizuka Kudo wrote:
--- walt [EMAIL
04:00 GMT Mar 12:
Just cvsup'd and rebuilt with same result as 12 hours ago --
I see a kernel panic page fault while in kernel mode just
after attempting to mount the root filesystem.
The kernel from yesterday works fine and when I reboot the
filesystems come up clean, so the new kernel nevers
IPsec: Initialized Security Association Processing.
IP Filter: v3.4.29 initialized. Default = pass all, Logging = enabled
wi0: WaveLAN/IEEE at port 0x100-0x13f irq 11 function 0 config 1 on pccard0
wi0: 802.11 address: 00:02:2d:04:df:e4
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent
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 immediately.
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 where
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
On Wed, 11 Sep 2002, Nate Lawson wrote:
This is being worked on. See msg thread in cvs-all, starting with:
[EMAIL PROTECTED]. You can back out the
change (1.49) if you need to get running.
Sorry, 1.50 fixed the problem. I reverted back to kernel.old
anyways which was from a
Revelent info:
* $FreeBSD: src/sys/kern/kern_acct.c,v 1.49 2002/09/11 04:10:41 arr Exp $
Console output...
Starting syslogd.
Sep 11 12:35:51 bigbang syslogd: kernel boot file is /boot/kernel/kernel
Starting named.
Starting ntpdate.
Turning on accounting.
recursed on non-recursive lock (sleep
This is being worked on. See msg thread in cvs-all, starting with:
[EMAIL PROTECTED]. You can back out the
change (1.49) if you need to get running.
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0x8:0xc4109ac1
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
Fatal trap 9: general protection fault while in kernel mode
instruction pointer =
Mitsuru IWASAKI wrote:
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
Fatal trap 9: general protection fault while in kernel mode
instruction pointer
On Thu, Aug 01, 2002 at 10:14:34PM +0900, Mitsuru IWASAKI wrote:
Hmmm, I don't think so. How about typing
unset acpi_load
in loader prompt, and see if this panic disappear or still happen?
Where is it documented what to do to stop the autoloading of acpi.ko?
To Unsubscribe: send mail
Terry Lambert wrote:
Michael Nottebrock wrote:
I tweaked my BIOS to assign a different irq (9) to
the NIC and now the kernel boots and runs my old userland quite nicely.
The old kernel ran perfectly well with the NIC on irq10 ... strange.
None of your other postings identified the devices
Michael Nottebrock wrote:
I tweaked my BIOS to assign a different irq (9) to
the NIC and now the kernel boots and runs my old userland quite nicely.
The old kernel ran perfectly well with the NIC on irq10 ... strange.
None of your other postings identified the devices also on
IRQ10. If
Hi.
On Wed, Jul 03, 2002 at 09:36:24PM +0200, Rasmus Skaarup wrote:
I'm also suddenly having a panics - every 5 minutes actually, since my
latest cvsup a few hours ago. They seem to be related to some ufs
and ffs calls..
I'm not able to read my core dumps for some reason (gdb says kernel
I cvsup'd and built world+kernel a few hours ago and was happy to see
KDE working again, but I got a spontaneous reboot while trying to track
down a segfault in a mozilla build component. I boot -v'ed and as
soon as the login prompt came up I hit a panic. I'm guessing the
backgorund fsck
:I cvsup'd and built world+kernel a few hours ago and was happy to see
:KDE working again, but I got a spontaneous reboot while trying to track
:down a segfault in a mozilla build component. I boot -v'ed and as
:soon as the login prompt came up I hit a panic. I'm guessing the
:backgorund
I'm also suddenly having a panics - every 5 minutes actually, since my
latest cvsup a few hours ago. They seem to be related to some ufs
and ffs calls..
I'm not able to read my core dumps for some reason (gdb says kernel
symbol 'cpuhead' not found.) and I don't have the time to scratch a
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: Plug Play
Mike Silbersack wrote:
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.
On Tue, Feb 26, 2002 at 09:29:51PM -0800, 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
Peter Wemm wrote:
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
I'm experiencing the same double panic on boot that PHK is now; are we the
only ones, or is it just that nobody else has updated recently?
Mike Silby Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Mike Silbersack wrote:
I'm experiencing the same double panic on boot that PHK is now; are we the
only ones, or is it just that nobody else has updated recently?
If you are not using acpica, then you're probably using vm86 for pcibios
calls. I've been told that I've broken bios.c..
You may
On 26-Feb-2002 (17:27:19/GMT) Mike Silbersack wrote:
I'm experiencing the same double panic on boot that PHK is
now; are we the only ones, or is it just that nobody else
has updated recently?
Mee too, just survied to 4 auto-reboot without messages...
Trying with a boot -v I see a keyboard
On Tue, 26 Feb 2002, Peter Wemm wrote:
Mike Silbersack wrote:
I'm experiencing the same double panic on boot that PHK is now; are we the
only ones, or is it just that nobody else has updated recently?
If you are not using acpica, then you're probably using vm86 for pcibios
calls. I've
On Tue, 2002-02-26 at 17:38, Peter Wemm wrote:
You may like to try reverting this change:
A great idea, but unfortunately, incorrect ...
--
Michael D. Harnois bilocational bivocational
Pastor, Redeemer Lutheran ChurchWashburn, Iowa
1L, UST School of Law
On Tue, 26 Feb 2002, Mike Silbersack wrote:
I reverted that change, and the double panic still occured. :|
FWIW, you're correct in that I'm not using the acpi module.
Mike Silby Silbersack
Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
early in the boot
On Tue, 26 Feb 2002, David Wolfskill wrote:
Date: Tue, 26 Feb 2002 19:46:59 + (GMT)
From: Mike Silbersack [EMAIL PROTECTED]
Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
early in the boot process? The dumpon manpage doesn't suggest a way as
far as I can
Mike Silbersack wrote:
On Tue, 26 Feb 2002, David Wolfskill wrote:
Date: Tue, 26 Feb 2002 19:46:59 + (GMT)
From: Mike Silbersack [EMAIL PROTECTED]
Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
early in the boot process? The dumpon manpage doesn't
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.
Mike Silby Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
201 - 300 of 342 matches
Mail list logo
