> Hi all, > > I'm on build 48 now, and I still don't get it. I am > using Caper's frkit > though, so that MIGHT make a difference. >
I'm also using Casper's frkit and running it shows that things appropriate to the machines are up-to-date. powernow is not appropriate as the machines have 32-bit Intel processors. I've got snv_47 on an older IBM A21p (P3-850 MHz with 512 MB at home) and a newer IBM T43p (P-M 2.1 GHz with 2 GB at work). > inetmenu deconfigures your interface if you haven't > done so on the way > down, so that shouldn't be an issue. What nameservice > are you using? I > almost never use NIS, and use DHCP-NoNIS. I always use DHCP-NoNIS at home and at work. I get the shutdown hang intermittently at both locations if I don't run inetmenu by hand and select deconfigure before running the shutdown command (shutdown -i5 -y -g0). I just tried making things more verbose per Tom's suggestion by doing: [a21p:/]# svccfg -s system/svc/restarter:default svc:/system/svc/restarter:default> addpg options application svc:/system/svc/restarter:default> setprop options/logging = astring: verbose svc:/system/svc/restarter:default> exit [a21p:/]# That certainly makes things chatty on the console during boot but it doesn't seem to change anything during shutdown. I'm a total novice at SMF and so on so I just blindly followed his instructions assuming that the \ at the end of one line was a continuation ... Stuart > > Very happy to fix it, but I can't reproduce the > problem. :-( > > Mike > > Tom Whitten wrote: > > Stuart F. Biggar writes: > > > >>> Stuart F. Biggar writes: > >>> I've also seen it occasionally on a Dell 600m > laptop. > >>> I haven't seen it > >>> ince upgrading to snv_47. Since it only happens > >>> occasionlly, though, I > >>> don't know for sure that it won't happen on > snv_47 > >>> the next time I shut > >>> down. > >>> > >>> tom > >>> > >> Tom, > >> > >> I've now updated to snv_47 and I still sometimes > get a hang. > >> More interesting is the message I get (at least > sometimes) > >> when I run inetment at the command line to > deconfigure > >> an interface before I shutdown. I've found that > having > >> the interface deconfigured prior to shutting down > almost > >> always works. The message comes after I run > >> > >> inetmenu -t -i bge0 > >> > >> and select 1) Deconfigure > >> > >> I then get: > >> > >> Sep 18 04:52:33 t43p /sbin/dhcpagent[722]: unable > to retrieve interface flags on bge0 > >> Interface: bge0 > >> Deconfigured > >> # > >> > >> If I run ifconfig -a the only plumbed interface is > the loopback so it looks like > >> deconfiguring worked. The machine also shuts > down. > >> > >> It has also happened with an older notebook with > an iprb0 interface running snv_47. > >> > >> Interesting ... > >> > >> I haven't yet tried making things more verbose. > >> > >> Stuart > >> > >> > >> This message posted from opensolaris.org > >> _______________________________________________ > >> laptop-discuss mailing list > >> laptop-discuss at opensolaris.org > >> > > > > Since sending out my original mail, I too have > encountered the problem on > > snv_47. Today, I'm upgrading to snv_48. If I see > the problem there, I'll > > turn on the the verbose stuff. > > > > tom This message posted from opensolaris.org
