In message: <1072398918.7cddfbe0dhee_at_myrealbox.com> "Dheeraj" <dhee_at_myrealbox.com> writes: : i see the following problems in my dell notebook. what kind of Dell notebook? I have a Inspiron 8000. : i just added a simple makefile in src/sys/modules to make it a : module. (else it won't boot at all ) This sounds like an interrupt routing problem of some sort. I too have a sio module, and it works great for me. kldload sio for me yields: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A Expected. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Also expected since I don't have a COM2 on this laptop. sio4: <3Com Megahertz 3CXEM556> at port 0x110-0x117 irq 10 function 1 config 39 on pccard1 So mine has a 3CXEM556 card, not the slightly newer 3CCFEM556B (I'm not sure if my fast ethernet 556 is a normal or a 'B'). sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode This looks normal. Now, let's take a look at yours: : Dec 25 19:33:10 vagisha kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa : 0 : Dec 25 19:33:10 vagisha kernel: sio0: type 16550A : Dec 25 19:33:10 vagisha kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 : Dec 25 19:33:10 vagisha kernel: sio1: type 16550A Standard COM0 and COM1. : Dec 25 19:33:10 vagisha kernel: sio4: <3Com Megahertz 3CCFEM556B> at port 0x120-0x127 irq 11 function 1 config 39 on pccard1 This looks like a card I recently got working (but I don't have the dongle for the modem). Like I said above, can't recall if mine is a 'B' or not. : Dec 25 19:33:10 vagisha kernel: sio4: type 16550A with a buggy IIR_TXRDY implementation This is odd. I really don't recall seeing this message at all (and I don't get it with the older 3cxem556 I'm using while traveling). : Dec 25 19:33:10 vagisha kernel: sio4: unable to activate interrupt in fast mode - using normal mode This is 'normal' for pccard modems. : --- and i have to use the power button to reboot. What happens if you don't have the 3com card installed. : If i compile a custom kernel with serial driver disabled, it works fine. Define: 'works fine' What are you seeing? Also, when it hangs, can you break to the debugger (add options DDB and BREAK_TO_DEBUGGER in your kernel)? If so can you do a 'show intrcnt' to see what interrupt is being 'hammered'. It will likely be the only one larger than rtc :-). If you are having trouble, continue and break again a second or two later. Chances are good that it will be the one that has > 100 more than the last one (and likely > 1000 or 10000!). It likely won't be irq 11. You might also try breaking at siointr. WarnerReceived on Thu Dec 25 2003 - 17:42:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:35 UTC