unsubscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Raymond Kohler wrote:
>
> - Original Message -
> From: "Donald J. Maddox" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, July 30, 2001 12:10 AM
> Subject: Re: just moved to current, mouse is jerky
>
> > Try not using /dev/{u}random (don't load random.ko at boot). The rand
On Tue, 31 Jul 2001, John Baldwin wrote:
>
> On 31-Jul-01 Vincent Poy wrote:
> > On Mon, 30 Jul 2001, John Baldwin wrote:
> >
> >> On 30-Jul-01 Sheldon Hearn wrote:
> >> >
> >> >
> >> > On Mon, 30 Jul 2001 07:38:47 MST, "David O'Brien" wrote:
> >> >
> >> >> However, those boxes were panicing ofte
On 31-Jul-01 Vincent Poy wrote:
> On Tue, 31 Jul 2001, John Baldwin wrote:
>> > root@pele [9:29pm][/usr/temp] >>
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: 1st
On Tue, 31 Jul 2001, John Baldwin wrote:
>
> On 31-Jul-01 Vincent Poy wrote:
> > On Tue, 31 Jul 2001, John Baldwin wrote:
> >> > root@pele [9:29pm][/usr/temp] >>
> >> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
> >> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order revers
On 31-Jul-01 Vincent Poy wrote:
> On Tue, 31 Jul 2001, John Baldwin wrote:
>
>>
>> On 31-Jul-01 Vincent Poy wrote:
>> > On Tue, 31 Jul 2001, John Baldwin wrote:
>> >> > root@pele [9:29pm][/usr/temp] >>
>> >> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
>> >> > Jul 28 21:29:40
On Tue, Jul 31, 2001 at 01:39:14PM -0400, Robert Watson wrote:
> what was going on, and given that scp doesn't support -1, was a bit of a
> pain.
Brian, what about adding "-1" to SCP?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 31 Jul 2001, John Baldwin wrote:
> >> On 31-Jul-01 Vincent Poy wrote:
> >> > On Tue, 31 Jul 2001, John Baldwin wrote:
> >> >> > root@pele [9:29pm][/usr/temp] >>
> >> >> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
> >> >> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock
Has anyone attempted to make a loadable module out of IPSEC yet?
brad
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
Last weekend I replaced my socket7 MVP3 board (w/ K6-2+)
to ASUS CUSI-FX socket370 SiS630E board (w/ VIA C3 733MHz),
then I found kernel panics when USB HUBs are detached.
My USB setup is as follows:
FreeBSD PC--+
|
CPU_switcherHUB1HUB
> > From [EMAIL PROTECTED] Tue Jul 31 12:15:25 2001
> >
> > set debug.acpi.timer_test="yes"
> >
> > at the loader prompt and boot? Ideally, you'll get a message "timer is
> > not monotonic", followed by some numbers. If this is the case, then I
> > need to get "smarter" with the ACPI timer
> > - What power management hardware your system has: look at the output of
> >pciconf -lv for a "power management controller", eg:
> >
> This machine has no separate controller. Attached is the complete output
> of "pciconf -lv"
That's OK; I can probably safely assume it's the M1533 device
On Mon, 30 Jul 2001, John Baldwin wrote:
> On 30-Jul-01 Sheldon Hearn wrote:
> >
> >
> > On Mon, 30 Jul 2001 07:38:47 MST, "David O'Brien" wrote:
> >
> >> However, those boxes were panicing often before I made that statement.
> >> So I still believe current is now in better shape than it was in J
Sheldon Hearn wrote:
> > The FreeBSD 4.3 manpage says:
> > Only users who are a member of group 0 (normally ``wheel'') can su to
> > ``root''. If group 0 is missing or empty, any user can su to
> > ``root''.
>
> I guess that could (at a stretch) be interpreted the same as OpenBSD
Kris Kennaway <[EMAIL PROTECTED]> writes:
> On Mon, Jul 30, 2001 at 07:44:33AM -0700, David O'Brien wrote:
> > On Sun, Jul 29, 2001, Kris Kennaway wrote:
> > >
> > > installed. This would involve a repo copy of crypto/openssl/crypto/bn
> > > to contrib/openssl-bn or something, and I'd keep the tw
On Mon, 30 Jul 2001 16:52:27 +0200, Sheldon Hearn wrote:
> I'll be a lot happier when I can enabled DDB_UNATTENDED and do whatever
> it is that causes my panic of the day and actually get a crashdump
> instead of
>
> panic: witness_restore: lock (sleep mutex) Giant not locked
Right! We
[Aside: problems getting crashdumps resolved, see message with ]
[Message-ID <[EMAIL PROTECTED]> sent to -current]
[with subject "Re: -current lockups". ]
On Mon, 30 Jul 2001 00:00:53 +0200, Sheldon Hearn wrote:
> I got a little help from some folks on I
Upgraded my laptop to current the other day, just to get the cardbus
cards working (which works like a charm). Found a problem though related
to XFree86. When I run startx X initiates for a short while, but dies
with the message:
(EE) xf86OpenSerial: Cannot open device /dev/psm0
Device bu
On Tue, 31 Jul 2001 05:35:00 +0100, Joshua Goodall wrote:
> The FreeBSD 4.3 manpage says:
> Only users who are a member of group 0 (normally ``wheel'') can su to
> ``root''. If group 0 is missing or empty, any user can su to
> ``root''.
I guess that could (at a stretch) be int
++ 31/07/01 14:06 +0200 - Gunnar Flygt:
| (EE) xf86OpenSerial: Cannot open device /dev/psm0
| Device busy.
| And then it's over :)
Sounds like you're running moused. I don't think XFree86 4.1 can use
/dev/sysmouse and interact with moused like 3.3.6 could.
-pete
--
Pete Fritchman <[EMAI
>Date: Tue, 31 Jul 2001 08:45:41 -0400
>From: Pete Fritchman <[EMAIL PROTECTED]>
>++ 31/07/01 14:06 +0200 - Gunnar Flygt:
>| (EE) xf86OpenSerial: Cannot open device /dev/psm0
>| Device busy.
>| And then it's over :)
>Sounds like you're running moused. I don't think XFree86 4.1 can use
>/d
Hi,
>>> Mike Smith wrote:
> I've just committed a slightly different patch, based on a mix of your
> ideas and mine (mostly yours). Can you test the -current code, and let
> me know what I broke this time? 8)
As haro wrote, acpi_pcib.c rev1.11 + neckpain's patch does work
on my machine too.
Hello Nakayama-san,
From: [EMAIL PROTECTED]
Date: Tue, 31 Jul 2001 23:28:39 +0900
::Hi,
::
::>>> Mike Smith wrote:
::> I've just committed a slightly different patch, based on a mix of your
::> ideas and mine (mostly yours). Can you test the -current code, and let
::> me know what I broke this
On 31-Jul-01 Sheldon Hearn wrote:
>
> [Aside: problems getting crashdumps resolved, see message with ]
> [Message-ID <[EMAIL PROTECTED]> sent to -current]
> [with subject "Re: -current lockups". ]
>
> On Mon, 30 Jul 2001 00:00:53 +0200, Sheldon Hearn wro
On 31-Jul-01 Vincent Poy wrote:
> On Mon, 30 Jul 2001, John Baldwin wrote:
>
>> On 30-Jul-01 Sheldon Hearn wrote:
>> >
>> >
>> > On Mon, 30 Jul 2001 07:38:47 MST, "David O'Brien" wrote:
>> >
>> >> However, those boxes were panicing often before I made that statement.
>> >> So I still believe cur
On 31-Jul-01 Terry Lambert wrote:
> Sheldon Hearn wrote:
>> > The FreeBSD 4.3 manpage says:
>> > Only users who are a member of group 0 (normally ``wheel'') can su to
>> > ``root''. If group 0 is missing or empty, any user can su to
>> > ``root''.
>>
>> I guess that could (at a
libpam will not build if you don't have the stock ssh installed.
I use ssh from ports.
(libpam)502}make
===> modules
===> modules/pam_deny
===> modules/pam_ftp
===> modules/pam_nologin
===> modules/pam_opie
===> modules/pam_permit
===> modules/pam_radius
===> modules/pam_rootok
===> modules/pam_s
On Tue, 31 Jul 2001, Terry Lambert wrote:
> The reason for this is that the pam code for doing the enforcement
> is being trusted utterly. In the past, we would consider both
> the primary group (the group from the passwd file entry), and the
> auxillary groups (the groups from the groups file
My only real observation is that with Protocol using (2) by default, my
logins to RELENG_4 boxes using RSA key authentication are broken. If I
stick a Protocol 1 in, it works fine, but it took me a bit to figure out
what was going on, and given that scp doesn't support -1, was a bit of a
pain. I
* Robert Watson <[EMAIL PROTECTED]> [010731 12:39] wrote:
> My only real observation is that with Protocol using (2) by default, my
> logins to RELENG_4 boxes using RSA key authentication are broken. If I
> stick a Protocol 1 in, it works fine, but it took me a bit to figure out
> what was going
I have the PR, and I will fix this :-)
M
>
> On Tue, 31 Jul 2001, Terry Lambert wrote:
>
> > The reason for this is that the pam code for doing the enforcement
> > is being trusted utterly. In the past, we would consider both
> > the primary group (the group from the passwd file entry), and t
> From [EMAIL PROTECTED] Tue Jul 31 12:15:25 2001
>
> set debug.acpi.timer_test="yes"
>
> at the loader prompt and boot? Ideally, you'll get a message "timer is
> not monotonic", followed by some numbers. If this is the case, then I
> need to get "smarter" with the ACPI timer probe.
acpi0:
Hi.
Yoichi Nakayama <[EMAIL PROTECTED]> wrote:
> ::As haro wrote, acpi_pcib.c rev1.11 + neckpain's patch does work
> ::on my machine too. But rev1.12 cause panic while booting on my
> ::PCG-C1VSX/K (NEWCARD + acpica).
Munehiro Matsuda <[EMAIL PROTECTED]> wrote:
> New patch was posted by [EMAIL
At 12:40 PM -0500 7/31/01, Alfred Perlstein wrote:
>* Robert Watson <[EMAIL PROTECTED]> [010731 12:39] wrote:
> > My only real observation is that with Protocol using (2) by default,
> > my logins to RELENG_4 boxes using RSA key authentication are broken.
>
>The protocol 2,1 thing should not be
34 matches
Mail list logo
