From: Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Cc: Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Maciej Rutecki
<maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Florian Mickler <florian-sVu6HhrpSfRAfugRpC6u6w@public.gmane.org>
Subject: Re: [Bug #29322] System lockup with 2.6.38-rc4+
Date: Mon, 21 Feb 2011 22:14:27 +0000 [thread overview]
Message-ID: <201102212214.27880.chris2553@googlemail.com> (raw)
In-Reply-To: <5HY1m9_-mkI.A.tTH.QWtYNB@chimera>
On Monday 21 February 2011, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.37. Please verify if it still should be listed and let the
> tracking team know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29322
> Subject : System lockup with 2.6.38-rc4+
> Submitter : Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
> Date : 2011-02-14 17:31 (8 days old)
> Message-ID : <201102141731.29331.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
> References : http://marc.info/?l=linux-kernel&m=129770471724602&w=2
Yes, I think this should stay open. I haven't heard anything since I replied to
Ben Gamari on 14 February. having said that, I haven't experienced the lock up
again since I reported it. Perhaps it's been fixed without me knowing.
Chris
--
The more I see, the more I know. The more I know, the less I understand.
Changing Man - Paul Weller
next prev parent reply other threads:[~2011-02-21 22:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 21:52 2.6.38-rc5-git6: Reported regressions from 2.6.37 Rafael J. Wysocki
2011-02-21 21:52 ` [Bug #27022] [REPORT] BUG: spinlock recursion on CPU#0, init/1 Rafael J. Wysocki
2011-02-21 22:02 ` [Bug #28262] Slow resume from suspend/hibernate on Dell Inspiron M301Z Rafael J. Wysocki
2011-02-21 22:02 ` [Bug #28422] kref and apparmor panic in 2.6.38-rc2 Rafael J. Wysocki
2011-02-21 22:02 ` [Bug #28102] New display errors in 2.6.38-rc2-00175-g6fb1b30 Rafael J. Wysocki
2011-02-21 22:02 ` [Bug #27382] ath5k phy0: gain calibration timeout Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #28522] Unable to mount FAT-formatted floppy on /dev/fd0, plus WARN_ON when using /dev/fd0u1440 Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #28432] khugepaged: gets stuck when writing to USB flash, 2.6.38-rc2 Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #28452] 2.6.38-rc3 regression on parisc: segfaults Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #28562] [BUG] usb problems in .38-rc3+ Rafael J. Wysocki
2011-02-22 2:06 ` Ed Tomlinson
[not found] ` <201102212106.07392.edt-Yad3+ZauZac@public.gmane.org>
2011-02-22 19:57 ` Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #28642] ACPI broken on DELL Latitude E6410 in 2.6.38-rc3 Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #28882] Screen corruption and GPU hangs Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #28842] 2.6.38-rc3 regression ipv6 TFTP download with curl failing in getpeername? Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #29022] [REGRESSION? 2.6.38-rc4] nouveau NV50 screen freeze Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #29202] 2.6.38-rc: fuse BUG, maybe related to detaching external usb drive without umounting Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #29232] [VT-d] VT-d device passthrough fail to guest Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #29252] IPv6 doesn't work in a kvm guest Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #29322] System lockup with 2.6.38-rc4+ Rafael J. Wysocki
2011-02-21 22:14 ` Chris Clayton [this message]
[not found] ` <201102212214.27880.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2011-02-21 22:30 ` Rafael J. Wysocki
2011-02-21 22:03 ` [Bug #29402] kernel panics while running ffsb scalability workloads on 2.6.38-rc1 through -rc5 Rafael J. Wysocki
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=201102212214.27880.chris2553@googlemail.com \
--to=chris2553-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=florian-sVu6HhrpSfRAfugRpC6u6w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.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;
as well as URLs for NNTP newsgroup(s).