incorrect irqs with pci devices

1999-12-02 Thread Mike Heffner
Hi, I have recently noticed that the irqs for my PCI devices are being screwed up somehow. It is easily noticeable with dmesg, the correct one's are in paren.: vga-pci0: irq 17(real 11) at device 0.0 on pci1 ^^ ^^ pcm1: irq 16(real 10) at device 15.0 on

Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread David O'Brien
On Thu, Dec 02, 1999 at 08:24:19PM -0500, Greg Lehey wrote: > Can't you boot from the old kernel? Or have you already wiped the > bdevs? If so, how about the fixit floppy/CD-ROM? At 2MB the Alpha fixit floppy isn't very useful. Nor is there a live files system for the Alpha. Nor can you even

Apologies

1999-12-02 Thread Matthew Jacob
I realize that I have been much more upset and unpleasant about this than the situation warranted, and I would like to extend my apologies to all and sundry for venting my frustration so publicly. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the

Re: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread Mike Smith
> > Sorry- maybe more of an edge case. It really has to do with 'ad' support > seemingly vanishing from the alpha. Or, rather, it's hard to say exactly > what has happened: > > > Mounting root from ufs:/dev/rad0a > no such device 'rad' You never mount 'r' devices. That should be '/dev/ad0a',

Sorry....

1999-12-02 Thread Matthew Jacob
> Well, I wasn't back in town until last night with 5000 messages to catch > up on. Sorry for not getting your questions first. > > There are other things broken too. Oh well- I really shouldn't get wired. > *BSD will get taken as a serious effort as much as it deserves based upon > what actual

Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread Matthew Jacob
(removed from general list) > Slow down. You are getting screwed by a combination of things. It > isn't all phk's fault. > > The bdev elimination is one factor, but the most important one (the > fsck/mount segv) is due to int/long breakage introduced version 1.85 > of mount.h. This happened

FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread Matthew Jacob
Sorry- maybe more of an edge case. It really has to do with 'ad' support seemingly vanishing from the alpha. Or, rather, it's hard to say exactly what has happened: Mounting root from ufs:/dev/rad0a no such device 'rad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6

Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread Andrew Gallatin
Matthew Jacob writes: > > > Can't you boot from the old kernel? Or have you already wiped the > > I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped > all block devs, so swapon, etc. ,fail.. However, this is the conundrum- > it's not safe to do a 'make installworld'

panic after make new kernel with ctm source upto src-cur.4115

1999-12-02 Thread Chan Yiu Wah
hello, I make world and new kernel with ctm source up to src-cur.4115 successfully. However, my system go to panic when I boot it with new kernel. The error was === Error === resume IOPL = 0 interrupt mask none <-- SMPXXX trap number = 12 mp_lock = 0102 cpuid = 1 boot() call

Re: World breakage in libpam?

1999-12-02 Thread John Polstra
In article <[EMAIL PROTECTED]>, David Scheidt <[EMAIL PROTECTED]> wrote: > Seeing this trying to build world, cvsup'd earlier today. > > cc -O -pipe -static -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING > -Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DINTERNAL_LS > -Dmain=ls_

Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread Matthew Jacob
> Can't you boot from the old kernel? Or have you already wiped the I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped all block devs, so swapon, etc. ,fail.. However, this is the conundrum- it's not safe to do a 'make installworld' on a two week old kernel, but the new ke

Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread Greg Lehey
On Thursday, 2 December 1999 at 17:21:55 -0800, Matthew Jacob wrote: > > Well, I am truly f*cked now. I read enough of this thread, saw nothing new > in UPDATING, and did the following: > > alpha > > kernel from today > MAKEDEV from today > (but not a make world install- the bin

Re: HEADS-UP: bdevs have been assimilated.

1999-12-02 Thread Matthew Jacob
Well, I am truly f*cked now. I read enough of this thread, saw nothing new in UPDATING, and did the following: alpha kernel from today MAKEDEV from today (but not a make world install- the binaries/libs are ~week old) cannot get out of single user mode. fsck core dumps.

Re: Problem with syscons in VESA mode

1999-12-02 Thread Kazutaka YOKOTA
>I'm using non-standard 100x37 console mode on my notebook, because in 80x25 >text mode letters seems too big for my 12' panel, while other modes doesn't >cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600 >100x37 mode (instead of default 80x25) with 8x16 font, and in m

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Mike Smith
> In message <[EMAIL PROTECTED]> "Matthew N. >Dodd" writes: > : On Thu, 2 Dec 1999, Nick Hibma wrote: > : > PCMCIA has the problem that the hardware register you are talking to can > : > disappear on the spot, between 2 outb()s. > : > : Can't we do something about this using bus_space? This wou

Re: Problem with syscons in VESA mode

1999-12-02 Thread Alexander Leidinger
On 2 Dec, John Baldwin wrote: >> It is interesting. Seems like it is not only VESA modes bug. Strange >> that nobody >> else observed this misbehaviour. > I have seen it in 132 x anything on both -stable and -current but just > haven't been bothered enough by it to complain. I´ve seen this onc

panic: vm_page_free: freeing wired page

1999-12-02 Thread David Scheidt
I am having the following panic, with a -CURRENT system as fo CTM cvs-cur.5868. I *think* the panic was induced by running mpg123 with a not an mp3 file. I've had two (maybe three, something happened to the box over night.) of these panics, but hte first was with no dump device configured. I

Re: Problem with syscons in VESA mode

1999-12-02 Thread Ollivier Robert
According to Maxim Sobolev: > It is interesting. Seems like it is not only VESA modes bug. Strange that > nobody else observed this misbehaviour. I used to see that in 132 col. mode a year or so (maybe more) and it was fixed at that time... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=

Re: Problem with syscons in VESA mode

1999-12-02 Thread Bernd Walter
On Thu, Dec 02, 1999 at 12:22:54PM -0500, John Baldwin wrote: > > On 02-Dec-99 Maxim Sobolev wrote: > > Tony Finch wrote: > > > >> Maxim Sobolev <[EMAIL PROTECTED]> wrote: > >> > > >> >I'm using non-standard 100x37 console mode on my notebook, because > >> >in 80x25 > >> >text mode letters seems

Re: block devices & dumpon.

1999-12-02 Thread Nick Hibma
> I agree (patches accepted), although it is hard to figure out just > exactly what is needed to "run one's system". > > Maybe a "remake" entry in MAKEDEV which remakes all current entries > if possible. cd /dev/; sh MAKEDEV * perhaps? It is going to be one hell of a ride on your disk,

Re: modules building...

1999-12-02 Thread Nick Hibma
Did you do a config of your kernel after updating? opt_linux.h is generated by config. Nick On Tue, 30 Nov 1999, Kenneth Culver wrote: > I tried to rebuild the linux kernel module, but it doesn't work: > > Warning: Object directory not changed from original > /usr/src/sys/modules/linux > cc -

Re: How do I get a USB mouse working in todays -CURRENT ?

1999-12-02 Thread Nick Hibma
> The problem is that the mouse doesn't work (its not a hardware problem), > all I get whenever I move the mouse are lots of the following messages > on the console: > > Discarded 7 bytes in queue This means that your mouse is working but moused is closing while the buffer is not empty yet. This

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Matthew N. Dodd
On Thu, 2 Dec 1999, Warner Losh wrote: > I had the same thought, but w/o a signal or other out of band error > communication, I'm not sure how to implement this. Well, if we do the detach and set a timeout freeing the device_t & softc the next read or write will fail and the 'sleeper' can bail ou

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : On Thu, 2 Dec 1999, Nick Hibma wrote: : > PCMCIA has the problem that the hardware register you are talking to can : > disappear on the spot, between 2 outb()s. : : Can't we do something about this using bus_space? This would give us a

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Warner Losh
In message <[EMAIL PROTECTED]> Nick Hibma writes: : PCMCIA has the problem that the hardware register you are talking to can : disappear on the spot, between 2 outb()s. Yes. That's why one must poll the device, from time to time, to see if it is gone. Yucky-poo. Warner To Unsubscribe: send m

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Matthew N. Dodd
On Thu, 2 Dec 1999, Nick Hibma wrote: > PCMCIA has the problem that the hardware register you are talking to can > disappear on the spot, between 2 outb()s. Can't we do something about this using bus_space? This would give us a fair bit of overhead for PCMCIA devices as well as require us to mor

Re: Problem with syscons in VESA mode

1999-12-02 Thread John Baldwin
On 02-Dec-99 Maxim Sobolev wrote: > Tony Finch wrote: > >> Maxim Sobolev <[EMAIL PROTECTED]> wrote: >> > >> >I'm using non-standard 100x37 console mode on my notebook, because >> >in 80x25 >> >text mode letters seems too big for my 12' panel, while other modes >> >doesn't >> >cover all panel siz

Re: Problem with syscons in VESA mode

1999-12-02 Thread Maxim Sobolev
Tony Finch wrote: > Maxim Sobolev <[EMAIL PROTECTED]> wrote: > > > >I'm using non-standard 100x37 console mode on my notebook, because in 80x25 > >text mode letters seems too big for my 12' panel, while other modes doesn't > >cover all panel size. So I've patched vidcontrol to switch to the VESA_

Re: Soundblaster 128 PCI

1999-12-02 Thread Russell Cattelan
Jeroen Ruigrok/Asmodai wrote: > -On [19991201 20:01], Russell Cattelan ([EMAIL PROTECTED]) wrote: > >Dag-Erling Smorgrav wrote: > >> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't > >> get to work with newpcm. > > >What mother board are you using? > >There have been some rep

Re: Well, the 3Com 574BT is still broken.

1999-12-02 Thread Matthew N. Dodd
On Thu, 2 Dec 1999, Frank Mayhar wrote: > Well, if there's _anything_ I can help with, please let me know. I did > dump the CIS using pccardc, but I didn't see the MAC address. I can even > set the laptop up with a serial console and hook it up to a system you can > log into, if that would help.

Re: Well, the 3Com 574BT is still broken.

1999-12-02 Thread Frank Mayhar
Matthew N. Dodd wrote: > On Thu, 2 Dec 1999, Frank Mayhar wrote: > > Suggestions? I could Really Use an ethernet connection on this > > laptop; right now I have the cardbus card (3Com 575CT) and the pcmcia > > card (the 574BT) sitting here, useless. > Looking at the NetBSD driver it appears that

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Nick Hibma
> There are other contexts for the same issues anyway. USB has devices > that go away suddenly, and it _is_ designed to be hot-removable, so > people are going to be pulling the plug on network adapters, ZIP > drives, etc. We need drivers that are capable of going away cleanly, > or at least wit

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Bruce Evans
On 2 Dec 1999, Ville-Pertti Keinonen wrote: > > The times are for `time make depend; time make' after `make clean; sync; > > sleep 1' (2 times for each run). The stack may have been perfectly > > misaligned for the default gcc. > > It depends on the command line. It took me a while to figure o

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Warner Losh
In message <[EMAIL PROTECTED]> Christopher Masto writes: : Hmm.. something's not right. I can eject my ed card (though I get : the "pccard: card removed, slot 0" message twice. But it doesn't : attach if I insert it again. "driver allocation failed for : Linksys(Combo PCMCIA EthernetCard (EC):

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Marcel Moolenaar
Ville-Pertti Keinonen wrote: > > If the pessimization persists when the initial alignment is fixed, > then there's a trade-off between a small pessimization for typical > code and a big pessimization for less common (but more often > performance-critical) code. Performance critical code should a

Re: semi-HEADS-UP (dumpon now wants raw disk device)

1999-12-02 Thread Bruce Evans
On Wed, 1 Dec 1999, Greg Lehey wrote: > > You must not have a very current -current :-). /dev/wd0 is a character > > device (with the same major/minor and character as /dev/rwd0) in -current: > > > > crw-r- 1 root operator3, 0x00010002 Dec 1 04:34 rwd0 > > crw-r- 1 root operator

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Ville-Pertti Keinonen
> > Note that double-alignment vs. word-alignment can really have >30% > > performance impact, at least on an Athlon and one meaningless floating > > point microbenchmark (operations on small, fixed-sized > > matrices...maybe it isn't even *that* meaningless). > > I verified that the default ali

Re: semi-HEADS-UP (dumpon now wants raw disk device)

1999-12-02 Thread Greg Lehey
On Wednesday, 1 December 1999 at 4:43:05 +1100, Bruce Evans wrote: > On Tue, 30 Nov 1999, Thomas Stromberg wrote: > > [ache wrote]: >> " >>> I see no needs of this change. I have -current dumpon/savecore work with >>> old entrly like /dev/wd0... >>> savecore understand both character and old blo

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Bruce Evans
On 2 Dec 1999, Ville-Pertti Keinonen wrote: >... > Note that double-alignment vs. word-alignment can really have >30% > performance impact, at least on an Athlon and one meaningless floating > point microbenchmark (operations on small, fixed-sized > matrices...maybe it isn't even *that* meaningl

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Ville-Pertti Keinonen
> > > Maybe alignment can even be done in the kernel... > > > > It gets messy, it has to be done before putting the env and argv > > pointers in place... > > Alignment also applies to calling signal handlers... Which is easier because sigframe has a constant size and you know what the relation

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Marcel Moolenaar
Ville-Pertti Keinonen wrote: > > Maybe alignment can even be done in the kernel... > > It gets messy, it has to be done before putting the env and argv > pointers in place... Alignment also applies to calling signal handlers... -- Marcel Moolenaarmailto:[EMAIL PROTECTE

Re: gcc-2.95.2, jade and freebsd-sgml-documentation

1999-12-02 Thread Jeroen Ruigrok van der Werven
-On [19991201 23:30], Nik Clayton ([EMAIL PROTECTED]) wrote: >On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote: >> i tried to make me a new handbook, so i needed jade. >> >> But the newest C++ fashion (g++ under current) has changed to fast for >> this very old 1998 heavily templa

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Ville-Pertti Keinonen
> AFAICT, it's enough to just align the stack before doing anything else. > In this case it means aligning the stack somewhere before > (exit(main(...)). gcc maintains proper alignment on an aligned stack. I wouldn't rely on that, gcc is free to assume that it can address local variables relativ

Re: Soundblaster 128 PCI

1999-12-02 Thread Dag-Erling Smorgrav
Russell Cattelan <[EMAIL PROTECTED]> writes: > Dag-Erling Smorgrav wrote: > > I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't > > get to work with newpcm. > What mother board are you using? Asus Socket 7. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send

Problem with syscons in VESA mode

1999-12-02 Thread Maxim Sobolev
Hi, I'm using non-standard 100x37 console mode on my notebook, because in 80x25 text mode letters seems too big for my 12' panel, while other modes doesn't cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600 100x37 mode (instead of default 80x25) with 8x16 font, and in

HEADS UP! device_add_child() change.

1999-12-02 Thread Matthew N. Dodd
I'm going to be committing the changes to eliminate the 'ivars' arguement to device_add_child(), and device_add_child_ordered(). The functionality will be provided by device_set_ivars(). I've got a go-ahead from Doug and Peter but as this change touches many files I'd like to give other driver m

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Marcel Moolenaar
Ville-Pertti Keinonen wrote: > +++ crt1.c 1999/12/02 09:02:05 > @@ -92,7 +92,17 @@ > monstartup(&eprol, &etext); > #endif > _init(); > -exit( main(argc, argv, env) ); > +asm volatile("andl $~15,%%esp;" > +"addl $4,%%esp;" > +"pushl %2;" > +

Re: minor bug in ee?

1999-12-02 Thread Bruce Evans
On Thu, 2 Dec 1999 [EMAIL PROTECTED] wrote: > I recently noticed that ^v (the scroll down a page command in ee) must be > entered twice to scroll down once (i.e. if you hit ^v once it won't do > anything, you must hit it again) on a 4.0-CURRENT system. As far as I can > recall, this has been hap

re: rpc.umntall does not work with AIX

1999-12-02 Thread Martin Blapp
> > Bad MNT PRC: RPC: Remote system error > Hi, This is a RPC problem, not an NFS problem. Maybe AIX does not support RPC_UMNTALL ? Because our support was buggy, noone may have notified it before. Or do you have problems with the AIX rpc.mountd ? Can you trace mountd(8) on the AIX side and lo

Re: minor bug in ee?

1999-12-02 Thread Sheldon Hearn
On Thu, 02 Dec 1999 00:54:11 CST, [EMAIL PROTECTED] wrote: > I recently noticed that ^v (the scroll down a page command in ee) must be > entered twice to scroll down once (i.e. if you hit ^v once it won't do > anything, you must hit it again) on a 4.0-CURRENT system. Sounds like ncurses takes

Re: kernel: -mpreferred-stack-boundary=2 ??

1999-12-02 Thread Ville-Pertti Keinonen
Ok, I've checked, and in -current, userland stack boundary alignment is useless because the stack pointer is initially only aligned on a word-boundary. I've also verified that the correct alignment is indeed expected to apply to frame pointers, i.e. stored frame pointers are at aligned stack slo

Re: Please check missing logical IDs for SB

1999-12-02 Thread Timo Geusch
On Wed, Dec 01, 1999 at 10:18:26AM +0900, Seigo Tanimura wrote: > If you have an SB card not probed since the import of the bridge > dirvers, could you please apply the following patch, add the logical > ID of your card into sbc_ids[] and see how it works? > (I have asked peter to review the PnP p

Re: Well, the 3Com 574BT is still broken.

1999-12-02 Thread Matthew N. Dodd
On Thu, 2 Dec 1999, Frank Mayhar wrote: > Suggestions? I could Really Use an ethernet connection on this > laptop; right now I have the cardbus card (3Com 575CT) and the pcmcia > card (the 574BT) sitting here, useless. Looking at the NetBSD driver it appears that the MAC address for the 574 is s

Well, the 3Com 574BT is still broken.

1999-12-02 Thread Frank Mayhar
And there appears to be some more brokenness. I've attached my latest (verbose) dmesg output. USB support is weird, and (not listed in dmesg) pccardd is failing to attach my Xircom modem card (which had been working), claiming "device not configured." Suggestions? I could Really Use an etherne

Re: PCCARD eject freeze (was Re: your mail)

1999-12-02 Thread Christopher Masto
On Wed, Dec 01, 1999 at 12:55:24AM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Christopher Masto writes: > : Well, here's all I've got. It's basically just a sloppy version of > : what you suggested. > > I've cleaned this up, worked it around, and managed to insert and > eject my