Re: Multi BOOT
Abdul Hakeem wrote: Does anyone know a way of simultaneously booting FreeBSD with Linux or Win2K with a dual-processor and dual NIC server ? I can set the processor affinity on the Win2k, but I am having trouble configuring the FreeBSD to use a particular processor and a particular NIC. Just because a machine has multiple processors and multiple NICs, doesn't make it capable of operating as two machines in the same case. There are a lot of different things, like the memory and I/O bus, the 8254 clock, etc., which have to be programmed differently for different OSs. To run two virtual machines on a single real machine, you are going to need some software assistance, e.g. a product like VMWare. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Text file busy
Paul Richards wrote: Overwriting a file that's currently executing results in a Text file busy error. When did this start happening? This was something that was fixed way back on FreeBSD but it seems to be a problem again. You are opening an existing file for write. You need to rename on top of it, or delete and create a new one, and this will not happen. The issue is that the pages in the executing file are not necessarily all in core, so it can't copy-on-write them, since it doesn't know that they are being dirtied. The copy-on-write behaviour is relatively new; old System V and Xenix system did not permit even deleting an executing file, since the process did not hold an open file reference on the file. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Text file busy
Wesley Morgan wrote: On Thu, 4 Sep 2003, Scott M. Likens wrote: On Thu, 2003-09-04 at 07:44, Paul Richards wrote: Overwriting a file that's currently executing results in a Text file busy error. this feature has always existed in FreeBSD for as long as I remember. It's also unfortunate that this protection does not seem to extend to libaries. I've had some in-use X libraries get overwritten with some very colorful results. So send patches. The specific problem is in the ld.so mapping of a page in a library file as executable, and this mapping not setting the bit on the file image. In general, this isn't done because the other references to the file image may be as data (there's a race condition on install, and a security race, if the libraries are writable, that could permit a linked-shared SUID executable to be compromised after it's running, but then if it's writable at all, that exists anyway). So it's probably safe to do this without resource tracking the processes who've got it mapped this way. My ld.so currently differs significantly from the stock version, as does my C++ static constructor code, since I have a working static libdlopen on my own developement boxes, so the patches I have for this would be pretty useless for you, but they would be quite trivial to recreate; all you do is set the bit whem mmap has PROT_EXEC, or when mprotect has PROT_EXEC (both of these are used by ld.so; for the crt0.c startup code that loads ld.so initially, only mmap is used). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
New kernels won't boot
Hi, I'm currently having the problem that newer kernels won't boot anymore on a HP Proliant DL380G3. The latest kernel I can boot is from Sun Aug 31 15:22:44 CEST 2003. Every attempt to boot a newer one (regardless whether UP or SMP) hangs at: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2387622296 Hz quality 800 Timecounters tick every 10.000 msec And then... silence. Any ideas? regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)
Alexander Leidinger wrote: Dan Nelson [EMAIL PROTECTED] wrote: If you're talking FreeBSD 5, you should be able to simply subsitute a C99 flexible array member (basically replace [0] with []) and get the same effect. 0-length arrays are a gcc extension: http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html Under FreeBSD 4.x, you can't use them because gcc 2.95 only supports the gcc extension. Intel has added support for a lot of gcc extensions recently; they may be willing to add this to the list. Please read my mail again, icc already supports my_array[0], but the resulting array in the binary has size '1'. The actual showstopper is the output of genassym.sh. To me it seems it's just a genassym.sh issue, but I don't really know what's going on in the kernel, so I ask here. The ICC is wrong. If they are supporting a GNU extension, they must do it the same way GNU does it, to actually be supporting it. The main issue here is that any reader of the object file, not just genassym.sh, will be unable to differentiate [0] vs. [1]. What does ICC do for []? Is it '1' also, or is it '0', like it's supposed to be? I, for one, would not be unhappy to see the GCC-ism fade into history. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)
On Thu, 4 Sep 2003 15:57:31 -0700 Marcel Moolenaar [EMAIL PROTECTED] wrote: On Thu, Sep 04, 2003 at 05:51:23PM -0500, Dan Nelson wrote: I guess the correct question to be asking is does the ELF format allow 0-length symbols? Of course. What size do you think a label should have otherwise? After mentioning the difference between gcc and icc I've got this response: ---snip--- Regarding the zero size array issue: Objects with zero size are incomplete objects and cannot be used in any meaningful way. Zero length arrays are explicitly prohibited by the Standard. We allowed zero length arrays as a feature request. We set their size to one so operations involving them can make some kind of sense. ---snip--- Can you please give me something a compiler developer should understand (an URL, a reference into some standard, a description, ...)? As long as we can provide strong evidence that gcc doesn't do the wrong thing Intel will change icc to be compatible with gcc. Bye, Alexander. -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)
Dan Nelson wrote: I guess the correct question to be asking is does the ELF format allow 0-length symbols? It does, according to my reading of it. They may have an issue with dead code removal or element aliasing. The way to find out would be to see what they emit for []... 0 lenth, or 1? If not, then gcc is generating invalid objects, and genassym will have to be rewritten to not use them (maybe add one to the array size, and have genassym.sh subtract it). If it does, then genassym.c (sys/assym.h actually) is legal code. If Intel doesn't want to change icc, we can still work around it, but there may be other code that will break on icc just like assym.h. For example, an actual array of length 1 would mean you were screwed, since treating 1 as if it were 0 would treat that as zero, as well, and get the wrong answer. The real answer is that the code should probably use an array length of one, and then use the address of the array length 1 element, rather than the address of the object plus the size of the object, when it's trying to use the zero length array trick to glue data with the correct object alignment (according to the array type) onto the end of a structure, which is where most of this type of code comes from. Unfortunately, the genassym.sh is a special case; for it to work out if you changed the nature of the trick, the script would need to grow special knowledge of the symbols in question. That is probably going to be the answer in any case, if Intel is unwilling/unable to adopt the GCC-ism. Anecdote on unable: At one point in time SEF had to deal with a compiler issue with the Microsoft C compiler used by SCO; it took code like this: char *hw = Hello World!\n + 6; and generated a data segment missing the Hello . When the code later did this: printf( %s, hw - 6); It got the wrong answer. The problem was the MS compiler was unable to gerate a pseudo-symbol for the start of the data, and so had no way of taking the origina string, and allocating storage, with a static symbol offset +6 into the string. If Intel ICC makes an optimization based on pruning of actually zero-length element, or not aligning them to their type boundary, etc., it would take deep compiler voodoo to correct this. Hopefully, they do the right thing for []. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)
On Thu, 4 Sep 2003, Marcel Moolenaar wrote: On Fri, Sep 05, 2003 at 02:59:22AM +0200, Marius Strobl wrote: We use the size of the symbol (ie the size of the object identified by the symbol) to pass around values. This we do by creating arrays. If we want to export a C constant 'FOOBAR' to assembly and the constant is defined to be 6, then we create an array for the sign, of which the size is 1 for negative numbers and 0 otherwise. In this case the array will be named FOOBARsign and its size is 0. We also create 4 arrays (*w0, *w1, *w2 and *w3), each with a maximum of 64K and corresponding to the 4 16-bit words that constitutes a single 64-bit entity. In this case 0006 C FOOBARw0 C FOOBARw1 C FOOBARw2 C FOOBARw3 If the compiler creates arrays of size 1 for arrays we define as a zero-sized array, you get exactly what you've observed. Is this rather complex approach really necessary? In theory, yes. In practice, maybe not. If I remember correctly, the problem we're trying to solve is twofold: More like fourfold: -1: A cross-compiler must be used for the first stage. The old method of printf()'ing the results of sizeof(), etc., only works if the host machine is the same as the target machine, since sizeof() must be evaluated by a compiler for target machine and printf() can only be run on host machines. 0: Compiler output is to unportable to parse easily, so arrange to use a small portable subset of it after passing it through some standard filters. nm output was the most portable binutils-related output that I could think of. 1. 64-bit constants given the limitations of the object format, which included widths of 32-bit and a.out. After choosing to use nm output, there are some minor problems representing all relevant numbers using it. Numbers larger than 2^32 need to be represented but cannot be represented directly as symbol values or sizes in nm output on 32-bit machines. Numbers nearly as large as 2^32 can be represented as absolute symbols, but there is no way to generate absolute symbols in semi-portable C AFAIK. asm() statements might work but would be very unportable (apart from not being standard C, different ones might be needed for the aout and elf cases). The technique of using array sizes for all numbers works for most sizes, but the compiler might object to creating arrays almost as large as the address space, and as we have just found, to creating arrays of size 0. 2. Sign extension or datatype limitations in awk(1)? I'm not sure about this point. Bruce? Yes: one-true-awk uses typedef double Awkfloat;, and gawk uses something similar by default IIRC, so awk can't hanele numbers larger than 2^53 without losing precision. typedef long double Awkfloat;, would be no better because of my restriction of the precision of long doubles on i386's and (when genassym.sh was written) the incomplete library support for long doubles, and the nonexisted support for more than 53 bits of precision on some supported (?) hardware. Long doubles with 64 bits of precision wouldn't work for representing 128-bit integers anyway. ... The genassym.sh(8) of NetBSD kind of directly exports the C-constants so it just needs one symbol per constant and doesn't require zero sized arrays. Given that it's from NetBSD their approach also should be very MI. I wouldn't have a problem using NetBSD's genassym implementation, provided we understand completely how it differs from ours and to what extend and how it affects us and provided of course we can live with whatever it is that's worse of just different from what we have now. The main differences seem to be that it parses the assembler output. This is less portable and not as easy -- it takes about 5 times as much code. If some values are unrepresentable then they need to be represtended using other values. E.g., add 1 to avoid 0, or multiply by the alignment size if some element of the tool chanin instsists on rounding up things for alignment like a broken aout version used to do. 16-bit values would need 17 bits to represent after adding 1. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ACPI problems with Compaq Evo N610c (fwd)
Hello Doug, From [EMAIL PROTECTED] Fri Sep 5 05:49:49 2003 Not sure if you got a copy of this first time or not... Sorry, no I did not. My mail pickup system got screwed several times lately. -- Forwarded message -- From: Doug Barton [EMAIL PROTECTED] To: Cagle, John (ISS-Houston) [EMAIL PROTECTED] Cc: Tony Maher [EMAIL PROTECTED], Robert Blacquière [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Sun, 31 Aug 2003 19:50:03 -0700 (PDT) Organization: http://www.FreeBSD.org/ Subject: RE: ACPI problems with Compaq Evo N610c I got interested in this recently because I inherited one of these laptops from work. On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com website.) I know that the _OSI(Windows 2001) bug will be fixed in the F.15 release, but I don't think the _GL_ portion of your patch will be included. Did you have to remove the Acquire Release of _GL_ in order to get xbat to work? (This is not a problem we see with Linux ACPI in 2.4.21, so I think that FreeBSD's ACPI stack needs updating.) I just updated to F.15, and it does indeed fix the windows bit in the output of 'acpidump -d'. However, even with Tony's recommendation of removing the acquire/release of _GL in methods C12C and C12D, I still can't get xbatt or wmbattery to run, even with the very latest -current (which has had at least one acpi stack upgrade since 7/30). When I run either command, it locks the box tight. If I ever get a cursor back, I have to Ctrl-Alt-Backspace to get out of X, since I can't actually type anything. I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY This certainly seems to be the case. I see ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS Also, the before and after acpidump's don't show anything different. So, I'm curious if wmbatt is still working for Tony and Robert or not with the latest -current. I am currently running FreeBSD k9.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 30 11:48:23 EST 2003 [EMAIL PROTECTED]:/var/obj/space/usr/src/sys/K9 i386 and xbatt works (to certain extent - it show s being power cable in and out and shos charging state when first booted up but after insertion/removal of power cord it no longer shows charging stae or time left in battery) If I get a cahnce on weekend I'll update to latest and let you know. The other problem I'm having is that doing 'sysctl -a', or just 'sysctl hw.acpi' locks the system tight for a couple minutes, and never completes. The last line that's printed to the screen is: hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 Any ideas on that one? This is becase the DSDT was not overridden. I used to see this as well. -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Text file busy
On Thu, 2003-09-04 at 19:20, Tim Kientzle wrote: Depends on how you're installing the binary. It has always been safe to do either of the following: * Rename the current executable and then install the new one. * Unlink the current executable and then install the new one. Many tools that claim to overwrite really do the latter, which causes a certain amount of understandable confusion. (I'm pretty sure install does unlink/copy by default and will do rename/copy if you specify -b.) I thought I remembered a discussion from the very early days where a solution was implemented to copy the pages if a file was overwritten into memory or swap but I can find no record of that now other than a suggestion in a thread that Solaris might do this. I think I'm confusing the above impression with an actual problem that was fixed where you'd still get the error even though the program had stopped executing. Paul. intY has scanned this email for all known viruses (www.inty.com) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sizedarrays(showstopperfor an icc compiled kernel)
Alexander Leidinger wrote:
On Fri, 05 Sep 2003 01:38:29 -0700
Terry Lambert [EMAIL PROTECTED] wrote:
Dan Nelson wrote:
I guess the correct question to be asking is does the ELF format allow
0-length symbols?
It does, according to my reading of it. They may have an issue with
dead code removal or element aliasing. The way to find out would be
to see what they emit for []... 0 lenth, or 1?
% icc.c
char array[];
% nm icc.o
0001 C array
Now try:
struct foo {
char c;
int i;
long array[];
};
struct foo foo;m
struct foo fee[1];
struct foo fie[3];
struct foo foe[0];
struct foo fum[1];
on both compilers. If they end up the same, then Intel needs to
change to using the 0. If they end up different, then they are
broken relative to the C99 standard and zero length arrays a final
elements in structures.
-- Terry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)
On Fri, 5 Sep 2003, I wrote: ... If some values are unrepresentable then they need to be represtended using other values. E.g., add 1 to avoid 0, or multiply by the alignment size if some element of the tool chanin instsists on rounding up things chain insists for alignment like a broken aout version used to do. 16-bit values would need 17 bits to represent after adding 1. Better, add 0x1 to avoid 0. awk has no support for parsing hex numbers so subtracting the bias of 1 would take a lot more code, but ignoring leading hexdigits requires no changes in genassym.sh -- it already ignores everything except the last 4 hexdigits. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sizedarrays(showstopper for an icc compiled kernel)
On Fri, 05 Sep 2003 02:06:56 -0700
Terry Lambert [EMAIL PROTECTED] wrote:
Now try:
struct foo {
char c;
int i;
long array[];
};
struct foo foo;m
struct foo fee[1];
struct foo fie[3];
struct foo foe[0];
struct foo fum[1];
on both compilers. If they end up the same, then Intel needs to
change to using the 0. If they end up different, then they are
broken relative to the C99 standard and zero length arrays a final
elements in structures.
% icc -c terry.c
terry.c(8): warning #1229: type containing an unknown-size array may alias another
element
struct foo fee[1];
^
terry.c(9): warning #1229: type containing an unknown-size array may alias another
element
struct foo fie[3];
^
terry.c(10): warning #1229: type containing an unknown-size array may alias another
element
struct foo foe[0];
^
terry.c(11): warning #1229: type containing an unknown-size array may alias another
element
struct foo fum[1];
^
icc:
0008 C fee
0018 C fie
0008 C foe
0008 C foo
0008 C fum
gcc:
0008 C fee
0018 C fie
C foe
0008 C foo
0008 C fum
Bye,
Alexander.
--
Where do you think you're going today?
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Patch] mdmfs currently broken
On Thu, 4 Sep 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Stefan =?iso-8859- 1?Q?E=DFer?= writes: Seems that mdmfs stopped working recently (probably because of GEOM related changes). One possible fix is to label the md and newfs the thusly created c partition. This requires running /sbin/disklabel, which didn't have an entry in paths.h. Any objections against me committing the follwoing fixes to -current ? Yes, please don't. We should not revert to putting BSD labels on everything. I'll find the root cause and fix that instead, it's probably fall-out from my ioctl change. Disk labels are required by the not unused fsck_ffs utility to search for alternate superblocks. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Patch] mdmfs currently broken
In message [EMAIL PROTECTED], Bruce Evans writes: We should not revert to putting BSD labels on everything. Disk labels are required by the not unused fsck_ffs utility to search for alternate superblocks. You mean: The widely used fsck_ffs utility is able to use information from the optional BSD disklabel. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Latest -current boot stops cold after first CD
I compiled the latest -current, and now it doesn't even boot. :( My first cd drive (a CD-ROM) is probed, but it falls back to PIO4. The kernel boot freezes after that point, and my CD-RW is never detected. This time the trick of putting a CD into the second drive doesn't help. I've added back the atapicam and ATA_STATIC_ID options to my kernel. Haven't had a chance to try the latest kernel without atapicam. I posted a dmesg recently, let me know if you need another copy. My 8/31 kernel works fine, FYI. Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel)
On Thu, Sep 04, 2003 at 11:28:58AM -0500, Dan Nelson wrote: In the last episode (Sep 04), Alexander Leidinger said: - If we depend on it: how hard would it be to rewrite it to not depend on 0-sized arrays (and does someone volunteer to rewrite it)? It would be nice if someone could point me to the source if it isn't an easy task, my contact @Intel is willing to convince the developers to change icc, but he has to present a persuasive argument to development to pursue a solution. If you're talking FreeBSD 5, you should be able to simply subsitute a C99 flexible array member (basically replace [0] with []) and get the same effect. 0-length arrays are a gcc extension: But even with flexible array members you cannot create an object with size 0. The struct must have at least one additional member and you cannot use sizeof on the flexible array member itself as its type is incomplete. Cheers, Stefan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)
On Fri, Sep 05, 2003 at 07:34:39PM +1000, Bruce Evans wrote: On Fri, 5 Sep 2003, I wrote: ... If some values are unrepresentable then they need to be represtended using other values. E.g., add 1 to avoid 0, or multiply by the alignment size if some element of the tool chanin instsists on rounding up things chain insists for alignment like a broken aout version used to do. 16-bit values would need 17 bits to represent after adding 1. Better, add 0x1 to avoid 0. awk has no support for parsing hex numbers so subtracting the bias of 1 would take a lot more code, but ignoring leading hexdigits requires no changes in genassym.sh -- it already ignores everything except the last 4 hexdigits. This works, too. Thanks for the detailed explanation Bruce! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Patch] mdmfs currently broken
On Fri, 5 Sep 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: We should not revert to putting BSD labels on everything. Disk labels are required by the not unused fsck_ffs utility to search for alternate superblocks. You mean: The widely used fsck_ffs utility is able to use information from the optional BSD disklabel. I mean: The widely used fsck_ffs utility's ability to find alternate superblocks will be broken when it is most needed if certain parts of disk labels or equivalent metadata is not written automatically somewhere outside of the file system proper. Users who don't know what a disk label or an alternate superblock is can't be expected to back them up or calculate the correct block number to supply to fsck_ffs -b. The file system info in the label is a form of backup of a (very) few parameters. The alternate superblocks are another. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New kernels won't boot
On Fri, 5 Sep 2003, Lukas Ertl wrote: I'm currently having the problem that newer kernels won't boot anymore on a HP Proliant DL380G3. The latest kernel I can boot is from Sun Aug 31 15:22:44 CEST 2003. Every attempt to boot a newer one (regardless whether UP or SMP) hangs at: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2387622296 Hz quality 800 Timecounters tick every 10.000 msec Ok, I've found out that if I boot -v I get further than this and see the following messages: (probe9:ciss0:0:9:0): Request completed with CAM_REQ_CMP_ERR (probe9:ciss0:0:9:0): error 5 (probe9:ciss0:0:9:0): Retries Exausted (probe10:ciss0:0:10:0): Request completed with CAM_REQ_CMP_ERR (probe10:ciss0:0:10:0): error 5 (probe10:ciss0:0:10:0): Retries Exausted (probe11:ciss0:0:11:0): Request completed with CAM_REQ_CMP_ERR (probe11:ciss0:0:11:0): error 5 (probe11:ciss0:0:11:0): Retries Exausted (probe12:ciss0:0:12:0): Request completed with CAM_REQ_CMP_ERR (probe12:ciss0:0:12:0): error 5 (probe12:ciss0:0:12:0): Retries Exausted (probe13:ciss0:0:13:0): Request completed with CAM_REQ_CMP_ERR (probe13:ciss0:0:13:0): error 5 (probe13:ciss0:0:13:0): Retries Exausted (probe14:ciss0:0:14:0): Request completed with CAM_REQ_CMP_ERR (probe14:ciss0:0:14:0): error 5 (probe14:ciss0:0:14:0): Retries Exausted ciss0: command status 0x1 (target status) scsi status 0x2 (probe0:ciss0:0:0:0): error 22 (probe0:ciss0:0:0:0): Unretryable Error ciss0: command status 0x1 (target status) scsi status 0x2 (probe1:ciss0:0:1:0): error 22 Anything CAM/SCSI-related? regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ips.ko load sequence for IBM ServerRaid 5i
I know this is the already the second place you have been directed to, but you may have more luck in freebsd-scsi. (cc'd there) On Thu, Sep 04, 2003 at 02:42:30PM -1000, Richard Puga wrote: I do have the ips driver working with the IBM ServerRaid 5i. However it only works if I boot of an IDE drive and load the driver after the kernel is loaded. What I believe the problem to be is the fact that this Raid card is just an add in card to a modified PCI slot that makes the on board LSI dual channel controller into a RAID, and something in the kernel is loading (not the LSI driver its been taken out) which makes these 2 separate devices act as one through the PCI bus and is the reason it can only be loaded after booting. I believe a quick and dirty fix for this may be to load the ips.ko module after the kernel has booted and before init mounts /. Is there a way to do this via something in /boot/loader (the standard way in loader.conf loads it too soon) or perhaps a way to compile isp into the kernel in a way that it would be probed at a later time or in a different sequence? Thanks again in advance Richard Puga [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
devd *NOT* called on wi0 insert?
I have a (within the week) -CURRENT system. If I boot with my Linksys WPC11 V.3 card inserted I get the dhcp actions and all is fine. If I remove the card, we don't kill off dhclient. If I boot without the card, and then insert it later, I do NOT get dhclient starting. I modified /etc/rc.d/devd to start devd with the -D switch, and it appears to my untrained eyes that devd is NOT being called on the insert. What can I get to help debug this? /etc/rc.conf: # -- sysinstall generated deltas -- # Thu Apr 3 13:56:26 2003 # Created: Thu Apr 3 13:56:26 2003 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. kern_securelevel_enable=NO linux_enable=YES moused_enable=YES sendmail_enable=YES sshd_enable=YES usbd_enable=YES hostname=lerlaptop devd_enable=YES dumpdev=/dev/ad0s1b dumpdir=/shared/crash/current apm_enable=YES # Set to YES to enable APM BIOS functions (or NO). apmd_enable=YES # Run apmd to handle APM event from userland. ifconfig_wi0=DHCP lpd_enable=YES # Run the line printer daemon. lpd_flags=-l# Flags to lpd (if enabled). inetd_enable=YES# Run the network daemon dispatcher (YES/NO). clear_tmp_enable=YES# Clear /tmp at startup. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about genassym, locore.s and 0-sized arrays(showstopper for an icc compiled kernel)
On Fri, Sep 05, 2003 at 10:55:07AM +0200, Alexander Leidinger wrote:
It does, according to my reading of it. They may have an issue with
dead code removal or element aliasing. The way to find out would be
to see what they emit for []... 0 lenth, or 1?
% icc.c
char array[];
% nm icc.o
0001 C array
Interesting, What does icc do with:
struct {
int tag;
char obj[];
} foo;
And what does the sizeof() operator give.
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
atapicam0: timeout waiting for ATAPI ready (5.1-CURRENT, IBM T30)
Yesterday's cvsup'd and compiled kernel hung at acd0: CDRW UJDA720 DVD/CDRW at ata1-master UDMA33 atapicam0: timeout waiting for ATAPI ready (5.1-current, IBM T30) I waited until today and did another cvsup, same problem. What I expect to see is: acd0: CDRW UJDA720 DVD/CDRW at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a It does this if there is a CD in the drive as well as when there isn't. Removing atapicam from the kernel def and recompile removed the hang. : || tylendel.castle.org [4] ; uname -a FreeBSD tylendel.castle.org 5.1-CURRENT FreeBSD 5.1-CURRENT #48: Fri Sep 5 10:53:09 PDT 2003 [EMAIL PROTECTED]:/users/FreeBSD-5.0/obj/users/Fre eBSD-5.0/src/sys/TYLENDEL i386 nomad --- - Lee nomad Damon - \ play: [EMAIL PROTECTED]or castle!nomad \ work: [EMAIL PROTECTED] \ /\ Seneschal, Castle PAUS./ \ Celebrate Diversity /\ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: config(8) KERNEL setting
Doug White wrote: On Thu, 4 Sep 2003, John Birrell wrote: however kern.post.mk only uses KERNEL_KO, so even though config(8) has set KERNEL for me, that name only gets used for the boot directory. There doesn't seem to be any way of getting KERNEL_KO set from the kernel config file. If you change the name of the kernel binary itself, loader won't be able to find it. By renaming the /boot directory it goes into it is Doing the Right Thing. Huh? kernel=kernel # /boot sub-directory containing kernel and modules bootfile=kernel # Kernel name (possibly absolute path) I note that loader.conf(5) is completely out of date in this regard. What can I say? I'm lazy. :-) In 5.X, the kernel is the core kernel binary and the modules built with it. All of it goes into the same directory. The /modules directory is unused and should be deleted. When you specify a kernel to load in loader, you ask for the /boot/foo directory name (load foo) and loader does the rest. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] She stood on the tracks Waving her arms Leading me to that third rail shock Quick as a wink She changed her mind She gave me a night That's all it was What will it take until I stop Kidding myself Wasting my time There's nothing else I can do 'Cause I'm doing it all for Leyna I don't want anyone new 'Cause I'm living it all for Leyna There's nothing in it for you 'Cause I'm giving it all to Leyna -- Billy Joel, All for Leyna (Glass Houses) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: Hi again chaps, I've been working on other things lately, including getting ready to move house and looking after my 3 month old daughter :) but recently I've took up trying to get this driver working again. If anyone is interested in helping out, could they give http://stu.bash.sh/if_sk.c and http://stu.bash.sh/if_skreg.h a try and let me know what output you get. I'm only really interested in what happens after the MAC gets printed so don't go to too much trouble to get the exact info. Just plonk the files in /usr/src/sys/pci over the top of the old ones. Thanks to anyone who helps out. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd *NOT* called on wi0 insert?
In message: [EMAIL PROTECTED] Larry Rosenman [EMAIL PROTECTED] writes: : I have a (within the week) -CURRENT system. If I boot with my Linksys : WPC11 V.3 card inserted : I get the dhcp actions and all is fine. If I remove the card, we don't : kill off dhclient. : : If I boot without the card, and then insert it later, I do NOT get dhclient : starting. : : I modified /etc/rc.d/devd to start devd with the -D switch, and it appears : to my : untrained eyes that devd is NOT being called on the insert. : : What can I get to help debug this? : : /etc/rc.conf: : : # -- sysinstall generated deltas -- # Thu Apr 3 13:56:26 2003 : # Created: Thu Apr 3 13:56:26 2003 : # Enable network daemons for user convenience. : # Please make all changes to this file, not to /etc/defaults/rc.conf. : # This file now contains just the overrides from /etc/defaults/rc.conf. : kern_securelevel_enable=NO : linux_enable=YES : moused_enable=YES : sendmail_enable=YES : sshd_enable=YES : usbd_enable=YES : hostname=lerlaptop : devd_enable=YES : dumpdev=/dev/ad0s1b : dumpdir=/shared/crash/current : : apm_enable=YES # Set to YES to enable APM BIOS functions (or NO). : apmd_enable=YES # Run apmd to handle APM event from userland. : ifconfig_wi0=DHCP : lpd_enable=YES # Run the line printer daemon. : lpd_flags=-l# Flags to lpd (if enabled). : inetd_enable=YES# Run the network daemon dispatcher (YES/NO). : clear_tmp_enable=YES# Clear /tmp at startup. Is devd running? What is the output of devd I know this is working, because I use it every single day many times a day with both ath and wi. I do have pccard_ifconfig=DHCP in my rc.conf. Maybe you have a second dhclient running. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd *NOT* called on wi0 insert?
--On Friday, September 05, 2003 13:30:03 -0600 M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] Larry Rosenman [EMAIL PROTECTED] writes: : I have a (within the week) -CURRENT system. If I boot with my Linksys : WPC11 V.3 card inserted : I get the dhcp actions and all is fine. If I remove the card, we don't : kill off dhclient. : : If I boot without the card, and then insert it later, I do NOT get dhclient : starting. : : I modified /etc/rc.d/devd to start devd with the -D switch, and it appears : to my : untrained eyes that devd is NOT being called on the insert. : : What can I get to help debug this? : Is devd running? yes. What is the output of devd all the stuff except for wi0 (but see below). I know this is working, because I use it every single day many times a day with both ath and wi. I do have pccard_ifconfig=DHCP in my rc.conf. Aha! I added this, and it now works(tm). Although I'd like to tell it NOT to config the onboard rl0 interface. Will ifconfig_rl0=NO do that? Maybe you have a second dhclient running. Nope. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
rpc.ypxfrd(8)
Is there anybody out there who successfully uses the rpc.ypxfrd(8) server to speed up distribution of NIS maps, either on 4.x or 5.x? I have trouble getting it to work. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: devd *NOT* called on wi0 insert?
--On Friday, September 05, 2003 14:37:39 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Friday, September 05, 2003 13:30:03 -0600 M. Warner Losh [EMAIL PROTECTED] wrote: I do have pccard_ifconfig=DHCP in my rc.conf. Aha! I added this, and it now works(tm). Although I'd like to tell it NOT to config the onboard rl0 interface. Will ifconfig_rl0=NO do that? In answer to my own question, the answer is NO. So, we still need a way to do that. Also, interestingly, with the /etc/rc.d/devd script modified to start devd with the -D option, my dmesg gets wiped out. :-( -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: devd *NOT* called on wi0 insert?
In message: [EMAIL PROTECTED] Larry Rosenman [EMAIL PROTECTED] writes: : : : --On Friday, September 05, 2003 14:37:39 -0500 Larry Rosenman : [EMAIL PROTECTED] wrote: : : : : --On Friday, September 05, 2003 13:30:03 -0600 M. Warner Losh : [EMAIL PROTECTED] wrote: : : : I do have pccard_ifconfig=DHCP in my rc.conf. : Aha! I added this, and it now works(tm). : : Although I'd like to tell it NOT to config the onboard rl0 interface. : : Will ifconfig_rl0=NO do that? : In answer to my own question, the answer is NO. : : So, we still need a way to do that. You can use tell devd.conf to say that all attachemnts to the pci bus do nothing. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd *NOT* called on wi0 insert?
--On Friday, September 05, 2003 14:37:04 -0600 M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] Larry Rosenman [EMAIL PROTECTED] writes: : : : --On Friday, September 05, 2003 14:37:39 -0500 Larry Rosenman : [EMAIL PROTECTED] wrote: : : : : --On Friday, September 05, 2003 13:30:03 -0600 M. Warner Losh : [EMAIL PROTECTED] wrote: : : : I do have pccard_ifconfig=DHCP in my rc.conf. : Aha! I added this, and it now works(tm). : : Although I'd like to tell it NOT to config the onboard rl0 interface. : : Will ifconfig_rl0=NO do that? : In answer to my own question, the answer is NO. : : So, we still need a way to do that. You can use tell devd.conf to say that all attachemnts to the pci bus do nothing. Could I impose on you to give me the magic? I'm confused and want to learn. LER Warner -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Fri, Sep 05, 2003 at 07:50:24PM +0100, Stuart Walsh wrote: On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: Hi again chaps, I've been working on other things lately, including getting ready to move house and looking after my 3 month old daughter :) but recently I've Changing nappies? ;) took up trying to get this driver working again. If anyone is interested in helping out, could they give http://stu.bash.sh/if_sk.c and http://stu.bash.sh/if_skreg.h a try and let me know what output you get. I'm only really interested in what happens after the MAC gets printed so don't go to too much trouble to get the exact info. Just plonk the files in /usr/src/sys/pci over the top of the old ones. Thanks to anyone who helps out. OK.. what it does is as follows: - print ethernet address - then it prints: Yukon chip detected Phy type 4 adr 0 initialising yukon device phy reset set mac reset set mac reset clear mac reset set hang This all on an Asus P4P800. Obviously a copper based NIC, without cable connected in this case. hth Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rpc.ypxfrd(8)
In the last episode (Sep 05), Ruslan Ermilov said: Is there anybody out there who successfully uses the rpc.ypxfrd(8) server to speed up distribution of NIS maps, either on 4.x or 5.x? I have trouble getting it to work. Seems to work for me, although it might be failing and falling back to a regular ypxfr for all I know. If I run rpc.ypxfrd on the server, then run chfn and change my name, lastcomm shows that rpc.ypxfrd forks a couple times, and the client's map is updated. -current server, 4.1 client. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New kernels won't boot
On Fri, 5 Sep 2003, Lukas Ertl wrote: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2387622296 Hz quality 800 Timecounters tick every 10.000 msec And then... silence. Any ideas? My sources indicate that you should try upgrading the system BIOS. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rpc.ypxfrd(8)
On Fri, 5 Sep 2003 22:47:02 +0300 Ruslan Ermilov [EMAIL PROTECTED] wrote: Is there anybody out there who successfully uses the rpc.ypxfrd(8) server to speed up distribution of NIS maps, either on 4.x or 5.x? I have trouble getting it to work. Cheers, -- Ruslan ErmilovSysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer I recently switched NIS master to 4.8-STABLE, and had some trouble. To make long story short, I did: 1. edit /var/yp/ypservers to make it single array of slaves. For example, server1 server1 server2 server2 server3 server3 ... to server1 server2 server3 ... 2. cd /var/yp make Qurious, which of ypinit, yppoll is to be blamed. horio shoichi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Lock order reversal
Has anyone seen this before? Sep 5 15:06:02 rdaver kernel: lock order reversal Sep 5 15:06:02 rdaver kernel: 1st 0xcf33ba34 filedesc structure (filedesc structure) @ kern/sys_generic.c:895 Sep 5 15:06:02 rdaver kernel: 2nd 0xc054c640 Giant (Giant) @ fs/specfs/spec_vnops.c:372 I've been getting this regularly. The above error was generated on a CVSUP from last night, but has occured on everything I've tried in 5.1. I'm running about 3T of disk, split into roughly 600G chunks for the bulk, and smaller volumes for /, /usr, etc. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP/STATUS: network locking
I've committed a number of changes to lock the middlware parts of the network subsystem. There's still more to come; I'm moving slowly to insure each batch gets exposure. All the pending changes can be found at: http://www.freebsd.org/~sam The major changes that will go in next week are: bridge, dummynet, ipfw, multicast routing (mroute), and the routing table (rtentry). I've been running with all these mods on a variety of machines (desktop, NFS server, laptop, firewall) for weeks but testing everything is difficult so don't be surprised if you encounter issues like lock order reversals. Each patch is pretty much independent so if you regularly use say dummynet then it would be useful to try the patch and send me feedback. In the above directory you'll also find the first tangible benefit of this work: netisr.patch contains changes to push Giant up one level. Note however that unless the network drivers mark their interrupt handlers MPSAFE you're not really going to exercise the locking. I've been running em, sis, fxp, wi, and ath drivers this way for several months with no ill effects (except for a problem running Atheros hardware in HostAP mode). Many other drivers are locked and appear ready to run MPSAFE. Shortly I'll have Giant pushed all the way up through the INET protocols. When that happens it'll be time to remove Giant from the socket layer and lock IPv6 and UNIX domain sockets. At some point we'll need to switch over to a non-Giant top half; at that point drivers and protocols that are not properly locked will need help or be left behind. Note that the current plan is to NOT commit any changes to remove Giant from the socket layer until after 5.2. Folks interested in trying this stuff will need to track the work in perforce or apply patches that I'll make available at stable points. If folks want to talk about this work at BSDCon I'll be around Wed-Fri. I'll also be at the developers summit on Saturday. Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
device_probe_and_attach: atkbd0 attach returned 6
Hey, I saw this post on http://lists.freebsd.org/pipermail/freebsd-current/2003-May/002982.html on Mon May 12 22:36:58 PDT 2003. I am having problems with my nic card. I also got the device_probe_and_attach: atkbd0 attach returned 6 exept, of course, mine was with the nic card - not the keyboard so the driver was dl0 not atkbd0. Anyway the point is, did you fix this? Do you know what the message means and what causes it? I'm just looking for somthing to point me in the right direction. I've looked around and I haven't been able to find too many resources. I hope you can give me some pointers, but if not don't worry. Thanks for taking the time to read this. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Panic, Trap 12
I am experiences some difficulty upgrading from 5.1-RELEASE to -CURRENT. I have a Sony VAIO GRX570(P4 1.6GHz, 512MB, DVDROM/CD-RW). I installed 5.1-R and CVSup'd -CURRENT, did I make world, with no problems. On reboot I get: Fatal trap 12: page fault while in kernel mode Fault virtual address= 0xdeadc0de Fault code= supervisor write, page not present Instruction pointer=0x8:0xc0 Stack pointer= 0x10:0xc077e7b8 Frame pointer= 0x10:0xc077e7d8 Code segment= base 0x0, limit 0xf, type 0x1b DBL0, pres 1, def32, gran 1 Processor eflags= interrupt enabled resume, IOPL = 0 Current process= 0 (swapper) Kernel type 12 trap, code = 0 Stopped at ithread_add_handler+0x143 movl %ebx,0(%eax) Please note that this happens directly after inphy on boot. Any ideas how to fix this error? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: device_probe_and_attach: atkbd0 attach returned 6
On Fri, 5 Sep 2003 20:55:39 -0700 peter [EMAIL PROTECTED] wrote: Hey, I saw this post on http://lists.freebsd.org/pipermail/freebsd-current/2003-May/002982.html on Mon May 12 22:36:58 PDT 2003. I am having problems with my nic card. I also got the device_probe_and_attach: atkbd0 attach returned 6 exept, of course, mine was with the nic card - not the keyboard so the driver was dl0 not atkbd0. Anyway the point is, did you fix this? Do you know what the message means and what causes it? I'm just looking for somthing to point me in the right direction. I've looked around and I haven't been able to find too many resources. I hope you can give me some pointers, but if not don't worry. Thanks for taking the time to read this. I worked around this by manually setting (in BIOS) the IRQ for the PCI slot that NIC was sitting on. Auto mode was giving the NIC IRQ 9 and I set it manually to IRQ 10. -- Cogeco ergo sum pgp0.pgp Description: PGP signature
Important changes to the .org tld today. (fwd)
FYI, Doug -- Forwarded message -- Date: Fri, 05 Sep 2003 06:03:15 -0700 From: Rodney Joffe [EMAIL PROTECTED] Organization: UltraDNS Corp Subject: Important changes to the .org tld today. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During the root zone (.) update later today, specifically with root zone serial number 2003090501, the entries for .org will me modified. The current zone entry contains the following authoritative nameservers for the .org tld: org.2D IN NSA7.NSTLD.COM. org.2D IN NSL7.NSTLD.COM. org.2D IN NSG7.NSTLD.COM. org.2D IN NSF7.NSTLD.COM. org.2D IN NSM5.NSTLD.COM. org.2D IN NSTLD1.ULTRADNS.NET. org.2D IN NSTLD2.ULTRADNS.NET. org.2D IN NSJ5.NSTLD.COM. org.2D IN NSI5.NSTLD.COM. org.2D IN NSC5.NSTLD.COM. org.2D IN NSE5.NSTLD.COM. Effective with the 2003090501 load, the entry will reflect the removal of the Verisign NSTLD.COM nameservers. The zone entry will therefore contain the following only: org.2D IN NSTLD1.ULTRADNS.NET. org.2D IN NSTLD2.ULTRADNS.NET. If you have the 9 ??.NSTLD.COM nameservers cached or hard coded in any way, you may wish to flush your cache or modify your nameservers in the near future to avoid any inconsistent or stale data, and you may want to make your system administrators, NOCs and customer support groups aware of the changes. The .org zone file will continue to be pushed to the Verisign nameservers for a short period of time. However due to the fact that the UltraDNS nameservers publish and propagate zone changes globally within 5 minutes, rather than the twice daily update schedule of the Verisign nameservers, answers from the NSTLD.COM nameservers may be out of date and inconsistent with the actual SOA for up to 24 hours after a change is accepted by the Public Interest Registry (PIR.org). Any questions or concerns regarding this change should be directed to the PIR (http://www.pir.org). Sincerely, Rodney Joffe CTO and Chairman UltraDNS Corp. http://www.ultradns.com -BEGIN PGP SIGNATURE- Version: PGP 8.0.2 iQA/AwUBP1iJJEa3pZtqJ3OwEQJvwACdHkKdAW3TqDSpOJVoguhFAx0YebwAnAw9 c6fW3PeXcgvjwhvLIPaxRVEW =+m9c -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
