From: FD Cami <francois.cami@free.fr>
To: "Alessandro Suardi" <alessandro.suardi@gmail.com>
Cc: "charles gagalac" <charles.gagalac@gmail.com>,
"daryll q" <daryll_26m@yahoo.com.ph>,
linux-kernel@vger.kernel.org
Subject: Re: Hang in 2.6.23-rc5
Date: Sun, 2 Sep 2007 23:29:39 +0200 [thread overview]
Message-ID: <20070902232939.f2c8acbb.francois.cami@free.fr> (raw)
In-Reply-To: <5a4c581d0709021338s1e9e0dc0md490a032781b60e8@mail.gmail.com>
On Sun, 2 Sep 2007 22:38:28 +0200
"Alessandro Suardi" <alessandro.suardi@gmail.com> wrote:
> On 9/2/07, charles gagalac <charles.gagalac@gmail.com> wrote:
> > On 9/2/07, daryll q wrote:
> > > Upgraded my kernel from 2.6.23-rc2 to 2.6.23-rc5.
> > >
> > > System hangs (caps lock and scroll lock leds are both flashing).
> > >
> > > It *randomly* happens but most of the time during after login to
> > > KDE.
> > >
> > > I have not investigated it yet because I have not tried doing
> > > it before.
> > >
> > > Also the system is really not responding so I can't do much..
> > > Just hope it blue screen so I can send the error code easily :)
> >
> > i experienced hangs, with the flashing caps and scroll locks as
> > you've described, in a few of my later pulls prior to rc5. i
> > couldn't reproduce the hangs and my logs didn't show evidence of a
> > problem. my system under rc5, so far, hasn't hung on me.
> >
> > charles
>
> Oh, I thought I was the only one. I also had a single hang+flashing
> Caps & Scroll Lock with -rc5, but haven't had one since.
>
> I had VMWare Player modules loaded at the time though, and I
> recently rebuilt them with the any-any-patch-113 (earlier versions
> would not build with very recent kernels).
>
> -rc4-git2 and -git3 never hung even with VMWare modules loaded.
>
> So I disabled the autoload of VMWare stuff. The problem has not
> reproduced so far. My system is a Dell D610, running updated
> Fedora 7, with Intel 915GM video chipset.
I've just had a kernel panic, running a vanilla 2.6.23-rc5, no
proprietary modules loaded, running X11 under moderate load.
2.6.23-rc[2-4] have been rock solid on the same box. I've reverted
to rc4 for now.
François
next prev parent reply other threads:[~2007-09-02 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 18:42 daryll q
2007-09-02 19:05 ` charles gagalac
2007-09-02 20:38 ` Alessandro Suardi
2007-09-02 21:26 ` Satyam Sharma
2007-09-02 21:29 ` FD Cami [this message]
2007-09-02 21:46 ` Alexey Dobriyan
2007-09-02 22:45 ` Satyam Sharma
2007-09-02 23:10 ` Alessandro Suardi
2007-09-03 6:39 ` Patrick Mau
2007-09-04 9:32 ` Romano Giannetti
2007-09-05 17:11 ` Jean Delvare
2007-09-05 22:02 ` Satyam Sharma
2007-09-08 9:37 ` FD Cami
2007-09-03 21:04 ` Robert Fitzsimons
2007-09-02 22:05 ` Richard Mittendorfer
2007-09-02 22:14 ` Jesper Juhl
2007-09-02 20:21 Andrew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070902232939.f2c8acbb.francois.cami@free.fr \
--to=francois.cami@free.fr \
--cc=alessandro.suardi@gmail.com \
--cc=charles.gagalac@gmail.com \
--cc=daryll_26m@yahoo.com.ph \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®