All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: rtc: IRQ 0 is not free.
Date: 05 Jul 2004 14:33:41 -0400	[thread overview]
Message-ID: <1089052420.15675.21.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FEF2D@hdsmsx403.hd.intel.com>

On Sun, 2004-06-27 at 10:26, Meelis Roos wrote:
> Latest 2.6.7+BK doe not enable the builtin RTC timer on my PC, dmesg
> shows only this:
> 
> rtc: IRQ 0 is not free.
> 
> I don't know when it actually broke since I don't depend on rtc so
> much that I would notice it breaking easyly.

it would be good if you could verify that vanilla 2.6.7 puts
rtc on IRQ8 properly for this box.

> dmesg and config are also below.

got the config, but the dmesg didn't come through, can you re-send it?

> lspnp -v shows
> 
> 03 PNP0b00 AT real-time clock
>         irq 8
>         io 0x0070-0x0071

hmmm, had never heard of lspnp (and neither does my local system)

> 
> /proc/interrupts:
> 
>            CPU0
>   0:   81450505          XT-PIC  timer
>   1:       6977          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>  10:   11071042          XT-PIC  VIA686A, uhci_hcd, uhci_hcd, eth1,
> mga@PCI:1:0:0
>  11:      36704          XT-PIC  acpi, bttv0, Ensoniq AudioPCI, Bt87x
> audio, eth0
>  12:     730526          XT-PIC  i8042
>  14:     225867          XT-PIC  ide0
>  15:     551481          XT-PIC  ide1
> NMI:          0
> LOC:   81457121
> ERR:     104354
> MIS:          0

Yep, no rtc on IRQ8...

thanks,
-Len



       reply	other threads:[~2004-07-05 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615FEF2D@hdsmsx403.hd.intel.com>
2004-07-05 18:33 ` Len Brown [this message]
2004-07-05 21:10   ` rtc: IRQ 0 is not free Meelis Roos
2004-06-27 14:26 Meelis Roos
2004-06-27 16:33 ` Grzegorz Kulewski
2004-06-27 17:32   ` Meelis Roos

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=1089052420.15675.21.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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.