> The PNP ones are normal, not sure about the digi ones; do you have any
> digiboards in your system?
Yes I do have a digi board (pci) in the system which is probed
correctly:
digi0 mem 0xb080-0xb0bf irq 10 at device 4.0 on pci0
But I don't have any ISA cards installed and I cou
Hi all,
I got now three times the same panic. Always it is now
T_PAGEFLT. And this is on new fresh ATA disks, a /dev/ar
raid.
So I guess I could say it is repeatable ;) It looks like
in February people had similar problems.
I have to admit that on the SCSI disk I do not run softupdates.
That m
On 13 Sep, Ian Dowse wrote:
> For example, if you hold the reference count at 1 while calling the
> cleanup function, it allows that function to safely add and drop
> references, but if that cleanup function has a bug that drops one
> too many references then you end up recursing instead of detec
On 13 Sep, Martin Blapp wrote:
>
> I've got some news here ...
>
> I have three different type of disks
>
> 1) - ATA100 Raid, 2 Disks a 80GB (striped)
> 2) - Vinum ATA Raid, 2 Disks a 16GB (striped)
> 3) - SCSI Disk
>
> I encounter pagefaults and all these nice panics on 1) and 2).
>
> I don'
On Thu, Sep 12, 2002 at 05:47:29PM -0700, David O'Brien wrote:
> On Thu, Sep 12, 2002 at 01:27:50PM -0700, Kris Kennaway wrote:
> > How are you supposed to disable -Werror in kernel builds? Setting
> > NO_WERROR in the env or passing it to 'make buildkernel' via -D
> > doesn't work; neither does
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
With current as of today, I can finally get the system to
boot without acpi enabled, but not otherwise. However,
with all combinations of hw.pcic.intr_path={0,1,2},
hw.pcic.irq=0, and hw.pcic.init_routing={0,1} the TI
is not happy and I can't use the wireless.
Since this system is acpi-only it
In message <[EMAIL PROTECTED]>, Terry Lambert writes:
>Ian Dowse wrote:
>> And I've just remembered a fifth :-) I think the old BSD code had
>> both an `open' count and a reference count. The open count is a
>> count of the real users of the vnode (it is what ufs_inactive really
>> wants to compar
On Thu, Sep 12, 2002 at 01:27:50PM -0700, Kris Kennaway wrote:
> How are you supposed to disable -Werror in kernel builds? Setting
> NO_WERROR in the env or passing it to 'make buildkernel' via -D
> doesn't work; neither does putting -Wno-error in COPTFLAGS. I get the
> following fatal warning w
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 pr
I've got some news here ...
I have three different type of disks
1) - ATA100 Raid, 2 Disks a 80GB (striped)
2) - Vinum ATA Raid, 2 Disks a 16GB (striped)
3) - SCSI Disk
I encounter pagefaults and all these nice panics on 1) and 2).
I don't see them if I build OpenOffice on the SCSI disk ! Doe
Kris Kennaway <[EMAIL PROTECTED]> writes:
> On Thu, Sep 12, 2002 at 01:52:40PM -0700, Nate Lawson wrote:
> > (who wants NO_WERROR back or better, warns-clean code more often in
> > -current)
>
> NO_WERROR is standard in userland; it should work in the kernel too.
Peter removed support for this a
Note that I run this system with same hardware for about
2 weeks on STABLE and there it works like a charm. I never
had any panics.
The panics began with gcc3.2 in the base system.
I run also without these ...
optionsDISABLE_PSE
optionsDISABLE_PG_G
Still looks like memory corr
I just installed -DP1, no problem. Then I made a world and kernel
(from sept 11 cvsup). Now I get this at boot:
FreeBSD 5.0-CURRENT #2: Thu Sep 12 21:20:00 CEST 2002
(...)
atapci0: port 0xe000-0xe00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 16 on atapci
On Thu, Sep 12, 2002 at 01:52:40PM -0700, Nate Lawson wrote:
> NO_WERROR was removed so the only way is to set in your make.conf:
> WERROR=
>
> This causes the WERROR?=-Werror to not set the flag.
Thanks, Bill Fenner also told me this on IRC. The directions in
/usr/src/UPDATING need to be fixe
On Thu, 12 Sep 2002, Kris Kennaway wrote:
> How are you supposed to disable -Werror in kernel builds? Setting
> NO_WERROR in the env or passing it to 'make buildkernel' via -D
> doesn't work; neither does putting -Wno-error in COPTFLAGS. I get the
> following fatal warning when compiling a recen
How are you supposed to disable -Werror in kernel builds? Setting
NO_WERROR in the env or passing it to 'make buildkernel' via -D
doesn't work; neither does putting -Wno-error in COPTFLAGS. I get the
following fatal warning when compiling a recent alpha 5.0 kernel under
4.x:
cc -c -O -pipe -Wno
After disabling ACPI through hints, the box has been up a few days, no
problems. Should I pursue this as a FreeBSD acpi problem or does Intel's
work on acpica have a long way to go? I don't really have an idea of what
we should expect from the current acpi implementation.
-Nate
On Thu, 5 Sep 2
On Thu, 12 Sep 2002, Robert Suetterlin wrote:
> Hi!
>
> I get some strange messages during device probing on my Current
> machine. I was pointed out that these might be due to device hints in
> /boot or compiled / configured into my kernel. Unfortunately I could
> not find any device hint
On 12 Sep 2002, Sid Carter wrote:
> > On Wed, 11 Sep 2002 11:30:55 -0700 (PDT), Nate Lawson <[EMAIL PROTECTED]> said:
>
> Nate> tell without more info. Enable options DDB, boot -vs, wait for the
> Nate> hang. Hit CTRL-ALT-ESC to go into DDB and type tr to get a
> Nate> backtrace
Maxim Sobolev wrote:
> Maxime Henrion wrote:
> >
> > Maxim Sobolev wrote:
> > > Any ideas?
> >
> > Looks like some other processes was modifying the mountlist while
> > vfs_unmountall() was running. Is this an SMP box ?
>
> No, it's UP.
>
> > It would be nice if
> > you could check in gdb whi
On Thu, Sep 12, 2002 at 10:21:38AM -0400, Wesley Morgan <[EMAIL PROTECTED]> wrote:
> I built all of XFree86 yesterday, with no problems. Try applying this
> patch to your compiler and rebuiling it:
>
> http://people.freebsd.org/~kan/gcc-all.diff
>
> On a side note to -current / gcc maintainers
Maxime Henrion wrote:
>
> Maxim Sobolev wrote:
> > Any ideas?
>
> Looks like some other processes was modifying the mountlist while
> vfs_unmountall() was running. Is this an SMP box ?
No, it's UP.
> It would be nice if
> you could check in gdb which other process was holding the mountlist_mt
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Ian Dowse wrote:
> And I've just remembered a fifth :-) I think the old BSD code had
> both an `open' count and a reference count. The open count is a
> count of the real users of the vnode (it is what ufs_inactive really
> wants to compare against 0), and the reference count is just for
> places
On Wed, Sep 11, 2002 at 10:16:40PM -0500, Dan Nelson wrote:
> In the last episode (Sep 11), David O'Brien said:
> > I'd like to make this commit to get better performance on today's
> > streaming tape drives. It seems my DLT drive doesn't stream well
> > with the default block size of '10'.
>
>
On 11-Sep-2002 Don Lewis wrote:
> On 11 Sep, John Baldwin wrote:
>>
>> On 11-Sep-2002 Don Lewis wrote:
>>> On 10 Sep, Don Lewis wrote:
On 10 Sep, Nate Lawson wrote:
> I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen
> before grabbing the proc lock. Dropp
On 18:46+0400, Sep 12, 2002, Kris Kennaway wrote:
> On Thu, Sep 12, 2002 at 12:02:45PM +0400, Maxim Konovalov wrote:
>
> > + /* Stdio internals do not deal correctly with zero length buffer */
>
> I thought ache fixed a lot of these; are you sure the situation still
> applies to -current?
Yes,
In message <[EMAIL PROTECTED]>, Don Lewis writes:
>After looking at ufs_inactive(), I'd like to add a fourth proposal
And I've just remembered a fifth :-) I think the old BSD code had
both an `open' count and a reference count. The open count is a
count of the real users of the vnode (it is what
OK; it's probably rather like a sledgehammer, but I got the kernel
to compile and run with the following patch:
Index: sys/net/if_ethersubr.c
===
RCS file: /cvs/freebsd/src/sys/net/if_ethersubr.c,v
retrieving revision 1.120
diff -u -
On Thu, Sep 12, 2002 at 12:02:45PM +0400, Maxim Konovalov wrote:
> + /* Stdio internals do not deal correctly with zero length buffer */
I thought ache fixed a lot of these; are you sure the situation still
applies to -current?
Kris
msg42930/pgp0.pgp
Description: PGP signature
Hi
I'm getting lcms port build failure in cms testing phase. The system
I'm building the port on (actually building kdegames3) is P4 with
Intel i845 chipset. World and kernel are built with system gcc-3.2
with CPUTYPE=p4. The main goal is to build a set of packages for an
old P2 system thus CPUTY
On 11 Sep, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Don Lewis writes:
>>
>>A potentially better solution just occurred to me. It looks like it
>>would be better if vrele() waited to decrement v_usecount until *after*
>>the call to VOP_INACTIVE() (and after the call to VI_LOCK()). If th
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Thu, 12 Sep 2002, Maxim Sobolev wrote:
> Any ideas?
See the thread about "Page faults from bento cluster (Re: Problems reading
vmcores)]" which seemed to diagnose this. The last mail that I got about
this pointed to:
http://www.chesapeake.net/~jroberson/VFSsmp.patch
As a workaround, tr
Hi
For a few days the XFree86-4-Server compilation fails with following
error. I'm running -current as of yesterday with kan's patch. The
world and kernel is built with CPUTYPE=p4 and I'm trying to build
complete set of packages for an old P2, thus CPUTYPE=p2 for entire
package build.
rm -f miPc
Hi!
I get some strange messages during device probing on my Current
machine. I was pointed out that these might be due to device hints in
/boot or compiled / configured into my kernel. Unfortunately I could
not find any device hints that look at all like the messages I get
during bootup
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Hello!
In my lab I use a digi Xem multiport serial card. Since approx. one
week I get the following error message during bootup:
digi0 mem 0xb080-0xb0bf irq 10 at device 4.0 on pci0
digi_Xem: Failed to autoload module: No filesystem
If I load the digi driver aft
Hello!
I'm using the D-Link DGE 500SX Gigabit Ethernet card in two of my
computers. One is running FreeBSD Current, the other runs Stable. The
lge driver (and miibus with xmphy) worked well on both systems.
Somewhen between Juli this August this Year, the Current driver stopped
working
On Wed, 11 Sep 2002, Dan Nelson wrote:
> In the last episode (Sep 11), David O'Brien said:
> > I'd like to make this commit to get better performance on today's
> > streaming tape drives. It seems my DLT drive doesn't stream well
> > with the default block size of '10'.
>
> Only if we also raise
> On Wed, 11 Sep 2002 11:30:55 -0700 (PDT), Nate Lawson <[EMAIL PROTECTED]> said:
Nate> tell without more info. Enable options DDB, boot -vs, wait for the
Nate> hang. Hit CTRL-ALT-ESC to go into DDB and type tr to get a
Nate> backtrace. Copy the trace info (serial console is be
On 12 Sep, Martin Blapp wrote:
> Just a thought ... What type of disks are you using? I'm running SCSI
>> here.
>
> ATA ... But I should see disk errors then ...
>
> I've bought now new disks and will try to build on them.
It's not that I think your hardware is defective. I'm wondering if
dif
Hi,
>
> options DISABLE_PSE
> options DISABLE_PG_G
I use that too. With them enabled I see memory corruption.
> Just a thought ... What type of disks are you using? I'm running SCSI
> here.
ATA ... But I should see disk errors then ...
I've bought now new disks and will try
On 12 Sep, Martin Blapp wrote:
>
> Hi,
>
>> If I were you I'd start swapping memory modules, because I'm not having
>
> Already did that. I even used ECC ram.
>
>> any trouble with -CURRENT and I havn't seen anyone else having trouble.
>
> Did you try to build a huge project ? If I don't comp
Maxim Sobolev wrote:
> Any ideas?
Looks like some other processes was modifying the mountlist while
vfs_unmountall() was running. Is this an SMP box ? It would be nice if
you could check in gdb which other process was holding the mountlist_mtx
mutex if any. The vfs_unmountall() function doesn'
Hello -current,
Our vsnprintf(3) has a memory leak, take a look at
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/36175 and
http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/26044
for details.
Any objections against a patch below (from OpenBSD)?
Index: libc/stdio/vsnprintf.c
=
Hi,
> > Oh ok, wierd... I've only tried (unsuccessfully, the compiler errors out)
> > kde3, and some make worlds and stuff. I guess that's not strenuous enough.
>
> kde3 compiled okay for me with Alexander Kabaev's gcc patch posted to
> this ML.
I could compile KDE, XFree86 and make buildworld
Any ideas?
max@notebook$ gdb -k /sys/i386/compile/NOTEBOOK/kernel.debug
/var/crash/vmcore.0
GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of
49 matches
Mail list logo
