Date: Mon, 26 Jan 2004 18:13:58 +0100 From: Harald Schmalzbauer <h@schmalzbauer.de> To: Robert Watson <rwatson@FreeBSD.org> Cc: current@freebsd.org Subject: Re: 5.2-rel NFS lockup and networking performance Message-ID: <200401261814.02987@harrymail> In-Reply-To: <Pine.NEB.3.96L.1040126114341.11399K-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040126114341.11399K-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Boundary-02=_arUFAFhH5zgSBlc Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline On Monday 26 January 2004 17:46, you wrote: > On Mon, 26 Jan 2004, Harald Schmalzbauer wrote: > > Thank you. I have set it up but I only get the following lines when > > sending a "~#" via tip: > > ~# > > The following connections are open: > > #0 client-session (t4 r0 i0/0 o0/0 fd 4/5) > > > > A bit googling showed something like "options COMCONSOLE". > > Do I need this? Th message was back from 1996 so I'm not sure what to d= o. > > Sorry, make sure you have: > > console=3D"comconsole" > > in /boot/loader.conf. Nothing further should be required. Did that. I also edited ttys so I can login via serial. No luck so far. Sti= ll=20 the same result when sending the "~#". But since I now have a real console, I found that not the whole machine is= =20 locked up, it seems just networking is frozen for some time. I still have a very interactive console while networking on the same box is= =20 completely dead. Regrettably sysstat doesn't work vi tip so I can't tell you if there were a= ny=20 interrupts on the network interface during the lock. If you're still interested in some traces please give me a hint how I can u= se=20 the serial debuger (I also had a quick look into the developer handbook, bu= t=20 ddb via serial isn't mentioned) Thanks, =2DHarry > > > Breaking to debugger is working on the console. (Which crashes my /home > > each time) Is there a possibility to shutdown the machine "clean" after > > the ddb? Like I mentioned before, this is my production Fileserver :( > > Normally, assuming your machine isn't already hung, you can type in "cont" > to continue, which should allow the system to continue normally. If the > system was hung/generally broken when you entered DDB, you can try "call > boot(0)" to see if you can get it to cleanly sync to disk, but whether > that succeeds depends a lot on how hung/broken the kernel was already. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research --Boundary-02=_arUFAFhH5zgSBlc Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQBAFUraBylq0S4AzzwRApM2AJ4ggE8FeW1K2uFKawtQsG4h/bESgwCgjScc MMekJylRIGsQX/oCj4QWW60= =+LFa -----END PGP SIGNATURE----- --Boundary-02=_arUFAFhH5zgSBlc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401261814.02987>