All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
	e1000-devel@lists.sourceforge.net
Subject: Re: [stable] Li-nux 2.6.27.19  2.6.28.7
Date: Fri, 13 Mar 2009 15:20:44 -0700	[thread overview]
Message-ID: <20090313222044.GA18010@kroah.com> (raw)
In-Reply-To: <20090313151051.a9198384.akpm@linux-foundation.org>

On Fri, Mar 13, 2009 at 03:10:51PM -0700, Andrew Morton wrote:
> 
> I fired up this kernel up on my FC8 laptop and I see
> http://userweb.kernel.org/~akpm/p3130212.jpg
> 
> On the next two boot attempts, the kernel came up OK.
> 

That's wierd, it can't find the root filesystem?

What driver controls the disk for /dev/root?  It's not the USB
controller, is it?  Is that normally sda?

> Also, during boot the e1000e driver has conniptions:
> 
> ------------[ cut here ]------------
> WARNING: at drivers/net/e1000e/ich8lan.c:408 e1000_acquire_swflag_ich8lan+0x51/0xf2()
> e1000e mutex contention. Owned by pid 10
> Modules linked in:
> Pid: 9, comm: events/0 Not tainted 2.6.28.7 #1
> Call Trace:
>  [<ffffffff8103a810>] warn_slowpath+0xae/0xcd
>  [<ffffffff8104394b>] ? lock_timer_base+0x26/0x4a
>  [<ffffffff8104394b>] ? lock_timer_base+0x26/0x4a
>  [<ffffffff8105d63f>] ? __lock_acquire+0x702/0x760
>  [<ffffffff8105bfc6>] ? mark_held_locks+0x50/0x6d
>  [<ffffffff812dd950>] ? mutex_trylock+0x104/0x118
>  [<ffffffff8105c170>] ? trace_hardirqs_on_caller+0xf8/0x123
>  [<ffffffff8105c1a8>] ? trace_hardirqs_on+0xd/0xf
>  [<ffffffff811ed838>] e1000_acquire_swflag_ich8lan+0x51/0xf2
>  [<ffffffff811f2fe9>] e1000e_read_kmrn_reg+0x1b/0x69
>  [<ffffffff811f63c5>] ? e1000e_downshift_workaround+0x0/0x12
>  [<ffffffff811ed1e9>] e1000e_gig_downshift_workaround_ich8lan+0x2c/0x71
>  [<ffffffff811f63d5>] e1000e_downshift_workaround+0x10/0x12
>  [<ffffffff8104a6ed>] run_workqueue+0xf5/0x1fd
>  [<ffffffff8104a697>] ? run_workqueue+0x9f/0x1fd
>  [<ffffffff8104a8f6>] ? worker_thread+0x0/0xe8
>  [<ffffffff8104a9d1>] worker_thread+0xdb/0xe8
>  [<ffffffff8104de14>] ? autoremove_wake_function+0x0/0x36
>  [<ffffffff8104a8f6>] ? worker_thread+0x0/0xe8
>  [<ffffffff8104db1a>] kthread+0x44/0x6b
>  [<ffffffff8100cf59>] child_rip+0xa/0x11
>  [<ffffffff8100c474>] ? restore_args+0x0/0x30
>  [<ffffffff8104dad6>] ? kthread+0x0/0x6b
>  [<ffffffff8100cf4f>] ? child_rip+0x0/0x11
> ---[ end trace 09c88554f9900e8b ]---
> 
> Config: http://userweb.kernel.org/~akpm/config-t61p.txt
> dmesg: http://userweb.kernel.org/~akpm/dmesg-t61p.txt

Wierd, I don't know.

thanks,

greg k-h

  reply	other threads:[~2009-03-13 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 22:54 Li-nux 2.6.27.19 2.6.28.7 Og
2009-02-20 22:55 ` Li-nux 2.6.27.19 Og
2009-02-20 22:56   ` Og
2009-02-20 22:56 ` Li-nux 2.6.28.7 Og
2009-02-20 22:57   ` Og
2009-02-21  1:53 ` Li-nux 2.6.27.19 2.6.28.7 Linus Torvalds
2009-03-13 22:10 ` [stable] " Andrew Morton
2009-03-13 22:20   ` Greg KH [this message]
2009-03-13 23:45     ` Andrew Morton
2009-03-14  1:01     ` [E1000-devel] " Brandeburg, Jesse
2009-03-14  1:21       ` Tetsuo Handa

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=20090313222044.GA18010@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.