RE: Laptop boot problem in current with GENERIC GENERIC.hints
On 27-Jun-00 John Baldwin wrote: On 27-Jun-00 Edwin Culp wrote: I have 5 machines running current. All are booting fine with the changes made on June 12, with the exception of a k-6 laptop. I have been booting the kernel.works since the changes and can't seem to get something right. I have tried with my original kernel configuration and now have been trying with the GENERIC configuration and GENERIC.hints. When I try to boot with my new kernel I get: BTX loader 1.0 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive B: is disk1 BIOS 639kB/97280kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 [EMAIL PROTECTED] Mon June 26 12:37:44 PDT 2000 int=000d err= eft=00010046 eip=92eb eax=00fb ebx= ecx=0152 edx=03f6 esi=000fbc92 edi=000f ebp=17b4 esp=17b4 cs:eip=0f 32 89 45 1c 89 55 14-46 eb cf 80 65 31 fd eb RDMSR instruction. It's trying to read an MSR (Model Specific Register) from the CPU. In this case, one that is not documented in Intel's manuals. Thus, it is either an undocmented MSR or a K6-only MSR. ss:esp=08 00 00 00 1c 9c 00 00-fe 0e 00 00 d4 17 00 00 System halted I copied this manually since I don't have a console on the laptop. Any suggestions will be appreciated. Rev 1.18 of sys/boot/i386/btx/btx/btx.s should fix this. Try doing an ftp install of a really recent snap from current.FreeBSD.org. Augh! I found out that actually rev 1.18 contained a bug causing this problem. Rev 1.19 of btx.s should actually fix this. Sorry. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
bug: kernel hangs at boot
Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in boot (no diagnostics even printed, just silent hang with "/" on the screen). Kernel from Jun14 with fresh -current bootblocks (i.e. the same bootblocks) booted Ok. -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RSA support..
I have been trying to get ssh working in current, but with no luck. Since I updated recently, all I get is: ssh: no RSA support in libssl and libcrypto. See ssl(8). I have been off the lists for a bit, so I apologize if I missed something, but this has always been confusing. It used to just work. Now that i doesn't though, I have no clue where to start looking. There appears to be no ssl(8) manpage, or anything in the list archives about this. Thanks, Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current from yesterday ; annoying messages..
Hi, can pleasee anyone explain what this means and how I can get rid of this ? fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 fd1: 1200-KB 5.25" drive on fdc0 drive 1 WARNING: "fd" is usurping "fd"'s cdevsw[] WARNING: "fd" is usurping "fd"'s bmaj ^^ and ist this normal ? sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 isa0: @@@ found ^ unknown: PNP0303 can't assign resources TIA Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13http://www.freibergnet.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA support..
On Thu, 29 Jun 2000 02:25:50 CDT, Chris Csanady wrote: I have been trying to get ssh working in current, but with no luck. Since I updated recently, all I get is: ssh: no RSA support in libssl and libcrypto. See ssl(8). This is the system's way of punishing you for neglecting your cvs-all mail, your freebsd-current mail and your src/UPDATING file. Hmm, I read through UPDATING, but didn't find much about this.. Your kernel is lacking support for the random device. Do your reading and smile. :-) I have been off the lists for a while, yes. :) Thanks very much for this tidbit.. Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA support..
On Thu, 29 Jun 2000 05:37:35 CDT, Chris Csanady wrote: Hmm, I read through UPDATING, but didn't find much about this.. Hmm, you're right; it doesn't explicitly say you need option RANDOMDEV in your kernel config. It just warns you about the state of the entropy harvesting. The exact "HowTo Enable" stuff was covered in a HEADS UP message, but as you said, you've been off the lists. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange make buildworld problem...
On Wed, 28 Jun 2000 19:54:17 -0400, Donn Miller wrote: Again, this is after re-making buildworld with -DNOCLEAN after a successful first make buildworld. Any chance the sources changed between buildworlds? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current from yesterday ; annoying messages..
Hello,
From: Holm Tiffe [EMAIL PROTECTED]
Date: Thu, 29 Jun 2000 09:32:31 +0200
::Hi,
::can pleasee anyone explain what this means and how I can get rid of this ?
::
::fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
::fdc0: FIFO enabled, 8 bytes threshold
::fd0: 1440-KB 3.5" drive on fdc0 drive 0
::fd1: 1200-KB 5.25" drive on fdc0 drive 1
::WARNING: "fd" is usurping "fd"'s cdevsw[]
::WARNING: "fd" is usurping "fd"'s bmaj
::^^
::
::and ist this normal ?
Because you have two floppy drives, and cdevsw_add() is being called twice.
The following patch should fix it. This patch was originaly created by
Kuwamura-san for PC98 fd driver. It's been working for me, for few month.
---8--8--8--8--- Cut Here ---8--8--8--8---
--- sys/isa/fd.c.orig Fri May 26 12:20:36 2000
+++ sys/isa/fd.cThu Jun 29 20:14:11 2000
@@ -1099,10 +1099,14 @@
int typemynor;
int typesize;
#endif
+ static int32_t fd_cdev_done = 0;
fd = device_get_softc(dev);
- cdevsw_add(fd_cdevsw); /* XXX */
+ if (!fd_cdev_done) {
+ cdevsw_add(fd_cdevsw); /* XXX */
+ fd_cdev_done++;
+ }
make_dev(fd_cdevsw, (fd-fdu 6),
UID_ROOT, GID_OPERATOR, 0640, "rfd%d", fd-fdu);
---8--8--8--8--- Cut Here ---8--8--8--8---
::sio1 at port 0x2f8-0x2ff irq 3 on isa0
::sio1: type 16550A
::vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
::isa0: @@@ found
::^
::unknown: PNP0303 can't assign resources
Same here.
I also would like to know about it.
Hope this helps,
Haro
=--
_ _Munehiro (haro) Matsuda
-|- /_\ |_|_| Business Incubation Dept., Kubota Corp.
/|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome
Chuo-ku Tokyo 103-8310, Japan
Tel: +81-3-3245-3318 Fax: +81-3-3245-3315
Email: [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic in sbdrop on SMP, kernel approx 9 days old
This morning my cable modem went out and it returned to service while I
was out of the room. When I returned I was greeted by fsck; I'm not sure
if this is related to networking somehow but I figured I'd report it
anyway. This computer has 3 nics, does bridging across two, and provides
nat to the third. Kernel is about as old as the uptime was. As usual,
any more info wanted, just ask.
gdb -k /sys/compile/SAPPHIRE-SMP3/kernel.debug vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-unknown-freebsd"...
SMP 2 cpus
IdlePTD 3375104
initial pcb at 2b83c0
panicstr: sbdrop
panic messages:
---
panic: sbdrop
mp_lock = 0101; cpuid = 1; lapic.id = 0100
boot() called on cpu#1
syncing disks... 1
done
Uptime: 8d18h3m30s
dumping to dev #ad/0x20001, offset 8192
dump ata0: resetting devices .. done
128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111
110 109 108 107 106 1
05 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83
82 81 80 79 78 77 7
6 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52
51 50 49 48 47 46 4
5 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21
20 19 18 17 16 15 1
4 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
#1 0xc015a62d in panic (fmt=0xc0257d06 "sbdrop") at
../../kern/kern_shutdown.c:553
#2 0xc017b500 in sbdrop (sb=0xc8572074, len=65392) at
../../kern/uipc_socket2.c:927
#3 0xc017b390 in sbflush (sb=0xc8572074) at ../../kern/uipc_socket2.c:906
#4 0xc017ae55 in sbrelease (sb=0xc8572074, so=0xc8572000) at
../../kern/uipc_socket2.c:589
#5 0xc01783cb in sofree (so=0xc8572000) at ../../kern/uipc_socket.c:250
#6 0xc0178502 in soclose (so=0xc8572000) at ../../kern/uipc_socket.c:316
#7 0xc016de8a in soo_close (fp=0xc1016a80, p=0xc954c2a0) at
../../kern/sys_socket.c:183
#8 0xc014e3ad in fdrop (fp=0xc1016a80, p=0xc954c2a0) at
../../sys/file.h:212
#9 0xc014e2f3 in closef (fp=0xc1016a80, p=0xc954c2a0) at
../../kern/kern_descrip.c:1079
#10 0xc014e044 in fdfree (p=0xc954c2a0) at ../../kern/kern_descrip.c:945
#11 0xc0150779 in exit1 (p=0xc954c2a0, rv=256) at
../../kern/kern_exit.c:186
#12 0xc01505e0 in exit1 (p=0xc954c2a0, rv=0) at ../../kern/kern_exit.c:103
#13 0xc02407e9 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 672387072,
tf_esi = 13118054, tf_ebp = -1077941132, tf_isp = -917430316, tf_ebx
= 672371384,
tf_edx = 0, tf_ecx = -1077941184, tf_eax = 1, tf_trapno = 12, tf_err
= 2,
tf_eip = 672019908, tf_cs = 31, tf_eflags = 663, tf_esp =
-1077941160, tf_ss = 47})
at ../../i386/i386/trap.c:1126
#14 0xc022e9fb in Xint0x80_syscall ()
cannot read proc at 0
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: What's going on with crypto all of a sudden ?
Hrmm, I think I just read somewhere (/usr/src/UPDATING?) that crypto is required to get a make world to work, and I guess certain other things won't work as well until you rebuild (?) :-) (:-P) if you're using -CURRENT, it's because you havn't followed the advice about the new randomdev. This doesn't explain why it suggests that the user reads a non-existent man page (ssl(8)) :-P = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Wed, 28 Jun 2000, Pascal Hofstee wrote: Just now after a new buildworld/installworld i am suddenly getting errors like the following when trying to use OpenSSH's version 1 protocoll: ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 Protocol major versions differ: 2 vs. 1 man 8 sslresults into the following: No entry for ssl in section 8 of the manual This has been working just fine for months before. I get the idea it has something to do with the /dev/(random|zero) update. Anyone care to explain this ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's going on with crypto all of a sudden ?
On Thu, 29 Jun 2000 10:25:05 -0400, Kenneth Wayne Culver wrote: Hrmm, I think I just read somewhere (/usr/src/UPDATING?) that crypto is required to get a make world to work, and I guess certain other things won't work as well until you rebuild (?) :-) (:-P) You're grasping at straws, since the ssl(8) manual page isn't installed. The base system's openssl maintainer still isn't sure what to do about the docs. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's going on with crypto all of a sudden ?
:-) Well, I didn't know that... That could explain it. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Thu, 29 Jun 2000, Sheldon Hearn wrote: On Thu, 29 Jun 2000 10:25:05 -0400, Kenneth Wayne Culver wrote: Hrmm, I think I just read somewhere (/usr/src/UPDATING?) that crypto is required to get a make world to work, and I guess certain other things won't work as well until you rebuild (?) :-) (:-P) You're grasping at straws, since the ssl(8) manual page isn't installed. The base system's openssl maintainer still isn't sure what to do about the docs. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
On Wed, Jun 28, 2000 at 06:24:01PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Nik Clayton writes: : On Wed, Jun 28, 2000 at 11:27:12AM -0400, Thomas M. Sommers wrote: : Warner Losh wrote: : : Any reason that the .c/.h files of the drivers couldn't be used to : generate this information? : : Or perhaps the other way around. : : That's what I'd prefer. Any solution that relys on trying to parse : "structured comments" like that is a kludge at best. I'd rather get : all this information in to a usefully structured form now, and then : process it to produce the various output formats we need. I think that this will doom the information to always being obsolete. If the information is in the .h or .c files, then it will be looked at (and corrected) all the time by the programmers. If not, then it will rot as badly as LINT has been rotting. It has taken much effort to keep LINT as non-rotten as it has been kept. The .h file(s) should be generated from this XML config file, or some other mechanism needs to be put in place to prevent a (hardware) module from working if there isn't a functional entry for it in this XML config file. We've successfully demonstrated that hardware authors don't keep things like LINT up to date. We've also successfully demonstrated that getting volunteers to scan the mailing lists and keep HARDWARE.TXT and similar up to date is equally futile. It's time to turn the tables. I don't know enough about the -current build environment to say precisely how this could be done (yet). But God help you all if I scrape together sufficient resources to put together a box for -current. In the meantime, I'd appreciate suggestions as to how you (or anyone else) would go about abstracting some of the core information that a driver needs out of a source file. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
In message [EMAIL PROTECTED] Nik Clayton writes: : The .h file(s) should be generated from this XML config file, or some other : mechanism needs to be put in place to prevent a (hardware) module from : working if there isn't a functional entry for it in this XML config file. : : We've successfully demonstrated that hardware authors don't keep things : like LINT up to date. We've also successfully demonstrated that getting : volunteers to scan the mailing lists and keep HARDWARE.TXT and similar : up to date is equally futile. : : It's time to turn the tables. I'd violently oppose this. I'd rather see the XML file generated from the .h files that we already use to build the system with. You would be making it just as hard to keep things up to date with little gain from the programmer's point of view. You need to make it easier for the programmer to keep things up to date rather than harder. : I don't know enough about the -current build environment to say precisely : how this could be done (yet). But God help you all if I scrape together : sufficient resources to put together a box for -current. : : In the meantime, I'd appreciate suggestions as to how you (or anyone else) : would go about abstracting some of the core information that a driver needs : out of a source file. While I hate the idea, I'd love to see what you'd come up with. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What's going on with crypto all of a sudden ?
if you're using -CURRENT, it's because you havn't followed the advice about the new randomdev. This doesn't explain why it suggests that the user reads a non-existent man page (ssl(8)) :-P = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Wed, 28 Jun 2000, Pascal Hofstee wrote: Just now after a new buildworld/installworld i am suddenly getting errors like the following when trying to use OpenSSH's version 1 protocoll: ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 Protocol major versions differ: 2 vs. 1 man 8 sslresults into the following: No entry for ssl in section 8 of the manual This has been working just fine for months before. I get the idea it has something to do with the /dev/(random|zero) update. Anyone care to explain this ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/contrib/isc-dhcp - Imported sources
On Thu, 29 Jun 2000 10:01:25 -0700, "David O'Brien" [EMAIL PROTECTED] said: 1. Everyone uses /bin/csh (show me a box that has never had root login at least once. I can show you several boxes where first thing root did after logging in was to configure itself for a Real Shell(tm). I personally would be much happier if root's default shell were /bin/sh (as it is on all of the new non-FreeBSD boxes we have around here). -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
roots shell == /bin/sh please
Hi. My vote is for root's shell to be /bin/sh if anyone's counting. Is the /bin/sh in freebsd more buggy than, say, the solaris /bin/sh? If so, thats's probably why it's currently /bin/csh. I could also live with /bin/bash as root's shell. Not sure why bash is not part of freebsd "core" anyways. ../Steven To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: roots shell == /bin/sh please
gnu not unix wrote: I could also live with /bin/bash as root's shell. Not sure why bash is not part of freebsd "core" anyways. GPL. Bloat. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
The choice to use crosstools is easier, since it by default installs the tool into the "strict path", but Mark used build-tools and a path to miniperl to do it instead, presumably since it is restricted to a very minor bit of the tree. Also because miniperl and libperl want libm, and that breaks at build time because it cannot be found. :-( M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl ...
I am not sure who is supposed to manage the fact that
/usr/ports/Mk/bsd.ports.mk doesn't yet know about perl-5.006. One
appears to need to set PERL_VER and PERL_VERSION. I just added an ."if
{OSVERSION} = 56" , but this clearly isn't enough for people who
have yet to upgrade to the newest "current'. Does this mean that the
OSVERSION needs to be incremented to indicate the perl upgrade?
I need to get this past Satoshi.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
Adding something to bootstrap-tools implies that we can't use the installed miniperl (backward compatibility problem) or the host doesn't have miniperl. The bootstrap-tools built miniperl would then be used throughout the build and install stages. I think that's what we have in this case. We need the newer version of miniperl to build perl, correct? Yes, and it is doing that now. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
On Wed, 28 Jun 2000, Mark Murray wrote: Adding something to bootstrap-tools implies that we can't use the installed miniperl (backward compatibility problem) or the host doesn't have miniperl. The bootstrap-tools built miniperl would then be used throughout the build and install stages. I think that's what we have in this case. We need the newer version of miniperl to build perl, correct? Yes, and it is doing that now. Except on alpha. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange make buildworld problem...
On Wed, Jun 28, 2000 at 07:54:17PM -0400, Donn Miller wrote: make: don't know how to make /usr/obj/usr/src/i386/usr/include/sys/types.h. Stop *** Error code 2 This is what I got when I tried to ``make -DNOCLEAN buildworld'' after the Perl 5.006 upgrade. Perl is being built at the wrong time, or a dependacy is missing. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in sbdrop on SMP, kernel approx 9 days old
What is the hardware in this box? Do you have an NCR scsi controller
using the ncr driver?
paul
Adam ([EMAIL PROTECTED]) wrote:
This morning my cable modem went out and it returned to service while I
was out of the room. When I returned I was greeted by fsck; I'm not sure
if this is related to networking somehow but I figured I'd report it
anyway. This computer has 3 nics, does bridging across two, and provides
nat to the third. Kernel is about as old as the uptime was. As usual,
any more info wanted, just ask.
gdb -k /sys/compile/SAPPHIRE-SMP3/kernel.debug vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-unknown-freebsd"...
SMP 2 cpus
IdlePTD 3375104
initial pcb at 2b83c0
panicstr: sbdrop
panic messages:
---
panic: sbdrop
mp_lock = 0101; cpuid = 1; lapic.id = 0100
boot() called on cpu#1
syncing disks... 1
done
Uptime: 8d18h3m30s
dumping to dev #ad/0x20001, offset 8192
dump ata0: resetting devices .. done
128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111
110 109 108 107 106 1
05 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83
82 81 80 79 78 77 7
6 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52
51 50 49 48 47 46 4
5 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21
20 19 18 17 16 15 1
4 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
#1 0xc015a62d in panic (fmt=0xc0257d06 "sbdrop") at
../../kern/kern_shutdown.c:553
#2 0xc017b500 in sbdrop (sb=0xc8572074, len=65392) at
../../kern/uipc_socket2.c:927
#3 0xc017b390 in sbflush (sb=0xc8572074) at ../../kern/uipc_socket2.c:906
#4 0xc017ae55 in sbrelease (sb=0xc8572074, so=0xc8572000) at
../../kern/uipc_socket2.c:589
#5 0xc01783cb in sofree (so=0xc8572000) at ../../kern/uipc_socket.c:250
#6 0xc0178502 in soclose (so=0xc8572000) at ../../kern/uipc_socket.c:316
#7 0xc016de8a in soo_close (fp=0xc1016a80, p=0xc954c2a0) at
../../kern/sys_socket.c:183
#8 0xc014e3ad in fdrop (fp=0xc1016a80, p=0xc954c2a0) at
../../sys/file.h:212
#9 0xc014e2f3 in closef (fp=0xc1016a80, p=0xc954c2a0) at
../../kern/kern_descrip.c:1079
#10 0xc014e044 in fdfree (p=0xc954c2a0) at ../../kern/kern_descrip.c:945
#11 0xc0150779 in exit1 (p=0xc954c2a0, rv=256) at
../../kern/kern_exit.c:186
#12 0xc01505e0 in exit1 (p=0xc954c2a0, rv=0) at ../../kern/kern_exit.c:103
#13 0xc02407e9 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 672387072,
tf_esi = 13118054, tf_ebp = -1077941132, tf_isp = -917430316, tf_ebx
= 672371384,
tf_edx = 0, tf_ecx = -1077941184, tf_eax = 1, tf_trapno = 12, tf_err
= 2,
tf_eip = 672019908, tf_cs = 31, tf_eflags = 663, tf_esp =
-1077941160, tf_ss = 47})
at ../../i386/i386/trap.c:1126
#14 0xc022e9fb in Xint0x80_syscall ()
cannot read proc at 0
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Paul Saab
Technical Yahoo
[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
Do You .. uhh .. Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Strange make buildworld problem...
On Wed, Jun 28, 2000 at 07:54:17PM -0400, Donn Miller wrote: make: don't know how to make /usr/obj/usr/src/i386/usr/include/sys/types.h. Stop *** Error code 2 This is what I got when I tried to ``make -DNOCLEAN buildworld'' after the Perl 5.006 upgrade. Perl is being built at the wrong time, or a dependacy is missing. This is now fixed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange make buildworld problem...
Hi I just committed a fix for this. M Recently, the make world problems with perl have been fixed, and I can do a make world all the way through, provided I do a make world the first time only. However, I did a cvsup to update my source tree again after the first make world. I did a make -DNOCLEAN buildworld with /usr/obj untouched. I get this: stage 2: build tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/us r/s rc/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 build-tools cd /usr/src/bin/sh; make build-tools cd /usr/src/games/adventure; make build-tools cd /usr/src/games/hack; make build-tools cd /usr/src/games/phantasia; make build-tools cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools cd /usr/src/gnu/usr.bin/cc/f771; make build-tools cd /usr/src/lib/libncurses; make build-tools cd /usr/src/share/syscons/scrnmaps; make build-tools cd /usr/src/gnu/usr.bin/perl; make build-tools cd /usr/src/gnu/usr.bin/perl/libperl make build-tools make: don't know how to make /usr/obj/usr/src/i386/usr/include/sys/types.h. Stop *** Error code 2 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src. *** Error code 1 Again, this is after re-making buildworld with -DNOCLEAN after a successful first make buildworld. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA support..
Hi Please check /usr/src/UPDATING M I have been trying to get ssh working in current, but with no luck. Since I updated recently, all I get is: ssh: no RSA support in libssl and libcrypto. See ssl(8). I have been off the lists for a bit, so I apologize if I missed something, but this has always been confusing. It used to just work. Now that i doesn't though, I have no clue where to start looking. There appears to be no ssl(8) manpage, or anything in the list archives about this. Thanks, Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bug: device ether no longer optional
Andrey A. Chernov writes: Without "device ether" in config file kernel fails to compile and complains on undefined function ether_ifdetach() in if.c:if_detach() Please fix. I'm working on it. Of course, in order to check in the fix, I first need to build a new kernel and test it. But once running the new kernel, I can't check in the fix thanks to the broken ssh. So now I'm now building another kernel with RANDOMDEV, even though that this is the solution was not at all obvious from reading UPDATING. Luckily I happened to have seen -current in the past couple of days. Trying to search -current on the web site for the appropriate keywords yeilded only articles from the years 1997 through 1999, nothing in 2000, and there is no way to sort by date anyway. I'm not trying to emit blame or anything, just pointing out that anything that makes it harder for developers to build test new kernels and/or ssh changes and fixes into freefall can lead to exponentially increasing problems and/or delays. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bug: device ether no longer optional
On Thu, Jun 29, 2000 at 11:57:59AM -0700, Archie Cobbs wrote: Andrey A. Chernov writes: Without "device ether" in config file kernel fails to compile and complains on undefined function ether_ifdetach() in if.c:if_detach() Please fix. I'm working on it. Of course, in order to check in the fix, I first need to build a new kernel and test it. But once running the new kernel, I can't check in the fix thanks to the broken ssh. So now I'm now building another kernel with RANDOMDEV, even though that this is the solution was not at all obvious from reading UPDATING. You can also use randomdev_load="YES" in your /boot/loader.conf BTW, I can't boot new kernel at all - kernel and modules loaded OK, but kernel immediately hangs at boot stage. Just to warn you. -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Release still broken with new Perl
On 29-Jun-00 Mark Murray wrote: Hi I just committed a fix for this. Thank you!! M -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: roots shell == /bin/sh please
On Thu, 29 Jun 2000, gnu not unix wrote: Hi. My vote is for root's shell to be /bin/sh if anyone's counting. This will never happen. This position was made clear in th erecent tcsh debate. -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bug: device ether no longer optional
On Thu, 29 Jun 2000, Andrey A. Chernov wrote: On Thu, Jun 29, 2000 at 11:57:59AM -0700, Archie Cobbs wrote: Andrey A. Chernov writes: Without "device ether" in config file kernel fails to compile and complains on undefined function ether_ifdetach() in if.c:if_detach() Please fix. I'm working on it. Of course, in order to check in the fix, I first need to build a new kernel and test it. But once running the new kernel, I can't check in the fix thanks to the broken ssh. So now I'm now building another kernel with RANDOMDEV, even though that this is the solution was not at all obvious from reading UPDATING. You can also use randomdev_load="YES" in your /boot/loader.conf BTW, I can't boot new kernel at all - kernel and modules loaded OK, but kernel immediately hangs at boot stage. Just to warn you. Are you using any optimizations other than "-O -pipe"? There's a problem since Peter's recent changes that cause it to bomb out with anything more exotic. Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bug: device ether no longer optional
On Thu, 29 Jun 2000, Archie Cobbs wrote: Luckily I happened to have seen -current in the past couple of days. Trying to search -current on the web site for the appropriate keywords yeilded only articles from the years 1997 through 1999, nothing in 2000, and there is no way to sort by date anyway. docs.freebsd.org and browse the archives directly. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: roots shell == /bin/sh please
On Thu, Jun 29, 2000 at 12:39:46PM -0700, Doug Barton wrote: On Thu, 29 Jun 2000, gnu not unix wrote: Hi. My vote is for root's shell to be /bin/sh if anyone's counting. This will never happen. This position was made clear in th erecent tcsh debate. Speaking of csh and tcsh, I noticed that /bin/csh is hard linked to /bin/tcsh, yet when I invoke tcsh, I get a different prompt than when I invoke csh. I find this rather odd. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
suidperl doesn't work
Hi, I'm now facing by a problem with the new Perl (5.006) on -current. When I invoke a suidperl script which had been working with the previous Perl, it fails with a message "Can't do setuid". You could reproduce the problem by the following steps.. $ echo '#!/usr/bin/suidperl' foo $ chmod 4755 foo $ ./foo Can't do setuid Anybody got a clue? -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Release still broken with new Perl
On 29-Jun-00 Mark Murray wrote: Hi I just committed a fix for this. Thank you!! Please give me feedback on this when releases work again for you... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: suidperl doesn't work
Hi I'll look at this. M Hi, I'm now facing by a problem with the new Perl (5.006) on -current. When I invoke a suidperl script which had been working with the previous Perl, it fails with a message "Can't do setuid". You could reproduce the problem by the following steps.. $ echo '#!/usr/bin/suidperl' foo $ chmod 4755 foo $ ./foo Can't do setuid Anybody got a clue? -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA support..
On Thu, Jun 29, 2000 at 02:25:50AM -0500, Chris Csanady wrote:
I have been trying to get ssh working in current, but with no luck.
Since I updated recently, all I get is:
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Same for me ... Wanted to make a ssh session to a site I maintain
doesn't work since I use a new kernel (since yesterday)...
andreas@titan{1001} $ ssh -c blowfish IP
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Disabling protocol version 1
Protocol major versions differ: 2 vs. 1
--
Andreas Klemm http://people.FreeBSD.ORG/~andreas
http://www.freebsd.org/~fsmp/SMP/SMP.html
powered by Symmetric MultiProcessor FreeBSD
New APSFILTER 542 and songs from our band - http://people.freebsd.org/~andreas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Panic in boot after flushing buffers
Hello,
I am running -CURRENT from June 27, 2000 (started cvsup around 19:05)
on a PII 266 MHz with 32MB RAM and one IDE disk.
Initially, I noticed that while syncing disks during a reboot, the
system would always give up before finishing. To capture the output,
I configured the kernel to use a serial console by setting flags for
the serial port in the hints file (hint.sio.0.flags="0xb0").
Now, instead of just failing to sync the disks, the system panics about
two out of every three reboots.
The kernel config file (MONSTER) is included as an attachment, as well
as the hints file. Below is the panic information and stack trace.
Let me know if you would like any more information (this is my first
crack at running -CURRENT, so I'm new at this).
Regards,
-brian
System shutdown time has arrived
Shutting down daemon processes: .
Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped
Waiting (max 60 seconds) for system process `syncer' to stop...stopped
syncing disks...
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc090b5bd
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc014c638
stack pointer = 0x10:0xc3b66f0c
frame pointer = 0x10:0xc3b66f20
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1 (init)
interrupt mask = none
panic: from debugger
panic: from debugger
Uptime: 11m4s
dumping to dev #ad/0x20001, offset 65536
dump ata0: resetting devices .. done
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
#1 0xc014cbd5 in panic (fmt=0xc02656f4 "from debugger")
at ../../kern/kern_shutdown.c:553
#2 0xc011f479 in db_panic (addr=-1072380360, have_addr=0, count=1,
modif=0xc3b66d78 "") at ../../ddb/db_command.c:433
#3 0xc011f419 in db_command (last_cmdp=0xc0294b78, cmd_table=0xc02949d8,
aux_cmd_tablep=0xc02b4880) at ../../ddb/db_command.c:333
#4 0xc011f4de in db_command_loop () at ../../ddb/db_command.c:455
#5 0xc012169b in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71
#6 0xc0244626 in kdb_trap (type=12, code=0, regs=0xc3b66ecc)
at ../../i386/i386/db_interface.c:158
#7 0xc0252698 in trap_fatal (frame=0xc3b66ecc, eva=3230709181)
at ../../i386/i386/trap.c:922
#8 0xc0252371 in trap_pfault (frame=0xc3b66ecc, usermode=0, eva=3230709181)
at ../../i386/i386/trap.c:820
#9 0xc0251f2b in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16,
tf_edi = -1011454080, tf_esi = 1, tf_ebp = -1011454176,
tf_isp = -1011454216, tf_ebx = -1064258240, tf_edx = 160160,
tf_ecx = -1070796288, tf_eax = 455, tf_trapno = 12, tf_err = 0,
tf_eip = -1072380360, tf_cs = 8, tf_eflags = 66050,
tf_esp = -1011479040, tf_ss = 1}) at ../../i386/i386/trap.c:426
#10 0xc014c638 in boot (howto=0) at ../../kern/kern_shutdown.c:234
#11 0xc014c40c in reboot (p=0xc3b60e00, uap=0xc3b66f80)
---Type return to continue, or q return to quit---
at ../../kern/kern_shutdown.c:146
#12 0xc0252971 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836,
tf_isp = -1011453996, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4,
tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31,
tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47})
at ../../i386/i386/trap.c:1126
#13 0xc0244f65 in Xint0x80_syscall ()
#14 0x80486ee in ?? ()
#15 0x8048478 in ?? ()
#16 0x8048139 in ?? ()
--
Brian O'Shea
[EMAIL PROTECTED]
#
# MONSTER -- Based on the GENERIC kernel configuration file
#
machine i386
cpu I686_CPU
ident MONSTER
maxusers32
hints "MONSTER.hints" #Default places to look for devices.
makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols
options MATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
options INET6 #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options SOFTUPDATES #Enable FFS soft updates support
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options NFS #Network Filesystem
options NFS_ROOT#NFS usable as root device, NFS required
options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
Re: roots shell == /bin/sh please
On Thu, Jun 29, 2000 at 01:11:39PM -0700, R Joseph Wright wrote: Speaking of csh and tcsh, I noticed that /bin/csh is hard linked to /bin/tcsh, yet when I invoke tcsh, I get a different prompt than when I invoke csh. I find this rather odd. When invoked as tcsh, the shell behaves like tcsh. This is a common technique (check out ex, nex, nvi, nview, vi, and view, for examples; all are hard links to the same file). The program checks its argv[0] and behaves differently depending on what it is set to. -brian -- Brian O'Shea [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA support..
On Thu, 29 Jun 2000, Andreas Klemm wrote: On Thu, Jun 29, 2000 at 02:25:50AM -0500, Chris Csanady wrote: I have been trying to get ssh working in current, but with no luck. Since I updated recently, all I get is: ssh: no RSA support in libssl and libcrypto. See ssl(8). Same for me ... Wanted to make a ssh session to a site I maintain doesn't work since I use a new kernel (since yesterday)... What do you want, a hand-delivered letter with curly letters in gold leaf explaining to you personally how to fix the problem? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RSA support..
Hi
Either you have no RANDOMDEV in the kernel, or you have not loaded the
module.
M
On Thu, Jun 29, 2000 at 02:25:50AM -0500, Chris Csanady wrote:
I have been trying to get ssh working in current, but with no luck.
Since I updated recently, all I get is:
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Same for me ... Wanted to make a ssh session to a site I maintain
doesn't work since I use a new kernel (since yesterday)...
andreas@titan{1001} $ ssh -c blowfish IP
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Disabling protocol version 1
Protocol major versions differ: 2 vs. 1
--
Andreas Klemm http://people.FreeBSD.ORG/~andrea
s
http://www.freebsd.org/~fsmp/SMP/SMP.htm
l
powered by Symmetric MultiProcessor FreeBS
D
New APSFILTER 542 and songs from our band - http://people.freebsd.org/~andrea
s
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic in boot after flushing buffers
Hi
I fixed this yesterday; please re-cvsup and reboot.
You should have sys/dev/randomdev/randomdev.c v1.5 to fix this.
M
I am running -CURRENT from June 27, 2000 (started cvsup around 19:05)
on a PII 266 MHz with 32MB RAM and one IDE disk.
Initially, I noticed that while syncing disks during a reboot, the
system would always give up before finishing. To capture the output,
I configured the kernel to use a serial console by setting flags for
the serial port in the hints file (hint.sio.0.flags="0xb0").
Now, instead of just failing to sync the disks, the system panics about
two out of every three reboots.
The kernel config file (MONSTER) is included as an attachment, as well
as the hints file. Below is the panic information and stack trace.
Let me know if you would like any more information (this is my first
crack at running -CURRENT, so I'm new at this).
Regards,
-brian
System shutdown time has arrived
Shutting down daemon processes: .
Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped
Waiting (max 60 seconds) for system process `syncer' to stop...stopped
syncing disks...
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc090b5bd
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc014c638
stack pointer = 0x10:0xc3b66f0c
frame pointer = 0x10:0xc3b66f20
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1 (init)
interrupt mask = none
panic: from debugger
panic: from debugger
Uptime: 11m4s
dumping to dev #ad/0x20001, offset 65536
dump ata0: resetting devices .. done
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6
5 4 3 2 1
---
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
#1 0xc014cbd5 in panic (fmt=0xc02656f4 "from debugger")
at ../../kern/kern_shutdown.c:553
#2 0xc011f479 in db_panic (addr=-1072380360, have_addr=0, count=1,
modif=0xc3b66d78 "") at ../../ddb/db_command.c:433
#3 0xc011f419 in db_command (last_cmdp=0xc0294b78, cmd_table=0xc02949d8,
aux_cmd_tablep=0xc02b4880) at ../../ddb/db_command.c:333
#4 0xc011f4de in db_command_loop () at ../../ddb/db_command.c:455
#5 0xc012169b in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71
#6 0xc0244626 in kdb_trap (type=12, code=0, regs=0xc3b66ecc)
at ../../i386/i386/db_interface.c:158
#7 0xc0252698 in trap_fatal (frame=0xc3b66ecc, eva=3230709181)
at ../../i386/i386/trap.c:922
#8 0xc0252371 in trap_pfault (frame=0xc3b66ecc, usermode=0, eva=3230709181)
at ../../i386/i386/trap.c:820
#9 0xc0251f2b in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16,
tf_edi = -1011454080, tf_esi = 1, tf_ebp = -1011454176,
tf_isp = -1011454216, tf_ebx = -1064258240, tf_edx = 160160,
tf_ecx = -1070796288, tf_eax = 455, tf_trapno = 12, tf_err = 0,
tf_eip = -1072380360, tf_cs = 8, tf_eflags = 66050,
tf_esp = -1011479040, tf_ss = 1}) at ../../i386/i386/trap.c:426
#10 0xc014c638 in boot (howto=0) at ../../kern/kern_shutdown.c:234
#11 0xc014c40c in reboot (p=0xc3b60e00, uap=0xc3b66f80)
---Type return to continue, or q return to quit---
at ../../kern/kern_shutdown.c:146
#12 0xc0252971 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836,
tf_isp = -1011453996, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4,
tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31,
tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47})
at ../../i386/i386/trap.c:1126
#13 0xc0244f65 in Xint0x80_syscall ()
#14 0x80486ee in ?? ()
#15 0x8048478 in ?? ()
#16 0x8048139 in ?? ()
--
Brian O'Shea
[EMAIL PROTECTED]
--7ZAtKRhVyVSsbBD2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=MONSTER
#
# MONSTER -- Based on the GENERIC kernel configuration file
#
machine i386
cpu I686_CPU
ident MONSTER
maxusers 32
hints "MONSTER.hints" #Default places to look for devices.
makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols
options MATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
options INET6 #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options SOFTUPDATES #Enable FFS soft updates support
options MFS #Memory Filesystem
Re: bug: device ether no longer optional
At 1:10 PM -0700 6/29/00, Kris Kennaway wrote: On Thu, 29 Jun 2000, Archie Cobbs wrote: Luckily I happened to have seen -current in the past couple of days. Trying to search -current on the web site for the appropriate keywords yeilded only articles from the years 1997 through 1999, nothing in 2000, and there is no way to sort by date anyway. docs.freebsd.org and browse the archives directly. Also, note that the problem is what the web site is REPORTING for the dates on messages, and not that the messages themselves are missing. I recently filed PR Docs/19507 on this. It wouldn't surprise me if someone else has filed a PR on it. The problem is that most articles which REALLY have a date in 2000 are REPORTED as having the same date as the most recent article in the search list which is not in year 2000. If you click on one of the articles, the article itself is fine. It's just the listing for it which is coming up wrong. (see the example given in http://www.freebsd.org/cgi/query-pr.cgi?pr=19507 ) --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
Warner Losh wrote: In message [EMAIL PROTECTED] "Thomas M. Sommers" writes: : Warner Losh wrote: : : Any reason that the .c/.h files of the drivers couldn't be used to : generate this information? : : Or perhaps the other way around. No. I'm saying that the .c and .h files (likely .h) are the source to the driver and driver maintanier are 1000% more likely to keep those up to date than they are xxx.xml. Right now, with modules, you can easily not have to worry about any config issues outside of those files. Forcing a doc file just to get docs and breaking this is undesirable. Expanding what the driver writers are already doing a little seems like a smarter move. I was thinking of something analogous to the way syscalls.master is used to generate several files. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
In message [EMAIL PROTECTED] "Thomas M. Sommers" writes: : I was thinking of something analogous to the way syscalls.master is used : to generate several files. This works well for syscalls.master, but I don't think it would work well in the driver area. Call me crazy. However, I'll take an open and honest look at anything people come up with in this area. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic in boot after flushing buffers
Interesting. I've also been seeing this on alphas. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: roots shell == /bin/sh please
R Joseph Wright wrote: Speaking of csh and tcsh, I noticed that /bin/csh is hard linked to /bin/tcsh, yet when I invoke tcsh, I get a different prompt than when I invoke csh. I find this rather odd. This is documented behaviour. When argv[0] is csh, it tries very hard to behave exactly the same as a traditional /bin/csh. -- || David Nugent || TS Manager, ISP Limited || \\ [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] // .\\ Ph: +61396422322 Fax: +61396422063 Cell: +61404867638 //. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Perl won't installworld: INET.pm
Just cvsupped: Make buildworld seems ok now, however make installworld fails: === gnu/usr.bin/perl === gnu/usr.bin/perl/libperl install -c -o root -g wheel -m 444 libperl.a /usr/lib install -c -s -o root -g wheel -m 444 libperl.so.4 /usr/lib ln -sf libperl.so.4 /usr/lib/libperl.so === gnu/usr.bin/perl/miniperl install -c -s -o root -g wheel -m 555 miniperl /usr/bin === gnu/usr.bin/perl/perl install -c -s -o root -g wheel -m 555 perl /usr/bin /usr/bin/perl5 - /usr/bin/perl /usr/bin/perl5.006 - /usr/bin/perl === gnu/usr.bin/perl/suidperl install -c -s -o root -g wheel -m 4511 suidperl /usr/bin /usr/bin/sperl5 - /usr/bin/suidperl /usr/bin/sperl5.006 - /usr/bin/suidperl === gnu/usr.bin/perl/library install: /usr/libdata/perl/5.006/./IO/Socket/INET.pm: No such file or directory *** Error code 71 Stop in /usr/src/gnu/usr.bin/perl/library. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
So, this is what I worried about. :-)
At 29 Jun 2000 16:01:36 GMT,
Warner Losh [EMAIL PROTECTED] wrote:
I'd violently oppose this. I'd rather see the XML file generated from
the .h files that we already use to build the system with. You would
be making it just as hard to keep things up to date with little gain
from the programmer's point of view. You need to make it easier for
the programmer to keep things up to date rather than harder.
From the documentation point of view, XML source file should be used
to generate other "rendered" text such as *.c/*.h. In principle,
using XML is same process such as using src/sys/dev/usb/usbdevs. As
you know, generation of usbdevs{,_data}.h is done by awk script. And
same procedure is done in src/sys/dev/pccarddevs for generating
pccarddevs{,_data}.h.
I think what Nik wants to say is, suggesting standard scheme to
generate these files from human readable source file. And he suggests
XML as that source file format.
Of course, source tree are for programmers. First thing we should
consider is not to stress programmers for that procedure. Nik's
suggestion is more conceptual one. We need more discussion for this
subject.
# Nik, we should explain more about XML for freebsd-current people
# before stepping forward. :-)
--
Jun Kuriyama [EMAIL PROTECTED] // FreeBSD Project
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
On Fri, 30 Jun 2000 12:08:50 +0900, Jun Kuriyama [EMAIL PROTECTED] said:
using XML is same process such as using src/sys/dev/usb/usbdevs. As
you know, generation of usbdevs{,_data}.h is done by awk script. And
same procedure is done in src/sys/dev/pccarddevs for generating
pccarddevs{,_data}.h.
Both of which are bugs imported from NetBSD.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
HEADS UP: new fetch(1)
On 29 Jun 2000 09:58:20 +0200, Dag-Erling Smorgrav [EMAIL PROTECTED] said: I've replaced fetch(1) with a libfetch-based implementation. It introduces numerous style bugs in both code and documentation, and furthermore claims copyright on text in the manual page which I wrote. It also removes support for a number of important features. On the positive site, it certainly looks a lot cleaner than the old implementation. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
