Brian Utterback wrote: > Mike Ramchand wrote: >> Brian, >> >> Two points: >> >> To run as non-root user, you simply need to create a profile in >> /etc/user_attr >> >> <username>::::type=normal;profiles=Ginetmenu > > I know. As I said, I used to be able to do it without > a problem. And it helped to do the truss, which had > to be done by root to truss across the pfexec. But the > inetmenu was still running as me. > >> >> >> Given that inetmenu is a script, it simply calls ifconfig, wificonfig, >> to do the right thing. It should be possible to figure out at which >> point it hangs. > > I am pretty sure that it is hanging in ifconfig, although the > truss does not show it. It is possible (likely) that the > truss file is behind because of the hang. The core file shows > an ifconfig child process to the inetmenu script. > >> >> P.S. Are you using the latest version of inetmenu? >> Does this EVER happen with your ethernet interface? >> Which wireless driver are you using? Is it the latest version? > > I am using version 1.9. I don't think it has ever happened with the > ethernet interface. I am using bcmndis. I think I am using ndis wrapper > 1.6. > > > Also, when I run inetmenu as route and choose the bcmndis0 interface > to configure, I get an error message from the "tr" command. > > I just noticed that I get some warnings in the messages file: > > May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0xc0786981 > May 24 16:59:13 metatron bcmndis: [ID 975483 kern.notice] > ndis_gld_ioctl: unknown cmd 0xc0786981 > May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x40586993 > May 24 16:59:13 metatron bcmndis: [ID 975483 kern.notice] > ndis_gld_ioctl: unknown cmd 0x40586993 > May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x1004 > May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x1003 > May 24 16:59:15 metatron last message repeated 1 time > May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x1004 > May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x1002 > May 24 16:59:15 metatron last message repeated 1 time > May 24 16:59:15 metatron bcmndis: [ID 428280 kern.notice] in the cfg > essid!! > May 24 16:59:15 metatron bcmndis: [ID 178118 kern.notice] bssid=utterbacks > May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x1002 > May 24 16:59:15 metatron last message repeated 1 time > May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x1003 > May 24 16:59:15 metatron bcmndis: [ID 141910 kern.notice] link up > May 24 16:59:16 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0x1003 > May 24 16:59:16 metatron last message repeated 1 time > May 24 16:59:27 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0xffffffff > May 24 16:59:27 metatron bcmndis: [ID 975483 kern.notice] > ndis_gld_ioctl: unknown cmd 0xffffffff > May 24 16:59:30 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0xffffffff > May 24 16:59:30 metatron bcmndis: [ID 975483 kern.notice] > ndis_gld_ioctl: unknown cmd 0xffffffff > May 24 16:59:30 metatron bcmndis: [ID 446631 kern.notice] > ndis_gld_ioctl: cmd 0xffffffff > May 24 16:59:30 metatron bcmndis: [ID 975483 kern.notice] > ndis_gld_ioctl: unknown cmd 0xffffffff > > However, these message look like they date back to when the bcmndis0 > driver was installed, before I had the problem. > > Any suggestions about how to figure out what ifconfig was doing > when the thing hung? >
Okay, given that inetmenu calls ifconfig, and the child process ifconfig is in the process list, I think we are safe assuming that the system is hanging in ifconfig. So, mucking about with mdb, I was able to print out the kernel thread stack, which may provide a clue. stack pointer for thread d5b70c00: d3fc145c d3fc14c8 fakesoftint_return+2() d3fc14fc pci_peekpoke_check+0x95() d3fc1544 pci_ctlops+0x6f() d3fc1564 ddi_ctlops+0x31() d3fc15a4 i_ddi_caut_getput_ctlops+0x47() d3fc15ec i_ddi_caut_get8+0x25() d3fc1604 pci_config_get8+0x20() d3fc1630 pci_lcap_locate+0x62() d3fc1658 pci_get_msi_ctrl+0x7a() d3fc1694 pci_msi_get_supported_type+0x4e() d3fc1724 pci_common_intr_ops+0x792() d3fc1748 pci_intr_ops+0x1a() d3fc178c i_ddi_intr_ops+0x36() d3fc1810 i_ddi_intr_get_supported_types+0x3f() d3fc1828 i_ddi_intr_devi_init+0x2b() d3fc18b8 ddi_intr_alloc+0x12a() d3fc18f4 ddi_add_intr+0x2f() d3fc19a4 ndis_attach+0x430() d3fc19d8 devi_attach+0x6c() d3fc19f8 attach_node+0x80() d3fc1a28 i_ndi_config_node+0xaf() d3fc1a48 i_ddi_attachchild+0x35() d3fc1a64 devi_attach_node+0x6b() d3fc1ac8 devi_config_one+0x449() d3fc1b0c ndi_devi_config_one+0x85() d3fc1b5c dv_find+0x175() d3fc1b80 devfs_lookup+0x22() d3fc1bc0 fop_lookup+0x32() d3fc1d4c lookuppnvp+0x2c8() d3fc1d94 lookuppnat+0xea() d3fc1e10 lookupnameat+0x54() d3fc1efc vn_openat+0x153() d3fc1f68 copen+0x287() d3fc1f84 open+0x1b() d3fc1fac sys_call+0x100() Hope that helps. -- blu Rose are #FF0000, Violets are #0000FF. All my base are belong to you. ---------------------------------------------------------------------- Brian Utterback - OP/N1 RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
