Re: my psm0 doesn't work with new acpi :(
On Wed, 5 Sep 2001, Kazutaka YOKOTA wrote: > As some other people are not having this problem, this may be > called a quirk or anomaly, to say the least. I think that it is ASUS A7V-133 feature, cause Harti has this board to, if i'm not wrong. Check our dmesgs. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
As I wrote in another mail to Harti Brandt and cc'ed to you, it now appears that ACPI on your motherboard declares IRQ 12 BOTH in the PS/2 mouse resource descriptors and in the system reserved resource descriptors. The system reserved resources are sucked by the sysresource driver in the acpi module. If the psm driver can get at IRQ 12 BEFORE the sysresource driver, or the sysresource driver is made to be probed AFTER all other acpi device nodes are probed, all should be fine... As some other people are not having this problem, this may be called a quirk or anomaly, to say the least. Kazu >> Then, would you remove my previous small patch from psm.c, and put the >> following line in /boot/device.hints instead and reboot? >> debug.acpi.disable="sysresource" >> Or, you may type >> set debug.acpi.disable="sysresource" >> at the loader prompt before "boot -v". > >Wow, my NetScroll is back in bussiness!!! ;-))) >So is it buggy BIOS, chipset, ASUS or PS/2 mouse? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Wed, 5 Sep 2001, Kazutaka YOKOTA wrote: > Then, would you remove my previous small patch from psm.c, and put the > following line in /boot/device.hints instead and reboot? > debug.acpi.disable="sysresource" > Or, you may type > set debug.acpi.disable="sysresource" > at the loader prompt before "boot -v". Wow, my NetScroll is back in bussiness!!! ;-))) So is it buggy BIOS, chipset, ASUS or PS/2 mouse? atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d atkbd1: unable to allocate the IRQ resource psm0: unable to allocate the IRQ resource atkbd1: unable to allocate the IRQ resource psm0: current command byte:0047 psm0: irq 12 on atkbdc0 psm0: model NetMouse/NetScroll Optical, device ID 0-00, 3 buttons psm0: config:, flags:, packet size:4 psm0: syncmask:08, syncbits:08 atkbdc-: atkbdc0 already exists, using atkbdc1 instead atkbdc1: failed to probe at port 0x60 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
Thank you. I got the files. Then, would you remove my previous small patch from psm.c, and put the following line in /boot/device.hints instead and reboot? debug.acpi.disable="sysresource" Or, you may type set debug.acpi.disable="sysresource" at the loader prompt before "boot -v". Kazu >You missunderstand or maybe i wrote something wrong. Now i've got a >bootable kernel with no panic and NO psm0 messages at all. So i had to >boot -v to produse some. Now i applied your patches and next mail would >be with boot -v messages > >> process. When the system comes completely up, please send me >> entire dmesg output and /boot/device.hints. >Ok. > >> It now appears we have several classes of symptoms regarding the PS/2 >> mouse and ACPI. Each may need different trick to fix... >I think that it is ASUS A7V-133 feature. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
> process. When the system comes completely up, please send me > entire dmesg output and /boot/device.hints. into.tar.bz2
Re: my psm0 doesn't work with new acpi :(
On Wed, 5 Sep 2001, Kazutaka YOKOTA wrote: > What was the message? Is that the following? > panic: nexus_setup_intr: NULL irq resource! > Or, something else? You missunderstand or maybe i wrote something wrong. Now i've got a bootable kernel with no panic and NO psm0 messages at all. So i had to boot -v to produse some. Now i applied your patches and next mail would be with boot -v messages > process. When the system comes completely up, please send me > entire dmesg output and /boot/device.hints. Ok. > It now appears we have several classes of symptoms regarding the PS/2 > mouse and ACPI. Each may need different trick to fix... I think that it is ASUS A7V-133 feature. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
>> > PS. I just removed and checkout sys/isa.
>> hope you did a "make clean" too...
>I tried this too - nothing changed. :(
>Where is my netscroll genius... I want it back
>;-)
What was the message? Is that the following?
panic: nexus_setup_intr: NULL irq resource!
Or, something else?
Can you provide the last few boot messages before the panic?
Would you please apply the attached patch in addition to my last one,
in order to get some more information on your system and ACPI BIOS.
I am afraid this patch still won't make your mouse available, but
it may stop your system from panicing and let you go through the boot
process. When the system comes completely up, please send me
entire dmesg output and /boot/device.hints.
It now appears we have several classes of symptoms regarding the PS/2
mouse and ACPI. Each may need different trick to fix...
Thanks
Kazu
--- psm.c-save Wed Sep 5 18:54:27 2001
+++ psm.c Wed Sep 5 19:07:09 2001
@@ -2818,8 +2818,14 @@
bus_set_resource(psm, SYS_RES_IRQ, 1, irq, 1);
bus_delete_resource(me, SYS_RES_IRQ, 0);
+ printf("adding...");
+ BUS_PRINT_CHILD(device_get_parent(psm), psm);
+
+ return 0;
+#if 0
/* ...then probe and attach it */
return device_probe_and_attach(psm);
+#endif
}
static int
@@ -2830,6 +2836,9 @@
if (ISA_PNP_PROBE(device_get_parent(dev), dev, psmcpnp_ids))
return ENXIO;
+ printf("probing...");
+ BUS_PRINT_CHILD(device_get_parent(dev), dev);
+
/*
* If we find an atkbdc device on the same bus,
* create our copy there.
@@ -2838,6 +2847,9 @@
device_get_unit(dev));
if (atkbdc && (device_get_state(atkbdc) == DS_ATTACHED))
create_a_copy(atkbdc, dev);
+
+ printf("quiting...");
+ BUS_PRINT_CHILD(device_get_parent(dev), dev);
/* keep quiet */
device_quiet(dev);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Tue, 4 Sep 2001, Julian Elischer wrote: > > PS. I just removed and checkout sys/isa. > hope you did a "make clean" too... I tried this too - nothing changed. :( Where is my netscroll genius... I want it back ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Wed, 5 Sep 2001, Kazutaka YOKOTA wrote: KY>>> Would try the following patch for /sys/isa/psm.c IN ADDITION TO KY>>> my previous patch? KY>>> KY>>> (This is a test patch. It's not a final fix.) KY>> KY>>panic: nexus_setup_intr: NULL irq resource! KY> KY>Ok, this is one last test patch. Please remove ALL my previous KY>patches and apply this one in /sys/isa. If I boot with -cv I see: ... atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d atkbd1: unable to allocate the IRQ resource psm0: unable to allocate the IRQ resource atkbd1: unable to allocate the IRQ resource psm0: unable to allocate the IRQ resource ppc1: cannot reserve I/O port range What wonders me is that psm0 is probed after atkbd1? harti To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
"Ilmar S. Habibulin" wrote: > > On Wed, 5 Sep 2001, Kazutaka YOKOTA wrote: > > > Ok, this is one last test patch. Please remove ALL my previous > > patches and apply this one in /sys/isa. > > Nothing at all, i had to boot with -c option to get any message about > psm0. Sendig you dmesg, but i think it wouldn't help much. > > PS. I just removed and checkout sys/isa. hope you did a "make clean" too... > > > Name: dmesg.bz2 >dmesg.bz2Type: unspecified type (APPLICATION/octet-stream) > Encoding: BASE64 -- ++ __ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ [EMAIL PROTECTED] +-->x USA\ a very strange | ( OZ)\___ ___ | country ! +- X_.---._/presently in San Francisco \_/ \\ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Wed, 5 Sep 2001, Kazutaka YOKOTA wrote: > Ok, this is one last test patch. Please remove ALL my previous > patches and apply this one in /sys/isa. Nothing at all, i had to boot with -c option to get any message about psm0. Sendig you dmesg, but i think it wouldn't help much. PS. I just removed and checkout sys/isa. dmesg.bz2
Re: my psm0 doesn't work with new acpi :(
>> Would try the following patch for /sys/isa/psm.c IN ADDITION TO
>> my previous patch?
>>
>> (This is a test patch. It's not a final fix.)
>
>panic: nexus_setup_intr: NULL irq resource!
Ok, this is one last test patch. Please remove ALL my previous
patches and apply this one in /sys/isa.
Thanks.
Kazu
begin 666 atkbdcident.diff3.gz
M'XL("%@HE3L V%T:V)D8VED96YT+F1I9F8S ,T;:7?;QO$S]"O6RHO* Q0!
M4K>:-+1$QVPL49%HQVG:APC
M8UEVV]IO=RQF=X^LW:/NCD$PFLUFQ<3#MK7#[(.CG=VC3G?CN^]8:[=CVAW6
MW-TQ[1WVW7<;;(/Y_-Z;N''L)(: H :.X6TS3MPD\-A]&/CB=>#S:1*,'VM^
M%-SSR$E80SR9""GP.(S 0QU6R[7!5$*>1>$UKZV:Y2:)Z]VLG!;Q>'ZW$%J&
M+S+$@551#<=8PXT^X+QTI@1PQY.;T N1%,JF\T@3? G7:#N9,']S%F
MKN\#!]F$NW'"PBEGWDTP :ZW8=;+MU=.[_34.7D]>'-:$R!,9@%8 M_Z=NH"
M3QI>*C@\ 4# #1^K$99/]
M\/+TA*8Y@\L?3;8%Z-6/GPOBU9O>]U< A A#]AKT!+JM :"AFC0C(=28AX[[F02>H[BL>#1U<^(\I4D!):1
MT/\#_]LFNWSE]$Y&@W=]0@LVJQ&P;]CYVS=OZF1[-'H=A@DHR748\SJ.&:EI
M@9#&4ACS*:&7A(SP1%'S>;+""3ZY!JA#*2UA(C &=G'U/["+&F*,Y\&B2Y2
M]9U\0$:R_JI"^M(1''9->X\U;7L?/]$3? 0H.2_ &K$'LC9NI0+C"+P^7M.@
M%AH.TPR''GD4A9$PCMC+:QVA(K6N]7]D(BROX4(S4 40D!*_U)!*)5C+S SB
M#$P0L"V8)K6!L;7U0.(^S2<0=O2/;:*[?A:0
MU+$HFO$/?,S5ZQZHQ,LW??:IPN5D>TF_4W80C-3JJC]Z>^$,SDAGPDK@Q/+!BI6!Z^[>T6Z'5'5GWX2P9N?0/)!A*V@E
MQ1; >G*HR>.,^WS,Y#$O@4J/BS%"YJ!0H[UP.@X^S".(,( B8:>DQS@-71I.
M&ESUZ/"X<^-;<>@5@@AG$L39MT+, X2OG0[X#/O^=0/2Z,QCP)WDA^;A!\"
MSYW@5"1[#\(YFS7W.F;'EH07 V'/62^N]ISJR+J9#X2SV;[O$(>S!6"()@)D
M8>1C/.C=N&#]%+;1F6S02_1%U0C085T)=#7R$7?!7.[=:,E*@5R AJ,<0'9N
M->[=237HARA(^#-@:\ %;,7**BU!!C7DAKDSA%1H.3L6P-5!EOWC4CK06I3,
MQ!^.-LB'RG.=SK;T&RAP?KX<]\+YE&:EYJ7AFQ-?.7):%T-E4V:1 13#K\[F
MO$(ZMRI#DQ:E,BI(F;NL>;"#B16=D:75\3R>(8,,$2!,P:X]-;@\@=,7I'D<
MRR6<=/HI6S1+UEF C[,U,S,K3*]B16I<9LG<*F9G]F*630CFMXK8YW0S3W3^
M7<7BHN(4>99_6S=+O"L9F[G("BL6%U&OM+:*=66L%]A!!7M=+P%&)MIBEN-8
M\74%")^O %(Q807K"GR?Y%Y6K(V7K8V7K_6!2^K#BLD9H.+X:7(XJ/:3-*/M9?9F?($=W=/7-G!PC?W47?
M2)07\@9D1$LO+K4TQR6X4,L[?8C(X"#40HHLF-AH80"7"^D@3FG_4N
M*L>MV$>]LL1&HA:89L.Y --DV7YU3:CH*?!8B6OB/&.WLE;P&4"6*X350:Y6
M^_!4\<.@XH=4%4&ECQ\RAA=CLH!A&$JMQ3>*Y.72 )\RW36D[C9\_!3FB9#R
M18#4]H]52:11RZ/'&HWZ@C()6F#'MLT="RSP\-#<[Z:^QU@;#&Q)Q1] OMV
M?UB#];!V.YE(/.,T1>(^5M2N.1.L%5_%-M8V+<6\" !1
MBZVJFK@N1PUG/<33-:D(B"UT(#)5)QG@E>(X4DI^=JM>.(\QJ%AAI&N8IK2NEG*0 M
M @/W _JRA>M;WZ9IM=A0C%&5B1BNZJM">=VI+UGR-Y@, X.Q7G(-8C8-P4(A
MK$U @:\?Z>7%](*]' RO "#KG5P,3+$TXF,>H9++Q3<@DYB-8=+@\L=MV'29
MQO_9VHZ"&5SUG(OS"^?B:Z =!F>!0):LKAV2DCD"GFIH.MI61Z02=BWF5K UV14B2[2$GBATD29I76WB0DAO(.4%IF12[
M51VM:Y9OR61S6%>QJ$R9U4Y*)'?Q*2O&_:E"5#Z[>O?]NDXJVVK@P. ZX7:!F+
MH.&$KWT=DKC-6'F%()1)1[>Y&MWL'O")]QHI=LH\<7-)W,*MB;8)$B=H6B:8
M<1@F><&P++>HB74J!-K=IUZ&SOZ!N2=KH^K$?(*>&/%# )X8R,#27IU*Q1YD
M1/GKI2.46T-H94VH;UWX%7D_9ES#T7)[7%Y,%TN+ETO%SP"P(H!W_?/3X>7@
M] BKCI4P].JR D,<.C@@#G6M[A_$H90EN -(M7Z/]>VUN*.Q8\'BY9S)LT+P
M2!;5!: \;[JVA:E[USXTN_OYJZ_^^;!_/CJ6$?6" +&ZQ/N\ F]EC,A4C)C%
M@>O++'7IQ:-Q.149 <\I)V1L+JCZ/8&AZ=Z5M>\_C%62@J@W;W@
MW3V)&-Y_TI.\SNRV.WO,[ASM6$>[^P:MPXM/?4K:JK=SU-F7*?X>>BC\4 [*
MT*YJ2#M,=A?.8XX:A_5+D*HX,=L--IY//;K;G$5A$J)HZ()3;_A"!%2W%W.<
MBYK6\I4I93U_:8:+1$>+6+%XEHBE5T[S>?4T\M*6\-*6+7E O0B4E E496<"
M)'5(*MX#+[@(@HU*MT [%2FA]C3,'8]V=JTI-M/8]GR7C_%IN6=?BF;JJ<)
MWM T\2COI+HV-7#"\;4G3W;\RQ<(D&*J]Z3-?JVO(%R#-/B1)VEM5D[&/H39
M=.8(IO]?7@I
M3QC6L;5\1=*#46K\0+3(1R2&KO,.;%2I_?W=K 46F[3B.Z52(-WH$?"DK!]5
MJM EJ:G ^CV2B.A:;9(XL;I3TE[<*:F8 ]P2=P/W=>,C>HI"YQS=6_]37%^W
M6G+T&";*\65_HJQ(W8_"M-SXECIGA!?'K_5C $),/NQBN\;^X:Z9]IXIS[6\
M&DIZ7%!@[%-;TC5&84:A7RT_IK)+A0**\Y?NO[01+[R[^<_V8<&T8B1*>
MZ,"B^]^F_$2:T)JLC8PW/K^>?ZB-+M]B8Q%+-3=G=5(-O!ONW5+Y:7 :IWJ/
MT@([6%JZ\;,F(VFH5!N@+J5ZEOG+KB5E/TQL\.7-=<^&4FI!E9Q8UF)*X0/%
M\K9<\(5-8?G6+\7R4O<7%:W*3:>Z,:3._EG=IPJ*RFN%].0+BI04L:A8V45B
M../3JBO$JJX_)2V$(BKY $>D5UOLXNK,.1F>OQI\+P2CL3>=6UEPJ%S+I"Q!
M=X^H3'KM>K_BK)YQ0^+VZ1MY_6H==$T;&QCQX2 ]!_$O]82*MTSQ5MG@$LUK99IG:6S\
MPI[&EHB)=1U,S;Y*!UN*%E5) 8/_VC]B:^@9JWWMU[=!VW!7"474%2FQUHRY
MDE?T)BW@MI[4^JPH2<'@X2U9[N-1IRS[F4#7/8O8)_0^3N_M>]36T>7PC?-R
M,+K*00#NZ]=Y<]=4$99M6UBN+@3CHVI]UJ*6;J.:-F5URQD4N*%2!NDF*ZP26))KV_9.OXW!\OO8V._\S'"%IJP
M5KC,.2'5'?*LAF(IY3VAB_9N1R9&.A88WG#IJ8<7_7,-DSYL^O.Q\H)9@WN.
M1TR)=-3O79X.?SI_4L=SUL+\)58N4N!]\.M=+/'N'9H'@M"*0@+8E*H8B*A(
MQ>+T7"PA0##>;@#%#3:Z <#
MV[BHC>M5N T,/L%@3:)SWCOK&P:Z:0]RJN(Q8\ Z:6X^RTW7
M/"'%I34E7E"U4%Q/.Z[CA;/'K$:H5#L=N..R\)"K,9J+_OBE$(]U:EKPJW)$Y\'Y3WX7F+_S%
MA?QAX5UX+WYWDL8V$/A@O#/E#PSY)'A:;#D43B%'GJV.B;0KI-!'N( C H_M
M[6W8=2I_S27:#:AP!0>_^#VR0IPSKD+;4E[&@I52L&O<
M\N=31:7M]86L3OLF'CC#%@4@4NZI:F[AE#@?8^,#EGW%"J&U)".2!TR)^#:]
M:Z?%Z2S4H>Z'W"5R"6?J&SDI6KZH?U:%6*E&R;VVMI@.F\Y#^8ZRY5/0T-&H
M=_*Z?RK8D3<\S=XR^=]R/F._S@,NQ2WATTBQ=%Z\+,H)NK)!3?Z0MKB^=,XA
Re: my psm0 doesn't work with new acpi :(
On Tue, 4 Sep 2001, Kazutaka YOKOTA wrote: > Would try the following patch for /sys/isa/psm.c IN ADDITION TO > my previous patch? > > (This is a test patch. It's not a final fix.) panic: nexus_setup_intr: NULL irq resource! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :( (fwd)
> ISH>On Tue, 4 Sep 2001, Kazutaka YOKOTA wrote: > ISH> > ISH>> Please apply the attached patch in /sys/isa and see what it does. > ISH>It does panic with a smiling face ;-))) > ISH> > ISH>panic message was "bad ivar read request" > > it fails in acpi_read_ivar with an index (3rd argument) of 12. And that > looks like the IRQ, so probably there is something really wrong. No. This is in psm.c:790. psmidentify is trying to get the ISA vendor ID. But it seems, that the read_ivar request to which this evaluates end in acpi_read_ivar instead of isa_read_ivar. If I comment out these two lines, the kernel boots as before, but the psm is still not attached. (the message from psm1 is new, this is probably because of the commented out line). harti Copyright (c) 1992-2001 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 #5: Tue Sep 4 15:44:25 CEST 2001 [EMAIL PROTECTED]:/opt/obj/usr/src/sys/BEAGLE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 908095602 Hz CPU: AMD Athlon(tm) Processor (908.10-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc044<,AMIE,DSP,3DNow!> real memory = 536788992 (524208K bytes) avail memory = 518848512 (506688K bytes) Preloaded elf kernel "kernel" at 0xc0394000. Preloaded elf module "random.ko" at 0xc039409c. Preloaded elf module "acpi.ko" at 0xc039413c. Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00f16c0 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 atkbdc_probe,110 acpi_cpu0: on acpi0 atkbdc_probe,110 acpi_button0: on acpi0 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 pci0: at device 4.1 (no driver attached) pci0: at device 4.2 (no driver attached) pci0: at device 4.3 (no driver attached) pci0: at device 9.0 (no driver attached) pcm0: port 0xa400-0xa41f irq 5 at device 10.0 on pci0 pci0: at device 11.0 (no driver attached) ahc0: port 0x9400-0x94ff mem 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs pci0: at device 13.0 (no driver attached) pci0: at device 17.0 (no driver attached) atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atkbdc_probe,110 atspeaker0 port 0x61 on acpi0 atkbdc_probe,110 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc_probe,110 ppc0 port 0x378-0x37f irq 7 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 atkbdc_probe,110 ppc1: cannot reserve I/O port range atkbdc_probe,110 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A atkbdc_probe,110 sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: unable to allocate the IRQ resource (12). psm1: unable to allocate the IRQ resource (-1). ppc1: cannot reserve I/O port range orm0: at iomem 0xcc000-0xcc7ff on isa0 fdc1: cannot reserve I/O port range (6 ports) ppc1: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Waiting 2 seconds for SCSI devices to settle acpi_cpu0: set speed to 100.0% acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.2% Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) linprocfs registered xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x9800-0x987f mem 0xd500-0xd57f irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:01:02:b1:64:c6 miibus0: on xl0 xlphy0: <3c
Re: my psm0 doesn't work with new acpi :(
>> Please apply the attached patch in /sys/isa and see what it does.
>It does panic with a smiling face ;-)))
>
>panic message was "bad ivar read request"
Would try the following patch for /sys/isa/psm.c IN ADDITION TO
my previous patch?
(This is a test patch. It's not a final fix.)
Kazu
--- psm.c-save Tue Sep 4 20:51:39 2001
+++ psm.c Tue Sep 4 22:29:49 2001
@@ -779,12 +779,8 @@
psmidentify(driver_t *driver, device_t parent)
{
-/* if we are in PnP mode, don't create a device node for now... */
-if (isa_get_vendorid(parent) != 0)
- return;
-
/* always add at least one child */
-BUS_ADD_CHILD(parent, 0, driver->name, -1);
+BUS_ADD_CHILD(parent, 0, NULL, -1);
}
#define endprobe(v){ if (bootverbose)\
@@ -814,6 +810,17 @@
BUS_READ_IVAR(device_get_parent(dev), dev, KBDC_IVAR_IRQ, &irq);
BUS_READ_IVAR(device_get_parent(dev), dev, KBDC_IVAR_FLAGS, &flags);
+/* see if IRQ is available */
+rid = 0;
+sc->intr = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, irq, irq, 1,
+ RF_ACTIVE);
+if (sc->intr == NULL) {
+ if (bootverbose)
+device_printf(dev, "unable to allocate the IRQ resource (%d).\n",
+ (int)irq);
+return (ENXIO);
+}
+
sc->kbdc = atkbdc_open(device_get_unit(device_get_parent(dev)));
sc->config = flags & PSM_CONFIG_FLAGS;
/* XXX: for backward compatibility */
@@ -1083,19 +1090,8 @@
endprobe(ENXIO);
}
-/* see if IRQ is available */
-rid = 0;
-sc->intr = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, irq, irq, 1,
- RF_ACTIVE);
-if (sc->intr == NULL) {
-printf("psm%d: unable to allocate the IRQ resource (%d).\n",
- unit, (int)irq);
-endprobe(ENXIO);
-} else {
- bus_release_resource(dev, SYS_RES_IRQ, rid, sc->intr);
-}
-
/* done */
+bus_release_resource(dev, SYS_RES_IRQ, rid, sc->intr);
kbdc_set_device_mask(sc->kbdc, mask | KBD_AUX_CONTROL_BITS);
kbdc_lock(sc->kbdc, FALSE);
return (0);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Tue, 4 Sep 2001, Ilmar S. Habibulin wrote: ISH> ISH> ISH>On Tue, 4 Sep 2001, Harti Brandt wrote: ISH> ISH>> ISH>panic message was "bad ivar read request" ISH>> it fails in acpi_read_ivar with an index (3rd argument) of 12. And that ISH>> looks like the IRQ, so probably there is something really wrong. ISH>Sorry, wrong with my hands or code is broken? While browsing through ISH>-current and -acpi lists i saw many working dmesgs, i mean there was psm0 ISH>and it detected attached mouse. With the code. I have the same problem as you: the new kernel fails to attach psm0. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Tue, 4 Sep 2001, Harti Brandt wrote: > ISH>panic message was "bad ivar read request" > it fails in acpi_read_ivar with an index (3rd argument) of 12. And that > looks like the IRQ, so probably there is something really wrong. Sorry, wrong with my hands or code is broken? While browsing through -current and -acpi lists i saw many working dmesgs, i mean there was psm0 and it detected attached mouse. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Tue, 4 Sep 2001, Ilmar S. Habibulin wrote: ISH> ISH> ISH>On Tue, 4 Sep 2001, Kazutaka YOKOTA wrote: ISH> ISH>> Please apply the attached patch in /sys/isa and see what it does. ISH>It does panic with a smiling face ;-))) ISH> ISH>panic message was "bad ivar read request" it fails in acpi_read_ivar with an index (3rd argument) of 12. And that looks like the IRQ, so probably there is something really wrong. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
On Tue, 4 Sep 2001, Kazutaka YOKOTA wrote: > Please apply the attached patch in /sys/isa and see what it does. It does panic with a smiling face ;-))) panic message was "bad ivar read request" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my psm0 doesn't work with new acpi :(
>So i can't use X server. The problem appeared right after i've compiled
>and installed freshly cvsuped kernel after new acpi first commit (31.08).
>I'm sending dmesg and kernel config files in attach, and waiting for
>help/comments. Thank you.
Please apply the attached patch in /sys/isa and see what it does.
Thank you.
Kazu
begin 666 atkbdcident.diff.gz
M'XL("%:OE#L V%T:V)D8VED96YT+F1I9F8 Q5C_4^)*$O\Y_!7SO"H?D" )
M("C6[JTK7"UUZ\J)N[?WK5(Q&30E)+Q)T.=Y_N_7W3-))A#4MU?UCK),,M/=
MTU\_,SV3*."_#IF7WET'OALFWH%?>_>__VJ79S,V#Q=\R-J)\-MGWV;T3!Z3
M-BS2UM>S[FN"IR+D]V%TPP0\DC".F'/0Z=2"<#YGK35K"?PLJ]EJM4H#1L>V
MG;9]U.[:S#X>.H?#3L<@*:9I5E$>M^T><^RA/1CVG-J'#ZS5MZT^,_L=ZXA]
M^%!C-9:D7AKZ+(Q20PE8B?B:UP/0TN=NRN"E<5)%YZ6IY]]N$IJ*,!O.J8/
M]6_#15 P7*\3"P6R6 1<6,R_]01K1MZ26S73@!]-KJ,PK59@)>"C4NCKR@ON
M!6YX[XD7.*5R(>:/56.DT!I&5JF ^>:]MP#1Z--!!WTZZ%L#\JDQ&G\['U]]
MNAAELI-ULN)18!FPA'O#(RY"/QML6%4<@B=K<$.)08XA/7BGX$"2W+G6EKLW
MY".UYC>KPI<5'+FWK"W_55 _B##E9?)B".C19T[G&)WF='LJ$XUGS$:#"Q$+
M]H[IN>AB"F2>N>%I_MVPV"H6J2T?#F:?$"Y^F+3;[V\R]',_&][J6
MTY66 S:L1<1(:Q".CFBIC+V/PZ#6TF(JO5 OIZD?1TFJET]1.+764ZV512&O
MR>8=O)[ 1#Y"D<<1K!$CA3=\!U]FUKF8'Y#S:UZ72Z!XB^T%@#?7"Q[L66P_
M;9#3V?X^2]E/Y/Z6H-$Z7B3RAU:ZFW*!^*7S2]203*:KV'
M"5 3W6#P1<(W)UK.V]>8+[R;I'H5FJI>)YNRY4(4'OA4\2J!J<6*]1I:4!.H
M%*RXI"Y+G=W)M&\]@T@-$FOL!4"OL2?(4$60Q//4Q_1)_#Q5I)4!/JC\LC&L
M$OK(TEI^B;#(LA#?BMPU5.XV WS*\D1)A=FEVD>1B0^3S7I9/=9L-C0&&E4<
M6($=Q[$ZAU"!1P.K>YQCC_%F,; DV@]%:K2;\(\UV6D0,$AII6>"!3D/;]:"
M!RR-V35GTK7R4RYC'Q!K&_ZCN64C<40S%/RE4L%X@%!R5B^R;@[[D[OT4@C<
M?@A9%D@G[@(,LDS4(O"I3B?WQ%[_^WSJR$]T5.
M*\!78 N*F<\U<^NX4C-_Z+RB :[Y!&6P W#-+< U<\ %77X8'LUJ>#1U>#0S
M>&1?OG[^+-?;"2MD:@E6I"S%\(YDZ#)S1,S7P!K]578QG0]T^)YH#<[OW-^\TMXX=JF]
M<>R2DGEW4VI9!NV.S9SNT#X<=GL&RIG,(C1 A^V''0*()+"#M]JP&2X>O,>$>;CKIPR[ -@3(BXK%/=&T_CX=>:>
MCD;NV:?)YU%=BJ >0HIOO9<0@MV$N5G0;%="9:6^2I:_3Y'30CO+N]LOE7>W
MKQ3#PJ8W5:G==J?/G,ZP9P\/!P;Q84GK)%3,]O'PL#,\[*MC6A^#C0_55D/[
M33_<:INTXUIL&:\3CJZ#+1]&&S+[(43S=>2GJ":X,8W3QQ6M.ZUH2%.%OE.L3F2@RBF,WE4SQ5\D"7DV&/NC:=%O3M1WE S!,TJ@T@B]
M,^&E'$T%^W85/BRT4?8,$WDDA8$J7,P]>*/]C :9FU[&@MQ-U632
M-T0F7Q4.#(X< H(C0(*!0GJP!L@ROX"*XA$:;[",XLXVBE^SXZVECZD'B\")
MX '.\P*]QJ;1%%(PP/-G'/T,;8S@$ OF95&*8([-8P$O#P<'!^1>2F$X5B!T
MX_'HGD=!#&V1 HE&?BK)FEDS7_MUW$'"-T)/RVFH,S#[0\#A2,[!:PIU[AO&
MDU+S.HY3X+J.$]Z@.[!_RJNP5DN-G@"A&G_I)ULKL#=+32^YJR=^ZSU.0"'#
M9^,$A%#M8V2[4/R#X[YU)"-,(#FZG'P;7[KG%Z.OG\=U"**ECL4697@6/WI7
M&SU9;LN3%#0S)O0R5[=API*U?Y>P]8H!37@3+3EFRES$2S;],OTXN9A1RW-Z
M-IT<(%,;^3,_36?G9T#E*G6^G)Z/#6,/5O57T6JOV&D,[?A!)8'SVA&D1)A7
M3XF81DXVZ631E CET,EV2Z-C %&^NOUK-5SHT+"J2+5"UK0@6OA[(M]#Z,S2
M_IL77.X16;12G0KGHK@-[7'( 1T1Q:*8T59/42JMI%HG+#7DE9COR]?" :#F
MKT[7G@=VSX'S_'36[LB-A6[N]MBS1XWYL2-ES/]>/58WT#?[EMAIL PROTECTED];"\+DF1)39>[B&%O!IDBU;[]>!VE
M1<\E^^*TN+!$&,CO*R__0J6R3T+@25*V9EK&=]S!FJS3'N\2DEO.;OCC]>Q
M)P*\=$E%O%A )I&[T=Q$-Y?P8M->9:ZT]D2Q!7S!4_Z2HQJY8H#KH 8=-/"B
MA^Y):$M'Y2+^P#"H4B-E6*G8@2&[I #],D@NI4>I#C=.A.5TD&!81'PR.W6Q
MEJ:7%Q_'^@VZC(>Z0Z=[%*TP&CNC /\ /R>T!>(E#IBKULQV/#B&H-T)7@WA
M)8+D4/LBAH^\ 22"']!<.[\M*6X-Z'ZH=/FRI3/=?9QM@H0\(U;=%N;)IM:"
M_E^7C>[F:H[Z^!%D[]75Z=FG\4BZHURCV:Y3-.F0"7>
Re: my psm0 doesn't work with new acpi :(
>So i can't use X server. The problem appeared right after i've compiled >and installed freshly cvsuped kernel after new acpi first commit (31.08). >I'm sending dmesg and kernel config files in attach, and waiting for >help/comments. Thank you. Please apply the attached patch in /sys/isa and see what it does. Thank you. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
