From owner-freebsd-stable Tue Oct 10 15:58:32 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA08396 for stable-outgoing; Tue, 10 Oct 1995 15:58:32 -0700 Received: from bigdipper.iagi.net (bigdipper.iagi.net [204.157.123.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA08391 ; Tue, 10 Oct 1995 15:58:30 -0700 Received: (from adhir@localhost) by bigdipper.iagi.net (8.6.12/8.6.9) id TAA05736; Tue, 10 Oct 1995 19:01:49 -0400 Date: Tue, 10 Oct 1995 19:01:49 -0400 (EDT) From: "Alok K. Dhir" To: questions@freebsd.org cc: stable@freebsd.org Subject: Boot off of sd0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk Hey all - we recently suffered the death of a 2 gig Quantum Empire due to over heating (the server room AC vent was off and poof went the disk). In any case, I've reinstalled and restored most of our data off of backups and fortunately we're back to where we were without too much loss. The problem I'm having is that I can't get the system (running 951005-snap of 2.1-stable) to boot off of sd0. I think I may have screwed something up during the disklabel portion of the custom install. If I boot without a floppy in the drive, I get a "Missing Operating System" message from the BIOS (I assume its from the BIOS, anyway). If I boot off of a boot floppy and enter "sd(0,a)/kernel" at the boot prompt, everything comes up beautifully. I have used "fdisk -a" to set the first partition (0) active (the entire disk, a Seagate 4 gig Hawk, is dedicated to FreeBSD) and have run "disklabel -B sd0". The server's up and running (production) as we speak, so I can't test to see if what I did worked without interrupting my users. I just want to make sure that what I did is correct before I reboot the system tonight around 2am (I won't be near the machine when I boot it so if what I did is NOT correct, I'll have to drive to the office in my jammies to boot it). Is there anything else I need to do to get the system to boot off of sd(0,a)/kernel other than setting the active partition to 0 and "disklabel -B"? Here's the output from fdisk: ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=9595 heads=19 sectors/track=46 (874 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=9595 heads=19 sectors/track=46 (874 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 46, size 8385984 (4094 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 1023/ sector 46/ head 18 The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: And here's the output from "disklabel sd0": # /dev/rsd0c: type: SCSI disk: sd0s1 label: flags: bytes/sector: 512 sectors/track: 46 tracks/cylinder: 19 sectors/cylinder: 874 cylinders: 9594 sectors/unit: 8385984 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 204800 0 4.2BSD 0 0 0 # (Cyl. 0 - 234*) b: 262144 204800 swap # (Cyl. 234*- 534*) c: 8385984 0 unused 0 0 # (Cyl. 0 - 9594*) e: 4096000 466944 4.2BSD 0 0 0 # (Cyl. 534*- 5220*) f: 3823040 4562944 4.2BSD 0 0 0 # (Cyl. 5220*- 9594*) Please advise... Thanks! Alok K. Dhir Internet Access Group, Inc. adhir@iagi.net (301) 652-0484 Fax: (301) 652-0649 http://www.iagi.net From owner-freebsd-stable Wed Oct 11 08:35:06 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA10930 for stable-outgoing; Wed, 11 Oct 1995 08:35:06 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA10924 for ; Wed, 11 Oct 1995 08:35:03 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id LAA09946 for stable@freebsd.org; Wed, 11 Oct 1995 11:40:17 -0400 From: Mark Hittinger Message-Id: <199510111540.LAA09946@ns1.win.net> Subject: kill the messenger To: stable@freebsd.org Date: Wed, 11 Oct 1995 11:40:16 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 801 Sender: owner-stable@freebsd.org Precedence: bulk Hey guys - some of 2.2's badness is bouncing down into 2.1 city. After I supped/built/rebooted on Oct 10 the following familiar problems have surfaced on 2.1. 1. Pci probe boot hangs on old EISA motherboards (printf's fix it) 2. Unusual file system corruption after a system hang 3. Unusual file system corruption after a panic induced by XFree312 4. System hang with disk drive light on 100% 5. System hangs very often - within minutes after rebooting. All of these problems were noted on 2.2 early last month. 2.1 Kernels before Oct10 did not exhibit these problems. I keep very up-to-date sup trees so these are very recent commits. 2.1 must not be allowed to go gold with these recent commits intact. Regards, Mark Hittinger Internet Manager WinNET Communications, Inc. bugs@win.net From owner-freebsd-stable Wed Oct 11 13:43:05 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA17208 for stable-outgoing; Wed, 11 Oct 1995 13:43:05 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA17203 ; Wed, 11 Oct 1995 13:43:00 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id NAA03105; Wed, 11 Oct 1995 13:42:43 -0700 From: Julian Elischer Message-Id: <199510112042.NAA03105@ref.tfs.com> Subject: Re: Boot off of sd0 To: adhir@iagi.net (Alok K. Dhir) Date: Wed, 11 Oct 1995 13:42:43 -0700 (PDT) Cc: questions@freebsd.org, stable@freebsd.org In-Reply-To: from "Alok K. Dhir" at Oct 10, 95 07:01:49 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3994 Sender: owner-stable@freebsd.org Precedence: bulk > > > Hey all - we recently suffered the death of a 2 gig Quantum Empire due to > over heating (the server room AC vent was off and poof went the disk). > In any case, I've reinstalled and restored most of our data off of > backups and fortunately we're back to where we were without too much > loss. > > The problem I'm having is that I can't get the system (running > 951005-snap of 2.1-stable) to boot off of sd0. I think I may have > screwed something up during the disklabel portion of the custom install. > If I boot without a floppy in the drive, I get a > "Missing Operating System" message from the BIOS (I assume its from the > BIOS, anyway). If I boot off of a boot floppy and enter "sd(0,a)/kernel" > at the boot prompt, everything comes up beautifully. > > I have used "fdisk -a" to set the first partition (0) active (the entire > disk, a Seagate 4 gig Hawk, is dedicated to FreeBSD) and have run > "disklabel -B sd0". The server's up and running (production) as we > speak, so I can't test to see if what I did worked without interrupting > my users. I just want to make sure that what I did is correct before I > reboot the system tonight around 2am (I won't be near the machine when I > boot it so if what I did is NOT correct, I'll have to drive to the office > in my jammies to boot it). > > Is there anything else I need to do to get the system to boot off of > sd(0,a)/kernel other than setting the active partition to 0 and "disklabel > -B"? > > Here's the output from fdisk: > > ******* Working on device /dev/rsd0 ******* > parameters extracted from in-core disklabel are: > cylinders=9595 heads=19 sectors/track=46 (874 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=9595 heads=19 sectors/track=46 (874 blks/cyl) > > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 0 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 46, size 8385984 (4094 Meg), flag 80 > beg: cyl 0/ sector 1/ head 1; > end: cyl 1023/ sector 46/ head 18 If you want to make this work, then change (by hand) the beg: figures to: cyl 0: sector 47: head 0: use fdisk -u sd0 for this and change NO OTHER fields.. (use the defaults given as long as they) agree with what you gave here.. ALTERNATIVELY: set the BIOS parameters used in fdisk to be 64 heads, 32 sectors 4000 tracks and allow it to recalculate the beg/end figures automatically MAKE SURE YOU USE THE SAME start 46, size 8385984 (4094 Meg), flag 80 figures you used before.. (or you'll have to re-install the data..) it probably would have been a better thing to start at 64 and set the figures to match the BIOS but you'll be ok with these.. > The data for partition 1 is: > > The data for partition 2 is: > > The data for partition 3 is: > > > And here's the output from "disklabel sd0": > > # /dev/rsd0c: > type: SCSI > disk: sd0s1 > label: > flags: > bytes/sector: 512 > sectors/track: 46 > tracks/cylinder: 19 > sectors/cylinder: 874 > cylinders: 9594 > sectors/unit: 8385984 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 204800 0 4.2BSD 0 0 0 # (Cyl. 0 - 234*) > b: 262144 204800 swap # (Cyl. 234*- 534*) > c: 8385984 0 unused 0 0 # (Cyl. 0 - 9594*) > e: 4096000 466944 4.2BSD 0 0 0 # (Cyl. 534*- 5220*) > f: 3823040 4562944 4.2BSD 0 0 0 # (Cyl. 5220*- 9594*) > > Please advise... > > Thanks! > > Alok K. Dhir > Internet Access Group, Inc. > adhir@iagi.net > (301) 652-0484 Fax: (301) 652-0649 > http://www.iagi.net > > From owner-freebsd-stable Wed Oct 11 16:31:46 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA23370 for stable-outgoing; Wed, 11 Oct 1995 16:31:46 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA23365 for ; Wed, 11 Oct 1995 16:31:43 -0700 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id QAA13142; Wed, 11 Oct 1995 16:31:42 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id QAA00927; Wed, 11 Oct 1995 16:31:36 -0700 Message-Id: <199510112331.QAA00927@corbin.Root.COM> To: Mark Hittinger cc: stable@freebsd.org Subject: Re: kill the messenger In-reply-to: Your message of "Wed, 11 Oct 95 11:40:16 EDT." <199510111540.LAA09946@ns1.win.net> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 11 Oct 1995 16:31:36 -0700 Sender: owner-stable@freebsd.org Precedence: bulk >Hey guys - some of 2.2's badness is bouncing down into 2.1 city. > >After I supped/built/rebooted on Oct 10 the following familiar problems >have surfaced on 2.1. > >1. Pci probe boot hangs on old EISA motherboards (printf's fix it) >2. Unusual file system corruption after a system hang >3. Unusual file system corruption after a panic induced by XFree312 >4. System hang with disk drive light on 100% >5. System hangs very often - within minutes after rebooting. > >All of these problems were noted on 2.2 early last month. 2.1 Kernels >before Oct10 did not exhibit these problems. > >I keep very up-to-date sup trees so these are very recent commits. > >2.1 must not be allowed to go gold with these recent commits intact. I appreciate the feedback, but I'm going to need a lot more information before I'll have any chance of narrowing down the problem. 1) What disk controller are you using? 2) What is the last SUP of -stable that worked without any trouble? 3) Are the problems all happening on the same (old EISA) machine, or are different problems happening on different machines? If the later, please associate the problems with the hardware configurations involved. The only significant things I've changed recently in -stable are pcibus.c and ncr.c. All other significant changes in the kernel were made last week. I'm using the NCR controller in two PCI machines here and have not seen any problems during my regression testing. Hmmm. The weird thing is that there have been relatively few changes to the kernel during the past few weeks - most of them were to recently added device drivers, and the rest were well-controlled bugfixes. I'll send you an older rev of sys/i386/isa/pcibus.c - it's the only thing I can think of that might cause the above problems. -DG From owner-freebsd-stable Thu Oct 12 07:42:04 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA18077 for stable-outgoing; Thu, 12 Oct 1995 07:42:04 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA18072 for ; Thu, 12 Oct 1995 07:42:01 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id KAA23854 for stable@freebsd.org; Thu, 12 Oct 1995 10:47:43 -0400 From: Mark Hittinger Message-Id: <199510121447.KAA23854@ns1.win.net> Subject: crypt.sgml missing? To: stable@freebsd.org Date: Thu, 12 Oct 1995 10:47:43 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 247 Sender: owner-stable@freebsd.org Precedence: bulk Handbook make fails with can't find 'crypt.sgml'. I realize this is probably one of those "special" modules that might need to be in the 'secure' distribution. Regards, Mark Hittinger Internet Manager WinNET Communications, Inc. bugs@win.net From owner-freebsd-stable Sat Oct 14 16:50:58 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA23029 for stable-outgoing; Sat, 14 Oct 1995 16:50:58 -0700 Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA23024 for ; Sat, 14 Oct 1995 16:50:56 -0700 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.12/8.6.12) with UUCP id QAA12544 for freebsd-stable@freebsd.org; Sat, 14 Oct 1995 16:50:50 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.12/8.6.12) id QAA10145 for freebsd-stable@freebsd.org; Sat, 14 Oct 1995 16:48:24 -0700 From: Frank Mayhar Message-Id: <199510142348.QAA10145@exit.com> Subject: Breakage in -STABLE? To: freebsd-stable@freebsd.org Date: Sat, 14 Oct 1995 16:48:24 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24 ME5a] Content-Type: text Content-Length: 2347 Sender: owner-stable@freebsd.org Precedence: bulk Latest sup (as of this afternoon) of 2.1-stable, fails with the following error when making the kernel: loading kernel scsi_base.o: Undefined symbol `_memcmp' referenced from text segment *** Error code 1 Stop. Here's the config file: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.46 1995/06/11 19:31:11 rgrimes Exp $ # machine "i386" cpu "I586_CPU" ident TINKER maxusers 64 options ALLOW_CONFLICT_IOADDR #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MFS #Memory File System options MSDOSFS #MSDOS Filesystem #options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options "NSWAPDEV=4" options COMPAT_LINUX options SYSVSHM options SYSVSEM options SYSVMSG options KTRACE #kernel tracing #options DDB #kernel debugger config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 controller ahc0 at pci? bio irq ? vector ahcintr controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options XSERVER # include code for XFree86 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port 0x338 tty irq 12 vector siointr device lpt0 at isa? port? tty controller snd0 device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr device pas0 at isa? port 0x388 irq 5 drq 3 vector pasintr device opl0 at isa? port 0x388 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device tun 2 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device vn 1 #Vnode driver -- Frank Mayhar frank@exit.com From owner-freebsd-stable Sat Oct 14 18:40:18 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA25263 for stable-outgoing; Sat, 14 Oct 1995 18:40:18 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA25258 for ; Sat, 14 Oct 1995 18:40:15 -0700 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id SAA18575; Sat, 14 Oct 1995 18:40:09 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id SAA04518; Sat, 14 Oct 1995 18:39:36 -0700 Message-Id: <199510150139.SAA04518@corbin.Root.COM> To: Frank Mayhar cc: freebsd-stable@freebsd.org Subject: Re: Breakage in -STABLE? In-reply-to: Your message of "Sat, 14 Oct 95 16:48:24 PDT." <199510142348.QAA10145@exit.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 14 Oct 1995 18:39:35 -0700 Sender: owner-stable@freebsd.org Precedence: bulk >Latest sup (as of this afternoon) of 2.1-stable, fails with the following >error when making the kernel: > >loading kernel >scsi_base.o: Undefined symbol `_memcmp' referenced from text segment >*** Error code 1 It appears that you are building the kernel without the -O cc flag. -O is required because we are (bogusly) relying on gcc to provide the inline version of memcmp. This was fixed recently in -current, but I chose not to bring those changes to -stable. -DG