On Thu, Nov 20, 2003 at 09:29:30PM -0500, Richard Coleman wrote:
But I've often wondered how frequently a production system has such
problems. I've been a sysadmin for many years and can't remember this
ever happening. It's much more common to blow a hard drive, or have
flaky memory, etc.
On Thu, Nov 20, 2003 at 09:51:48PM +0100, boyd, rounin wrote:
From: Peter Jeremy [EMAIL PROTECTED]
Shouldn't that be 'chmod +t /bin/sh' ???
Definitely. Why waste a new bit when there's already a perfectly good
one that is (or was) defined for the purpose.
the 't' bit was known as the
On recent -CURRENT + http://www.freebsd.org/~jhb/patches/acpi_irq.patch
panic: NULL softc for 0
cpuid = 0;
Debugger(panic)
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db tr
Debugger(c08983fd,0,c086865c,e041ccbc,100) at Debugger+0x55
panic(c086865c,0,80246,0,e041cce8) at panic+0x156
I can only say that I had a core dump under current on sparc, but the core
file was unusable. Can you compile rcp.lockd with -g in CFLAGS and LDFLAGS
and try to find out with gdb where it aborts?
harti
Hi :)
I investigate a little more this nfs locking issue.
I recompile my system with
From: Peter Jeremy [EMAIL PROTECTED]
As for overloading the 't' bit, I don't believe it's ever been used
for anything else on executable files.
directories
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
Submitter-Id: current-users
Originator:Vladimir Grebenschikov
Organization: SWsoft
Confidential: no
Synopsis: Problem with GDB on latest -CURRENT
Severity: non-critical
Priority: medium
Category: bin
Class: sw-bug
Release: FreeBSD 5.1-CURRENT i386
Thanks to everyone who suggested things... now the port's been updated it
compiles fine. Doesn't run, however, but I'll try to suss that out myself...
thanks,
Ben
___
[EMAIL PROTECTED] mailing list
Tim Kientzle wrote on Thursday, November 20, 2003 6:31 PM
Garance A Drosihn wrote:
At 6:26 PM +0100 11/17/03, Julian Stacey wrote:
Seconded ! Better commit an improved switch with
default = Off.
The time for voting was months ago.
...
I'm pretty comfortable with the failsafes
I got bit by this just two days ago. I have one machine that tracks
-current. It upgraded to DYNAMICROOT just fine. I nfs mounted /usr/src
and /usr/obj on another 5.0-release machine made the necessary adjustments,
installed the kernel, rebooted, remounted and began make installworld. It
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
This might be the underlying wierdness we were seeing in gtetlow's
microdrive with transfers over 8k. The one-page-crossing ohci limitation
is really annoying.
On Thu, 20 Nov 2003, Brian F. Feldman wrote:
Doug White [EMAIL PROTECTED] wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
I'll look around for a bootable NetBSD CD.
This might be the underlying wierdness we were seeing in gtetlow's
microdrive with transfers over 8k. The
Guy Helmer wrote:
Thanks to /rescue and the live filesystem archives on
current.freebsd.org, I was able to recover a machine
that I hosed after the statfs change by trying to installworld
without building booting a new kernel first.
Great! Any changes you could suggest
to /rescue based on that
Hi,
I need a new MAJOR number for our new device.
How can I get it?
I've read that FreeBSD doesn't use them any more.
But we may need it to not interfere with other device
drivers in previous releases of FreeBSD.
??? ce Cronyx Tau-32 E1 adapter
___
Best regars,
Roman
On Wed, 19 Nov 2003, Eric Anderson wrote:
Nate Lawson wrote:
You should run a benchmark with different values for
hw.acpi.cpu.current_speed to be sure the throttling control still works
ok. I left it mostly intact so you shouldn't see any problems but it's
still good to test. As you change
On Wed, Nov 19, 2003 at 05:32:37PM -0800, Sean Chittenden wrote:
I don't know if Lucent cards are supported or not. How old is your
kernel, btw? You should update to -CURRENT as there have been many
wlan fixes since 5.1-RELEASE. -sc
To the best of my knowledge, only PRISM2 has ever been
On Thu, Nov 20, 2003 at 04:31:10PM -0800, Tim Kientzle wrote:
* /rescue/vi is currently unusable if /usr is missing because
the termcap database is in /usr. One possibility
would be to build a couple of default termcap entries
into ncurses or into vi.
My suggested candidates are
On Thu, Nov 20, 2003 at 02:31:23PM -0500, John Baldwin wrote:
On 20-Nov-2003 Kris Kennaway wrote:
I updated bento last night, and it panicked after a few hours with:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 01
fault virtual address = 0xe5
fault code
* Bruce M Simpson [Fr, 21 Nov 2003 at 20:36 GMT]:
On Wed, Nov 19, 2003 at 05:32:37PM -0800, Sean Chittenden wrote:
I don't know if Lucent cards are supported or not. How old is your
kernel, btw? You should update to -CURRENT as there have been many
wlan fixes since 5.1-RELEASE. -sc
To the
Whoops. http://damien.bergamini.free.fr/ueagle/download.html.
BMS
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Fri, Nov 21, 2003 at 09:11:33AM -0800, Doug White wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
This might be the underlying wierdness we were seeing in gtetlow's
microdrive with transfers over 8k. The one-page-crossing ohci limitation
Is anyone using this successfully? I had to install it from Linux. The
grub.conf below works when installed by the Linux grub-install but
FreeBSD's port always fails with the below messages. Package: grub-0.92
The other problem is I think grub cannot boot UFS2 partitions so I'm using
UFS1.
Hi
I'm getting some strange xl0 timeout messages on 5.1-CURRENT (synced
today).
I've searched the archives, and it seems that this problem is related to
ACPI
(http://docs.freebsd.org/cgi/getmsg.cgi?fetch=608457+0+archive/2003/freebsd-current/20031109.freebsd-current)
Strange thing is that this
On Thu, Nov 20, 2003 at 09:29:30PM -0500, Richard Coleman wrote:
But I've often wondered how frequently a production system has such
problems. I've been a sysadmin for many years and can't remember this
ever happening. It's much more common to blow a hard drive, or have
flaky memory, etc.
In message: [EMAIL PROTECTED]
Roman Kurakin [EMAIL PROTECTED] writes:
: ??? ce Cronyx Tau-32 E1 adapter
I've checked -stable and -current. You may have:
185 ce Cronyx Tau-32 E1 adapeter [EMAIL PROTECTED]
for your adapter. Sorry for the hassles in getting it.
On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
Hi
I'm getting some strange xl0 timeout messages on 5.1-CURRENT (synced
today).
I've searched the archives, and it seems that this problem is related to
ACPI
On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote:
Doug White [EMAIL PROTECTED] wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
I'll look around for a bootable NetBSD CD.
NetBSD is different in that point.
This might be
Hi all,
Last night's -CURRENT appears to have demonstrated deadlock. My experience
in this area is extremely limited so I have been trying to track down the
problem with kan's help.
It manifested itself as being unable to log into the machine directly (via
serial console, *or* sshd) due to
Bernd Walter [EMAIL PROTECTED] wrote:
On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote:
Doug White [EMAIL PROTECTED] wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
I'll look around for a bootable NetBSD CD.
NetBSD
--On Thursday, November 20, 2003 9:40 PM -0500 Richard Coleman
[EMAIL PROTECTED] wrote:
ust put a tiny termcap file in /rescue (i.e. termcap.rescue) that
contains 5 or 6 of the most common terminal types (cons25, vt102,
etc), and have /rescue/vi default to cons25.
If you are hosed enough to
Since both of these happen in irq handlers, you might want to look at the
new random entropy gathering use of locking.
-Nate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
So i have a machine freshly installed from 5.1 mini iso.
I did a cvs co of latest current sources, and accidentally
did a 'make world' instead of 'make buildworld'.
Now i just get 'Bad system call' when i try to do anything.
i need to get the correct kernel on there, does anyone have a
Is this an SMP box? If so, please do:
x/xl cpu_softc
x/xl cpu_softc+4
x/xl cpu_softc+8
And send me the output of
acpidump -t -d tiamat-MachineType.asl
-Nate
___
[EMAIL PROTECTED] mailing list
Tim Kientzle wrote:
Guy Helmer wrote:
Thanks to /rescue and the live filesystem archives on
current.freebsd.org, I was able to recover a machine
that I hosed after the statfs change by trying to installworld
without building booting a new kernel first.
Great! Any changes you could
Sorry to reply to myself. Are you loading acpi as a module and have an
SMP box? If so, please try this patch, recompile the module, and go
again:
retrieving revision 1.32
diff -u -r1.32 Makefile
--- Makefile15 Nov 2003 19:26:06 - 1.32
+++ Makefile21 Nov 2003 21:37:41 -
@@
On Fri, 21 Nov 2003, Don Bowman wrote:
So i have a machine freshly installed from 5.1 mini iso.
I did a cvs co of latest current sources, and accidentally
did a 'make world' instead of 'make buildworld'.
Now i just get 'Bad system call' when i try to do anything.
i need to get the correct
At 8:52 PM +1100 11/20/03, Peter Jeremy wrote:
On Wed, Nov 19, 2003, Lyndon Nerenberg wrote:
--On Wed, Nov 19, 2003, Garance A Drosihn [EMAIL PROTECTED] wrote:
have a: chflags ldcache /bin/sh
Shouldn't that be 'chmod +t /bin/sh' ???
Definitely. Why waste a new bit when there's already a
On Tue, 18 Nov 2003, Lukas Ertl wrote:
I'm gonna try some buildkernelstones with the different settings. If
you have some special benchmarks in mind I'd be happy to run them.
That's probably ok. It has a lot of IO.
Now I've tried running make buildkernel and tarring /usr/src to a
Thanks to /rescue and the live filesystem archives on
current.freebsd.org, I was able to recover
... I could have used the ftp client (or fetch) in /rescue :-)
Yes, fetch would be useful. I imagine a lot of people
in emergency situations will need to pull things over
a network connection.
Is this an SMP box? If so, please do:
This Intel® Server Board SE7501BR2 with one CPU and enabled Hyper-Threading.
x/xl cpu_softc
x/xl cpu_softc+4
x/xl cpu_softc+8
panic: NULL softc for 0
cpuid = 0;
Debugger(panic)
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db x/xl
Hi Nate,
On Friday 21 November 2003 21:11, Nate Lawson wrote:
Is anyone using this successfully? I had to install it from Linux.
The grub.conf below works when installed by the Linux grub-install
but FreeBSD's port always fails with the below messages. Package:
grub-0.92
Yes, I'm using
On Fri, 2003-11-21 at 21:29, Kris Kennaway wrote:
On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
I saw this with some of sam's locking changes that (temporarily) broke
DUMMYNET. I see you're using ipfilter - it's possible that this
configuration has not been well-tested. Are
On Fri, 21 Nov 2003, Nate Lawson wrote:
On Tue, 18 Nov 2003, Lukas Ertl wrote:
I'm gonna try some buildkernelstones with the different settings. If
you have some special benchmarks in mind I'd be happy to run them.
That's probably ok. It has a lot of IO.
Now I've tried
On Sat, 22 Nov 2003, Alex Deiter wrote:
Is this an SMP box? If so, please do:
This Intel® Server Board SE7501BR2 with one CPU and enabled Hyper-Threading.
x/xl cpu_softc
x/xl cpu_softc+4
x/xl cpu_softc+8
panic: NULL softc for 0
cpuid = 0;
Debugger(panic)
Stopped at
On Thu, Nov 20, 2003 at 10:12:44AM -0800, Wade Klaver wrote:
Hello all,
When trying to bring a box up to date, we noticed that the
IPFIREWALL_FORWARD kernel option has been removed somewhere between the 2'nd
of this month and now. Has it been obsoleted by other options? I saw
nothing
On Sat, 22 Nov 2003, Alex Deiter wrote:
Is this an SMP box? If so, please do:
This Intel® Server Board SE7501BR2 with one CPU and enabled Hyper-Threading.
x/xl cpu_softc
x/xl cpu_softc+4
x/xl cpu_softc+8
panic: NULL softc for 0
cpuid = 0;
Debugger(panic)
Stopped at
On Sat, 22 Nov 2003, Alex Deiter wrote:
Sorry to reply to myself. Are you loading acpi as a module and have an
SMP box? If so, please try this patch, recompile the module, and go
again:
i applay this patch, comment device acpi in GENERIC and rebuild kernel.
After reboot it work, does
Leo Bicknell wrote:
To boot a machine into single user mode you need a kernel, init,
and /bin/sh (minimally). It would seem to me that alone is a good
argument for those three things to be static.
You need a static shell, yes. That does not have to be /bin/sh.
init does prompt, and /rescue/sh is
Leo Bicknell wrote:
The more I think about init the more I don't like dynamic linking for
it. init needs to have as few failure modes as possible. I do still
think it's fine for all the other /bin and /sbin things.
Right now, /sbin/init is statically linked.
Tim Kientzle
Hello,
I just upgraded a -CURRENT box this afternoon to discover that vinum
is broken. If I hadn't done dumps of my working world beforehand I
would be in pretty sad shape. Should UPDATING make note of this breakage?
It would have saved me some embarassment, and I'm sure others are about
to
Jimmy Selgen wrote:
On Fri, 2003-11-21 at 21:29, Kris Kennaway wrote:
On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
I saw this with some of sam's locking changes that (temporarily) broke
DUMMYNET. I see you're using ipfilter - it's possible that this
configuration has not been
On Fri, 21 Nov 2003 15:38:49 -0800, Tim Kientzle [EMAIL PROTECTED] said:
There have been a lot of proposed solutions:
* Rewrite NSS to not require dlopen().
* Rewrite dlopen() to not require dynamic linking.
* Don't support NSS in /bin/sh.
* Change the default script interpreter
Bruce Evans wrote:
It obviously uses NSS. How else could it be so bloated? :
$ ls -l /sbin/init
-r-x-- 1 root wheel 453348 Nov 18 10:30 /sbin/init
I believe it's actually DNS, not NSS.
Pre-5.0, the resolver ballooned significantly.
A lot of the bloat in /bin and /sbin came
from the NIS
On Fri, Nov 21, 2003 at 01:08:13PM -0800, Nate Lawson wrote:
Since both of these happen in irq handlers, you might want to look at the
new random entropy gathering use of locking.
I'm running a kernel with dev/random backed out to the day before
mark's commits, because at the time I needed to
Garrett Wollman wrote:
On Fri, 21 Nov 2003 15:38:49 -0800, Tim Kientzle [EMAIL PROTECTED] said:
There have been a lot of proposed solutions:
* Rewrite NSS to not require dlopen().
* Rewrite dlopen() to not require dynamic linking.
* Don't support NSS in /bin/sh.
* Change the default script
On Sat, 22 Nov 2003, Lukas Ertl wrote:
On Fri, 21 Nov 2003, Nate Lawson wrote:
Those are what is more interesting. Also, can you send me your sysctl
hw.acpi.cpu.cx_history after you've used it for a while with the maximum
cx_lowest setting?
hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85
On Fri, Nov 21, 2003 at 11:40:37PM +0100, Jimmy Selgen wrote:
The box in question is my workstation, so I guess i'm not passing that
much traffic through ipfilter. Also, when I said that the NIC still
worked, I might have mislead you a bit. I had about 5-10 timeouts while
scp'ing the dmesg
On Friday, 21 November 2003 at 15:42:12 -0800, Marcus Reid wrote:
Hello,
I just upgraded a -CURRENT box this afternoon to discover that vinum
is broken. If I hadn't done dumps of my working world beforehand I
would be in pretty sad shape. Should UPDATING make note of this
breakage?
No.
Hi Greg,
On Sat, Nov 22, 2003 at 11:05:38AM +1030, Greg 'groggy' Lehey wrote:
On Friday, 21 November 2003 at 15:42:12 -0800, Marcus Reid wrote:
Hello,
I just upgraded a -CURRENT box this afternoon to discover that vinum
is broken. If I hadn't done dumps of my working world beforehand I
Hi,
It has been almost a month that my system fails to upgrade the
kdelibs-3.1.4 port on my FreeBSD-current box. I have synchronized my OS
with -current many times, but the problem seems to persist. Here is the
error message:
../dcop/dcopidl/dcopidl ./ksycoca.h ksycoca.kidl || ( rm -f
On Fri, 21 Nov 2003, Nate Lawson wrote:
On Sat, 22 Nov 2003, Lukas Ertl wrote:
On Fri, 21 Nov 2003, Nate Lawson wrote:
Those are what is more interesting. Also, can you send me your sysctl
hw.acpi.cpu.cx_history after you've used it for a while with the maximum
cx_lowest setting?
On Fri, 21 Nov 2003, Don Bowman wrote:
So i have a machine freshly installed from 5.1 mini iso.
I did a cvs co of latest current sources, and accidentally
did a 'make world' instead of 'make buildworld'.
Now i just get 'Bad system call' when i try to do anything.
i need to get the correct
On Fri, 21 Nov 2003, Tim Kientzle wrote:
Bruce Evans wrote:
It obviously uses NSS. How else could it be so bloated? :
$ ls -l /sbin/init
-r-x-- 1 root wheel 453348 Nov 18 10:30 /sbin/init
I believe it's actually DNS, not NSS.
Pre-5.0, the resolver ballooned significantly.
A
On Fri, Nov 21, 2003 at 05:35:59PM -0800, Doug White wrote:
On Fri, 21 Nov 2003, Don Bowman wrote:
So i have a machine freshly installed from 5.1 mini iso.
I did a cvs co of latest current sources, and accidentally
did a 'make world' instead of 'make buildworld'.
Now i just get 'Bad
From: William Josephson [EMAIL PROTECTED]
People at Berkeley (and elsewhere) have done user studies to try to
quantify this sort of thing. It is pretty clear that with modern
hardware, most failures are due to human error. That's not to say
that hardware and software faults aren't real
On Fri, Nov 21, 2003 at 04:52:00PM -0500, Garance A Drosihn wrote:
Shouldn't that be 'chmod +t /bin/sh' ???
b) I thought that you might want to have this an admin-only
command, so nefarious users couldn't abuse it on a shared
system.
I would make one change to your proposal: Instead of
On Fri, 21 Nov 2003, Guillaume EGLES wrote:
Hi,
It has been almost a month that my system fails to upgrade the
kdelibs-3.1.4 port on my FreeBSD-current box. I have synchronized my OS
with -current many times, but the problem seems to persist. Here is the
error message:
On Wed, Nov 19, 2003 at 09:26:10PM -0800, Len Sassaman wrote:
It is my intuition from this behavior that the sshd master process
listening for connections is unable to spawn a new process to complete
the authentication step, and thus the connection is being dropped.
There is no information of
67 matches
Mail list logo
