public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jacky Liu" <jq419@my-deja.com>
To: linux-kernel@vger.kernel.org
Cc: hahn@coffee.psychology.mcmaster.ca
Subject: Re: 2.4.4 kernel freeze for unknown reason
Date: Tue, 15 May 2001 00:13:58 -0700	[thread overview]
Message-ID: <200105150713.AAA18791@mail7.bigmailbox.com> (raw)

Hi everyone,

Mark, I got your point about the dma/udma stuffs. My hdparm setting is UDMA w/ MultiSector 16..

I had recompiled my kernel and disabled the FB option but my linux box still hanged (another completely freeze) yesterday... Oh well..

I have been tracking this thread for a few days and it seem the source of this problem is related to swap space. Vincent, would you mind to send me the patch for swap space problem if Alan had sent it to you? So I can test it on my machine and report the result later.

Mark, please suggest a setting for the hdparm so I can test it on my machine. Thanks alot for your time.

Best Regards,
Jacky Liu


>Date: Thu, 10 May 2001 23:20:17 -0400 (EDT)
>From: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
>To: Jacky Liu <jq419@my-deja.com>
>SUBJECT
>> You are right for the other assumption, I am running the harddisk in UDMA w/32bits mode. Are you suggesting me to turn off both functions? But if I turn them off, the performance will decrease alot.
>
>the only thing that matters is dma/udma or not.  32b mode is irrelevant
>to the actual dma/udma transfer, as is -m settings.  even -u has no
>measurable effect.
>
>> Is there any way I can get any crash information? e.g. any function I can turn on for logging or something?
>
>if your hang is as I'm imagining, there's nothing you can do, since it's
>purely hardware.  you could try compiling in magic sysrq, but I suspect 
>the hardware is hung.




------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/

             reply	other threads:[~2001-05-15  7:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-15  7:13 Jacky Liu [this message]
2001-05-16  5:25 ` 2.4.4 kernel freeze for unknown reason Vincent Stemen
  -- strict thread matches above, loose matches on Subject: below --
2001-05-29  3:59 Vasco Figueira
2001-05-11  2:26 Jacky Liu
2001-05-10  3:57 Jacky Liu
2001-05-11 18:45 ` Vincent Stemen
2001-05-11 18:46   ` Alan Cox
2001-05-12  6:05     ` Mike Galbraith
2001-05-12 11:18       ` Alan Cox
2001-05-12 13:45         ` Mike Galbraith
2001-05-12 14:25           ` Alan Cox
2001-05-12 15:33             ` Mike Galbraith
2001-05-13 18:16       ` Christoph Rohland
2001-05-14  4:36         ` Mike Galbraith
2001-05-13  6:17     ` Vincent Stemen

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=200105150713.AAA18791@mail7.bigmailbox.com \
    --to=jq419@my-deja.com \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --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