Re: AHC0 fireworks ?

At 25/11/99, Justin T. Gibbs wrote: > > But I have now a lot of errors (as you can see in this logs) on my scsi > chain. > > I had never experienced such things in the near past (even if as an old > > current user sometimes I see also worse things :-) > > > > Btw I don't see in the current mailin

Re: Sv: Dr Neuhaus niccy go not recognized

On Sat, Nov 27, 1999 at 02:11:16AM +0100, Leif Neland wrote: > > > On Sun, 7 Nov 1999, German Tischler wrote: > > > On Sun, Nov 07, 1999 at 06:27:37PM +0100, Leif Neland wrote: > > > I'd like to test, So how do I proceed from here? > > > > Get the latest i4b-dev snapshot (00.83.11), get my pat

Make world broken in libc_r

Hi "make world" is broken in libc_r. Simple fix is to replace all "socklen_t" with "int". M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Update of if_dc driver

On Thu, 25 Nov 1999, Bill Paul wrote: > My goal is to try and get this driver into 4.0 as soon as possible so > I can use it as a replacement for the al, ax, dm, pn and mx drivers. > However, there's a small problem: the de driver already supports the > 21143, although it does so poorly according

ESS1879, pnp_id patch and illegal probe about ESS1888

I play 4-current with MITSUBISHI AmityCN(NOTE-PC) which has ESS1879(ISA-PnP) Sound Chip. I hope to added below patch to 4-current sound driver. -- By the way I added only below line to kernel configuration file. device pcm0 But kernel probed ESS1888 as pcm0 and ESS1879 as pcm1.

repeatable crash in -current (softupdates, NFS)

I'm running a -current system from Nov 26th (approx 4am EST). I can currently reliably crash the system by doing: ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html The crash only works when I do it on a NFS mounted filesystem. I'm using NFSv2/UDP. The server is a 3.

Re: ESS1879, pnp_id patch and illegal probe about ESS1888

On Sun, 28 Nov 1999, MIHIRA Sanpei Yoshiro wrote: > I play 4-current with MITSUBISHI AmityCN(NOTE-PC) which has > ESS1879(ISA-PnP) Sound Chip. > > I hope to added below patch to 4-current sound driver. > > -- > By the way I added only below line to kernel configuration file. > >

mount_nfs broken

Hi Mount_mfs is broken - mounttab\* not present. M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Odd panic

Hi, cvsup at Sat Nov 27 04:02:41 GMT 1999, looks like it went in the middle of starting up SCSI devices. This box is not SMP and has a 2940UW, my SMP -current box with a plain 2940 doesn't do this. ... da0 at ahc0 bus 0 target 0 lun 0 da0: Fied Direct Access SCSI-2 device da0: 40.000MB/s transf

Re: Update of if_dc driver

> On Thu, 25 Nov 1999, Bill Paul wrote: > > > My goal is to try and get this driver into 4.0 as soon as possible so > > I can use it as a replacement for the al, ax, dm, pn and mx drivers. > > However, there's a small problem: the de driver already supports the > > 21143, although it does so poor

Re: Odd panic

Bob, can you try to locate the symbols around 0xc01658e6 in your kernel ? Also, when you end in the debugger, always type "trace" so we get a stacktrace to look at. Poul-Henning In message , Bob Bishop writes: >Hi, > >cvsup at Sat Nov 27 04:02:41 GMT 1999

Re: repeatable crash in -current (softupdates, NFS)

On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote: > > I'm running a -current system from Nov 26th (approx 4am EST). > > I can currently reliably crash the system by doing: > > ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html > > > The crash only works w

Re: Odd panic

Hi, >can you try to locate the symbols around 0xc01658e6 in your kernel ? I mistranscribed that (really must get serial consoles sorted out), in fact it's: c0165e80 T devsw >Also, when you end in the debugger, always type "trace" so we get >a stacktrace to look at. Yes, sorry, got called for

Re: Odd panic

In message , Bob Bishop writes: >devsw() at devsw+0x6 >vfs_mountroot_try(c0391092,c02c531c) at vfs_mountroot_try+0xe9 >vfs_mountroot(0,3a4c00,3ab000,0,c011d5e6) at vfs_mountroot+0x5a >mi_startup(c03a6fb4,b0246,ffe,3ab000,c017ada1) at mi_startup+0x70 >

Re: Make world broken in libc_r

On Sat, 27 Nov 1999, Mark Murray wrote: > Hi > > "make world" is broken in libc_r. Simple fix is to replace all > "socklen_t" with "int". libc_r likes to pull data from /usr/include instead of the source tree, "make includes" fixes this. I'm not sure if that's the correct way to fix it though

Re: Odd panic

Hi, At 7:54 pm +0100 27/11/99, Poul-Henning Kamp wrote: >[...] >What is in your /etc/fstab for the root fs ? That was it: I was still running on /dev/sd*, looks like that just stopped working. Thanks -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]

ATA and msdosfs problems / corruption

When attempting to copy a large file over to a FAT partition, I had these errors pop up: Nov 27 16:26:59 volatile /kernel: ata0-master: ad_timeout: lost disk contact - resetting Nov 27 16:28:17 volatile /kernel: ata0: resetting devices .. WARNING: WAIT_READY active=ATA_ACTIVE_ATA Nov 27 16:28:1

State of Alpha support and Oracle.

I am not sure of thw state of things but if someone wanted to run Oracle-8 and had an idea in their mind that they'd like to run it in an Alpha, tehn teh following questions would need to be answered (and I dont know the answers) 1/ does FreeBSD-alpha support SMB 2/ is there a binary version of

Re: State of Alpha support and Oracle.

> > I am not sure of thw state of things but if someone wanted to run Oracle-8 > and had an idea in their mind that they'd like to run it in an Alpha, > tehn teh following questions would need to be answered (and I dont know > the answers) > > 1/ does FreeBSD-alpha support SMB Samba works just

Re: mount_nfs broken

: :Hi : :Mount_mfs is broken - mounttab\* not present. : :M Could you be more specific? It seems to work for me (I removed /var/db/mounttab and tried it with a new build and it did work). -Matt Matthew Dil

Re: Route table leaks

:+ s = splnet(); :+ RTFREE(rt); :+ splx(s); :... :+ s = splnet(); :+ RTFREE(rt); :+ splx(s); :+ } : ro->ro_rt = rtalloc1(&ro->ro_dst, 1, ignore); : } : : :Now for my questions: : :1. Do I really need the spl

Re: Which is the truth? (sycalls and traps)

:>Am I also right in assuming that all the registers that the user was :>running when they did the KERNCALL have been saved on the KERNEL stack by :>the time that the above routines are called? : : No, that's what the pushal (push all) does. : :-DG : :David Greenman pushing/popping integer

Re: Which is the truth? (sycalls and traps)

Oops, let me add an addendum, I didn't answer the original question! :(Julian wrote...) : :Am I also right in assuming that all the registers that the user was :running when they did the KERNCALL have been saved on the KERNEL stack by :the time that the above routines are called? : :(It's a p

Re: Odd panic

> Hi, > > At 7:54 pm +0100 27/11/99, Poul-Henning Kamp wrote: > >[...] > >What is in your /etc/fstab for the root fs ? > > That was it: I was still running on /dev/sd*, looks like that just stopped > working. Thanks A week or two back, actually. But you should have received a more civilised f

Re: State of Alpha support and Oracle.

On Sat, Nov 27, 1999 at 05:53:21PM -0800, Mike Smith wrote: > > If all you want is an oracle-like database however, I would recommend > that you look at Linter (www.relcom.ru, IIRC). OCI-compatible, and much, > much cheaper. http://www.relex.ru/linter/ Greg -- Gregory S. Sutter

Re: Which is the truth? (sycalls and traps)

Matthew Dillon wrote: > Oops, let me add an addendum, I didn't answer the original question! > > :(Julian wrote...) > : > :Am I also right in assuming that all the registers that the user was > :running when they did the KERNCALL have been saved on the KERNEL stack by > :the time that the abo

Re: mount_nfs broken

> > : > :Hi > : > :Mount_mfs is broken - mounttab\* not present. > : > :M > > Could you be more specific? It seems to work for me (I removed > /var/db/mounttab and tried it with a new build and it did work). Damn. I screwed up the reporting bigtime. It is mount_nfs, and there is ment

Re: repeatable crash in -current (softupdates, NFS)

On Sat, 27 Nov 1999, Eivind Eklund wrote: > On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote: > > > > I'm running a -current system from Nov 26th (approx 4am EST). > > > > I can currently reliably crash the system by doing: > > > > ln -s /home/users/vshah/public_html/index.html /ho