y useful, and it owuld be quite
nice to have them for the standard subsystems -- I found find
it far more convenient to type eg 'amdc restart' instead of
'killall amd && . /etc/rc.conf && amd -p ${amd_flags}' :)
Thomas.
--
Thomas Quinot ** Département Informatiq
the setuid bit is set on the
client binary.
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
... because it walks through the entire NIS db just to find out what the
longest user name is (/src/usr.bin/top/machine.c 1.5). At this site,
this means 2800 RPC calls and dozens of seconds when the network and/or
NIS server are busy.
What do others think of the following patch?
Thomas.
--- mac
m this afternoon, I can launch an X client
on the -CURRENT box and have the X connection forwarded to my
-STABLE desktop machine.
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Un
Le 2001-09-08, Nick Hibma écrivait :
> Why don't you add an early-out for namelength => 15 or put the
> if-statement in the loop:
Well, in my case all usernames are <= 8 characters, so the proposed
changes would not prevent a complete walk of the NIS db.
Thomas.
--
[EMAIL PROTECTED]
To U
Le 2001-10-10, Thomas Quinot écrivait :
> > Sep 28 09:47:19 hunter amd[309]: /net: mount: No such file or directory
> > Sep 28 09:47:19 hunter amd[309]: extra mkdirs required for /net
> > Sep 28 09:47:19 hunter amd[309]: amfs_toplvl_mount: mount_amfs_toplvl faile
ser.enst.fr: error 5 (RPC: Timed
out)
-rw--- 1 quinot astre474 Oct 18 14:17 photos-ta
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECT
4.4-RELEASE (which works) and -current
> (which doesn't).
> Both versions get it wrong. I have no idea why 4.4-RELEASE worked.
Thanks for this information!
I have opened a PR on that problem earlier yesterday: kern/31479.
--
Thomas Quinot ** Département Informatique
below.
Seems to work. Thanks!
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Le 2001-11-13, Stijn Hoop écrivait :
> Just curious, but how is the patch progressing?
For the moment I am expecting feedback from the testers who have
reported problems booting with the patch (esp. on SMP machines).
> Can I try this out on a -STABLE system somehow?
Yes, the patch available fr
Le 2001-10-10, NAKAMURA Kazushi écrivait :
> % inc +inbox
> ...(many minutes)...
> inc: unable to lock and fopen /var/mail/kaz
I have been having problems with NFS client locking on -CURRENT for
some time, cf. PR bin/27231.
Thomas.
--
Thomas Quinot ** Département Informatique
et
> Sep 28 09:47:19 hunter amd[309]: amfs_toplvl_mount: mount_amfs_toplvl failed:
>Operation not supported by device
Problem reproduced here, and resolved likewise (by kldload'ing
nfsclient) with a freshly-cvsupped -CURRENT.
Thomas.
--
Thomas Quinot ** Département Inform
defined in libc.so.5).
Shouldn't the major for libm have been bumped as its ABI was changed?
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EM
Ooops. This was discussed here recently. That's what I get for not
reading -CURRENT when on holidays *and* not grepping enough of the
backlog. Sorry.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PA
Currently, when reboot is invoked with the '-p' command line flag
(powerdown), it performs a shutdown with RB_HALT|RB_POWEROFF.
In some situations, it can be useful to try to perform a poweroff,
but reboot if it fails (e.g. when you are shutting down the system
as a result of a power failure, you
Le 2001-12-27, Garance A Drosihn écrivait :
> If I understand your request, you would want
>shutdown -p now
> to behave the same as
>shutdown -r now
> if the operating system does not know how to power down the hardware.
> Is that what you want?
Actually what I want would
;;
- esac
-
- if [ -n "${amd_flags}" ]; then
- amd -p ${amd_flags}\
- > /var/run/amd.pid 2> /dev/null
- else
- amd 2> /dev/null
-
Le 2002-01-08, Thomas Quinot écrivait :
> case ${nfs_client_enable} in
> [Yy][Ee][Ss])
> +kldload nfsclient && nfsclient_in_kernel=1
Ooops, this is *far* too aggressive!
Here is a corrected version of the previous patch. Sorry!
Le 2002-01-08, Sheldon Hearn écrivait :
> Nits follow:
[ whitespace ]
[ style ]
> I'd suggest getting your patch tested by -CURRENT users by posting the
> patch to the freebsd-current mailing list.
I have produced a new diff that incorporates the changes suggested
by Sheldon. Those interested
> Is there a place where I can find this updated patch which will work for
> me in the current -current? Thanks.
I put up updated patches at
http://www.cuivre.fr.eu.org/~thomas/atapicam/
For -CURRENT, you should be using the latest one (of today)
which fixes a silly line inversion.
I'd be v
> Is there a place where I can find this updated patch which will work for
> me in the current -current? Thanks.
I put up updated patches at
http://www.cuivre.fr.eu.org/~thomas/atapicam/
For -CURRENT, you should be using the latest one (of today)
which fixes a silly line inversion.
I'd be v
ibutes for /usr"),
and I am left with an empty kernel export list.
This used to work with 5.0-CURRENT as of a few months ago.
Shouldn't such an export work as expected?
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 r
ce...)
> m: "A, you are correct, now get cracking!"
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ymore. All I get
is the following on stdout:
Formatting page, please wait...mdoc error: end-macro (.em) respecification is not
allowed. (#41)
Should this have been `.Em ...'?
User Abort.
Done.
Sources are from cvsup a few hours ago from now.
Thomas.
--
Thomas Quinot **
Le 2001-04-18, Ruslan Ermilov écrivait :
> cd /usr/src/gnu/usr.bin/groff/tmac && make cleandir obj && make all install
It works here, thanks!
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75
happening? :)
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
servconf.c serverloop.c \
+ auth.c auth1.c auth2.c auth-options.c session.c dh.c \
auth-pam.c
MAN= sshd.8
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send
Le 2001-05-28, Matthew Jacob écrivait :
> On startup:
> May 28 10:16:04 farrago mountd[216]: can't delete exports for /
Same here with -CURRENT as of today.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault /
ching rpc.lockd with truss shows that the crash occurs (shortly)
after it has forked.
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECTED
he Kernel Debugging section of the
> FreeBSD handbook for instructions on how to obtain such information.
Will try that, thanks.
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscri
lps to at least find out
where precisely the error occurs. Or maybe I could add a call to panic()
when the faulty trap occurs, which would drop me into DDB?
Thomas.
--
Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault //
Le 2001-04-23, Thomas Quinot écrivait :
> deterministic fashion. It also tends to leave the mailbox locked on the
> server even after quitting. Running lockd with debugging enabled did
> not show anything that looks like an abnormal condition.
I am still seeing this problem on -CURR
Looks like the stack got horribly corrupted... Bonus points for double
panic while dumping.
This is 5.0-RELEASE running on a Dell Inspiron 8200 laptop with ACPI
disabled (it crashes once or twice per day when ACPI is enabled).
Fatal trap 12: page fault while in kernel mode
fault virtual address
Le 2003-02-05, Tim Robbins écrivait :
> Since revision 1.11 of src/usr.sbin/cron/lib/env.c, you need to put the
> value of the environment variable inside quotes if it contains any spaces.
> I suspect that this change of behaviour was unintentional given that the
> implementation differs from the
Le 2003-02-07, CHOI Junho écrivait :
> Oops. It doesn't solve the problem. There is no error when editing
> crontab, but the variable is not substituted correctly(just blank).
Hum, strange, it seemed to work here. Can you send me your crontab and
the output of 'cron -x pars' ?
Thomas.
--
[
Le 2003-02-08, CHOI Junho écrivait :
> Oh sorry... I didn't restart cron :P. It works well. 'cron -x pars'
> says that whitespaces is correctly parsed.
OK, that's reassuring! Ollivier can you review the posted patch please?
Thanks,
Thomas.
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to
On a Dell Inspiron 8200 laptop, with ACPI disabled, 5.0-REL rebooted
while the system was quiescent. gdb appears to be unable to make sense
of the produced crash dump:
# gdb -k /usr/obj/usr/src/sys/MALEVIL/kernel.debug vmcore.1
GNU gdb 5.2.1 (FreeBSD)
[...]
This GDB was configured as "i386-undermy
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.
>More information on that below.
>
> - MODE_SENSE and MODE_SELECT translation removed in ATAPICAM and in
>t
Le 2003-02-16, Chris BeHanna écrivait :
> Do you use cvs2p4? How about going in the other direction (from your
> local branches back to the trunk?)
VCP is also a nice solution for moving changes across CVS and Perforce
repositories. I use it to update a read-only CVS pserver view of a
project th
Le 2003-02-05, Thomas Quinot écrivait :
> #13 0xc032f438 in calltrap () at {standard input}:98
> #14 0xc030652c in vm_page_wakeup (m=0x0) at /usr/src/sys/vm/vm_page.c:324
Got the same one again last night circa 04:30, while the machine was
completely idle (except for an xscreensaver p
* Randy Stewart, 2010-09-02 :
> And now my backup to atapi-cam is failing.. I get:
>
> r...@lakerest /usr/tmp]# /usr/local/bin/growisofs -Z /dev/cd0 -R -J
> backup_init.08-31-2010.gz
> :-( unable to CAMGETPASSTHRU for /dev/cd0: Inappropriate ioctl for
> device
Would be interesting to see the
Le 2003-08-24, Matt écrivait :
> This did work perfectly with the old ATA, but the new ATA panic's. I have
> found that it is due to having device atapicam for the SCSI emulation. If I
I'll need a backtrace please.
Thanks,
Thomas.
--
[EMAIL PROTECTED]
__
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 means we're going through action_oom, and so you
should have had one of the f
Le 2003-08-25, Matt écrivait :
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x0
> fault code = supervisor write, page not present
> instruction pointer = 0x8:0xc015e59e
> stack pointer = 0x10:0xd717bac0
> frame pointer = 0x10:0xd717bacc
> code segment = base 0x0, limi
Le 2003-08-27, Lee Damon écrivait :
> Removing atapicam from my kernel configuration fixed the problem
> for me as well.
Please try the patch I posted on -current under "HEADS UP! ATAng
committed".
Thanks,
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL
Le 2003-08-29, Glenn Johnson écrivait :
> When I have atapicam enabled in my kernel config (-current, as of
> Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
> nautilus. Nautilus loads fine after removing the atapicam option.
> Atapicam worked fine prior to ATAng.
Strange. No
Le 2003-08-29, Glenn Johnson écrivait :
> console. There was nothing written to the log file that I remember but
> I should check that again tonight when I get home. I will also try to
> ssh in from another machine and see if the network is still up.
Yes. A serial console could also perhaps pr
Le 2003-08-30, Glenn Johnson écrivait :
> I guess I wrote that too soon, it just locked up again. This time
> though, the machine rebooted after about 10 seconds so I could not get
> to another machine to see if I could poke around.
If it rebooted, then maybe it panic'd. Do you have a kernel cor
Le 2003-09-12, Kevin Oberman écrivait :
> cdstart(c419d500,c4192000,1,c407cc30,c407cc00) at cdstart+0xcb
> xpt_run_dev_allocq(c40b8c00,c407cc08,1,c418d800,c419d500) at
> xpt_run_dev_allocq+0xab
> xpt_schedule(c419d500,1,0,ce54ec78,dd5b6c70) at xpt_schedule+0xca
> cdstrategy(ce54ec78,0,0,0,d439f00
Le 2003-09-15, Lee Damon écrivait :
> >Yesterday's cvsup'd and compiled kernel hung at
> > acd0: CDRW at ata1-master UDMA33
> > atapicam0: timeout waiting for ATAPI ready
This is from the low-level ATA layer. Do you see the same message if you
disable ATAPICAM?
Thomas.
--
[EMAIL
Le 2003-09-13, Daniel Eischen écrivait :
> cd0 at ata1 bus 0 target 0 lun 0
> cd0: Removable CD-ROM SCSI-0 device
> cd0: 33.000MB/s transfers
> cd0: cd present [3737169375 x 3737169374 byte records]
Several others have reported similar completely bogus sector size data.
I suspect a problem in t
Le 2003-09-06, Petri Helenius écrivait :
> Should this work or is the work to port this to ATAng still undergoing?
This should work, but does not, so the work is still in progress...
> panic: mutex Giant not owned at ../../../dev/ata/atapi-cam.c:117
Please try this patch.
Index: atapi-cam.c
=
Le 2003-09-06, Guillaume écrivait :
> I'm running FreeBSD 5-CURRENT (Aug. 28 2003) on a P3 733MHz, 768MB ram
> with a LG DVD-RW/DVD-RAM burner. I would like to know why ATAPICAM is so
> slow with my system.
Maybe because ATAPI/CAM does not actually enable DMA. Can you try the
following patch?
Th
Le 2003-09-16, Daniel Eischen écrivait :
> I get this even without atapicam in the kernel. Is trying
> CAMDEBUG and CAM_DEBUG_CDB going to show anything interesting?
No, indeed, probably not. Can you try the following patch:
Index: ata-lowlevel.c
Le 2003-09-17, Guillaume écrivait :
> > + if (atapi_dma && atp->channel->dma &&
> > + (atp->param->config & ATA_DRQ_MASK) != ATA_DRQ_INTR)
> > + atp->setmode(atadev, ATA_DMA_MAX);
> > + else
> > + atp->setmode(atadev, ATA_PIO_MAX);
Ahem. Replace atadev with atp on both lines
Le 2003-09-17, Bryan Liesner écrivait :
> The patch seems to work, my cd0 and cd1 lines in the dmesg now report
> 33.000 MB/s insetad of 3.300 MB/s.
OK, good, so that's one half of the problem resolved. Now, can you test
whether the actual performances are improved or still slow?
Thomas.
--
Le 2003-09-18, Jan Srzednicki écrivait :
> Anyway, here's backtrace for atapicam panic I've mentioned. It's
> triggered by:
>
> cdrecord dev=1,1,0 /some/track
Um. Do you see the same crash if both drives contain CDs at boot time?
If not, this could be a consequence of the error condition corrupt
Le 2003-09-19, Guillaume écrivait :
> Thanks for the patch. cd0 is faster now and ATAPICAM works great.
That's good news!
> Are you going to commit the patch?
Yes, the patch is currently being reviewed.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED]
Le 2003-09-20, Daniel Eischen écrivait :
> No, using latest sources, with or without atapicam, does
> not solve the problem. It still hangs.
Please try the patch below, it should at least work around the problem.
> http://people.freebsd.org/~deischen/ata_hang.091903
Interesting, the last 2 l
Le 2003-09-20, David R. Colyer écrivait :
> Is atapicam a kernel config option?
It is a device (cf. man atapicam): you can enable it with
"device atapicam" in your kernel config file.
> I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi
> cdrw locks my system and then
Le 2003-09-19, Dan Naumov écrivait :
> Disabling atapicam in the kernel or detaching the drive from the system
> works around the problem.
Please try the patch I posted a few moments ago under "ATAng no good for
me/REQUEST_SENSE recovered from missing interrupt".
Thomas.
--
[EMAIL PROTECTE
Le 2003-09-20, Shin-ichi Yoshimoto écrivait :
> > acd0: WARNING - REQUEST_SENSE recovered from missing interrupt
> This message disappeared, but It still hang
Can you get a backtrace at that point?
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] maili
Le 2003-09-21, Dan Naumov écrivait :
> (probe2:ata1:0:0:0): Recovered Sense
> (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0
> (probe2:ata1:0:0:0): CAM Status: SCSI Status Error
> (probe2:ata1:0:0:0): SCSI Status: Check Condition
> (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0
> (probe2:ata1:0
Le 2003-09-21, Bryan Liesner écrivait :
> The patch doesn't take care of the hang for me.
Does it change anything, or do you still see the 'REQUEST_SENSE
recovered from missing interrupt'? Is your source tree up-to-date?
Several fixes have been committed to both the ATA and the CAM subsystems
rec
Le 2003-09-21, Shin-ichi Yoshimoto écrivait :
> I could not get a backtrace because infinite loop occured like this:
Can't you drop into DDB at that point? Also, do you have up-to-date
sources?
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] m
Le 2003-09-21, Daniel Eischen écrivait :
> Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error
> Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition
> Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): Recovered Sense
> Sep 21 12:40:28 sirius kern
Le 2003-09-21, Bryan Liesner écrivait :
> Thanks, the hang problems are fixed now.
That's great news!
> No one told me that I was barking up the wrong tree...
Ah, computers are fragile and playful things that always find creative
and unexcepted ways of failing... :)
Thomas.
--
[EMAIL PRO
Le 2003-09-22, Dan Naumov écrivait :
> Speaking of failing, should I completely disregard the probe2:ata1
> warnings during boot which you saw in the dmesg output I sent you ?
Yes, these messages are perfectly inocuous, they mean that your CD drive
does not provide serial number information. You
Le 2003-09-22, Matthias Andree écrivait :
> I'm getting complaints from ata or atapicam during boot-up, but my
>From CAM actually, and you can safely ignore them.
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebs
Le 2003-09-21, Sascha Holzleiter écrivait :
> i still have problems with atapicam and atang, while booting with
> atapicam i get these messages:
There is nothing abnormal with these messages.
> When trying to burn a disk with cdrecord i get the following panic:
> panic: mutex vm object not own
Le 2003-09-19, Guillaume écrivait :
> Thanks for the patch. cd0 is faster now and ATAPICAM works great.
> Are you going to commit the patch?
DMA is now enabled for ATAPI/CAM i/o, as of atapi-cam.c rev. 1.26.
Thanks to all who tested and reviewed the change.
Thomas.
--
[EMAIL PROTECTED]
___
Le 2003-10-04, Jan Stocker écrivait :
> are printed so fast i cant really read but it must be something
> like that:
> acd1: WARNING - REQUEST_UDMA (error request)
> acd1: WARNING - INQUIRE_SENSE (retrying request)
Little can be said without complete and accurate error messages,
pr
Le 2003-10-05, Jan Stocker écrivait :
> /usr/local/bin/cdrecord: Permission denied. Cannot send SCSI cmd via ioctl
Check perms on your /dev nodes.
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/li
Le 2003-10-05, Jan Stocker écrivait :
> it's an atapicam problem...
That we do not know so far. Recent problems reported by ATAPI/CAM users
were mostly ATA and CAM bugs. Please do not make such hasty statements
until a complete analysis of the problem has been made.
Thanks,
Thomas.
--
[EM
Le 2003-10-06, Jan Stocker écrivait :
> I would give you more info... but as i wrote... thats an endless loop.
You might be able to interrupt the loop by breaking into DDB with
Crtl+Alt+Esc, which then allows you to get a backtrace.
> > interesting to know whether the enclosed patch changes anyt
Le 2003-10-06, Jan Stocker écrivait :
> But here some stuff when booting in "safe mode" (maybe it boots because
> DMA support for atapi is off, have to check)
Probably so. The messages you quote look perfectly normal.
Thomas.
--
[EMAIL PROTECTED]
___
* Greg 'groggy' Lehey, 2003-10-27 :
> I'm running a -CURRENT kernel built about a week ago, and on
> 'camcontrol devlist' I get the following repeatable panic:
Fixed in vfs_bio.c rev. 1.418.
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mail
* Stuart Walsh, 2003-10-18 :
> I have an easily reproducable panic when using atapicam. Vague trace
This has nothing to do whatsoever with ATAPI/CAM! this is an inconsistency
between cam_periph.c and vfs_bio.c, you need to update the latter to rev.
1.418 or newer.
Thomas.
--
[EMAIL PROTEC
-CURRENT as of this week-end on a Dell Inspiron 8200 laptop.
During desktop use :
panic: bremfree: removing a buffer not on a queue
panic messages:
---
panic: bwrite: buffer is not busy???
syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue
Uptime: 9h18m39s
Dumpi
Le 2003-03-12, Jeff Roberson écrivait :
> Can you please print bp? I'd like to know what all of the members are. A
> cluster buf should NEVER have BX_BKGRDWRITE set. This is totally bogus.
(kgdb) fr
#11 0xc0232072 in bwrite (bp=0xce5313e0) at
/usr/src/sys/kern/vfs_bio.c:795
795
Le 2003-03-12, Jeff Roberson écrivait :
> Can you disable sync on panic to make sure that something has not come
> along and cleaned this buffer? I suspect that it has been modified after
> the first panic. Do you know when this first started to happen? Do you
> have any more clues into what tr
Le 2003-03-12, Jeff Roberson écrivait :
> > > Can you please print bp? I'd like to know what all of the members are. A
> > > cluster buf should NEVER have BX_BKGRDWRITE set. This is totally bogus.
Got that crash again, with sync-on-panic disabled. The interesting thing
is that the stack trace
Le 2002-06-11, Juli Mallett écrivait :
> feature I've missed having in our ps(1) for a while, the ability to get a
> tree of processes printed so you can tell who is whose child, etc.
Yes, this would be an invaluable feature!
Even nicer would be a user interface (command line, output style)
c
Le 2002-06-11, Juli Mallett écrivait :
> mask it behind something that looks good. What exactly can you get from
> that kind of output?
The overall organization of the tree. Useless if the information you
are looking for is 'what is the PID of the father of X', but may be
useful when you have s
Le 2002-07-14, Willie Viljoen écrivait :
> Just to follow up, I went back to -STABLE after discovering I don't need
> -current to do this (*slight sigh of reliefe*)
Yep, I do most ATAPI/CAM develoment on -STABLE machines.
> Thomas, ever consider asking for it to be committed into FreeBSD proper
Le 2002-08-17, Nate Lawson écrivait :
> I'm working on cleaning up quirk entries in scsi_da.c, especially ones
> related to READ/WRITE 6->10 escalation. For those just joining in, there
> is a function (cmd6workaround) that handles a R/W6 error by translating
> the cdb to 10 bytes and restarting
Le 2002-09-01, Scott Long écrivait :
> > ===> aic7xxx/ahc
> > (null): Unable to malloc scope object
> > *** Error code 70
>
> Um, what?
>
> I just did a buildworld, followed by a buildkernel KERNCONF=GENERIC
> and did not see this.
Um, I see this one as well, on a not-too-recent -CURRENT that
Le 2002-09-03, Lamont Granquist écrivait :
> i cvsup'd last night, and now i tried portupdate -a -f and debugging
> build problems with libtool i found that on my system i can make perl spin
> and consume 100% of a CPU just by:
>
> perl -pe s/foo/bar/g /tmp
Any chance you have a /usr/local/bin/
Being a user of ipfilter, I always longed for it to benefit from
the same treatment as ipfw in daily security checks, so I
undertook the implementation of an ipf equivalent of 500.ipfwdenied.
In the course of that, I noticed that much of that script was
non-trivial *and* duplicated wrt 600.ip6fwde
Le 2002-09-18, Thomas Quinot écrivait :
> http://www.cuivre.fr.eu.org/~thomas/periodic-fw.diff
I have prepared an updated version of the patch that also includes
100.chksetuid, 200.chkmounts and 700.kernelmsg in the factoring.
http://www.cuivre.fr.eu.org/~thomas/periodic-secur
Le 2002-10-27, Soeren Schmidt écrivait :
> Hmm, it is true that I could use ATAPI command directly in burncd, and
> I actually have a version in the lab that is ~75% converted to that,
Nice!
> but that is not the only issue here. The ATAPI cd driver has quite a
> bit of functionality that the SC
An updated version of the ATAPI/CAM patches is available from
http://www.cuivre.fr.eu.org/~thomas/atapicam/
This version contains no functional changes, but synchronize with
recent modifications to the generic ATAPI code.
As always, I would be interested in any feedback. Specifically, there
is
Wow /that's/ a thread ;)
> >On Thu, 28 Feb 2002, Søren Schmidt wrote:
> >> I'll quit the ATA/ATAPI development/maintenance if this goes in quickly.
First of all I'd like to make two points:
* Søren is doing a great job as ATA maintainer, and it would be a
Bad Thing to have him quit;
* I
Le 2002-02-28, Søren Schmidt écrivait :
> I have no problem with you doing it, I was just fishing for getting
> Thomas into the net also, we need all the hands we can get :)
As I mentioned I am entirely willing to take charge of the care
and feeding of the bugs I wrote.
Thomas.
--
[EMAIL
Le 2002-03-19, Søren Schmidt écrivait :
> ftp://freebsd.dk/pub/ATA/cdrtools-1.10-ATA.tgz
> On -stable it needs the ATA driver update I did a yesterday.
> It does *not* need CAM or the atapicam patches, it uses the
> ATA driver directly..
Alternatively, for those who'd like to use stock issue cdr
Le 2002-03-19, Søren Schmidt écrivait :
> ftp://freebsd.dk/pub/ATA/cdrdao-1.1.5-ATA.tgz
> Again no CAM or atapicam needed :)
Hum this package does not compile out of the box:
c++ -DHAVE_CONFIG_H -I.. -I. -I/usr/local/include/pccts -O -pipe -c
TocParser.cpp -o TocParser.o
TocParser.cpp:512: m
Le 2002-03-19, Søren Schmidt écrivait :
> > gmake[1]: *** [TocParser.o] Error 1
> You need to have pccts installed to compile cdrdao
I do, and as I mentioned in my first message, the compileation completed
after a gmake distclean.
> These utils are ATA only (as the name implies), if our po
Le 2002-03-20, Søren Schmidt écrivait :
> I thought there was work on this already ? Justin called for a timeout
> to get it done "the right way" in CAM, I was sort of expecting to
> hear about how that should integrate in the ATA/ATAPI world...
Well I have not heard of any specific requirements
Le 2002-03-20, John Baldwin écrivait :
> Looks mostly ok to me. Not entirely sure about the autoboot changes
> as it looks weird to load(kname) right before you change what kname
> is. I think the logic must somehow be wrong there.
But this is what is currently in the code (as I mentioned in t
Le 2002-03-21, Harti Brandt écrivait :
> This revision of kern_linker.c entirly disables module loads from /etc/rc
> during boot:
Or even after boot. Confirmed here: kldload always returns 'Operation
not permitted'.
Thomas.
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECT
1 - 100 of 106 matches
Mail list logo
