Freebsd 7.2-RC boot problem
Hi, I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Freebsd 7.2-RC boot problem
On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic sata doesn't work issue: acd0: DVDROM Optiarc DVD-ROM DDU1675S/1.10 at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
fsck -C in stable/7 and 7.2
It is quite possible that I messed my local src repo, but this is what I see in stable/7 r191214. fsck(8) describes -C option, fsck mentions this option in its usage message, but: $ fsck -C fsck_ufs: illegal option -- C usage: fsck_ufs [-BCFpfny] [-b block] [-c level] [-m mode] filesystem ... Am I he only one to see this? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
fsck, glabel and sudden paralellism
So I recently switched one system to have only (g)labels instead of raw device names in fstab and noticed that now initial (preen) fsck is performed in parallel on couple of filesystems where before it used to be sequential. Here is a lengthy quote from fsck(8): In preen mode, after pass 1 completes, all remaining file systems are checked, in pass number order running one process per disk drive in par- allel for each pass number in increasing order. In other words: In preen mode all pass 1 partitions are checked sequen- tially. Next all pass 2 partitions are checked in parallel, one process per disk drive. Next all pass 3 partitions are checked in parallel, one process per disk drive. etc. The disk drive containing each file system is inferred from the shortest prefix of the device name that ends in a digit; the remaining characters are assumed to be the partition and slice designators. I think it is highly desirable that fsck knows which filesystems reside on the same disk regardless of how they are referred to. I think that the simple string matching described above is not sufficient these days. Is there an easy geom way to query this info? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Freebsd 7.2-RC boot problem
On Monday 27 April 2009 19:05:16 Ken Smith wrote: On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic sata doesn't work issue: acd0: DVDROM Optiarc DVD-ROM DDU1675S/1.10 at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. Hello, i've got some problem with my SATA Optiarc DVD RW: message output on the screen in not stopped, but repeating with incremental delay: ... acd0: DVDR Optiarc DVD RW AD-7200S/1.06 at ata3-master UDMA33 HEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install run_interrupt_driven hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven hooks: still waiting after 300 seconds for xpt_config ... .. Motherboard is Asus m3n78-em. I've check CD - FreeBSD 7.1-RELEASE disc1 for amd64 - FreeBSD 7.2-RC2 disc1 for amd64 - PCBSD 7.1 DVD for i386 With equally results ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Boot error 16 lba
on 25/04/2009 06:42 Ruben Lara said the following: Hi all, All was working fine, i reboot and now i get: error 16 lba 752991 It seems that error 16 means uncorrectable CRC or ECC error on read result status from INT 13h BIOS routine. My far-fetched guess is that it's either the failing drive or a problem with cabling. No /boot/loader Default: 0:ad(0,ad)/boot/kernel/kernel I lose my system? What can i do? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Freebsd 7.2-RC boot problem
Em 27/04/2009 12:05, Ken Smith escreveu: On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic sata doesn't work issue: acd0: DVDROM Optiarc DVD-ROM DDU1675S/1.10 at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. I can say there is a problem to boot with cdrom since 7.2-BETA1. All system is same, all older version can boot in this machine: 6.1, 6.2, ...,7.1, etc. amd64 or i386. I've burnt 03 media to test 7.2-RC2, one cd-rw burnt with cdrecord and two cd-r burnt first with burncd and last was burnt with cdrecord. What I can do to help this release? Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Freebsd 7.2-RC boot problem
On Mon, 2009-04-27 at 14:10 -0300, Paulo Fragoso wrote: Em 27/04/2009 12:05, Ken Smith escreveu: On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR HL-DT-STDVD-RAM GH22NS30/1.01 at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic sata doesn't work issue: acd0: DVDROM Optiarc DVD-ROM DDU1675S/1.10 at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. I can say there is a problem to boot with cdrom since 7.2-BETA1. All system is same, all older version can boot in this machine: 6.1, 6.2, ...,7.1, etc. amd64 or i386. I've burnt 03 media to test 7.2-RC2, one cd-rw burnt with cdrecord and two cd-r burnt first with burncd and last was burnt with cdrecord. What I can do to help this release? We need more information about how far it gets before it stops. Does it seem like it attempts the boot off the CD at all or does it just fall through to booting off the hard drive? If it does attempt to boot off the CD does it lock up with no messages? If there are messages what are the last few things it says? -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: em0 watchdog timeout (and 3ware problems) 7-stable
Greg, I have another report of this problem, and I have a patch for you to try out, will be sending it out a bit later today. Jack On Sun, Apr 26, 2009 at 5:50 AM, Greg Byshenk free...@byshenk.net wrote: I have one machine that is seeing watchdog timeouts on em0, running 7-STABLE amd64 as of 2009.04.19, and also some other more perverse errors. Twice now in the last 48 hours, this machine has become unreachable via the network, and connecting to the console shows an endless string of [...] em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting messages. The machine is almost locked up. That is, I can get a login prompt, but can go no further than typing in a username; after the username, no password prompt, and nothing further. The only option is to hard reset the machine or to drop to debugger and reboot. Now the perverse part. After restarting, the system partition is no more. Background detail: the machine is a fileserver, with a 3Ware 9650SE-16ML SATA controller, connected to 16 1TB SATA drives, this configured as a 14-drive RAID10 array (+ 2 hot spares), with a 50GB system partition and 6.5TB data partition. The system partition is configured as da1, with one slice and more or less standard partitions for / /var /tmp, etc. (the data partition of the array is sliced with gpt). The issue here is that, upon restart, all parition information on da0 seems to have disappeared, and restarting results in a no operating system found message, and a failure to boot (obviously). But all of the data is still present. If I boot into rescue mode, recreate da0s1, mark it bootable, and restore the bsdlabel, then everything works again. I can restart the machine, and it comes back up normally (it requires an fsck of everything on da0, but after that everything is back to normal). I don't know if this is two unrelated problems, or one problem with two symptoms, or something else. I think that I can safely say that it is not a problem with the 3Ware controller itself, as I replaced the controller with a spare (identical model), and the problem recurred. Additionally, I have an almost-identical configuration on four other machines, none of which are experiencing any problems. One thing that is different is that the other machines use Intel PRO/1000 PF (pci-e) NICs. Is there some known problem with the Intel 2572 fibre NIC? Or some potential interaction of it with the 3ware RAID controller? For the moment, I've set hw.pci.enable_msi=0 (as discussed in the threads on 7.2/bge), and am building a new kernel/world from sources csup'd one hour ago, but I'd really like to hear any ideas about this -- particularly the wiping of the label. Some information about the system: # /dev/da0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 209715204.2BSD0 0 0 b: 8388608 2097152 swap c: 1048561920unused0 0 # raw part, don't edit d: 8388608 104857604.2BSD0 0 0 e: 2097152 188743684.2BSD0 0 0 f: 41943040 209715204.2BSD0 0 0 g: 41941632 629145604.2BSD0 0 0 e...@pci0:4:1:0: class=0x02 card=0x10038086 chip=0x10018086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation'thernet Controller (Fiber)' device = '2572 10/100/1000 Ethernet Controller (Fiber)' class = networktory, range 32, base 0xda00, size 131072, enabled subclass = ethernetory, range 32, base 0xda00, size 131072, enabled bar [10] = type Memory, range 32, base 0xda00, size 131072, enabled bar [14] = type Memory, range 32, base 0xda02, size 65536, enabled0x00 t...@pci0:9:0:0:class=0x010400 card=0x100413c1 chip=0x100413c1 rev=0x01 hdr=0x00 device = '9650SE Series PCI-Express SATA2 Raid Controller' class = mass storage subclass = RAID bar [10] = type Prefetchable Memory, range 64, base 0xd800, size 33554432, enabled bar [18] = type Memory, range 64, base 0xda30, size 4096, enabled bar [20] = type I/O Port, range 32, base 0x3000, size 256, enabled cap 01[40] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 32 messages, 64 bit cap 10[70] = PCI-Express 1 legacy endpoint -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
bsnmpd problems during buildworld
Hi all,
I'm running into an issue during a buildworld. I noticed this problem
early last week, and also after another csup as of this morning.
I've rm'd everything in /usr/obj, but the problem persists. If anyone
could provide info on how I can avoid this, I'd appreciate it:
=== usr.sbin/bsnmpd/modules/snmp_bridge (depend)
cat /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge/bridge_tree.def |
gensnmptree -e dot1dBridge newRoot topologyChange begemotBridgeNewRoot
begemotBridgeTopologyChange begemotBridgeBaseName bridge_oid.h
line 31: '(' expected at begin of node
context: TruthValue ENUM (
*** Error code 1
Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge.
*** Error code 1
Stop in /usr/src/usr.sbin/bsnmpd/modules.
*** Error code 1
Stop in /usr/src/usr.sbin/bsnmpd.
*** Error code 1
Stop in /usr/src/usr.sbin.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
Steve
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Freebsd 7.2-RC boot problem
subbsd wrote: Hello, i've got some problem with my SATA Optiarc DVD RW: message output on the screen in not stopped, but repeating with incremental delay: ... acd0: DVDR Optiarc DVD RW AD-7200S/1.06 at ata3-master UDMA33 HEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install Did you retype this? Or did it really say HEOM? If that's not a typo, you may want to check for RAM errors. run_interrupt_driven hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven hooks: still waiting after 300 seconds for xpt_config I spoke with someone the other day who had that exact same message, and it was due to either a Firewire controller in the BIOS, or a USB card reader. They disabled both at the same time, and the message went away. That appears to be the CAM subsystem probing for root-capable devices, from what I found via Google the other day. Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: fsck -C in stable/7 and 7.2
On 2009-04-27, Andriy Gapon wrote: fsck(8) describes -C option, fsck mentions this option in its usage message, but: $ fsck -C fsck_ufs: illegal option -- C usage: fsck_ufs [-BCFpfny] [-b block] [-c level] [-m mode] filesystem ... Am I he only one to see this? r190357 probably accidentally reverted the code for -C option partially. r190357 | obrien | 2009-03-24 03:51:42 +0200 (Tue, 24 Mar 2009) | 2 lines MFC: r186581: Sound less scary about errorousous disk geometry. r186581 didn't touch fsck_ffs(8) at all. I have cc'd obrien@ who committed r190357. -- Jaakko ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: fsck -C in stable/7 and 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andriy Gapon wrote:
It is quite possible that I messed my local src repo, but this is what I see
in
stable/7 r191214. fsck(8) describes -C option, fsck mentions this option in
its
usage message, but:
$ fsck -C
fsck_ufs: illegal option -- C
usage: fsck_ufs [-BCFpfny] [-b block] [-c level] [-m mode] filesystem ...
Am I he only one to see this?
I think this is a bug (caused by revision 190357). Part of that commit
reverts a previous changeset (see attachment).
Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkn189wACgkQi+vbBBjt66DFfgCePFgPWcWqzjbdU0JvulvX5tFR
d2YAn0FOHlhMbJYG8ow1dS0E48N5S0FE
=v0n/
-END PGP SIGNATURE-
Index: sbin/fsck_ffs/setup.c
===
--- sbin/fsck_ffs/setup.c (revision 191561)
+++ sbin/fsck_ffs/setup.c (working copy)
@@ -65,7 +65,7 @@
/*
* Read in a superblock finding an alternate if necessary.
* Return 1 if successful, 0 if unsuccessful, -1 if file system
- * is already clean (preen mode only).
+ * is already clean (ckclean and preen mode only).
*/
int
setup(char *dev)
@@ -201,7 +201,7 @@
pwarn(USING ALTERNATE SUPERBLOCK AT %d\n, bflag);
bflag = 0;
}
- if (skipclean preen sblock.fs_clean) {
+ if (skipclean ckclean sblock.fs_clean) {
pwarn(FILE SYSTEM CLEAN; SKIPPING CHECKS\n);
return (-1);
}
Index: sbin/fsck_ffs/fsck_ffs.8
===
--- sbin/fsck_ffs/fsck_ffs.8(revision 191561)
+++ sbin/fsck_ffs/fsck_ffs.8(working copy)
@@ -29,7 +29,7 @@
.\@(#)fsck.8 8.4 (Berkeley) 5/9/95
.\ $FreeBSD$
.\
-.Dd January 20, 2009
+.Dd January 25, 2009
.Dt FSCK_FFS 8
.Os
.Sh NAME
@@ -46,9 +46,9 @@
.Ar ...
.Sh DESCRIPTION
The specified disk partitions and/or file systems are checked.
-In preen mode the clean flag of each file system's superblock is examined
-and only those file systems that
-are not marked clean are checked.
+In preen or check clean mode the clean flag of each file system's
+superblock is examined and only those file systems that are not marked clean
+are checked.
File systems are marked clean when they are unmounted,
when they have been mounted read-only, or when
.Nm
@@ -175,6 +175,14 @@
the super block for the file system.
An alternate super block is usually located at block 32 for UFS1,
and block 160 for UFS2.
+.It Fl C
+Check if file system was dismouted cleanly.
+If so, skip file system checks (like preen).
+However, if the file system was not cleanly dismounted, do full checks,
+is if
+.Nm
+was invoked without
+.Fl C .
.It Fl c
Convert the file system to the specified level.
Note that the level of a file system can only be raised.
Index: sbin/fsck_ffs/main.c
===
--- sbin/fsck_ffs/main.c(revision 191561)
+++ sbin/fsck_ffs/main.c(working copy)
@@ -82,7 +82,7 @@
sync();
skipclean = 1;
damagedflag = 0;
- while ((ch = getopt(argc, argv, b:Bc:dDfFm:npy)) != -1) {
+ while ((ch = getopt(argc, argv, b:Bc:CdDfFm:npy)) != -1) {
switch (ch) {
case 'b':
skipclean = 0;
@@ -132,6 +132,10 @@
case 'p':
preen++;
+ /*FALLTHROUGH*/
+
+ case 'C':
+ ckclean++;
break;
case 'y':
@@ -151,7 +155,7 @@
if (signal(SIGINT, SIG_IGN) != SIG_IGN)
(void)signal(SIGINT, catch);
- if (preen)
+ if (ckclean)
(void)signal(SIGQUIT, catchquit);
signal(SIGINFO, infohandler);
if (bkgrdflag) {
@@ -216,7 +220,7 @@
errmsg[0] = '\0';
cdevname = filesys;
- if (debug preen)
+ if (debug ckclean)
pwarn(starting\n);
/*
* Make best effort to get the disk name. Check first to see
@@ -251,7 +255,7 @@
exit(7);/* Filesystem clean, report it now */
exit(0);
}
- if (preen skipclean) {
+ if (ckclean skipclean) {
/*
* If file system is gjournaled, check it here.
*/
@@ -302,7 +306,7 @@
CANNOT RUN IN BACKGROUND\n);
}
if ((sblock.fs_flags FS_UNCLEAN) == 0
- skipclean preen) {
+ skipclean ckclean) {
/*
* file system is clean;
* skip
Re: fsck -C in stable/7 and 7.2
on 27/04/2009 20:49 Jaakko Heinonen said the following: On 2009-04-27, Andriy Gapon wrote: fsck(8) describes -C option, fsck mentions this option in its usage message, but: $ fsck -C fsck_ufs: illegal option -- C usage: fsck_ufs [-BCFpfny] [-b block] [-c level] [-m mode] filesystem ... Am I he only one to see this? r190357 probably accidentally reverted the code for -C option partially. r190357 | obrien | 2009-03-24 03:51:42 +0200 (Tue, 24 Mar 2009) | 2 lines MFC: r186581: Sound less scary about errorousous disk geometry. r186581 didn't touch fsck_ffs(8) at all. I have cc'd obrien@ who committed r190357. Yes, I see that there was r190361 which reverted part of the damage done by r190357 - it seems to have fixed sbin/fsck, but not sbin/fsck_ffs. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: fsck -C in stable/7 and 7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have committed a fix for that. Thanks for reporting! Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkn2BJYACgkQi+vbBBjt66Cy/gCgjiWNTp0D2O5+OFaMGUoJ/p2X tEYAn2mlzSZ73qQXbMt+0ZNhRDJjMhoK =DLKN -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bsnmpd problems during buildworld
On Mon, 27 Apr 2009 13:37:50 -0400 Steve Bertrand wrote:
SB Hi all,
SB I'm running into an issue during a buildworld. I noticed this problem
SB early last week, and also after another csup as of this morning.
SB I've rm'd everything in /usr/obj, but the problem persists. If anyone
SB could provide info on how I can avoid this, I'd appreciate it:
SB === usr.sbin/bsnmpd/modules/snmp_bridge (depend)
SB cat /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge/bridge_tree.def |
SB gensnmptree -e dot1dBridge newRoot topologyChange begemotBridgeNewRoot
SB begemotBridgeTopologyChange begemotBridgeBaseName bridge_oid.h
SB line 31: '(' expected at begin of node
SB context: TruthValue ENUM (
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd/modules.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin.
SB *** Error code 1
SB Stop in /usr/src.
SB *** Error code 1
SB Stop in /usr/src.
SB *** Error code 1
SB Stop in /usr/src.
What version of FreeBSD are you trying to build on what host version?
I see that gensnmptree from 6.2 has the problems with bridge_tree.def:
kopusha:/tmp% uname -a
FreeBSD kopusha.onet 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon Mar 31 23:57:19
EEST 2008 r...@kopusha.onet:/usr/obj/usr/src/sys/KOPUSHA i386
kopusha:/tmp% cat bridge_tree.def| gensnmptree -e dot1dBridge newRoot
topologyChange begemotBridgeNewRoot begemotBridgeTopologyChange
begemotBridgeBaseName
line 31: '(' expected at begin of node
context: TruthValue ENUM (
kopusha:/tmp% ident `which gensnmptree`
/usr/sbin/gensnmptree:
$FreeBSD: src/lib/csu/i386-elf/crti.S,v 1.7 2005/05/19 07:31:06 dfr Exp $
$FreeBSD: src/lib/csu/i386-elf/crtn.S,v 1.6 2005/05/19 07:31:06 dfr Exp $
$FreeBSD: src/lib/csu/common/crtbrand.c,v 1.4 2003/10/17 15:43:13 peter
Exp $
$FreeBSD: src/lib/csu/i386-elf/crt1.c,v 1.14 2005/05/19 07:36:07 dfr Exp $
According to man this version does not support ENUM type.
gensnmptree from 6.3 works ok.
--
Mikolaj Golub
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bsnmpd problems during buildworld
Mikolaj Golub wrote:
On Mon, 27 Apr 2009 13:37:50 -0400 Steve Bertrand wrote:
SB Hi all,
SB I'm running into an issue during a buildworld. I noticed this problem
SB early last week, and also after another csup as of this morning.
SB I've rm'd everything in /usr/obj, but the problem persists. If anyone
SB could provide info on how I can avoid this, I'd appreciate it:
SB === usr.sbin/bsnmpd/modules/snmp_bridge (depend)
SB cat /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge/bridge_tree.def |
SB gensnmptree -e dot1dBridge newRoot topologyChange begemotBridgeNewRoot
SB begemotBridgeTopologyChange begemotBridgeBaseName bridge_oid.h
SB line 31: '(' expected at begin of node
SB context: TruthValue ENUM (
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd/modules.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin.
SB *** Error code 1
SB Stop in /usr/src.
SB *** Error code 1
SB Stop in /usr/src.
SB *** Error code 1
SB Stop in /usr/src.
What version of FreeBSD are you trying to build on what host version?
*default tag=RELENG_7
*default host=cvsup.ca.FreeBSD.org
On:
dns5# uname -a
FreeBSD dns5.eagle.ca 7.1-STABLE FreeBSD 7.1-STABLE #1: Thu Mar 19
08:52:46 EDT 2009
Cheers,
Steve
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bsnmpd problems during buildworld
On Mon, 27 Apr 2009 15:30:44 -0400 Steve Bertrand wrote:
SB Mikolaj Golub wrote:
On Mon, 27 Apr 2009 13:37:50 -0400 Steve Bertrand wrote:
SB Hi all,
SB I'm running into an issue during a buildworld. I noticed this problem
SB early last week, and also after another csup as of this morning.
SB I've rm'd everything in /usr/obj, but the problem persists. If anyone
SB could provide info on how I can avoid this, I'd appreciate it:
SB === usr.sbin/bsnmpd/modules/snmp_bridge (depend)
SB cat /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge/bridge_tree.def |
SB gensnmptree -e dot1dBridge newRoot topologyChange begemotBridgeNewRoot
SB begemotBridgeTopologyChange begemotBridgeBaseName bridge_oid.h
SB line 31: '(' expected at begin of node
SB context: TruthValue ENUM (
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd/modules.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin/bsnmpd.
SB *** Error code 1
SB Stop in /usr/src/usr.sbin.
SB *** Error code 1
SB Stop in /usr/src.
SB *** Error code 1
SB Stop in /usr/src.
SB *** Error code 1
SB Stop in /usr/src.
What version of FreeBSD are you trying to build on what host version?
SB *default tag=RELENG_7
SB *default host=cvsup.ca.FreeBSD.org
SB On:
SB dns5# uname -a
SB FreeBSD dns5.eagle.ca 7.1-STABLE FreeBSD 7.1-STABLE #1: Thu Mar 19
SB 08:52:46 EDT 2009
Don't you have old net-mgmt/bsnmpd installed? What does `which gensnmptree`
return?
--
Mikolaj Golub
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
7.1/i386: restarts just after begin booting
Hello All, The 6.2 and 6.4 releases work well but I've got some problems when booting 7.1/i386 release on my server (Duron1200/ASUS A7N233-VM). When booting from installation CD the computer suddenly restarts after about 2sec so I even can't see any output (seems it's regs dump). MD5 hash of CD is OK, replacing CD-ROM drive didn't give any effect. However after a lot of experimentation I managed to install 7.1 via PXE. But on the first boot just installed 7.1 the same problem has appeared again. I think there is a bug in boot2 or in some code executes before the loader because it boots successfully via PXE (by pxeboot) and by loader at FreeBSD 6.4 installed on an other hard drive. P.S. BIOS was updated to latest stable version. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 7.2 RC2 Installation
Dear All , I have installed FreeBSD 7.2 RC2 for testing its installation on a PC with the following configuration : Main board : Asus P5VD2-VM Processor : Pentium 4 3.00 GHz RAM : 2 GB Hard Disk : Seagate ST3250410AS 3.AAC ( 238 475 MB ) SATA II PS/2 Mouse PS/2 Keyboard VGA : On board ( Chip model is not specified in manual , supports up to 2048 x 1536 at 75 Hz, up to 256 MB shared memory ) Dmesg recognized it as vga0 : Generic ISA VGA sc0 : VGA 16 virtual consoles , ... vgapci0 : VGA-compatible display Monitor : Philips 109B6 ( max resolution : 1920 x 1440 , advised resolution : 1600 x 1200 ) re0 : RealTek 8169/8110SC Giga-bit ... : Manual : RealTek RTL 8110SC DVD : TSSTcorp CDDVDW SH-S202J/SB02 from SysInstall main menu , first DHCP YES selected . Installation : Standard Partition : Existent OS has been deleted , and entire disk allocated to FreeBSD Boot : Standard Choose Distributions : ALL DHCP : Router Detected All of the packages installed with the following exceptions : Categories : accessibility , chinese , ipv6 , japanese , korean , palm , Packages from selected categories : ghostscript7-nox11-7.07_20 apache+mod_ssl-1.3.41+2.8.31 apache-1.3.41 sudo-1.6.9.20 links-2.2,1 lynx-2.8.6.5_5,1 rxvt-2.6,4_5 xorg-vfbserver-1.6.0,1 (1) During package installation the following errors occurred : add of package ,,, aborted , error code 1 : kdemultimedia-4.2.2 xscreensaver-gnome-hacks-5.08 gnome-screesaver-2.26.0 failed . emacs-22.3 (2) After installation , I have included into rc.conf gnome_enable=¨YES¨ After reboot , it gave error dbus_enabled=¨YES¨ is not specified in rc.conf I included this also in rc.conf , and rebooted . Gnome could not be started due to Xorg exited on signal 6 error . I tried xorgconfig -textmode but xorgconfig is not available in release 7.2 RC2 . I tried Xorg -configure and X -config /root/xorg.config.new it exited with signal 11 . startx : Not working . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.2 RC2 Installation
On Mon, Apr 27, 2009 at 9:30 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: Dear All , I have installed FreeBSD 7.2 RC2 for testing its installation on a PC with the following configuration : Main board : Asus P5VD2-VM Processor : Pentium 4 3.00 GHz RAM : 2 GB Hard Disk : Seagate ST3250410AS 3.AAC ( 238 475 MB ) SATA II PS/2 Mouse PS/2 Keyboard VGA : On board ( Chip model is not specified in manual , supports up to 2048 x 1536 at 75 Hz, up to 256 MB shared memory ) Dmesg recognized it as vga0 : Generic ISA VGA sc0 : VGA 16 virtual consoles , ... vgapci0 : VGA-compatible display Monitor : Philips 109B6 ( max resolution : 1920 x 1440 , advised resolution : 1600 x 1200 ) re0 : RealTek 8169/8110SC Giga-bit ... : Manual : RealTek RTL 8110SC DVD : TSSTcorp CDDVDW SH-S202J/SB02 from SysInstall main menu , first DHCP YES selected . Installation : Standard Partition : Existent OS has been deleted , and entire disk allocated to FreeBSD Boot : Standard Choose Distributions : ALL DHCP : Router Detected All of the packages installed with the following exceptions : Categories : accessibility , chinese , ipv6 , japanese , korean , palm , Packages from selected categories : ghostscript7-nox11-7.07_20 apache+mod_ssl-1.3.41+2.8.31 apache-1.3.41 sudo-1.6.9.20 links-2.2,1 lynx-2.8.6.5_5,1 rxvt-2.6,4_5 xorg-vfbserver-1.6.0,1 (1) During package installation the following errors occurred : add of package ,,, aborted , error code 1 : kdemultimedia-4.2.2 xscreensaver-gnome-hacks-5.08 gnome-screesaver-2.26.0 failed . emacs-22.3 (2) After installation , I have included into rc.conf gnome_enable=¨YES¨ After reboot , it gave error dbus_enabled=¨YES¨ is not specified in rc.conf I included this also in rc.conf , and rebooted . Gnome could not be started due to Xorg exited on signal 6 error . I tried xorgconfig -textmode but xorgconfig is not available in release 7.2 RC2 . I tried Xorg -configure and X -config /root/xorg.config.new it exited with signal 11 . startx : Not working . The FreeBSD 7.2 amd64 RC2 has been installed . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
