Re: ext2fs support for writing - what's the verdict?
Jordan Hubbard writes: That's a nice idea and may work in my particular case, but this is also the out-of-box configuration for Red Hat and most Linux-to-FreeBSD users wouldn't know a tune2fs if it snuck up and bit them on the ass in broad daylight. How hard would it be to support sparse superblocks? Just FYI, Mandrake 7.1 does the same thing out of the box. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TI1225 CardBus controller
We have a lot of Lucent WaveLan (Orinoco) installations, primarily using the ISA-to-PCMCIA adapters. We would urgently need a PCI-to-PCMCIA solution and Lucent provides the adapters which use a TI1225 chip. Unfortunatelly the legacy FreeBSD pccard driver has problems with this chip. I'm willing to put some work into making it work. I know about Warner's CardBus effort, but it's going too slow for my taste because I need a solution now (meaning this month). From reading the mailing list archives, I figured that the TI1225 driver does actually work in some laptops, because the BIOS does some magic initialization which the driver misses when running on a non-laptop box. Could somebody who has a laptop with a TI1225 PC card controller chip please contact me? My idea currently is to print out the values of important chip registers on a laptop and on a desktop and check what the differences are. This way I may be able to find out what the driver is missing out in the initialization. Anyone with knowledge of the issues involved is welcomed to contact me as well with as much information as possible - because my idea could be totally wrong for example. I have the datasheet for the TI1225 and am looking at it, but it's just too much for a newbie like me. I think comparing the setup of registers on a working and a non-working configuration could be a possible way to solve the problem, even for a newbie :) Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with kthread_exit() and SMPng
Hello,
Currently I'm trying to make KLD which uses kernel threads
unloadable under recent -current. The prototype of functions looks like
this:
void
my_thread(void*arg)
{
while(wearewanted) {
do_something();
tsleep();
}
exited = 1;
kthread_exit(0);
}
void
my_unload()
{
wearewanted = 0;
while (!exited)
tsleep(1sec);
}
my_unload() function called from the module unload event which
issued from the kldunload() syscall.
Unfortunately, kernel panics in the mtx_exit_hard() function.
After some examination I've found that two fields in the Giant mutex
structure set to unexpected values:
empty mtx_blocked for mutex Giant
mtx_contested not in any list for mutex Giant
These messages printed by added diagnostics code. With this patch
(see attachment) it is possible to load and unload KLD without any
problems on UP machine except that the above messages printed. However,
I'm don't know if they are correct. (btw, 4.1 doesn't have this problem).
Any ideas why this happened and how to fix it ?
--
Boris Popov
http://www.butya.kz/~bp/
Index: synch_machdep.c
===
RCS file: /home/ncvs/src/sys/i386/i386/synch_machdep.c,v
retrieving revision 1.5
diff -u -r1.5 synch_machdep.c
--- synch_machdep.c 2000/10/04 01:20:49 1.5
+++ synch_machdep.c 2000/10/05 10:23:33
@@ -355,10 +355,16 @@
p = CURPROC;
p1 = TAILQ_FIRST(m-mtx_blocked);
MPASS(p-p_magic == P_MAGIC);
- MPASS(p1-p_magic == P_MAGIC);
- TAILQ_REMOVE(m-mtx_blocked, p1, p_procq);
+ if (p1) {
+ MPASS(p1-p_magic == P_MAGIC);
+ TAILQ_REMOVE(m-mtx_blocked, p1, p_procq);
+ } else
+ printf("empty mtx_blocked for mutex %s\n",
+m-mtx_description);
if (TAILQ_EMPTY(m-mtx_blocked)) {
- LIST_REMOVE(m, mtx_contested);
+ if (m-mtx_contested.le_prev != NULL)
+ LIST_REMOVE(m, mtx_contested);
+ else
+ printf("mtx_contested not in any list for mutex %s\n",
+m-mtx_description);
atomic_cmpset_int(m-mtx_lock, m-mtx_lock,
MTX_UNOWNED);
CTR1(KTR_LOCK, "mtx_exit: 0x%p not held", m);
@@ -373,12 +379,15 @@
if (pri p-p_nativepri)
pri = p-p_nativepri;
SET_PRIO(p, pri);
- CTR2(KTR_LOCK, "mtx_exit: 0x%p contested setrunqueue 0x%p",
- m, p1);
- p1-p_blocked = NULL;
- p1-p_stat = SRUN;
- setrunqueue(p1);
- if ((type MTX_NOSWITCH) == 0 p1-p_priority pri) {
+ if (p1) {
+ CTR2(KTR_LOCK, "mtx_exit: 0x%p contested setrunqueue 0x%p",
+ m, p1);
+ p1-p_blocked = NULL;
+ p1-p_stat = SRUN;
+ setrunqueue(p1);
+ }
+ if ((type MTX_NOSWITCH) == 0
+ (p1 == NULL || p1-p_priority pri)) {
#ifdef notyet
if (p-p_flag (P_ITHD | P_SITHD)) {
ithd_t *it = (ithd_t *)p;
Re: #include struct.h in sys/queue.h
On Tue, 3 Oct 2000, Jeffrey Hsu wrote: I think struct.h should have been removed when offsetof() became standard. At last count, offsetof() is defined in 11 different places in the kernel: alpha/alpha/machdep.c, line 234 ... Some other places include stddef.h. If we unify it in one header file, I'd be happy to use that for STAILQ_LAST(). machine/ansi.h is a good place for it now. strbase() is now used in sys/queue.h. It is easy to implement directly using offsetof(). Unfortunately, if it is implemented using offsetof(), then sys/queue.h will depend on stddef.h. So, what's the correct solution? I'm currently using the following. This avoids a bug in fldoff(): casting to int is wrong and causes warnings on alphas. I use a cast to __uintptr_t since casting to size_t is normally right (offsetof() depends on it), and __uintptr_t is normally equivalent to size_t and is easier to get at. --- diff -c2 queue.h~ queue.h *** queue.h~Fri Aug 4 21:38:55 2000 --- queue.h Thu Oct 5 21:22:51 2000 *** *** 38,43 #define _SYS_QUEUE_H_ - #include struct.h - /* * This file defines five types of data structures: singly-linked lists, --- 38,41 *** *** 224,231 } while (0) #define STAILQ_LAST(head, type, field) \ ! (STAILQ_EMPTY(head) ? \ ! NULL : \ ! strbase(type, (head)-stqh_last, field)) #define STAILQ_NEXT(elm, field) ((elm)-field.stqe_next) --- 222,239 } while (0) + /* + * XXX auxiliary macros for STAILQ_LAST() adapted from offsetof() in + * stddef.h and strbase() in struct.h. + */ + #include machine/ansi.h + + #define __offsetof(type, member)\ + ((__uintptr_t)(((type *)0)-member)) + #define __strbase(name, addr, field)\ + ((struct name *)((char *)(addr) - __offsetof(struct name, field))) + #define STAILQ_LAST(head, type, field) \ ! (STAILQ_EMPTY(head) ? NULL :\ ! __strbase(type, (head)-stqh_last, field)) #define STAILQ_NEXT(elm, field) ((elm)-field.stqe_next) --- Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Submiting new code
Hi, How can I send a quite big submission of source code. Handbook says that I should put big part of report in to ftp.freebsd.org/pub/FreeBSD/incoming but I can't found it. Kurakin Roman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[HEADS-UP] mbuf mutex code going in...
Hello, I've just committed the mbuf-related SMPng code please see commit logs for details, and: http://people.freebsd.org/~bmilekic/mtx_journal I sincerely hope that there were little or no errors, as I've tried hard to avoid them. But this is a big diff, it's been sitting around for a while, and it covers a lot of things. So, despite 6 versions of a diff, and numerous reviews, certain things may have slipped through the cracks. Please, don't panic: just report problems and provide all necessary details. I'll do my best to take care of all issues as soon as possible, if necessary. :-) If all goes well, more commits, some adding important functionality, to follow... Regards, Bosko Milekic [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: page fault while in kernel mode
Hi Michael, Do you think you can provide us with a stack trace, at the least? This would deffinately give us something more to work with. Unfortunately, with this information, it's very difficult to pin-point the problem, as we're not certain as to what is at 0xc029e6cb, exactly. Also, is there anything particular that you notice that is happening in parallel to this? Anything special you're doing? On 3 Oct 2000, Michael Harnois wrote: The past three days or so with -current my system has been locking up solid under load. Today I was fortunate enough to have in happen when in console mode so that I could see the problem: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1 fault code = supervisor read, page not present instruction pointer = 0x8:0xc029e6cb stack pointer = 0x10:0xcefdfe18 frame pointer = 0x10:0xccfdfe20 code segment= base 0x0, limit 0x, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 2355 (procmail) trap number = 12 panic: page fault acpi0: acpi_io_pml_enable(1) = (0) acpi0: acpi_io_gpe0_enable(1) = (0) syncing disks... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis Regards, Bosko Milekic [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Submiting new code
(copied to -doc for reasons which will become clear below) The FTP server no longer accepts uploads. Use uuencode and send-pr. Many people put code submissions up on a local web site and request comments on -current or -hackers before doing this. It makes the eventual code submission much more likely to be accepted. Docs folks, would one of you like to whack the offending statement from the Handbook? It looks like section 19.2.4 is the problem. (Of course, if we have a new FTP site, that would be good too. :) On Thu, Oct 05, 2000 at 05:40:51PM +0400, Kurakin Roman wrote: Hi, How can I send a quite big submission of source code. Handbook says that I should put big part of report in to ftp.freebsd.org/pub/FreeBSD/incoming but I can't found it. Kurakin Roman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TI1225 CardBus controller
On Thu, 5 Oct 2000 11:37:02 +0200 (CEST), Blaz Zupan [EMAIL PROTECTED] said: From reading the mailing list archives, I figured that the TI1225 driver does actually work in some laptops, because the BIOS does some magic initialization which the driver misses when running on a non-laptop box. It's not necessarily just because of what the BIOS does. I am of the belief that the PCI card only works under the CardBus programming model. The reason should be obvious: the IRQ lines that the PC-Card interface needs aren't available on the PCI connector. When that chip is used in a laptop, it's connected directly to the PIIX so that it can get the full ISA functionality it needs in order to implement the Intel PCIC programming model. -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
Re: Submiting new code
Thank you. Michael Lucas wrote: (copied to -doc for reasons which will become clear below) The FTP server no longer accepts uploads. Use uuencode and send-pr. Many people put code submissions up on a local web site and request comments on -current or -hackers before doing this. It makes the eventual code submission much more likely to be accepted. Docs folks, would one of you like to whack the offending statement from the Handbook? It looks like section 19.2.4 is the problem. (Of course, if we have a new FTP site, that would be good too. :) On Thu, Oct 05, 2000 at 05:40:51PM +0400, Kurakin Roman wrote: Hi, How can I send a quite big submission of source code. Handbook says that I should put big part of report in to ftp.freebsd.org/pub/FreeBSD/incoming but I can't found it. Kurakin Roman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: TI1225 CardBus controller
Blaz Zupan wrote: Could somebody who has a laptop with a TI1225 PC card controller chip please contact me? My idea currently is to print out the values of important chip registers on a laptop and on a desktop and check what the differences are. This way I may be able to find out what the driver is missing out in the initialization. The Dell Inspiron 7500 has one.. works just fine.. pcic-pci0: TI PCI-1225 PCI-CardBus Bridge at device 4.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC p ci int + CSC serial isa irq] pcic-pci1: TI PCI-1225 PCI-CardBus Bridge at device 4.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC p ci int + CSC serial isa irq] ... pccard: card inserted, slot 0 sio4 at port 0x2e8-0x2ef irq 9 slot 0 on pccard0 sio4: type 16550A -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Looking for Patches
hi, anyone knows where to find a MYSQL patch for cistron? cheers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: ATA DMA support is broken
On 03-Oct-00 Valentin Chopov wrote: After last changes ata DMA support is not workind and atapicd is not recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) Yes, I've currently got the last round of ATA commits backed out in sys/dev/ata on my machine as well. The problem seems to be that the atapci driver is not attaching the ata child devices. Normal dmesg output: atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB TOSHIBA MK1814GAV [35152/16/63] at ata0-master UDMA33 Bad dmesg output: atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 7.1 on pci0 -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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: TI1225 CardBus controller
It doesn't work for cardbus. = | 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, 5 Oct 2000, Julian Elischer wrote: Blaz Zupan wrote: Could somebody who has a laptop with a TI1225 PC card controller chip please contact me? My idea currently is to print out the values of important chip registers on a laptop and on a desktop and check what the differences are. This way I may be able to find out what the driver is missing out in the initialization. The Dell Inspiron 7500 has one.. works just fine.. pcic-pci0: TI PCI-1225 PCI-CardBus Bridge at device 4.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC p ci int + CSC serial isa irq] pcic-pci1: TI PCI-1225 PCI-CardBus Bridge at device 4.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC p ci int + CSC serial isa irq] ... pccard: card inserted, slot 0 sio4 at port 0x2e8-0x2ef irq 9 slot 0 on pccard0 sio4: type 16550A -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: TI1225 CardBus controller
In message [EMAIL PROTECTED] Blaz Zupan writes: : We have a lot of Lucent WaveLan (Orinoco) installations, primarily using the : ISA-to-PCMCIA adapters. We would urgently need a PCI-to-PCMCIA solution and : Lucent provides the adapters which use a TI1225 chip. Unfortunatelly the : legacy FreeBSD pccard driver has problems with this chip. I'm willing to put : some work into making it work. I know about Warner's CardBus effort, but it's : going too slow for my taste because I need a solution now (meaning this : month). : : From reading the mailing list archives, I figured that the TI1225 driver does : actually work in some laptops, because the BIOS does some magic initialization : which the driver misses when running on a non-laptop box. The TI-1225 works in a lot of laptops. The problem is that the pci cards don't have the "normal" cheater connection to the south bridge to do PCI based interrupts. : Anyone with knowledge of the issues involved is welcomed to contact me as well : with as much information as possible - because my idea could be totally wrong : for example. The problem is that FreeBSD needs to be able to route the interrupts to the pci bus using PCIBIOS (on i386, maybe others) but doesn't have a good interface for that. You would have to implement that infrastructure, or flesh out one of the partially implemented versions floating around and then fix the pcic driver to somehow know that it has to route the interrupts as well as just establishing them. If you'd like a less vague description, and are willing to work on it please let me know. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA DMA support is broken
It seems John Baldwin wrote: On 03-Oct-00 Valentin Chopov wrote: After last changes ata DMA support is not workind and atapicd is not recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) Yes, I've currently got the last round of ATA commits backed out in sys/dev/ata on my machine as well. The problem seems to be that the atapci driver is not attaching the ata child devices. Normal dmesg output: atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB TOSHIBA MK1814GAV [35152/16/63] at ata0-master UDMA33 Bad dmesg output: atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 7.1 on pci0 I fixed this ~20 hours after that commit, blunder on my part, sorry... Use ata-all.c rev 1.73 or later... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: TI1225 CardBus controller
In message [EMAIL PROTECTED] Garrett Wollman writes: : On Thu, 5 Oct 2000 11:37:02 +0200 (CEST), Blaz Zupan [EMAIL PROTECTED] said: : : From reading the mailing list archives, I figured that the TI1225 : driver does actually work in some laptops, because the BIOS does : some magic initialization which the driver misses when running on a : non-laptop box. : : It's not necessarily just because of what the BIOS does. I am of the : belief that the PCI card only works under the CardBus programming : model. I don't think that's the case. This card would work fine under the legacy model if you can have the interupts routed correctly as well as all the other stuff it does. The interrupt routing really is the only issue here, at least from my reading of the data sheets and such. there's also a side issue of level vs pulse interrupts that you might run into. You can still use the legacy interface to talk to card, modulo one or two pci config space register settings (iirc). Maybe this is what you mean. : The reason should be obvious: the IRQ lines that the PC-Card : interface needs aren't available on the PCI connector. When that chip : is used in a laptop, it's connected directly to the PIIX so that it : can get the full ISA functionality it needs in order to implement the : Intel PCIC programming model. This part is correct. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Problems with kthread_exit() and SMPng
Ugh, my mail client ate my reply, lemme try again.
On 05-Oct-00 Boris Popov wrote:
Hello,
Currently I'm trying to make KLD which uses kernel threads
unloadable under recent -current. The prototype of functions looks like
this:
void
my_thread(void*arg)
{
while(wearewanted) {
do_something();
tsleep();
}
exited = 1;
kthread_exit(0);
}
You need Giant before calling kthread_exit().
void
my_unload()
{
wearewanted = 0;
while (!exited)
tsleep(1sec);
}
my_unload() function called from the module unload event which
issued from the kldunload() syscall.
Unfortunately, kernel panics in the mtx_exit_hard() function.
After some examination I've found that two fields in the Giant mutex
structure set to unexpected values:
It should have died much earlier if you had INVARIANTS turned on. :( It
looks like you are releasing a mutex you probably do not own because
cpu_exit() (called by exit1() - exit() - kthread_exit()) releases Giant
as one of its final tasks.
empty mtx_blocked for mutex Giant
mtx_contested not in any list for mutex Giant
These messages printed by added diagnostics code. With this patch
(see attachment) it is possible to load and unload KLD without any
problems on UP machine except that the above messages printed. However,
I'm don't know if they are correct. (btw, 4.1 doesn't have this problem).
This patch is bogus I'm afraid. A contested mutex should always have a
process waiting to grab it when it is released.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/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
HEADS UP: ports layout restructuring happening this weekend
Hello world, As those of you who have been following the ports list may know, we are changing the ports skeletons' layout in an effort to reduce the number of small directories and significantly speed up operation on the ports tree. This should especially help operations such as "CVS update", and will also reduce the number of i-nodes required to keep the whole tree around. The conversion will be done this weekend. It will only take a day or two. There should be no functional changes that you can see after the conversion (minus the bugs I may introduce, of course). However, during the conversion, the tree will be in an inconsistent state and attempts to use the tree will fail in most weird ways, so it is recommended that you cvsup the tree on or before Friday and do not cvsup again until I post an "all clear" message. Thanks, -PW To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -CURRENT clock deviation
On 04-Oct-00 Alain Thivillon wrote: I have noticed that -CURRENT (build last week) is subject to a very high clock deviation: I'm about to commit some changes to the clock interrupt code on the x86, try again once those are in place. I run -CURRENT on a laptop, it seems that last commit in idle loop (the one replacing loop by HLT and lowering temperature) broke the clock. Hmm, this shouldn't really break it. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/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: -CURRENT clock deviation
On 04-Oct-00 Alain Thivillon wrote: I have noticed that -CURRENT (build last week) is subject to a very high clock deviation: I run -CURRENT on a laptop, it seems that last commit in idle loop (the one replacing loop by HLT and lowering temperature) broke the clock. Hmm, this shouldn't really break it. I'm also a little surprised about that, but the whole "idle thread" concept is up for some major revision soon anyway, with APCI promising to substantially change the way we view "idleness" in a lot of cases. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Problems with kthread_exit() and SMPng
On Thu, 5 Oct 2000, John Baldwin wrote: You need Giant before calling kthread_exit(). Ok. After some examination I've found that two fields in the Giant mutex structure set to unexpected values: It should have died much earlier if you had INVARIANTS turned on. :( It looks like you are releasing a mutex you probably do not own because cpu_exit() (called by exit1() - exit() - kthread_exit()) releases Giant as one of its final tasks. This is probably the bug somewhere in the diagnostic code. I have INVARIANTS/INVARIANT_SUPPORT/DIAGNOSTIC turned on and UP machine just panics in the mtx_exit_hard() while SMP machine silently reboots :( This patch is bogus I'm afraid. A contested mutex should always have a process waiting to grab it when it is released. Yes, it should be bogus. But diagnostic is rather useful :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in ufs_extattr_uepm_destroy()
I'm getting a panic in ufs_extattr_uepm_destroy() because in ffs_vfsops.c it is being called (line 788) with ump NULL: ufs_extattr_uepm_destroy(ump-um_extattr); Of course disabling FFS_EXTATTR gets rid of this:) -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
boot problem with Mylex DAC960 - help ?
I installed 4.1.1 on an Intel ISP 2150 with a Mylex AcceleRAID 250. The fireware on the controller is 4.06 . After install and while it starts to boot I get: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 636kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Mon Sep 25 23:47:21 GMT 2000) Loading /boot/defaults/loader.conf | It hangs right there. Anyone run into this and resolve it? According to the mailing list archives, I should be able to boot off the Mylex. Thanks. - mz -- matthew zeier - "There ain't no rules around here. We're trying to accomplish something." - Thomas Edison To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot problem with Mylex DAC960 - help ?
I don't know of any problems related to this at this time. Make sure you have the latest BIOS from Intel for the ISP2150. I installed 4.1.1 on an Intel ISP 2150 with a Mylex AcceleRAID 250. The fireware on the controller is 4.06 . After install and while it starts to boot I get: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 636kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Mon Sep 25 23:47:21 GMT 2000) Loading /boot/defaults/loader.conf | It hangs right there. Anyone run into this and resolve it? According to the mailing list archives, I should be able to boot off the Mylex. Thanks. - mz -- matthew zeier - "There ain't no rules around here. We're trying to accomplish something." - Thomas Edison To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
