public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-rc1 ahci regression
Date: Thu, 3 Jun 2010 12:41:04 +0400	[thread overview]
Message-ID: <20100603084104.GA17431@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <AANLkTil6k_4YwdvLai_VUlVjgz030ctu7djVGHu0qgd2@mail.gmail.com>

On Thu, Jun 03, 2010 at 04:11:57PM +0800, Luming Yu wrote:
> On Thu, Jun 3, 2010 at 3:54 PM, Anton Vorontsov <cbouatmailru@gmail.com> wrote:
[...]
> >> I happened to notice that the commit 365cfa1ed5 caused the following
> >> boot error with 2.6.25-rc1
[...]
> > Can you provide full boot log (dmesg) please?
[...]

I don't see any AHCI devices probed.

[...]
> ------------[ cut here ]------------
> WARNING: at fs/sysfs/dir.c:451 sysfs_add_one+0xc9/0x130()
> Hardware name: X8DTN
> sysfs: cannot create duplicate filename
> '/devices/pci0000:00/0000:00:1c.4/0000:0f:00.0/slot'

This looks suspicious.

> usb 1-5: New USB device found, idVendor=14dd, idProduct=0002

(...this is async USB stuff, doesn't matter...)

> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.35-rc1 #1
> Call Trace:
>  [<ffffffff8105ed8f>] warn_slowpath_common+0x7f/0xc0
>  [<ffffffff8105ee86>] warn_slowpath_fmt+0x46/0x50
>  [<ffffffff811ad969>] sysfs_add_one+0xc9/0x130
>  [<ffffffff811ae0f8>] sysfs_do_create_link+0xd8/0x1a0
>  [<ffffffff811ae1f3>] sysfs_create_link+0x13/0x20
>  [<ffffffff81236466>] pci_create_sysfs_dev_files+0x3d6/0x5f0

Anyway, I just tried to move code around from libahci.c
back to ahci.c by hand, to verify that there are actually
no code changes, and there isn't.

So, I wonder, have you actually bisected the thing correctly?
Does "git reset --hard 365cfa1ed5^" actually help and does
"git reset --hard 365cfa1ed5" actually break things?

  parent reply	other threads:[~2010-06-03  8:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03  7:02 2.6.25-rc1 ahci regression Luming Yu
2010-06-03  7:13 ` Jeff Garzik
2010-06-03  7:28   ` Luming Yu
2010-06-03 15:54     ` Jeff Garzik
2010-06-03  7:54 ` Anton Vorontsov
     [not found]   ` <AANLkTil6k_4YwdvLai_VUlVjgz030ctu7djVGHu0qgd2@mail.gmail.com>
2010-06-03  8:41     ` Anton Vorontsov [this message]
2010-06-03  8:56       ` Luming Yu
2010-06-03  9:15         ` Anton Vorontsov
2010-06-03  9:18         ` Luming Yu
2010-06-03  9:39           ` Anton Vorontsov
2010-06-03 12:35             ` Luming Yu
2010-06-03 13:14               ` Anton Vorontsov
2010-06-03 13:23                 ` Anton Vorontsov
2010-06-03 13:50                   ` Anton Vorontsov
2010-06-03 14:13                     ` Luming Yu
2010-06-03 15:04                       ` Anton Vorontsov
2010-06-03 15:07                         ` Luming Yu
2010-06-03 15:45                         ` Américo Wang
2010-06-03 15:48                           ` Luming Yu
2010-06-04  4:58                             ` Américo Wang
2010-06-03 15:55                           ` Anton Vorontsov
2010-06-04  5:00                             ` Américo Wang
2010-06-03 13:38                 ` Luming Yu

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=20100603084104.GA17431@oksana.dev.rtsoft.ru \
    --to=cbouatmailru@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@gmail.com \
    /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