From: Reuben Farrelly <reuben-lkml@reub.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-mm2
Date: Fri, 11 Nov 2005 18:49:57 +1300 [thread overview]
Message-ID: <43743105.7030201@reub.net> (raw)
In-Reply-To: <20051110203544.027e992c.akpm@osdl.org>
Hi,
On 11/11/2005 5:35 p.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14/2.6.14-mm2/
>
> - reiser4 seems to be broken when built as a module (due, I assume, to a
> reiser4-specific kbuild change). CONFIG_REISER4_FS=y will be needed.
>
> - New git tree git-cfq.patch - CFQ I/O scheduler updates from Jens
>
> - The git-pcmcia tree has been reinstated
>
> - git-audit and the several -mm fixups to it have been dropped for now - it's
> undergoing a bit of churn.
>
> - Numerous subsystem updates. Notably more v4l work.
Network is a no-go for me:
[root@tornado ~]# /etc/init.d/network restart
e100: 0000:06:03.0: e100_eeprom_load: EEPROM corrupted
e100: probe of 0000:06:03.0 failed with error -11
sky2 0000:04:00.0: unsupported chip type 0xff
sky2: probe of 0000:04:00.0 failed with error -95
Both drivers worked under 2.6.14-rc5-mm1, but failed with 2.6.14-mm2. I also
re-tested against 2.6.14-mm1 and this problem also occurs there (I didn't get
to test this this far with -mm1, had too many problems with other things and
been having other hassles such as dsl connection).
Somehow I doubt that these two cards are both genuinely faulty..........I can
swap out with another e100 if need be.
New config is up at http://www.reub.net/kernel/
Otherwise compiles, starts up and shuts down fine.
Reuben
next prev parent reply other threads:[~2005-11-11 5:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 4:35 2.6.14-mm2 Andrew Morton
2005-11-11 5:23 ` 2.6.14-mm2: loop detected in depmod Brice Goglin
2005-11-11 7:52 ` Antonino A. Daplas
2005-11-12 3:41 ` Brice Goglin
2005-11-11 5:49 ` Reuben Farrelly [this message]
2005-11-11 6:07 ` 2.6.14-mm2 Andrew Morton
2005-11-11 8:28 ` 2.6.14-mm2 Reuben Farrelly
2005-11-11 8:55 ` 2.6.14-mm2 Andrew Morton
2005-11-11 13:28 ` 2.6.14-mm2 Reuben Farrelly
2005-11-11 8:54 ` 2.6.14-mm2 J.A. Magallon
2005-11-11 12:33 ` 2.6.14-mm2 Felipe Alfaro Solana
2005-11-11 16:40 ` [-mm patch] fs/ocfs2/file.c: make ocfs2_extend_allocation() static Adrian Bunk
2005-11-11 17:09 ` [-mm PATCH] slob: add kmem_set_shrinker Yoichi Yuasa
2005-11-11 19:14 ` 2.6.14-mm2 Badari Pulavarty
2005-11-11 19:21 ` 2.6.14-mm2 Andrew Morton
2005-11-11 19:32 ` 2.6.14-mm2 Badari Pulavarty
2005-11-11 22:32 ` 2.6.14-mm2 Michal Piotrowski
2005-11-11 22:37 ` 2.6.14-mm2 Michal Piotrowski
2005-11-11 23:01 ` 2.6.14-mm2 Andrew Morton
2005-11-11 23:28 ` [PATCH] nvidiafb: Fix bug in nvidiafb_pan_display Antonino A. Daplas
2005-11-11 23:38 ` Benjamin Herrenschmidt
2005-11-11 23:55 ` Antonino A. Daplas
2005-11-11 23:54 ` Michal Piotrowski
2005-11-11 23:30 ` 2.6.14-mm2 Michal Piotrowski
2005-11-12 0:45 ` 2.6.14-mm2 Antonino A. Daplas
2005-11-16 9:04 ` 2.6.14-mm2 KAMEZAWA Hiroyuki
2005-11-16 12:56 ` 2.6.14-mm2 KAMEZAWA Hiroyuki
2005-11-16 13:17 ` [Lhms-devel] 2.6.14-mm2 Dave Hansen
2005-11-16 16:02 ` Kamezawa Hiroyuki
2005-11-16 16:31 ` Dave Hansen
2005-11-16 16:39 ` Kamezawa Hiroyuki
2005-11-17 0:10 ` KAMEZAWA Hiroyuki
2005-11-17 9:16 ` KAMEZAWA Hiroyuki
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=43743105.7030201@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