Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
> You're kidding, right? Nope.. Apparently I suffer from lack of sleep, and GDB syndrome, I looked right at the crash line, and didn't even pay attention to what was above it. My apologies for that - didn't even notice it. > You were asked to send a ps and a trace. You sent "what you > thought was required", which was not what was asked for. See above. > You were told by a developer that what you sent was not useful. > > And now you whine that life is unfair and you are oppressed. > > If what you are after is a shiny, happy computing experience > with a loving and dedicated support staff there to coddle > your every partial bug report and politely ask you for more > information and refer to you as Sir or Mr. Wolfpaw, you are > using the wrong OS. Not really - my point still somewhat remains - I was not claiming things should be all shiny and nice, but honestly, I would submit that if someone tries to submit a bug report, and may be doing it wrong, hostility isn't required - a simple - hey your not doing this right.. might be more conducive of a positive response from folks that have not submitted a crash report before. That's all I was trying to point out - I admit I made an error in not reading the screen fully.. But not realizing that, I would say its fairly understandable to see why one would get a hostile response from someone who doesn't realize they have committed a taboo. > Quit feeling sorry for yourself. If you truly want to help, > recreate the crash, send a full bug report chock full of > useful and required information, and go on with life. No idea what caused it, so its not possible for me to recreate it.. As I said before, if there is other information (such as ddb.log) somewhere on the machine that I can send in, I would happily do so. > crash(8) may be a useful read. Agreed D.
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
From: Wolfpaw - Dale Corse [mailto:[EMAIL PROTECTED] > Not sure what instructions on which screen you are even talking about. > All I saw was it was in DDB, so I looked around, and sent what info > I thought was required. This is why I am so confused, and fairly > offended as to the nasty tone of the responses You're kidding, right? You were asked to send a ps and a trace. You sent "what you thought was required", which was not what was asked for. You were told by a developer that what you sent was not useful. And now you whine that life is unfair and you are oppressed. If what you are after is a shiny, happy computing experience with a loving and dedicated support staff there to coddle your every partial bug report and politely ask you for more information and refer to you as Sir or Mr. Wolfpaw, you are using the wrong OS. Quit feeling sorry for yourself. If you truly want to help, recreate the crash, send a full bug report chock full of useful and required information, and go on with life. crash(8) may be a useful read. DS
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Wolfpaw - Dale Corse > Sent: Tuesday, October 18, 2005 1:43 PM > To: 'Peter Hessler' > Cc: misc@openbsd.org > Subject: Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite > sure which it originates from) > > Not sure what instructions on which screen you are even talking about. > All I saw was it was in DDB, so I looked around, and sent what info > I thought was required. This is why I am so confused, and fairly > offended as to the nasty tone of the responses > For some of us, this might be the first time we have ever done a crash report with OpenBSD. For the developers, they have endured 10 years of unhelpful crash reports and may sometimes take it out on you if you repeat the obvious mistakes of past users. Even following the directions can be hard. No only should you submit the output from three tools, but you should do so in a single email. I received swear words when I sent a separate email for each output, but it was sent only to me and not the list, so I figured it was their way of saying the liked me. ;) There is a culture of harsh language within OpenBSD. I don't think it will change. Find humor in it.
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
Not sure what instructions on which screen you are even talking about. All I saw was it was in DDB, so I looked around, and sent what info I thought was required. This is why I am so confused, and fairly offended as to the nasty tone of the responses D. > -Original Message- > From: Peter Hessler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 18, 2005 11:35 AM > To: Wolfpaw - Dale Corse > Cc: misc@openbsd.org > Subject: Re: OpenBSD Kernel Crash in uvm_fault or > uvm_rb_remove (not quite sure which it originates from) > > > You refused to follow the instructions printed on the screen. > Why are > you suprised to the tone of the responses? > > Now, if you gave the information requested, you would have received a > very different tone of reply. Not knowing what to do is one > thing, but > blatently ignoring instructions is another. > > > > On Tue, Oct 18, 2005 at 11:10:00AM -0600, Wolfpaw - Dale > Corse wrote: :Shrug.. Ok .. I'll keep my bug reports to > myself from here on in, since :it seems someone asking for > some help, which may not realize the information :provided > was not entirely what was required is to receive a fairly > rude reply, :which, rather then saying - hey, please send > this.. It would be helpful, :lambastes someone, and says > RTFM. Not very friendly at all. My apologies :for the > intention of trying to help you folks with what may be a > serious :bug (or may not, but crashed none the less, which > should not happen, :especially where it concerns an OS that > promotes security and stability.) :I would more then happily > send anything that is required, but I have :no time, or > tolerance for rudeness. > : > :I shall leave the list, and no longer insult your guruness > with my :simple presence. > : > :D. > : > > -- > Q: What's a light-year? > A: One-third less calories than a regular year.
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
You refused to follow the instructions printed on the screen. Why are you suprised to the tone of the responses? Now, if you gave the information requested, you would have received a very different tone of reply. Not knowing what to do is one thing, but blatently ignoring instructions is another. On Tue, Oct 18, 2005 at 11:10:00AM -0600, Wolfpaw - Dale Corse wrote: :Shrug.. Ok .. I'll keep my bug reports to myself from here on in, since :it seems someone asking for some help, which may not realize the information :provided was not entirely what was required is to receive a fairly rude reply, :which, rather then saying - hey, please send this.. It would be helpful, :lambastes someone, and says RTFM. Not very friendly at all. My apologies :for the intention of trying to help you folks with what may be a serious :bug (or may not, but crashed none the less, which should not happen, :especially where it concerns an OS that promotes security and stability.) :I would more then happily send anything that is required, but I have :no time, or tolerance for rudeness. : :I shall leave the list, and no longer insult your guruness with my :simple presence. : :D. : -- Q: What's a light-year? A: One-third less calories than a regular year.
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
Shrug.. Ok .. I'll keep my bug reports to myself from here on in, since it seems someone asking for some help, which may not realize the information provided was not entirely what was required is to receive a fairly rude reply, which, rather then saying - hey, please send this.. It would be helpful, lambastes someone, and says RTFM. Not very friendly at all. My apologies for the intention of trying to help you folks with what may be a serious bug (or may not, but crashed none the less, which should not happen, especially where it concerns an OS that promotes security and stability.) I would more then happily send anything that is required, but I have no time, or tolerance for rudeness. I shall leave the list, and no longer insult your guruness with my simple presence. D. > > > > > It dropped to DDB (because I forgot to disable it :( > and I did > > > > > The following: > > > > > > > > First thing you should probably do is actually read what is > > > > on the screen and actually send the output of ps, trace and a > > > > dmesg(8). Else, you're not going to get much reliable support. > > > > > > > > RTFM -- it's a good catch phrase. Tell your friends, > and enemies. > > > > > > Wow.. That's really helpful, thanks! > > > > It is actually. > > I agree 100%. > > > > Considering it was 1AM when I got there, and it wouldn't write > > > anything to disk, I suppose your suggesting that I copy > the entire > > > ps output to a pad of paper? > > > > Yes, if you have to. I think ddb.log is set to true by default > > though. And you didn't mention that boot dump failed in > your email. > > You should read both the crash and the ddb man pages. > > When I get see a bug report that is incomplete I simply > delete it. Only in exceptional cases do I send more mail back to ask. > > > > and I did send the trace. > > > > No you didn't. > > > > > What was in the dmesg is also in that email.. > > > > Which isn't helpful or what was asked for. You are supposed to > > include a dmesg. Not whatever lines from it you think is relevant, > > the entire thing. > > > > > Sorry to sound snarky, but this response it a little over > the top. > > > If you don't have anything helpful to add, please, don't bother. > > > > No, that response is far nicer than you deserve. If you > can't grasp > > the very clear statement: "RUN AT LEAST 'trace' AND 'ps' > AND INCLUDE > > OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS > > WITHOUT INCLUDING THAT INFORMATION!", then don't expect > alot of help. > > If you expect people to have "anything helpful to add", then you > > should act like you want help. > > Dale -- we don't help people who don't help us help them. > > I deleted your original post immediately. It had no > information which might help.
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
> On Tue, 18 Oct 2005 09:22:26 -0600 "Wolfpaw - Dale Corse" [EMAIL PROTECTED]> wrote: > > > > > It dropped to DDB (because I forgot to disable it :( and I did > > > > The following: > > > > > > First thing you should probably do is actually read what is > > > on the screen and actually send the output of ps, trace and a > > > dmesg(8). Else, you're not going to get much reliable support. > > > > > > RTFM -- it's a good catch phrase. Tell your friends, and enemies. > > > > Wow.. That's really helpful, thanks! > > It is actually. I agree 100%. > > Considering it was 1AM when I got there, and it wouldn't write > > anything to disk, I suppose your suggesting that I copy the > > entire ps output to a pad of paper? > > Yes, if you have to. I think ddb.log is set to true by default though. > And you didn't mention that boot dump failed in your email. You should > read both the crash and the ddb man pages. When I get see a bug report that is incomplete I simply delete it. Only in exceptional cases do I send more mail back to ask. > > and I did send the trace. > > No you didn't. > > > What was in the dmesg is also in that email.. > > Which isn't helpful or what was asked for. You are supposed to include > a dmesg. Not whatever lines from it you think is relevant, the entire > thing. > > > Sorry to sound snarky, but this response it a little over the top. > > If you don't have anything helpful to add, please, don't bother. > > No, that response is far nicer than you deserve. If you can't grasp > the very clear statement: "RUN AT LEAST 'trace' AND 'ps' AND INCLUDE > OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS > WITHOUT INCLUDING THAT INFORMATION!", then don't expect alot of help. > If you expect people to have "anything helpful to add", then you should > act like you want help. Dale -- we don't help people who don't help us help them. I deleted your original post immediately. It had no information which might help.
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
On Tue, 18 Oct 2005 09:22:26 -0600 "Wolfpaw - Dale Corse" wrote: > > > It dropped to DDB (because I forgot to disable it :( and I did > > > The following: > > > > First thing you should probably do is actually read what is > > on the screen and actually send the output of ps, trace and a > > dmesg(8). Else, you're not going to get much reliable support. > > > > RTFM -- it's a good catch phrase. Tell your friends, and enemies. > > Wow.. That's really helpful, thanks! It is actually. > Considering it was 1AM when I got there, and it wouldn't write > anything to disk, I suppose your suggesting that I copy the > entire ps output to a pad of paper? Yes, if you have to. I think ddb.log is set to true by default though. And you didn't mention that boot dump failed in your email. You should read both the crash and the ddb man pages. > and I did send the trace. No you didn't. > What was in the dmesg is also in that email.. Which isn't helpful or what was asked for. You are supposed to include a dmesg. Not whatever lines from it you think is relevant, the entire thing. > Sorry to sound snarky, but this response it a little over the top. > If you don't have anything helpful to add, please, don't bother. No, that response is far nicer than you deserve. If you can't grasp the very clear statement: "RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!", then don't expect alot of help. If you expect people to have "anything helpful to add", then you should act like you want help. Adam
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
> > It dropped to DDB (because I forgot to disable it :( and I did The > > following: > > First thing you should probably do is actually read what is > on the screen and actually send the output of ps, trace and a > dmesg(8). Else, you're not going to get much reliable support. > > RTFM -- it's a good catch phrase. Tell your friends, and enemies. Wow.. That's really helpful, thanks! Considering it was 1AM when I got there, and it wouldn't write anything to disk, I suppose your suggesting that I copy the entire ps output to a pad of paper? I did look at it, and I did send the trace. Maybe you should read the email before you write a reply. What was in the dmesg is also in that email.. If you'd like me to send you 6 pages of irrelevant console logs, I can do that too.. Though I don't see what good it will do. Sorry to sound snarky, but this response it a little over the top. If you don't have anything helpful to add, please, don't bother. -D.
Re: OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
On Mon, 2005-10-17 at 19:57:31 -0600, Wolfpaw - Dale Corse proclaimed... > It dropped to DDB (because I forgot to disable it :( and I did > The following: First thing you should probably do is actually read what is on the screen and actually send the output of ps, trace and a dmesg(8). Else, you're not going to get much reliable support. RTFM -- it's a good catch phrase. Tell your friends, and enemies.
OpenBSD Kernel Crash in uvm_fault or uvm_rb_remove (not quite sure which it originates from)
Greetings, Saturday evening, one of our firewalls crashed (thankfully carp worked well :) with the following error in the messages file: Oct 15 23:56:41 new-fw /bsd: uvm_fault(0xd676852c, 0x74000, 0, 1) -> e Oct 16 01:14:53 new-fw syslogd: restart Oct 16 01:14:53 new-fw /bsd: OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005 It dropped to DDB (because I forgot to disable it :( and I did The following: >examine uvm_rb_remove+0x144: 5443b60f >print uvm_rb_remove(740c6,6,0,d674629c) uvm_map_p(d676852c,e9015f00,1f5000,0,f,f,0,d057ec88,e9015f10,d 021ad38) uvm_map_p+0x3fb sys_obreak.. syscall+0x2ee Does anyone know what caused this, and how to fix it? Thanks! Dale Dale Corse System Administrator Wolfpaw Services Inc. http://www.wolfpaw.net (780) 474-4095
