Re: LOR on current as of last Friday

[Alexander Pohoyda]

I hope this is not off topic here.
> > I'm talking about TP600E and 4.7-STABLE (as of yesterday) here.

Just recompiled:

device  pcm
options PNPBIOS

> > ps2 ? audio
Enabled, Address 530, IRQ 5, DMA 3, SBAddress 220

> > ps2 ? midi
Enabled, Address 330, IRQ 9

> > No sound. Ideas?
Same result.

A new line in dmesg:
pci0:  (vendor=0x1013, dev=0x6001) at 6.0 irq 10

I do use DOS ps2 utility, and it seems to work.
Should I disable AUDIOCTRL device? What about PCIIRQ?

Anything else I may try?
Thanks to all who replied!


-- 
Alexander Pohoyda
<[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[Max Khon]

hi, there!

On Mon, Jan 27, 2003 at 07:05:45PM -0800, David Schultz wrote:

> > > > > Portions of the ext2fs source are covered by the GPL.  You
> > > > > need to rebuild the kernel with "option EXT2FS".  The
> > > > > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
> > > > 
> > > > This is weird.
> > > > Builting it as part of kernel is ok, but separate, as a module
> > > > isn't.
> > > 
> > > IIRC NetBSD has BSD-copyrighted ext2fs implementation
> > 
> > Closely tied to their VFS implementation, which is different, of course,
> > last I heard it was a fairly heavy task to port it, but something a lot
> > of people would like to see.
> 
> Does it work any better/worse than FreeBSD's implementation?

I've heard that their implementation is more stable and bug-free.
Just a speculation though. Never had a time to look at it.

/fjoe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: INVARIANTS-related fs panic on alpha

[Kris Kennaway]

On Sat, Jan 25, 2003 at 12:12:34AM -0800, Kris Kennaway wrote:
> One of the alpha package clients panicked with this.  It was under
> very high load at the time (25 simultaneous package builds):
> 
> fatal kernel trap:
> 
> trap entry = 0x2 (memory management fault)
> faulting va= 0xdeadc0dedeadc0e6
> type   = access violation
> cause  = store instruction
> pc = 0xfc53453c
> ra = 0xfc53b2a8
> sp = 0xfe001da15b30
> curthread  = 0xfc003e33b930
> pid = 3, comm = g_up
> 
> Stopped at  add_to_worklist+0xac:   stq a0,0x8(t0) <0xdeadc0dedeadc0e6> 
>
> db> trace
> add_to_worklist() at add_to_worklist+0xac
> handle_written_inodeblock() at handle_written_inodeblock+0x5e8
> softdep_disk_write_complete() at softdep_disk_write_complete+0xac
> bufdone() at bufdone+0x19c
> bufdonebio() at bufdonebio+0x1c
> biodone() at biodone+0x28
> g_dev_done() at g_dev_done+0xd8
> biodone() at biodone+0x28
> g_io_schedule_up() at g_io_schedule_up+0x4c
> g_up_procbody() at g_up_procbody+0x9c
> fork_exit() at fork_exit+0x100
> exception_return() at exception_return
> --- root of call graph ---
> db>

Here it is again:

fatal kernel trap:

trap entry = 0x4 (unaligned access fault)
faulting va= 0xdeadc0dedeadc0e6
opcode = 0x2d
register   = 0x10
pc = 0xfc534540
ra = 0xfc53b2a8
sp = 0xfe0006c0fb30
curthread  = 0xfc0007ba7930
pid = 3, comm = g_up

Stopped at  add_to_worklist+0xb0:   ldq t0,0x7c60(gp) <0xfc6581d0> 
 
db> trace
add_to_worklist() at add_to_worklist+0xb0
handle_written_inodeblock() at handle_written_inodeblock+0x5e8
softdep_disk_write_complete() at softdep_disk_write_complete+0xac
bufdone() at bufdone+0x19c
bufdonebio() at bufdonebio+0x1c
biodone() at biodone+0x28
g_dev_done() at g_dev_done+0xd8
biodone() at biodone+0x28
g_io_schedule_up() at g_io_schedule_up+0x4c
g_up_procbody() at g_up_procbody+0x9c
fork_exit() at fork_exit+0x100
exception_return() at exception_return
--- root of call graph ---
db>




msg51086/pgp0.pgp
Description: PGP signature

5.0 kernel build problem

[VNI imap]

I'm trying to upgrade from 4.7-RELEASE-P1 to 5.0-RELEASE but I consistently
get the same error when trying to compile a kernel (GENERIC or otherwise):


linking kernel
   textdata bss dec hex filename
3043330  343744  277828 3664902  37ec06 kernel
cd /usr/src/sys/modules ;
MAKEOBJDIRPREFIX=/usr/obj/usr/src/sys/GERTRUDE/modules KMODDIR=/boot/kernel
MACHINE=i386 make all
===> accf_data
make: don't know how to make @/sys/inttypes.h. Stop



I feel silly not being able to find the problem.  This is after a buildworld
and comes late in the process after:

env -i make buildkernel KERNCONF=GERTRUDE

Attempting to build GENERIC results in the same failure.

thanks


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Force 1 CPU on SMP kernel?

[Adam Migus]

Hi,
I'm doing some performance analysis on FreeBSD.  I would like to
be able to make an SMP kernel use only one CPU.  Of course I
realize running GENERIC would only use 1 CPU but the concern is
that the overhead assoicated with SMP will skew the statistics. 
So my question is what would be the 'best' way to make an SMP
kernel only start/use CPU0?
-- 
Adam Migus - Research Scientist
Network Associates Laboratories (http://www.nailabs.com)
TrustedBSD (http://www.trustedbsd.org)
FreeBSD (http://www.freebsd.org)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Lock order reversal in if_ether.c

[Andre Guibert de Bruet]

Hello,

I've seen this very same message on one of my -current testboxes. While
we're on the topic of LORs, I've also come across the following:

Jan 27 00:44:57 largo kernel: lock order reversal
Jan 27 00:44:57 largo kernel: 1st 0xc6708314 inp (inp) 
@../../../netinet/tcp_input.c:641
Jan 27 00:44:57 largo kernel: 2nd 0xc0390cec tcp (tcp) @ 
../../../netinet/tcp_usrreq.c:621

and:

Jan 27 09:41:41 largo kernel: lock order reversal
Jan 27 09:41:41 largo kernel: 1st 0xc63d0460 process lock (process lock) @ 
../../../kern/kern_descrip.c:2104
Jan 27 09:41:41 largo kernel: 2nd 0xc63b9c34 filedesc structure (filedesc structure) @ 
../../../kern/kern_descrip.c:2111

largo# uname -a
FreeBSD largo.properkernel.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jan 27 04:25:33 
EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LARGO i386

Regards,

> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>

On Mon, 27 Jan 2003, Craig Rodrigues wrote:

> Hi,
>
> I am seeingthis from a kernel cvsup'd a few days ago:
>
> login: lock order reversal
>  1st 0xc060ad20 arp mutex (arp mutex) @ /usr/src/sys/netinet/if_ether.c:151
>  2nd 0xc339097c radix node head (radix node head) @ /usr/src/sys/net/route.c:549
>
> Thanks.
> --
> Craig Rodrigues
> http://home.attbi.com/~rodrigc
> [EMAIL PROTECTED]
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[Juli Mallett]

* De: David Schultz <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: add ext2fs to the module list in modules/Makefile ]
> Thus spake Juli Mallett <[EMAIL PROTECTED]>:
> > * De: Max Khon <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
> > [ Subjecte: Re: add ext2fs to the module list in modules/Makefile ]
> > > IIRC NetBSD has BSD-copyrighted ext2fs implementation
> > 
> > Closely tied to their VFS implementation, which is different, of course,
> > last I heard it was a fairly heavy task to port it, but something a lot
> > of people would like to see.
> 
> Does it work any better/worse than FreeBSD's implementation?

Think about it: people don't have to be bothered by the license when they
work on it, etc.
-- 
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet
OpenDarwin, Mono, FreeBSD Developer
ircd-hybrid Developer, EFnet addict
FreeBSD on MIPS-Anything on FreeBSD

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[David Schultz]

Thus spake Juli Mallett <[EMAIL PROTECTED]>:
> * De: Max Khon <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
>   [ Subjecte: Re: add ext2fs to the module list in modules/Makefile ]
> > hi, there!
> > 
> > On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:
> > 
> > > On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > > > Portions of the ext2fs source are covered by the GPL.  You
> > > > need to rebuild the kernel with "option EXT2FS".  The
> > > > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
> > > 
> > > This is weird.
> > > Builting it as part of kernel is ok, but separate, as a module
> > > isn't.
> > 
> > IIRC NetBSD has BSD-copyrighted ext2fs implementation
> 
> Closely tied to their VFS implementation, which is different, of course,
> last I heard it was a fairly heavy task to port it, but something a lot
> of people would like to see.

Does it work any better/worse than FreeBSD's implementation?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanicin -current

[Aniruddha Bohra]

Hi
I agree here with Terry. It is immense help to be able to set
MAXMEM to something less to study the behaviour of the system under
memory pressure for one. 
It is also helpful to keep the size of the crash dumps small 

Aniruddha


On Mon, 27 Jan 2003, Terry Lambert wrote:

> Vincent Poy wrote:
> > > > >>Is there any reason, on newer motherboards, to need the MAXMEM option?
> > > > >
> > > > > I don't know.  I've always used MAXMEM.  Guess it's
> > > > > time to remove it from my kernel config file.
> > > >
> > > > FWIW, I've been using FBSD -stable and -current for about 3 years
> > > > on five different machines and I've never used MAXMEM.  Never had
> > > > any problems recognizing memory, either -- guess I've been luckier
> > > > than some.
> > >
> > > MAXMEM is useful for testing configurations with less memory,
> > > without having to open up your box and yank SIMMs, or to have
> > > a bunch of different sized pairs of SIMMs lying around.
> > 
> > I thought the original purpose atleast in FreeBSD 2.x and earlier
> > was so the kernel can recognize more than 64 megs of physical ram.
> 
> If you guys are planning on yanking it from config files and
> the source code, you should at least be aware that there is
> more than one use for it, one which is not tied to using old
> motherboards.
> 
> -- Terry
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

src/sbin/mount/mount.c argv[0] cleanup

[John De Boskey]

Hi,

   I've built and installed a complete system with the patch
below. Amoung other things, this allows the individual mount_$vfstype
executables to not have to differentiate how they were
invoked. They can then have their XXX sections removed along
with a small amount of code (and this will help our poor
boot floppies :-)

   Does anyone know any reason why this should not be done?

Thanks!
John


Index: mount.c
===   
RCS file: /mnt/cvs/src/sbin/mount/mount.c,v
retrieving revision 1.50
diff -c -r1.50 mount.c
*** mount.c 14 Oct 2002 19:40:00 -  1.50
--- mount.c 26 Jan 2003 20:06:36 -
***
*** 469,474 
--- 469,475 
for (edir = edirs; *edir; edir++) {
(void)snprintf(execname,
sizeof(execname), "%s/mount_%s", *edir, vfstype);
+   argv[0] = execname;
execv(execname, (char * const *)argv);
}
if (errno == ENOENT) {


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Lock order reversal in if_ether.c

[Craig Rodrigues]

Hi,

I am seeingthis from a kernel cvsup'd a few days ago:

login: lock order reversal
 1st 0xc060ad20 arp mutex (arp mutex) @ /usr/src/sys/netinet/if_ether.c:151
 2nd 0xc339097c radix node head (radix node head) @ /usr/src/sys/net/route.c:549

Thanks.
-- 
Craig Rodrigues
http://home.attbi.com/~rodrigc
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Performance problems with 5.0-RELEASE

[Atte Peltomaki]

> > If it's long enough to pause the console noticibly, the next
> > thing to try is breaking to the debugger -- which might require
> > an NMI card -- to see what code it's stuck in during the pause.
> 
> It's noticeable - if you type under heavy load in console, you
> experience similar to ssh lag - you can't see what you type, but it
> appears a second later to the screen. 

Just as an update: I've been listening to quite a lot of techno/trance
music lately, and it scares me - every now and then xmms loses the beat
when playing, even if there was absolutely no other load. The pause is
so quick you can't really notice it elsewhere, but it's definetely
there. 

Continuing investigations.


Atte Peltomäki
http://kameli.org

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: tunefs using libufs.

[Juli Mallett]

* De: Conrad Sabatier <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: tunefs using libufs. ]
> I'm getting some odd behavior with tunefs (5.0-CURRENT cvsupped and built
> Sunday, Jan 26).  If a filesystem, rather than an actual device, is specified,
> it spits out a weird error message regarding my linproc mount:
> 
> # tunefs -p /tmp
> tunefs: linproc: could not find special device
> 
> My /etc/fstab:
> 
> # DeviceMountpoint  FStype  Options DumpPass#
> /dev/ad0s1b noneswapsw  0   0
> /dev/ad0s1a /   ufs rw  1   1
> /dev/ad0s1f /tmpufs rw  2   2
> /dev/ad0s1g /usrufs rw  2   2
> /dev/ad0s1e /varufs rw  2   2
> /dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
> /dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0
> proc/proc   procfs  rw  0   0
> /dev/ad1s1e /mm ufs rw  2   2
> linproc /compat/linux/proc  linprocfs   rw  0   0
> 
> Is anyone else seeing this?  Could it just be the result of the gcc
> optimizations I'm using (an admittedly heavy set of flags)?  Or might it be
> related to the recent changes the OP mentioned?

Now that libufs will hunt for the disk, tunefs shouldn't, that's all.
Doing it both shouldn't have caused a problem, I don't think, but it
does for me, too.  This is caused by more-recent changes to libufs.
I'll commit a fix shortly, once I verify the behaviour is correct.
-- 
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet
OpenDarwin, Mono, FreeBSD Developer
ircd-hybrid Developer, EFnet addict
FreeBSD on MIPS-Anything on FreeBSD

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: continuing problems with RealPlayer

[John Van Sickle]

On Sun, 26 Jan 2003 13:42:32 -0500
Mikhail Teterin <[EMAIL PROTECTED]> wrote:

> Can anyone, please, try the following URL, for example:
> 
>   pnm://rm.content.loudeye.com/~ttt-600111/0619060_0103_00_0002.ra
> 
> It causes RealPlayer8.cs2 to get SIGABRT on two of my -current systems. I must 
> have it working on at least one machine in the house, but before changing the
> laptop to -stable, I'd like to find out it will work there :-) The other 
> alternative would be to install Windows...
> 
> FWIW, I tried with both linux_base and linux_base-6 -- same symptoms. There 
> are other URLs on Amazon's Music shopping, that break it, but one is enough, 
> I guess...

  I know this doesn't in any way help you with your problem but mplayer can play both 
RealPlayer8 video and audio. There is even a mozilla plugin in the works.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

subscribe

[john chung]

subscribe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: tunefs using libufs.

[Conrad Sabatier]

I'm getting some odd behavior with tunefs (5.0-CURRENT cvsupped and built
Sunday, Jan 26).  If a filesystem, rather than an actual device, is specified,
it spits out a weird error message regarding my linproc mount:

# tunefs -p /tmp
tunefs: linproc: could not find special device

My /etc/fstab:

# DeviceMountpoint  FStype  Options DumpPass#
/dev/ad0s1b noneswapsw  0   0
/dev/ad0s1a /   ufs rw  1   1
/dev/ad0s1f /tmpufs rw  2   2
/dev/ad0s1g /usrufs rw  2   2
/dev/ad0s1e /varufs rw  2   2
/dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
/dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0
proc/proc   procfs  rw  0   0
/dev/ad1s1e /mm ufs rw  2   2
linproc /compat/linux/proc  linprocfs   rw  0   0

Is anyone else seeing this?  Could it just be the result of the gcc
optimizations I'm using (an admittedly heavy set of flags)?  Or might it be
related to the recent changes the OP mentioned?

On 18-Jan-2003 Juli Mallett wrote:
> Can I get some tests of these changes to make tunefs use libufs?
> 
> Thanx,
> juli.

-- 
Conrad Sabatier <[EMAIL PROTECTED]> - "In Unix veritas"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

5.0-RELEASE Boot Failure on Thinkpad R30

[Raymond Mouton]

Installs from network just fine, no problems besides not finding the ports 
package. Then, when reboots, system goes into panic almost immediately after 
booting.

Because it is not feasible to make screenshots using some program in this 
case, I made them in the literal sense with my digital camera.
I have included the address below for the pictures from which you can see my 
bios and BTX loader env variables clearly (enough(NOTE: My hand shakes in 
some of the remaining culled photos)) and the portion of the dmesg that 
happens through till the panic.

I hope someone can tell me how to either fix this or get around it because I 
want to enjoy the new features of 5.0 rather than having to regress to 
4.7-RELEASE (Which works except for ohci device (I have submitted bug report 
on this))

Sincerely,
Raymond A. Mouton

http://photos.yahoo.com/bc/the_physics_guy/lst?&.dir=/FreeBSD+5.0-Release+on+Thinkpad+R30&.src=ph&.begin=&.view=t&.order=&.done=http%3a//photos.yahoo.com/bc/the_physics_guy/lst%3f%26.dir=/FreeBSD%2b5.0-Release%2bon%2bThinkpad%2bR30%26.src=ph%26.view=t";>Photos 
of 5.0-RELEASE on Thinkpad R30

and for those who get a REALLY jumbled link above

http://photos.yahoo.com/bc/the_physics_guy/lst?&.dir=/FreeBSD+5.0-Release+on+Thinkpad+R30&.src=ph&.begin=&.view=t&.order=&.done=http%3a//photos.yahoo.com/bc/the_physics_guy/lst%3f%26.dir=/FreeBSD%2b5.0-Release%2bon%2bThinkpad%2bR30%26.src=ph%26.view=t

_
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Matthew N. Dodd]

On Tue, 28 Jan 2003, Alexander Pohoyda wrote:
> I'm talking about TP600E and 4.7-STABLE (as of yesterday) here.
>
> Just recompiled:
>
> apog@oak:~$ grep csa /sys/conf/files
> dev/sound/pci/csa.c optional csa pci
> #dev/sound/pci/csa.coptional pcm pci
> dev/sound/pci/csapcm.c  optional csa pcm pci
> apog@oak:~$ grep pcm0 /sys/i386/conf/OAK
> device  pcm0at isa? port 0x530 irq 9 drq 1 flags 0x10
> apog@oak:~$ grep pcm /var/run/dmesg.boot
> apog@oak:~$
>
>
> ps2 ? audio
> Enabled, Address 530, IRQ 9, DMA 0 - 1, SBAddress 220
>
> ps2 ? midi
> Enabled, Address 580, IRQ 5
>
> No sound. Ideas?

Don't use hints; they're not going to work (I suppose they might if you
use 'snd_mss0')

Enable PNPBIOS.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Matthew N. Dodd]

On Mon, 27 Jan 2003, Alexander Pohoyda wrote:
> I'd wish to have sound working..  On my second notebook (TP600E) I have
> a PCI sound card -- 0x1013 0x6001. Don't you?

You'll need to configure the sound resources in DOS using the 'ps2.exe'
utility.  (Or you can wait a few days until I get my config util working
in FreeBSD.)

pcm0:  at port 0x220-0x233,0x388-0x38b,0x530-0x537 irq 5 drq 3,1 on isa0

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: xl thinkpad 600x watchdog timeout

[Juli Mallett]

* De: "Matthew N. Dodd" <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: xl thinkpad 600x watchdog timeout ]
> On Mon, 27 Jan 2003, Toni Schmidbauer wrote:
> > got no useful response from -mobile so re-posting to -current:
> >
> > i am having problems with 5.0-REL on an ibm thinkpad 600x.the xl
> > driver for my 3com 3ccfe575ct writes the following message to the
> > console "xl0: watchdog timeout".
> 
> The 575 may require some special driver attention.  I haven't had much
> time to look into it.

Also 3c556, which is a mini-pci 56k/xl combo card, has a lot of stalls
and tx issues.
-- 
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet
OpenDarwin, Mono, FreeBSD Developer
ircd-hybrid Developer, EFnet addict
FreeBSD on MIPS-Anything on FreeBSD

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: xl thinkpad 600x watchdog timeout

[Matthew N. Dodd]

On Mon, 27 Jan 2003, Toni Schmidbauer wrote:
> got no useful response from -mobile so re-posting to -current:
>
> i am having problems with 5.0-REL on an ibm thinkpad 600x.the xl
> driver for my 3com 3ccfe575ct writes the following message to the
> console "xl0: watchdog timeout".

The 575 may require some special driver attention.  I haven't had much
time to look into it.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Direct Server Return and FreeBSD 5

[Terry Lambert]

John David Duncan wrote:
> There's a load balancing configuration known as direct server return
> (DSR), in which packets pass from the client through the load balancer to
> the server, but then the replies from the server go directly to the client
> (bypassing the load balancer).  The way this works is that the load
> balancer sends the server an IP packet with the virtual IP address as its
> destination addr, inside an ethernet frame whose destination is the real
> MAC addr of the server. The server replies with a normal packet using the
> VIP as the source addr.
> 
> The usual way to configure a BSD box to work this way is to bring up the
> VIP as an alias on the loopback address, like this:
>ifconfig lo0 add 1.2.3.4 netmask 0xff00
> 
> As far as I can tell from my testing, this trick just doesn't work on my
> box running -CURRENT.  In tcpdump I see packets coming in but none
> going out.
> 
> Does anybody know why, or what I would have to do to change the behavior?

Rather than actually fixing the routing code, FreeBSD did a
hack to save the inbound route for outbound responses, do the
response goes out on the same interface the request came in on.

It does not check for equivalency, when it does this.

See the discussion in the -current list archives, a month or so
ago.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Direct Server Return and FreeBSD 5

[Paul Saab]

You need to set
net.inet.ip.check_interface=0

John David Duncan ([EMAIL PROTECTED]) wrote:
> 
> There's a load balancing configuration known as direct server return
> (DSR), in which packets pass from the client through the load balancer to
> the server, but then the replies from the server go directly to the client
> (bypassing the load balancer).  The way this works is that the load
> balancer sends the server an IP packet with the virtual IP address as its
> destination addr, inside an ethernet frame whose destination is the real
> MAC addr of the server. The server replies with a normal packet using the
> VIP as the source addr.
> 
> The usual way to configure a BSD box to work this way is to bring up the
> VIP as an alias on the loopback address, like this:
>ifconfig lo0 add 1.2.3.4 netmask 0xff00
> 
> As far as I can tell from my testing, this trick just doesn't work on my
> box running -CURRENT.  In tcpdump I see packets coming in but none
> going out.
> 
> Does anybody know why, or what I would have to do to change the behavior?
> 
> - JD
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message

-- 
Paul Saab
Technical Yahoo
[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
Do You .. uhh .. Yahoo!?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Direct Server Return and FreeBSD 5

[John David Duncan]

There's a load balancing configuration known as direct server return
(DSR), in which packets pass from the client through the load balancer to
the server, but then the replies from the server go directly to the client
(bypassing the load balancer).  The way this works is that the load
balancer sends the server an IP packet with the virtual IP address as its
destination addr, inside an ethernet frame whose destination is the real
MAC addr of the server. The server replies with a normal packet using the
VIP as the source addr.

The usual way to configure a BSD box to work this way is to bring up the
VIP as an alias on the loopback address, like this:
   ifconfig lo0 add 1.2.3.4 netmask 0xff00

As far as I can tell from my testing, this trick just doesn't work on my
box running -CURRENT.  In tcpdump I see packets coming in but none
going out.

Does anybody know why, or what I would have to do to change the behavior?

- JD


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

[5.0-RELEASE] uid option in ipfw

[Oleg Baranov]

It looks like firewall in 5.0-RELEASE doesn't respect uid option.
I migrated from 4.7 where the following lines worked fine:

allow tcp from me to any uid 500 setup
allow udp from me to any uid 500 keep-state

I couldn't get these lines working on 5.0 (packets don't match these rules).
it's a little strange thing - the following lines DO work, but they 
match for ANY user on the system:

allow tcp from me to any uid 0 setup
allow udp from me to any uid 0 keep-state

also the counters are updated in a mysterious way...
it's a very confusing thing for me. can anyone help to solve the problem 
plz?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0 i386 Live Filesystem

[Evan Dower]

Oh, I didn't realize. Fantastic. Thanks a lot. :-)


From: Kris Kennaway <[EMAIL PROTECTED]>
To: Evan Dower <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: 5.0 i386 Live Filesystem
Date: Mon, 27 Jan 2003 15:57:18 -0800
MIME-Version: 1.0
Received: from mc7-f40.law1.hotmail.com ([65.54.253.47]) by 
mc7-s6.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 27 Jan 
2003 15:57:35 -0800
Received: from mx2.freebsd.org ([216.136.204.119]) by 
mc7-f40.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 27 Jan 
2003 15:57:33 -0800
Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])by 
mx2.freebsd.org (Postfix) with ESMTPid 0FDA755760; Mon, 27 Jan 2003 
15:57:23 -0800 (PST)(envelope-from [EMAIL PROTECTED])
Received: by hub.freebsd.org (Postfix, from userid 538)id BA1C137B405; Mon, 
27 Jan 2003 15:57:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org 
(Postfix) with SMTPid 9AC562E800A; Mon, 27 Jan 2003 15:57:21 -0800 (PST)
Received: by hub.freebsd.org (bulk_mailer v1.12); Mon, 27 Jan 2003 15:57:21 
-0800
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])by 
hub.freebsd.org (Postfix) with ESMTP id 5804837B401for 
<[EMAIL PROTECTED]>; Mon, 27 Jan 2003 15:57:20 -0800 (PST)
Received: from obsecurity.dyndns.org 
(adsl-64-169-104-205.dsl.lsan03.pacbell.net [64.169.104.205])by 
mx1.FreeBSD.org (Postfix) with ESMTP id 2EBD343F43for 
<[EMAIL PROTECTED]>; Mon, 27 Jan 2003 15:57:19 -0800 
(PST)(envelope-from [EMAIL PROTECTED])
Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5])by 
obsecurity.dyndns.org (Postfix) with ESMTPid 403A867892; Mon, 27 Jan 2003 
15:57:18 -0800 (PST)
Received: by rot13.obsecurity.org (Postfix, from userid 1000)id 1B8171719; 
Mon, 27 Jan 2003 15:57:18 -0800 (PST)
X-Message-Info: dHZMQeBBv44lPE7o4B5bAg==
Delivered-To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.4i
Sender: [EMAIL PROTECTED]
List-ID: 
List-Archive:  (Web Archive)
List-Help:  (List Instructions)
List-Subscribe: 

List-Unsubscribe: 

X-Loop: FreeBSD.ORG
Precedence: bulk
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 27 Jan 2003 23:57:34.0156 (UTC) 
FILETIME=[DC6478C0:01C2C65F]

On Mon, Jan 27, 2003 at 03:50:40PM -0800, Evan Dower wrote:
> I recently was installing the world when it ran out of space. I ^C'ed 
too
> many times and ended up with trying to start up on an incomplete world,
> really incomplete. I don't have /bin/sh, for example. Can someone point 
me
> toward an i386 Live Filesystem ISO so I can try to fix my mess?
> Thanks a lot,
> Evan Dower (and his fubar computer)

That's what the disc 2 iso is on the FTP sites.

Kris
<< attach3 >>


_
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanicin -current

[Terry Lambert]

Vincent Poy wrote:
> > > MAXMEM is useful for testing configurations with less memory,
> > > without having to open up your box and yank SIMMs, or to have
> > > a bunch of different sized pairs of SIMMs lying around.
> >
> > For uses such as testing I can understand, but I don't see a use under
> > normal conditions, at least on newer systems.  I haven't dug into the
> > source yet today, but there must be a reason why ACPI doesn't play nice
> > on certain systems when MAXMEM is specified.
> >
> > I wonder if it is just AMD systems?  Mine's a 900MHz Duron, and IIRC I
> > think someone else in earlier in the thread was using an AMD also.
> 
> I posted the original thread and can say the problem occurs on
> both PII366 notebook, P4m-2Ghz, P4-1.7Ghz as well as PIII1Ghz systems and
> various AMD Athlon XP's.

This is a well known problem with the TLB implementation; the
answer is that, were you to yank out real physical memory, so
that you had the same amount of memory as your were telling
the machine you had, you would end up with the same problem.

In other words, the setting is exposing a bug in FreeBSD, and
this is what it's supposed to be doing, so please leave it
alone in the source code, so that someone who wants to fix it
can reproduce the problem locally on their machine.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0 i386 Live Filesystem

[Kris Kennaway]

On Mon, Jan 27, 2003 at 03:50:40PM -0800, Evan Dower wrote:
> I recently was installing the world when it ran out of space. I ^C'ed too 
> many times and ended up with trying to start up on an incomplete world, 
> really incomplete. I don't have /bin/sh, for example. Can someone point me 
> toward an i386 Live Filesystem ISO so I can try to fix my mess?
> Thanks a lot,
> Evan Dower (and his fubar computer)

That's what the disc 2 iso is on the FTP sites.

Kris



msg51061/pgp0.pgp
Description: PGP signature

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanicin -current

[Terry Lambert]

Vincent Poy wrote:
> > > >>Is there any reason, on newer motherboards, to need the MAXMEM option?
> > > >
> > > > I don't know.  I've always used MAXMEM.  Guess it's
> > > > time to remove it from my kernel config file.
> > >
> > > FWIW, I've been using FBSD -stable and -current for about 3 years
> > > on five different machines and I've never used MAXMEM.  Never had
> > > any problems recognizing memory, either -- guess I've been luckier
> > > than some.
> >
> > MAXMEM is useful for testing configurations with less memory,
> > without having to open up your box and yank SIMMs, or to have
> > a bunch of different sized pairs of SIMMs lying around.
> 
> I thought the original purpose atleast in FreeBSD 2.x and earlier
> was so the kernel can recognize more than 64 megs of physical ram.

If you guys are planning on yanking it from config files and
the source code, you should at least be aware that there is
more than one use for it, one which is not tied to using old
motherboards.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

5.0 i386 Live Filesystem

[Evan Dower]

I recently was installing the world when it ran out of space. I ^C'ed too 
many times and ended up with trying to start up on an incomplete world, 
really incomplete. I don't have /bin/sh, for example. Can someone point me 
toward an i386 Live Filesystem ISO so I can try to fix my mess?
Thanks a lot,
Evan Dower (and his fubar computer)

_
Add photos to your e-mail with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/featuredemail


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Diff to make fsck(8) ignore certain filesystems.

[Juli Mallett]

* De: Juli Mallett <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Diff to make fsck(8) ignore certain filesystems. ]
> This prevents fsck from failing at boot if there are nullfs or unionfs
> filesystems in fstab(5), as reported by [EMAIL PROTECTED]  Anyone mind
> if I commit this?  (Or have suggestions for filesystems to add to the
> list?)

Nevermind, it's too long since I wrote an fstab(5) by hand, and I (and the
submitter) forgot about the Pass# field, and what it actually means *sigh*
Sorry :/

juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet.
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[Juli Mallett]

* De: Max Khon <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: add ext2fs to the module list in modules/Makefile ]
> hi, there!
> 
> On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:
> 
> > On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > > Portions of the ext2fs source are covered by the GPL.  You
> > > need to rebuild the kernel with "option EXT2FS".  The
> > > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
> > 
> > This is weird.
> > Builting it as part of kernel is ok, but separate, as a module
> > isn't.
> 
> IIRC NetBSD has BSD-copyrighted ext2fs implementation

Closely tied to their VFS implementation, which is different, of course,
last I heard it was a fairly heavy task to port it, but something a lot
of people would like to see.

juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet.
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[Max Khon]

hi, there!

On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:

> On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > Portions of the ext2fs source are covered by the GPL.  You
> > need to rebuild the kernel with "option EXT2FS".  The
> > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
> 
> This is weird.
> Builting it as part of kernel is ok, but separate, as a module
> isn't.

IIRC NetBSD has BSD-copyrighted ext2fs implementation

/fjoe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Alexander Pohoyda]

I'm talking about TP600E and 4.7-STABLE (as of yesterday) here.

Just recompiled:

apog@oak:~$ grep csa /sys/conf/files
dev/sound/pci/csa.c optional csa pci
#dev/sound/pci/csa.coptional pcm pci
dev/sound/pci/csapcm.c  optional csa pcm pci
apog@oak:~$ grep pcm0 /sys/i386/conf/OAK 
device  pcm0at isa? port 0x530 irq 9 drq 1 flags 0x10
apog@oak:~$ grep pcm /var/run/dmesg.boot 
apog@oak:~$


ps2 ? audio
Enabled, Address 530, IRQ 9, DMA 0 - 1, SBAddress 220

ps2 ? midi
Enabled, Address 580, IRQ 5


No sound. Ideas?


-- 
Alexander Pohoyda
<[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Diff to make fsck(8) ignore certain filesystems.

[Juli Mallett]

This prevents fsck from failing at boot if there are nullfs or unionfs
filesystems in fstab(5), as reported by [EMAIL PROTECTED]  Anyone mind
if I commit this?  (Or have suggestions for filesystems to add to the
list?)

%%%
Index: fsck.c
===
RCS file: /home/ncvs/src/sbin/fsck/fsck.c,v
retrieving revision 1.12
diff -d -u -r1.12 fsck.c
--- fsck.c  31 Oct 2002 15:32:39 -  1.12
+++ fsck.c  27 Jan 2003 23:24:51 -
@@ -79,6 +79,8 @@
 static int flags = 0;
 static int forceflag = 0;
 
+static const char *nofsck[] = { "nullfs", "unionfs", NULL };
+
 static int checkfs(const char *, const char *, const char *, char *, pid_t *);
 static int selected(const char *);
 static void addoption(char *);
@@ -90,6 +92,7 @@
 static const char *getfslab(const char *);
 static void usage(void) __dead2;
 static int isok(struct fstab *);
+static int skip(const char *);
 
 int
 main(int argc, char *argv[])
@@ -209,6 +212,10 @@
errx(1, "%s has unknown file system type.",
spec);
}
+   if (skip(type)) {
+   printf("%s: FILESYSTEM DOES NOT SUPPORT FSCK\n", *argv);
+   continue;
+   }
if ((flags & CHECK_BACKGRD) &&
checkfs(type, spec, mntpt, "-F", NULL) == 0) {
printf("%s: DEFER FOR BACKGROUND CHECKING\n", *argv);
@@ -577,6 +584,17 @@
return vfstype;
 }
 
+static int
+skip(const char *fstype)
+{
+   const char *p;
+
+   for (p = nofsck[0]; p != NULL; p++) {
+   if (strcmp(p, fstype) == 0)
+   return 1;
+   }
+   return 0;
+}
 
 static void
 usage(void)
%%%

Thanx,
juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet.
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: I've just had a massive file system crash

[Rahul Siddharthan]

David Schultz wrote:
> I still can't figure out why the problem would trash your entire   
> home directory, though.  Even if the disk reordered writes and
> failed to write some sectors, directory entries that were not
> being actively modified shouldn't have become corrupted, as far as
> I know.

Something similar happened to me in 4-STABLE several months ago.
After a panic/crash (caused by an unstable USB audio driver) the
automatic fsck failed.  This happened twice; the second time my
filesystem was totally messed up, and after fsck did its thing,
several files were missing, including files in /usr/bin and /usr/sbin
that had not been touched for many weeks (ie since the last
installworld).  The damage wasn't as extensive as Greg reports, and my
home directory was spared, but I had to reinstall the base system to
get things working smoothly again.

I then turned off write caching on the IDE drive.  Afterwards I had
several such crashes (caused by the same driver) but never again had
filesystem damage -- automatic fsck always worked.  Nevertheless, as
you say, it's strange files which had not been touched went missing.

- Rahul

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

incremental cross-builds

[Max Khon]

hi, there!

Is it possible to build a part of (for example) 5.x tree on 4.x machine?
Suppose I have run make buildworld once, have bootstrap toolchain
in /usr/obj and want to rebuild only libc.

/fjoe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Martin Blapp]

Hi all,

We can end this tread. The bug has been found and fixed
in HEAD.

Martin

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: follow up on acpi issue

[Bryan Liesner]

On Mon, 27 Jan 2003, Nate Lawson wrote:

> On Sat, 25 Jan 2003, Bryan Liesner wrote:
> > Thanks, Nate.  When you suggested that I remove the apm stuff fron the
> > kernel, you meant ALL of the apm stuff, didn't you :) .  I took a
> > second look and found I still had viapm and its requirements still in
> > the config file.  The system boots fine now with acpi.
> >
> > By the way, the system didn't hang as I claimed in my earlier mail.  I
> > was able to telnet in...  Having acpi and viapm had the side effect of
> > making the console go away.
>
> viapm is VIA power management, not an apm system.  It's interesting that
> it made your console go away.  I'm sending this back to -current to see if
> anyone has ideas what might be wrong with viapm.

I had viapm and its requirements (iicbus, iicsmb) compiled in to my
4.7 kernel so that I could use mbmon to monitor temperatures, etc.
Mbmon works just fine without it on 5.0 (a benefit of acpi??).

-- 
==
= Bryan D. Liesner LeezSoft Communications, Inc. =
=  A subsidiary of LeezSoft Inc. =
= [EMAIL PROTECTED]Home of the Gipper=
==

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Alexander Pohoyda]

Thanks for your suggestions! I will try it out.

> The sound on the 600 is different from the 600E and, while I know the
> magic was different on V4, I don't have any experience with it. Most
> likely you need adjustments to hints file.

Funny is that if I add some:
hint.pcm.0.at="isa"
...

to /boot/device.hints, I will get a line telling that
pcm0: failed to probe on 

...
and later
...
pcm1:  on isa0
device_probe_and_attach: pcm1 attach returned 6

Talking about 5.0-CURRENT here.


-- 
Alexander Pohoyda
<[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Kevin Oberman]

> Date: Mon, 27 Jan 2003 23:32:57 +0100 (CET)
> From: Alexander Pohoyda <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
> 
> 
> > The sound on the 600E is weird. It connect to both PCI and ISA for
> > different functions. As a result, I have to edit /sys/conf/files to
> > delete the csa pcm entry and add csa to the csapcm line.
> > 
> > dev/sound/pci/csa.c optional csa pci
> > #dev/sound/pci/csa.coptional pcm pci
> > dev/sound/pci/csamidi.c optional midi csa
> > dev/sound/pci/csapcm.c  optional csa pcm pci
> 
> Thanks! That's something new to me, will try it out.
> 
> devicepcm
> #options  PNPBIOS
> #device   csa
> 
> Right?
If you don't have PNPBIOS, you will need to add the ISA config info to
/boot/device.hints (V5.0) or the kernel config (V4):
hint.pcm.0.at-"isa"
hint.pcm.0.port="0x52c"
hint.pcm.0.irq="5"
hint.pcm.0.drq="1"
hint.pcm.0.flags="0x10"
or
device pcm0   at isa? port 0x52c irq 5 drq 1 flags 0x10 

> I've spent a whole day trying to make it working on 4.7-STABLE. No
> result. I have seen some very old messages on mobile@ about this
> sound card, but nothing helped.
> The best I can get is:
> csa0:  mem 0x5000-0x500f,0x5010-0x50100fff irq 5 at 
>device 6.0 on pci0
> csa: card is Unknown/invalid SSID (CS4610)
> pcm0:  on csa0
> pcm0: AC97 reset timed out.pcm0: ac97 codec invalid or not present (id == 0)
> device_probe_and_attach: pcm0 attach returned 6

This indicates the need to modify /sys/conf/files before building the
kernel. For V4 the changes are the same as for V5, but the csamidi.c
line is not present in V4. If dmesg contains a csa line, you don't
have files properly edited.

> Does it matter how you configure it with ps2.exe utility?
> Which settings are you running on?

You must enable the sound card and set the IRQ and DRQ with ps2, but
the required settings are hte default, so you really should not need
to change anything. Matthew Dodd tells me that he has fixed the sound
after resume problem that was in V4, but it didn't make 5.0-Release.
You will need to be running current to get it.

> > That's all it took to get sound to work on my 600E.
> 
> I am also not able to make sound working on TP600 with 5.0-CURRENT.
> There is CS4236 there. Pure ISA, AFAIK. Worked fine with 4.5-RELEASE.
> I would spend as much time as it needs to bring it to life. I'd
> appreciate any ideas how to preceed.

The sound on the 600 is different from the 600E and, while I know the
magic was different on V4, I don't have any experience with it. Most
likely you need adjustments to hints file.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[Robert Watson]

On Tue, 28 Jan 2003, Enache Adrian wrote:

> On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > Portions of the ext2fs source are covered by the GPL.  You
> > need to rebuild the kernel with "option EXT2FS".  The
> > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
> 
> This is weird.  Builting it as part of kernel is ok, but separate, as a
> module isn't. 

That's not quite it. :-)  You building it into the kernel is fine, we just
can't do it and distribute it without putting the rest of the kernel under
GPL.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[Steve Kargl]

On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:
> On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > Portions of the ext2fs source are covered by the GPL.  You
> > need to rebuild the kernel with "option EXT2FS".  The
> > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
> 
> This is weird.
> Builting it as part of kernel is ok, but separate, as a module
> isn't.

There a linking clausing in the GPL, which one can interpret
to mean that loading ext2fs.ko into the kernel would cause
the entire kernel to be tainted by the GPL.

> 
> However, FreeBSD builds by default (as modules) the maestro3
> sound driver and the gnu fpu emulator which are GPL too.
> 

gnu fpu appears to be dual licensed software, and
covered by a BSD type license for FreeBSD's use.
Don't know about maestro3.

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: add ext2fs to the module list in modules/Makefile

[Enache Adrian]

On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> Portions of the ext2fs source are covered by the GPL.  You
> need to rebuild the kernel with "option EXT2FS".  The
> FreeBSD cannot create a ext2fs.ko and comply with the GPL.

This is weird.
Builting it as part of kernel is ok, but separate, as a module
isn't.

However, FreeBSD builds by default (as modules) the maestro3
sound driver and the gnu fpu emulator which are GPL too.

Regards
Adi


> -- 
> Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Alexander Pohoyda]

> The sound on the 600E is weird. It connect to both PCI and ISA for
> different functions. As a result, I have to edit /sys/conf/files to
> delete the csa pcm entry and add csa to the csapcm line.
> 
> dev/sound/pci/csa.c   optional csa pci
> #dev/sound/pci/csa.c  optional pcm pci
> dev/sound/pci/csamidi.c optional midi csa
> dev/sound/pci/csapcm.coptional csa pcm pci

Thanks! That's something new to me, will try it out.

device  pcm
#optionsPNPBIOS
#device csa

Right?


I've spent a whole day trying to make it working on 4.7-STABLE. No
result. I have seen some very old messages on mobile@ about this
sound card, but nothing helped.
The best I can get is:
csa0:  mem 0x5000-0x500f,0x5010-0x50100fff irq 5 at device 
6.0 on pci0
csa: card is Unknown/invalid SSID (CS4610)
pcm0:  on csa0
pcm0: AC97 reset timed out.pcm0: ac97 codec invalid or not present (id == 0)
device_probe_and_attach: pcm0 attach returned 6

Does it matter how you configure it with ps2.exe utility?
Which settings are you running on?


> That's all it took to get sound to work on my 600E.

I am also not able to make sound working on TP600 with 5.0-CURRENT.
There is CS4236 there. Pure ISA, AFAIK. Worked fine with 4.5-RELEASE.
I would spend as much time as it needs to bring it to life. I'd
appreciate any ideas how to preceed.


-- 
Alexander Pohoyda
<[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: boot delay when testing for ata devices

[David Schultz]

Thus spake Enache Adrian <[EMAIL PROTECTED]>:
> FreeBSD used to have an irritating boot delay in 4.4. It was gone in
> ~4.6, never reappeared in -STABLE, but is there in -CURRENT.
> (I've seen it also mentioned in some vmware documentation).
> 
> Applying this patch fixes it:
> 
> --- /arc/freebsd/src/sys/dev/ata/ata-all.cSun Jan 19 23:54:13 2003
> +++ sys/dev/ata/ata-all.c Mon Jan 27 21:02:34 2003
> @@ -514,7 +514,7 @@
>  
>  /* apparently some devices needs this repeated */
>  do {
> - if (ata_command(atadev, command, 0, 0, 0, ATA_WAIT_INTR)) {
> + if (ata_command(atadev, command, 0, 0, 0, ATA_IMMEDIATE)) {
>   ata_prtdev(atadev, "%s identify failed\n",
>  command == ATA_C_ATAPI_IDENTIFY ? "ATAPI" : "ATA");
>   free(ata_parm, M_ATA);
> 
> I'm not familiar with the ata code, but I can't see from ata-all.c
> which harm this could cause.

There is already at least one person for whom this code doesn't
work, so this patch doesn't seem like a good idea.  Someone needs
to figure out exactly what delays are needed here to make
everyone's hardware actually work.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

subscribe

[Brent Jones]

subscribe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

boot delay when testing for ata devices

[Enache Adrian]

FreeBSD used to have an irritating boot delay in 4.4. It was gone in
~4.6, never reappeared in -STABLE, but is there in -CURRENT.
(I've seen it also mentioned in some vmware documentation).

Applying this patch fixes it:

--- /arc/freebsd/src/sys/dev/ata/ata-all.c  Sun Jan 19 23:54:13 2003
+++ sys/dev/ata/ata-all.c   Mon Jan 27 21:02:34 2003
@@ -514,7 +514,7 @@
 
 /* apparently some devices needs this repeated */
 do {
-   if (ata_command(atadev, command, 0, 0, 0, ATA_WAIT_INTR)) {
+   if (ata_command(atadev, command, 0, 0, 0, ATA_IMMEDIATE)) {
ata_prtdev(atadev, "%s identify failed\n",
   command == ATA_C_ATAPI_IDENTIFY ? "ATAPI" : "ATA");
free(ata_parm, M_ATA);

I'm not familiar with the ata code, but I can't see from ata-all.c
which harm this could cause.

Regards
Adi

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Kevin Oberman]

> Sender: [EMAIL PROTECTED]
> From: Alexander Pohoyda <[EMAIL PROTECTED]>
> Date: 27 Jan 2003 22:13:40 +0100
> 
> "Kevin Oberman" <[EMAIL PROTECTED]> writes:
> 
> > I am getting LORs on my ThinkPad 600e running current of 1/24. I don't
> > know if these have been previously reported, so I thought I'd send
> > them in.
> > 
> > lock order reversal
> >  1st 0xc20193f8 process lock (process lock) @ 
>/scratch/src/sys/kern/kern_descrip.c:2104
> >  2nd 0xc1ff7934 filedesc structure (filedesc structure) @ 
>/scratch/src/sys/kern/kern_descrip.c:2111
> 
> I am getting same messages on every start. IBM ThinkPad 600, 5.0-CURRENT.
> 
> 
> > lock order reversal
> >  1st 0xc1f4a040 pcm0 (sound softc) @ /scratch/src/sys/dev/sound/isa/mss.c:177
> >  2nd 0xc1f4a680 pcm0:play:0 (pcm channel) @ 
>/scratch/src/sys/dev/sound/pcm/channel.c:441
> 
> I'd wish to have sound working.. 
> On my second notebook (TP600E) I have a PCI sound card -- 0x1013 0x6001. Don't you?

The sound on the 600E is weird. It connect to both PCI and ISA for
different functions. As a result, I have to edit /sys/conf/files to
delete the csa pcm entry and add csa to the csapcm line.

dev/sound/pci/csa.c optional csa pci
#dev/sound/pci/csa.coptional pcm pci
dev/sound/pci/csamidi.c optional midi csa
dev/sound/pci/csapcm.c  optional csa pcm pci

One line is commented out and the final one is modified.

That's all it took to get sound to work on my 600E.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: xl thinkpad 600x watchdog timeout

[Sergey A. Osokin]

On Mon, Jan 27, 2003 at 10:18:48PM +0100, Toni Schmidbauer wrote:
> hi,
> 
> got no useful response from -mobile so re-posting to -current:
> 
> i am having problems with 5.0-REL on an ibm thinkpad 600x.the xl
> driver for my 3com 3ccfe575ct writes the following message to the
> console "xl0: watchdog timeout".
> 
> after skimming through newsgroups i found out that it has
> something to the with irq mapping. the cardbus controller uses
> irq11. my first try was to disable the usb-controller because it
> uses irq11 too. no luck!
>  
> a boot -v shows me that a hole bunch of pci devices uses irq11...
>  
> the problem is that the network connection is _very_ slow. i
> think its because of the irq conflict. had anyone the same
> problems before?
>  
> i also tried a different card (3com 3cxfe575bt) - same effect.
>  
> removing the card from the pcmcia slot prompts:
> "xl0: command never completed!" and
> "xl0: reset didn't complete"
> 
> find attached:
>   - pciconf -v -l
>   - boot -v with usb
>   - boot -v w/o usb
> 
> thanks for any help

Try to add hw.pci.allow_unsupported_io_range="1" in your
/boot/loader.conf.local and reboot your machine.

-- 

Rgdz,/"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,   \ /AGAINST HTML MAIL
http://ozz.pp.ru/ X  AND NEWS
 / \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: panic in fork() on SMP 5.0-RELEASE

[John Baldwin]

On 27-Jan-2003 Morten Rodal wrote:
> On Mon, Jan 27, 2003 at 03:27:00PM -0500, John Baldwin wrote:
>> Do you still have the kernel.debug from this kernel lying around?
>> Can you pop gdb up on it and do 'l *0xc01bdb48' please?  That is
>> the instruction pointer from the fault and will give the line that
>> the actual panic occurred at.
>> 
> 
> (kgdb) l *0xc01bdb48
> 0xc01bdb48 is in fork1 (/usr/src/sys/kern/kern_fork.c:388).
> 383  */
> 384 p2 = LIST_FIRST(&allproc);
> 385 again:
> 386 for (; p2 != NULL; p2 = LIST_NEXT(p2, p_list)) {
> 387 PROC_LOCK(p2);
> 388 while (p2->p_pid == trypid ||
> 389 p2->p_pgrp->pg_id == trypid ||
> 390 p2->p_session->s_sid == trypid) {
> 391 trypid++;
> 392 if (trypid >= pidchecked) {

Well, that's gross.  I have no idea how that could happen.  Somehow
p2 is NULL.  But we shouldn't even be in the loop if p2 is NULL.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: kernel build core dump

[Kris Kennaway]

On Mon, Jan 27, 2003 at 03:18:51PM +0300, Odhiambo Washington wrote:

> rm -f /usr/src/sys/modules/ip_mroute_mod/export_syms ip_mroute.ko ip_mroute.kld 
>ip_mroute.o @ machine symb.tmp tmp.o opt_mac.h opt_mrouting.h opt_random_ip_id.h
> Illegal instruction (core dumped)
> *** Error code 132

Can you isolate what command contains the illegal instruction, and
better yet, what the instruction is?  The most likely cause is that
you compiled a binary with incorrect CPUFLAGS.

Kris



msg51037/pgp0.pgp
Description: PGP signature

Re: add ext2fs to the module list in modules/Makefile

[Steve Kargl]

On Mon, Jan 27, 2003 at 11:14:41PM +0200, Enache Adrian wrote:
> please add ext2fs to the modules list in src/sys/modules/Makefile.
> 
> my /usr/src tree resides on an ext2fs partition and the fact that
> ext2fs.ko isn't built causes me trouble when making installworld
> just after rebooting the new kernel.
> 

Portions of the ext2fs source are covered by the GPL.  You
need to rebuild the kernel with "option EXT2FS".  The
FreeBSD cannot create a ext2fs.ko and comply with the GPL.

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: follow up on acpi issue

[Peter Hessler]

I have viapm, smb, and acpi enabled on my system, and console is
not gone.  It works just fine.  I can [ctrl-alt]-F[1-8] as normal
and xdm works just fine.  I can get a dmesg and kernel config if
people want it.

On Mon, Jan 27, 2003 at 12:36:18PM -0800, Nate Lawson wrote:
: On Sat, 25 Jan 2003, Bryan Liesner wrote:
: > Thanks, Nate.  When you suggested that I remove the apm stuff fron the
: > kernel, you meant ALL of the apm stuff, didn't you :) .  I took a
: > second look and found I still had viapm and its requirements still in
: > the config file.  The system boots fine now with acpi.
: > 
: > By the way, the system didn't hang as I claimed in my earlier mail.  I
: > was able to telnet in...  Having acpi and viapm had the side effect of
: > making the console go away.
: 
: viapm is VIA power management, not an apm system.  It's interesting that
: it made your console go away.  I'm sending this back to -current to see if
: anyone has ideas what might be wrong with viapm.
: 
: -Nate
: 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problem with X

[Alexander Pohoyda]

Charlie ROOT <[EMAIL PROTECTED]> writes:

> root, nor a regular user. Is this a font path problem?

No, it is not.


> /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol
> "__thr_jtable"

This is a problem. Version numbers are OK, though.


-- 
Alexander Pohoyda
<[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: LOR on current as of last Friday

[Alexander Pohoyda]

"Kevin Oberman" <[EMAIL PROTECTED]> writes:

> I am getting LORs on my ThinkPad 600e running current of 1/24. I don't
> know if these have been previously reported, so I thought I'd send
> them in.
> 
> lock order reversal
>  1st 0xc20193f8 process lock (process lock) @ 
>/scratch/src/sys/kern/kern_descrip.c:2104
>  2nd 0xc1ff7934 filedesc structure (filedesc structure) @ 
>/scratch/src/sys/kern/kern_descrip.c:2111

I am getting same messages on every start. IBM ThinkPad 600, 5.0-CURRENT.


> lock order reversal
>  1st 0xc1f4a040 pcm0 (sound softc) @ /scratch/src/sys/dev/sound/isa/mss.c:177
>  2nd 0xc1f4a680 pcm0:play:0 (pcm channel) @ 
>/scratch/src/sys/dev/sound/pcm/channel.c:441

I'd wish to have sound working.. 
On my second notebook (TP600E) I have a PCI sound card -- 0x1013 0x6001. Don't you?


-- 
Alexander Pohoyda
<[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

xl thinkpad 600x watchdog timeout

[Toni Schmidbauer]

hi,

got no useful response from -mobile so re-posting to -current:

i am having problems with 5.0-REL on an ibm thinkpad 600x.the xl
driver for my 3com 3ccfe575ct writes the following message to the
console "xl0: watchdog timeout".

after skimming through newsgroups i found out that it has
something to the with irq mapping. the cardbus controller uses
irq11. my first try was to disable the usb-controller because it
uses irq11 too. no luck!
 
a boot -v shows me that a hole bunch of pci devices uses irq11...
 
the problem is that the network connection is _very_ slow. i
think its because of the irq conflict. had anyone the same
problems before?
 
i also tried a different card (3com 3cxfe575bt) - same effect.
 
removing the card from the pcmcia slot prompts:
"xl0: command never completed!" and
"xl0: reset didn't complete"

find attached:
  - pciconf -v -l
  - boot -v with usb
  - boot -v w/o usb

thanks for any help

toni
-- 
Terror ist der Krieg der Armen,   | [EMAIL PROTECTED]
Krieg ist der Terror der Reichen. | Toni Schmidbauer
- Sir Peter Ustinov   |

agp0@pci0:0:0:  class=0x06 card=0x chip=0x71908086 rev=0x03 hdr=0x00
vendor   = 'Intel Corporation'
device   = '82443BX/ZX 440BX/ZX CPU to PCI Bridge (AGP Implemented)'
class= bridge
subclass = HOST-PCI
pcib1@pci0:1:0: class=0x060400 card=0x chip=0x71918086 rev=0x03 hdr=0x01
vendor   = 'Intel Corporation'
device   = '82443BX/ZX 440BX/ZX AGPset PCI-to-PCI bridge'
class= bridge
subclass = PCI-PCI
cbb0@pci0:2:0:  class=0x060700 card=0x01301014 chip=0xac1b104c rev=0x03 hdr=0x02
vendor   = 'Texas Instruments (TI)'
device   = 'PCI1450 PC card CardBus Controller'
class= bridge
subclass = PCI-CardBus
cbb1@pci0:2:1:  class=0x060700 card=0x01301014 chip=0xac1b104c rev=0x03 hdr=0x02
vendor   = 'Texas Instruments (TI)'
device   = 'PCI1450 PC card CardBus Controller'
class= bridge
subclass = PCI-CardBus
none0@pci0:3:0: class=0x078000 card=0x018c1014 chip=0x044911c1 rev=0x01 hdr=0x00
vendor   = 'Lucent/Agere Systems (Was: AT&T MicroElectronics)'
device   = 'LT Winmodem 56k'
class= simple comms
none1@pci0:6:0: class=0x040100 card=0x01531014 chip=0x60031013 rev=0x01 hdr=0x00
vendor   = 'Cirrus Logic'
device   = 'Crystal CS4610/14/22/24/30 SoundFusion PCI Audio Accelerator'
class= multimedia
subclass = audio
isab0@pci0:7:0: class=0x068000 card=0x chip=0x71108086 rev=0x02 hdr=0x00
vendor   = 'Intel Corporation'
device   = '82371AB/EB/MB PIIX4/4E/4M ISA Bridge'
class= bridge
subclass = PCI-unknown
atapci0@pci0:7:1:   class=0x010180 card=0x chip=0x71118086 rev=0x01 
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82371AB/EB/MB PIIX4/4E/4M IDE Controller'
class= mass storage
subclass = ATA
none2@pci0:7:2: class=0x0c0300 card=0x chip=0x71128086 rev=0x01 hdr=0x00
vendor   = 'Intel Corporation'
device   = '82371AB/EB/MB PIIX4/4E/4M USB Interface'
class= serial bus
subclass = USB
none3@pci0:7:3: class=0x068000 card=0x chip=0x71138086 rev=0x03 hdr=0x00
vendor   = 'Intel Corporation'
device   = '82371AB/EB/MB PIIX4/4E/4M Power Management Controller'
class= bridge
subclass = PCI-unknown
none4@pci1:0:0: class=0x03 card=0x01521014 chip=0x000610c8 rev=0x00 hdr=0x00
vendor   = 'Neomagic Corporation'
device   = 'NM2360 MagicMedia 256ZX / 256M6D'
class= display
subclass = VGA

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-RELEASE #1: Thu Jan 23 13:35:57 GMT 2003
root@castrop:/usr/obj/usr/src/sys/wasnix
Preloaded elf kernel "/boot/kernel/kernel" at 0xc04c9000.
Calibrating clock(s) ... TSC clock: 498275308 Hz, i8254 clock: 1193192 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
TSC initialization skipped: APM enabled.
CPU: Pentium III/Pentium III Xeon/Celeron (498.27-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x681  Stepping = 1
  
Features=0x383f9ff
real memory  = 134021120 (127 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x004f - 0x07fc7fff, 128811008 bytes (31448 pages)
avail memory = 125018112 (119 MB)
bios32: Found BIOS32 Service Directory header at 0xc00fd800
bios32: Entry = 0xfd820 (c00fd820)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xfd880+0x0
pnpbios: Found PnP BIOS data at 0xc00fe700
pnpbios: Entry = f:e724  Rev = 1.0
pnpbios: Event flag at 415
Other BIOS signatures found:
Initializing GEOMetry subsystem
null: 
random: 
mem: 
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
pci_open(1):mode 1 addr port (0

VOP_STRATEGY on VCHR

[Enache Adrian]

I get this when I try to access for the first time a file on an ext2fs
filesystem.

VOP_STRATEGY on VCHR
: 0xc1c23000: tag devfs, type VCHR, usecount 2, writecount 0, refcount 3,
backtrace(c02fe7bd,c1c23000,0,c87eb938,c0166ed8) at backtrace+0x8
spec_strategy(c87eb960,c87eb97c,c1c4163b,c87eb960,0) at spec_strategy+0x2d
spec_vnoperate(c87eb960,0,c87eb95c,0,0) at spec_vnoperate+0x18
ext2_strategy(c87eb9c8,0,0,1000,0) at ext2_strategy+0x8b
breadn(c1c22e6c,0,0,1000,0) at breadn+0x126
bread(c1c22e6c,0,0,1000,0) at bread+0x4c
ext2_read(c87ebaf0,c0328a20,0,0,0) at ext2_read+0x293
ext2_readdir(c87ebc98,20002,c0b9a1e0,0,c1c22e6c) at ext2_readdir+0x130
getdirentries(c0b9a1e0,c87ebd14,c03195a7,407,4) at getdirentries+0x128
syscall(2f,2f,2f,80d1000,80d1040) at syscall+0x271
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (196), eip = 0x808cf1f, esp = 0xbfbff1bc, ebp = 0xbfbff1d8 ---

Is that anything serious or just noise ?

(this is -CURRENT from yesterday)
Regards
Adi

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

add ext2fs to the module list in modules/Makefile

[Enache Adrian]

please add ext2fs to the modules list in src/sys/modules/Makefile.

my /usr/src tree resides on an ext2fs partition and the fact that
ext2fs.ko isn't built causes me trouble when making installworld
just after rebooting the new kernel.

Thanks & Regards
Adi

--- /arc/freebsd/src/sys/modules/Makefile   2003-01-22 01:31:50.0 +0200
+++ sys/modules/Makefile2003-01-27 21:36:45.0 +0200
@@ -34,6 +34,7 @@
de \
digi \
dummynet \
+   ext2fs \
fdc \
fdescfs \
firewire \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: panic in fork() on SMP 5.0-RELEASE

[Morten Rodal]

On Mon, Jan 27, 2003 at 03:27:00PM -0500, John Baldwin wrote:
> Do you still have the kernel.debug from this kernel lying around?
> Can you pop gdb up on it and do 'l *0xc01bdb48' please?  That is
> the instruction pointer from the fault and will give the line that
> the actual panic occurred at.
> 

(kgdb) l *0xc01bdb48
0xc01bdb48 is in fork1 (/usr/src/sys/kern/kern_fork.c:388).
383  */
384 p2 = LIST_FIRST(&allproc);
385 again:
386 for (; p2 != NULL; p2 = LIST_NEXT(p2, p_list)) {
387 PROC_LOCK(p2);
388 while (p2->p_pid == trypid ||
389 p2->p_pgrp->pg_id == trypid ||
390 p2->p_session->s_sid == trypid) {
391 trypid++;
392 if (trypid >= pidchecked) {

-- 
Morten Rodal




msg51029/pgp0.pgp
Description: PGP signature

Re: follow up on acpi issue

[Nate Lawson]

On Sat, 25 Jan 2003, Bryan Liesner wrote:
> Thanks, Nate.  When you suggested that I remove the apm stuff fron the
> kernel, you meant ALL of the apm stuff, didn't you :) .  I took a
> second look and found I still had viapm and its requirements still in
> the config file.  The system boots fine now with acpi.
> 
> By the way, the system didn't hang as I claimed in my earlier mail.  I
> was able to telnet in...  Having acpi and viapm had the side effect of
> making the console go away.

viapm is VIA power management, not an apm system.  It's interesting that
it made your console go away.  I'm sending this back to -current to see if
anyone has ideas what might be wrong with viapm.

-Nate


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: (FWD) cvs commit: src/sys/alpha/alpha trap.c vm_machdep.c sr

[John Baldwin]

On 27-Jan-2003 Julian Elischer wrote:
> 
> 
> On Sun, 26 Jan 2003, David O'Brien wrote:
> 
>> On Sun, Jan 26, 2003 at 04:05:31PM -0800, Julian Elischer wrote:
>> > 
>> > or simply check out the newer sources.
>> 
>> Looking at the commit you made, it doesn't seem to address the other
>> issues of the commit this thread is trying to avoid.
>> 
>> I guess you're not going to honor mine and others request for a full
>> backout of the commit pending farther review and testing?
> 
> 
> 
> firstly, I have seen no requests for backout (and even if I had, it
> wouldn't concern me because it wasn't my commit in the first place), and
> secondly, I have seen no tinderbox failures (becasue I don't seem to be
> getting the mails these days) so my commit was purely from code
> inspection. I have seen no firsthand complaints of problems and have
> only responded to look for problems because I heard via robert that
> there were rumours of failures on secontary architecures.
> 
> If anyone has a real problem they might make it easier by emailing me
> with them so I have a clue what is going on. 
> 
> As for the testing, the code in question is 99.5% in KSE specific code
> and THAT has been tested pretty thoroughly. A backout is David's
> decision but My personal thought is that it would be a retrograde move.
> 
> What we need is to see the problems. I haven't seen a single firsthand
> report of any problem yet. I think the mail system at FreeBSD.org
> may have had a flaky morning..
> How about sending me a mail saying what the problem is and then we might
> be making some forward progress..

What we need is for people making commits to the kernel to test
them.  If your e-mail doesn't work, then don't commit code. I
realize you didn't commit this patch, but your mentee did.  As a
mentor you are responsible for what he commits and you are
supposed to make sure the code is tested, etc.  KSE is not some
poky little device driver, so you need to do more testing with
the KSE work than you do when working on other things in the
kernel.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: where is MAKEDEV

[John Baldwin]

On 27-Jan-2003 FredBriand wrote:
> Hi,
> 
> I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now
> everything seems OK, but my sound card. In the handbook they say I must
> use the MAKEDEV script (as in Linux) but I can't find it on my disk.
> I tried to download it with the sysinstall tool but again there seems to
> be no package available.
> 
> What can I do?
> 
> Please help. fred.

If you have installed 5.0, then you are using devfs which means that
you don't need MAKEDEV.  Devices appear in /dev automatically.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: panic in fork() on SMP 5.0-RELEASE

[John Baldwin]

On 25-Jan-2003 Morten Rodal wrote:
> Is this a known panic?  I tried to search the mailinglist archives to
> see if somebody had posted something similar, but I couldn't find
> anything.
> 
> The system is running 5.0-RELEASE with a pretty standard kernel (just
> removed all the drivers I don't use and added SMP support).  I think
> the load of the system might have been high at the moment as I had
> just started
> 
> 
>   cd /usr/ports && make -j8 clean
> 
> before I went to eat dinner.  When I came back a few hours later it at
> rebooted, with this panic.
> 
> I have attached the backtrace of this (dual?) panic.  I have never
> poked in the kernel source code before, so if there is anything else
> you need to know just ask and I'll see what I can do.

Do you still have the kernel.debug from this kernel lying around?
Can you pop gdb up on it and do 'l *0xc01bdb48' please?  That is
the instruction pointer from the fault and will give the line that
the actual panic occurred at.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: panic in fork() on SMP 5.0-RELEASE

[John Baldwin]

On 25-Jan-2003 Nate Lawson wrote:
> On Sat, 25 Jan 2003, Morten Rodal wrote:
>> The system is running 5.0-RELEASE with a pretty standard kernel (just
>> removed all the drivers I don't use and added SMP support).  I think
>> the load of the system might have been high at the moment as I had
>> just started
>> 
>>   cd /usr/ports && make -j8 clean
> 
> The problem is uap is invalid in this frame:
>#15 0xc01bd2f0 in fork (td=0xc5144000, uap=0xe3ac4d10) at
> /usr/src/sys/kern/kern_fork.c:124
> 
> The question is, why?  I suspect something to do with memory due to the
> second two bytes being a valid kernel address.  How about a dmesg?

Eh?  0xefoo is a valid address, it's just not text, it's a stack
address.  Also, the last two bytes are '4d10' which would be the
start of a user address.  The 'c' is the low nibble in the 'ac' byte.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: where is MAKEDEV

[Toni Schmidbauer]

On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote:
> everything seems OK, but my sound card. In the handbook they say I must
> use the MAKEDEV script (as in Linux) but I can't find it on my disk.

freebsd 5.0 is using devfs(5). so device inodes are created
automatically. 

for your soundcard be sure to enable pcm(4) in your kernel.

for info on compiling a new kernel see the freebsd handbook:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html

toni
-- 
Terror ist der Krieg der Armen,   | [EMAIL PROTECTED]
Krieg ist der Terror der Reichen. | Toni Schmidbauer
- Sir Peter Ustinov   |



msg51023/pgp0.pgp
Description: PGP signature

Re: where is MAKEDEV

[Wilko Bulte]

On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote:
> Hi,
> 
> I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now
> everything seems OK, but my sound card. In the handbook they say I must
> use the MAKEDEV script (as in Linux) but I can't find it on my disk.
> I tried to download it with the sysinstall tool but again there seems to
> be no package available.
> 
> What can I do?

Read the docs/mailing list archives? ;-)

Kidding aside: -current uses devfs, which makes MAKEDEV obsolete. 

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

where is MAKEDEV

[FredBriand]

Hi,

I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now
everything seems OK, but my sound card. In the handbook they say I must
use the MAKEDEV script (as in Linux) but I can't find it on my disk.
I tried to download it with the sysinstall tool but again there seems to
be no package available.

What can I do?

Please help. fred.





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Does bg fsck have problems with large filesystems?

[Gerrit Kühn]

Hi all,

I've just installed my first 5.0-rel system and did some
"torture-testing". When resetting the machine to test the backgrounded
fsck I experienced the following problem:
All filesystems came back quickly and bg fsck worked fine, except for
one. I had created a large (>50GB) /export filesystem on with fsck
reproducively hang. I also couldn't reboot the system cleanly anymore,
because of those fsck processes not going away.
Finally, I commented out /export from /etc/fstab and run fsck manually
in fg mode after the rest of the system had been checked cleanly.
There were a few errors, and after that the check finished and marked
the system as clean. However, mounting the clean system took several
seconds and gave me this message from the kernel:
FFS_SNAPSHOT_MOUNT: old format snapshot inode 4
Well, whatever... :)

Nevertheless everything is working fine now, again. I havn't checked
yet, but will this happen every time my systems reboots without
unmounting the filesystems cleanly? Is anything wrong with filesystems
that large, or could I have done anything else that causes this strange
behaviour?


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: hw.acpi.disable_on_poweroff

[Mathew Kanner]

On Jan 27, Scott Sipe wrote:
> 
> This defaulted to 1 ony my Current--is there a reason for this?  I like
> being able to press the power putton and have it shutdown properly, or have
> shutdown -p power down.

Hello Scott,
When it's 0, it's prevents some rogue machines from
mysteriously turning on a few minutes after power off, like my bp6
motherboard.

--Mat
-- 
Brain: Are you pondering what I'm pondering?
Pinky: Wuh, I think so, Brain, but wouldn't anything lose its flavor
on the bedpost overnight?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

LOR on current as of last Friday

[Kevin Oberman]

I am getting LORs on my ThinkPad 600e running current of 1/24. I don't
know if these have been previously reported, so I thought I'd send
them in.

lock order reversal
 1st 0xc20193f8 process lock (process lock) @ /scratch/src/sys/kern/kern_descrip.c:2104
 2nd 0xc1ff7934 filedesc structure (filedesc structure) @ 
/scratch/src/sys/kern/kern_descrip.c:2111
lock order reversal
 1st 0xc1f4a040 pcm0 (sound softc) @ /scratch/src/sys/dev/sound/isa/mss.c:177
 2nd 0xc1f4a680 pcm0:play:0 (pcm channel) @ 
/scratch/src/sys/dev/sound/pcm/channel.c:441

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

problem with X

[Charlie ROOT]

I'm getting the following error when I try and start X. I just built 5.0
and had x working untill I portupgraded gnome2. I have rebuilt wrapper,
and freetype2. I have also re-run xf86config. No one can start x, not
root, nor a regular user. Is this a font path problem? if so what should I
try?

Thanks Kirk

error message:

lorax# xinit


XFree86 Version 4.2.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: FreeBSD 4.7-STABLE i386 [ELF]
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jan 27 11:41:17 2003
(==) Using config file: "/etc/X11/XF86Config"
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/,
removing from
 list!
/usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol
"__thr_jtable"

waiting for X server to shut down



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: openpam error from sshd

[Dag-Erling Smorgrav]

Kris Kennaway <[EMAIL PROTECTED]> writes:
> I've just updated bento to 5.0, and sshd is now giving the following
> error every few seconds:
>
>  bento sshd[55737]: in _openpam_check_error_code():
> pam_sm_setcred(): unexpected return value 24
>
> Peter says he's seen this elsewhere on the cluster.  What's going on?

*grumble* it's a bug in one of our PAM modules (krb5, I think), which
I never got around to fixing it because it isn't really important.
Error 24 is PAM_NO_MODULE_DATA, which isn't an allowed return value
for pam_setcred() according to the XSSO, but nobody really cares
because anything else than PAM_SUCCESS is an error, so the bug doesn't
have any adverse effect other than making OpenPAM bitch so I remember
to fix it :)

Workaround until I fix the module: in src/lib/libpam/libpam/Makefile,
add

CFLAGS  += -DOPENPAM_RELAX_CHECKS

somewhere around the other CFLAGS stuff, then make clean && make &&
make install.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

panic: ip_output: no HDR

[Maksim Yevmenkin]

Dear Hackers,

During the testing process for the new in-kernel RFCOMM Bluetooth
code my not so -current panic()ed with the trace below. This panic
happend while ~2MB FTP transfer (PPP over new RFCOMM over
Bluetooth).

A little detail - new RFCOMM code opens L2CAP sockets from inside
kernel (very much like ng_ksocket(4) does) and then provides another
socket layer (SOCK_STREAM) on top of it.

Of course i suspect my own code and will continue to look for the
problem, but may be someone can give a clue here.

thanks,
max

beetle# gdb -k /sys/i386/compile/BEETLE/kernel.debug /var/crash/vmcore.23
GNU gdb 5.2.1 (FreeBSD)
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 it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: from debugger
panic messages:
---
panic: ip_output: no HDR
panic: from debugger
Uptime: 5m33s
pfs_vncache_unload(): 1 entries remaining
/dev/vmmon: Module vmmon: unloaded
Dumping 191 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112 128 144 160 176
---
#0  doadump () at ../../../kern/kern_shutdown.c:232
232 dumping++;
(kgdb) where
#0  doadump () at ../../../kern/kern_shutdown.c:232
#1  0xc01a51be in boot (howto=260) at ../../../kern/kern_shutdown.c:364
#2  0xc01a5403 in panic () at ../../../kern/kern_shutdown.c:517
#3  0xc0126a32 in db_panic () at ../../../ddb/db_command.c:450
#4  0xc01269b2 in db_command (last_cmdp=0xc0319a60, cmd_table=0x0,
   aux_cmd_tablep=0xc031422c, aux_cmd_tablep_end=0xc0314230)
   at ../../../ddb/db_command.c:346
#5  0xc0126ac6 in db_command_loop () at ../../../ddb/db_command.c:472
#6  0xc012975a in db_trap (type=3, code=0) at ../../../ddb/db_trap.c:72
#7  0xc02ba9a2 in kdb_trap (type=3, code=0, regs=0xcaeb79ec)
   at ../../../i386/i386/db_interface.c:166
#8  0xc02cbb9f in trap (frame=
 {tf_fs = -1047265256, tf_es = -1070268400, tf_ds = -890568688, 
tf_edi = -1048077696, tf_esi = 256, tf_ebp = -890537416, tf_isp = 
-890537448, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 18, tf_trapno = 
3, tf_err = 0, tf_eip = -1070879676, tf_cs = 8, tf_eflags = 646, tf_esp 
= -1070534461, tf_ss = -1070642966})
   at ../../../i386/i386/trap.c:603
#9  0xc02bc178 in calltrap () at {standard input}:98
#10 0xc01a53eb in panic (fmt=0x0) at ../../../kern/kern_shutdown.c:503
#11 0xc021dc89 in ip_output (m0=0xc0d48c00, opt=0x0, ro=0xc1d384f4, 
flags=0,
   imo=0x0, inp=0xc1d384b8) at ../../../netinet/ip_output.c:195
#12 0xc0224544 in tcp_output (tp=0xc1d385b8)
   at ../../../netinet/tcp_output.c:916
#13 0xc0228c2e in tcp_usr_send (so=0xc1979500, flags=0, m=0xc0d48d00, 
nam=0x0,
   control=0x0, td=0xc1879a80) at ../../../netinet/tcp_usrreq.c:719
#14 0xc01e5589 in do_sendfile (td=0xc1879a80, uap=0xcaeb7d10, compat=0)
   at ../../../kern/uipc_syscalls.c:2000
#15 0xc01e4c60 in sendfile (td=0x0, uap=0x0)
   at ../../../kern/uipc_syscalls.c:1690
#16 0xc02cc49e in syscall (frame=
 {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 672807192, tf_esi = 
0, tf_ebp = -1077940824, tf_isp = -890536588, tf_ebx = 2806026, tf_edx = 
0, tf_ecx = 134571553, tf_eax = 393, tf_trapno = 0, tf_err = 2, tf_eip = 
672254899, tf_cs = 31, tf_eflags = 518, tf_esp = -1077940916, tf_ss = 47})
   at ../../../i386/i386/trap.c:1033
#17 0xc02bc1cd in Xint0x80_syscall () at {standard input}:140
---Can't read userspace from dump, or kernel process---

(kgdb)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Opening /dev/tty in session leader after controlling terminal is revoked causes panic.

[phk]

In message <[EMAIL PROTECTED]>, "Peter Edwards" writes:

>> >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process
>> >has its P_CONTROLT flag set, then it's session has a valid vnode for it's
>> >controlling terminal. This doesn't hold if the terminal was revoked.

>Yes, this patch also fixes the problem.

OK, committed!

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Opening /dev/tty in session leader after controlling terminal is revoked causes panic.

[Peter Edwards]

[EMAIL PROTECTED] wrote:

> 
> In message <[EMAIL PROTECTED]>, "Peter Edwards" writes:
> 
> >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process
> >has its P_CONTROLT flag set, then it's session has a valid vnode for it's
> >controlling terminal. This doesn't hold if the terminal was revoked.
> 
> Can you try this patch ?

[snip patch]

Yes, this patch also fixes the problem.
-- 
Peter Edwards.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Martin Blapp]

Hi,

> s->c MOUNT V1 EXPORT Reply (duplicate)

I suspect timeouts or packet loss cause this together with
the new nonblock code change.

I just tried V2 (mountd -2) and amd with -2 option. The
bug does not appear.

If possible I'd like to reproduce packet loss with dummynet,
has anyone the necessary commands at hand ?

Martin

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

MySQL 3.23.55 patch-an

[Antal Rutz]

The correct files/patch-an for the port mysql 3.23.55:

--- Makefile.in.origThu Dec  5 10:37:22 2002
+++ Makefile.in Sat Dec 14 16:24:26 2002
@@ -195,10 +195,11 @@
 EXTRA_DIST = INSTALL-SOURCE README \
COPYING COPYING.LIB MIRRORS

-SUBDIRS = . include @docs_dirs@ @readline_dir@ \
-   @thread_dirs@ @sql_client_dirs@ \
-   @sql_server_dirs@ scripts tests man \
-   @bench_dirs@ support-files os2
+.if defined(CLIENT_ONLY)
+SUBDIRS = include @readline_dir@ @sql_client_dirs@ tests man
+.else
+SUBDIRS = include @thread_dirs@ @docs_dirs@ @sql_server_dirs@ scripts support-files
+.endif


-- 
 
 
--rutz

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

kernel build core dump

[Odhiambo Washington]

===> if_tap
rm -f opt_devfs.h opt_inet.h vnode_if.h /usr/src/sys/modules/if_tap/export_syms 
if_tap.ko if_tap.kld if_tap.o @ machine symb.tmp tmp.o opt_inet.h vnode_if.h
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> if_tun
rm -f /usr/src/sys/modules/if_tun/export_syms if_tun.ko if_tun.kld if_tun.o @ machine 
symb.tmp tmp.o opt_inet.h opt_mac.h vnode_if.h
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> if_vlan
rm -f /usr/src/sys/modules/if_vlan/export_syms if_vlan.ko if_vlan.kld if_vlan.o @ 
machine symb.tmp tmp.o opt_inet.h
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> ip6fw
rm -f /usr/src/sys/modules/ip6fw/export_syms ip6fw.ko ip6fw.kld ip6_fw.o @ machine 
symb.tmp tmp.o
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> ip_mroute_mod
rm -f /usr/src/sys/modules/ip_mroute_mod/export_syms ip_mroute.ko ip_mroute.kld 
ip_mroute.o @ machine symb.tmp tmp.o opt_mac.h opt_mrouting.h opt_random_ip_id.h
Illegal instruction (core dumped)
*** Error code 132

Stop in /usr/src/sys/modules/ip_mroute_mod.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/Kern5.x.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

typo in UPDATING

[Vitaly Markitantov]

Seems like it's typo in src/UPDATING about acpi disabling.
Can somebody fix it?


--- UPDATING.orig   Mon Jan 27 14:14:12 2003
+++ UPDATINGMon Jan 27 14:07:50 2003
@@ -290,7 +290,7 @@
 20010927:
Some weird problems result from using ACPI on some machines.
To disable ACPI you can add
-   hint.acpi.0.disable="1"
+   hint.acpi.0.disabled="1"
to /boot/loader.conf (or by putting set X=Y at the boot
loader "ok" prompt).


-- 
 Vitaly Markitantov mailto: [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: I've just had a massive file system crash

[David Schultz]

Thus spake Greg Lehey <[EMAIL PROTECTED]>:
> I've been thinking about what happened, and I have a possibility: the
> session before shutdown included a lot of writing to that file system,
> and I did a shutdown -p.  It's possible that the shutdown powered off
> the system before the disk had flushed its cache.  For the moment I'm
> avoiding shutdown -p, but when I get home I'll try to provoke it
> again.

Just a heads up: Soeren tells me he will commit a fix for this in
his next ATA meta-commit.  I have patches if wanted.

I still can't figure out why the problem would trash your entire
home directory, though.  Even if the disk reordered writes and
failed to write some sectors, directory entries that were not
being actively modified shouldn't have become corrupted, as far as
I know.  (Maybe your disk does track-at-once writes and just
happened to be flushing the last few sectors from its cache when
the power was cut.)  Perhaps someone could ask Kirk, although it
may take an actual hosed filesystem to diagnose what happened.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Fatal trap 12

[Franz Klammer]

Hello!

because my old (-stable) harddisk was broken (bad sectors) 
i've done the switch to -current earlier as i wanted.

now if i want to copy everything what possible from my old disk.
but when i cd into a directory or read a file which is not readable
my pc is doing this:


first i get these messages on the console:
--
Jan 27 12:10:10 ds9 kernel: ad2: hard error cmd=read fsbn 160203390 of
80101695-80101710
Jan 27 12:10:10 ds9 kernel: trying PIO mode
Jan 27 12:10:15 ds9 kernel: ad2: hard error cmd=read fsbn 160203390 of
80101695-80101710
Jan 27 12:10:15 ds9 kernel: status=59 error=40
Jan 27 12:10:20 ds9 kernel: ad2: hard error cmd=read fsbn 160203390 of
80101695-80101710
Jan 27 12:10:20 ds9 kernel: status=59 error=40
Jan 27 12:10:25 ds9 kernel: ad2: hard error cmd=read fsbn 160203390 of
80101695-80101710
Jan 27 12:10:25 ds9 kernel: status=59 error=40
Jan 27 12:10:30 ds9 kernel: ad2: hard error cmd=read fsbn 160203390 of
80101695-80101710
Jan 27 12:10:30 ds9 kernel: status=59 error=40

and then this (written by hand - hopefully i didn't forgot anything):

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x0
fault code  = supervisor write, page not present
instriction pointer = 0x8: 0xc026daed
stack pointer   = 0x10: 0xdceh08ec
frame pointer   = 0x10: 0xdce40904
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def 32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL=0
current process = 551 (mc)
trap number = 12
syncing disks, buffers remaining... panic: bdwrite: buffer is not busy
Terminate ACPI
Atomatic reboot ... (the rest i think you can imagine)


last cvsuped and build:
---
5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Jan 26 20:02:25 CET 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DS9  i386


ok! the next what i can do is do try it in PIO-mode.
but now i'm afraid to try it again before there is no
solution for this problem because it's not a test machine.

franz.


-- 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: [PATCH]: newfs(8) FS_OPTSPACE vs FS_OPTTIME bug

[David Schultz]

Thus spake Maxim Konovalov <[EMAIL PROTECTED]>:
> newfs(8) incorrectly claims that FS_OPTTIME is unavailable when
> minfree is less than MINFREE. MINFREE is defined in ufs/ffs/fs.h:
> 
> #define MINFREE  8
> 
> But relevant code in ufs/ffs/ffs_alloc.c uses hardcoded value:
> 
> 288 if (fs->fs_minfree <= 5 ||
> 289 fs->fs_cstotal.cs_nffree >
> 290 (off_t)fs->fs_dsize * fs->fs_minfree / (2 * 100))
> 291 break;
> 292 log(LOG_NOTICE, "%s: optimization changed from SPACE to TIME\n",
> 
> tunefs(8) metions 5% too.

The code you quote in ffs_alloc.c doesn't do what you think it
does.  The minfree comparison there is an exception to the rule
``if there is too much fragmentation, switch optimization from
space to time''.  The kernel must do this because the calculation
on lines 289 and 290 doesn't work very well if minfree is small.

The code in newfs works in the opposite direction: it forces
optimization from time to space if minfree is too small (<8%).
The rationale here is different: if you set minfree very low, you
must expect space to be very tight, so the filesystem should
optimize from space from the start.

So these numbers are different on purpose, because they address
separate issues.  The tunefs(8) comment you refer to seems to have
been introduced in rev. 1.2 of tunefs.8.  I revised the comment in
rev. 1.18, but even then I didn't catch the error.  I think we
need to s/of 5% and less/below the default value/.  The manpage
should also point out that the time/space optimization
restrictions based on minfree are enforced by newfs/tunefs when
minfree is changed, and not by the kernel.  They can be overridden
by subsequently asking for space or time optimization again.

Also, newfs does not match tunefs exactly in its treatment of
minfree.  Tunefs will additionally force time optimization if
minfree is >= the default.  Early comments in CVS logs seem to
indicate that tunefs's behavior was the intended one.

**OR**

Here is another idea: rip out of tunefs and newfs the magic that
forces space/time optimization.  Instead, when someone tries to
specify a small value for minfree, just warn them why they
shouldn't do that.  The one bit of minfree magic in ffs_alloc.c
stays because it's important.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: I've just had a massive file system crash

[Eugene M. Kim]

On Sun, Jan 26, 2003 at 04:08:31PM +0800, Greg Lehey wrote:
> On Sunday, 26 January 2003 at 14:24:02 +1030, Daniel O'Connor wrote:
> > On Sun, 2003-01-26 at 08:08, David Schultz wrote:
> >> Good.  I was referring to IDE in this case, because I assume
> >> that's what Greg's laptop uses.  The ATA driver flushes the cache
> >> when the device is closed, but I don't think that happens during
> >> shutdown.  It probably needs to register a shutdown hook like the
> >> SCSI driver.  Also, the driver is a bit optimistic about how long
> >> the flush will take; it times out after 5 seconds, whereas the ATA
> >> spec says a flush can take up to 30 seconds.
> >
> > I am wondering if I experienced this problem with my -stable laptop..
> >
> > I shut it down and then booted it up later to find fsck having a nice
> > good chew on the drive (deleting REAMS of files).
> 
> Did you use shutdown -p?  If my hypothesis is correct, it's possible
> to get this result with shutdown -h if you press the power switch as
> soon as the "System halted" message appears, but normally you'd give
> it a few seconds longer.  With shutdown -p, it's immediate, modulo
> delay.

Just a random idea: If that poses an issue, how about this patch?

Eugene

--- src/sys/kern_shutdown.c Sun Jan 26 14:24:56 2003
+++ src/sys/kern_shutdown.c.new Sun Jan 26 14:25:42 2003
@@ -545,7 +545,7 @@
 static void 
 poweroff_wait(void *junk, int howto)
 {
-   if(!(howto & RB_POWEROFF) || poweroff_delay <= 0)
+   if(!(howto & (RB_POWEROFF | RB_HALT)) || poweroff_delay <= 0)
return;
DELAY(poweroff_delay * 1000);
 }

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Jun Kuriyama]

At Mon, 27 Jan 2003 11:58:34 +0100 (CET),
Martin Blapp wrote:
> Can you try to cvsup on both boxes and then manually rebuild
> libc, mountd, rpcbind, nfsd.

Hmm, 5.0-RELEASE box is difficult to upgrade to HEAD.

I'll try to update my box to the latest of HEAD tomorrow.


-- 
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
 <[EMAIL PROTECTED]> // FreeBSD Project

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Martin Blapp]

Hi,

> In my environment, server is 5.0-RELEASE and client is HEAD as of Jan
> 20th.  Both have nfsd, rpc.lockd, rpc.statd and nfs client.

Just tried to reproduce it again.

I'm not able to reproduce it :-(

Can you try to cvsup on both boxes and then manually rebuild
libc, mountd, rpcbind, nfsd.

I just tired udp and tcp automounts.

Martin

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Jun Kuriyama]

At Mon, 27 Jan 2003 11:21:54 +0100 (CET),
Martin Blapp wrote:
> There seem to be definitly a problem around. Can you exactly tell
> me how you can reproduce it ?

Hmm, sorry for my little description.

> I tried it too and amd still works. I use on both servers a recent
> CURRENT and one has amd running, the other the nfsd and mountd.
> 
> tcp and udp mounts still work fine. So the trigger of this
> bug must be elsewhere ...

In my environment, server is 5.0-RELEASE and client is HEAD as of Jan
20th.  Both have nfsd, rpc.lockd, rpc.statd and nfs client.

I'll verify to find the case which is easy to reproduce.


-- 
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Martin Blapp]

Hi,

> I don't know the problem is in amd or mountd.  I fear other programs
> are broken with this commit...

Mounting nfs volumes manually works, as other services work fine.
I also tested other rpc-service and they seem to be fine. So we
have to find out why mountd replies twice.

With the committed change, mountd uses non-blocking rpc for tcp.

If I can reproduce it, I'm a bit closer to solve it.

Martin

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Martin Blapp]

Hi,

> So, problem may be in mountd.  I tested with reverting the commit at
> 2003/01/15, and it works fine.

There seem to be definitly a problem around. Can you exactly tell
me how you can reproduce it ?

I tried it too and amd still works. I use on both servers a recent
CURRENT and one has amd running, the other the nfsd and mountd.

tcp and udp mounts still work fine. So the trigger of this
bug must be elsewhere ...

Martin

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problem during alpha cross-building

[Ruslan Ermilov]

On Sun, Jan 26, 2003 at 03:15:28PM -0800, David O'Brien wrote:
> On Sat, Jan 25, 2003 at 06:50:08PM +0200, Ruslan Ermilov wrote:
> > On Fri, Jan 24, 2003 at 05:54:46PM -0800, Kris Kennaway wrote:
> > > On Fri, Jan 24, 2003 at 02:45:44PM -0800, Kris Kennaway wrote:
> > > > I'm getting this when trying to cross-build an alpha world.  Is anyone
> > > > else seeing it?
> > > > 
> > > > cc -O -pipe -DNLIST_ELF64 -static -o crunchide crunchide.o exec_elf64.o
> > > > exec_elf64.o: In function `hide_elf64':
> > > > exec_elf64.o(.text+0x30b): undefined reference to `be64toh'
> > > > exec_elf64.o(.text+0x530): undefined reference to `be64toh'
> > > > exec_elf64.o(.text+0x575): undefined reference to `be64toh'
> > > > exec_elf64.o(.text+0x59f): undefined reference to `be64toh'
> > > > exec_elf64.o(.text+0x5e6): undefined reference to `be64toh'
> > > > exec_elf64.o(.text+0x639): more undefined references to `be64toh' follow
> > > > *** Error code 1
> > > > 
> > > > Stop in /a/asami/portbuild/alpha/5/src/usr.sbin/crunch/crunchide.
> > > > *** Error code 1
> > > 
> > > I get the same problem trying to cross-build sparc64.  Looks like
> > > cross-building is broken.
> > > 
> > This is the result of David O'Brien removing part of my work
> > in the quoted commit (see attached), for no apparent reason.
> 
> I gave the reason -- "private version".  It is accepted that
> duplication on the level of the private endian.h is bad.  I made a
> change to the system endian.h and found in a manual build of usr.sbin it
> wasn't being used.  I tracked it down to the private version of endian.h.
> The exact details escape me at this time.  It appeared to me that you
> added the private endian.h because at the time of your commit there
> wasn't a system one with the needed bits.
> 
It wasn't entirely private.  If you look into it, you'll see this:

#if __FreeBSD_version >= 500034
#include 
#else
THE REST
#endif

So the "private" part of this header was only used on systems without
endianness macros in , e.g. RELENG_4 and 5.0-DP1, like
I said.

> So instead of backing out the commit, can we make the cross build work
> with the system version.  From the quoted error messages, I don't have
> enough context to know when in the cross 'make world' this is happening.
>  
Obviously, this is happening in cross-tools attempting to build crunchide.
You can reproduce it locally:

: Script started on Mon Jan 27 10:04:33 2003
: $ uname -a
: FreeBSD allmouth.sunbay.crimea.ua 4.7-STABLE FreeBSD 4.7-STABLE #59: Sun Jan  5 
:15:29:59 EET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PERL  i386
: $ pwd
: /home/ru/crunch/crunchide
: $ make TARGET_ARCH=sparc64
: Warning: Object directory not changed from original /home/ru/crunch/crunchide
: cc -O -pipe -march=pentiumpro -DNLIST_ELF64-c crunchide.c
: cc -O -pipe -march=pentiumpro -DNLIST_ELF64 -o crunchide crunchide.o 
:exec_elf64.o 
: exec_elf64.o: In function `hide_elf64':
: exec_elf64.o(.text+0x317): undefined reference to `be64toh'
: exec_elf64.o(.text+0x544): undefined reference to `be64toh'
: exec_elf64.o(.text+0x589): undefined reference to `be64toh'
: exec_elf64.o(.text+0x5b3): undefined reference to `be64toh'
: exec_elf64.o(.text+0x5fa): undefined reference to `be64toh'
: exec_elf64.o(.text+0x64d): more undefined references to `be64toh' follow
: *** Error code 1
: 
: Stop in /home/ru/crunch/crunchide.
: Script done on Mon Jan 27 10:04:45 2003

> > The "private version" of endian.h was smart enough to pick up
> > the system  if the latter was fresh enough to
> > have the necessary macros; now it tries to use 
> > unconditionally, and fails on systems without be32toh() etc.
> > macros in their , e.g. RELENG_4 or 5.0-DP1.
> 
> What are all the cases that things fail now?  It looks like you're saying
> (1) doing an Alpha cross-world -CURRENT build on i386, (2) doing a 'make
> buildworld' on -CURRENT sources on a 5.0-DP1 install, (3) doing an
> upgrade from RELENG_4 to HEAD.  Is that correct?
> 
Upgrades from i386 RELENG_4 to i386 HEAD are unaffected, because
 in RELENG_4 has partial (but incomplete, see below)
support for endianness macros, but only for little endian machines,
so if you attempt to upgrade to big endian (sparc64), it is broken.
Even if you attempt to upgrade to little endian but 64bit (alpha),
it is broken, because RELENG_4  misses the be64*()
macros.

As for 5.0-DP1, the upgrades to 5.0-RELEASE are now broken with
this change, because there's no  in DP1.  Too bad,
I worked really hard on making upgrades to 5.0-RELEASE as painless
as they could be, and I didn't notice this your change in time.

> Perhaps we need the current-compat.h header we've talked about many times
> that we can "cc -include {TOP}/tools/current-compat.h" during the 1st
> stage of 'make buildworld'
> 
I think we need to restore the lost functionality first.  :-)

This current-compat.h header would presumably be a "union" of
all headers that have __FreeBSD_version stuff in them.  Using
this header in a st

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanicin -current

[Vincent Poy]

On 26 Jan 2003, Eric Jones wrote:

> On Sun, 2003-01-26 at 20:55, Terry Lambert wrote:
> > walt wrote:
> > > Steve Kargl wrote:
> > > > On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
> > > >>Is there any reason, on newer motherboards, to need the MAXMEM option?
> > > >
> > > > I don't know.  I've always used MAXMEM.  Guess it's
> > > > time to remove it from my kernel config file.
> > >
> > > FWIW, I've been using FBSD -stable and -current for about 3 years
> > > on five different machines and I've never used MAXMEM.  Never had
> > > any problems recognizing memory, either -- guess I've been luckier
> > > than some.
> >
> > MAXMEM is useful for testing configurations with less memory,
> > without having to open up your box and yank SIMMs, or to have
> > a bunch of different sized pairs of SIMMs lying around.
> >
> > -- Terry
> >
>
> For uses such as testing I can understand, but I don't see a use under
> normal conditions, at least on newer systems.  I haven't dug into the
> source yet today, but there must be a reason why ACPI doesn't play nice
> on certain systems when MAXMEM is specified.
>
> I wonder if it is just AMD systems?  Mine's a 900MHz Duron, and IIRC I
> think someone else in earlier in the thread was using an AMD also.

I posted the original thread and can say the problem occurs on
both PII366 notebook, P4m-2Ghz, P4-1.7Ghz as well as PIII1Ghz systems and
various AMD Athlon XP's.


Cheers,
Vince - [EMAIL PROTECTED] - Vice President    __ 
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanicin -current

[Vincent Poy]

On Sun, 26 Jan 2003, Terry Lambert wrote:

> walt wrote:
> > Steve Kargl wrote:
> > > On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
> > >>Is there any reason, on newer motherboards, to need the MAXMEM option?
> > >
> > > I don't know.  I've always used MAXMEM.  Guess it's
> > > time to remove it from my kernel config file.
> >
> > FWIW, I've been using FBSD -stable and -current for about 3 years
> > on five different machines and I've never used MAXMEM.  Never had
> > any problems recognizing memory, either -- guess I've been luckier
> > than some.
>
> MAXMEM is useful for testing configurations with less memory,
> without having to open up your box and yank SIMMs, or to have
> a bunch of different sized pairs of SIMMs lying around.
>
> -- Terry

I thought the original purpose atleast in FreeBSD 2.x and earlier
was so the kernel can recognize more than 64 megs of physical ram.


Cheers,
Vince - [EMAIL PROTECTED] - Vice President    __ 
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanic in -current

[Vincent Poy]

On Sun, 26 Jan 2003, Steve Kargl wrote:

> On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
> > On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
> > > >
> > >
> > > Disable acpi. acpi is broken.
> >
> > I had the same problem until today.  If ACPI was enabled, I would get a
> > panic on boot.  I removed MAXMEM from my kernel conf, recompiled, and
> > voila, no panic.  ACPI looks like its working, according to the dmesg,
> > where any attempt to load it before panicked with pmap_mapdev: Couldn't
> > alloc kernel virtual memory.
> >
> > Is there any reason, on newer motherboards, to need the MAXMEM option?
>
> I don't know.  I've always used MAXMEM.  Guess it's
> time to remove it from my kernel config file.

Yeah, me too on all the previous systems I built and manage since
atleast 6 years ago, without MAXMEM, it will not show memory above 64 megs
so I continued to use it until I decided to build new systems for others
and the MAXMEM option gave the problem while without the option, it seems
to be fine and shows all memory.


Cheers,
Vince - [EMAIL PROTECTED] - Vice President    __ 
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Am I blind? (devfs issue)

[Thomas E. Zander]

Hi,

On Mon, 27. Jan 2003, at  9:49 +0100, [EMAIL PROTECTED] wrote
according to [Re: Am I blind? (devfs issue)]:

> >Could somebody explain to me why the device isn't listed in the first
> >ls -l call?
> 
> Hehe: welcome to clonable devices :-)
> 
> Notice that the major/minor is 3/27 which maps to /dev/dsp0.0.
> 
> /dev/dsp is a cloned device which gives you the first free /dev/dsp*
> device.
> 
> cloned devices do not appear in readdir requests, that's why you don't
> see it with "ls -l /dev/dsp*"

Okay, I understand.

Thanks for the quick answer.

Riggs

-- 
- "[...] I talked to the computer at great length and
-- explained my view of the Universe to it" said Marvin.
--- And what happened?" pressed Ford.
 "It committed suicide." said Marvin.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanic in -current

[Vincent Poy]

On 26 Jan 2003, Eric Jones wrote:

> On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
>
> Sorry if this is the second copy, I'm not sure if it went out the first
> time or not
>
> > On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
> > >
> > > /boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0
> > > syms=[0x4+0x5540+0x702d|]
> >
> > snip
> >
> > > embedded  0 6 A   0x60  3 4 5 6 7 9 10 11 12 14 15
> > > panic: pmap_mapdev: Couldn't alloc kernel virtual memory
> > > Debugger("panic")
> > > Stopped at  Debugger+0x45:  xchgl  %ebx,in_Debugger.0
> > > db> trace
> > > Debugger(c0435e9c) at Debugger+0x45
> > > panic(c0460ba0,0,0,c064cbc4,0) at panic+0x7c
> > > pmap_mapdev(1ffd,0,c064cc54,c064cbd4,c060547a) at pmap_mapdev+0x5d
> > > AcpiOsMapMemory(1ffd,0,0,c064cbc4,0) at AcpiOsMapMemory+0x12
> > > AcpiTbGetThisTable(c064cc54,c064cc08,c064cc64,c064cc54,c064cc54) at
> > > AcpiTbGetThisTable+0xa6
> > > AcpiTbGetTableBody(c064cc54,c064cc08,c064cc64,0,0) at AcpiTbTableBody+0x3b
> > > AcpiTbGetTable(c064cc54,c064cc64,c064cc54,9,1ffd) at AcpiTbGetTable+0x29
> > > AcpiTbGetTableRsdt(1,fd6e0,0,c061a520,c159ec80) at AcpiTbGetTableRsdt+0x1a
> > > AcpiLoadTables(0,c66d8118,c061a3c8,c1586aa0,c064ccfc) at AcpiLoadTables+0x85
> > > acpi_identify(c061a3c8,c159ec80) at acpi_identify+0x99
> > > bus_generic_probe(c159ec80,c66b1090,c064cd34,c028e724,c159ec80) at
> > > bus_generic_probe+0x54
> > > nexus_probe(c159ec80) at nexus_probe+0x186
> > > device_probe_child(c159ef00,c159ec80,c028e4e5,c15917c8,1) at
> > > device_probe_child+0xcc
> > > device_probe_and_attach(c159ec80) at device_probe_and_attach+0x4b
> > > root_bus_configure(c159ef00,c045b660,0,4) at root_bus_configure+0x16
> > > configure(0,649c00,649000,0,c01378b5) at configure+0x22
> > > mi_startup() at mi_startup+0x9a
> > > begin() at begin+0x2c
> > > db>
> > >
> >
> > Disable acpi. acpi is broken.
>
> I had the same problem until today.  If ACPI was enabled, I would get a
> panic on boot.  I removed MAXMEM from my kernel config, recompiled, and
> voila, no panic.  Everything seems to be working, acpi is doing
> something, according to the dmesg.  When I had MAXMEM as an option, I
> received the following panic less than a second into the kernel boot.
>
> pmap_mapdev: Couldn't alloc kernel virtual memory
>
> With MAXMEM unspecified, no problems.  Is there any reason, on newer
> motherboards, to need the MAXMEM option?  Without it specified, I see
> all 256M in the system.  I originally had it for my old MB (a K6-2) that
> wouldn't work without it (4-CURRENT days).  My new MB doesn't need it.
>
> Just my $0.02

I've actually been using the MAXMEM option since the 2.x days
since I remember unless MAXMEM was specified, FreeBSD will only see 64megs
of ram but I guess they fixed it so it detects more than that sometime
later.


Cheers,
Vince - [EMAIL PROTECTED] - Vice President    __ 
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Options MAXMEM added to GENERIC kernel config causes kernelpanic in -current

[Vincent Poy]

On Thu, 23 Jan 2003, Dan Nelson wrote:

> In the last episode (Jan 23), Vincent Poy said:
> > Greetings everyone,
> >
> >   With the latest -CURRENTs ever since atleast September 12, 2002
> > that I have tested on several different machines ranging from
> > PII/PIII/PIV Desktop and Notebooks, whenever the following option is
> > added to the GENERIC kernel config, the kernel will panic on booting
> > up.  I used this option in the January 2002 -currents without
> > problems.  The tested systems range in memory from 128MB to 1GIG.
> >
> > options MAXMEM=786432
>
> I have used the equivalent loader variable hw.physmem to limit memory
> usage for quite a while with no panics.  Try putting
>
> hw.physmem="768M"
>
> in /boot/loader.conf and see if it does what you want.
>
> > Physical memory use set to 786432K
> [...]
> > real memory  = 536870912 (524288K bytes)
> > Physical memory chunk(s):
> > 0x1000 - 0x0009efff, 647168 bytes (158 pages)
> > 0x00651000 - 0x1fff7fff, 530214912 bytes (129447 pages)
> > avail memory = 513802240 (501760K bytes)
>
> It looks like there is just 512M of available memory in the system
> anyhow.  Setting MAXMEM to 768M isn't going to do you any good.

Actually, it depends on which system you're referring to.  This
one actually has 576Megs of ram but the IBM ThinkPad BIOS will only show
512Megs.  The system sees all memory without the MAXMEM option, I just
remember it was needed in older FreeBSD versions from atleast 6 years ago
since I remember without the option, it will only see 64megs or something.


Cheers,
Vince - [EMAIL PROTECTED] - Vice President    __ 
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Required kernel config file change soon

[Wiktor Niesiobedzki]

On Sun, Jan 26, 2003 at 12:03:47AM -0500, Jeff Roberson wrote:
> I'm about to commit code that will make one of :
> 
> options SCHED_4BSD
> 
> or
> 
> options SCHED_ULE
> 
As far as I see, SCHED_ULE scheduler doesn't take advantage of having more
than 1 processor.
During make -j 6 buildworld, and other process that consumes as much of
computing power as he can, I get such output from top:
CPU states: 36.0% user,  0.0% nice, 13.8% system,  2.5% interrupt, 47.7% idle

Is it natural for this scheduler?
Dmesg attached.

Best regards,

Wiktor Niesiobedzki

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #10: Mon Jan 27 08:06:28 CET 2003
root@portal:/usr/obj/usr/src/sys/PORTALSMP
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0439000.
Preloaded elf module "/boot/kernel/if_ed.ko" at 0xc04390a8.
Preloaded elf module "/boot/kernel/miibus.ko" at 0xc0439154.
Preloaded elf module "/boot/kernel/if_rl.ko" at 0xc0439200.
Preloaded elf module "/boot/kernel/random.ko" at 0xc04392ac.
Preloaded elf module "/boot/kernel/dummynet.ko" at 0xc0439358.
Preloaded elf module "/boot/kernel/ipfw.ko" at 0xc0439408.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04394b4.
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (534.55-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
  
Features=0x183fbff
real memory  = 268369920 (255 MB)
avail memory = 256094208 (244 MB)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
Using $PIR table, 8 entries at 0xc00fd7e0
ACPI-0438: *** Error: Looking up [\\_PR_.CPU0] in namespace, AE_NOT_FOUND
ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-safe"  frequency 3579545 Hz
ACPI-1287: *** Error: Method execution failed, AE_AML_UNINITIALIZED_LOCAL
can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_UNINITIALIZED_LOCAL
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
acpi_cpu0:  on acpi0
acpi_cpu1:  on acpi0
acpi_tz0:  on acpi0
ACPI-0438: *** Error: Looking up [\\_PR_.CPU0] in namespace, AE_NOT_FOUND
ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
acpi_button0:  on acpi0
pcib0:  port 0x5000-0x500f,0x4000-0x4041,0xcf8-0xcff on acpi0
pci0:  on pcib0
IOAPIC #0 intpin 19 -> irq 2
IOAPIC #0 intpin 18 -> irq 10
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
IOAPIC #0 intpin 16 -> irq 11
pci1:  at device 0.0 (no driver attached)
isab0:  at device 7.0 on pci0
isa0:  on isab0
atapci0:  port 0xf000-0xf00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0:  at device 7.2 (no driver attached)
Timecounter "PIIX"  frequency 3579545 Hz
pci0:  at device 7.3 (no driver attached)
rl0:  port 0xc400-0xc4ff mem 0xdb40-0xdb4000ff irq 2 at 
device 9.0 on pci0
rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode
rl0: Ethernet address: 00:02:44:45:6e:27
miibus0:  on rl0
rlphy0:  on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ed0:  port 0xc800-0xc81f irq 10 at device 11.0 on 
pci0
ed0: address 52:54:05:f6:9c:6b, type NE2000 (16 bit) 
atapci1:  port 
0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 10 at device 19.0 on pci0
ata2: at 0xcc00 on atapci1
atapci2:  port 
0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 10 at device 19.1 on pci0
ata3: at 0xd800 on atapci2
fdc0: cannot reserve I/O port range (1 ports)
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0: cannot reserve I/O port range (1 ports)
pmtimer0 on isa0
orm0:  at iomem 0xef000-0xe,0xc-0xc9fff on isa0
atkbdc0:  at port 0x64,0x60 on isa0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
fdc0: cannot reserve I/O port range (6 ports)
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
Timecounters tick every 10.000 msec
DUMMYNET initialized (011031)
ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to deny, 
logging disabled
IP Filter: v3.4.29 initialized.  Default = pass all, Logging = enabled
acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0%
ad0: 515MB  [1048/16/63] at ata0-master PIO3
ad2: 58644MB  [119150/

Re: 4.7-amd cannot mount exports from 5.0-RELEASE

[Jun Kuriyama]

At Tue, 21 Jan 2003 23:29:16 + (UTC),
Masafumi NAKANE wrote:
> Well, not so quick.  I took another -CURRENT box and the problem was
> not reproduceable on this box.  I can't quite figure out what the
> differences between these two boxes are, though.

I think I found the solution.

On HEAD and RELENG_5_0 as of now

On RELENG_4 and old (e.g. last year's) HEAD, refering remote
filesystem via AMD retrieves export list from server and trying to
mount like this:

c->s MOUNT V1 EXPORT Call
s->c MOUNT V1 EXPORT Reply
c->s MOUNT V1 MNT Call
s->c MOUNT V1 MNT Reply

But on latest HEAD and RELENG_5_0, packets show like this:

c->s MOUNT V1 EXPORT Call
s->c MOUNT V1 EXPORT Reply
c->s MOUNT V1 MNT Call
s->c MOUNT V1 EXPORT Reply (duplicate)

So, problem may be in mountd.  I tested with reverting the commit at
2003/01/15, and it works fine.

mbr 2003/01/15 23:27:31 PST

  Modified files:
usr.sbin/mountd  mountd.c 
  Log:
  Implement nonblocking tpc-connections. rpcgen -m does still
  produce backcompatible code.


I don't know the problem is in amd or mountd.  I fear other programs
are broken with this commit...


-- 
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
 <[EMAIL PROTECTED]> // FreeBSD Project

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Am I blind? (devfs issue)

[phk]

In message <[EMAIL PROTECTED]>, "Thomas E. Zander" write
s:
>Sorry, this is probably a stupid question, but:
>
>[riggs] ~ > ll /dev/ds*
>crw-rw-rw-  1 root  wheel   30,   3 27 Jan 14:46 /dev/dsp0.0
>crw-rw-rw-  1 root  wheel   30, 0x00010003 27 Jan 10:59 /dev/dsp0.1
>crw-rw-rw-  1 root  wheel   30,   5 27 Jan 10:59 /dev/dspW0.0
>crw-rw-rw-  1 root  wheel   30, 0x00010005 27 Jan 10:59 /dev/dspW0.1
>crw-rw-rw-  1 root  wheel   30,  11 27 Jan 10:59 /dev/dspr0.0
>
>[riggs] ~ > ll /dev/dsp
>crw-rw-rw-  1 root  wheel   30,   3 27 Jan 14:46 /dev/dsp
>
>Could somebody explain to me why the device isn't listed in the first
>ls -l call?

Hehe: welcome to clonable devices :-)

Notice that the major/minor is 3/27 which maps to /dev/dsp0.0.

/dev/dsp is a cloned device which gives you the first free /dev/dsp*
device.

cloned devices do not appear in readdir requests, that's why you don't
see it with "ls -l /dev/dsp*"

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Am I blind? (devfs issue)

[Thomas E. Zander]

Sorry, this is probably a stupid question, but:

[riggs] ~ > ll /dev/ds*
crw-rw-rw-  1 root  wheel   30,   3 27 Jan 14:46 /dev/dsp0.0
crw-rw-rw-  1 root  wheel   30, 0x00010003 27 Jan 10:59 /dev/dsp0.1
crw-rw-rw-  1 root  wheel   30,   5 27 Jan 10:59 /dev/dspW0.0
crw-rw-rw-  1 root  wheel   30, 0x00010005 27 Jan 10:59 /dev/dspW0.1
crw-rw-rw-  1 root  wheel   30,  11 27 Jan 10:59 /dev/dspr0.0

[riggs] ~ > ll /dev/dsp
crw-rw-rw-  1 root  wheel   30,   3 27 Jan 14:46 /dev/dsp

Could somebody explain to me why the device isn't listed in the first
ls -l call?

TIA
Riggs

P.S.
FreeBSD trillian.mugiri.au 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Wed Jan 22 23:19:13 WST 
2003

-- 
- Die Welt schläft tief schon lange Zeit | Sent with RiggiSmooth [tm] -
-- Mich nur flieht die Dunkelheit| - --
--- Denn per Infrarot seh ich| just to fit your ---
 Die Nacht ist wirklich widerlich.   | primitive screen.   

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message