Re: BAD psmintr: [Re: psm problem]
Anselm Garbe wrote: > 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 :-) You might want to check if there's a BIOS update available that changes the ACPI information for your system to make it more correct. If you know the last time it was working, and have a local CVS repository, it should only take log2(N)+1, at most, to do a binary date search to see what day the code broke. That's 10 recompiles and reboots to get the date, if it occurred at any time in the last 16 months. If it's when ACPI was enabled by default in the first place, it means it's your BIOS (which is why I suggested going after the BIOS first thing). You've played "higher/lower" enough to know the optimum strategy, right? Basically, you get a bounding date, and divide it in two, and divide the remaining time in 2, etc., until you have the day, using e.g. cvs co # fails == +0 cvs co -D"512 days ago" # works == -512 cvs co -D"256 days ago" # works == +256 cvs co -D"128 days ago" # fails == +128 cvs co -D"192 days ago" # works == -96 ... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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
Re: BAD psmintr: [Re: psm problem]
Anselm Garbe wrote: > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 Mine (which works) says: atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: failed to get data. psm0: 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: 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: 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=0x183f9ff AMD Features=0xc040 real memory = 671023104 (655296K bytes) avail memory = 645595136 (630464K bytes) Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00fde50 npx0: on motherboard npx0: INT 16 interface acpi0: 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: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 agp0: mem 0xd800-0xdbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xa000-0xa00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) rl0: 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: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xb000-0xb01f irq 10 at device 13.0 on pci0 rl1: 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: on rl1 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: 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: 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: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: at iomem 0xcc000-0xc,0xc-0xcbfff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: 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 [89355/16/63] at ata2-master UDMA100 acd0: CDROM 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 XKBD? > > > > > > > > > > I'm using moused - the problem isn't X related at all. > > > > > > Here's my configuration: > > > > > > ---[rc.conf]--- > > > [...] > > > moused_port="/dev/psm0" > > > moused_type="auto" > > > moused_enable="YES" > > > > > > > > > /boot/device.hints is identical to current GENERIC.hints > > > > > > Anselm > > > > > > > > > > > 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]
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). -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 XKBD? > > > > > > > I'm using moused - the problem isn't X related at all. > > > > Here's my configuration: > > > > ---[rc.conf]--- > > [...] > > moused_port="/dev/psm0" > > moused_type="auto" > > moused_enable="YES" > > > > > > /boot/device.hints is identical to current GENERIC.hints > > > > Anselm > > > > > > 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]
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 XKBD? > > > > I'm using moused - the problem isn't X related at all. > > Here's my configuration: > > ---[rc.conf]--- > [...] > moused_port="/dev/psm0" > moused_type="auto" > moused_enable="YES" > > > /boot/device.hints is identical to current GENERIC.hints > > Anselm > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BAD psmintr: [Re: psm problem]
Are you using /dev/psm0 directly in X or with moused or with XKBD? On Tue, 20 Aug 2002, Anselm Garbe wrote: > Hi there again, > > so after using -current of Mon Aug 19 22:50:47 CEST 2002 I get the > same errors. Maybe I should describe the problem more precisely. > > On Aug 15, 2002 I upgraded my -current system (world+kernel). Therefore > I used -current of Aug 6, 2002 without any problems. > Since Aug 15 I get following errors with several ps/2 mouses (I only > have two ones - MS Mouse of late 80s and a very new MS IntelliEye): > > Aug 20 20:22:49 odin kernel: psmintr: out of sync (00c0 != ). > Aug 20 20:22:49 odin kernel: psmintr: discard a byte (1). > Aug 20 20:22:49 odin kernel: psmintr: out of sync (00c0 != ). > Aug 20 20:22:49 odin kernel: psmintr: discard a byte (2). > Aug 20 20:22:52 odin kernel: psmintr: out of sync (00c0 != ). > Aug 20 20:22:52 odin kernel: psmintr: re-enable the mouse. > Aug 20 20:51:38 odin kernel: psmintr: out of sync (00c0 != ). > > > Sometimes the mouse doesn't work after booting or after tons of error > messages like above, /dev/psaux will be disabled by the kernel. > > I searched for related questions via google and several freebsd-mailing lists, and >tried in fact to set hint.psm.0.flags="0x800" in /boot/device.hints. > I tried both mouses with no different behavior. > > I tried 4.6-RELEASE, which works fine. > > Any hints? What could be the problem? And remember, that everything > worked fine with -current of Aug 6, 2002 and before. > > Thanks, > Anselm To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BAD psmintr: [Re: psm problem]
Hi there again, so after using -current of Mon Aug 19 22:50:47 CEST 2002 I get the same errors. Maybe I should describe the problem more precisely. On Aug 15, 2002 I upgraded my -current system (world+kernel). Therefore I used -current of Aug 6, 2002 without any problems. Since Aug 15 I get following errors with several ps/2 mouses (I only have two ones - MS Mouse of late 80s and a very new MS IntelliEye): Aug 20 20:22:49 odin kernel: psmintr: out of sync (00c0 != ). Aug 20 20:22:49 odin kernel: psmintr: discard a byte (1). Aug 20 20:22:49 odin kernel: psmintr: out of sync (00c0 != ). Aug 20 20:22:49 odin kernel: psmintr: discard a byte (2). Aug 20 20:22:52 odin kernel: psmintr: out of sync (00c0 != ). Aug 20 20:22:52 odin kernel: psmintr: re-enable the mouse. Aug 20 20:51:38 odin kernel: psmintr: out of sync (00c0 != ). Sometimes the mouse doesn't work after booting or after tons of error messages like above, /dev/psaux will be disabled by the kernel. I searched for related questions via google and several freebsd-mailing lists, and tried in fact to set hint.psm.0.flags="0x800" in /boot/device.hints. I tried both mouses with no different behavior. I tried 4.6-RELEASE, which works fine. Any hints? What could be the problem? And remember, that everything worked fine with -current of Aug 6, 2002 and before. Thanks, Anselm On Thu, Aug 15, 2002 at 08:43:25AM +0200, Anselm Garbe wrote: > On Thu, Aug 15, 2002 at 12:14:37AM +0200, Anselm Garbe wrote: > > Hi there, > > > > after make world of today: > > my mouse behaves sometimes curios (while moving around, some selections > > are done, without clicking)... > > OK, after installing a new world (source code of Aug 15, 2002 at 00:00 > MEZ), the psm problem still exists, here's what /var/log/messages says: > > Aug 15 08:30:36 odin named[183]: Ready to answer queries. > Aug 15 08:34:13 odin kernel: drm0: port 0x9000-0x90ff mem >0xdd00-0xdd00,0xd000-0xd7ff irq 5 at device 0.0 on pci1 > Aug 15 08:34:13 odin kernel: info: [drm] AGP at 0xd800 64MB > Aug 15 08:34:13 odin kernel: info: [drm] Initialized radeon 1.1.1 20010405 on minor 0 > Aug 15 08:34:41 odin kernel: psmintr: out of sync ( != 0008). > Aug 15 08:34:41 odin kernel: psmintr: discard a byte (1). > Aug 15 08:34:41 odin kernel: psmintr: out of sync ( != 0008). > Aug 15 08:34:41 odin kernel: psmintr: discard a byte (2). > Aug 15 08:34:41 odin kernel: psmintr: out of sync ( != 0008). > Aug 15 08:34:41 odin kernel: psmintr: discard a byte (3). > > It's clear now, that this problem starts after launching X. > The last world I tried was of Aug 06, 2002 without these problems. > XFree86 was installed also on Aug 06, 2002 via ports. > > Anselm > > 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: psm problem
On Thu, Aug 15, 2002 at 12:14:37AM +0200, Anselm Garbe wrote: > Hi there, > > after make world of today: > my mouse behaves sometimes curios (while moving around, some selections > are done, without clicking)... OK, after installing a new world (source code of Aug 15, 2002 at 00:00 MEZ), the psm problem still exists, here's what /var/log/messages says: Aug 15 08:30:36 odin named[183]: Ready to answer queries. Aug 15 08:34:13 odin kernel: drm0: port 0x9000-0x90ff mem 0xdd00-0xdd00,0xd000-0xd7ff irq 5 at device 0.0 on pci1 Aug 15 08:34:13 odin kernel: info: [drm] AGP at 0xd800 64MB Aug 15 08:34:13 odin kernel: info: [drm] Initialized radeon 1.1.1 20010405 on minor 0 Aug 15 08:34:41 odin kernel: psmintr: out of sync ( != 0008). Aug 15 08:34:41 odin kernel: psmintr: discard a byte (1). Aug 15 08:34:41 odin kernel: psmintr: out of sync ( != 0008). Aug 15 08:34:41 odin kernel: psmintr: discard a byte (2). Aug 15 08:34:41 odin kernel: psmintr: out of sync ( != 0008). Aug 15 08:34:41 odin kernel: psmintr: discard a byte (3). It's clear now, that this problem starts after launching X. The last world I tried was of Aug 06, 2002 without these problems. XFree86 was installed also on Aug 06, 2002 via ports. Anselm To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
