Re: port upgrade problem
Looks like nobody else expirienced this problem Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 21 Aug 2002, Maxim M. Kazachek wrote: portupgrade fails with reason (Makefile broken) on print/jadetex and x11-fonts/webfonts due to make warning: /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored When I try to make/install documentation make also shows a lot of warnings about duplicates. This only affects -CURRENT, -STABLE doesn't have this error message. So I'm afraid that it's related to -CURRENT... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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
sparc64 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- === sys/boot/sparc64/loader In file included from /usr/home/des/tinderbox/sparc64/src/sys/boot/sparc64/loader/locore.S:15: machine/asm.h:105:1: warning: __FBSDID redefined In file included from machine/asm.h:46, from /usr/home/des/tinderbox/sparc64/src/sys/boot/sparc64/loader/locore.S:15: /usr/home/des/tinderbox/sparc64/src/sys/sys/cdefs.h:247:1: warning: this is the location of the previous definition In file included from /usr/home/des/tinderbox/sparc64/src/sys/boot/sparc64/loader/main.c:25: /usr/home/des/tinderbox/sparc64/src/sys/sys/pcpu.h:37:2: #error no user-serviceable parts inside mkdep: compile failed *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/sys/boot/sparc64/loader. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/sys/boot/sparc64. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/sys/boot. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/sys. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: port upgrade problem
On Wed, 21 Aug 2002 14:51:59 +0700 (NOVST) Maxim M. Kazachek wrote: Looks like nobody else expirienced this problem /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored no, i got the same problem. some make issue i guess -- /\ http://corecode.ath.cx/#donate \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News msg42080/pgp0.pgp Description: PGP signature
Re: VM panic
What kind of value do you use for N? It looks like lately the makefiles are too aggressive when using -j, so you end up with N * N * 2 processes running simultaneously. On my -current box with 128M RAM, I used -j13 for a long time, but that runs out of swap nowadays, so I'm using -j4 which does work. My machine is a PentiumMMX/200 x 2 SMP. I'm slowly working down from -j13, and I'm now at -j5 with the same panic. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current buildworld failure on Alpha?
Wilko Bulte [EMAIL PROTECTED] wrote: ds10#make Segmentation fault (core dumped) /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/share/mk CPUTYPE=ev56 -V CPUTYPE returned non-zero status There was a time window when make -V ... was broken on 64-bit archs, i.e. it would segfault after printing the result. This has been fixed in revision 1.69 of make/main.c. FreeBSD ds10.wbnet 5.0-CURRENT FreeBSD 5.0-CURRENT #7: Sat Aug 10 19:51:27 make was fixed on August 11. -- Christian naddy Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: acpi prevents fdc to detect correctly
my kernel can't detect fdc anymore when loading acpi. does anybody else have such issues? i know that it worked with a Aug 6 or a Aug 3 kernel, this was the last time i accessed my fd0. though reverting to a -D 08/06/2002 src/sys doesn't bring the desired effect (working fdc). Hmmm, there are very few changes on ACPI between 08/06/2002 and 08/19/2002... Sorry, I have no idea. Guys, any ideas? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Solved: CURRENT and P-IV problems
Hi, As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. I've replaced everything, two - three times, the problem persisted. I also tried three motherboards, but all from the same type: Intel BD843BG with DDR 266 Ram (2100). Just for interest, I've replaced this Mobo now with an Asus P4B533-V board. All segfaults and illegal instructions are gone now. So it seems to be specific to the Intel board. BIOS update did not help. Change timing settings also not. The default settings produce these errors. It happens rarely on STABLE, often on CURRENT. What issue could this be with the Intel manufacured board ? Is it a design issue, or could it still be a FreeBSD bug ? Both Mobo's use the same i845 chipset, and use the same Ram. Can anyone who experienced those coredumps send me a exact list of used chipsets ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: port upgrade problem
Maxim M. Kazachek wrote: Looks like nobody else expirienced this problem Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 21 Aug 2002, Maxim M. Kazachek wrote: portupgrade fails with reason (Makefile broken) on print/jadetex and x11-fonts/webfonts due to make warning: /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored When I try to make/install documentation make also shows a lot of warnings about duplicates. This only affects -CURRENT, -STABLE doesn't have this error message. So I'm afraid that it's related to -CURRENT... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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 I have the same problem /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On Wed, Aug 21, 2002 at 02:48:38PM +0200, Martin Blapp wrote: Hi, As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. I've replaced everything, two - three times, the problem persisted. I also tried three motherboards, but all from the same type: Intel BD843BG with DDR 266 Ram (2100). Just for interest, I've replaced this Mobo now with an Asus P4B533-V board. All segfaults and illegal instructions are gone now. So it seems to be specific to the Intel board. BIOS update did not help. Change timing settings also not. The default settings produce these errors. It happens rarely on STABLE, often on CURRENT. What issue could this be with the Intel manufacured board ? Is it a design issue, or could it still be a FreeBSD bug ? Both Mobo's use the same i845 chipset, and use the same Ram. Can anyone who experienced those coredumps send me a exact list of used chipsets ? Hi Martin, I have a P4 mobile in my laptop and also had this behaviour for a certain -current window last week (the time I got the laptop). (Dell C640) Now it is gone. I'm sorry, I don't have an exact date/commit. It has the Intel Mobile 845MP chipset. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
Hi, I have a P4 mobile in my laptop and also had this behaviour for a certain -current window last week (the time I got the laptop). (Dell C640) Now it is gone. I'm sorry, I don't have an exact date/commit. Try to do some worlds in a row (5-10) and you will see if it survives. The problem here was that it did work sometimes, sometimes not. But I could never finish 10 worlds in a row. Can you try that ? It has the Intel Mobile 845MP chipset. Ah, well mine is here: http://www.intel.com/design/motherbd/bg/index.htm?iid=ipp_dlc_deskmb+p4pmb_D845BG; It's a normal Intel 845 chipset. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On Wed, Aug 21, 2002 at 03:32:44PM +0200, Martin Blapp wrote: I have a P4 mobile in my laptop and also had this behaviour for a certain -current window last week (the time I got the laptop). (Dell C640) Now it is gone. I'm sorry, I don't have an exact date/commit. Try to do some worlds in a row (5-10) and you will see if it survives. The problem here was that it did work sometimes, sometimes not. But I could never finish 10 worlds in a row. Can you try that ? Eek! First one already bailed out! Talking about bad luck! Signal 10 this time. Now I come to think of it, I didn't do much buildworld's, mostly buildkernels. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
install crash on hp omnibook 6100
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi all, i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar situation? any ideas why? 4.6 works fine. thx, tomas -BEGIN PGP SIGNATURE- Version: PGPfreeware 7.0.3 for non-commercial use http://www.pgp.com iQA/AwUBPWOhE/iU4xGSqIZ0EQKM4gCeKeo7H6SOY3O3yeCHnIKHersjb1MAnjVg bbs17FVA15kEzkGrjDy0ywMe =W7ww -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: port upgrade problem
Maxim M. Kazachek [EMAIL PROTECTED] wrote: /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored One of the recent changes in make (revision 1.38 of parse.c) causes it to emit this type of warning. This causes heaps of apparently harmless warnings in some places and breakage in a few others. Presumably the offending Makefiles should be fixed. I haven't been sufficiently annoyed yet to really look at the issue. -- Christian naddy Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On Wed, Aug 21, 2002 at 04:07:14PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 03:32:44PM +0200, Martin Blapp wrote: I have a P4 mobile in my laptop and also had this behaviour for a certain -current window last week (the time I got the laptop). (Dell C640) Now it is gone. I'm sorry, I don't have an exact date/commit. Try to do some worlds in a row (5-10) and you will see if it survives. The problem here was that it did work sometimes, sometimes not. But I could never finish 10 worlds in a row. Can you try that ? Eek! First one already bailed out! Talking about bad luck! Signal 10 this time. The 2nd one fails at exactly the same point, that can't be coindedence. Also with a signal 10. (libutil) The 3rd ended somewhere else(games/rogue), but now with signal 4. Doing the 4rd now. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On Wed, Aug 21, 2002 at 04:45:54PM +0200, Mark Santcroos wrote: Can you try that ? Eek! First one already bailed out! Talking about bad luck! Signal 10 this time. The 2nd one fails at exactly the same point, that can't be coindedence. Also with a signal 10. (libutil) The 3rd ended somewhere else(games/rogue), but now with signal 4. Doing the 4rd now. Which ends with signal 11 in usr.sbin/devinfo/ ... Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
Hi, The 2nd one fails at exactly the same point, that can't be coindedence. Also with a signal 10. (libutil) The 3rd ended somewhere else(games/rogue), but now with signal 4. Doing the 4rd now. Which ends with signal 11 in usr.sbin/devinfo/ ... Mark May this be the memory corruption other users see (Alfred, David) ? I'll start again a new row of 10 builds here and see where it ends. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands. All the strange signals have disappeared since then. Good-luck, kt On Wed, Aug 21, 2002 at 05:27:24PM +0200, Martin Blapp wrote: Hi, The 2nd one fails at exactly the same point, that can't be coindedence. Also with a signal 10. (libutil) The 3rd ended somewhere else(games/rogue), but now with signal 4. Doing the 4rd now. Which ends with signal 11 in usr.sbin/devinfo/ ... Mark May this be the memory corruption other users see (Alfred, David) ? I'll start again a new row of 10 builds here and see where it ends. Martin 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: question about ipl.ko
Hello, Crist! You wrote to Sergey Mokryshev [EMAIL PROTECTED] on Tue, 20 Aug 2002 11:15:20 -0700: [skipped] $ grep PFIL /usr/src/sys/i386/conf/AMBER options PFIL_HOOKS You need to include options PFIL_HOOKS in your kernel configuration to be able to use ipfilter as a loadable module. CJC But what's the point? PFIL_HOOKS only used by IPFilter. If you CJC are going to be recompiling a kernel, you might just as well CJC compile in options IPFILTER and be done with it. PFIL hooks is a generic kernel interface and can be used by other programs that work with network. Another point - you can upgrade ipfilter stuff without rebooting, it is useful in situations where minimum downtime is possible. PFIL_HOOKS does not add much functionality to the kernel and I always turn this on on every box. Sergey Mokryshev. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
Another point - you can upgrade ipfilter stuff without rebooting, it is useful in situations where minimum downtime is possible. PFIL_HOOKS does not add much functionality to the kernel and I always turn this on on every box. I think you are missing his point though. Some people kldload ipl.ko because they don't want to recompile their kernel. IF they recompile it with PFIL_HOOKS might as well do ipfilter at the same time. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: port upgrade problem
On Tuesday 20 August 2002 11:51 pm, Maxim M. Kazachek wrote: Looks like nobody else expirienced this problem Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 21 Aug 2002, Maxim M. Kazachek wrote: portupgrade fails with reason (Makefile broken) on print/jadetex and x11-fonts/webfonts due to make warning: /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored When I try to make/install documentation make also shows a lot of warnings about duplicates. This only affects -CURRENT, -STABLE doesn't have this error message. So I'm afraid that it's related to -CURRENT... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] I am having the same problem. I just commented out that line as a temporary workaround (It's just a message anyway) and everything builds ok. Beech -- --- Beech Rintoul - SysAdmin - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Proliferating quirk table entries
On Tue, 20 Aug 2002, Terry Lambert wrote: I think everyone in this thread needs to read the last instance of this same thread, the first time it came up. I believe the general consensus was to send the 6, and if it failed, retry with the 10, and set a flag so that subsequent requests were 10 (this instead of a static quirk table that could find itself out of date). As someone mentioned, some devices choke on the first 6-byte command and then just don't work anymore even if you start sending the 10-byte commands from then on. I have a USB multi-flash (CF/MD, MMC, SD, etc) card reader that does exactly that. I have to enable kern.cam.da.no_6_byte=1 before try to use the device and everything works fine. I also don't have any problems with any of my other SCSI devices (various SCSI CD-ROMs, a SCSI CD-RW, a SCSI ZIP drive, and SCSI DDS2 and DDS3 tape drives) when using only 10-byte commands. What problems would occur if you try 10 first and then 6 if that fails? Will the devices that only take 6-byte commands choke permanently on the first 10-byte command as some of the non-SCSI stuff does on the 6-byte commands, or would they truncate 4 bytes and treat it as the wrong command? I believe someone already proposed this, but since only some very old SCSI devices won't handle 10-byte commands correctly (correct me if I'm wrong there) and should affect very few people, how about just enabling 10-byte commands by default and offering a sysctl to turn on the 6-byte-then-10-byte method when it is needed? The benefit of that should greatly outweigh the drawbacks with the state of the hardware as it is today. -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, ARM, and S/390 under development - http://www.freebsd.org No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
(removed questions@ from Cc) Hello, David! You wrote to Sergey Mokryshev [EMAIL PROTECTED] on Wed, 21 Aug 2002 11:26:32 -0500: Another point - you can upgrade ipfilter stuff without rebooting, it is useful in situations where minimum downtime is possible. PFIL_HOOKS does not add much functionality to the kernel and I always turn this on on every box. DWC I think you are missing his point though. Some people kldload DWC ipl.ko because they don't want to recompile their kernel. IF DWC they recompile it with PFIL_HOOKS might as well do ipfilter at DWC the same time. No, David. I understand it. For those who load modules dynamically because they don't want to recompile kernel this is not a solution. My practice is to load modules dynamically to share the same kernel between several boxes. One of this PCs works as a firewall, another one serve my personal CVS repository and works as a test box (there are other machines running -CURRENT and virtually all use the same kernel and modules). Some time ago I tried to upgrade IPFilter on the fly (kldunload kldload) and it worked like a charm. It is an endless discussion, and I really don't want to continue. I wrote a letter because I disagree with Crist J. Clark CJC Both. If you are getting an 'Exec format error,' there is CJC something wrong at your end. However, ipl.ko has been broken in CJC CURRENT for a long time (over a year at least) and will not CJC load (albeit with a different error message). No, ipl.ko is not broken. It depends on pfil(9). Sincerely yours, Sergey Mokryshev. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
No, ipl.ko is not broken. It depends on pfil(9). Shouldn't we try to make a pfil.ko that ipl.ko depends on then? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
Hello, David! You wrote to Sergey Mokryshev [EMAIL PROTECTED] on Wed, 21 Aug 2002 12:07:43 -0500: No, ipl.ko is not broken. It depends on pfil(9). DWC Shouldn't we try to make a pfil.ko that ipl.ko depends on then? I make a brief look into code (I am not a kernel hacker nor a programmer). There are a few files with PFIL_HOOKS-dependant #ifdefs, but it is strongly tied with the code. /sys/net/bridge.c /sys/netinet/ip_input.c /sys/netinet/ip_output.c /sys/netinet6/ip6_forward.c /sys/netinet6/ip6_input.c /sys/netinet6/ip6_output.c Darren Reed has some pieces of code on his site, but I did not read it. ftp://coombs.anu.edu.au/pub/net/ip-filter/pfil-1.26.tar.gz According to pfil(9) manual --- BUGS The current pfil implementation will need changes to suit a threaded ker- nel model. --- May be this is the reason not to make it default. Sincerely yours, Sergey Mokryshev. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
There are a few files with PFIL_HOOKS-dependant #ifdefs, but it is strongly tied with the code. /sys/net/bridge.c /sys/netinet/ip_input.c /sys/netinet/ip_output.c /sys/netinet6/ip6_forward.c /sys/netinet6/ip6_input.c /sys/netinet6/ip6_output.c Darren Reed has some pieces of code on his site, but I did not read it. ftp://coombs.anu.edu.au/pub/net/ip-filter/pfil-1.26.tar.gz According to pfil(9) manual --- BUGS The current pfil implementation will need changes to suit a threaded ker- nel model. --- May be this is the reason not to make it default. I'm sure there is probably some reason, but if we can make it a kld, there shouldn't be a reason we can't make ipl.ko depend on it. I do not do much coding so I don't know if its even possible to do it as a kld -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On Wed, 21 Aug 2002 14:48:38 +0200 (CEST) Martin Blapp [EMAIL PROTECTED] wrote: As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. I've replaced everything, two - three times, the problem persisted. I also tried three motherboards, but all from the same type: Intel BD843BG with DDR 266 Ram (2100). Can anyone who experienced those coredumps send me a exact list of used chipsets ? Are you interested in a pciconf -v -l? Mainboard: Intel D845BGL Sockel478 bulk WA/WL System: 4.6-REL Mostly SIG4, very few SIG11 (both in buildorlds, but not in every buildworld). Bye, Alexander. -- I believe the technical term is Oops! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands. All the strange signals have disappeared since then. Thanks for the hint, I'm building /usr/ports/lang/gcc31/ now. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: acpi prevents fdc to detect correctly
As Simon 'corecode' Schubert wrote: my kernel can't detect fdc anymore when loading acpi. does anybody else have such issues? Hmm, not here. However, my fdc driver is modloaded, too (from the bootloader). I just tried to unload it, then load acpi (which yields module_register_init: MOD_LOAD (nexus/acpi, 0xc02109c0, 0xc3a83824) error 1 but the module appears in kldstat anyway), and then fdc, but that works. Unfortunately, my scratch machine which is available for testing doesn't speak ACPI at all. i know that it worked with a Aug 6 or a Aug 3 kernel, this was the last time i accessed my fd0. I haven't been changing much in the fdc(4) code lately. However, the driver gets its resource allocations from elsewhere, and if ACPI is present, wasn't it responsible for assigning resources? I don't know enough about ACPI, sorry. fdc0: output ready timeout fdc0: cmd 3 failed at out byte 1 of 3 fdc0: output ready timeout fdc0: cmd 3 failed at out byte 1 of 3 All this smells a bit similar to the behaviour of the problem in kern/21397, although it happens on those Compaqs even without ACPI. What's mysterious there is that the boot-time probe works but any later access fails with an FDC that's no longer responding at all to ISA bus selections (pattern 0xff on the bus). fdc0: cannot reserve I/O port range (6 ports) fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 Hmm. This means that the resources are told to be unavailable by whoever has to decide about this. If i read this right, with the acpi module loaded, resource allocation is perhaps handled by ACPI, while otherwise it's handled by the PnP BIOS? -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: install crash on hp omnibook 6100
Tomas Hodan wrote: i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar situation? any ideas why? 4.6 works fine. See the mailing list archives about how to disable ACPI on load. Certain Sony VAIO models have the same problem. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On Wed, Aug 21, 2002 at 08:05:17PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands. All the strange signals have disappeared since then. Thanks for the hint, I'm building /usr/ports/lang/gcc31/ now. /usr/local/bin/gcc31 -fpic -DPIC -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/s_nextafter.c -o s_nextafter.So Illegal instruction (core dumped) *** Error code 132 Stop in /usr/src. *** Error code 1 That didn't work. I will now try the other gcc's from ports. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
Hi, Try to compile the entire system on another box, install it then on the CURRENT target box, and try again ! Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/ To bad - so it's definitly data corruption in CURRENT. Asus Board P4B533-V, P-IV 2,26Ghz, 1GB DDR 2100 Ram. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: install crash on hp omnibook 6100
i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar situation? any ideas why? 4.6 works fine. Hi Tomas, Last time I installed -current on a 6100, having ACPI enabled would reboot the machine. Try disabling it from the boot loader, search the -STABLE archives for the ACPI causes immediate reboot thread. I don't know the current status (I couldn't get an acceptable subset of devices for my primary machine whilst travelling, so sold it on). At least one person with a 6100 persevered further with this, maybe someone else can help you with the current status or better advice? Cheers, AS msg42110/pgp0.pgp Description: PGP signature
Re: fd0 sometime not configured....
[EMAIL PROTECTED] (Jan Stocker) wrote: I cant mount my floppy from time to time. twoflower# mount -t msdosfs /dev/fd0 /home/jstocker/floppy/ msdosfs: /dev/fd0: Device not configured ENXIO is something of a `catch-all' error code in the kernel. It could mean that there's no such driver in the kernel (which is apparently not the problem in your case), but it could happen for quite many other problems, like a missing medium etc. The Unix fathers didn't waste too many error codes, did they? :-) Are there any kernel error messages logged? Ah, i see that msdosfs is complaining (not the fdc(4) driver), so this will even extend the possible range of problems to those where the FAT filesystem structure doesn't match msdosfs' expectations. So it would at least be worth giving mtools a try as well to read that floppy. Failing all this, make sure that you can access the medium at all (my usual test is to run hd on it). -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: BAD psmintr: [Re: psm problem]
Hi Nate, here's my dmesg: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Aug 19 22:50:47 CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ODIN Preloaded elf kernel /boot/kernel/kernel at 0xc046. Preloaded elf module /boot/kernel/acpi.ko at 0xc04600a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 700033141 Hz CPU: AMD Athlon(tm) Processor (700.03-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x622 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc040AMIE,DSP,3DNow! real memory = 671023104 (655296K bytes) avail memory = 645595136 (630464K bytes) Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00fde50 npx0: math processor on motherboard npx0: INT 16 interface acpi0: VT8371 AWRDACPI on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 agp0: VIA Generic host to PCI bridge mem 0xd800-0xdbff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686 ATA66 controller port 0xa000-0xa00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at device 7.2 (no driver attached) pci0: serial bus, USB at device 7.3 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xac00-0xacff mem 0xdf00-0xdfff irq 11 at device 9.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:50:fc:3b:58:24 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: Creative EMU10K1 port 0xb000-0xb01f irq 10 at device 13.0 on pci0 rl1: RealTek 8139 10/100BaseTX port 0xb800-0xb8ff mem 0xdf001000-0xdf0010ff irq 10 at device 15.0 on pci0 rl1: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl1: Ethernet address: 00:50:fc:3b:b1:fa miibus1: MII bus on rl1 rlphy1: RealTek internal media interface on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: HighPoint HPT370 ATA100 controller port 0xcc00-0xccff,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07 irq 11 at device 19.0 on pci0 ata2: at 0xbc00 on atapci1 ata3: at 0xc400 on atapci1 fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: Option ROMs at iomem 0xcc000-0xc,0xc-0xcbfff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to deny, logging disabled acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% ad4: 43979MB IBM-DTLA-307045 [89355/16/63] at ata2-master UDMA100 acd0: CDROM TOSHIBA CD-ROM XM-6702B at ata0-master PIO4 Mounting root from ufs:/dev/ad4s1a On Tue, Aug 20, 2002 at 04:05:44PM -0700, Nate Lawson wrote: BTW, just a hunch: try reverting sys/dev/pci/pci.c to 1.194 and see if that helps. Looks like the current version of psm.c is requesting a shared interrupt (RF_SHAREABLE). I'll currently build a world with pci.c version 1.194 and try it again! -Anselm -Nate On Tue, 20 Aug 2002, Nate Lawson wrote: Nothing has changed in moused or sys/isa/psm.c for at least 5 months so this may be a more general problem. How about a dmesg? Please keep -current in the cc: so everyone can benefit. On Wed, 21 Aug 2002, Anselm Garbe wrote: On Tue, Aug 20, 2002 at 01:37:34PM -0700, Nate Lawson wrote: Are you using /dev/psm0 directly in X or with moused or with
Re: install crash on hp omnibook 6100
Am Mi, 2002-08-21 um 21.52 schrieb Andy Sparrow: i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar situation? any ideas why? 4.6 works fine. Hi Tomas, Last time I installed -current on a 6100, having ACPI enabled would reboot the machine. Try disabling it from the boot loader, search the -STABLE archives for the ACPI causes immediate reboot thread. I don't know the current status (I couldn't get an acceptable subset of devices for my primary machine whilst travelling, so sold it on). At least one person with a 6100 persevered further with this, maybe someone else can help you with the current status or better advice? Yes I ran -current on my 6100 for a while. I also reported the immediate reset when booting with ACPI enabled. I haven't been able to further narrow the problem down, and didn't get a reply from the ACPI folks as well. So I ran with ACPI disabled. I switched to 4.6R a while ago because I got tired of -current after a phase of instability. Note that this is not a complaint, it is just that a released version better fits my needs. I may go back to running -current when I have more spare time. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: install crash on hp omnibook 6100
On Wed, 21 Aug 2002, Andy Sparrow wrote: At least one person with a 6100 persevered further with this, maybe someone else can help you with the current status or better advice? There is an issue with the HP laptop DSDT and our ACPI code. They initialize some child devices before initializing their parents, causing an infinite loop. The acpi-jp list doesn't seem interested in changing the way we do initialization, and theres no docs on the part it's initializing to rewrite the DSDT. In short - its broke, just turn it off :) BTW windows has issues with sleep/hibernate on these machines anyway, so there are probably deeper issues at hand. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: BAD psmintr: [Re: psm problem]
On Tue, Aug 20, 2002 at 04:05:44PM -0700, Nate Lawson wrote: BTW, just a hunch: try reverting sys/dev/pci/pci.c to 1.194 and see if that helps. Looks like the current version of psm.c is requesting a shared interrupt (RF_SHAREABLE). I've done that and compiled a new kernel (currently without new world, because I think it's not needed here - the world is of Aug 19) with pci.c 1.194 - but the mouse behaves still like 1.195 of pci.c :-( Does nobody else notices such problems? Hmmm If you need something more related info, mail me and I'll send to you! Thanks for any hints, Anselm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
Hi Please try to continue from where it broke by repeating make. Otherwise, please get a precompiled port package. kt On Wed, Aug 21, 2002 at 10:26:37PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 08:05:17PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands. All the strange signals have disappeared since then. Thanks for the hint, I'm building /usr/ports/lang/gcc31/ now. /usr/local/bin/gcc31 -fpic -DPIC -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/s_nextafter.c -o s_nextafter.So Illegal instruction (core dumped) *** Error code 132 Stop in /usr/src. *** Error code 1 That didn't work. I will now try the other gcc's from ports. Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM 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: BAD psmintr: [Re: psm problem]
Anselm Garbe wrote: atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 Mine (which works) says: atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: failed to get data. psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 On a hunch, I will guess that the special case code for ISA sharing for the keyboard and mouse on the same PS/2 controller is not present in the ACPI. Try not loading ACPI, and see if it fixes it for you (this seems to be the week for ACPI). I'm not sure about the IRQ 12 (that's the bus mouse IRQ; the PS/2 mouse interrupt is supposed to be shared with the keyboard, according to Frank van Guilliwe?!?), but ACPI is *a* difference, even if it's not *the* difference -- at least it's something to try. 8-(. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Solved: CURRENT and P-IV problems
On 21 Aug, Martin Blapp wrote: Hi, Try to compile the entire system on another box, install it then on the CURRENT target box, and try again ! Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/ To bad - so it's definitly data corruption in CURRENT. Asus Board P4B533-V, P-IV 2,26Ghz, 1GB DDR 2100 Ram. No sign of any problems here with last night's -current. Gigabyte GA7-DX+, Athlon XP 1900+, 1GB PC2100 ECC DRAM, SCSI disk, NFS client. I'm not running any sound hardware or the Xserver, and I'm accessing the host via ssh instead of the console. The kernel is GENERIC + SMBus. It's on buildworld #7 at the moment: -rw-r--r-- 1 root wheel 5321510 Aug 21 14:43 /var/tmp/buildworld24-1 -rw-r--r-- 1 root wheel 5321510 Aug 21 15:38 /var/tmp/buildworld24-2 -rw-r--r-- 1 root wheel 5321510 Aug 21 16:33 /var/tmp/buildworld24-3 -rw-r--r-- 1 root wheel 5321510 Aug 21 17:28 /var/tmp/buildworld24-4 -rw-r--r-- 1 root wheel 5321510 Aug 21 18:23 /var/tmp/buildworld24-5 -rw-r--r-- 1 root wheel 5321510 Aug 21 19:18 /var/tmp/buildworld24-6 -rw-r--r-- 1 root wheel 826096 Aug 21 19:28 /var/tmp/buildworld24-7 I was having filesystem corruption problems a couple months ago, but haven't seen any of these problems in ages. The only outstanding problem is a lock order reversal in the pipe code that is triggered by the OpenOffice port build. Witness complains, but the build completes successfully. Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #34: Wed Aug 21 01:36:34 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERICSMB Preloaded elf kernel /boot/kernel/kernel at 0xc0603000. Preloaded elf module /boot/kernel/acpi.ko at 0xc06030a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 1608231091 Hz CPU: AMD Athlon(tm) XP 1900+ (1608.23-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 1073676288 (1048512K bytes) avail memory = 1035575296 (1011304K bytes) Pentium Pro MTRR support enabled Using $PIR table, 11 entries at 0xc00fdc30 npx0: math processor on motherboard npx0: INT 16 interface acpi0: GBTAWRDACPI on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 acpi_pcib0: Host-PCI bridge port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 agp0: AMD 761 host to AGP bridge port 0xc000-0xc003 mem 0xef02-0xef020fff,0xe800-0xebff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 5.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686 ATA100 controller port 0xc400-0xc40f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: VIA 83C572 USB controller port 0xc800-0xc81f irq 5 at device 7.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 uhci1: VIA 83C572 USB controller port 0xcc00-0xcc1f irq 5 at device 7.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 viapropm0: SMBus I/O base at 0x5000 viapropm0: VIA VT82C686A Power Management Unit port 0x5000-0x500f at device 7.4 on pci0 viapropm0: SMBus revision code 0x40 smb0: SMBus generic I/O on smbus0 fxp0: Intel Pro 10/100B/100+ Ethernet port 0xe000-0xe03f mem 0xef00-0xef01,0xef021000-0xef021fff irq 10 at device 10.0 on pci0 fxp0: Ethernet address 00:02:b3:5c:8b:82 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc_pci0: Adaptec 19160B Ultra160 SCSI adapter port 0xe400-0xe4ff mem 0xef022000-0xef022fff irq 11 at device 12.0 on pci0 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4
Re: BAD psmintr: [Re: psm problem]
On Wed, Aug 21, 2002 at 05:34:36PM -0700, Terry Lambert wrote: On a hunch, I will guess that the special case code for ISA sharing for the keyboard and mouse on the same PS/2 controller is not present in the ACPI. Try not loading ACPI, and see if it fixes it for you (this seems to be the week for ACPI). Well Terry, without loading ACPI it works fine for me now. It seems, that there's the dog :-) -Anselm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
