linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "Pawe³ Go³aszewski" <blues@ds.pg.gda.pl>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.71
Date: Sun, 15 Jun 2003 14:45:38 +0100	[thread overview]
Message-ID: <20030615144538.B32102@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.51L.0306151526190.11459@piorun.ds.pg.gda.pl>; from blues@ds.pg.gda.pl on Sun, Jun 15, 2003 at 03:29:11PM +0200

On Sun, Jun 15, 2003 at 03:29:11PM +0200, Pawe³ Go³aszewski wrote:
> On Sat, 14 Jun 2003, Linus Torvalds wrote:
> > I think I'll call this kernel the "sticky turtle", in honor of that
> > historic "greased weasel" kernel, and as a comment on how sadly
> > dependent I've become on the daily BK snapshots. It's been too long
> > since 2.5.70.
> 
> well done - this kernel looks really good. Even building is cleaner...
> 
> But - I get now after make modules_install:
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.5.71; fi
> WARNING: /lib/modules/2.5.71/kernel/drivers/char/agp/nvidia-agp.ko needs unknown symbol agp_memory_reserved
> WARNING: /lib/modules/2.5.71/kernel/drivers/net/3c509.ko needs unknown symbol netdev_boot_setup_check

I'm afraid to say it, but I'm considering christening this kernel as
"the most whinging 2.5 kernel thus far". 8/

I'm currently tracking down the cause of all these whinges, eg:

VFS: Mounted root (ext2 filesystem).
Freeing init memory: 88K
bad: scheduling while atomic! (00000001 0 1 swapper)
[<c02372d0>] (schedule+0x0/0x490) from [<c0258cc4>] (do_generic_mapping_read+0x48c/0x49c)
[<c0258838>] (do_generic_mapping_read+0x0/0x49c) from [<c0258fb0>] (__generic_file_aio_read+0x1ac/0x1e4)
[<c0258e04>] (__generic_file_aio_read+0x0/0x1e4) from [<c02590e4>] (generic_file_read+0x68/0x90)
[<c025907c>] (generic_file_read+0x0/0x90) from [<c0277b90>] (vfs_read+0xd8/0x124)
[<c0277ab8>] (vfs_read+0x0/0x124) from [<c0284100>] (kernel_read+0x54/0x80)
[<c02840ac>] (kernel_read+0x0/0x80) from [<c0285388>] (do_execve+0x104/0x1dc)
[<c0285284>] (do_execve+0x0/0x1dc) from [<c02273a0>] (sys_execve+0x44/0x60)
[<c022735c>] (sys_execve+0x0/0x60) from [<c0222300>] (ret_fast_syscall+0x0/0x30)

(UP preempt)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-06-15 13:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14 21:17 Linux 2.5.71 Linus Torvalds
2003-06-15  1:42 ` Florin Iucha
2003-06-15  1:58   ` Linus Torvalds
2003-06-15  2:00     ` Florin Iucha
2003-06-15  4:55       ` Florin Iucha
2003-06-15  8:03     ` Trond Myklebust
2003-06-15  6:54 ` Andre Hedrick
2003-06-15  7:15   ` Andre Hedrick
2003-06-15 13:29 ` Paweł Gołaszewski
2003-06-15 13:45   ` Russell King [this message]
2003-06-16 18:04 ` John Cherry
2003-06-17 19:29 ` [2.5 patch] 2.5.72: moxa.c doesn't compile Adrian Bunk
2003-06-17 23:33   ` viro
2003-06-19 18:53   ` Thiago Rondon
2003-06-20  4:28     ` Rusty Russell
     [not found] <20030614213012$6a47@gated-at.bofh.it>
2003-06-14 22:21 ` Linux 2.5.71 John Weber
2003-06-15  0:42   ` Herbert Xu
2003-06-15  0:43   ` Herbert Xu
2003-06-15  1:10     ` Arnaldo Carvalho de Melo
2003-06-15  0:21 Larry McVoy
2003-06-17 16:13 ` H. Peter Anvin

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=20030615144538.B32102@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=blues@ds.pg.gda.pl \
    --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;
as well as URLs for NNTP newsgroup(s).