From: James MacLean (macleajb_at_ednet.ns.ca)
Date: Tue 18 Nov 2003 - 01:17:31 GMT
Hi Herbert,
Been too long since I've been playing with kernel oops :(. I started to
write down the Oops screen and got too tired too quickly and missed
getting enough info. What happen to it being trapped in
/var/log/<somefile> ? I use to just run ksymoops on that and get what was
needed. Anyhow, for now, if it helps, I have :
Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 39 83 f0 02 00 00 cmp %eax,0x2f0(%ebx)
Code; 00000006 Before first symbol
6: 0f 84 74 01 00 00 je 180 <_EIP+0x180>
Code; 0000000c Before first symbol
c: 31 42 48 xor %eax,0x48(%edx)
Code; 0000000f Before first symbol
f: b8 01 00 00 00 mov $0x1,%eax
c024dfe0 T tcp_get_info
c0131b00 T do_mmap_pgoff
c016bcd0 t proc_file_read
c0144350 T sys_read
c014d130 T sys_fstat64
c01092dc T system_call
Again, tcp_get_info is always where it dies. Anyone wishing to enjoy this
experience need only do a "netstat -nap --inet" from the root server when
a vserver it alive... Or atleast, that is all that I do :).
I'll see if I can figure out how to get the rest of the Oops copied in ;(.
JES
On Mon, 17 Nov 2003, Herbert Poetzl wrote:
> On Mon, Nov 17, 2003 at 08:53:56AM -0400, James MacLean wrote:
> > Hi Matt,
> >
> > On my system, when it Oopses, it's down for the count. No ping or
> > anything. Keyboard lights flashing just to point out it's in bad shape :).
>
> when the keyboard leds start to flash, it's a panic
> and you should capture/copy the stack trace (oops) and
> feed it through ksymoops, this way, we could not only
> pity you for the crash, but also try to figure out how
> it happened ...
>
> TIA,
> Herbert
>
> > I saw the oops this morning, but didn't copy all the register data and
> > stack log as it is always so much to pencil down :), and I was hoping this
> > was already being tracked down ;).
> >
> > Maybe I should grab that if 1.1.3 dies tomorrow am?
>
> definitely ...
>
> > JES
> >
> > On Mon, 17 Nov 2003, Matt Ayres wrote:
> >
> > > I have 2 servers who keep crashing, sometimes every few hours... I am
> > > still working on a console solution so I don't know the exact place
> > > where the problem is.
> > >
> > > The servers are in a "half hung" state, they respond to PING and will
> > > open TCP connections, but they won't send any data back.
> > >
> > > Is this how yours responds or is it a hard lock?
> > >
> > > I've tried with 2.4.22-c17e, 2.4.23pre8-c17h and 2.4.22-vs1.0.0 all with
> > > the same results.
> > >
> > > On Mon, 2003-11-17 at 06:00, James MacLean wrote:
> > > > Hi folks,
> > > >
> > > > 2 nights in a row at 4:00am when netstat runs, the system is Oopsing. I
> > > > was running vs1.1.2 and am now upgrading to vs1.1.3 but do not see
> > > > anything that suggests a fix in in the diffs.
> > > >
> > > > Possibly I am the only lucky one :)? I remember this happening some time
> > > > ago in earlier vservers, and someone new the fix. The Oops was within
> > > > tcp_get_info if I am reading the System.map correctly.
> > > >
> > > > JES
> > >
> >
> > --
> > James B. MacLean macleajb_at_ednet.ns.ca
> > Department of Education
> > Nova Scotia, Canada
> > B3M 4B2
> >
> >
> > _______________________________________________
> > Vserver mailing list
> > Vserver_at_list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
>
--
James B. MacLean macleajb_at_ednet.ns.ca
Department of Education
Nova Scotia, Canada
B3M 4B2
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver