mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Yinghai Lu <yinghai@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-wireless@vger.kernel.org,
	Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: iwl3945 didn't survive after s2ram failure
Date: Fri, 6 Jan 2012 09:49:16 +0100	[thread overview]
Message-ID: <20120106084916.GA10292@tiehlicka.suse.cz> (raw)
In-Reply-To: <CAE9FiQVi_TN29mUtvHG6ZqWRCkyE6H5eG5z350uXrub=zUmYgA@mail.gmail.com>

On Thu 05-01-12 11:44:17, Yinghai Lu wrote:
> On Thu, Jan 5, 2012 at 6:19 AM, Michal Hocko <mhocko@suse.cz> wrote:
> 
> >
> > Looking in the history it seems that 497f16f2 [pci: Fix hotplug of
> > Express Module with pci bridges] might be related. It fixes an issue
> > introduced by bbef98ab [PCI: defer enablement of SRIOV BARS] which is a
> > part of my 3.2.0-rc6-00005-ga36bfdd problematic version. But I do not
> > understand details of the patch so I cannot tell that for 100%.
> > Yinghai Lu, is it possible that I the problem I have seen is somehow
> > related? For reference the thread started at
> > https://lkml.org/lkml/2011/12/27/65
> 
> you have one bridge that BIOS does not assign resource to it.
> so kernel will allocate resource to it.
> 
> [    0.331694] pci 0000:00:1c.2: BAR 8: assigned [mem 0x80100000-0x803fffff]
> [    0.331825] pci 0000:00:1c.2: BAR 9: assigned [mem
> 0x80400000-0x805fffff 64bit pref]
> [    0.332041] pci 0000:00:1c.2: BAR 7: assigned [io  0x4000-0x4fff]
> [    0.334271] pci 0000:05:00.0: BAR 0: assigned [mem 0x80100000-0x80100fff]
> [    0.334455] pci 0000:05:00.0: BAR 0: set to [mem
> 0x80100000-0x80100fff] (PCI address [0x80100000-0x80100fff])
> [    0.334666] pci 0000:00:1c.2: PCI bridge to [bus 05-05]
> [    0.334794] pci 0000:00:1c.2:   bridge window [io  0x4000-0x4fff]
> [    0.334926] pci 0000:00:1c.2:   bridge window [mem 0x80100000-0x803fffff]
> [    0.335058] pci 0000:00:1c.2:   bridge window [mem
> 0x80400000-0x805fffff 64bit pref]
> 
> yes, the commit fix the problem.

Thanks for the confirmation!

> 
> in the commit log i already said:
> 
> |    That should fix regression like BIOS does not assign correct resource to
> |    bridge.
> 
> 
> Thanks
> 
> Yinghai Lu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

      reply	other threads:[~2012-01-06  8:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 10:53 Michal Hocko
2012-01-03 10:34 ` Stanislaw Gruszka
2012-01-03 12:23   ` Stanislaw Gruszka
2012-01-03 13:07     ` Michal Hocko
2012-01-05 11:26       ` Stanislaw Gruszka
2012-01-05 12:20         ` Michal Hocko
2012-01-03 13:03   ` Michal Hocko
2012-01-05 11:07     ` Stanislaw Gruszka
2012-01-05 14:19       ` Michal Hocko
2012-01-05 14:34         ` Michal Hocko
2012-01-05 15:00         ` Stanislaw Gruszka
2012-01-05 16:25           ` Michal Hocko
2012-01-05 19:44         ` Yinghai Lu
2012-01-06  8:49           ` Michal Hocko [this message]

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=20120106084916.GA10292@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=yinghai@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

Powered by JetHome