public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <greg@kroah.com>, Boaz Harrosh <bharrosh@panasas.com>,
	Alan Cox <alan@redhat.com>
Subject: Re: 2.6.24-rc6-git7: Reported regressions from 2.6.23
Date: Wed, 2 Jan 2008 12:00:08 +0100	[thread overview]
Message-ID: <20080102110008.GB14731@elte.hu> (raw)
In-Reply-To: <1199244650.3252.18.camel@localhost.localdomain>


* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:

> Could you direct this poster to linux-scsi and we'll see if we can 
> finger the root cause (which will be difficult to do without getting a 
> boot trace).

FYI, here's a new one reported against 2.6.24-rc6-git7:

http://bugzilla.kernel.org/show_bug.cgi?id=9674

           Summary: Oops during rmmod'ing modeuls sdhci, sr_mod, ricoh_mmc,
                    mmc_core
           Product: Other
           Version: 2.5
     KernelVersion: 2.6.24-rc6-git7

has a very SCSI looking crash backtrace:

[   40.158530] Call Trace:
[   40.158537]  [<ffffffff80331800>] elv_next_request+0xe0/0x170
[   40.158543]  [<ffffffff803f7fa9>] scsi_request_fn+0x69/0x360
[   40.158547]  [<ffffffff803352a2>] blk_execute_rq_nowait+0x62/0xb0
[   40.158551]  [<ffffffff80336d6a>] blk_execute_rq+0x8a/0x100
[   40.158553]  [<ffffffff803347e5>] get_request+0x155/0x2d0
[   40.158557]  [<ffffffff803f7d64>] scsi_execute+0xe4/0x120
[   40.158560]  [<ffffffff803f7e31>] scsi_execute_req+0x91/0x100
[   40.158565]  [<ffffffff8800b70b>] :sr_mod:sr_probe+0x21b/0x630
[   40.158570]  [<ffffffff802fa0a9>] sysfs_create_link+0xa9/0x150
[   40.158575]  [<ffffffff805620a5>] klist_next+0x35/0xe0
[   40.158579]  [<ffffffff803c34cc>] driver_probe_device+0x9c/0x1b0
[   40.158582]  [<ffffffff803c37b1>] __driver_attach+0xe1/0xf0
[   40.158585]  [<ffffffff803c36d0>] __driver_attach+0x0/0xf0
[   40.158589]  [<ffffffff803c26bd>] bus_for_each_dev+0x4d/0x80
[   40.158592]  [<ffffffff803c2acf>] bus_add_driver+0xaf/0x220

	Ingo

  reply	other threads:[~2008-01-02 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 21:02 2.6.24-rc6-git7: Reported regressions from 2.6.23 Rafael J. Wysocki
2008-01-01 22:26 ` Linus Torvalds
2008-01-02  3:30   ` James Bottomley
2008-01-02 11:00     ` Ingo Molnar [this message]
2008-01-02  5:38   ` Greg KH
2008-01-02  3:12 ` Zhenyu Wang
2008-01-02 13:12   ` Rafael J. Wysocki
2008-01-02 13:24     ` Ingo Molnar
2008-01-02 13:37       ` 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=20080102110008.GB14731@elte.hu \
    --to=mingo@elte.hu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@redhat.com \
    --cc=bharrosh@panasas.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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