ATA problems on Promise controller

With a -current kernel ( cvsupped today ) I can no longer boot. It hangs on the drives connected to the promis controller built into my MSI KT266 mobo. The messages are like ad2: READ command timeout tag=0 serv=0 - resetting Same for ad3. It tries falling back to pio mode but after that it hangs

Re: USB detach crashes possibly fixed

ery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: process

Re: USB detach crashes possibly fixed

ch action is never executed when I switch off my Sony camera ( it has never worked as far as I know) Attach actions are executed fine.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

usdb missing detaches ???

detach "umount -f /sony" BTW This is on -current compiled and installed yesterday. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

nfsclient and amd

?? Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: df -l broken

> Paul van der Zwan wrote: > > > > I noticed the -l option of the df command is broken. It is supposed to > > print df for local filesystems but on my system it prints nothing at all. > > I had a quick look at the code , as far as I can tell it uses sysctl to

df -l broken

I noticed the -l option of the df command is broken. It is supposed to print df for local filesystems but on my system it prints nothing at all. I had a quick look at the code , as far as I can tell it uses sysctl to figure out the mounted filesystems but thinks all of them are non-local and ign

Re: Multiple NFS server problems with Solaris 8 clients

t;but I would take PROG_UNAVAIL if I could get -current to eject it. In this case ( the NFS_ACL one) it seems PROG_UNAVAIL is the right thing. It has a different program number from NFS and it is not just a not implemented procedure that is part of NFS. Paul -- Paul van der Zwan

Re: Multiple NFS server problems with Solaris 8 clients

In message <[EMAIL PROTECTED]>, Thomas Quinot wrote: >Le 2001-10-14, Paul van der Zwan écrivait : > >> I am using -current box as a homedir server for my Solaris clients and >> have noticed a wierd problem. > >Other problems here, with Solaris 2.[68] as clients,

Multiple NFS server problems with Solaris 8 clients

I am using -current box as a homedir server for my Solaris clients and have noticed a wierd problem. When I login my homedir gets mounted ok but when I type ls -l it just waits until I ^C it. If I run snoop on Solaris I see a getattr request being sent and an answer being received but apparently

Parallel port back

My parallel port is back. Switching the it from 3BC to 378 made the probe recognize it again. Apparently the new code doesn't like the 3BC address as much as the old code.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to the

Parallel port gone missing (extra info)

In message <[EMAIL PROTECTED]>, Paul van der Zwan wrote: > >I just notice my par. port is no longer detected. A kernel built on Jan 21st >fails to detect my par. port which has worked fine so far. >In /var/log/messages I get the following: > >Jan 27 22:29:53 trantor

Par. gone missing

g detected ?? Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ATAPI CD errors

(atp->atapi_parm->dmaflag ? 4 : 0) : > This patch allows me to mount the cdrom... The probes show PIO mode i.s.o. DMA. So it looks like DMA is broken for this drive.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, every

Re: ATAPI CD errors

In message <[EMAIL PROTECTED]>, Paul van der Zwan wrote: > >I switched to the 'new' atapi driver and I am having trouble with my cdrom >which worked fine using the old wd driver. > >I have the following in my config file : > >controller ata0 >

ATAPI CD errors

tray acd0: Medium: no/blank disc inside, unlocked But when I try to mount the CD I get the following error : atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 Anybody any idea or hint ?? TIA Paul -- Paul va

sio.c breaks kernel ( even GENERIC)

reference to `gdb_putc' *** Error code 1 Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: CPP broken on egcs current

> In article <199904051112.naa22...@trantor.xs4all.nl>, > Paul van der Zwan wrote: > > > > A make buildworld fails on an freshly rebuilt system. > > The following error is shown: > ... > > /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/c

cpp breakage on egcs -current

addition xdm and xdrb also suffer .. This is on a system on which I ran a succesfull make world last night. The kernel is also built using egcs. This is the only problem I have found so far. The CFLAGS for make world were -O2 -pipe, for the kernel -O -pipe. Paul -- Paul van der Zwan

CPP broken on egcs current

thru CPP so does xdm trying the run Xresources thru cpp.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: Slow seq. write on Seagate ST36530N

B/s. So it looks like there is at least an acceptable ( to me ) workaround. Maybe the CAM maintainer can put an entry in cam_xpt.c for this drive ??? dmgs shows is as : da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offs

Re: Slow seq. write on Seagate ST36530N

> Paul van der Zwan wrote... > > > > I am having some performance problems on my -current ( update last weekend) > > I hooked up a new Seagate ST36530N yesterday ( connected to an Adaptec > > 2940U) > Andreas Klemm has had similar trouble, as he pointed out. >

Slow seq. write on Seagate ST36530N

), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) Anybody an idea ?? Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majord...@f