From: Reuben Farrelly <reuben-lkml@reub.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc1-mm1
Date: Fri, 18 Nov 2005 20:20:29 +1300 [thread overview]
Message-ID: <437D80BD.7030609@reub.net> (raw)
In-Reply-To: <20051117111807.6d4b0535.akpm@osdl.org>
Hi,
On 18/11/2005 8:18 a.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
>
> - reiser4 significantly updated
>
>
>
>
> Changes since 2.6.14-mm2:
This has been one of the best -mm releases in a while. No problems compiling
or running - and so far nearly 18 hours uptime without any surprises.
Following up on a posting from the last -mm release, I'm still seeing errors
loading multiple network drivers as modules (e100 and sky2) when
CONFIG_PREEMPT_BKL is enabled, with 2.6.14-mm1, 2.6.14-mm2 and now
2.6.15-rc1-mm1. Mainline git doesn't exhibit the problem, so it's -mm specific.
This is what is logged:
Nov 18 17:40:42 tornado kernel: e100: 0000:06:03.0: e100_eeprom_load: EEPROM
corrupted
Nov 18 17:40:42 tornado kernel: ACPI: PCI interrupt for device 0000:06:03.0
disabled
Nov 18 17:40:42 tornado kernel: e100: probe of 0000:06:03.0 failed with error -11
Nov 18 17:40:43 tornado kernel: ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17
(level, low) -> IRQ 177
Nov 18 17:40:43 tornado kernel: sky2 0000:04:00.0: unsupported chip type 0xff
Nov 18 17:40:43 tornado kernel: ACPI: PCI interrupt for device 0000:04:00.0
disabled
Nov 18 17:40:43 tornado kernel: sky2: probe of 0000:04:00.0 failed with error -95
I'm certain that both of these NIC's are OK as they work fine with
CONFIG_PREEMPT_BKL not selected.
With CONFIG_PREEMPT_BKL disabled and an otherwise identical config, the
driver modules load up just fine.
A known good kernel with this config was 2.6.14-rc5-mm1.
I have backed out git-netdev-all but it made no difference, as well as backed
out the e100 changes in -mm on 2.6.15-mm2, again no difference. So I suspect
it's not a netdev driver problem.
What else can I do to help narrow down the problem? What other trees or patches
would be worth backing out to try and narrow it down?
.config and system details are up on http://www.reub.net/kernel/
Reuben
next prev parent reply other threads:[~2005-11-18 7:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 19:18 2.6.15-rc1-mm1 Andrew Morton
2005-11-17 21:30 ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-17 22:14 ` 2.6.15-rc1-mm1 David Howells
2005-11-17 22:23 ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-18 4:23 ` 2.6.15-rc1-mm1 - immediate system reset at boot Valdis.Kletnieks
2005-11-18 4:27 ` Andrew Morton
2005-11-18 1:41 ` [-mm patch] kernel/signal.c: fix compile warning Adrian Bunk
2005-11-18 3:59 ` George Anzinger
2005-11-18 1:44 ` 2.6.15-rc1-mm1 Richard Knutsson
2005-11-18 1:53 ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18 7:20 ` Reuben Farrelly [this message]
2005-11-18 7:42 ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18 7:56 ` 2.6.15-rc1-mm1 Sander
2005-11-18 20:58 ` 2.6.15-rc1-mm1 Reuben Farrelly
2005-11-18 21:19 ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18 12:43 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 20:37 ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 21:14 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-18 23:16 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:03 ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 23:35 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:51 ` 2.6.15-rc1-mm1 Greg KH
2005-11-19 1:24 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-19 1:26 ` 2.6.15-rc1-mm1 Greg KH
2005-11-19 1:49 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19 3:24 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-21 0:00 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-21 0:26 ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 20:47 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-22 20:55 ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 22:05 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19 1:40 ` 2.6.15-rc1-mm1 Ian McDonald
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=437D80BD.7030609@reub.net \
--to=reuben-lkml@reub.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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