public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: Lukasz Trabinski <lukasz@trabinski.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.25-pre6
Date: Thu, 29 Jan 2004 17:12:18 +0300	[thread overview]
Message-ID: <871xpirghp.wl@canopus.ns.zel.ru> (raw)


Lukasz Trabinski wrote:
> On Tue, 20 Jan 2004, Xose Vazquez Perez wrote:                                         
> > as usual:                                                                            
> >                                                                                      
> > - run memtest86+ [1] and cpuburn [2] to check the HW.                                
> > - update the firmware(MOBO BIOS and BackPlane/ESM, SCSI, hard disks, ...)            
> >   to latest levels.                                                                  
>                                                                                        
> Hardware is OK, with older kernel (2.4.22?) works fine.                                
This could be misleading, still.

I`ve had a situation in the past when a n+1`th 2.4 kernel had sound crashes
where none of the ...n`th didn`t have any.

I`ve narrowed it down to cpu overclocking... ;-)

It was a very intricate situation for the kernel crashed more or less
after a certain fixed amount of time of sound playing, no matter how
long ago the bootup happened...

regards, Samium Gromoff



             reply	other threads:[~2004-01-30 12:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 14:12 Samium Gromoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-20 22:02 Linux 2.4.25-pre6 Xose Vazquez Perez
2004-01-21  6:49 ` Lukasz Trabinski
2004-01-16 14:11 Marcelo Tosatti
2004-01-16 15:34 ` Maciej Soltysiak
2004-01-20 21:25 ` Lukasz Trabinski
2004-01-20 21:41   ` Marcelo Tosatti
2004-01-21  6:47     ` Lukasz Trabinski
2004-01-21 10:53       ` Marcelo Tosatti
2004-01-21 11:28         ` Lukasz Trabinski
2004-01-21 11:54           ` David Woodhouse
2004-01-21 16:07             ` Lukasz Trabinski
2004-01-21 20:12               ` Marcelo Tosatti
2004-01-28 15:04                 ` David Woodhouse
2004-01-28 17:03                   ` Lukasz Trabinski
2004-02-02 22:24                   ` Lukasz Trabinski
     [not found]                 ` <Pine.LNX.4.58L.0401220929450.18938@logos.cnet>
     [not found]                   ` <Pine.LNX.4.58LT.0401221248560.11640@oceanic.wsisiz.edu.pl>
     [not found]                     ` <Pine.LNX.4.58L.0401221014510.18938@logos.cnet>
     [not found]                       ` <Pine.LNX.4.58LT.0401221334070.2772@oceanic.wsisiz.edu.pl>
2004-02-04 13:26                         ` Marcelo Tosatti
2004-02-04 18:45                           ` Lukasz Trabinski
2004-02-04 23:20                             ` Lukasz Trabinski
2004-01-21 11:01       ` Marcelo Tosatti
2004-01-21 11:07       ` David Woodhouse

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=871xpirghp.wl@canopus.ns.zel.ru \
    --to=deepfire@sic-elvis.zel.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz@trabinski.net \
    /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