to manipulate the list itself, until time comes to destroy it.
Okay, but does this mean that bus_dmamap_load_mbuf no longer takes
a dmamap? Drivers may want to allocate/manage the dmamaps in a
different way.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
). This
example made me realize that the bounce code doesn't deal with
multiple segments being copied into a single page (i.e. tracking
and using remaining free space in a page already allocated for
bouncing for a single map). I'll have to break loose some time
to fix that.
--
Justin
To Unsubscribe: send
Chances are you are going to use the map again soon, so destroying
it on every transaction is a waste.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
settings with some devices.
These all seem quite normal.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
gates all interrupt activity. I don't
know that it will tell you why you are hung though. All that is clear
is that interrupts at least work for a time.
btw, thanks very much for your help!
Sure.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
or the aic7xxx driver. You
probably need to work with John Baldwin to trace the early
execution of the system to see why it is haning up.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, the transaction is already complete. This
usually indicates (as the driver mentions) a problem with interrupts.
Perhaps one of the SMPng guys may know why this is happening. At this
point, I don't believe that it is an aic7xxx specific bug.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED
language correctly.
Perhaps this could be configured directly via the language table or
keymap? Whatever the solution, it should be automatic with the
configuration of a locale change.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
kicks our ass in caching meta-data unless you have
a lot of memory. That sucks.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
There's no downside, really.
It just seems inelegant to have a system that, on paper, is
so inefficient. Can't we do better?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
fraction of that size.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
Just had one of these on yesterday's -current. Anyone interested in the
details?
Nah. Its probably just you, or something specific to your system.
It couldn't possibly be a bug in *my* code.
;-)
Of course I'm interested!
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED
a
copy of the dump handy, but the offending controller is a 7895 (possibly a
7899 [39160] but I think the 7895 gets hit first)
I really need the complete set of messages printed out prior to the panic.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
On Fri, 30 Mar 2001, Justin T. Gibbs wrote:
I really need the complete set of messages printed out prior to the panic.
Okay, here yer go (transcribed using hi-tech ballpoint and scribbly
handwriting, I'm afraid!)
This is certainly a bug, but some things about what you've written
make me
Dear Justin,
Since the update around the middle of feb of the ahc driver the aic7892
chip is no longer supported correctly. The same card with aic7870 is
working as usual. So I think that this is the problem. The snapshot
(2001/02/10) of the current version is OK.
Can you give me the revision
I've just tested both -current and -stable on a card with identical
specs. Can you provide more inforamtion on where the attach fails
(e.g. add printfs)?
### 29160 BIOS v.2.57.2
### pciconf
aries# pciconf -l
ahc0@pci0:9:0: class=0x01 card=0xe2a09005 chip=0x00809005 rev=0x02
--
Justin
l have to instrument
the driver to find out where the attach is failing. Start by going
into aic7xxx.c:ahc_init() and adding a printf to all of the early
returns. If that doesn't catch it, do the same for
aic7xxx_pci.c:aic7xxx_config(). I'll add this logging the next
time I touch th
exhibited this problem. Unfortunately
I don't, so it has been difficult to get the workaround for this
particular hardware bug correct.
Can you see if this patch works for you?
--
Justin
Index: aic7xxx.c
===
RCS file: /usr/cvs/src/sys/d
"Justin T. Gibbs" [EMAIL PROTECTED] wrote:
It is not necessarily sufficient since the media may be changed after
open on certain types of devices that don't have a media lock.
But don't you risk a panic if you do that?
By pulling the media out and flipping off the hardware write prot
of devices that don't have a media lock. Some
devices will only tell you that they are write protected on the first
write, etc. For the devices where we can tell, we should make the check
in open, but not rely on that catching all cases where a driver will
return EACCESS.
--
Justin
To Unsubscribe
"WARNING" printf in aic7xxx.c? I'm trying to reproduce this here as
well. I don't know what I've changed that could cause the qoutfifo
to become confused. How many drives do you have on the controller?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
latest checkin corrects the problem. Please let me know if you
experience any additional difficulties.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
their
nic address the same way.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the mac address wrong for one of my xircom
cards but not so wrong as to make it non-functional. The other
xircom card (the type-III with modem) seemed to end up with a
mac address that was considered invalid by many switches.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED
perl -pi -e "s:^V^M::g" Gibbsdiffs # How come... :-)
That's MH's mime for you.
Summing up: SCSI seems to work like a charm.
The patch has been committed to both -current and -stable.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
Dear FreeBSD'ers,
I am running -CURRENT as of today (sources as of ~ 18:15 GMT). I can
see the following (a # sign precedes my comments):
Can you see if this patch corrects the problem?
--
Justin
Index: dev/aic7xxx/aic7xxx.c
tached to the Mylex card are 2 x 4.3GB Fujitsu UW SCSI drives, set up
as a single mirrored pair. It all works fine with NT4, but that's not
an option for this server.
Regards and best wishes,
Justin Clift
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ontrollers.
Are you sure that your drives aren't just attached to the second port?
Have you tried a current since Friday? I committed a fix for the
original problem that was reported.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
My guess
is that your MB vendor did not use the correct subsystem ID for the
aic7896 to enable the second channel. We only recently started to
pay attention to this. What MB is this?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
this
protection without requiring any locks. Other than having to aquire
Giant at thread starup (as most code below us is not thread safe yet),
I don't see any other locking requirements.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
this won't tell you if your interrupt thread has already been dispatched
but the interrupt source has gone away (card was removed, so interrupt
line is dead). Hmmm.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
brand
new 256MB modules and installed them. It is still happening.
This is a production environment type of server. I've had no other problems
with FreeBSD 4.2-S, and i'm hoping maybe this is something that has been
fixed.
--
Justin W. Pauler (drnet)
E-Mail: [EMAIL PROTECTED]
WWW: http://www.j
"AGP data structures");
from
MALLOC_DEFINE(M_AGP, "agp", "AGP data structures");
in the latest pci/agp.c.
CC me as I'm not on the list. (I know, but I can't cope well with that
type of mail volume...)
Justin A. Kolodziej
To Unsubscribe: send mail to [EMAIL PROT
that facilitates walking the CIS that can be used
at anytime.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
That's what I mean. You call this, and it will remap the CIS (if it
has been unmapped), walk it for you and pass you a pointer to each CIS
entry one at a time to the function you specify.
Warner
I'd rather have a seek/read interface than have a callback.
--
Justin
To Unsubscribe: send mail
of having a seeking interface might be necessary.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
implemented for function 0 and the ROM
contains information for all functions of the chip. So, functions
greater than 0 must have the flexibility to activate at least the ROM
BAR on function 0 as well as access that region.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
I'll have to look up the CIS_PTR spec. I'm not sure I like hardwiring
things like this.
Where did you get a copy of the pccard spec? Do you have to order
it from the pcmcia SIG?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
ill always grow in
4K increments from its parent resource pool. The parent would then
grow according to its own requirements, etc.
--
Justin
Index: dev/cardbus/cardbus.c
===
RCS file: /usr/cvs/src/sys/dev/cardbus/cardbus.c,v
retrievin
-On [20001109 21:30], Justin T. Gibbs ([EMAIL PROTECTED]) wrote:
If possible, please include a contact name, email, or phone number so
we can ask additional questions if necessary.
Do foreign educational institutes count as well for this purpose?
Yes.
--
Justin
To Unsubscribe: send mail
, this wouldn't be
an issue any longer.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
be referenced while the chip is in a paused state.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
cards are identified using ISA probe
techniques in all cases I'm aware of. It just turns out that the 2842
uses a scheme that is very similar to that of an EISA card.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
. VL cards are identified using ISA probe
techniques in all cases I'm aware of. It just turns out that the 2842
uses a scheme that is very similar to that of an EISA card.
As a backgrounder for other-than-Justin, Adaptec has a habit of
making multipurpose ROMs that sit on different types of devices
How do we use the EISA BIOS on an Alpha or an SGI though?
I believe thorpej recently committed some code in NetBSD to do this
on the Alpha.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
we can
ask additional questions if necessary.
Thanks in advance for your help!
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
for good reason),
so a conventional 'To' line didn't work.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The IRQ allocation needs the RF_SHAREABLE flag or it will blow up in
the case where the IRQ is shared with another device.
So the EISA attachment doesn't set RF_SHAREABLE if the system is
using a level sensitive interrupt?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED
On Wed, 8 Nov 2000, Justin T. Gibbs wrote:
So the EISA attachment doesn't set RF_SHAREABLE if the system is using
a level sensitive interrupt?
The current EISA code isn't as smart as it should be.
Speaking of that, I'd like to see the EISA code move to be
more like PCI. We should see
nonvolatile region in the ELCR, but I could
never find out how to do this.
Humm...
Try ftp://ftp.jurai.net/users/winter/eisabook.zip
I can't seem to fetch it. Permission denied.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
EISA bus blindly.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Humm... I had wondered why that was there. Is there a way to detect VLB
devices some other way?
This is specific to the aha2842 and is the only way I know of detecting
those boards.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
o the
card that is having problems under FreeBSD without any difficulty.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
n -current.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
,c877af80,80b4348,80b5028,80b4300) at lstat+0x41
syscall2(2f,2f,2f,80b4300,80b5028) at syscall2+0x33c
Xint0x80_syscall() at Xint0x80_syscall+0x1f
Since addaliasu doesn't bother to check for NODEV, I take it this is
a "can't happen" situation?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
Please test review this patch:
http://phk.freebsd.dk/patch/offsetof.patch
I believe that several drivers include stddef.h to get
offsetof. I think most of these files are flagged by
"/* for offsetof */".
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
Attached is the end of the .out file where my error occurs. Thanks for
any help.
~Justin
=== libdevstat
cc -O -pipe -I/usr/src/lib/libdevstat -I/usr/src/lib/libdevstat/../../sys
-I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libdevstat/devstat.c -o devstat.o
building standard devstat
What would cause freebsd -current to lock up when i telnet, ftp, or ssh to
it? Somthing with inetd?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens ([EMAIL PROTECTED])
System/Network Administrator
http://www.lostworld.net
http://resume.lostworld.net -- Personal
N.M. it seems to be somthing with my kernel, i booted up off an older
kernel (4.1-STABLE) and i can telnet to it, so im going to try and make a
new config file and recompile my kernel..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens ([EMAIL PROTECTED])
System
I have a little Q: when i compile my kernel for 5.0-CURRENT
[root@calloc:/usr/src/sys/compile/CALLOC]# make install
You must activate /boot/device.hints in loader.conf.
*** Error code 1
How do i activate it?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens
I didn't see it in UPDATING but i figured it out.. :P
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens ([EMAIL PROTECTED])
System/Network Administrator
http://www.lostworld.net
http://resume.lostworld.net -- Personal Resume.
"I dread success. To have succ
suscribe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens ([EMAIL PROTECTED])
System/Network Administrator
http://www.lostworld.net
http://resume.lostworld.net -- Personal Resume.
"I dread success. To have succeeded is to have finished one's business
on
to. Is there a BSD option to 'keep-alive' the
connection so I do not time out? I would prefer not to leave an X session
opening refreshing CNN every five minutes :P
Your help and/or scripts are
welcome :)
Justin W. Pauler
JWPages Web Development
[EMAIL PROTECTED]
I still can't get remote GDB to work correctly in a 5.0-current
environment at speeds greater than 9600bps. Is anyone else
experiencing similar results? I thought that grog had fixed this...
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
On Wednesday, 14 June 2000 at 11:05:41 -0600, Justin T. Gibbs wrote:
I still can't get remote GDB to work correctly in a 5.0-current
environment at speeds greater than 9600bps. Is anyone else
experiencing similar results? I thought that grog had fixed this...
So did I. Are you just getting
?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
kernel)
the error message
"ahc0: brkadrintr, Data-path Parity Error at seqaddr = 0x14e"
occurs.
any ideas, that could help?
I just want to make sure. Is your problem fixed now?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ic' device, but I do notice
some odd behavior if I move the trackpoint really fast. I've always
assumed that this was from a spurious double-click event caused by pressing
on the trackpoint, but I could be wrong.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
found on Thinkpads?
The version on my 770X has a double click by "pushing hard on the
trackpoint" feature. It also has the ability to do the scroll
thing if you hold the middle mouse button and move the trackpoint.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
; state: Exp; lines: +24 -3
Teach pkg_delete and pkg_info how to deal with full pathnames
(/var/db/pkg/foo-1.0, instead of just foo-1.0).
Submitted by: Matthew D. Fuller [EMAIL PROTECTED]
If no one else fixes it, I'll try to look at it later today.
Thanks,
Justin
To Unsubscribe: send mail
for the target to request the next
byte at the time this occurs, but that request never comes.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
connector had been loose
for a long time and has just shifted to the point of causing a failure.
Open your case, reseat everything and see if the problem clears up.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Justin T. Gibbs wrote:
It looks like both nsio and sio have PCCARD support disabled at the
moment. Is there any other way I can get the system to recognize my
modem?
Fix the broken sio, it might be KNF and all but it doesn't work...
-Soren
The pccard brokenness is not sio's fault
not provided a
buffer with any data in it.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It looks like both nsio and sio have PCCARD support disabled at the
moment. Is there any other way I can get the system to recognize my
modem?
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'm noticing some new output. What does it mean and is it going
to stay there? :-)
Peter killed these last week.
- Jordan
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
and interrupts end up being serviced
by the dummy probe routines.
Do you record this stuff anywhere? I think we should have a Bruce's
nits page so this stuff isn't forgotten.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
In message 199905192231.qaa09...@narnia.plutotech.com, Justin T. Gibbs wri
t
es:
In article 199905191637.jaa03...@dingo.cdrom.com you wrote:
I'm not sure why it happens like this; try putting a DELAY() just
before we actually set the root device and see if you can put it off.
Why not just spl
. There
are also devices like scanners and older WORM devices that can take
up to a minute to become ready. It seems quite silly to me to hold
up booting for devices that are not even referenced during boot.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current
into the console buffer?
This would just move the race. It is probably already elsewhere for
serial consoles.
Perhaps I should use the log facility instead of printf in the announce
code?
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
into the console buffer?
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
are primarily
from the fact that NetBSD has enhanced or modified their interfaces
since my original work and I haven't found the time to sync us back
up.
Warner
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
.
There seems to be some relation to how recently the last lot of tape activity
was (althought this is rather tenuous).
It would be usefull to see the ps -l output for the hung process so
we know what resource it is blocking on.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
use MMC now and cdrecord supports MMC
devices. Why write another utility if there is already one that speaks the
necessary language that our users are familiar with?
OK, I'm done discussing this (se my other mail), I'd rater spend
my (very limitted) time productively.
Fair enough.
--
Justin
are slightly different.
But hey, I don't have the time to work on ATAPI. Soren does, so he gets
to call the shots.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
than
by device node too - it would practically eliminate the need for hard
wiring of devices.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
I half suspect that what Justin had in mind at some point was a set of common
code that is either #ifdef'ed or otherwise preprocessed to produce a
standalone 'SCSI-CAM' system versus an 'ATA[PI]-CAM' system. This would
have the advantage of having all the common code together in one place
peripheral driver here, but CAM doesn't tie your hands
one way or the other.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
. Until DEVFS is a reality,
the kernel will still need to perform a name to major number translation,
but it should be left up to the kernel.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
# Are you *sure* you're running -current as of today? Justin put code in to
# silence Illegal request error messages from the sync cache command.
These messages, since they are occurring only during a panic, are caused
by the code in dashutdown(). I didn't modify this code in my last checkin
for web server, file server, and other-server types of uses, and haven't seen any (reports of) leakage like this.
I'll look more closely at the results we see, to verify that we don't have a problem.
Regards,
Justin
From: Chris Csanady ccsan...@friley-185-205.res.iastate.edu>
Date: 1999-02-1
that was fixed a day or so later.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
.
--
Justin
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
201 - 293 of 293 matches
Mail list logo
