Re: pcic state
On Mon, Oct 14, 2002 at 07:39:12PM +0900, Takanori Watanabe wrote: > In message <[EMAIL PROTECTED]>, Bernd Walter さんいわく: > >Yesterday I updated my notebook from 31th Aug -current to 3rd Oct. > >Now pccardd complains there is no /dev/card0. > >The probing looks fine. > > That's no expected. > Newcard currently has no way to access PCCARD CIS and catch inseartion event > from userland, OK - I've switched to oldcard for the time beeing. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
alpha tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- >>> Kernel build for GENERIC started on Tue Oct 15 03:07:30 PDT 2002 -- >>> Kernel build for GENERIC completed on Tue Oct 15 03:35:01 PDT 2002 -- >>> Kernel build for LINT started on Tue Oct 15 03:35:01 PDT 2002 -- ===> vinum "Makefile", line 4244: warning: duplicate script for target "geom_bsd.o" ignored cc1: warnings being treated as errors /h/des/src/sys/dev/aic7xxx/ahd_pci.c: In function `ahd_pci_map_registers': /h/des/src/sys/dev/aic7xxx/ahd_pci.c:171: warning: implicit declaration of function `bus_space_subregion' *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM question
Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, walt writes: > >>Would the GEOM framework make it feasible to use a DOS-extended/logical >>partition for a BSD filesystem? > We already support that as far as I know, both with and without GEOM Yes! The reason I could never make it work is because of an 'error' in the man page for newfs: "Before running newfs the disk must be labeled using disklabel(8)" Well, disklabel won't work on an extended/logical partition so I never actually got as far as newfs until just now. Turns out that newfs works just great without a disklabel on a logical partition. I just moved the entire ports collection to my brand new 8Gb ufs partition and never went near growfs. I'm very happy! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI problems with today's current
Hi, > > But never mind, you can force to compile the ASL and generate DSDT; > > # iasl -i SupermicroP3TDE6.new.asl > > then copy generated acpi_dsdt.aml to /boot/. > > # cp acpi_dsdt.aml /boot/ > > Okay, I did that, and then typed the following at the boot prompt: > > set acpi_dsdt_load="YES" > set acpi_dsdt_name="/boot/acpi_dsdt.aml" > > Things still don't seem to be working properly. I've attached dmesg > output. [snip] > Preloaded elf kernel "/boot/kernel.test32/kernel" at 0xc0569000. > Preloaded elf module "/boot/kernel.test32/acpi.ko" at 0xc05690b0. > Timecounter "i8254" frequency 1193182 Hz Hmm, it seems that /boot/acpi_dsdt.aml doesn't to be loaded. I think `set acpi_dsdt_load="YES"' at the boot prompt is not effective. How about having acpi_dsdt_load="YES" in your loader.conf, or typing `load -t acpi_dsdt /boot/acpi_dsdt.aml' at the boot prompt ? Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fdisk -u with geom
What's the equivalent of fdisk -u with geom? ( Assuming that it's not the same after getting: laptop# fdisk -u ad0 fdisk: can't open device /dev/ad0 fdisk: cannot open disk /dev/ad0: Operation not permitted ) Thanks Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM "The surest sign that intelligent life exists elsewhere in the universe is that it has never tried to contact us." -- Hobbes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM
In article <[EMAIL PROTECTED]> Poul-Henning Kamp <[EMAIL PROTECTED]> writes: > >After this commit, the wd driver causes panic at wdsleep() via > >wdopen(). Please fix this problem or back out your change. > > Can you provide some details on this panic ? I attach panic message. --- TAKAHASHI Yoshihiro <[EMAIL PROTECTED]> Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1994-2002 FreeBSD(98) porting team. Copyright (c) 1992 A.Kojima F.Ukai M.Ishii (KMC). Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #48: Tue Oct 15 22:33:48 JST 2002 [EMAIL PROTECTED]:/usr/src/sys/pc98/compile/YUE Preloaded elf kernel "/boot/kernel/kernel" at 0xc049f000. Timecounter "i8254" frequency 2457600 Hz CPU: Pentium Pro (198.95-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x616 Stepping = 6 Features=0xf9ff real memory = 134217728 (131072K bytes) avail memory = 124321792 (121408K bytes) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: at port 0x6b8e on motherboard apm0: found APM BIOS v1.11, connected at v1.0 pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 6.0 on pci0 isa0: on isab0 pci0: at device 7.0 (no driver attached) pci0: at device 8.0 (no driver attached) fxp0: port 0x6000-0x601f mem 0x2050-0x205f,0x2041-0x20410fff irq 3 at device 11.0 on pci0 fxp0: Ethernet address xx:xx:xx:xx:xx:xx nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0x6100-0x61ff mem 0x20411000-0x20411fff irq 3 at device 16.0 on pci0 aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs pnpbios: error 0/82 getting device count/size limit orm0: at iomem 0xdc000-0xdf7ff on isa0 fdc0 at port 0x4be,0xbe,0x94,0x92,0x90 irq 11 drq 2 on isa0 fd0: <1.44M FDD> on fdc0 drive 0 wdc0 at port 0x640-0x647 irq 9 on isa0 wdc0: unit 0 (wd0): wd0: 3079MB (6306048 sectors), 46368 cyls, 8 heads, 17 S/T, 512 B/S wdc0: unit 2 (wd1): wd1: 407MB (833544 sectors), 6129 cyls, 8 heads, 17 S/T, 512 B/S wdc0: unit 1 (wd2): wd2: 1222MB (2503760 sectors), 18410 cyls, 8 heads, 17 S/T, 512 B/S wdc0: unit 3 (atapi): , removable, accel, dma, iordis wcd0: drive speed 1031KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 256 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc0: driver is using old-style compatibility shims pckbd0: at port 0x43,0x41 irq 1 on isa0 kbd0 at pckbd0 gdc0: at port 0xaf,0xad,0xab,0xa9,0xa7,0xa5,0xa3,0xa1,0x7e,0x7c,0x7a,0x78,0x76,0x74,0x72,0x70,0x9ae,0x9ac,0x9aa,0x9a8,0x9a6,0x9a4,0x9a2,0x9a0,0x4ae,0x4ac,0x4aa,0x4a8,0x4a6,0x4a4,0x4a2,0x4a0,0xae,0xac,0xaa,0xa8,0xa6,0xa4,0xa2,0xa0,0x6e,0x6c,0x6a,0x68,0x66,0x64,0x62,0x60 iomem 0xe-0xe7fff,0xa8000-0xb,0xa-0xa4fff on isa0 sc0: on isa0 sc0: PC-98x1 <16 virtual consoles, flags=0x0> pmtimer0 on isa0 Found OPTi device OPTi930 pcm0: at port 0xf8f-0xf97,0xe0e,0xf40-0xf47 irq 12 drq 1 flags 0x1b000 on isa0 drq/irq conf 22 sio0 at port 0x30 irq 4 on isa0 sio0: type (internal fifo v-fast) sio1 at port 0x238-0x23f irq 5 flags 0x1210 on isa0 sio1: type 16550A, console sio2: configured irq 5 not in bitmap of probed irqs 0 sio2: port may not be enabled sio3: configured irq 5 not in bitmap of probed irqs 0 sio3: port may not be enabled sio4 at port 0x10be,0x10bc,0x10ba,0x10b8,0x10b6,0x10b4,0x10b2,0x10b0 irq 10 flags 0x15000401 on isa0 sio4: type 16550A (RSB-3000) (multiport master) sio5: configured irq 10 not in bitmap of probed irqs 0 sio5: port may not be enabled sio5 at port 0x10bf,0x10bd,0x10bb,0x10b9,0x10b7,0x10b5,0x10b3,0x10b1 flags 0x15000401 on isa0 sio5: type 16550A (RSB-3000) (multiport) sio6: configured irq 6 not in bitmap of probed irqs 0 sio6: port may not be enabled sio7: configured irq 6 not in bitmap of probed irqs 0 sio7: port may not be enabled sio8: configured irq 5 not in bitmap of probed irqs 0 sio8: port may not be enabled mse0: at port 0x7fdf,0x7fdd,0x7fdb,0x7fd9 irq 13 on isa0 ppc0: at port 0x140-0x147 irq 14 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port Timecounters tick every 10.000 msec Initializing GEOMetry subsystem Waiting 15 seconds for SCSI devices to settle g_pc98_taste: error 45 Sectors are 512 bytes g_error 45 Mediasize is 0 bytes g_pc98_taste: error 45 guessing 17 sectors g_pc98_taste: error 45 guessing 8 heads da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15) da0: 19546MB (40031712 512 byte sectors: 8H 128S/T 39092C) Mounting root from ufs:/dev/da0s1a Entropy harvesting: interrupts ethernet point_to_point. kernel dumps on /dev/da0s1b swapon: adding /dev/da0s1b as swap device Starting file system checks: /dev/da0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/
Re: alpha tinderbox failure
On Tue, Oct 15, 2002 at 03:39:46AM -0700, Dag-Erling Smorgrav wrote: > -- > >>> Kernel build for LINT started on Tue Oct 15 03:35:01 PDT 2002 > -- > ===> vinum > "Makefile", line 4244: warning: duplicate script for target "geom_bsd.o" ignored > cc1: warnings being treated as errors > Poul, Can you please remove the "geom_bsd.c" script from either sys/conf/files or all of sys/conf/files.*? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg44706/pgp0.pgp Description: PGP signature
Re: alpha tinderbox failure
Ruslan Ermilov wrote: > > --+g7M9IMkV8truYOl > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Tue, Oct 15, 2002 at 03:39:46AM -0700, Dag-Erling Smorgrav wrote: > > -- > > >>> Kernel build for LINT started on Tue Oct 15 03:35:01 PDT 2002 > > -- > > =3D=3D=3D> vinum > > "Makefile", line 4244: warning: duplicate script for target "geom_bsd.o" = > ignored > > cc1: warnings being treated as errors > >=20 > Poul, > > Can you please remove the "geom_bsd.c" script from either > sys/conf/files or all of sys/conf/files.*? This is not the cause of the problem. The build is not disturbed by this config(8) bug. The reason for the failure is that the alpha bus_sppace code does not have the function that ahd needs. It either needs to be implemented or ahd needs to be removed from the alpha build. ahd works on ia64 and sparc64, so dont add it to the i386-only section. However, there are hundreds more failures after this. Fixing this one just gets us to the next failure. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: alpha tinderbox failure
On Tue, Oct 15, 2002 at 07:54:50AM -0700, Peter Wemm wrote: > Ruslan Ermilov wrote: > > > > --+g7M9IMkV8truYOl > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > Content-Transfer-Encoding: quoted-printable > > > > On Tue, Oct 15, 2002 at 03:39:46AM -0700, Dag-Erling Smorgrav wrote: > > > -- > > > >>> Kernel build for LINT started on Tue Oct 15 03:35:01 PDT 2002 > > > -- > > > =3D=3D=3D> vinum > > > "Makefile", line 4244: warning: duplicate script for target "geom_bsd.o" = > > ignored > > > cc1: warnings being treated as errors > > >=20 > > Poul, > > > > Can you please remove the "geom_bsd.c" script from either > > sys/conf/files or all of sys/conf/files.*? > > This is not the cause of the problem. The build is not disturbed by > this config(8) bug. > > The reason for the failure is that the alpha bus_sppace code does not > have the function that ahd needs. It either needs to be implemented > or ahd needs to be removed from the alpha build. ahd works on ia64 > and sparc64, so dont add it to the i386-only section. > > However, there are hundreds more failures after this. Fixing this one > just gets us to the next failure. > I did not say it was the reason for a failure, I asked Poul to remove the offending lines to eliminate the quoted warning. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg44708/pgp0.pgp Description: PGP signature
Re: X problems & 5.0... -RELEASE?
On Mon, 14 Oct 2002, Steve Kargl wrote: > On Tue, Oct 15, 2002 at 12:39:26PM +1000, Tim Robbins wrote: > > On Mon, Oct 14, 2002 at 01:00:46PM -0700, Kris Kennaway wrote: > > > > [...] > > > Did anyone test -current with the various FP test suites people posted > > > about last week? I run some of them occasionally (last ran ucbtest on June 18), but they are perfectly irrelevant to this problem since they don't use signals in any significant way. > > Yes. I ran paranoia from http://cm.bell-labs.com/netlib/paranoia/ and > > found that FP arithmethic is satisfactory when -O is not used, and no > > -march or -mcpu options are used. > > > > However, compiling with -O causes a lot of failures. > > Are you using an intel cpu? You need to add -ffloat-store > to get the correct results due to the 80 bit FPU registers. > Otherwise, intermediate results are stored with higher > precision. This is a well-known bug in gcc. Intermediate results may be computed with higher precision. paranioa knows this and uses lots of assignments to clip the results to double (or single) precision, aa is required to work by C standards (very fuzzily in C90 and very clearly in C99). This doesn't actually work in the i386 gcc. The -ffloat-store hack works around this and gives much the same pessimizations as would a standards conforming compiler. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X problems & 5.0... -RELEASE?
Tim Robbins writes: > > It's worth noting that 4.7-RELEASE (w/ gcc 2.95.4) fails *more* test cases > than -CURRENT when -O is used to compile paranoia. Does 2.95.4 fail the same tests or different ones? Also, this program doesn't deal with signals, which is where I suspect the problem may be (ie, not the compiler but the kernel). If you understand this code, can you write and install signal handler for, say, sigusr1 and have another programe fire sigusr1's at the math test? Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Making an "Fbone"
On Mon, 14 Oct 2002, Julian Elischer wrote: > > > > On Mon, 14 Oct 2002, Julian Elischer wrote: > > > > but it'd be nice if FreeBSD could build it's own "conference-net" > > so we could do that sort of thing.. > > > > > > I've used Vic, and wb, but we don't have a mbone to run it on any more > > really.. > > uunet was charging for it last I looked.. We need to work out some > > way to organise our own "Fbone" :-) > > > > So, What would be the tools of choice? > someone mentionned gnomemeeting, and there are the old Multicast tools > e.g. vic/wb/sdr etc. > any other suggestions? > and what would be a good suggestion for cheap cameras people > could just go out and buy... > > Is there a good selection of white-board tools? > > If freebsd woudl act as a hub on an mbone or similar distribution scheme > how woudl we organise he topolgy? how would we work out where a new > user should tap into the net? It seems to me tunneling similar to the Six to Four method would be quite cool for a "virtual MBone" or "Fbone" where there was of course a central tunnel hub or something. I'm not sure, since the latency would be high. -Trish -- Trish Lynch[EMAIL PROTECTED] Ecartis Core Team [EMAIL PROTECTED] EFNet IRC Oper @ efnet.dkom.atAilleCat@EFNet UNIXNet IRC Admin @ femme.ipv6.sapphite.org AilleCat@UNIXNet Key fingerprint = C44E 8E63 6E3C 18BD 608F E004 9DC7 C2E9 0E24 DFBD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM question
On Tue, 15 Oct 2002, walt wrote: > Poul-Henning Kamp wrote: > > In message <[EMAIL PROTECTED]>, walt writes: > > > >>Would the GEOM framework make it feasible to use a DOS-extended/logical > >>partition for a BSD filesystem? > > > We already support that as far as I know, both with and without GEOM > > Yes! The reason I could never make it work is because of an 'error' > in the man page for newfs: > > "Before running newfs the disk must be labeled using disklabel(8)" > > Well, disklabel won't work on an extended/logical partition so I > never actually got as far as newfs until just now. Turns out that > newfs works just great without a disklabel on a logical partition. Um, disklabel works on any slice. E.g.: %%% Script started on Wed Oct 16 03:23:36 2002 ttyv1:root@gamplex:/tmp> fdisk /dev/ad2 *** Working on device /dev/ad2 *** parameters extracted from in-core disklabel are: cylinders=1123 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1123 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT) start 63, size 2104452 (1027 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 130/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 2104515, size 9189180 (4486 Meg), flag 80 (active) beg: cyl 131/ head 0/ sector 1; end: cyl 702/ head 254/ sector 63 The data for partition 3 is: sysid 131 (0x83),(Linux native) start 11293695, size 1028160 (502 Meg), flag 0 beg: cyl 703/ head 0/ sector 1; end: cyl 766/ head 254/ sector 63 The data for partition 4 is: sysid 130 (0x82),(Linux swap or Solaris x86) start 12321855, size 273105 (133 Meg), flag 0 beg: cyl 767/ head 0/ sector 1; end: cyl 783/ head 254/ sector 63 ttyv1:root@gamplex:/tmp> disklabel ad2s3 disklabel: ioctl DIOCGDINFO: Invalid argument ttyv1:root@gamplex:/tmp> disklabel -rw ad2s3 auto disklabel: cannot open /dev/ad2s3c: No such file or directory disklabel: auto: unknown disk type ttyv1:root@gamplex:/tmp> ln /dev/ad2s3 /dev/ad2s3c ttyv1:root@gamplex:/tmp> disklabel -rw ad2s3 auto ttyv1:root@gamplex:/tmp> disklabel ad2s3 # /dev/ad2s3c: type: unknown disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 1020 sectors/unit: 1028160 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 10281600unused0 0 # (Cyl.0 - 1019) ttyv1:root@gamplex:/tmp> exit Script done on Wed Oct 16 03:25:07 2002 %%% This puts a label on an unused Linux partition (ad2s3). I had to create /dev/ad2s3c because I don't use devfs and this device didn't already exist. I used a link instead of MAKEDEV because that is easier. It is a historical bug that disklabel wants a 'c' partition. "disklabel /dev/ad2s3" should work, but bogusly refuses to work for the "auto" case. disklabel also works on almost anything that can be read and written to, given suitable parameters. E.g.: %%% Script started on Wed Oct 16 03:37:13 2002 ttyv2:bde@gamplex:/tmp> cd /tmp ttyv2:bde@gamplex:/tmp> dd if=/dev/zero of=foo bs=1440k count=1 1+0 records in 1+0 records out 1474560 bytes transferred in 0.101175 secs (14574358 bytes/sec) ttyv2:bde@gamplex:/tmp> disklabel -rw /tmp/foo floppy ttyv2:bde@gamplex:/tmp> disklabel /tmp/foo disklabel: ioctl DIOCGDINFO: Inappropriate ioctl for device ttyv2:bde@gamplex:/tmp> disklabel -r /tmp/foo # /tmp/foo: type: unknown disk: fd1440 label: flags: bytes/sector: 512 sectors/track: 18 tracks/cylinder: 2 sectors/cylinder: 36 cylinders: 80 sectors/unit: 2880 rpm: 300 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 28800unused 512 4096 # (Cyl.0 - 79) b: 28800unused 512 4096 # (Cyl.0 - 79) c: 28800unused 512 4096 # (Cyl.0 - 79) ttyv2:bde@gamplex:/tmp> exit Script done on Wed Oct 16 03:37:56 2002 %%% Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.8 broken in current
David O'Brien schrieb: >On Mon, Oct 14, 2002 at 01:44:07PM -0700, Alex Zepeda wrote: > > >>So turn off the optimizations? >> >> > >No in -CURRENT with GCC 3.2, we want to know when -O2 causes a problem. > > > >>gcc's code optimizations are broken, and should be avoided. >> >> > >Not any more with GCC 3.2, unless you have a test case to prove it broken. > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > > The errors during "make test" are only one issue. What bothers me even more ist the high runtime of some of the tests (up to several *hours*). Finally a "make test" completed on my machine (perl-5.8 compiled without optimizations, which isn't a big issue, see my previous mail showing run times of one test): All tests successful. u=13.8672 s=5.61719 cu=21700.3 cs=2264.12 scripts=666 tests=68469 36915,89 real 21726,29 user 2278,34 sys The same tests on Solaris/x86 (processor ~40% faster) only take 12 minutes. Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
unbreaking buildkernel?
Yes, I know that buildworld will fix the toolchain but is there a more granular fix? cd /usr/src/gnu && make install ? FYI, buildworld takes hours and I have some kernel changes to test before committing. -Nate linking kernel.debug ld: target elf32-i386-freebsd not found *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.8 broken in current
On Tue, Oct 15, 2002 at 07:31:28PM +0200, Daniel Rock wrote: > The errors during "make test" are only one issue. What bothers me even > more ist the high runtime of some of the tests (up to several *hours*). > Finally a "make test" completed on my machine (perl-5.8 compiled without > optimizations, which isn't a big issue, see my previous mail showing run > times of one test): > > All tests successful. > u=13.8672 s=5.61719 cu=21700.3 cs=2264.12 scripts=666 tests=68469 >36915,89 real 21726,29 user 2278,34 sys > > The same tests on Solaris/x86 (processor ~40% faster) only take 12 minutes. It would help if you can do some form of profiling to work out what exactly is taking longer. Kris msg44715/pgp0.pgp Description: PGP signature
Re: fdisk -u with geom
In message <[EMAIL PROTECTED]>, Mark Santcroos writes: >What's the equivalent of fdisk -u with geom? >( Assuming that it's not the same after getting: >laptop# fdisk -u ad0 >fdisk: can't open device /dev/ad0 >fdisk: cannot open disk /dev/ad0: Operation not permitted ) This currently does not work if you have open partitions under that device, I have patches underway for that. -- 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 what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unbreaking buildkernel?
In the last episode (Oct 15), Nate Lawson said: > Yes, I know that buildworld will fix the toolchain but is there a > more granular fix? cd /usr/src/gnu && make install ? > > FYI, buildworld takes hours and I have some kernel changes to test > before committing. I reinstalled src/gnu/usr.bin/binutils, which seems to have worked. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: anybody help? undefined reference to 'xstrtod' occuring
On 14-Oct-2002 (18:10:16/GMT) David Francheski wrote: > I'm trying to upgrade from a 5.0 DP1 system to the latest -current > (as of last week sometime). I recently asked a similar question: upgrade from a too old -CURRENT (May 15) to a recent one. The solution was some small intermediate update, I use this dates and they worked fine: *default date=2002.08.15.00.00.42 *default date=2002.08.26.00.00.42 *default date=2002.09.09.00.00.42 *default date=2002.09.15.00.00.42 This means 4 more builds, but it worked for me. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Xfree86, GNOME, KDE freezing over
Hi, I am running a current from 22nd of september. I compiled gnome2 using the ports method. after some help from people in this list i finally installed it. Now as soon as I startup gnome in X the computer freezes. So I compiled and installed kde3 and the same thing happens. Simple X with just twm seemed to run fine(xterm and a whole bunch of X utilities and all), untill I displayed a remote netscape on this display, which is when this froze over again. Other things that freeze the computer are mozilla running under twm within 10 seconds of startup even just the sawfish window manager freezes as soon as I resize any window. I have no idea how to get more info or catch this bug It just gives no error nothing, even in a generic Kernel with all the debugging features turned on! ANY CLUES, SUGGESTIONS Any one running these applications on current successfully? Anyways here is what I did further. It seems as if the problem is in some package that is used by all these applications. So I gathered a list of dependency packages for all these and started looking for common members. There are tons no surprise there. among all however the common members seem to be Dependency: libiconv-1.8_1 Dependency: lcms-1.08 Dependency: freetype2-2.1.2 of these lcms and libiconv seem to be ruled out in XFree-* dependency list. So the most/(only?) common package in all these software seems to be freetype2-2.1.2 Another thing i noticed is that kde starts up fine : displays a couple of windows and then right around then while displaying one of the windows it freezes half way through. Sort of leaving a feeling that it froze over while rendering some graphics or doing font manipulation calculation.. is freetype the real culprit, I do not know! ofcourse all this could very well be no more than a hunch. Any help will be very much appreciated. thanks and best regards, Saurabh Gupta To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unbreaking buildkernel?
On Tue, 15 Oct 2002, Dan Nelson wrote: > In the last episode (Oct 15), Nate Lawson said: > > Yes, I know that buildworld will fix the toolchain but is there a > > more granular fix? cd /usr/src/gnu && make install ? > > > > FYI, buildworld takes hours and I have some kernel changes to test > > before committing. > > I reinstalled src/gnu/usr.bin/binutils, which seems to have worked. cd /usr/src/gnu/usr.bin/binutils; make cleandir; make depend; make all install Installed everything, same error. I also copied ld + ldscripts to: /usr/obj/usr/src/i386/usr/libdata/ldscripts Same error. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Laptop lockup on re-inserting CD-RW after "atacontrol detach 1"
This happened to me about a week ago under -STABLE, and again today under -STABLE, so I tried it under -CURRENT today (in single-user mode, to reduce variables), and was able to re-create it. I *believe* that I had successfully inserted the drive after "atacontrol detach 1" shortly after the atacontrol-related changes were MFCed. This laptop is a Dell Inspiron 5000e. (In fairness, I should point out that the laptop I was using until about 3 weeks ago was very similar, and actually had the same manufacturer. It was, however, somewhat different, even though the peripherals, batteries, and disk drive are interchangeable -- and the disk drive I'm using now is the same one I have been using since March, 2001.) I track -STABLE and -CURRENT (on different slices) daily on the machine. (One rason I do it this way is to be able to compare -STABLE and -CURRENT on precisely the same hardware.) Under -STABLE (which I'm running at the moment) here is some data of interest: g1-9(4.7-S)[1] vmstat -i interrupt total rate mux irq11 66477 76 ata0 irq14 4809 5 ata1 irq15 4 0 fdc0 irq6 2 0 atkbd0 irq1 2310 2 psm0 irq12 2538 2 ppc0 irq7 1 0 clk irq086892 99 Total 163033187 g1-9(4.7-S)[2] uname -a FreeBSD g1-9.catwhisker.org 4.7-STABLE FreeBSD 4.7-STABLE #318: Tue Oct 15 06:16:15 PDT 2002 [EMAIL PROTECTED]:/common/S1/obj/usr/src/sys/LAPTOP_30W i386 g1-9(4.7-S)[3] sudo atacontrol list Password: ATA channel 0: Master: ad0 ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI rev 0 Slave: no device present g1-9(4.7-S)[4] The drive in question is /dev/acd0 -- the Matsushita UJDA310L. I booted the machine to -CURRENT, in single-user mode, then: * fsck -p * mount -a * umount /common[Large file system; not needed for this experiment] * atacontrol list * atacontrol detach 1 * atacontrol list > removed CD-RW drive; machine reported "stray interrupt IRQ 15" * atacontrol list [still shows nothing cnnected to channel 1] > re-inserted CD-RW drive [screen went blank; machine unresponsive to all but power cycle] I recently obtained a DVD/CD (read-only) drive (Toshiba DVD-ROM drive, model SD-C2402), and I am able to insert it OK: g1-9(4.7-S)[6] sudo atacontrol list Password: ATA channel 0: Master: ad0 ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI rev 0 Slave: no device present g1-9(4.7-S)[7] sudo atacontrol detach 1 g1-9(4.7-S)[8] sudo atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present g1-9(4.7-S)[9] sudo atacontrol list Password: ATA channel 0: Master: ad0 ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present g1-9(4.7-S)[10] sudo atacontrol attach 1 Master: acd0 ATA/ATAPI rev 0 Slave: no device present g1-9(4.7-S)[11] sudo atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI rev 0 Slave: no device present g1-9(4.7-S)[12] Now, the above was under -STABLE (ref. the prompts), but it was under -STABLE that I first noticed the lockup(/panic?) from inserting the CD-RW drive. How may I help get this fixed? (I do have a CVS repo available that I update (at least) daily, and I have a spare slice where I can clone either -CURRENT or -STABLE and hack at it.) Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] To paraphrase David Hilbert, there can be no conflicts between the discipline of systems administration and Microsoft, since they have nothing in common. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unbreaking buildkernel?
On Tue, 15 Oct 2002, Nate Lawson wrote:
> Yes, I know that buildworld will fix the toolchain but is there a more
> granular fix? cd /usr/src/gnu && make install ?
>
> FYI, buildworld takes hours and I have some kernel changes to test before
> committing.
Just edit ldscript.i386? This is what I did to unbreak building of
RELENG_4 kernels under -current:
%%%
Index: ldscript.i386
===
RCS file: /home/ncvs/src/sys/conf/ldscript.i386,v
retrieving revision 1.4.2.1
diff -u -2 -r1.4.2.1 ldscript.i386
--- ldscript.i386 20 Sep 2001 09:29:23 - 1.4.2.1
+++ ldscript.i386 15 Oct 2002 19:02:16 -
@@ -1,4 +1,4 @@
/* $FreeBSD: src/sys/conf/ldscript.i386,v 1.4.2.1 2001/09/20 09:29:23 peter Exp $ */
-OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
+OUTPUT_FORMAT("elf32-i386-freebsd", "elf32-i386-freebsd", "elf32-i386-freebsd")
OUTPUT_ARCH(i386)
ENTRY(btext)
%%%
Similarly to unbreak building of RELENG_4 kernels under -current.
The reverse patch might unbreak building of -current kernels under
-not-very-current.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PCI problems with today's current
On Tue, Oct 15, 2002 at 22:17:53 +0900, Mitsuru IWASAKI wrote: > Hi, > > > But never mind, you can force to compile the ASL and generate DSDT; > > > # iasl -i SupermicroP3TDE6.new.asl > > > then copy generated acpi_dsdt.aml to /boot/. > > > # cp acpi_dsdt.aml /boot/ > > > > Okay, I did that, and then typed the following at the boot prompt: > > > > set acpi_dsdt_load="YES" > > set acpi_dsdt_name="/boot/acpi_dsdt.aml" > > > > Things still don't seem to be working properly. I've attached dmesg > > output. > [snip] > > Preloaded elf kernel "/boot/kernel.test32/kernel" at 0xc0569000. > > Preloaded elf module "/boot/kernel.test32/acpi.ko" at 0xc05690b0. > > Timecounter "i8254" frequency 1193182 Hz > > Hmm, it seems that /boot/acpi_dsdt.aml doesn't to be loaded. > I think `set acpi_dsdt_load="YES"' at the boot prompt is not > effective. > How about having acpi_dsdt_load="YES" in your loader.conf, or > typing `load -t acpi_dsdt /boot/acpi_dsdt.aml' at the boot prompt ? I tried 'load -t...', and the aml file seems to get loaded. Things don't fail in the same way now, but I still can't see ti0, which is on the PCI bus in question. I've attached the dmesg. Ken -- Kenneth Merry [EMAIL PROTECTED] Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #5: Sun Oct 13 22:38:04 MDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/home/ken/perforce/FreeBSD-ken/src/sys/gondolin Preloaded elf kernel "/boot/kernel/kernel" at 0xc057. Preloaded acpi_dsdt "/boot/acpi_dsdt.aml" at 0xc05700a8. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05700f0. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1266.07-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff real memory = 2684289024 (2621376K bytes) avail memory = 2602532864 (2541536K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS ACPI-0623: *** Warning: Type override - [DEB_] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [MLIB] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [IO__] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [DATA] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [SIO_] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [SB__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [ICNT] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [ACPI] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [OSB4] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [BIOS] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0623: *** Warning: Type override - [CMOS] had invalid type (Integer) for Scope operator, changed to (Scope) npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz Using $PIR table, 10 entries at 0xc00f52e0 can't fetch resources for \\_SB_.NRTH - AE_AML_OPERAND_TYPE acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_cpu2: on acpi0 acpi_cpu3: on acpi0 acpi_button0: on acpi0 pcib0: on acpi0 initial configuration before setting priority for links before fixup boot-disabled links - after fixup boot-disabled links -- arbitrated configuration - pci0: on pcib0 IOAPIC #1 intpin 10 -> irq 2 IOAPIC #1 intpin 11 -> irq 5 IOAPIC #1 intpin 15 -> irq 9 pcib1: at device 0.1 on pci0 initial configuration before setting priority for links -
Re: unbreaking buildkernel?
On Tue, 15 Oct 2002, Dan Nelson wrote: > In the last episode (Oct 15), Nate Lawson said: > > On Tue, 15 Oct 2002, Dan Nelson wrote: > > > In the last episode (Oct 15), Nate Lawson said: > > > > Yes, I know that buildworld will fix the toolchain but is there a > > > > more granular fix? cd /usr/src/gnu && make install ? > > > > > > > > FYI, buildworld takes hours and I have some kernel changes to test > > > > before committing. > > > > > > I reinstalled src/gnu/usr.bin/binutils, which seems to have worked. > > > > cd /usr/src/gnu/usr.bin/binutils; make cleandir; make depend; make all > > install > > Is your src/contrib/binutils up-to-date? > > -- > Dan Nelson > [EMAIL PROTECTED] Sorry, pilot error. Somewhere between updating from cvsup-master and cvsup3 the binutils changes didn't make it into my local repository. Everything works now. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Surprise! (Re: HEADS UP: Port recompiles needed (Re: Unknown symbol"__sF"))
Kris Kennaway wrote: > Peter removed the stdio transitional aid for older -current systems. > This means that older 5.0 libraries are no longer compatible with the > new 5.0 libc, and you will need to recompile everything that depends > on them. 4.x applications (i.e. things that link with libc.so.4) > should be unaffected. After the first shock i decided to see it as a challenge, got a fresh drive and decided to reinstall the whole (grown over the years ...) system - preparing for the worst :-) I am really, really astonished: all went smoothly! XFree86-4, the complete kde3 (i never managed to compile kde on stable or current before without the need to adjust something !), Staroffice52 and vmware all compiled out of the box and ran out of the box (just vmware2, i had to relink /compat/linux/dev/vmnet1 to /dev/vmnet1). The rest is not worth to mention, i did not noticed _any_ showstopper yet! This is cool! I'd like to thank everyone involved for the good work! hellmuth -- Hellmuth MichaelisHamburg, Europe[EMAIL PROTECTED]www.kts.org There is a difference between an open mind and a hole in the head. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unbreaking buildkernel?
In the last episode (Oct 15), Nate Lawson said: > On Tue, 15 Oct 2002, Dan Nelson wrote: > > In the last episode (Oct 15), Nate Lawson said: > > > Yes, I know that buildworld will fix the toolchain but is there a > > > more granular fix? cd /usr/src/gnu && make install ? > > > > > > FYI, buildworld takes hours and I have some kernel changes to test > > > before committing. > > > > I reinstalled src/gnu/usr.bin/binutils, which seems to have worked. > > cd /usr/src/gnu/usr.bin/binutils; make cleandir; make depend; make all > install Is your src/contrib/binutils up-to-date? -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
GEOM/fdisk/USB drive problem
fdisk against my USB flash drive crashes with divide by zero. It turns out that get_params() starts with some default values (since there is no disklabel) and then runs some ioctls: DIOCGFWSECTORS and DIOCGFWHEADS. The problem is that fdisk checks the error from that ioctl and then happily uses whatever parameters it returned. My question is, should I add the error checking in userland (error == 0 && sector != 0) or in g_dev_ioctl? IMO, it should be in g_dev_ioctl so that we only have to validate the data in one place instead of multiple utilities (fdisk, disklabel, ...?) -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM/fdisk/USB drive problem
In message <[EMAIL PROTECTED]>, Nate Lawson wri tes: >fdisk against my USB flash drive crashes with divide by zero. It turns >out that get_params() starts with some default values (since there is >no disklabel) and then runs some ioctls: DIOCGFWSECTORS and DIOCGFWHEADS. > >The problem is that fdisk checks the error from that ioctl and then >happily uses whatever parameters it returned. My question is, should I >add the error checking in userland (error == 0 && sector != 0) or in >g_dev_ioctl? IMO, it should be in g_dev_ioctl so that we only have to >validate the data in one place instead of multiple utilities (fdisk, >disklabel, ...?) I really think it belongs in userland and not in the kernel. The "FW" values are advisory, and if they are not there or not sensible, userland should cope. I could agree to make g_dev_ioctl fail the ioctl with some errno if they came back as zero, but not substituting another value. -- 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 what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM/fdisk/USB drive problem
On Tue, 15 Oct 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Nate Lawson wri
> tes:
> >fdisk against my USB flash drive crashes with divide by zero. It turns
> >out that get_params() starts with some default values (since there is
> >no disklabel) and then runs some ioctls: DIOCGFWSECTORS and DIOCGFWHEADS.
> >
> >The problem is that fdisk checks the error from that ioctl and then
> >happily uses whatever parameters it returned. My question is, should I
> >add the error checking in userland (error == 0 && sector != 0) or in
> >g_dev_ioctl? IMO, it should be in g_dev_ioctl so that we only have to
> >validate the data in one place instead of multiple utilities (fdisk,
> >disklabel, ...?)
>
> I really think it belongs in userland and not in the kernel.
>
> The "FW" values are advisory, and if they are not there or not
> sensible, userland should cope.
>
> I could agree to make g_dev_ioctl fail the ioctl with some errno
> if they came back as zero, but not substituting another value.
The attached patch makes everything work fine for my drive (64 MB USB
flash).
-Nate
fdisk: can't get disk parameters on /dev/da0; supplying dummy ones
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=129024 heads=1 sectors/track=1 (1 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=129024 heads=1 sectors/track=1 (1 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 6 (0x06),(Primary 'big' DOS (>= 32MB))
start 32, size 128480 (62 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 250/ head 15/ sector 32
The data for partition 2 is:
The data for partition 3 is:
The data for partition 4 is:
Index: sys/geom/geom_dev.c
===
RCS file: /home/ncvs/src/sys/geom/geom_dev.c,v
retrieving revision 1.25
diff -u -r1.25 geom_dev.c
--- sys/geom/geom_dev.c 7 Oct 2002 06:25:26 - 1.25
+++ sys/geom/geom_dev.c 15 Oct 2002 12:46:35 -
@@ -245,15 +245,23 @@
switch (cmd) {
case DIOCGSECTORSIZE:
error = g_io_getattr("GEOM::sectorsize", cp, &i, data);
+ if (error == 0 && *(u_int *)data == 0)
+ error = EINVAL;
break;
case DIOCGMEDIASIZE:
error = g_io_getattr("GEOM::mediasize", cp, &i, data);
+ if (error == 0 && *(u_int *)data == 0)
+ error = EINVAL;
break;
case DIOCGFWSECTORS:
error = g_io_getattr("GEOM::fwsectors", cp, &i, data);
+ if (error == 0 && *(u_int *)data == 0)
+ error = EINVAL;
break;
case DIOCGFWHEADS:
error = g_io_getattr("GEOM::fwheads", cp, &i, data);
+ if (error == 0 && *(u_int *)data == 0)
+ error = EINVAL;
break;
case DIOCGFRONTSTUFF:
error = g_io_getattr("GEOM::frontstuff", cp, &i, data);
Debug: Signal 11 caught. That's bad!
System: Asus A7M266-D wAMD-768 Chipset, on dual Athalon MP 1900, 512 MB ram, generic ATI card and Intel Pro 100 nic. (dmesg currently unavailable...) When I try to install FreeBSD-current based on snapshot bootable CD (most recent) I get the following when trying to setup partitions Debug: installCommit: System state is "init" Debug: diskpartitionwrite: Examining 1 devices Debug: Notify: writing partition information to device ad1 ad1: hard error reading fsbn 65 (ad1 bn 65, cn 0 tn 1 sn 2) trying PIO mode ad1 hard errer reading fsbn 65 (ad1 bn 65, cn 0 tn 1 sn 2) states = 59 error = 40 Debug: Signal 11 caught! that's bad! I have by default 3 60GB ATA Maxtor drives in the tower. I have removed the 2 on the secondary and the install still fails. I have tried reversing the order of the disk (HD as either master or slave and it still fails). I have tried one of the two other disks and I have the same problem with it as well. This problem alternates between finding my primary drives or not finding my primary devices on boot. Any ideas? (Plug and Pray bios and all that jazz have been disabled). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI problems with today's current
> > How about having acpi_dsdt_load="YES" in your loader.conf, or > > typing `load -t acpi_dsdt /boot/acpi_dsdt.aml' at the boot prompt ? > > I tried 'load -t...', and the aml file seems to get loaded. Things don't > fail in the same way now, but I still can't see ti0, which is on the PCI > bus in question. OK, now that all PCI bridges were probed, but the last one seems to have wrong bus number. > pcib2: on acpi0 > initial configuration > before setting priority for links > before fixup boot-disabled links - > after fixup boot-disabled links -- > arbitrated configuration - > pci3: on pcib2 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 As I told before, could you change _BBN value in the patch and try again? From: Mitsuru IWASAKI <[EMAIL PROTECTED]> Subject: Re: PCI problems with today's current Date: Sat, 05 Oct 2002 12:09:47 +0900 (JST) Message-ID: <[EMAIL PROTECTED]> > If still NG, please try the attached patch against SupermicroP3TDE6.asl. > # _BBN is bridge bus number, my guess is 0x3. You can try to change it > # if failed. Maybe 0x2 is correct. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM question
[EMAIL PROTECTED] (Bruce Evans) writes: > On Tue, 15 Oct 2002, walt wrote: > > Well, disklabel won't work on an extended/logical partition... > Um, disklabel works on any slice. E.g.: > ttyv1:root@gamplex:/tmp> disklabel ad2s3 > #size offsetfstype [fsize bsize bps/cpg] > c: 10281600unused0 0 # (Cyl.0 - 1019) We have a semantic problem, as often happens when the DOS and BSD worlds collide. s3 is a 'slice' which is the same as a 'DOS primary partition' and yes, disklabel works on any 'primary' partition. My new BSD filesystem is on ad2s8, which is a DOS 'logical' partition in my 'DOS-extended' (primary) partition ad2s4: #fdisk ad2 The data for partition 4 is: sysid 15 (0x0f),(Extended DOS (LBA)) The logical drive is numbered 's8' because it is the 4th 'logical' drive in the 'extended DOS' slice, and the 'logical' drives are numbered beginning with s5 and work upwards from there, and they don't show up in FBSD's fdisk, unfortunately, though they do show up in /dev. The 'primary' partitions are numbered 1 thru 4 only. I think we have M$ (and perhaps IBM) to thank for this marvelous feature of the PC which has caused so many headaches over the decades. If there is a way to create 'logical' partitions in FreeBSD I'm not aware of it. I usually use PartitionMagic to do all the grunt work of creating and resizing such partitions. And now I can use them as native BSD ufs filesystems, which I never knew until now. Cool! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM/fdisk/USB drive problem
In message <[EMAIL PROTECTED]>, Nate Lawson wri tes: >> I could agree to make g_dev_ioctl fail the ioctl with some errno >> if they came back as zero, but not substituting another value. > >The attached patch makes everything work fine for my drive (64 MB USB >flash). Apart from the choice of EINVAL, this would be OK with me, I would probably say ENOENT instead. EINVAL generally means "you gave a wrong parameter to a syscall", ENOENT is more of a "Looked, found nothing" kind of error. -- 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 what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Debug: Signal 11 caught. That's bad!
Further playing... Disabled UDMA access to no success, however it will install if I install to a secondary disk Go figure... still kinda wanna be able to run it on primary thoughts> CH On Tuesday, October 15, 2002, at 01:58 PM, Colin Harford wrote: > > > System: Asus A7M266-D wAMD-768 Chipset, on dual Athalon MP 1900, 512 > MB ram, generic ATI card and Intel Pro 100 nic. > > (dmesg currently unavailable...) > > When I try to install FreeBSD-current based on snapshot bootable CD > (most recent) I get the following when trying to setup partitions > > > Debug: installCommit: System state is "init" > Debug: diskpartitionwrite: Examining 1 devices > Debug: Notify: writing partition information to device ad1 > ad1: hard error reading fsbn 65 (ad1 bn 65, cn 0 tn 1 sn 2) trying > PIO mode > ad1 hard errer reading fsbn 65 (ad1 bn 65, cn 0 tn 1 sn 2) states = > 59 error = 40 > Debug: Signal 11 caught! that's bad! > > > > I have by default 3 60GB ATA Maxtor drives in the tower. I have > removed the 2 on the secondary and the install still fails. I have > tried reversing the order of the disk (HD as either master or slave > and it still fails). I have tried one of the two other disks and I > have the same problem with it as well. > > > > This problem alternates between finding my primary drives or not > finding my primary devices on boot. > > > Any ideas? > > (Plug and Pray bios and all that jazz have been disabled). > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: Re: cvs commit: src/sys/net pfkeyv2.h
Hi,
I've just committed the following changes. This broke binary
compatibility of IPsec related applications. When upgrading your
kernel, you need to recompile libipsec, netstat(1) and setkey(8). If
you are using racoon(8) or isakmpd(8), you need to reinstall it from
ports, too.
Sincerely,
> On Tue, 15 Oct 2002 13:59:56 -0700 (PDT)
> Hajimu UMEMOTO <[EMAIL PROTECTED]> said:
ume> ume 2002/10/15 13:59:56 PDT
ume> Modified files:
ume> sys/net pfkeyv2.h
ume> Log:
ume> Correct the definitions of SADB_* to be compatible with
ume> RFC2407/IANA assignment. This change breaks binary
ume> compatibility. So, you need to recompile IPsec related
ume> applications.
ume> Revision ChangesPath
ume> 1.8 +16 -16src/sys/net/pfkeyv2.h
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Surprise! (Re: HEADS UP: Port recompiles needed (Re: Unknown symbol "__sF"))
On Tue, Oct 15, 2002 at 11:14:49PM +0200, Hellmuth Michaelis wrote: > I am really, really astonished: all went smoothly! XFree86-4, the complete > kde3 (i never managed to compile kde on stable or current before without > the need to adjust something !), Staroffice52 and vmware all compiled out > of the box and ran out of the box (just vmware2, i had to relink > /compat/linux/dev/vmnet1 to /dev/vmnet1). The rest is not worth to mention, > i did not noticed _any_ showstopper yet! > > This is cool! I'd like to thank everyone involved for the good work! Excellent, thanks for the valuable datapoint! Kris msg44736/pgp0.pgp Description: PGP signature
Re: CNet Pro200WL (Davicom DM9102A): fine under 4.6.2-p2, no worky under -CURRENT
On Sat, Oct 12, 2002 at 04:12:02AM -0500, ryan beasley wrote: > was loaded / probed the card? (FWIW, I'm not seeing any significant > changes to dc_setfilt_21143() between revs 1.9.2.33 and 1.81...) Er, I meant dc_attach. Rilly. Trust me. ;) ( I think I initially guessed there from the 'set our mac address' comment without taking *any* of the surrounding code into context. ) I skimmed over a portion of the DM9102A data sheet, saw the SROM layout, and modified this driver to grab the MAC from that space. It's worked fine ever since. (I sent a pr this morning with said patch, and while my mail logs show the message as having been received as msgID B63E843E3B, it hasn't shown up anywhere.) Thoughts? -- ryan beasley<[EMAIL PROTECTED]> GPG ID: 0x16EFBD48 http://www.goddamnbastard.org # made against if_dcreg.h 1.27 and if_dc.c 1.81 --- sys/pci/if_dcreg.h.orig Tue Oct 15 07:44:12 2002 +++ sys/pci/if_dcreg.h Tue Oct 15 07:42:37 2002 @@ -856,6 +856,11 @@ #define DC_REVISION_DM9102A0x30 /* + * DM9102A MAC address SROM offset. + */ +#defineDC_DM9102_NODEADDR 0x14 + +/* * ADMtek vendor ID. */ #define DC_VENDORID_ADMTEK 0x1317 --- sys/pci/if_dc.c.origTue Oct 15 07:44:08 2002 +++ sys/pci/if_dc.c Tue Oct 15 07:42:29 2002 @@ -1995,6 +1995,9 @@ command &= 0x00FF; command |= 0x8000; pci_write_config(dev, DC_PCI_CFLT, command, 4); + /* See above. ;) */ + dc_eeprom_width(sc); + dc_read_srom(sc, sc->dc_romwidth); break; case DC_DEVICEID_AL981: sc->dc_type = DC_TYPE_AL981; @@ -2142,6 +2145,9 @@ dc_read_eeprom(sc, (caddr_t)&eaddr, 0, 3, 1); break; case DC_TYPE_DM9102: + bcopy(&sc->dc_srom[DC_DM9102_NODEADDR], (caddr_t)&eaddr, + ETHER_ADDR_LEN); + break; case DC_TYPE_21143: case DC_TYPE_ASIX: dc_read_eeprom(sc, (caddr_t)&eaddr, DC_EE_NODEADDR, 3, 0); msg44737/pgp0.pgp Description: PGP signature
alpha tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- >>> Kernel build for GENERIC started on Tue Oct 15 15:10:52 PDT 2002 -- >>> Kernel build for GENERIC completed on Tue Oct 15 15:42:21 PDT 2002 -- >>> Kernel build for LINT started on Tue Oct 15 15:42:21 PDT 2002 -- ===> vinum "Makefile", line 4244: warning: duplicate script for target "geom_bsd.o" ignored cc1: warnings being treated as errors /h/des/src/sys/dev/aic7xxx/ahd_pci.c: In function `ahd_pci_map_registers': /h/des/src/sys/dev/aic7xxx/ahd_pci.c:171: warning: implicit declaration of function `bus_space_subregion' *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bad system call: aio_read()
< said: > I am trying to port the ACE library ( > http://www.cs.wustl.edu/~schmidt/ACE.html ) to FreeBSD-CURRENT, and > it is very confusing that code in -STABLE which compiled and worked, > does not work the same way in -CURRENT. (ie. the code compiles, but > it crashes because of a new kernel option not being enabled or a > module not being kldload'ed). The code is erroneous. In -current, _POSIX_ASYNCHRONOUS_IO is defined with value zero, which indicates that an application must call pathconf() or fpathconf() with key _PC_ASYNC_IO to determine whether AIO is supported for the path or file descriptor in question. If you call AIO functions without first checking whether they are available in the run-time environment, your computer is liable to turn into a frog. Other nasty things, such as abnormal program termination resulting from SIGSYS, may also happen. (If the code actually did this, it would find that FreeBSD's implementation of pathconf() is somewhat broken and always fails for this key. This is on my list of things to fix in my Copious Free Time, but if a Junior Kernel Hacker cared to do it for me I wouldn't mind at all.) -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.8 broken in current
Kris Kennaway schrieb: >On Tue, Oct 15, 2002 at 07:31:28PM +0200, Daniel Rock wrote: > > > >>The errors during "make test" are only one issue. What bothers me even >>more ist the high runtime of some of the tests (up to several *hours*). >>Finally a "make test" completed on my machine (perl-5.8 compiled without >>optimizations, which isn't a big issue, see my previous mail showing run >>times of one test): >> >>All tests successful. >>u=13.8672 s=5.61719 cu=21700.3 cs=2264.12 scripts=666 tests=68469 >> 36915,89 real 21726,29 user 2278,34 sys >> >>The same tests on Solaris/x86 (processor ~40% faster) only take 12 minutes. >> >> > >It would help if you can do some form of profiling to work out what >exactly is taking longer. > >Kris > > Ok, I tried it but the results are very strange. I recompiled perl with profiling enabled and ran the test t/op/pat.t gprof "thinks" the runtime is only 8 seconds, while in reality it takes more than 2 minutes to complete the test. A small excerpt from gprof output FreeBSD: granularity: each sample hit covers 4 byte(s) for 0.01% of 8.15 seconds called/total parents index %timeself descendents called+selfname index called/total children [...] [2] 92.10.007.50 main [2] 0.004.88 1/1 perl_parse [3] 0.002.01 1/1 perl_destruct [6] 0.000.35 1/1 perl_run [22] 0.000.26 1/1 perl_construct [31] 0.000.00 1/1 __fpsetreg [1807] 0.000.00 1/1 perl_alloc [817] 0.000.00 1/1 perl_free [818] Solaris: granularity: each sample hit covers 4 byte(s) for 0.02% of 10.13 seconds called/total parents index %timeself descendents called+selfname index called/total children 0.005.79 1/1 _start [2] [1] 57.10.005.79 1 main [1] 0.003.80 1/1 perl_parse [5] 0.001.21 1/1 perl_destruct [8] 0.000.56 1/1 perl_construct [15] 0.000.21 1/1 perl_run [27] 0.000.00 1/1 perl_alloc [600] 0.000.00 1/1 perl_free [610] 0.000.00 1/1 _pthread_atfork [624] 0.000.00 1/1 _signal [2752] 0.000.00 1/1 pthread_mutex_destroy [943] Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI problems with today's current
On Wed, Oct 16, 2002 at 04:59:18 +0900, Mitsuru IWASAKI wrote: > > > How about having acpi_dsdt_load="YES" in your loader.conf, or > > > typing `load -t acpi_dsdt /boot/acpi_dsdt.aml' at the boot prompt ? > > > > I tried 'load -t...', and the aml file seems to get loaded. Things don't > > fail in the same way now, but I still can't see ti0, which is on the PCI > > bus in question. > > OK, now that all PCI bridges were probed, but the last one seems to > have wrong bus number. Ahh. > > pcib2: on acpi0 > > initial configuration > > before setting priority for links > > before fixup boot-disabled links - > > after fixup boot-disabled links -- > > arbitrated configuration - > > pci3: on pcib2 > > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > > As I told before, could you change _BBN value in the patch and > try again? > > From: Mitsuru IWASAKI <[EMAIL PROTECTED]> > Subject: Re: PCI problems with today's current > Date: Sat, 05 Oct 2002 12:09:47 +0900 (JST) > Message-ID: <[EMAIL PROTECTED]> > > > If still NG, please try the attached patch against SupermicroP3TDE6.asl. > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it > > # if failed. > > Maybe 0x2 is correct. I tried 2, and it seems to work correctly now. Thanks! Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: short uid/gid
At least for our Linux emulation layer, supporting IPC_64 would be one
of the pieces (probably the main one) keeping The Sims from running.
The other thing we are missing is the Linux ioctl() interface for reading
MSDOSFS directories, but that may be optional.
I will eventually take a look at this (IPC_64) if the scheduling fairy brings
me the time.
Danny
[EMAIL PROTECTED]
On Monday 14 October 2002 15:18, Maxim Sobolev wrote:
> Linux solved the problem by introducing a new flag for {msg,shm,sem}ctl(3)
> interfaces (IPC_64), which if set tells the kernel that user supplies
> new version of the structure. The kernel itself internally keeps all
> relevant information already in IPC_64 format, doing conversion before
> returning it to user if IPC_64 isn't set. I think that for portability
> reasons we should at least consider the same or similar route.
>
> -Maxim
>
> On Mon, Oct 14, 2002 at 01:27:57PM -0400, Robert Watson wrote:
> > Yeah, this is a Known Problem, and it's quite unfortunate, actually. I
> > looked at trying to solve it -- changing the types respectively to uid_t,
> > gid_t, and mode_t, but it involved a lot of ABI munging because the
> > structures are shared between the userland interface and the kernel
> > implementation. The result is that any change in the kernel structure
> > really requires you to break out the user structures from the kernel
> > structure, which requires a lot of work. Also, ipc_perm is shared
> > between all three SysVIPC services, and to compound things, there are
> > already ofoo() interfaces for older versions of the structures. My
> > belief is that seperating the user and kernel structures is really
> > necessary -- making a kipc_perm, etc, so we can better support
> > fine-grained locking and extensible security. However, someone has to do
> > the grunt work, and last time I tried, I spent several days and only made
> > a bit of progress. If you want to give a first pass at breaking out the
> > user and kernel structures and send a patch, I'll be happy to work with
> > you to get it integrated. I think the steps are:
> >
> > (1) Divorce user and kernel structures for all of the SysVIPC interfaces,
> > and provide functions to map between them as necessary.
> >
> > (2) Remove the original compatibility interfaces left over from eons ago
> > (and figure out how many eons ago so we know what ABIs we're finally
> > removing).
> >
> > (3) Define new userland versions of necessary structures and create a new
> > set of ofoo() and foo() interfaces based on the change.
> >
> > (4) Go back through and dribble the kernel structures with new toys, such
> > as 'struct label', etc.
> >
> > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
> > [EMAIL PROTECTED] Network Associates Laboratories
> >
> > On Mon, 14 Oct 2002, Vladimir B.
Grebenschikov,Moscow,408-7227,123-4567,Some-info wrote:
> > > Hi
> > >
> > > I have found that SysVIPC functions uses structure with short uid/gid
> > > types.
> > >
> > > What is valid solution ?
> > >
> > > Change types to uid_t/gid_t (but this will broke binary compatibility)
> > > Change syscalls to old_* and add new with "right" structures,
> > > or something else ?
> > >
> > > struct ipc_perm {
> > > ushort cuid; /* creator user id */
> > > ushort cgid; /* creator group id */
> > > ushort uid;/* user id */
> > > ushort gid;/* group id */
> > > ushort mode; /* r/w permission */
> > > ushort seq;/* sequence # (to generate unique msg/sem/shm id) */
> > > key_t key;/* user specified msg/sem/shm key */
> > > };
> > >
> > > --
> > > Vladimir B. Grebenschikov
> > > [EMAIL PROTECTED], SWsoft, Inc.
> > >
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-arch" in the body of the message
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.8 broken in current
On Wed, Oct 16, 2002 at 02:12:07AM +0200, Daniel Rock wrote: > gprof "thinks" the runtime is only 8 seconds, while in reality it takes > more than 2 minutes to complete the test. A small excerpt from gprof output Are you running a kernel with WITNESS enabled? This can really chew up kernel CPU time if you're doing a lot of syscalls. Kris msg44743/pgp0.pgp Description: PGP signature
Re: Kernel panic with panic: kmem_malloc(4096): kmem_map too small...
On Tue, 15 Oct 2002, Makoto Matsushita wrote: > > I'm now trying Terry's patch (just rebuilding a kernel). > > jroberson> You are using 100mb of KVA for malloc(9)? Are you certain > jroberson> that you don't have a memory leak? > > Maybe there's a chance of a memory leakage by GLOBAL, but I don't sure. > > jroberson> How much memory is in this machine? What are you using it > jroberson> for? > > It has 256MB memory, and is used for 5-current release buildbox. > I suspect that there is some other bug then. 1/2 of your memory should not be consumed by kernel malloc. Do you have an abnormally large MD or something? Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
My Old X server vs -current libs
If I try run any X stuff I get: julian@jules:current1(101) startx /usr/libexec/ld-elf.so.1: Undefined symbol "__sF" referenced from COPY relocatio n in xauth /usr/libexec/ld-elf.so.1: Undefined symbol "__sF" referenced from COPY relocatio n in xauth /usr/libexec/ld-elf.so.1: Undefined symbol "__sF" referenced from COPY relocatio n in xauth /usr/libexec/ld-elf.so.1: Undefined symbol "__sF" referenced from COPY relocatio n in xauth /usr/libexec/ld-elf.so.1: Undefined symbol "__sF" referenced from COPY relocatio n in xinit /usr/libexec/ld-elf.so.1: Undefined symbol "__sF" referenced from COPY relocatio n in xauth julian@jules:current1(102) etc. not being an expert in the libraries, I don't really know what the problem is.. Do I need to install a new X? I have no clue as to whether this represents a problem for 4.x compatibility, as I can't remember where I got the X stuff from. Julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: short uid/gid
"Danny J. Zerkel" wrote: > At least for our Linux emulation layer, supporting IPC_64 would be one > of the pieces (probably the main one) keeping The Sims from running. > The other thing we are missing is the Linux ioctl() interface for reading > MSDOSFS directories, but that may be optional. > > I will eventually take a look at this (IPC_64) if the scheduling fairy brings > me the time. Basically, they convert a lot of short fields to what the manual page calls "longs", but which are actually 32 bit values; makes you wonder where they obtained the name "IPC_64", when it should probably more properly be "IPC_32". They pad it out to 36 bytes by adding two unsigned long fields (32 bit longs); gotta wonder why they didn't stop at 32 bytes... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: short uid/gid
On Tue, 15 Oct 2002, Danny J. Zerkel wrote: > At least for our Linux emulation layer, supporting IPC_64 would be one > of the pieces (probably the main one) keeping The Sims from running. > The other thing we are missing is the Linux ioctl() interface for > reading MSDOSFS directories, but that may be optional. > > I will eventually take a look at this (IPC_64) if the scheduling fairy > brings me the time. While I think support for the IPC_64 flag under emulation is useful, I'd rather make use of compatibility system calls and type improvements for the base FreeBSD implementation of the System V IPC APIs. Most of the work necessary to support those changes is required in order to better support fine-grained locking and MAC (breaking out the user and kernel structures). Also, it means future applications will make use of the improved APIs by default. In addition, other systems, such as Solaris, have already made this change in this way, avoiding the IPC_64 flag design. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My Old X server vs -current libs
On Tue, Oct 15, 2002 at 08:58:00PM -0700, Julian Elischer wrote:
> not being an expert in the libraries, I don't really know what the
> problem is..
> Do I need to install a new X?
Yup. I had to rebuild a few things after the switch. The following bit
of sh lets you scan files for this old symbol and figure out which ports
you need to rebuild if you have portupgrade installed.
-- Brooks
#!/bin/sh
sym=__sF
for file in $*; do
if [ -n "`nm ${file} 2>&1 | egrep " ${sym}$"`" ]; then
echo ${file} "\t" `pkg_which $file`
fi
done
msg44748/pgp0.pgp
Description: PGP signature
CD-ROM troubles on i815EP based MB
Hello. I have trouble installing -CURRENT (and booting live snapshot) on MSI MS-6337LE motherboard (which uses i815EP chipset). Kernel just can not find CD :-( This PC has Sony 52x CD-ROM I can boot with same live CD on older VIA-chipset based PC. Also, I have trouble installing anything newer than 4.5-RELEASE on this system. Kernel finds CD device, but goes big loop of "MODE_SENSE_BIG command timeout - reseting" Then it boots but without CD. -- Igor Roboul, System administrator at Speech Technology Center http://www.speechpro.com http://www.speechpro.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM question
On Tue, 15 Oct 2002, walt wrote: > [EMAIL PROTECTED] (Bruce Evans) writes: > > > On Tue, 15 Oct 2002, walt wrote: > > > > Well, disklabel won't work on an extended/logical partition... > > > Um, disklabel works on any slice. E.g.: > > We have a semantic problem, as often happens when the DOS and BSD worlds collide. > > s3 is a 'slice' which is the same as a 'DOS primary partition' and yes, disklabel > works on any 'primary' partition. It works on anything that resembles a disk. All slices of disks resemble disks, and 'DOS logical drives' are mapped to slices. There is nothing special about the slices for 'DOS primary partitions' and 'DOS logical drives' as far as disklabel can tell. > My new BSD filesystem is on ad2s8, which is a DOS 'logical' partition in my > 'DOS-extended' (primary) partition ad2s4: > > #fdisk ad2 > The data for partition 4 is: > sysid 15 (0x0f),(Extended DOS (LBA)) > > The logical drive is numbered 's8' because it is the 4th 'logical' drive in > the 'extended DOS' slice, and the 'logical' drives are numbered beginning > with s5 and work upwards from there, and they don't show up in FBSD's fdisk, > unfortunately, though they do show up in /dev. The 'primary' partitions are > numbered 1 thru 4 only. > > I think we have M$ (and perhaps IBM) to thank for this marvelous feature > of the PC which has caused so many headaches over the decades. Actually, we have Linux to thank for providing an fdisk that supports extended partitions and logical drives, so that we don't need to fix update FreeBSD fdisk to get a free fdisk that supports them :-). > If there is a way to create 'logical' partitions in FreeBSD I'm not aware > of it. I usually use PartitionMagic to do all the grunt work of creating > and resizing such partitions. And now I can use them as native BSD ufs > filesystems, which I never knew until now. Cool! I haven't used extended partitions for many years. I would boot Linux or DOS to create them. The Linux fdisk binary that I have handy (a version from 1997) used to run well enough under FreeBSD to at least display everything. It is now broken by linkage problems (it wants to use the FreeBSD libc.so.5). I never tried it to create partitions, but would expect it to work. Once logical drives are created, you can just use them. This was a design goal in the origianl version of the slice code in 1995. (Don't use extended partitions directly. It is easy to make a mess by clobbering the pointers to the logical drive within them.) Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CD-ROM troubles on i815EP based MB
This should possibly have been posted to -questions... at least half of it has nothing to do with -current. Igor Roboul wrote: > I have trouble installing -CURRENT (and booting live snapshot) on > MSI MS-6337LE motherboard (which uses i815EP chipset). > Kernel just can not find CD :-( This PC has Sony 52x CD-ROM The CDROM boot mechanism operates by using the BIOS; it's totally unrelated to whether or not the hardware is supported or not by FreeBSD. Specifically, the way it works is that the BIOS for the CDROM hardware patches the POST BIOS routines in the system (if it is a seperate CDROM controller), or the system BIOS directly supports booting from CDROM. The BIOS fakes up a floppy disk drive, using the floppy image from the CDROM, which the BIOS locates by searching for a particular file on the CDROM, that references a floppy disk image on the CDROM. If you can not boot FreeBSD from a CDROM at all -- if booting from the CDROM is not an option -- then it is a problem with the BIOS of your system, and not a problem with FreeBSD. Most likely, you need to go into the BIOS setup screen, and change the device boot order, to ensure the CDROM is attempted to boot before the hard drive is attempted. If you have a seperate disk controller card which you have installed for the CDROM to use, you will need to go into the setup for that card, instead of the system BIOS setup. Alternately, you need to upgrade the system BIOS, or the BIOS in the controller to which the CDROM is attached. > I can boot with same live CD on older VIA-chipset based PC. It's the BIOS, not the FreeBSD. > Also, I have trouble installing anything newer than 4.5-RELEASE on > this system. Kernel finds CD device, but goes big loop of > "MODE_SENSE_BIG command timeout - reseting" > Then it boots but without CD. First, record the dmesg for the kernel that works: cd /root dmesg > dmesg_45_OK This *is* a driver problem. As a workaround, you should install the FreeBSD 4.5-RELEASE version on the machine, and then mount the floppy image on the CDROM on a vnode device (man vnconfig) to get the image off. Then, from within the floppy image itself, you will need to copy off the "sysinstall" program to /tmp, so that you have a copy of "sysinstall" that matches the version on the CDROM (the sysinstall program is not available on the CDROM directly because [insert no good reason here]). After you have copied the sysinstall to /tmp, unmount all the vnode devices (you will have used two to get at the sysinstall image), and: cd /tmp ./sysinstall This will run the version off the CDROM. Select "upgrade", and use the "from CDROM" or "from local file system" option, and upgrade. Exit the sysinstall. Now *before you reboot*, run the commands that are not run off a vanilla sysinstall, but are run off a boot sysinstall (again [insert no good reason here]). Specifically: cd /dev sh MAKEDEV all sync When you reboot, the new kernel may or may not recognize your CDROM drive; if not, then you will need to provide a problem report; most likely, though, it's just related to the drivers on the old kernel vs. the new kernel (e.g. some people have removed some historically supported drivers from 4.7 for [insert bogus licensing reason that never mattered before now here]). If your drive is one of these, it's possible to make it work with the 4.7 kernel (this was discussed on -hacker and -current recently). If that's the case, you should find the CDROM announcement line in the dmesg for the 4.5 kernel that you recorded at the start of the upgrade process, and post again to this list, and someone will be able to help you. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CD-ROM troubles on i815EP based MB
On Tue, Oct 15, 2002 at 11:54:50PM -0700, Terry Lambert wrote: > unrelated to whether or not the hardware is supported or not by > FreeBSD. FreeBSD boots from CD, but could not mount / from it :-( Also in 4.6 case, this was system upgraded from sources. But same problem when booting from intall CD. Yet again: system boots, sysinstall starts (in -CURRENT case), but it could not find CD :-(. With 4.6 system boots but without CD, both source upgraded and from installation CD. PS. I'm tracking -CURRENT on various machines from March, 2000. So, I know how system boots from CD. -- Igor Roboul, System administrator at Speech Technology Center http://www.speechpro.com http://www.speechpro.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
