Hi,
Sorry to bother/spam this mailing list again. In brief, rescent kernel
may panic because of several IPFIREWALL options. The panic message I could
tell is about trap 12, swi6: clock and page fault. And the machine hangs
solidly right away, I have no idea how to provide a back trace :(
"Alexander N. Kabaev" wrote:
Why FreeBSD does not link libgcc into shared libraries by default? Everyone
else is doing that. Linking shared libraries with libgcc seems to be the
ultimate work-around. Are there any compatibility problems which are keeping
FreeBSD from doing that?
OK,
John Polstra wrote:
In article [EMAIL PROTECTED],
Maxim Sobolev [EMAIL PROTECTED] wrote:
After the crt changes the following piece of code, which worked previously,
gives a 'host: dlopen() failed: ./module.so: Undefined symbol
"__register_frame_info' error message (yeah, I know that
On Tue, Nov 07, 2000 at 04:13:37PM +0800, Clive Lin scribbled:
| may panic because of several IPFIREWALL options. The panic message I could
| tell is about trap 12, swi6: clock and page fault. And the machine hangs
| solidly right away, I have no idea how to provide a back trace :(
What is your
On Mon, Nov 06, 2000 at 06:18:38PM -0500, Chris Faulhaber wrote:
You forgot the patch(es) to the port(s) this would affect (e.g. xinetd).
The affected ports would need their ${PREFIX}/etc/rc.d files removed
(otherwise you would start them twice) along with a message letting the
installer
Hi,
i've updated one of my systems (a fujitsu-siemens series C) laptop
to the current from yesterday, and my dfe-650 10/100 ethernet pcmcia
card started to behave strangely:
it is detected by the kernel and pccardd correctly as an ed0 device,
ifconfig configures it correctly, but as soon as the
Chris Faulhaber wrote:
On Tue, Nov 07, 2000 at 01:02:03AM +0200, Giorgos Keramidas wrote:
On Mon, Nov 06, 2000 at 03:37:01PM -0500, Forrest Aldrich wrote:
It would be useful to have back the program specification variable for
inetd. Currently we have:
inetd_enable="YES"
On Tue, Nov 07, 2000 at 09:30:48AM +, Konstantin Chuguev wrote:
If xinetd has a startup script, why don't you just set inetd_enable="NO" and let
the /usr/local/etc/rc.d/xinetd.sh start normally? You need to edit no /etc/rc.*
files (except for rc.conf.local, obviously).
The original idea
Hi,
On recent -current (as of yesterday), linux acroread4 no longer works
properly. The main window comes up, but then either it crashes
immediately, displays copy of the background or a messed-up fragments of
document contents (menus still work), and after a couple of seconds
crashes anyway
it is detected by the kernel and pccardd correctly as an ed0 device,
ifconfig configures it correctly, but as soon as the interface
is up, the kernel starts spewing ed0: device timeout...
This usually means IRQ stuffups.
at first i suspected cable/hardware problem, and rebooted in windows98SE
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, Nov 07, 2000 at 12:19:40PM +0100, Rogier R. Mulhuijzen wrote:
it is detected by the kernel and pccardd correctly as an ed0 device,
ifconfig configures it correctly, but as soon as the interface
is up, the kernel starts spewing ed0: device timeout...
This usually means IRQ
I've been getting a hard panic/page fault whenever attempting to print
for a few weeks now.
it always shows that it is hung in the irq7 process.
does this have to do with the /dev/random wierdness? if so, any idea
on when it will be fixed?
jim
--
All opinions expressed are mine, if you|
tcpdump on the laptop sees the packet? That's very odd.
Ceratinly is. I don't think this particular problem has anything
to do with the cardbus adapter. I run tcpdump with "-v -v -v" and
it never reported a bad checksum either.
For curiosity's sake, I'd try a different cable to the
At 09:30 AM 11/7/2000 +, Konstantin Chuguev wrote:
If xinetd has a startup script, why don't you just set inetd_enable="NO"
and let
the /usr/local/etc/rc.d/xinetd.sh start normally? You need to edit no
/etc/rc.*
files (except for rc.conf.local, obviously).
[ .. ]
Sure that would work, but
Hello,
I upgraded my box to the latest -current yesterday and also rebuilt
XFree86 4. Last one was from August.
Aside from some configuration hassles that were easy to overcome
thanks to the UPDATING file and comparison of my config with
NOTES and GENERIC, I had big problems today with my
Hi,
At Tue, 7 Nov 100 07:39:25 -0600 (CST),
Jim Bryant [EMAIL PROTECTED] wrote:
I've been getting a hard panic/page fault whenever attempting to print
for a few weeks now.
I have the same problem on the i386/SMP from Oct 10 to date.
Sep 23 world works fine.
dmesg:
ppc0: Parallel port at
Hello Harti,
is there somebody working to make if_tap devfs-ready? Or I'm doing
something wrong?
[SNIP]
it seems to me that it did not get commited. i will look into it again
today and re-send patch to the list.
Great! It works. (Minus a spelling error: the parameter in
Nope, explicitly linking shared module with -lgcc doesn't solve this problem.
-Maxim
Then it is not new crt* code that is broken
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In article [EMAIL PROTECTED],
Maxim Sobolev [EMAIL PROTECTED] wrote:
The full sources of this testcase can be found at:
http://people.freebsd.org/~sobomax/dlbug.tar.gz .
Thanks for the nice test case. It made my job a lot easier. :-)
The bug is in the dynamic linker. I'll append the patch
In article [EMAIL PROTECTED],
Alexander N. Kabaev [EMAIL PROTECTED] wrote:
Nope, explicitly linking shared module with -lgcc doesn't solve
this problem.
Then it is not new crt* code that is broken
That's correct. The new crt code just uncovered the bug in the
dynamic linker.
John
--
John,
I think dymanic loader should clear it's error_string variable before returning
success to the caller. I am halfway done preparing the patch to do that. Is
that the bug you mentioned or there is something else? Anyway, do you want to
see my patch when it is ready or you prefer to take care
In article [EMAIL PROTECTED], Alexander N. Kabaev
[EMAIL PROTECTED] wrote:
I think dymanic loader should clear it's error_string variable
before returning success to the caller.
I don't think it is allowed to do that. See the SUSv2 description:
I tried the latest build from current.freebsd.org. (11-7)
I tried multiple floppies to make sure that it was not a problem with bad
sectors (fdimage should catch this anyway). On boot from the kern.flp
image the computer stops at the boot loader with the message
elf_loadexec: cannot seek
can't
I don't think it is allowed to do that. See the SUSv2 description:
http://www.opengroup.org/onlinepubs/007908799/xsh/dlerror.html
Sorry, you are right of course. The attached patch removes the _rtld_error
call at the end of the symlook_default function which seems to be unnecessary.
In message [EMAIL PROTECTED] "Rogier R. Mulhuijzen"
writes:
: Reboot again, and see which IRQ the driver there uses. Then go into
: /etc/pccard.conf and replace the ? on the config line with that IRQ.
Strike that. Don't replace the ? on the config line.
Since we have
I just tried to umount -f /home, where /home was an NFS mounted file
system on a network that was no longer attached to my laptop. In the
past this has just worked, even if processes were hung in disk wait
state. When I tried it last night on an Oct 29th kernel, I got EBUSY
and the file system
On Tue, Nov 07, 2000 at 01:13:41PM -0700, Warner Losh wrote:
I just tried to umount -f /home, where /home was an NFS mounted file
system on a network that was no longer attached to my laptop. In the
past this has just worked, even if processes were hung in disk wait
state. When I tried it
In message [EMAIL PROTECTED] Bill Fumerola writes:
: On Tue, Nov 07, 2000 at 01:13:41PM -0700, Warner Losh wrote:
:
: I just tried to umount -f /home, where /home was an NFS mounted file
: system on a network that was no longer attached to my laptop. In the
: past this has just worked, even
* Warner Losh [EMAIL PROTECTED] [001107 13:14] wrote:
In message [EMAIL PROTECTED] Bill Fumerola writes:
: On Tue, Nov 07, 2000 at 01:13:41PM -0700, Warner Losh wrote:
:
: I just tried to umount -f /home, where /home was an NFS mounted file
: system on a network that was no longer
In message [EMAIL PROTECTED] Alfred Perlstein writes:
: Yes, this used to work quite well for some time, I have no idea
: who broke it. Maybe you can sprinkle some printfs in the code and
: narrow it down a bit?
I'll give it a shot. I'm glad to see it is a "should work but is
busted" rather
Hi,
please have a look at the following dmesg output.
I'm sure I must have overseen something trivial, but currently I can't
figure out what it is.
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the
In article [EMAIL PROTECTED],
Maxim Sobolev [EMAIL PROTECTED] wrote:
After the crt changes the following piece of code, which worked previously,
gives a 'host: dlopen() failed: ./module.so: Undefined symbol
"__register_frame_info' error message (yeah, I know that it's better to check
handle
I'm sure I must have overseen something trivial, but currently I can't
figure out what it is.
The lower 16 MB memory has been used for
kernel text, data, bss
arrays allocated by vm_page_startup()
memory allocated via malloc() with M_ZERO
- Tor Egge
To Unsubscribe:
34 matches
Mail list logo
