Re: cvs commit: src/sys/i386/i386 elan-mmcr.c

In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: >phk 2003/02/27 13:13:08 PST > > Modified files: >sys/i386/i386elan-mmcr.c > Log: > Add support for the Elan CPU hardware watchdog used in "active" mode. Now we can get the watch

Re: No more new majors, and help loose the old ones...

In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes: >> What is a good driver to crib this from? I'll do /dev/(null|zero|random). > >Heh. null and zero are two drivers phk is considering keeping fixed >majors for. :-) I'd suggest that we put the

Re: Volunteer with genuine i386 cpu & lots of time wanted.

In message <[EMAIL PROTECTED]>, "Bill Blum" writes: >> Date: Wed, 26 Feb 2003 23:13:18 +0100 >> From: Poul-Henning Kamp <[EMAIL PROTECTED]> >> Subject: Volunteer with genuine i386 cpu & lots of time wanted. >> >> Is there anybody out there who can try to run a straight -current >> on a _real_ i386

Re: Any ideas why we can't even boot a i386 ?

In message <[EMAIL PROTECTED]>, David Schultz writes: >Just out of curiosity, is your agenda to convince everyone to nix >386 support altogether or to fix 386 support? I'm not against >either, although I consider the latter goal to be a bit silly. My agenda is to find some data either in support

Re: Any ideas why we can't even boot a i386 ?

In message <[EMAIL PROTECTED]>, Geoffrey writes: >On Thu, 27 Feb 2003, Juli Mallett wrote: > >> * De: Poul-Henning Kamp <[EMAIL PROTECTED]> [ Data: 2003-02-27 ] >> [ Subjecte: Any ideas why we can't even boot a i386 ? ] >> >Yup. 386dx - 33Mhz. Results below: >> > >> >Loaded kern.flp,

Re: machdep.guessed_bootdev sysctl on i386

In message <[EMAIL PROTECTED]>, Hiten Pandya writes: > >--2oS5YaxWCcQjTEyO >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline > >Hello gang. Nothing big, but important... > >Can someone tell me if the machdep.guessed_bootdev sysctl is helpful at >all? I think it's a waste, a

Re: Mounting Root fails with error 22 (EINVAL)

Can somebody please use "cvs update -D " to do a binary search and identify which exact commit caused the problem ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice

Re: Mounting Root fails with error 22 (EINVAL)

In message <[EMAIL PROTECTED]>, Michael Class writes: >> Please try "boot -v" and send dmesg. >> >> Also, please try entering "?" to root device prompt to see what devices >> are available. > >Hello, enclosed is the boot -v output that you were asking for. >Mounting root from ufs:/dev/ad0s4a >Ro

Re: Mounting Root fails with error 22 (EINVAL)

In message <[EMAIL PROTECTED]>, Michael Class writes: >Hello, > >just as a data-point. I am seeing the same behaviour. It started with a >kernel from Feb 21th. The kernel from Feb. 20th works o.k. > >Enclosed is the dmesg out, if that helps. Please try "boot -v" and send dmesg. Also, please try

Re: Optimizing "universe" somewhat

In message <[EMAIL PROTECTED]>, Ruslan Ermilov writes: > >--/9DWx/yDrRhgMJTb >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Wed, Feb 19, 2003 at 07:40:19AM -0800, Ruslan Ermilov wrote: >> ru 2003/02/19 07:40:19 PS

Re: The cbus driver for pc98

In message <[EMAIL PROTECTED]>, Takahashi Yoshihiro writes: >In article <[EMAIL PROTECTED]> >"M. Warner Losh" <[EMAIL PROTECTED]> writes: > >> Cbus is to ISA as CardBus is to PCI in many ways. Cbus is very much >> like ISA in all but a few details. CardBus is pci with a few twists >> and turns t

Re: 5.0R - panic: bwrite: buffer is not busy

In message <[EMAIL PROTECTED]>, Patric Mrawek writes: >I am seeing a reproducible panic with > >FreeBSD talisker 5.0-RELEASE FreeBSD 5.0-RELEASE #5: Wed Jan 29 10:49:32 CET 2003 >root@talisker:/usr/src/sys/i386/compile/TALISKER i386 > >What I've done is: >- kldload uvisor.ko >- running »/usr/sbin/u

Re: cvs commit: src/sys/alpha/alpha busdma_machdep.c src/sys/alpha/osf1 imgact_osf1.c osf1_misc.c src/sys/cam cam_periph.c cam_sim.c cam_xpt.c src/sys/cam/scsi scsi_cd.c scsi_ch.c scsi_da.c scsi_low.c scsi_sa.c scsi_target.c src/sys/coda cnode.h ...

In message <[EMAIL PROTECTED]>, Peter Wemm writes: >[EMAIL PROTECTED] wrote: > >> The attached patch will print a backtrace if any calls to malloc >> fail to have either M_WAITOK or M_NOWAIT. > >Please do not commit this as-is.. There is a DoS here if a user figures >out how to provoke this. This

Re: Simply impossible to format disk under current.

In message <[EMAIL PROTECTED]>, David Gilbert writes: >I ran into an interesting problem last night ... that was very >frustrating. I was recycling SCSI drives from some NetBSD machines >(that were client boxes) to add to a RAID server running >FreeBSD-5.0-RELEASE. > >It's simply impossible to for

Re: cvs commit: src/sys/alpha/alpha busdma_machdep.c src/sys/alpha/osf1 imgact_osf1.c osf1_misc.c src/sys/cam cam_periph.c cam_sim.c cam_xpt.c src/sys/cam/scsi scsi_cd.c scsi_ch.c scsi_da.c scsi_low.c scsi_sa.c scsi_target.c src/sys/coda cnode.h ...

In message <[EMAIL PROTECTED]>, Warner Losh write s: >imp 2003/02/18 21:47:47 PST > > Modified files: >[... everything ...] > uma_core.c vm_map.c vm_object.c > Log: > Back out M_* changes, per decision of the TRB. > > Approved by: trb The attached patch w

Re: New ad*s* devices not automatically appearing in devfs

In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: >[EMAIL PROTECTED] wrote: >> In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: >> >>>When I add a new slice or partition to a disk, the device files don't >>>automatically appear in /dev. If I reboot, it shows up, but having to >>>reboot

Re: New ad*s* devices not automatically appearing in devfs

In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: >When I add a new slice or partition to a disk, the device files don't >automatically appear in /dev. If I reboot, it shows up, but having to >reboot twice just to add a filesystem to a running disk is absurd. How >do I make /dev automaticall

Re: Problems creating and writing to disk slices

In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: >I can understand the usefulness of preventing modifications applying to >mounted partitions, and I can see the logic in unliaterally preventing >them, but preventing modifying slice table and disk label entries for >unmounted portions of t

Re: Problems creating and writing to disk slices

h at: > >ftp://ftp.jurai.net/users/winter/patches/geom-foot.patch > >(Hint: sysctl kern.geom.allow_foot_shooting=1) > >Then help me convincing phk that there might be legitimate needs >for such an option. :-/ You're out of date, one such has been committed to current. -- Po

Re: The cbus driver for pc98

In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes: >In message: <[EMAIL PROTECTED]> >[EMAIL PROTECTED] writes: >: In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes: >: >In message: <[EMAIL PROTECTED]> >: >Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes: >: >: Taka

Re: The cbus driver for pc98

In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes: >In message: <[EMAIL PROTECTED]> >Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes: >: Takahashi Yoshihiro <[EMAIL PROTECTED]> writes: >: > I have had some questions like "Does PC98 have ISA bus?" or "Why PC98 >: > uses ISA driver?"

Re: disklabel is broken (GEOM related)

In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes: >[EMAIL PROTECTED] writes: >> In message <[EMAIL PROTECTED]>, Maxim Sobolev writes: >> > It seems that disklabel is currently broken on -current. In `read' mode it >> > reports incorrect information about disk layout: >> Don't use the "-r"

Re: disklabel is broken (GEOM related)

In message <[EMAIL PROTECTED]>, Maxim Sobolev writes: >Hi, > >It seems that disklabel is currently broken on -current. In `read' mode it >reports incorrect information about disk layout: Don't use the "-r" option and you will be ok. Poul-Henning >root@notebook# disklabel -r ad0s1 -- Poul-Henni

Re: ACPI timer bug

In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes: >The clock on my ASUS P5A still runs at double speed unless I have >debug.acpi.disable="timer" in loader.conf (as it has for as long as >we've had ACPI support). Do any ACPI wizards have any suggestions as >to how I could track down the c

Re: Console API related patch.

In message <[EMAIL PROTECTED]>, Marcel Moolenaar writes: >> This patch changes the API so that rather than pass a "dev_t" to the >> console functions, the "struct consdev *" is passed: >> >> -typedefvoidcn_putc_t(dev_t, int); >> +typedefvoidcn_putc_t(struct consd

Re: Clock disabled during DDB

In message <[EMAIL PROTECTED]>, Bruce Evans writes: >The >piix timecounter has a lower frequency than the TSC, but for some >reason we mask it to 24 bits (16M cycles @ 3.5+ MHz = 4+ seconds). We do this because the spec defines it as either 32 or 24 bit and some 24 bit implementations claim to ha

Re: OPIE breakage: backout & patch for review

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >> Please take this to private email. > >I not see enough good will from des side for it. Then please just stop. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer

Re: OPIE breakage: backout & patch for review

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sun, Feb 16, 2003 at 13:27:38 +0300, Andrey A. Chernov wrote: >> >> Unless you specify exact details of what I ignore, I'll be forced to >> treat your reply as NO REVIEW and commit this changes. > >Well, after numerous exchanges of n

Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

In message <[EMAIL PROTECTED]>, Makoto Matsushita writes: > >phk> Not yet. I think adding a "-m architecture" flag to disklabel is the >phk> way around this problem, but have not had time to do so. > >Thanks, I'm waiting until you have enough time to do

Re: make depend broken in cpp0

In message <[EMAIL PROTECTED]>, Kris Kennaway writes: > >--5UGlQXeG3ziZS81+ >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Sat, Feb 15, 2003 at 11:01:52PM +0100, [EMAIL PROTECTED] wrote: > >> >> #cd /usr/src/gnu/usr.bin/cc

Re: make depend broken in cpp0

In message <[EMAIL PROTECTED]>, Kris Kennaway writes: > >--mJm6k4Vb/yFcL9ZU >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Sat, Feb 15, 2003 at 07:28:45PM +0100, Poul-Henning Kamp wrote: >>=20 >> I installed 5.0-R on my ne

Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

In message <[EMAIL PROTECTED]>, Makoto Matsushita writes: > >I've tried to do "make release" of FreeBSD/alpha on FreeBSD/i386 box >last night, and found that follow error while generating drivers.flp: > >If my understandings are correct, this is because disklabel(8) kicked >is FreeBSD/i386 native b

Re: fix: lock order reversal proc/filedesc.

In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes: >Makes me want to get my Norwegian Sword [tm] and make a short trip to >Denmark. I my be reading my email out of order here, but I guess you changed your mind and tried to bury use with boatloads of useless asterix ('*') instead ? :-)

Re: Problems with timekeeping

In message <[EMAIL PROTECTED]>, "tony" writes: >My time clock seems to do two ticks for every one that it should do. I'm not >sure where to start on fixing this. I had 4.7 installed and did a clean >install of 5.0 release thats when I noticed the time keeping weirdness.. it >always kept time perfec

Re: gbde

In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] write s: >I keep ketting errors when trying to make my root filesystem encrypted: > >bash-2.05b# gbde init /dev/ad0s2a >gbde: /dev/ad0s2a: No such file or directory >bash-2.05b# If you have ad0s2a mounted as a filesystem, doing the above doesn't

Re: sio issue

y, I end up in ddb when I connect my (unconnected) serial console >cable to another machine. It's not critical, since "c" will continue >fine, but it's annoying. Here's a trace: > > >Could this commit be related at all? No, not a chance. >>

Re: i386 tinderbox failure

>/local0/scratch/des/src/sys/geom/bde/g_bde.c: In function `g_bde_config': >/local0/scratch/des/src/sys/geom/bde/g_bde.c:251: structure has no member named >`slicesize' >/local0/scratch/des/src/sys/geom/bde/g_bde.c:252: structure has no member named >`sliceoffset' My fault, already fixed. --

Re: panic with heavy io

In message <[EMAIL PROTECTED]>, Mark Santcroos writes: >596: DEV_STRATEGY(bp); > >I don't understand what you want me to examine there as the arguments are >not usefull anymore (or are they?). Well that line in my copy was not code, so I just wanted to see what your sources said. >> >#15 0xc01

Re: panic with heavy io

In message <[EMAIL PROTECTED]>, Mark Santcroos writes: >While doing heavy IO (updating my p4 repo) on my laptop I got the following >panic. (I was running in X so both backtrace and dmesg are from the core >dump after reboot) > >I'm wondering whether the ENOMEM's reported by GEOM point out that GE

Re: Preview: GEOMs statistics code.

In message <[EMAIL PROTECTED]>, Mattias Pantzare writes: >[EMAIL PROTECTED] wrote: >> I have played with the statistics collection in GEOM a bit, and need >> more feedback, but first: try to play with it a bit. >> >> Assuming you're running -current as of today, otherwise install >> include files

Re: Does bg fsck have problems with large filesystems?

In message <[EMAIL PROTECTED]>, Gerrit =?iso-8859-1?Q? K=FChn?= writes: >On Tue, Jan 28, 2003 at 06:31:42PM +0100, Gerrit Kühn wrote: > >> > I've been trying to reproduce this bug on my desktop. This machine has 2 >> > 80gb disks, one of which is dedicated with one slice. So far, after 8 hard >> >

Re: Do we still have a FIFO / named pipe problem?

Yes, we do have FIFO/named pipe problems in -current. I committed a workaround to prevent one particular condition under which my diskless box would hang forever in sendmail processing in /etc/rc by setting a 1 sec timeout on the sleep it hung in. This is nowhere near correct as pointed out by B

Re: Preview: GEOMs statistics code.

I have played with the statistics collection in GEOM a bit, and need more feedback, but first: try to play with it a bit. Assuming you're running -current as of today, otherwise install include files and libgeom by hand first. Apply this patch in src/sys/geom and make a new kernel. http

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sat, Feb 08, 2003 at 00:16:24 +0100, [EMAIL PROTECTED] wrote: >> >> Can we stop considering workarounds, and instead work on solving >> the problem please ? > >I see no solving way until kernel will understand fully and can handle >ti

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Thu, Feb 06, 2003 at 22:10:43 +1100, Bruce Evans wrote: >> >> More precisely: some are mounted, but they are mounted read-only (modulo >> the bug that adjkerntz is run a little after mounting filesystems read-write). > >Obvious workar

Re: GEOM and Extended Slices

In message <[EMAIL PROTECTED]>, Hiten Pandya writes: >Hi gang. > >Recently removing the NO_GEOM option from my kernel; I noticed that my >dos extended slices dev entries disappeared under a GEOM kernel. This >is sorta bad, but I can bare for now. > >Also, I tried searching the sys/geom/ tree if th

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >> This is not any different from any other filesystem. > >No, it IS different - no real filesystems mounted at this point yet, so no >real timestamps damaged. Think diskless NFS, think MD(4) based root, think... The only problem is

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, Bruce Evans writes: >On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > >> On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: >> > >> > >2) Feb 6 01:36 (boot time) >> > >3) Feb 6 04:36 (+3 TZ future jump) >> > >> > These timestamps have been touched, and

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: >> >> >2) Feb 6 01:36 (boot time) >> >3) Feb 6 04:36 (+3 TZ future jump) >> >> These timestamps have been touched, and the clock has made a 3 hour >> jump either forward

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 23:23:26 +0100, [EMAIL PROTECTED] wrote: >> >> Try to remove the three "fix" lines, and see what you get then. >> > >Very strange effect: 3 kinds of entries appearse: >1) Jan 1 1970 These are the intact untouc

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 22:10:41 +0100, [EMAIL PROTECTED] wrote: >> >> You can try this patch instead. It has a different side effect: >> if you reset your clock the (untouched) timestamps will change. > >It not helps, see 00:48 -> 03:4

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Wed, Feb 05, 2003 at 20:52:54 +0100, [EMAIL PROTECTED] wrote: >> >> My guess: Your RTC has the wrong time and ntpdate or similar stepped >> your clock to be correct. > >It is each boot repeated effect, not one time. >I run local cloc

Re: 5.0 issues

In message <[EMAIL PROTECTED]>, Oliver Fromme writes : >1. I have some shell scripts that make use of redirections >with file descriptors (3>&1 and /dev/fd/3 etc.). Those >worked under 4.x out of the box, but didn't work in 5.0, >because there is no /dev/fd/3 in DEVFS. I solved this by >manuall

Re: Wrong date for DEVFS entries

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >Look at the snapshot below, taken right after boot time. Most entries are >at "Feb 5 22:34" which is boot time, but some other are "Feb 6 01:34" >which is in the future! It looks like TZ offset added for them by mistake. >Please fix thi

Re: Preview: GEOMs statistics code.

In message , Brad Knowles writes: >At 8:26 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote: > My understanding was that a disk is 100% busy, if the heads are >constantly moving to and fro, and there is no period of time when >they aren't being yanked around.

Re: Preview: GEOMs statistics code.

In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey" writes: >2. %busy. I personally think this is the most important one, but as >you say, there's no reason not to do the others as well. The problem with this one is that we can't measure it in a way which tells us the truth, and we may n

Re: Preview: GEOMs statistics code.

In message , Brad Knowles writes: >At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote: > >> In difference from the devstat framework which measures how big a >> percentage of the time a drive has one or more outstanding requests, >> I think that measurin

Re: Minor oddity with sysinstall/disklabel on -current

In message , Garance A Drosihn writes: >So, I'm trying something on -current. > >I boot up, log into root. I have two hard disks on the system. All >of my mounted partitions are on ad0, except for one partition on ad2. >I 'umount' that partition. I run the

Re: extended slices on 5.0-RELEASE?

In message <[EMAIL PROTECTED]>, Mike Meyer writes: >[I asked this on -questions, and got no response, so...] > >Is it just me, or has disklabel lost the ability to read/write from >extended slices in 5.0-RELEASE? I hope not. Please send me the output of sysctl -b kern.geom.confxml in priv

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >[EMAIL PROTECTED] wrote: > >> Say, do you actually have the GEOM_BDE option in your kernel ? > > Sigh, no. I missed it in gbde(4). > > You might want to further idiot-proof gbde(8) with code like: > >err(1, "ioctl(GEOMCONFIGGEOM) (is

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >[EMAIL PROTECTED] wrote: > >> Can you please try this: >> >> mdconfig -a -t malloc -s 4m -u 75 >> gbde init /dev/md75 >> gbde attach md75 > > Nope, exact same error. That is weird, it works like a charm here. syv

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >[EMAIL PROTECTED] wrote: > >> >su-2.05b# gbde init /dev/md0 -L /tmp/foo.lock >> >> Don't use the -L and -l arguments unless you have to. > > Thanks, but that was what I originally tried, and I still got the >"gbde: ioctl(GEOMCONFIGGEOM):

Re: gbde & vnode md devices?

In message <[EMAIL PROTECTED]>, Darryl Okahata writes : >su-2.05b# gbde init /dev/md0 -L /tmp/foo.lock Don't use the -L and -l arguments unless you have to. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD sinc

Re: rand() is broken

In message <[EMAIL PROTECTED]>, Mark Murray wr ites: >We have most of this, and RC4 can deliver. RC4's "licence" is >fine. Call it "ArCFour" and there is no problem. The code is >small, fast and repeatable, and meets conditions 1-4 above. There are some concerns about RC4's strength and predictab

Re: rand() is broken

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sun, Feb 02, 2003 at 19:32:50 +0100, [EMAIL PROTECTED] wrote: >> >> Anyway, last time we discussed this, I think we stuck with the rand() >> we had because we feared that people were using it's repeatable well >> documented sequence o

Re: rand() is broken

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sun, Feb 02, 2003 at 17:30:48 +, Mark Murray wrote: >> >> Why not? Arc4 is a) deterministic and b) good for all bits. > >If you mean arc4random() function - not, because it use true randomness, >if you mean RC4 algorithm, probably

Re: rand() is broken

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: > >--SUOF0GtieIMvvwua >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Sun, Feb 02, 2003 at 01:11:06 -0800, Kris Kennaway wrote: >>=20 >> Another problem (noticed b

Re: split out patch

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: >Oh shut up Poul-Henning. Try to remain civil here Julian :-) I tried to explain the situation to you, to make sure you would not be tempted to do rush something which needs to take the time things take. >I know I'm on your shit list, an

Re: split out patch

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: >still no comments? Julian, you sent this out a few hours ago, after people had spent a lot of time and getting quite frustrated trying to get you to DTRT with your mentee's inappropriate commit. If people are sick and tired of you right n

Re: ata0: resetting device - ASUS P4S8X

In message <[EMAIL PROTECTED]>, Christoph Kuk ulies writes: > >I bought new hardware for a server today, an ASUS P4S8X with >an 1.8 GHZ P4 CPU, nothing fancy I would say, which has an >onboard RAID controller (Promise) but I'm not using it >for the moment. I attached an IBM 60GB Deskstar ATA/IDE di

Re: last KSE changes

In message <[EMAIL PROTECTED]>, Jul ian Elischer writes: >The rumour mill has been running wild on this but **AS FAR AS I KNOW** >the breakages have been fixed, since no-one has told me directl of any >current breakages. If you have any breakage from this commit, >PLEASE TELL ME! I think you sho

Re: VOP_STRATEGY on VCHR

In message <[EMAIL PROTECTED]>, Enache Adrian writes: >I get this when I try to access for the first time a file on an ext2fs >filesystem. > >VOP_STRATEGY on VCHR Please try this patch and let me know if it helps ? Index: ext2_vnops.c ==

Re: Opening /dev/tty in session leader after controlling terminal is revoked causes panic.

In message <[EMAIL PROTECTED]>, "Peter Edwards" writes: >> >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process >> >has its P_CONTROLT flag set, then it's session has a valid vnode for it's >> >controlling terminal. This doesn't hold if the terminal was revoked. >Yes, t

Re: Am I blind? (devfs issue)

In message <[EMAIL PROTECTED]>, "Thomas E. Zander" write s: >Sorry, this is probably a stupid question, but: > >[riggs] ~ > ll /dev/ds* >crw-rw-rw- 1 root wheel 30, 3 27 Jan 14:46 /dev/dsp0.0 >crw-rw-rw- 1 root wheel 30, 0x00010003 27 Jan 10:59 /dev/dsp0.1 >crw-rw-rw- 1 root wheel 30,

Re: mdconfig -l broken after /sys/dev/md/md.c rev 1.77

In message <[EMAIL PROTECTED]>, Giorgos Keramidas writes: >mdconfig -l stopped working in -current after revision 1.76 of md.c. > >I just reverted src/sys/dev/md/md.c to revision 1.76 and removed >M_WAITOK to let me build a kernel with that version of md.c. Now >mdconfig correctly lists the open m

Re: alpha/GENERIC børked

In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: > ># make >cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -Wall -Wredundant-decls -Wnested-externs >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual >-fformat-extensions -ansi -g -nostdinc -I- -I. -I../../.. -I../../..

Re: HEADSUP: disklabel(8): men at work.

In message <[EMAIL PROTECTED]>, Wilko Bulte writes: >On Sun, Jan 26, 2003 at 03:47:11PM +0100, Poul-Henning Kamp wrote: >> >> I'm still not done with disklabel(8), and I have not run it through >> all the tests I want (I'm waiting for my glacial 233MHz EV45 alpha >> to compile a world) so be caref

Re: cvs commit: src/sbin/disklabel disklabel.8 disklabel.c

In message <[EMAIL PROTECTED]>, Ruslan Ermilov writes: >and installed the new kernel (without any problems) on it. Next >reboot refused to boot FreeBSD by mentioning that "No operating >system was found". I wondered how I managed to screw my disk up. Welcome to the club if people who was bitten

Re: Opening /dev/tty in session leader after controlling terminal is revoked causes panic.

In message <[EMAIL PROTECTED]>, "Peter Edwards" writes: >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process >has its P_CONTROLT flag set, then it's session has a valid vnode for it's >controlling terminal. This doesn't hold if the terminal was revoked. Can you try this

Re: GEOM & disklabel

In message <[EMAIL PROTECTED]>, Michael Reifenberger writes: >On Fri, 24 Jan 2003 [EMAIL PROTECTED] wrote: >... >> Don't use the '-r' option, it gets confused because geom::BSD does >> not lie to it. >Yes, that seems to work... >Time to say good bye for '-r' ? Well, we still need it for writing t

Re: GEOM & disklabel

In message <[EMAIL PROTECTED]>, Michael Reifenberger w rites: > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without MIME-aware tools. > Send mail to [EMAIL PROTECTED] for more info. > >--0-240786022-1043432225=:647 >C

Re: -current error in kernel build with NO_GEOM

In message <[EMAIL PROTECTED]>, Gary Jennejohn w rites: >Am I the only person using NO_GEOM in -current? Probably. NO_GEOM is scheduled to be removed as an option in some weeks, so if there is a bug or other issue which prevents you from running GEOM this would be a really good time to tell me.

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Bernd Walter writes: >> da1a closed but without FREAD|FWRITE, which turns the close into a no-op. > >[125]cicely5# grep d_open * >grep: CVS: Operation not permitted >vinumext.h:d_open_t vinumopen; >vinumio.c: drive->lasterror = (dsw->d_open) (drive->dev, FWRITE

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >Here's the result. What does it mean to me? (debug flag set from >DDB, and turned off in single-user again.) Here's the bug: g_dev_open(da1a, 3, 0, 0) da1a opened (FREAD|FWRITE) g_access_rel(0xc1178a40(da1a), 1, 1, 0)

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Bernd Walter writes: >On Tue, Jan 21, 2003 at 11:06:05PM +0100, [EMAIL PROTECTED] wrote: >> In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >> >As [EMAIL PROTECTED] wrote: >> > >> >> Hang on. >> >> >> >> If no disk partitions of any kind are open, there is noth

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >It wouldn't have paniced it at all, since i /knew/ nothing was open >on it. Well, the only reason why GEOM didn't let you was that it knew that something was open. As I said, the XML output contains the truth in this matter... -- Poul-Henn

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >As [EMAIL PROTECTED] wrote: > >> Hang on. >> >> If no disk partitions of any kind are open, there is nothing which >> prevents you from doing a "dd if=/dev/zero of=/dev/da0 bs=64k". > >My guess is that vinum scanned the disks when starting, but

Re: I want a sysctl kern.allow_shooting_into_my_foot!

In message <[EMAIL PROTECTED]>, Joerg Wunsch writes: >Included an old disk into a running system. Want to install a new >label onto it: > >uncle# disklabel -Brw da0 auto >disklabel: ioctl DIOCSDINFO: open partition would move or shrink > >Needless to say, there is nothing open at all on it. As i

Re: HEADSUP: CCD(4) hackery...

In message <[EMAIL PROTECTED]>, Lars Eggert writes: >I just booted today's -current kernel in single-user mode to do an >installworld, and when I do the usual "ccdconfig -C" (since my /usr is >striped), I now get: > > # ccdconfig -C > ccdconfig: open: /dev/ccd0c: No such file or dire

Re: panic: malloc(M_WAITOK) returned NULL

In message <[EMAIL PROTECTED]>, Kris Kennaway writes: >I just got the following on axp1: > >panic: malloc(M_WAITOK) returned NULL >db_print_backtrace() at db_print_backtrace+0x18 >panic() at panic+0x104 >malloc() at malloc+0x1a8 >initiate_write_inodeblock_ufs1() at initiate_write_inodeblock_ufs1+0

Re: Somebody: port this: http://www.theinquirer.net/?article=7231

In message <[EMAIL PROTECTED]>, Kris Kennaway writes: > >--ALfTUftag+2gvp1h >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline > >"The tool costs $699 and Intel said it will be available in February." > >That would make it somewhat difficult, no? I don't think so. VTUNE is p

Re: SMP hang at boot on Compaq Proliant ML370

In message <[EMAIL PROTECTED]>, Nicolas Kowalski writes: >Fritz Heinrichmeyer <[EMAIL PROTECTED]> writes: > >> On Wed, Jan 15, 2003 at 11:09:09AM +0100, Nicolas Kowalski wrote: >>> The server is configured for Unixware7, as told in the archives. >> >> our Compaq worked when configured for linux > >

Re: FreeBSD 5.0 RC3 now available

In message <[EMAIL PROTECTED] .com>, "local.freebsd.current" writes: >On Mon, 13 Jan 2003 11:46:43 -, [EMAIL PROTECTED] wrote: > >>In the meantime we _really_ have to ship 5.0-RELEASE, we keep >>slipping it. > >That sounds like "it's time to ship so we're going to ship". That's it. >I'm not t

Re: Geom disklabel/fdisk issues?

In message <[EMAIL PROTECTED]>, walt writes: >[EMAIL PROTECTED] wrote: >> Julian Elischer writes: >> >>>I think that one of the things we need to do is declare a new flag in >>>disklabel that declares that the disklabel has been converted to use >>>relative offsets... > >> Better plan: Abandon BS

Re: Geom disklabel/fdisk issues?

In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: > >I think that one of the things we need to do is declare a new flag in >disklabel that declares that the disklabel has been converted to use >relative offsets. if the flag is not set then absolute offsets are >expected.. That would give a w

Re: FreeBSD 5.0 RC3 now available

In message <[EMAIL PROTECTED]>, "Roderick van Domburg" writes: >I would like to point to a currently unresolved issue that Thomas Moestl is >helping me solve on freebsd-sparc@. It isn't listed on the Open Issues page, >but I'd say it's something that needs to be resolved before the release is >rol

Re: GEOM prevents bootblocks writing

In message <[EMAIL PROTECTED]>, Sean Kelly writes: >Since I haven't seen any response to this, I'll "me too" it in hopes that >it will get some attention drawn to it. boot0cfg and fdisk should work as advertised. There is an erratum on "disklabel -B" for 5.0-RELEASE. -- Poul-Henning Kamp

Re: 5.0 without swap

In message <[EMAIL PROTECTED]>, "Geof frey T. Falk" writes: >Further to my previous message on encrypting swap: >In order for it to work, apparently, one must change the fstype within >the disklabel, so that the swap partition (e.g. /dev/ad0s1b) is fstype >"4.2BSD", not "swap". This shouldn't be n

Re: VOP_SPECSTRATEGY on non-VCHR

In message <[EMAIL PROTECTED]>, Lars Eggert writes: >just got this on today's -current, when accessing a mounted NTFS partition: > >VOP_SPECSTRATEGY on non-VCHR >: 0xc6d73c34: tag ntfs, type VREG, usecount 3, writecount 0, refcount 0, >flags (VV_OBJBUF), lock type ntfs: SHARED (count 1) Can you

Re: strange dump/restore behaviour

I've seen this when dumping live filesystems. I belive it means that dump couldn't find the file it had already dumped in the directory once it got to dump the contents. In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes: >This happened while copying data over to a new disk (mounted on /

  1   2   >