At 10:55 PM +0200 4/4/04, Martin Blapp wrote: >Hi, > >During testing I found that the following procedure is pretty >dangerous and leads sometimes to a panic(): For the times when it does not cause a panic, does it cause any other problems? Ie, would it be better to say "procedure is pretty dangerous *because* it sometimes causes a panic"? Or is there some other problem in addition to the possible panic? >I'm trying to reproduce it tomorrow for a useful dump. I had it >happen twice but was not able to take any notices because it >happenend on a productive server. I can exclude any hardware >problems. We use current from a week ago. What kind of hardware are you doing this on? Is it multi-CPU? Does it have a lot of RAM? (I am just curious...) Once you have a dump, you might want to include Kirk McKusick <mckusick_at_beastie.mckusick.com> on a message with a pointer to the dump. I don't know how often he reads freebsd-current. -- Garance Alistair Drosehn = gad_at_gilead.netel.rpi.edu Senior Systems Programmer or gad_at_freebsd.org Rensselaer Polytechnic Institute or drosih_at_rpi.eduReceived on Sun Apr 04 2004 - 12:20:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:49 UTC