headers
Kevin Oberman | 1 Mar 2005 01:21

Re: Xorg 6.8.1 and SCHED_ULE vs. SCHED_4BSD

> Date: Sun, 27 Feb 2005 21:36:23 +0100
> From: Godwin Stewart <gstewart <at> bonivet.net>
> Sender: owner-freebsd-stable <at> freebsd.org
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sat, 26 Feb 2005 21:49:00 +0100, Michael Nottebrock
> <michaelnottebrock <at> gmx.net> wrote:
> 
> > I've been using that for a long time now, since Xorg 6.8.1 breaks vt-
> > switching for me.
> 
> Well, I decided to bite the bullet and upgraded to Xorg 6.8.1 anyway. It
> didn't break vt-switching for me, thankfully. Other than the core keyboard
> driver being "kbd" instead of "Keyboard" now, which threw me off for a
> couple of minutes, all went well. It seems to be stable enough. Cross
> fingers, touch wood etc.
> 
> I also took advantage of the latest cvsup to 5.4-PRE and ensuing recompile
> to revert to SCHED_4BSD from SCHED_ULE and PREEMPTION in the kernel. The
> difference is staggering.
> 
> One of the things I've been doing is to record some of my old cassettes
> (you know, those old plastic things with 2 holes and a tape inside :) onto
> CD. Applying a FFT filter to 50 minutes of audio takes between 10 and 15
> minutes on this machine (P-III/550, 384MB) depending on the complexity of
> the filter. During this time, with SCHED_ULE and PREEMTION, the machine is
> unusable. It freezes hard for periods of 10-12 seconds and then when it
> unfreezes (while doing disk i/o apparently) the keys you typed turn up in
(Continue reading)

Permalink | Reply | 6 comments |
headers
Garance A Drosihn | 1 Mar 2005 02:04
Picon
Favicon

Re: patch: fix 30 second hang while resuming

re <at>  note:  This might be important for 5.4-release

At 5:59 PM -0800 2/27/05, Nate Lawson wrote:
>Garance A Drosihn wrote:
>>
>>One minor point: Søren is on vacation right now.  I *think* he
>>will be getting back around March 5th....
>
>Augh.  Not the most convenient circumstances.  I'm happy to work
>with someone else if necessary.
>
>>Is this something which only comes up in 6.x?  Or is the same
>>thing happening in 5.x too?
>
>There are two bugs I sent in two separate messages.  The first
>gives several overwrites of 512 bytes of memory adjacent to the
>ATA param structure.  The second is just a very long delay on
>resume.

Well, if the first is a serious bug then I assume we can get that
fix in when Søren gets back.  I don't know who else you would
work with.  I don't know enough in that code to review any major
changes.

--

-- 
Garance Alistair Drosehn            =   gad <at> gilead.netel.rpi.edu
Senior Systems Programmer           or  gad <at> freebsd.org
Rensselaer Polytechnic Institute    or  drosih <at> rpi.edu
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mars Trading | 1 Mar 2005 02:23
Picon

Re: putc to a clist with no reserved cblocks


I haven't moved up to 5.4-PRERELEASE yet but have had this problem 
since using UC232 adapters w/ 5-stable.  Adding this line to 
uplcom.c seems to help with the read() hang problem:

#define RSAQ_STATUS_CTS	0x80

but I still get a lot of "putc to a clist with no reserved cblocks" 
whenever mgetty restarts coming out of ppp mode.

I heard that it's been fixed on -current; wonder when it'll get to 
-stable?

Dennis 

On Monday 28 February 2005 09:14, Brandon Fosdick wrote:
> Daniel O'Connor wrote:
> > On Mon, 28 Feb 2005 11:14, Brandon Fosdick wrote:
> >>I'm working on a small app that talks to a device with a FTDI
> >> USB to 232 chip in it. ucom and uftdi seem to detect it just
> >> fine. But calls to read() hang and I'm getting messages like
> >> "putc to a clist with no reserved cblocks" in my kernel logs.
> >> Any idea what this is?
> >
> > What version of FreeBSD?
>
> Oops, sorry about that.
>
> 17:14 bfoz <at> poseidon~>uname -a
> FreeBSD poseidon.bfoz.net 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE
(Continue reading)

Permalink | Reply | 0 comments |
headers
Don Bowman | 1 Mar 2005 03:03
Favicon

RE: Adaptec 3210S, 4.9-STABLE, corruption when disk fails

From: Uwe Doering [mailto:gemini <at> geminix.org] 
> Don Bowman wrote:
> > I have a machine running:
> > 
> > $ uname -a
> > FreeBSD machine.phaedrus.sandvine.com 4.9-STABLE FreeBSD 
> 4.9-STABLE #0:
> > Fri Mar 19 10:39:07 EST 2004
> > user <at> machine.phaedrus.sandvine.com:/usr/src/sys/compile/LABDB  i386
> > 

...

I have merged asr.c from RELENG_4 to get this fix:

"Fix a mis-merge in the MFC of rev. 1.64 in rev. 1.3.2.3; the following
change wasn't included:
- Set the CAM status to CAM_SCSI_STATUS_ERROR rather than CAM_REQ_CMP
  in case of a CHECK CONDITION."

since I guess its conceivable this could cause my problem.

--don
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |
headers
Suresh Naidu | 1 Mar 2005 03:41
Picon

(Help Me!) Problem in Compiling Nx Src on FreeBSD Machine of version 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0:)

Hi Guys

 GREETING!!!

I am facing few errors while compiling Nx src can Any one please help
me in the below issue.

I am giving detail explanation ( with errors printed) about the errors
I got step by Step please go through the errors if necessary and
please do let me know any solution.

FYI,
I am using FreeBSD machine for compiling the below src, and FreeBSD version is
5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0:)

After Untar I noticed .... 11 CONFIGURE SCRIPTS and MAKE FILES , which
can be executed I have executed all the 11 CONFIGURE SCRIPTS and MAKE
files and explained u all the output for ur reference

I have downloaded following tarballs from the
 http://www.nomachine.com/sources  NX-OSS Sources

NOTE: IF I am worng with the following procedure please do let me know
the correct way to compile NX SRC on FreeBSD machine

----------Start of  TAR BALLS  List -------

1. nxagent-1.4.0-65.tar.gz
2. nxdarwin-1.4.0-3.tar.gz
3. nxauth-1.4.0-2.tar.gz
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matt Emmerton | 1 Mar 2005 04:24
Picon
Favicon

5.3-R and D-Link DFE530TX cards

I just installed 5.3-R on a spare machine, which is equipped with a D-Link
DFE-530TX network card.
This is a "typical" Digital 21440A-based card which has worked fine fine
under 4.x before.
In 5.3, it's shows up as a 'de' device, but I recall it being either a 'dc'
or a 'vr' under 4.x.  Or maybe not.

Here's what "boot -v" shows (hand-transcribed):

de0: <Digital 21140A Fast Ethernet> port 0xe800-0xe87f mem
0xc9000000-0xc900007f irq 5 at device 9.0 in pci0
de0: Reserved 0x80 bytes for rid 0x10 type 4 at 0xe800
de0: can't read ENET ROM (why=-4) (7f7fef7f ..... )
de0: 21140A [10-100Mb/s] pass 2.2
de0: address unknown

Any ideas of what I can do to get this card working?  I am going cvsup
to -STABLE as soon as I can find another card that works.

--
Matt Emmerton

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 4 comments |
headers
John Reynolds | 1 Mar 2005 05:09

Re: CALL FOR TESTERS: new candidate for libusb port


[ On Monday, February 28, Peter Pentchev wrote: ]
> 
> Wouldn't it be better if you provided a patch to the port as well, so
> people can build it on other releases of FreeBSD, e.g. 4.x? :)
> 
> G'luck,
> Peter
> 

These easiest way to do this it seems is to attach a shar archive of the
current port. I could not get the "diff -urN" output I created to patch back
cleanly onto a "virgin" libusb directory and I have very few cycles to debug
patch(1)'s behavior (or what I did wrong in making the diff) tonight :(. So,
for those interested in libusb on other versions of FreeBSD, do the following.

 0) Save the shar attachment to "libusb.shar"
 1) backup your existing .so files then pkg_delete -f libusb-0.1.7_1
 2) (as root) cd /usr/ports/devel
 3) backup your libusb: mv libusb libusb.orig
 4) sh /path/to/libusb.shar

this should create the libusb directory again and everything under it. Go to
libusb and do the usual "make && make install".

As I had mentioned before, Johannes bumped the lib version so after you compile
and install this port you will need to go to /usr/local/lib (or whatever your
PREFIX is) and do

  ln -s libusb-0.1.so.8 libusb-0.1.so.7
(Continue reading)

Permalink | Reply | 0 comments |
headers
Doug White | 1 Mar 2005 06:23

Re: FreeBSD 5.3-R-p5: frequent kernel panics

On Mon, 28 Feb 2005, Piotr Gnyp wrote:

> On Fri, Feb 25, 2005 at 05:11:46PM -0800, Doug White wrote:
> > Please capture the panic messages and relevant kernel output along with
> > your traces. It helps to know what the system was doing when it tanked,
> > and the trap info decodes the frame in an easy-to-digest format for
> > humans. :)
>
> In info files:
> Good dump found on device /dev/da2s1b
>   Architecture: i386
>   Architecture version: 1
>   Dump length: 1073152000B (1023 MB)
>   Blocksize: 512
>   Dumptime: Wed Feb 23 15:31:58 2005
>   Versionstring: FreeBSD 5.3-RELEASE-p5 #1: Fri Feb 18 11:30:01 CET 2005
>   Panicstring: page fault
>   Bounds: 6

This is insufficient... use kgdb to load up the crashdump and post the
output of 'print msgbuf'. That will have the trap message in it.

> > Your traces are quite bizarre... somehow ttwakeup() jumps off into space.
> > Line 2370 of ttwakeup() is ttecho() which implies your system is suffering
> > from severe memory corruption, or your kernel binary is damaged.  I'd
> > suggest doing a fresh buildworld+kernel and running memtest86. Also the
> > mpt driver in 5.3 is known to react badly to SCSI errors but I don't think
> > it runs off and randomly corrupts memory.
>
> I phoned HP, they told me to reorganize RAM in banks, so now 512MB is in
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel O'Connor | 1 Mar 2005 06:38
Picon
Favicon

Suppressing bounce messages in sendmail

Hi,
We run sendmail on our systems in the field to hold and send email (but never 
receive it from the outside world) and I would like to be able to suppress 
bounce generation.

The local user sending the email on the system has it's email redirected 
outside (to us back at base) so we're not the bounce messages provide pretty 
much zero useful information and just slow the link down when it does come 
back.

Does anyone know how? I've seen DOUBLE_BOUNCE_ADDRESS which would help, but it 
would be nice to suppress them all if possible.

Thanks.

--

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Permalink | Reply | 3 comments |
headers
O. Hartmann | 1 Mar 2005 08:30
Picon
Picon
Favicon

Re: FreeBSD 5.4-PRERELEASE as cvsupdated today won't build, OS crashes

Well, it sounds funny,
but it seems to be fixed by plugging in keyboard/mouse (both USB) into 
the USB ports on mobo - not as the scientist in Mainz did: into the
TFT's USB hub. This seems to be an issue. Fridey last week, this machine ran
head- and keyboardless until I did some stupid misconfigurations in the
kernel. That's it ...

Sorry

Oliver

P.S. Why is this behaviour so lethal to the kernel?

Donald J. O'Neill wrote:
> On Monday 28 February 2005 11:06 am, Robert Watson wrote:
> 
>>On Mon, 28 Feb 2005, O. Hartmann wrote:
>>
>>>I did a cvsupdate several minutes before and tried to build world. 
>>>A buildworld stops as shown below in building libkvm.
>>
>>This is believed to now be fixed with an updated kvm_proc.c.  If not,
>>please let me know.
>>
>>
>>>Also, the system is really instable after I build the kernel for
>>>itself. Under heavy load, the machine get stuck and freezes.
>>>
>>>I have no more informations due to remote control of the system.
>>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane