public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-mm1
Date: Fri, 11 Nov 2005 16:51:56 -0800	[thread overview]
Message-ID: <20051111165156.05391fef.akpm@osdl.org> (raw)
In-Reply-To: <6bffcb0e0511111631h52ff73e1q@mail.gmail.com>

Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
>
> [1.] One line summary of the problem:
>  Oops when starting system (perhaps /etc/init.d/networking)
> 
>  [4.] Kernel version (from /proc/version):
>  Linux version 2.6.14-mm1 (michal@debian) (gcc version 4.0.3 20051023
>  (prerelease) (Debian 4.0.2-3)) #2 SMP PREEMPT Mon Nov 7 14:11:39 CET
>  2005
> 
>  [5.] Output of Oops
>  Nov 12 01:16:57 debian kernel: EXT3 FS on sda3, internal journal
>  Nov 12 01:16:57 debian kernel: EXT3-fs: mounted filesystem with
>  ordered data mode.
>  Nov 12 01:16:57 debian kernel: fill_kobj_path: path = '/block/sda/sda3'
>  Nov 12 01:16:57 debian kernel: irq 20: nobody cared (try booting with
>  the "irqpoll" option)
>  Nov 12 01:16:57 debian kernel:  [<c0103e68>] dump_stack+0x1e/0x20
>  Nov 12 01:16:57 debian kernel:  [<c0143079>] __report_bad_irq+0x2b/0x90
>  Nov 12 01:16:57 debian kernel:  [<c0143189>] note_interrupt+0x79/0xd0
>  Nov 12 01:16:57 debian kernel:  [<c0142ab8>] __do_IRQ+0xe9/0x101
>  Nov 12 01:16:57 debian kernel:  [<c01051c7>] do_IRQ+0x67/0xa7
>  Nov 12 01:16:57 debian kernel:  =======================
>  Nov 12 01:16:57 debian kernel:  [<c0103952>] common_interrupt+0x1a/0x20
>  Nov 12 01:16:57 debian kernel:  [<c0100df4>] cpu_idle+0x49/0xa0
>  Nov 12 01:16:57 debian kernel:  [<c01002e5>] rest_init+0x45/0x47
>  Nov 12 01:16:57 debian kernel:  [<c036095a>] start_kernel+0x18a/0x19d
>  Nov 12 01:16:57 debian kernel:  [<c0100210>] 0xc0100210
>  Nov 12 01:16:57 debian kernel: ---------------------------
>  Nov 12 01:16:57 debian kernel: | preempt count: 00010001 ]
>  Nov 12 01:16:57 debian kernel: | 1 level deep critical section nesting:
>  Nov 12 01:16:57 debian kernel: ----------------------------------------
>  Nov 12 01:16:57 debian kernel: .. [<c0100e49>] .... cpu_idle+0x9e/0xa0
>  Nov 12 01:16:57 debian kernel: .....[<c01002e5>] ..   ( <= rest_init+0x45/0x47)
>  Nov 12 01:16:57 debian kernel:
>  Nov 12 01:16:57 debian kernel: handlers:
>  Nov 12 01:16:57 debian kernel: [<f98e77b4>]
>  (snd_intel8x0_interrupt+0x0/0x27a [snd_intel8x0])
>  Nov 12 01:16:57 debian kernel: Disabling IRQ #20
>  Nov 12 01:16:57 debian kernel: kobject af_packet: registering. parent:
>  <NULL>, set: module
>  Nov 12 01:16:57 debian kernel: kobject_hotplug

Crap.  This is one of those crashes where the sound people, the PCI people,
the ACPI people and the PM people all earnestly hope that it's the other
guy's bug and you and I are left with a mess on our hands.

Possibly the card didn't get powered up.  I know there's a way to get all
those snd_printk()'s to print something, but I never have much success
finding the right value for the right /proc file to make it happen.

So can you add this please?

--- devel/sound/pci/intel8x0.c~a	2005-11-11 16:47:00.000000000 -0800
+++ devel-akpm/sound/pci/intel8x0.c	2005-11-11 16:48:13.000000000 -0800
@@ -779,6 +779,7 @@ static irqreturn_t snd_intel8x0_interrup
 	unsigned int i;
 
 	status = igetdword(chip, chip->int_sta_reg);
+	printk("status: 0x%8x\n", status);
 	if (status == 0xffffffff)	/* we are not yet resumed */
 		return IRQ_NONE;
 
_

and let us know what it says?

Also, it would be useful if you could disable the sound driver in config
and see if you can get it booted.  If so, then generate the `dmesg -s
1000000' output for good and bad kernels and let's see what they look like.

Thanks.

  reply	other threads:[~2005-11-12  0:52 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07  2:24 2.6.14-mm1 Andrew Morton
2005-11-07  3:25 ` 2.6.14-mm1 Christoph Hellwig
2005-11-07  6:12   ` 2.6.14-mm1 Andrew Morton
2005-11-07  6:34     ` 2.6.14-mm1 Herbert Xu
2005-11-07  3:30 ` 2.6.14-mm1 Christoph Hellwig
2005-11-07 12:18   ` 2.6.14-mm1 Roman Zippel
2005-11-07 17:02     ` 2.6.14-mm1 Christoph Hellwig
2005-11-07 17:23       ` 2.6.14-mm1 Roman Zippel
2005-11-07 12:41   ` 2.6.14-mm1 Geert Uytterhoeven
2005-11-07  4:04 ` 2.6.14-mm1 Brice Goglin
2005-11-07  4:10 ` 2.6.14-mm1 Reuben Farrelly
2005-11-07  6:07   ` 2.6.14-mm1 Andrew Morton
2005-11-07  8:24   ` 2.6.14-mm1 Benoit Boissinot
2005-11-07  9:54 ` 2.6.14-mm1 Reuben Farrelly
2005-11-07 10:09   ` 2.6.14-mm1 Andrew Morton
2005-11-07 10:26     ` 2.6.14-mm1 Neil Brown
2005-11-07 10:37       ` 2.6.14-mm1 Andrew Morton
2005-11-07 10:44         ` 2.6.14-mm1 Reuben Farrelly
2005-11-07 18:52           ` 2.6.14-mm1 Andrew Morton
2005-11-07 19:27             ` 2.6.14-mm1 Alan Stern
2005-11-07 21:43             ` 2.6.14-mm1 J.A. Magallon
2005-11-08  0:07               ` 2.6.14-mm1 J.A. Magallon
2005-11-08 14:21             ` 2.6.14-mm1 James Bottomley
2005-11-09  0:30               ` 2.6.14-mm1 Reuben Farrelly
2005-11-07 12:00 ` 2.6.14-mm1 Jiri Slaby
2005-11-07 15:04   ` 2.6.14-mm1 Dustin Kirkland
2005-11-07 15:11     ` 2.6.14-mm1 Jiri Slaby
2005-11-07 16:15 ` 2.6.14-mm1 Alexander E. Patrakov
2005-11-07 19:52   ` 2.6.14-mm1 Andrew Morton
2005-11-07 20:07     ` 2.6.14-mm1 Greg KH
2005-11-07 20:30       ` 2.6.14-mm1 Dmitry Torokhov
2005-11-07 20:21     ` 2.6.14-mm1 Valdis.Kletnieks
2005-11-07 20:40       ` 2.6.14-mm1 Dmitry Torokhov
2005-11-07 20:46       ` 2.6.14-mm1 Andrew Morton
2005-11-11  9:32         ` 2.6.14-mm1 Alexander E. Patrakov
     [not found]           ` <437472DA.4090001@linuxfromscratch.org>
2005-11-11 11:50             ` 2.6.14-mm1 Alexander E. Patrakov
2005-11-07 17:37 ` 2.6.14-mm1: drivers/pci/hotplug/: namespace clashes Adrian Bunk
2005-11-07 18:41   ` Rajesh Shah
2005-11-07 20:03     ` Adrian Bunk
2005-11-07 21:37       ` Rajesh Shah
2005-11-07 21:10 ` 2.6.14-mm1: Why is USB_LIBUSUAL user-visible? Adrian Bunk
2005-11-07 21:52   ` Greg KH
2005-11-07 22:26     ` [linux-usb-devel] " Alan Stern
2005-11-07 22:28       ` Greg KH
2005-11-08  0:47         ` [-mm patch] USB_LIBUSUAL shouldn't be user-visible Adrian Bunk
2005-11-09 22:28           ` Greg KH
2005-11-10  6:41             ` Pete Zaitcev
2005-11-10 10:56               ` Adrian Bunk
2005-11-10 23:46                 ` Greg KH
2005-11-11  2:09                   ` Adrian Bunk
2005-11-11  6:13                     ` Greg KH
2005-11-11  9:31                     ` Pete Zaitcev
2005-11-10 12:11               ` Reuben Farrelly
2005-11-11  9:14           ` Pete Zaitcev
2005-11-07 23:34   ` 2.6.14-mm1: Why is USB_LIBUSUAL user-visible? Pete Zaitcev
2005-11-07 22:28 ` 2.6.14-mm1 - cpufreq build problem Rafael J. Wysocki
2005-11-08  4:36 ` [-mm patch] __deprecated_for_modules the lookup_hash() prototype Adrian Bunk
2005-11-10 13:07 ` 2.6.14-mm1 Serge Hallyn
     [not found]   ` <OFE00FE25C.725B5669-ON872570B5.0066EFF0-862570B5.00679646@us.ibm.com>
2005-11-11 17:59     ` 2.6.14-mm1 Serge Hallyn
2005-11-14 17:05       ` 2.6.14-mm1 Greg KH
2005-11-12  0:31 ` 2.6.14-mm1 Michal Piotrowski
2005-11-12  0:51   ` Andrew Morton [this message]
2005-11-12  1:30     ` 2.6.14-mm1 Michal Piotrowski
2005-11-12  1:47       ` 2.6.14-mm1 Andrew Morton
2005-11-12 18:00         ` 2.6.14-mm1 Michal Piotrowski

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=20051111165156.05391fef.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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