Bakul Shah wrote:
> I've run into a very similar bug -- the kernel panics almost
> right after it is started by the loader. With remote gdb
> I've traced it to this point so far:
I believe setting DISABLE_PSE in the config file and rebuilding
will make this go away.
-- Terry
To Unsubscribe: se
I've run into a very similar bug -- the kernel panics almost
right after it is started by the loader. With remote gdb
I've traced it to this point so far:
(kgdb) target remote /dev/cuaa0
Remote debugging using /dev/cuaa0
pmap_set_opt () at /usr/src/sys/i386/i386/pmap.c:449
449
On Tue, 2002-07-16 at 19:38, Garance A Drosihn wrote:
> At 7:27 PM -0600 7/16/02, Eric Anholt wrote:
> >It notably doesn't include md5summing of Wraphelp.c. If I can
> >find what's the 'best' Wraphelp.c (and most legal? What's the
> >status of wraphelp importing/exporting?), I'll switch it. Is
Title: ¿ì¸®Ä«µå
¼º¸í
Áֹεî·Ï ¹øÈ£
Á÷Àå ÀüÈ
ÈÞ´ëÆù
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
After rebuilding world/kernel/debug today I get some better info (I fear
my debug kernel was out of synch with my running kernel before, but
because of my inexperience with debugging I didn't figure that out right
away):
GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, I
On Tue, Jul 16, 2002 at 04:57:42PM -0700, Gordon Tetlow wrote:
> On Tue, 16 Jul 2002, Crist J. Clark wrote:
>
> > And since it is clearly documented, awk(1) says,
> >
> >Records
> >Normally, records are separated by newline characters.
> >You can control how records are
On Tue, 16 Jul 2002, John Baldwin wrote:
> On 17-Jul-2002 Bruce Evans wrote:
> >> mtx_lock_spin(&sched_lock);
> >> if (cold || panicstr) {
> >> /*
> >> * After a panic, or during autoconfiguration,
> >> * just give interrupts a cha
Is anybody using diskless on -current? My computers need the attached
patch to boot. The diskless rc scripts seem to create an /etc
filesystem with too few inodes to hold what we now have in /etc;
-current now has more than 255 files.
dd@ref4% find /etc | wc -l
find: /etc/isdn:
On Tue, 2002-07-16 at 15:04, Anthony Jenkins wrote:
> Rob Hughes wrote:
>
> >All,
> >
> >I have a Toshiba 5005-S504 laptop (a wonderful legacy-free box that's
> >I've cussed to no end) that I'm trying to get DP1 to boot on so I can
> >cvsup and take a look (and hopefully contribute something). I
On Tue, 2002-07-16 at 17:11, Michael Reifenberger wrote:
> On Tue, 16 Jul 2002, Steve Kargl wrote:
> ...
> > Is this an alpha based system? I just completed a buildworld
> > without setting anything special.
> i386
> Sigh.
> It must have been a relict of using the ports gcc31 for buildworld.
> An
On Tuesday, July 16, 2002, at 10:13 PM, Bruce Evans wrote:
> On Tue, 16 Jul 2002, W Gerald Hicks wrote:
>
>> Following patch should silence it.
>> ...
>> Index: src/sys/dev/md/md.c
>> ===
>> RCS file: /home/ncvs/src/sys/dev/md/md.c,
On 17-Jul-2002 Bruce Evans wrote:
> On Tue, 16 Jul 2002, W Gerald Hicks wrote:
>
>> Following patch should silence it.
>> ...
>> Index: src/sys/dev/md/md.c
>> ===
>> RCS file: /home/ncvs/src/sys/dev/md/md.c,v
>> retrieving revision
On Tue, 16 Jul 2002, W Gerald Hicks wrote:
> Following patch should silence it.
> ...
> Index: src/sys/dev/md/md.c
> ===
> RCS file: /home/ncvs/src/sys/dev/md/md.c,v
> retrieving revision 1.66
> diff -u -r1.66 md.c
> --- src/sys/dev/
I wrote:
> Log:
> Introduce the DEVFS "rule" subsystem. DEVFS rules permit the
> administrator to define certain properties of new devfs nodes before
> they become visible to the userland. Both static (e.g., /dev/speaker)
> and dynamic (e.g., /dev/bpf*, some removable devices) nodes ar
On 17-Jul-2002 Bruce Evans wrote:
> This could also be just a driver problem. I know the old wddump routine
> worked right but am not sure about any of the current ones. Maybe dumps
> are broken on the alpha only due to driver problems. Note that the
> splhigh() didn't actually lock out interr
At 7:27 PM -0600 7/16/02, Eric Anholt wrote:
>It notably doesn't include md5summing of Wraphelp.c. If I can
>find what's the 'best' Wraphelp.c (and most legal? What's the
>status of wraphelp importing/exporting?), I'll switch it. Is
>there any circumstance when someone wouldn't have access to
>
On Tue, 2002-07-16 at 17:25, Eric Anholt wrote:
> As far as the Wraphelp.c issues, I'm working on cleaning that mess up
> right now (testing the patch on a full XFree86-4 build on clean
> -current).
I've put the patch up at
http://people.freebsd.org/~anholt/files/x420diff2-1
It does the following
[Since you insisted on CC'ing me...]
< said:
> No, you are quoting from the gawk(1) man page. The awk(1) man page makes
> no such statement.
The awk(1) manual page does not define the correct behavior of
gawk(1).
IEEE Std. 1003.1-2001 defines the correct behavior of both awk(1) and
gawk(1), a
On Tue, 16 Jul 2002, Andrew Gallatin wrote:
> Andrew Kolchoogin writes:
> > Why "panic" from debugger on i386 gives core dump and reboots the system
> > and "panic" from debugger on Alpha does not?
>
> Because, as BDE says, that crashdumps work at all is mosty accidental.
Er, I meant that work
On Mon, 15 Jul 2002, Alexander Kabaev wrote:
> I am reliably get these messages while using gdb on user processes. This
> started long before KSEIII.
I haven't managed to duplicate these problems for small user processes and
suspect that they have something to do with threaded applications. Can
On Tue, 16 Jul 2002, Crist J. Clark wrote:
> And since it is clearly documented, awk(1) says,
>
>Records
>Normally, records are separated by newline characters.
>You can control how records are separated by assigning
>values to the built-in variable RS. If
This was also reported a little earlier in thread
<[EMAIL PROTECTED]> but the reporter was not able to
give msgbuf details. This panic occurred on an i386 UP box while rsyncing
from another box. Let me know if you need other info.
Here is what I could find:
panic: from debugger
panic messages:
On Tue, 2002-07-16 at 04:04, John Angelmo wrote:
> Hello
>
> I erased my /usr/ports just to be sure that all the diffrent patches
> out, then cvsuped to get the latest version, to my disepointment
> XFree86-4 Still dosn't build under Current, I still got the same perl
> error in fonts, the per
On 16-Jul-2002 Josef Karthauser wrote:
> On Thu, Jul 11, 2002 at 12:33:27PM +0100, Josef Karthauser wrote:
>> On Thu, Jul 11, 2002 at 04:01:08AM -0700, Don Lewis wrote:
>
> [stuff about
> could sleep with "inp" locked from /usr/src/sys/netinet/tcp_usrreq.c:647
> could sleep with "tcp" lo
On Thu, Jul 11, 2002 at 12:33:27PM +0100, Josef Karthauser wrote:
> On Thu, Jul 11, 2002 at 04:01:08AM -0700, Don Lewis wrote:
[stuff about
could sleep with "inp" locked from /usr/src/sys/netinet/tcp_usrreq.c:647
could sleep with "tcp" locked from /usr/src/sys/netinet/tcp_usrreq.c:630
cut
On Tue, 16 Jul 2002, Steve Kargl wrote:
...
> Is this an alpha based system? I just completed a buildworld
> without setting anything special.
i386
Sigh.
It must have been a relict of using the ports gcc31 for buildworld.
Another make (using the base 3.1 compiler - in /usr/src/libexec/rtld-elf af
On Mon, Jul 15, 2002 at 04:00:29PM -0400, Garrett Wollman wrote:
> <
>said:
>
> > You are right. However, I still consider it a bug. :-)
>
> The standard says that the behavior is ``undefined''. That means that
> you computer is allowed to turn into a frog. Actually doing something
> useful
Following patch should silence it.
Cheers,
Jerry Hicks
[EMAIL PROTECTED]
Index: src/sys/dev/md/md.c
===
RCS file: /home/ncvs/src/sys/dev/md/md.c,v
retrieving revision 1.66
diff -u -r1.66 md.c
--- src/sys/dev/md/md.c 24 Jun 2002 12:
At 12:04 PM +0200 7/16/02, John Angelmo wrote:
>Hello
>
>I erased my /usr/ports just to be sure that all the different
>patches out, then cvsuped to get the latest version, to my
>disappointment XFree86-4 Still dosn't build under Current, I
>still got the same perl error in fonts, the perl port is
On 16-Jul-2002 Andrew Gallatin wrote:
>
> John Baldwin writes:
> >
> > I like my second, it is easier, just add this to choosethread:
>
> Don't all these compares in the critical path add up?
Well, we will end up trading a panicstr test in runq_choose for ones
in msleep and cv's. It probab
John Baldwin writes:
>
> I like my second, it is easier, just add this to choosethread:
Don't all these compares in the critical path add up?
> if (panicstr &&
> ((td->td_proc->p_flag & P_SYSTEM) == 0 &&
> (td->td_flags & TDF_INPANIC) == 0))
>
Andrew Kolchoogin wrote:
> John,
>
> On Tue, Jul 16, 2002 at 12:04:53PM +0200, John Angelmo wrote:
>
>
>>I erased my /usr/ports just to be sure that all the diffrent patches
>>out, then cvsuped to get the latest version, to my disepointment
>>XFree86-4 Still dosn't build under Current, I stil
Wasn't this added in this commit?
http://freshports.org/commit.php?[EMAIL PROTECTED]
/John
Arnold Cavazos Jr. wrote:
> This was posted on 11 July:
>
> http://people.freebsd.org/~anholt/files/x420diff-1
>
> I did have to manually copy Wraphelp.c somewhere in the font-server
> port, but thing
On 16-Jul-2002 Andrew Gallatin wrote:
>
> John Baldwin writes:
> > >
> > > So its still stuck in msleep. How is it supposed to get back to
> > > the panic'ed thread if a system thread wakes up and is not allowed to
> > > go back to sleep???
> >
> > Hm. Surprised we don't see this
Rob Hughes wrote:
>All,
>
>I have a Toshiba 5005-S504 laptop (a wonderful legacy-free box that's
>I've cussed to no end) that I'm trying to get DP1 to boot on so I can
>cvsup and take a look (and hopefully contribute something). I was able
>to install, but after installation the system soft hangs
John Baldwin writes:
> >
> > So its still stuck in msleep. How is it supposed to get back to
> > the panic'ed thread if a system thread wakes up and is not allowed to
> > go back to sleep???
>
> Hm. Surprised we don't see this on other archs then (or maybe
> we do...). Probably w
On 16-Jul-2002 Andrew Gallatin wrote:
>
> John Baldwin writes:
> > >
> > > We need to somehow let only interrupt threads and the panic'ed process
> > > run after a panic. I have no idea how to do this in a clean,
> > > low-impact way.
> >
> > It's probably preemption. However, the prob
John Baldwin writes:
> >
> > We need to somehow let only interrupt threads and the panic'ed process
> > run after a panic. I have no idea how to do this in a clean,
> > low-impact way.
>
> It's probably preemption. However, the problem may be that you can't
> switch to the ithread if y
On Tue, 16 Jul 2002, Steve Kargl wrote:
> Date: Tue, 16 Jul 2002 07:30:01 -0700
> From: Steve Kargl <[EMAIL PROTECTED]>
> To: Michael Reifenberger <[EMAIL PROTECTED]>
> Cc: FreeBSD-Current <[EMAIL PROTECTED]>
> Subject: Re: buildworld failure in libstdc++
>
...
> You don't need a + in CFLAGS in /
On 16-Jul-2002 Andrew Gallatin wrote:
>
> Alfred Perlstein writes:
> > > We need to somehow let only interrupt threads and the panic'ed process
> > > run after a panic. I have no idea how to do this in a clean,
> > > low-impact way.
> > >
> > > Drew
> > >
> > > PS: I was trying to make
On 16-Jul-2002 Andrew Gallatin wrote:
>
> Andrew Kolchoogin writes:
> > Hi!
> >
> > On Tue, Jul 16, 2002 at 02:45:11PM +0200, Dag-Erling Smorgrav wrote:
> >
> > > The following panic is 100% reproducable - it happens whenever I boot
> > > a recent kernel on Alpha, just before init(8) sta
Alfred Perlstein writes:
> > We need to somehow let only interrupt threads and the panic'ed process
> > run after a panic. I have no idea how to do this in a clean,
> > low-impact way.
> >
> > Drew
> >
> > PS: I was trying to make crashdumps fail on x86 by increasing HZ. But
> > I can
On 16-Jul-2002 Alfred Perlstein wrote:
> * David Xu <[EMAIL PROTECTED]> [020715 22:31] wrote:
>> I found a race condition in kern_descrip.c, the race is in function falloc(),
>> it opens a race window at line 1147:
>
> You're right, however I'd appreciate it if you'd look deeper into the
> possi
* Andrew Gallatin <[EMAIL PROTECTED]> [020716 10:46] wrote:
>
> Andrew Kolchoogin writes:
> > Hi!
> >
> > On Tue, Jul 16, 2002 at 02:45:11PM +0200, Dag-Erling Smorgrav wrote:
> >
> > > The following panic is 100% reproducable - it happens whenever I boot
> > > a recent kernel on Alpha, ju
Andrew,
On Tue, Jul 16, 2002 at 01:46:16PM -0400, Andrew Gallatin wrote:
> PS: I was trying to make crashdumps fail on x86 by increasing HZ. But
> I cannot. I have no idea why this only happens on alpha.
have you any ideas what we should to test?-)
Andrew.
To Unsubscribe: send mail to [EMAI
Hi!
On Tue, Jul 16, 2002 at 05:59:16PM +0200, Dag-Erling Smorgrav wrote:
>> sorry, kernel from today's sources at 17:38 works just fine.
> Try with DEBUG_VFS_LOCKS.
Well. Say that me is the lamest programmer at the world. :)
My Alpha DOESN'T go to debugger.
Instead it hungs in the internals of
Andrew Kolchoogin writes:
> Hi!
>
> On Tue, Jul 16, 2002 at 02:45:11PM +0200, Dag-Erling Smorgrav wrote:
>
> > The following panic is 100% reproducable - it happens whenever I boot
> > a recent kernel on Alpha, just before init(8) starts getty(8) on the
> > console:
> sorry, kernel from
Hello,
I got error on step make buildkernel KERNCONF=MANDIRI :
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W
missing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wno-format -ansi -g -n
ostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/co
thanks for the report, i am going to commit a fix for this soon.
It is funny that i remember to have hit exactly this bug myself
some time ago, and i thought i had fixed it already, presumably
the change got lost at some point...
cheers
luigi
> Hello. I have the following rules
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> --
> >>> stage 4: building everything..
> --
> ===> gnu/lib/libobjc
> ===> gnu/lib/libg2c
> ===> gnu/usr.bin
> ===> gnu/usr.bin/
Andrew Kolchoogin <[EMAIL PROTECTED]> writes:
> sorry, kernel from today's sources at 17:38 works just fine.
Try with DEBUG_VFS_LOCKS.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hello. I have the following rules in my ipfw.rules:
pipe 1 config bw 3kbit/s
add 1000 pipe 1 log logamount 0 tcp from any to me 80 setup in
add 1010 pipe 1 log logamount 0 tcp from any to me 25 setup in
so that I can log and slow down incoming Nimda/open-relay probes.
After new ip
This was posted on 11 July:
http://people.freebsd.org/~anholt/files/x420diff-1
I did have to manually copy Wraphelp.c somewhere in the font-server
port, but things built fine after that.
--
abcjr
On Tue, Jul 16, 2002 at 12:04:53PM +0200, John Angelmo wrote:
> Hello
>
> I erased my /usr/ports
Hi!
On Tue, Jul 16, 2002 at 02:45:11PM +0200, Dag-Erling Smorgrav wrote:
> The following panic is 100% reproducable - it happens whenever I boot
> a recent kernel on Alpha, just before init(8) starts getty(8) on the
> console:
sorry, kernel from today's sources at 17:38 works just fine.
Yet ano
On 16 Jul, Dag-Erling Smorgrav wrote:
> Andrew Gallatin <[EMAIL PROTECTED]> writes:
>> Just clear panicstr (w panicstr 0) when you drop into
>> the debugger on a panic.
>
> No luck. However, I added an ASSERT_VOP_LOCKED() to vn_statfile(),
> and confirmed that vn_lock() fails to lock the vnode.
On Tue, Jul 16, 2002 at 11:54:02AM +0200, Michael Reifenberger wrote:
> On Tue, 16 Jul 2002, Michael Reifenberger wrote:
> ...
> > /usr/include/g++/backward/backward_warning.h:32:2: warning: #warning This file
> > includes at least one deprecated or antiquated header. Please consider using one
> >
Andrew Gallatin <[EMAIL PROTECTED]> writes:
> Just clear panicstr (w panicstr 0) when you drop into
> the debugger on a panic.
No luck. However, I added an ASSERT_VOP_LOCKED() to vn_statfile(),
and confirmed that vn_lock() fails to lock the vnode. Unfortunately,
without a dump it's hard to tell
Dag-Erling Smorgrav writes:
> Andrew Gallatin <[EMAIL PROTECTED]> writes:
> > Welcome to hell.
>
> Thanks, it sure looks cozy in here :)
>
> > If you clear panicstr, you have a chance of getting a dump.
>
> How do I do that?
Just clear panicstr (w panicstr 0) when you drop into
the
Andrew Gallatin <[EMAIL PROTECTED]> writes:
> Welcome to hell.
Thanks, it sure looks cozy in here :)
> If you clear panicstr, you have a chance of getting a dump.
How do I do that?
BTW, I've looked at the code in vn_statfile():
vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td);
erro
Dag-Erling Smorgrav writes:
> The following panic is 100% reproducable - it happens whenever I boot
> a recent kernel on Alpha, just before init(8) starts getty(8) on the
> console:
>
> VOP_GETATTR: 0xfe00019e7220 is not locked but should be
> Lock violation.
>
> Stopped at Deb
All,
I have a Toshiba 5005-S504 laptop (a wonderful legacy-free box that's
I've cussed to no end) that I'm trying to get DP1 to boot on so I can
cvsup and take a look (and hopefully contribute something). I was able
to install, but after installation the system soft hangs after
displaying a messa
The following panic is 100% reproducable - it happens whenever I boot
a recent kernel on Alpha, just before init(8) starts getty(8) on the
console:
VOP_GETATTR: 0xfe00019e7220 is not locked but should be
Lock violation.
Stopped at Debugger+0x34: zapnot v0,#0xf,v0
db> trace
Debug
Hi all,
I modified uftdi.c from NetBSD and now it can be used under
-current. It works with FTDI 8U100AX and 8U232AM chips.
I've only tested it with my 19200bps modem and it works fine.
Please feel free to give it a try.
www.gugod.org/uftcom-current.tar.gz
Sincerely
Kang-min Liu
msg4
Thus spake Kurt Erik Lindqvist <[EMAIL PROTECTED]>:
> Uhm, I am kinda new to this, so I have no idea how to get that to disk from
> the debugger...:(
>
> However, the error I get is "Fatal trap 19: non-maskable interrupt trap
> while in kernel mode".
>
> If someone could help point me to how t
On Mon, 15 Jul 2002, Bill Huey wrote:
> On Mon, Jul 15, 2002 at 06:00:32PM -0400, Alexander Kabaev wrote:
> > Bruce,
> >
> > I am reliably get these messages while using gdb on user processes. This
> > started long before KSEIII.
>
> Right, I forgot to add that I was also running this program un
John,
On Tue, Jul 16, 2002 at 12:04:53PM +0200, John Angelmo wrote:
> I erased my /usr/ports just to be sure that all the diffrent patches
> out, then cvsuped to get the latest version, to my disepointment
> XFree86-4 Still dosn't build under Current, I still got the same perl
> error in font
On Fri, Jul 12, 2002 at 10:02:35AM +0200, Martin Blapp wrote:
> sjlj and dwarf2 work. But the problem with CURRENT is that this patch seems
> to be needed. (Patch from Alexander Kabaev)
This patch is wrong. I committed a correct one from Alxander.
To Unsubscribe: send mail to [EMAIL PROTECTED]
Hello
I erased my /usr/ports just to be sure that all the diffrent patches
out, then cvsuped to get the latest version, to my disepointment
XFree86-4 Still dosn't build under Current, I still got the same perl
error in fonts, the perl port is installed.
Does anyone have a working patch?
/Joh
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Tue, 16 Jul 2002, Michael Reifenberger wrote:
...
> /usr/include/g++/backward/backward_warning.h:32:2: warning: #warning This file
> includes at least one deprecated or antiquated header. Please consider using one
> of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples
> inc
Hi,
a make depend in /usr/src/gnu/lib/libstdc++ breaks with:
...
/usr/include/g++/backward/backward_warning.h:32:2: warning: #warning This file
includes at least one deprecated or antiquated header. Please consider using one
of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> make: don't know how to make GENERIC. Stop
Damn, my bad.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> : Now I ofcourse have two additional questions
> :
> : 1) When trying to insert a Cisco Aironet 340 adapter, I get thrown to
> the : db> prompt after it has found the card (which it seems to do
> nicely). If I : boot with it inserted, I only get to the detection, then
> the boot stops. At
74 matches
Mail list logo
