On Tue, Nov 27, 2001 at 08:13:38 +0300, Andrey A. Chernov wrote:
> cc -O -pipe -march=pentiumpro -DSETPROCTITLE -DLOGIN_CAP -DVIRTUAL_HOSTING
> -Wall
> -DINET6 -I/usr/src/libexec/ftpd -Dmain=ls_main
> -I/usr/src/libexec/ftpd/../../bin/ls -DUSE_PAM
> -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.
I've got a machine with 4G of RAM, and I'm trying to test all the RAM out
to make sure it's okay.
I've tried doing buildworlds, but never end up using more than 1G of RAM on
cache, etc.
I've got -current and -stable on it, and I've tried making an MFS
filesystem under -stable. I can't seem to
On Tue, Jan 22, 2002 at 22:18:51 -0700, Samuel J.Greear wrote:
> On Monday 21 January 2002 10:20 pm, Kenneth D. Merry wrote:
> > I've got a machine with 4G of RAM, and I'm trying to test all the RAM out
> > to make sure it's okay.
> >
> > I've tried
Attached is a patch for the aic(4) driver to do the following:
- enable 10MHz (fast SCSI) operation on boards that support it. (only
aic6360 boards with fast SCSI enabled can do it)
- bounds check sync periods and offsets passed in from the transport layer
- tell the user which resource a
On Fri, Mar 16, 2001 at 08:43:51 -0800, Alfred Perlstein wrote:
> * Sergey A. Osokin <[EMAIL PROTECTED]> [010316 08:27] wrote:
> > On Fri, Mar 16, 2001 at 09:27:30AM -0600, Dan Nelson wrote:
> > > In the last episode (Mar 16), Sergey A. Osokin said:
> > > > Hello, -currenters.
> > > >
> > > > Wh
I won't repeat the commit message here, but the new CAM error recovery code
has been committed to -current.
Note that error printouts are now a little more descriptive, so don't be
alarmed at that.
If there are any problems with the new code, send mail to
[EMAIL PROTECTED], or to [EMAIL PROTECT
On Sat, Apr 28, 2001 at 23:09:07 +0300, Tomi Vainio - Sun Finland - wrote:
> Hi,
>
> My source disk is quite noisy so normally I stop it after building the
> world and restart it once a week. Couple weeks this restart hasn't
> worked as before. Only way to start disk again is reboot.
>
> cam
On Sun, Apr 29, 2001 at 14:47:47 +0300, Tomi Vainio - Sun Finland - wrote:
> Kenneth D. Merry writes:
> >
> > Can you do the following:
> >
> > camcontrol stop da1
> > camcontrol tur da1 -v
> > [ then you can start it back up with camcontrol start
On Sun, Apr 29, 2001 at 14:47:47 +0300, Tomi Vainio - Sun Finland - wrote:
> Kenneth D. Merry writes:
> >
> > Can you do the following:
> >
> > camcontrol stop da1
> > camcontrol tur da1 -v
> > [ then you can start it back up with camcontrol start
On Mon, Apr 30, 2001 at 21:22:01 +0300, Tomi Vainio - Sun Finland - wrote:
> Kenneth D. Merry writes:
> >
> > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant
> > search and replace that caused the 'start' bit in the start/stop unit t
On Tue, May 01, 2001 at 22:03:37 +0300, Tomi Vainio - Sun Finland - wrote:
> Kenneth D. Merry writes:
> >
> > Hmm. Well, I definitely haven't seen this before. The only thing I can
> > figure is that we got into some sort of infinite rescan loop. I don't kno
I'm updating a machine (Pentium II 350, 128MB RAM) to -current, and ran
into this panic in the fxp driver. Sources are from today (5/1/2001).
I believe the chip is an 82557.
I compiled and installed a kernel, rebooted and started running an
installworld over NFS. The installworld stopped here:
On Sun, May 06, 2001 at 11:19:53 +0200, J Wunsch wrote:
> [F'up changed to freebsd-scsi]
>
> "Kenneth D. Merry" <[EMAIL PROTECTED]> wrote:
>
> > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant
> > search and replace that cau
On Mon, Aug 06, 2001 at 21:39:11 -0700, Arun Sharma wrote:
> On 7 Aug 2001 05:07:13 +0200, Daniel Eischen <[EMAIL PROTECTED]> wrote:
> > > At this stage diffs must be pushing close to 1MB (maybe more)
> > > (I don't know as I don't know yet how to get p4 to generate diffs :-)
> >
> > Isn't it jus
On Tue, Aug 07, 2001 at 09:36:01 -0700, John Baldwin wrote:
>
> On 07-Aug-01 Julian Elischer wrote:
> >
> > I have pushed the thread pointers down through most of the code
> > though there are still many many places that assume that there is only one
> > thread per process. (no multithreading ye
On Wed, Aug 22, 2001 at 07:02:54 +0200, Slawek Zak wrote:
> I have 2 such controlers in a Dell 6400. Both did work on 4.3-STABLE,
> updated about 4 weeks ago. After upgrade to 4.4-RC none of them is
> detected during boot. Did the ahc driver `suffer' some dramatic
> changes lately?
There was some
[ -arch and -current BCC'ed for wider coverage, please direct followups to
-net and/or me ]
I have put a new copy of the zero copy sockets and NFS patches, against
-current as of early September 5th, 2000, here:
http://people.FreeBSD.ORG/~ken/zero_copy/
Questions, comments and feedback are welc
On Sun, Sep 24, 2000 at 00:04:38 +0200, German Tischler wrote:
[ problems with SMP, but not UP kernels, I don't know anything about that ]
> Is anyone else seeing this ?
>
> Another strange thing is that cdrecord -scanbus tells me
>
> scsibus0:
> 0,0,0 0) *
> 0,1,0 1) *
On Tue, Oct 31, 2000 at 16:16:26 +0900, Akinori MUSHA wrote:
> At Sun, 29 Oct 2000 23:03:02 -0800 (PST),
> Kenneth Merry wrote:
> > ken 2000/10/29 23:03:02 PST
> >
> > Modified files:
> > sys/kern subr_diskslice.c
> > sys/sys diskslice.h
> > sys/ca
On Tue, Oct 31, 2000 at 16:16:26 +0900, Akinori MUSHA wrote:
> At Sun, 29 Oct 2000 23:03:02 -0800 (PST),
> Kenneth Merry wrote:
> > ken 2000/10/29 23:03:02 PST
> >
> > Modified files:
> > sys/kern subr_diskslice.c
> > sys/sys diskslice.h
> > sys/ca
[ -arch and -current BCC'ed for wider coverage, please direct followups to
-net and/or me ]
I have put a new copy of the zero copy sockets and NFS patches, against
-current as of early October 30th, 2000, here:
http://people.FreeBSD.ORG/~ken/zero_copy/
Questions, comments and feedback are welco
[ -arch and -current BCC'ed for wider coverage, please direct followups to
-net and/or me ]
I have put a new copy of the zero copy sockets and NFS patches, against
-current as of early November 14th, 2000, here:
http://people.FreeBSD.ORG/~ken/zero_copy/
Questions, comments and feedback are welc
[ -arch and -current BCC'ed for wider coverage, please direct followups to
-net and/or me ]
I have put a new copy of the zero copy sockets and NFS patches, against
-current as of early November 20th, 2000, here:
http://people.FreeBSD.ORG/~ken/zero_copy/
Questions, comments and feedback are welc
[ -net and -current BCCed for wider coverage, this is probably best
handled on -arch ]
I would like to request reviews of the zero copy sockets and NFS code I've
been posting about for months:
http://people.FreeBSD.org/~ken/zero_copy
There are diffs posted above against -current as of early Nov
On Sat, Jan 06, 2001 at 15:02:45 -0600, Russell Cattelan wrote:
> "Justin T. Gibbs" wrote:
>
> > >After upgrading my system from 13'th December to latest -current,
> > >the ahc driver doesn't attach to onboard AIC-7896 second channel
> > >anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are
On Wed, Jan 17, 2001 at 12:59:28 -0800, Jordan Hubbard wrote:
> Weren't the zero-copy patches supposed to make it into -current some
> time back? I recall a little grumbling over it since it made it
> necessary for some other projects to sync up their own work, but
> nobody seemed to object in pr
On Tue, Jan 30, 2001 at 08:41:44 -0800, Cy Schubert - ITSD Open Systems Group wrote:
> I just submitted a PR and patch in kern/24740 to fix a tagged queueing
> related filesystem corruption problem on CONNER CFP1080 drives. The
> patch adds an entry to the xpt_quirk_tabke. Anyone willing to comm
On Tue, Feb 06, 2001 at 00:15:27 +0100, Bernd Walter wrote:
> On Mon, Feb 05, 2001 at 09:34:44AM -0500, Trevor Johnson wrote:
> > I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od
> > driver for magneto-optical disks, which I got from his archives at
> > ftp://daemon.jp.freeb
On Thu, Feb 08, 2001 at 21:42:59 +0900, [EMAIL PROTECTED] wrote:
> From: Bernd Walter <[EMAIL PROTECTED]>
> Date: Wed, 7 Feb 2001 17:11:57 +0100
> > On Tue, Feb 06, 2001 at 11:21:12PM +0900, [EMAIL PROTECTED] wrote:
> > > Today I tried with 4.2-RELEASE (sorry not -current) and,
> > > 1. Boot up th
Peter Mutsaers wrote...
> Hello,
>
> When CAM was integrated someone reported that the aic driver was not
> ready yet for CAM, but that "Brian Beattie is
> working on it".
Right.
> At the moment, looking in LINT, it looks like aic still isn't
> supported. Is that true? Does anyone know whether
Ken Krebs wrote...
>
> In /usr/src/release/texts/RELNOTES.TXT it lists the following for
> supported adaptec controllers:
>
> Adaptec 1535 ISA SCSI controllers
> Adaptec 154x series ISA SCSI controllers
> Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
> Adaptec 274X/284X/
Edwin Culp wrote...
> I'm getting a lot of these SCSI disk errors from Current as of Sunday
> with the onboard Adaptec Controler with an IBM netfinity 3500. Can
> someone tell me if I should worry and/or what they mean?
>
> Thanks,
>
> ed
>
> (da0:ahc0:0:0:0): parity error during Data-In phase.
Matt Behrens wrote...
> Never mind. Apparently it went south on me while I was having
> lunch.
>
> I got this curious error when I paniced the debugger (paraphrased):
>
> HELP! busy_count is less then 0 (-1)
>
> Is this something of a clue? I've never been able to sync the
> drives at all by p
Gary Jennejohn wrote...
> Are there any plans to add devstat support to atapi-cd.c, a la scsi_cd.c ?
>
> Is it even considered to be desirable ?
I think it is desireable. I think the best person to do it is probably
Soren or someone else who is familar with the driver.
The thing you have to mak
Leif Neland wrote...
>
>
> On Wed, 27 Jan 1999, Archie Cobbs wrote:
>
> > Doug Rabson writes:
> > > And another thing. Why can't we use a non-driver-specific name for the
> > > disk? Most users simply don't care whether the driver was fd, wfd, wd or
> > > anything. They just want to get to th
Daren R. Sefcik wrote...
> Thanks..I ended up just pulling my old Atari out of the closet and doing
> the format on it...that seemed to work and I am now up and running. I
> would still like to know how to do it under FreeBSD.
First off, someone (can't tell who, because the attributions were dele
Daren Sefcik wrote...
> > You are, probably, using a wrong device name. First, check the file
> > /var/run/dmesg.boot to find out exactly how the drive was found --
> > what is the device number (da? something).
>
> >From dmesg.boot:
>
> (da0:adv0:0:1:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
Kenneth D. Merry wrote...
> Daren R. Sefcik wrote...
> > Thanks..I ended up just pulling my old Atari out of the closet and doing
> > the format on it...that seemed to work and I am now up and running. I
> > would still like to know how to do it under FreeBSD.
>
>
Mikhail Teterin wrote...
> Kenneth D. Merry once stated:
>
> =To format a disk, you would do something like this:
> =
> =camcontrol cmd -n da -u 0 -t 3600 -v -c "4 0 0 0 0 0"
>
> Yep, this similar to what the scsiformat(8) script was doing using
> the scsi(8)
Mike Smith wrote...
> > Thanks..I ended up just pulling my old Atari out of the closet and doing
> > the format on it...that seemed to work and I am now up and running. I
> > would still like to know how to do it under FreeBSD.
>
> If the disk wasn't being probed, then you can't format it, period.
I have just commited changes to devstat(9) that will require recompilation
of the following things:
libdevstat [ do this first! ]
systat
iostat
vmstat
rpc.rstatd
You'll have to recompile those things in order to use them with the new
kernel changes.
You will probably also have to recompile any
Ben Stuyts wrote...
> I've been getting the following message, usually within a minute or so after
> booting. It shows up only once, and doesn't seem to interfere with normal
> operation of the CDR:
>
> (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (cd1:ahc0:0:5:0):
Ben Stuyts wrote...
> On Sat, 13 Feb 1999, "Chris D. Faulhaber" wrote:
>
> > Interesting, this happens to both my CDR and regular CD:
> >
> > cd0 at ahc0 bus 0 target 3 lun 0
> > cd0: Removable CD-ROM SCSI-2 device
> > cd0: 10.0MB/s transfers (10.0MHz, offset 15)
> > cd0: Attempt to query device
Amancio Hasty wrote...
>
> SGI is releasing GLX 8)
>
> http://biz.yahoo.com/prnews/990216/ca_silicon_2.html
>
> Have Fun,
> Amancio
>
> P.S.: If companies start dumping large packages is going to weight us down :(
Heh. That's pretty cool. Although I wouldn't say that GLX itself
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)
> and sequential write is very slow.
> Compared to an IBM DORS-32160 connected to the same controller ( even th
Paul van der Zwan wrote...
> > 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 point
Matthew Jacob wrote...
>
>
> Well, yes, it can if the number of tagged commands you throw at a device
> overloads the sequencer so it can never really get started on the first
> command. If you don't disconnect, you don't throw multiple commands at
> the disk. I don't remember from the original m
Matthew Jacob wrote...
>
> If you're feeling kind, could you try and see if you could get a
> performance curve related to the number of outstanding tags allowed?
I will send him some diffs for camcontrol in a separate piece of mail that
will enable him to change the number of tags on the fly.
Dennis Glatting wrote...
>
> Just to throw my voice in, I get crappy SCSI performance on my
> three SCSI card Dell. I don't understand why.
Umm, you're going to have to be a little more specific than that.
You do have one of those slow Western Digital drives, which could cause
some problems.
>
Greg Lehey wrote...
> On Saturday, 20 February 1999 at 17:21:19 -0700, Kenneth D. Merry wrote:
> > Matthew Jacob wrote...
> >>
> >> If you're feeling kind, could you try and see if you could get a
> >> performance curve related to the number of outstand
Matthew Jacob wrote...
> > On Saturday, 20 February 1999 at 17:21:19 -0700, Kenneth D. Merry wrote:
> > > Matthew Jacob wrote...
> > >>
> > >> If you're feeling kind, could you try and see if you could get a
> > >> performance curve related
Dennis Glatting wrote...
>
> > > Just to throw my voice in, I get crappy SCSI performance on my
> > > three SCSI card Dell. I don't understand why.
> >
> > Umm, you're going to have to be a little more specific than that.
> >
> > You do have one of those slow Western Digital drives, which
> > coul
Matthew Jacob wrote...
> > >
> > > It sounds like a good idea, and it is. What I want to see is scsi_da use
> > > this automatically. I have never liked the "punch it, Chewey!" approach
> > > CAM has been taking.
> >
> > What do you mean "scsi_da use this automatically"?
> >
> > All of the t
Dennis Glatting wrote...
>
> > > On the ST410800W I am getting, according to iozone:
> >
> > FWIW, several people have reported bad performance with that
> > drive when tagged queueing is enabled. Their firmware
> > revisions, however, were 71xx, not 45xx. Apparantly drives
> > with firmware tha
Mikhail Teterin wrote...
> What's the chance the Adaptec-152x controller (aic0) will soon work
> with 3.1-STABLE?
I think the chances are very slim that it will work soon with 3.x or 4.x.
It may get done at some point, but I don't think anyone is actively working
on it at the moment.
> It has pre
Neal Westfall wrote...
> Not that I have one of these controllers, but I just received my 3.1
> cd set in the mail today, and happened to notice that the Adaptec
> 152x controller is listed on the back as supported, along with the
> Tekram DC390 (and other AMD 53c974 based boards). I was sure that
Joss Roots wrote...
> Hi thre
>
> I'm running -current (since about one month), and can't
> get cd-write to compile due to failure of the Tix
> port, anyone haas got the cd-write binary ?
>
> and will it run with out the Tix libraries installed.
>
> How are you people making CDs anyway.
> I ju
Mikhail A. Sokolov wrote...
> Hello,
>
> we're experiencing repeated 4.0-C (as of today, something around 12:00
> GMT, 1999-03-16) ufs_dirbad() panics, which are the
> following (below), which usually occur when squid is running. The box
> doesn't have ccd, nor vinum nor anything fancy in it's
Mikhail A. Sokolov wrote...
> On Tue, Mar 16, 1999 at 01:14:52PM -0700, Kenneth D. Merry wrote:
> # Mikhail A. Sokolov wrote...
> # > Hello,
> # >
> # I have no idea why you're getting a panic, but I do have a question...
> #
> # > syncing disks... 134 63
Ollivier Robert wrote...
> According to David E . O'Brien:
> > If not, can we PLEASE rename SCSI disks back to ``sd''?
>
> I'm tempted to agree. Many people I know who are upgrading to 3.* are
> somewhat pissed off by the renaming, even if it is in the release
> notes. They don't see any good reas
David O'Brien wrote...
> > And it's not like anyone had to upgrade their fstab -- all of the sd
> > devices still work, since the major number is the same. So there's not
> > a lot of room for complaint here.
>
> Only if sysinstall goes back to creating the /dev/sd* devices and
> matching fstab
Andrew N. Edmond (Nero) wrote...
> Our hardware vendor, in an effort to save us PCI slot space, fitted us
> with a new 3950U2B instead of the old 3940 (no longer in production!)
> cards we were used to. All documents on FreeBSD.org say that FreeBSD 3.1
> supports this card. However, /stand/sysins
Smelly Pooh wrote...
> Has the worm driver been taken out of current?
Yes. You have to use cdrecord now for SCSI CD burners.
> If so does the CAM CD driver
> handle ATAPI CD-Rs or what is the new way of doing it?
No, you need to use the IDE/ATAPI CDROM driver. wormcontrol will talk to
that dri
Here are patches against -current to add automatic detection of
CDROM drives that can't handle 6 byte mode sense and mode select:
http://people.FreeBSD.org/~ken/scsi_cd.cmdsize.20030214
These patches will be checked in in a few days if I don't get any
negative feedback.
Things fixed/changed in
On Sat, Feb 15, 2003 at 12:20:46 +0100, Thomas Quinot wrote:
> Le 2003-02-15, Kenneth D. Merry écrivait :
>
> > - Automatically detect CDROM drives that can't handle 6 byte mode
> >sense and mode select, and adjust our command size accordingly.
> >M
On Sun, Feb 16, 2003 at 22:45:14 -0700, Kenneth D. Merry wrote:
> On Sat, Feb 15, 2003 at 12:20:46 +0100, Thomas Quinot wrote:
> > Le 2003-02-15, Kenneth D. Merry écrivait :
> >
> > > - Automatically detect CDROM drives that can't handle 6 byte mode
> > >
spec, so that's
generally what it uses anyway.
Also, all sysctls in the da(4) and cd(4) drivers are accessible as
loader tunables now.
For the rest, see the commit message below.
Let me know if you see any problems resulting from this commit.
Ken
- Forwarded message from "Kenneth D.
I sent this out to the -scsi list earlier today. Testers would be
appreciated for the 6Gb LSI SAS driver.
Please follow up to me or the -scsi list.
Thanks,
Ken
- Forwarded message from "Kenneth D. Merry" -
Date: Fri, 10 Sep 2010 09:04:38 -0600
From: "Kenneth D
On Sun, Jul 20, 2003 at 09:13:51 +0200, Harald Schmalzbauer wrote:
> Hello all,
>
> while my CF-Card USB adaptor is crashing 5.1 and my NEC USB floppy also
> crashes 5.1 I found that sysctl -w kern.cam.da.no_6_byte=1 could help but it
> seems that this sysctl doesn't exist any more!
> Is there any
On Sun, Jul 20, 2003 at 19:40:58 +0200, Harald Schmalzbauer wrote:
> Andre Guibert de Bruet wrote:
> > On Sun, 20 Jul 2003, Harald Schmalzbauer wrote:
> >
> > > Kenneth D. Merry wrote:
> > > > > seems that this sysctl doesn't exist any more!
> > &
On Mon, Aug 25, 2003 at 13:49:30 -0700, Nate Lawson wrote:
> Ken is aware of the following problem. It is in both cd(4) and da(4) as
> well as stable and current. One possible approach would be to run
> {da,cd}register() from a task queue and not at interrupt time.
That would be tricky, since th
On Mon, Aug 25, 2003 at 19:25:42 +0200, Thomas Quinot wrote:
> Le 2003-08-25, Matt ?crivait :
>
> > db> trace
> > free_hcb(c40f1040,c03c7e40,101,c41d5800,c1528130) at free_hcb+0x2e
> > atapi_action(c40f1440,c41d5800,c0132b33,c41db000,c41d5800) at
> > atapi_action+ox56c
>
> OK, so that presumably
On Mon, Aug 25, 2003 at 18:29:49 -0600, Kenneth D. Merry wrote:
> On Mon, Aug 25, 2003 at 13:49:30 -0700, Nate Lawson wrote:
> > Ken is aware of the following problem. It is in both cd(4) and da(4) as
> > well as stable and current. One possible approach would be to run
>
On Wed, Aug 27, 2003 at 00:49:56 +0200, Martin wrote:
>
> Hi,
>
> I compiled world and kernel tonight (Aug 26th) on my Thinkpad
> R40 with a CD/RW drive. I tried my old settings with cam
> enabled so I can use cdrecord.
>
> During boot I got a kernel panic about 10 seconds after the
> kernel d
On Wed, Aug 27, 2003 at 16:54:05 +0200, Martin wrote:
> On Wed, 2003-08-27 at 02:27, Kenneth D. Merry wrote:
> > There are known problems with atapicam.
> >
> > Try enabling DDB in your kernel config, and get a stack trace. If you're
> > panicing in free_hcb()
I've figured out that after some recent posix1e upgrades (mac stuff?),
ifconfig -a will blow up if mac.conf isn't there:
# mv /etc/mac.conf /etc/mac.conf.backup
# ifconfig -a
fxp0: flags=8843 mtu 1500
inet 10.0.0.6 netmask 0xff00 broadcast 10.0.0.255
ether 00:30:48:21:bb:74
I've been working on a set of patches to remove the sysctl variable creation
from interrupt context in the cd(4) and da(4) drivers.
To fix the problem, I've created a new taskqueue that runs in a thread
context, instead of inside a software interrupt like the current task
queues. (The eventual f
On Sat, Aug 30, 2003 at 09:22:10 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Kenneth D. Merry" writes:
>
> >I think I have everything setup correctly, but I keep getting panics inside
> >the GEOM code with these patches. (Memory modi
On Sun, Aug 31, 2003 at 12:52:47 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Kenneth D. Merry" writes:
>
> >Anyway, I got some debugging output, and I've attached dmesg output. Let
> >me know whether anything in there looks suspic
On Mon, Sep 01, 2003 at 02:23:18 +0200, Pawel Jakub Dawidek wrote:
> On Mon, Sep 01, 2003 at 02:13:45AM +0200, Pawel Jakub Dawidek wrote:
> +> I was getting same panics while I was working on GEOM Gate.
> +> After many hours of debugging I've tracked this down - I've initialized
> +> a mutex, but I
On Wed, Sep 03, 2003 at 03:03:04 -0700, Don Lewis wrote:
> On 3 Sep, Michael Bretterklieber wrote:
> > Hi,
> >
> > buildworld fails (cvsup some minutes ago):
> > In file included from /usr/src/sys/cam/scsi/scsi_da.c:51:
> > /usr/src/sys/sys/taskqueue.h:33:2: #error "no user-servicable parts
> > i
On Thu, Sep 04, 2003 at 10:02:10 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]> writes:
> : Hello,
> : I have same problem as
> http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008948.html,
> : but with other PCMCIA card - new Proxim
On Fri, Sep 12, 2003 at 08:57:22 -0700, Kevin Oberman wrote:
> I am seeing a peculiar, possibly timing sensitive, crash that looks
> like if is probably in either atapicam or scsi_cd. The system is
> CURRENT as of yesterday morning.
>
> The crash happens frequently when nautilus starts up. It does
I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114
wireless router.
I've been trying to get the card and the router talking under FreeBSD.
(Both 802.11a and 802.11g work fine under Windows on the same machine.)
I'm using -current from September 15th.
Anyway, whenever I tr
On Wed, Sep 17, 2003 at 12:43:08 -0700, Sam Leffler wrote:
> > I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114
> > wireless router.
> >
> > I've been trying to get the card and the router talking under FreeBSD.
> > (Both 802.11a and 802.11g work fine under Windows on the
On Fri, Sep 19, 2003 at 08:22:13 -0700, Sam Leffler wrote:
> > Hmm. One other thing I'm seeing is that when I configure a 128 bit key
> > with ifconfig or wicontrol (wicontrol shows all 28 characters -- 0x plus
> > 26 hex characters), ifconfig still thinks it is a 104 bit key. This is
> > because
On Sun, Oct 12, 2003 at 10:26:54 -0700, Steve Kargl wrote:
> Can I assume that the following error messages are
> erronous because cd0 appears to function without
> any problems? There is a CD in the drive.
>
> cd0 at ahc0 bus 0 target 4 lun 0
> cd0: Removable CD-ROM SCSI-2 device
> cd0: 10.000
On Sun, Oct 12, 2003 at 14:29:38 -0700, Steve Kargl wrote:
> On Sun, Oct 12, 2003 at 02:51:50PM -0600, Kenneth D. Merry wrote:
> > On Sun, Oct 12, 2003 at 10:26:54 -0700, Steve Kargl wrote:
> > > Can I assume that the following error messages are
> > > erronous beca
I checked in a change to the CAM error recovery code that will hopefully
have a positive effect on systems with CDROM drives that were taking a
while to probe.
Anyway, try this out and let me know if there are any regressions.
Thanks,
Ken
- Forwarded message from "Kenneth D.
Andreas Dobloug wrote...
> * Kenneth D. Merry
> | > Has the worm driver been taken out of current?
> | Yes. You have to use cdrecord now for SCSI CD burners.
>
> cdrecord lacks support for a whole lot of CD-burners...
Oh really? The old Worm driver only supported HP/Philips
Andreas Dobloug wrote...
> * Kenneth D. Merry
> | > | > Has the worm driver been taken out of current?
> | > | Yes. You have to use cdrecord now for SCSI CD burners.
> | > cdrecord lacks support for a whole lot of CD-burners...
> | Oh really? The old Worm driver on
Daniel O'Connor wrote...
>
> On 06-Apr-99 Kenneth D. Merry wrote:
> > > I've got a Matsushita CW-7501. I'll send him a mail.
> > My guess is that cdrecord won't support it. See:
> >
> > http://www.fokus.gmd.de/research/cc/glone/e
Matthew Jacob wrote...
>
> Oh, very well, I'll have to say Perforce isn't that bad- it's just that it
> doesn't have a snappy set of tcl/tk GUI tools that allow you look at whole
> branch and revision histories..
I know there's a reasonable web-based tool that lets you look at revision
histories
I have just committed a number of CAM changes that will require
recompilation of any userland programs you have that access the CAM
passthrough driver. So things like cdrecord, xmcd, etc., should be
recompiled.
The best way to update your system is via make world.
NOTE: I would really like to
Eric Hodel wrote...
> I'm having trouble using tosha after the CAM changes, I updated source
> early this morning (around 7:00 PDT 5/7/1999) including ports, then
> make deinstall make distclean in /usr/ports/audio/tosha then make &&
> make install and tosha, and now tosha gives me (as root):
>
>
Eric Hodel wrote...
> "Kenneth D. Merry" wrote:
> >
> > Eric Hodel wrote...
> > > I'm having trouble using tosha after the CAM changes, I updated source
> > > early this morning (around 7:00 PDT 5/7/1999) including ports, then
> > > mak
Eric Hodel wrote...
> > Hmm, so you did a make world?
> >
> > I assume you mean "cdcontrol" above, and not "cdrecord". You can't pause,
> > play, etc., cds with cdrecord. cdcontrol uses the ioctl interface to the
> > cd driver, and so it shouldn't be affected.
>
> yes :(
>
> > Well, can you se
Eric Hodel wrote...
> "Kenneth D. Merry" wrote:
> > So I'm a little confused here. Does camcontrol work? Try this:
> >
> > camcontrol devlist
>
> camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for
> device
>
> > camcont
Wilko Bulte wrote...
> As Kenneth D. Merry wrote ...
> > Eric Hodel wrote...
> > > "Kenneth D. Merry" wrote:
> > > > So I'm a little confused here. Does camcontrol work? Try this:
> > > >
> > > > camcontrol devlist
> >
Matt Hamilton wrote...
> Dear All,
>
> I am trying to mmap a raw device (/dev/rda0) yet mmap() keeps returning
> EINVAL. From what I have read on the list archives, mmap() should be able
> to map a character device (just not a block device), am I missing
> something here?
>
> I have tried this o
101 - 200 of 342 matches
Mail list logo
