All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc1-mm2 (badness)
Date: Fri, 29 Oct 2004 15:33:19 -0700	[thread overview]
Message-ID: <4182C52F.20301@osdl.org> (raw)
In-Reply-To: <20041029014930.21ed5b9a.akpm@osdl.org>

Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm2/

I am seeing 2 badness reports with $Subject:

kobject i823650: cleaning up
Device 'i823650' does not have a release() function, it is broken and 
must be f.
Badness in device_release at drivers/base/core.c:85
  [<c0106e09>] dump_stack+0x1e/0x20
  [<c0218619>] kobject_cleanup+0x94/0x96
  [<c021906b>] kref_put+0x49/0xaa
  [<c0218648>] kobject_put+0x20/0x22
  [<c057841a>] init_i82365+0x1e0/0x1f6
  [<c055a981>] do_initcalls+0x27/0xc0
  [<c010050c>] init+0x7d/0x19c
  [<c0104295>] kernel_thread_helper+0x5/0xb
kobject i82365: unregistering

&&

Badness in enable_irq at kernel/irq/manage.c:106
  [<c0106e09>] dump_stack+0x1e/0x20
  [<c013f767>] enable_irq+0x72/0xd9
  [<c02b0416>] e100_up+0xfe/0x20a
  [<c02b15ca>] e100_open+0x26/0x6e
  [<c0396816>] dev_open+0x6e/0x7c
  [<c0397d85>] dev_change_flags+0x56/0x126
  [<c03d23a6>] devinet_ioctl+0x60b/0x6cd
  [<c03d41e1>] inet_ioctl+0x81/0xae
  [<c038dd3c>] sock_ioctl+0x1d3/0x2d6
  [<c0172920>] sys_ioctl+0x179/0x21d
  [<c0105f5d>] sysenter_past_esp+0x52/0x71
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

Dual-P4, IDE, 1 GB RAM.
.config at:
http://developer.osdl.org/rddunlap/configs/config-2610rc1mm2

-- 
~Randy

  parent reply	other threads:[~2004-10-29 22:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29  8:49 2.6.10-rc1-mm2 Andrew Morton
2004-10-29 10:24 ` 2.6.10-rc1-mm2 (compiler warnings on x86_64) Rafael J. Wysocki
2004-10-29 11:45 ` 2.6.10-rc1-mm2: `key_init' multiple definition Adrian Bunk
2004-10-29 17:35   ` Chris Wright
2004-10-29 20:20     ` Andrew Morton
2004-10-29 20:36       ` Chris Wright
2004-10-29 23:52         ` Andrew Morton
2004-10-29 23:53           ` Chris Wright
2004-10-29 16:04 ` 2.6.10-rc1-mm2 Alexander Nyberg
2004-10-29 17:44   ` 2.6.10-rc1-mm2 Randy.Dunlap
2004-10-29 17:16 ` 2.6.10-rc1-mm2 Borislav Petkov
2004-10-29 19:55 ` 2.6.10-rc1-mm2 Doug Maxey
2004-10-29 22:13   ` 2.6.10-rc1-mm2 Sam Ravnborg
2004-10-29 21:24     ` 2.6.10-rc1-mm2 Doug Maxey
2004-10-29 22:33 ` Randy.Dunlap [this message]
2004-10-30  3:24 ` 2.6.10-rc1-mm2: intelfb/AGP unknown symbols Adrian Bunk
2004-10-30  8:28   ` Arjan van de Ven
2004-10-30 11:21     ` Antonino A. Daplas
2004-10-30 11:21       ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-30 11:34       ` Arjan van de Ven
2004-10-30 13:08         ` Antonino A. Daplas
2004-10-30 13:08           ` Antonino A. Daplas
2004-10-30 15:16     ` Christoph Hellwig
2004-10-30 15:18 ` No PS2 with ACPI [was Re: 2.6.10-rc1-mm2] J.A. Magallon
2004-10-30 21:31   ` Andrew Morton
2004-10-31  0:06     ` Dmitry Torokhov
2004-11-01 22:05       ` J.A. Magallon
2004-11-02  3:31         ` Dmitry Torokhov
2004-11-01  8:46   ` Amit Shah
2004-11-03  6:08 ` ipw2100 and 2.6.10-rc1-bk12 Marcos D. Marado Torres

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=4182C52F.20301@osdl.org \
    --to=rddunlap@osdl.org \
    --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 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.