From: Jochen Hein <jochen@jochen.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [2.5.50] more uninitialized timers
Date: Sat, 30 Nov 2002 17:21:08 +0100 [thread overview]
Message-ID: <87isyfjaff.fsf@gswi1164.jochen.org> (raw)
Nov 30 17:06:31 gswi1164 kernel: Linux Kernel Card Services 3.1.22
Nov 30 17:06:31 gswi1164 kernel: options: [pci] [cardbus] [pm]
Nov 30 17:06:31 gswi1164 kernel: pci_link-0484 [19] acpi_pci_link_get_irq : Link disabled
Nov 30 17:06:31 gswi1164 kernel: pci_irq-0256 [18] acpi_pci_irq_lookup : Invalid IRQ link routing entry
Nov 30 17:06:31 gswi1164 kernel: pci_irq-0295 [18] acpi_pci_irq_derive : Unable to derive IRQ for device 00:02.0
Nov 30 17:06:31 gswi1164 kernel: ACPI: No IRQ known for interrupt pin A of device 00:02.0 - using IRQ 255
Nov 30 17:06:31 gswi1164 kernel: Module yenta_socket cannot be unloaded due to unsafe usage in drivers/pcmcia/yenta.c:940
Nov 30 17:06:31 gswi1164 kernel: Uninitialised timer!
Nov 30 17:06:31 gswi1164 kernel: This is just a warning. Your computer is OK
Nov 30 17:06:31 gswi1164 kernel: function=0xc6a90e40, data=0xc6a92160
Nov 30 17:06:31 gswi1164 kernel: Call Trace: [check_timer_failed+64/76] [add_timer+59/288] [worker_thread+489/716] [worker_thread+0/716] [default_wake_function+0/52] [default_wake_function+0/52] [kernel_thread_helper+5/12]
Nov 30 17:06:31 gswi1164 kernel: Yenta IRQ list 04b8, PCI irq0
Nov 30 17:06:31 gswi1164 kernel: pci_link-0484 [19] acpi_pci_link_get_irq : Link disabled
Nov 30 17:06:31 gswi1164 kernel: pci_irq-0256 [18] acpi_pci_irq_lookup : Invalid IRQ link routing entry
Nov 30 17:06:31 gswi1164 kernel: pci_irq-0295 [18] acpi_pci_irq_derive : Unable to derive IRQ for device 00:02.1
Nov 30 17:06:31 gswi1164 kernel: ACPI: No IRQ known for interrupt pin B of device 00:02.1 - using IRQ 255
Nov 30 17:06:31 gswi1164 kernel: Socket status: 30000010
Nov 30 17:06:31 gswi1164 kernel: Uninitialised timer!
Nov 30 17:06:31 gswi1164 kernel: This is just a warning. Your computer is OK
Nov 30 17:06:31 gswi1164 kernel: function=0xc6a90e40, data=0xc6a92218
Nov 30 17:06:31 gswi1164 kernel: Call Trace: [check_timer_failed+64/76] [<c6a90e40>] [<c6a92218>] [<c6a92290>] [add_timer+59/288] [<c6a92290>] [<c6a92218>] [<c6a91057>] [<c6a92290>] [<c6a92218>] [worker_thread+489/716] [<c6a92218>] [worker_thread+0/716] [<c6a92218>] [<c6a90fd0>] [default_wake_function+0/52] [default_wake_function+0/52] [kernel_thread_helper+5/12]
Nov 30 17:06:31 gswi1164 kernel: Yenta IRQ list 04b0, PCI irq0
The second one comes when loading PCMCIA modules, but ksymoops gives
no definite hints.
Trace; c011deb0 <check_timer_failed+40/4c>
Trace; c6a90e40 <END_OF_CODE+6699060/????>
Trace; c6a92218 <END_OF_CODE+669a438/????>
Trace; c6a92290 <END_OF_CODE+669a4b0/????>
Trace; c011def7 <add_timer+3b/120>
Trace; c6a92290 <END_OF_CODE+669a4b0/????>
Trace; c6a92218 <END_OF_CODE+669a438/????>
Trace; c6a91057 <END_OF_CODE+6699277/????>
Trace; c6a92290 <END_OF_CODE+669a4b0/????>
Trace; c6a92218 <END_OF_CODE+669a438/????>
Trace; c0123961 <worker_thread+1e9/2cc>
Trace; c6a92218 <END_OF_CODE+669a438/????>
Trace; c0123778 <worker_thread+0/2cc>
Trace; c6a92218 <END_OF_CODE+669a438/????>
Trace; c6a90fd0 <END_OF_CODE+66991f0/????>
Trace; c0115610 <default_wake_function+0/34>
Trace; c0115610 <default_wake_function+0/34>
Trace; c0106e6d <kernel_thread_helper+5/c>
The following modules are loaded:
root@gswi1164:~# lsmod
Module Size Used by
pcnet_cs 10942 1 [unsafe]
8390 6149 1 pcnet_cs
ds 6173 2 pcnet_cs
yenta_socket 10067 1 [unsafe]
pcmcia_core 37051 3 pcnet_cs ds yenta_socket
uhci_hcd 22625 0
rxrpc 51542 0
usbnet 14528 0
usbcore 76323 4 uhci_hcd usbnet
ircomm_tty 28005 0
ircomm 11396 1 ircomm_tty
irda 134582 3 ircomm_tty ircomm [unsafe]
vfat 9174 0
fat 32835 1 vfat
Jochen
--
Wenn Du nicht weißt was Du tust, tu's mit Eleganz.
reply other threads:[~2002-11-30 18:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87isyfjaff.fsf@gswi1164.jochen.org \
--to=jochen@jochen.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
Powered by JetHome