public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: davidhart@tqmcube.com
Cc: "bugme-daemon@kernel-bugs.osdl.org" 
	<bugme-daemon@bugzilla.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 8392] New: Hard Lock Subsequent to Boot
Date: Sat, 28 Apr 2007 11:59:06 -0700	[thread overview]
Message-ID: <20070428115906.86e93af6.akpm@linux-foundation.org> (raw)
In-Reply-To: <200704281634.l3SGYhJX014704@fire-2.osdl.org>


(please reply via email, retaining all cc's)

On Sat, 28 Apr 2007 09:34:43 -0700 bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=8392
> 
>            Summary: Hard Lock Subsequent to Boot
>     Kernel Version: 2.6.21/2,6,21.1
>             Status: NEW
>           Severity: blocking
>              Owner: other_other@kernel-bugs.osdl.org
>          Submitter: davidhart@tqmcube.com
> 
> 
> Most recent kernel where this bug did *NOT* occur:
> 2.6.20.8
> 
> Distribution:
> Fedora Core 6
> 
> Hardware Environment:
> Sony Vaio 2.4gh/512 mb
> 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 645xx (rev 03)
> 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
> 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO]
> (rev 14)
> 00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
> 00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0)
> 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97
> Sound Controller (rev a0)
> 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
> 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
> 00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
> 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
> 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast
> Ethernet (rev 90)
> 00:07.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC
> (rev 01)
> 00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
> 00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
> 00:0a.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 02)
> 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go]
> (rev a3)
> Software Environment:
> 
> KDE.
> Kernel compiled with full debugging
> Standard nv driver - NOT nvidia.
> 
> Problem Description:
> 
> Kernel boots. X starts. Hard lock occurs immediately on launching an
> application. Complete freeze  stops logging (no panic or error messages. No
> debug information whatsoever. Neither SysReq nor alt-ctl-del are responsive.
> 
> Steps to reproduce:
> 
> Boot into X. Launch any application (web, mail client, etc).

Lovely regression.

If you have time, there are a couple of things to do here:

1: Watch virtual terminal #1 while starting that appliction.  ie: in an
   xterm (assuming you can open one) do

	sleep 5; mozilla

   then do a quick alt-shift-F1 before the sleep expires.  See if
   anything comes up on the console.

2: get netconsole working: see Documentation/networking/netconsole.txt

3: Performa a git bisection search, find the buggy patch.  This is quite a
   lot of work, and I hate asking people to do it because we don't (afaik)
   have any particularly good documentation on how to perform it.


       reply	other threads:[~2007-04-28 18:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200704281634.l3SGYhJX014704@fire-2.osdl.org>
2007-04-28 18:59 ` Andrew Morton [this message]
2007-04-28 19:18   ` [Bugme-new] [Bug 8392] New: Hard Lock Subsequent to Boot Adrian Bunk
2007-04-28 21:00     ` Roland Dreier

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=20070428115906.86e93af6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=davidhart@tqmcube.com \
    --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