ACPI glitch
Just a FYI: #2 0xc01f0231 in panic (fmt=0xc031c8c0 "malloc(M_WAITOK) in interrupt context") at ../../kern/kern_shutdown.c:570 #3 0xc01ea192 in malloc (size=28, type=0xc03465c0, flags=0) at ../../kern/kern_malloc.c:151 #4 0xc016a4ce in AcpiOsQueueForExecution (Priority=2, Function=0xc0166e98 EcGpeQueryHandler, Context=0xc1096e40) at ../../dev/acpica/Osd/OsdSchedule.c:68 #5 0xc0167025 in EcGpeHandler (Context=0xc1096e40) at ../../dev/acpica/acpi_ec.c:471 #6 0xc01446a4 in AcpiEvGpeDispatch (GpeNumber=9) at ../../contrib/dev/acpica/Subsystem/Events/evevent.c:913 #7 0xc01444fe in AcpiEvGpeDetect () at ../../contrib/dev/acpica/Subsystem/Events/evevent.c:779 #8 0xc0145a7d in AcpiEvSciHandler (Context=0x0) at ../../contrib/dev/acpica/Subsystem/Events/evsci.c:185 #9 0xc02d3fee in ithd_loop (dummy=0x0) at ../../i386/isa/ithread.c:188 Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB problems
Hi, I cannot get the USB interface to work on my ASUS L7300G Laptop with -CURRENT. I have attached an excerpt of the message file and the section of the config file dealing with USB. Any hints? messages: Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci0: Intel 82443MX USB controller port 0x1c00-0x1c1f irq 11 at device 7.2 on pci0 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci_run: setting run=0 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci_run: done cmd=0x0 sts=0x20 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci_run: setting run=1 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci_run: done cmd=0x81 sts=0x0 Jan 23 10:01:22 tybalt /boot/kernel/kernel: usb0: Intel 82443MX USB controller on uhci0 Jan 23 10:01:22 tybalt /boot/kernel/kernel: usb0: USB revision 1.0 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhub0: 2 ports with 2 removable, self powered Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci_waitintr: timeout Jan 23 10:01:22 tybalt /boot/kernel/kernel: usbd_transfer_cb: short transfer 08 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci_waitintr: timeout Jan 23 10:01:22 tybalt /boot/kernel/kernel: usbd_transfer_cb: short transfer 08 Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhci_waitintr: timeout Jan 23 10:01:22 tybalt /boot/kernel/kernel: usbd_transfer_cb: short transfer 08 Jan 23 10:01:22 tybalt /boot/kernel/kernel: usbd_new_device: addr=2, getting first desc failed Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhub_explore: usb_new_device failed, error=SHORT_XFER Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhub0: device problem, disabling port 1 config: # USB support device uhci# UHCI PCI-USB interface device usb # USB Bus (required) device ugen# Generic device uhid# "Human Interface Devices" device ums # Mouse options UHCI_DEBUG options USB_DEBUG options UGEN_DEBUG options UHID_DEBUG options UHUB_DEBUG options UMS_DEBUG Thanks -Thorsten To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB problems
Thorsten Greiner wrote: Hi, I cannot get the USB interface to work on my ASUS L7300G Laptop with -CURRENT. I have attached an excerpt of the message file and the section of the config file dealing with USB. Any hints? messages: Jan 23 10:01:22 tybalt /boot/kernel/kernel: usbd_transfer_cb: short transfer 08 Jan 23 10:01:22 tybalt /boot/kernel/kernel: usbd_new_device: addr=2, getting first desc failed Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhub_explore: usb_new_device failed, error=SHORT_XFER Jan 23 10:01:22 tybalt /boot/kernel/kernel: uhub0: device problem, disabling port 1 Yes, I have the same problem. Apparently there is some problem with reading the header information that requires a reset to be issued between the two reads. Windows does the reset, and the USB maintainer was wondering why.. Now we know. :-] No, there is no known fix or workaround yet. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Why would my IRQs suddenly move?
After installing a fresh cvsup last Sunday, I find that my usb printer quit working. Some investigation shows that this is because the uhci and fxp are now on the same IRQ. This hasn't been a problem previously. I haven't made any hardware changes in quite a while, and haven't mucked around with the BIOS either. Anyone got a clue as to why the IRQ would change? Is there anything in FreeBSD that could change it? Thanx, mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
world build broken in -current as of yesterday
=== usr.bin/vmstat cc -O -pipe -I/usr/src/usr.bin/vmstat/../../sys -I/usr/obj/usr/src/i386/usr/in clude -c /usr/src/usr.bin/vmstat/vmstat.c /usr/src/usr.bin/vmstat/vmstat.c:483: warning: `pgtok' redefined /usr/obj/usr/src/i386/usr/include/machine/param.h:166: warning: this is the loca tion of the previous definition /usr/src/usr.bin/vmstat/vmstat.c: In function `dozmem': /usr/src/usr.bin/vmstat/vmstat.c:907: structure has no member named `znext' *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc messages
On a current SMP box running a kernel from this morning I see messages from the ahc driver I haven't seen before. The machine keeps on running though. Should I worry about them or back down to kernel of yesterday? Hmmm. Can you add a call to "ahc_dump_card_state(ahc);" after the "WARNING" printf in aic7xxx.c? I'm trying to reproduce this here as well. I don't know what I've changed that could cause the qoutfifo to become confused. How many drives do you have on the controller? -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: make -j 128 world hang....
On 23-Jan-01 Poul-Henning Kamp wrote:
I can still stall my 2xPII/350 machine with a make -j 128 world,
but it is slightly different now I think: I can break into ddb.
This machine is a ahc/scsi machine, so I don't know if this is
really SMP or Justins recent changes...
Poul-Henning
Ok, the problem children here are the 'allproc' waiters, which are waiting on
the allproc lock. I have had this lockup occur once so far. It appears to be
a deadlock in the lockmgr (surprise, suprise). When I had this, the allproc
lockmgr lock has 1 pending exclusive lock and 4 pending exclusive locks, and 1
existing shared lock. However, the actual lockmgr struct itself thought it had
1 existing shared lock and 5 pending shared locks. *sigh* I tried to dig
around and determined that my smp_hlt.patch had made it worse because cpu0 had
basically HLT'd and never been woken up, and cpu1 was spinning forever in
lockmgr in the atkbd0 ithread. I got no farther than that, however:
55818 cdc1ba80 cdc6c0000 55775 16280 004006 3 allproc c02e08a0 cc
Exclusive lock for wait4() or exit1(). I think exit1().
13 cbc73400 cc4c10000 0 0 00020c 3 allproc c02e08a0 swi6:
clock
12 cbc73620 cc4bf0000 0 0 000204 3 allproc c02e08a0 swi1:
net
These are both shared lock waiters. The fact that softclock() is blocked is
why the machine "locks up". It is blocked in schedcpu(), and no timeouts are
being called.
I have a vmcore and kernel.debug and have futzed around in gdb with them for a
while but don't know why it is locked up. IIRC, the atkbd thread was stuck
here:
/*
* This is the waitloop optimization, and note for this to work
* simple_lock and simple_unlock should be subroutines to avoid
* optimization troubles.
*/
static int
apause(struct lock *lkp, int flags)
{
#ifdef SMP
int i, lock_wait;
#endif
if ((lkp-lk_flags flags) == 0)
return 0;
#ifdef SMP
for (lock_wait = LOCK_WAIT_TIME; lock_wait 0; lock_wait--) {
mtx_exit(lkp-lk_interlock, MTX_DEF);
for (i = LOCK_SAMPLE_WAIT; i 0; i--)
if ((lkp-lk_flags flags) == 0)
break;
mtx_enter(lkp-lk_interlock, MTX_DEF);
if ((lkp-lk_flags flags) == 0)
return 0;
}
#endif
return 1;
}
If you want some fun, stick KTR and KTR_EXTEND in your kernel. Then, before
you start your world, do:
sysctl -w debug.ktr.mask=0x1008
To log process switches (0x1000) and mutex ops (8). When you break into ddb,
you can use 'tbuf' to display the first entry in the log buffer, and 'tnext' to
display the next entry. Then tnext again, etc. If you can get a core dump (it
worked for me on my dual 200 at least), then I have gdb macros that allow you
to dump the KTR logs in gdb easily. As for a fix, Jason Evans has implemented
and tested and will hopefully soon commit some simpler and lighter weith
shared/exclusive locks that allproc and proctree will switch to using.
However, lockmgr is used in lots of places, so it is still in our best interest
to get it fixed. Also, for the preemptive kernel, (which is very close to
running stably on UP and SMP x86 and UP alpha last I heard, just some problems
with FPU state) all these #ifdef SMP's will have to go away and we will use
mutexes in UP as well.
--
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: Why would my IRQs suddenly move?
After installing a fresh cvsup last Sunday, I find that my usb printer quit working. Some investigation shows that this is because the uhci and fxp are now on the same IRQ. Why would this cause your printer to stop working? Have you determined that this is actually the case, or did you only just notice that they're on the same IRQ? Anyone got a clue as to why the IRQ would change? Is there anything in FreeBSD that could change it? Has it actually changed? -- ... 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: ahc messages
On a current SMP box running a kernel from this morning I see messages from the ahc driver I haven't seen before. The machine keeps on running though. Should I worry about them or back down to kernel of yesterday? Hmmm. Can you add a call to "ahc_dump_card_state(ahc);" after the "WARNING" printf in aic7xxx.c? I'm trying to reproduce this here as well. I don't know what I've changed that could cause the qoutfifo to become confused. How many drives do you have on the controller? There are 3 drives on the controller. Almost everything is on da0 except /usr/obj that is on da2. Releases are also built on da2. da1 is mostly idle. I have only seen it once. The first time after a reboot with the new kernel. I have now rebooted again with the same kernel and built a whole release with a squeek from ahc. Is it possible that it could have been some interaction or leftover from the previous sequencer code or something like that? I'll put ahc_dump_card_state(ahc) in. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why would my IRQs suddenly move?
Mike Smith [EMAIL PROTECTED] types: After installing a fresh cvsup last Sunday, I find that my usb printer quit working. Some investigation shows that this is because the uhci and fxp are now on the same IRQ. Why would this cause your printer to stop working? Have you determined that this is actually the case, or did you only just notice that they're on the same IRQ? I don't know why it would cause the printer to stop working. I didn't just notice that the IRQs were the same - I checked for it specifically. What I noticed was that the printer wasn't working, and lpq showed it as possibly offline. When I first installed the USB printer, I had the exact same problem - until I changed changed the hardware config so that the fxp and uhci weren't using the same IRQ. That's why I checked for this case. Anyone got a clue as to why the IRQ would change? Is there anything in FreeBSD that could change it? Has it actually changed? I'm still trying to figure that one out. I haven't been able to get a config with the fxp and uhci on different IRQs. I've got a doctor's appointment, after which I'm going to pull the fxp and see how that goes. Thanx, mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mountd changed?
Suddenly the following error messages occur: Jan 23 07:21:02 jules mountd[435]: can't export /unused Jan 23 07:21:02 jules mountd[435]: bad exports list line /unused -maproot Jan 23 07:21:02 jules mountd[435]: could not remount /usr: Bad address Jan 23 07:21:02 jules mountd[435]: bad exports list line /usr -alldirs -maproot The file is: /unused -maproot=root vjules /usr-alldirs-maproot=root vjules vjules is just fine as an address: julian@jules:ping vjules PING vjules (192.168.254.2): 56 data bytes . CVS shows no changes to mountd recently. this /etc/exports file was working fine a couple of weeks ago. Is this related to the 'ucred' thing people have been talking about? -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: mountd changed?
On 23-Jan-01 Julian Elischer wrote: Suddenly the following error messages occur: Jan 23 07:21:02 jules mountd[435]: can't export /unused Jan 23 07:21:02 jules mountd[435]: bad exports list line /unused -maproot Jan 23 07:21:02 jules mountd[435]: could not remount /usr: Bad address Jan 23 07:21:02 jules mountd[435]: bad exports list line /usr -alldirs -maproot The file is: /unused -maproot=root vjules /usr-alldirs-maproot=root vjules vjules is just fine as an address: julian@jules:ping vjules PING vjules (192.168.254.2): 56 data bytes . CVS shows no changes to mountd recently. this /etc/exports file was working fine a couple of weeks ago. Is this related to the 'ucred' thing people have been talking about? Possibly, are your kernel and world out of sync? You should've gotten evil console messages about trying to malloc some obscene amount of memory like 128MB though. -- 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: mountd changed?
* John Baldwin [EMAIL PROTECTED] [010123 12:41] wrote: On 23-Jan-01 Julian Elischer wrote: Suddenly the following error messages occur: Jan 23 07:21:02 jules mountd[435]: can't export /unused Jan 23 07:21:02 jules mountd[435]: bad exports list line /unused -maproot Jan 23 07:21:02 jules mountd[435]: could not remount /usr: Bad address Jan 23 07:21:02 jules mountd[435]: bad exports list line /usr -alldirs -maproot The file is: /unused -maproot=root vjules /usr-alldirs-maproot=root vjules vjules is just fine as an address: julian@jules:ping vjules PING vjules (192.168.254.2): 56 data bytes . CVS shows no changes to mountd recently. this /etc/exports file was working fine a couple of weeks ago. Is this related to the 'ucred' thing people have been talking about? Possibly, are your kernel and world out of sync? You should've gotten evil console messages about trying to malloc some obscene amount of memory like 128MB though. No, he would have panic'd before seeing that. Something else is broken I think. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
uucico dies with floating point errors
I pick up my mail with uucico, because I don't want to put all the mail for my domain (read: my family) in one mailbox, and I don't have a fixed ip, so etrn won't work (easily). Anyway during the last month or so, around a third of the times it runs, it appearently dies, and I get a message saying uucico died because of a floating point error. It seems I get the mail on the next call. The box is running current of 6. jan, but I¨m pretty sure it started before that. It's using user-isdn and uucp over tcp. How would I start debugging this? There is no core files, or other error messages. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world build broken in -current as of yesterday
Nope, been fixed. I fixed it quickly and was yelled at by DES who fixed it better. === usr.bin/vmstat cc -O -pipe -I/usr/src/usr.bin/vmstat/../../sys -I/usr/obj/usr/src/i386/usr/in clude -c /usr/src/usr.bin/vmstat/vmstat.c /usr/src/usr.bin/vmstat/vmstat.c:483: warning: `pgtok' redefined /usr/obj/usr/src/i386/usr/include/machine/param.h:166: warning: this is the loca tion of the previous definition /usr/src/usr.bin/vmstat/vmstat.c: In function `dozmem': /usr/src/usr.bin/vmstat/vmstat.c:907: structure has no member named `znext' *** Error code 1 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: ahc messages
On a current SMP box running a kernel from this morning I see messages from the ahc driver I haven't seen before. The machine keeps on running though. Should I worry about them or back down to kernel of yesterday? I know you are having difficulties reproducing this, but I believe that my latest checkin corrects the problem. Please let me know if you experience any additional difficulties. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: uucico dies with floating point errors
Anyway during the last month or so, around a third of the times it runs, it appearently dies, and I get a message saying uucico died because of a floating point error. The most frequent floating point error is a divide by zero error. I'd speculate that some statistic that uucico is calculating (say bytes/second) is causing a divide by zero floating point exception. That is - unless I didn't just look at the source and not find any floats. Maybe there is an integer divide by zero in there someplace. Are you sure it isn't generating a core in the /var/spool/uucp area someplace? Are you using the taylor uucp built from the -current source tree or an older uucico (maybe a.out format?). Floating point exceptions in a program that doesn't use fp generally implies some sort of buffer overflow and code jumping into garbage that happens to look like fp code. You can rebuild taylor with debug on and try to figure out what is happening that way. You may discover that the other side is sending a field that is too long - like a system that has larger usernames than yours does etc. Good luck! Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed...
Hello! After CVSup i try to buildworld under my FreeBSD 5.0-CURRENT #0: Sat Jan 13 22:57:43 MSK 2001 box and it failed: === usr.bin/kdump cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:99: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the location of the previous definition In file included from ioctl.c:51: /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX' undeclared here (not in a function) ioctl.c: In function `ioctlname': ioctl.c:693: invalid use of `restrict' ioctl.c:693: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Any idea? -- Rgdz,/"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN [EMAIL PROTECTED]X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why would my IRQs suddenly move?
This sounds like a necessary consequence of the "PCI crapshoot." On Tue, 23 Jan 2001, Mike Meyer wrote: Mike Smith [EMAIL PROTECTED] types: After installing a fresh cvsup last Sunday, I find that my usb printer quit working. Some investigation shows that this is because the uhci and fxp are now on the same IRQ. Why would this cause your printer to stop working? Have you determined that this is actually the case, or did you only just notice that they're on the same IRQ? I don't know why it would cause the printer to stop working. I didn't just notice that the IRQs were the same - I checked for it specifically. What I noticed was that the printer wasn't working, and lpq showed it as possibly offline. When I first installed the USB printer, I had the exact same problem - until I changed changed the hardware config so that the fxp and uhci weren't using the same IRQ. That's why I checked for this case. Anyone got a clue as to why the IRQ would change? Is there anything in FreeBSD that could change it? Has it actually changed? I'm still trying to figure that one out. I haven't been able to get a config with the fxp and uhci on different IRQs. I've got a doctor's appointment, after which I'm going to pull the fxp and see how that goes. Thanx, mike -- Mike Meyer [EMAIL PROTECTED]http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. 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: Why would my IRQs suddenly move?
Mike Meyer [EMAIL PROTECTED] types: Mike Smith [EMAIL PROTECTED] types: After installing a fresh cvsup last Sunday, I find that my usb printer quit working. Some investigation shows that this is because the uhci and fxp are now on the same IRQ. Why would this cause your printer to stop working? Have you determined that this is actually the case, or did you only just notice that they're on the same IRQ? I don't know why it would cause the printer to stop working. I didn't just notice that the IRQs were the same - I checked for it specifically. What I noticed was that the printer wasn't working, and lpq showed it as possibly offline. When I first installed the USB printer, I had the exact same problem - until I changed changed the hardware config so that the fxp and uhci weren't using the same IRQ. That's why I checked for this case. FWIW, juggling the hardware so that the fxp and uhci controller aren't on the same IRQ, and the printer works. However, the fxp is now sharing IRQs with an an aic7890, and the uhci is sharing an irq with a 2940. Strange stuff. Anyone got a clue as to why the IRQ would change? Is there anything in FreeBSD that could change it? Has it actually changed? I'm still trying to figure that one out. I haven't been able to get a config with the fxp and uhci on different IRQs. I've got a doctor's appointment, after which I'm going to pull the fxp and see how that goes. And it looks like FreeBSD had nothing to do with it, other than not working sharing the fxp uhci controllers. Thanx, mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildkernel trouble ?
Hello, I'm tracking -CURRENT on my workstation around 3 months. Recently I have found that "make buildkernel" fails. Even with GENERIC. Ok, I have removed /usr/src/* and cvsupped again. Now, if I do make buildkernel KERNEL=MORDOR GENERIC kernel will be built, so I don't know how to build kernel now :-( Last cvsup was on 2000.01.23 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel trouble ?
In message [EMAIL PROTECTED] Igor Robul writes: : Hello, : I'm tracking -CURRENT on my workstation around 3 months. Recently I : have found that "make buildkernel" fails. Even with GENERIC. : Ok, I have removed : /usr/src/* and cvsupped again. Now, if I do : make buildkernel KERNEL=MORDOR : GENERIC kernel will be built, so I don't know how to build kernel now : :-( Read UPDATING: 20010122: ** WARNING ** buildkernel has been changed slightly ** WARNING ** KERNCONF replaces the variable KERNEL for buildkernel. You should update your scripts and make.conf accordingly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
