From: Roessner Christian <info@roessner-net.com>
To: linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: APIC probs with kernel 2.6.6-rc1-bk2 and usb, bttv
Date: Sun, 25 Apr 2004 20:13:34 +0200 [thread overview]
Message-ID: <200404252013.34704.info@roessner-net.com> (raw)
In-Reply-To: <1082862426.3163.30.camel@dhcppc4>
Hello,
>
> Tagged where? These flags apply equally to both architectures.
Okay, sorry. I did not read the leading text inside kernel-parameters.txt.
Just did a grep acpi and looked for the listed lines.
> CPU0
> 0: 345800 XT-PIC timer
> 1: 1452 IO-APIC-edge i8042
> 2: 0 XT-PIC cascade
> 8: 0 IO-APIC-edge rtc
> 9: 0 IO-APIC-level acpi
> 12: 50 IO-APIC-edge i8042
> 14: 6155 IO-APIC-edge ide0
> 15: 42 IO-APIC-edge ide1
> 16: 678 IO-APIC-level bttv0, nvidia
> 17: 147 IO-APIC-level aic7xxx, libata
> 18: 227 IO-APIC-level eth0, b1pci-9c00
> 19: 7 IO-APIC-level eth1
> 20: 0 IO-APIC-level ohci_hcd
> 21: 0 IO-APIC-level ehci_hcd
> 22: 1806 IO-APIC-level NVidia nForce3, ohci_hcd
>
> If you run the latest -mm patch, you can fix the XT-PIC timer
> by passing "acpi_skip_timer_override" on the cmdline.
>
I will try this later, What does this timer-fix mean for my system?
> RE: USB is totally dead.
> you've got a number of controllers, are they all dead.
> hard to tell if the last one if taking the interrupts,
> or if that is your sound. perhaps you can disable sound
> and see if IRQ22 becomes quiescent.
>
I have stopped the sound and have removed all sound modules (Init-script did
this for me ;-) ) I have checked, if the modules had been removed (lsmod). I
did a cat /proc/interrupts and: IRQ22 had ohci_hcd for itself. After that I
tried to do a hotplug restart, but the init-script was unable to restart it.
It did nothing, just waiting. I could not break it with CTRL+C.
So, USB does not work, even when sound is not running.
I also tested my SCSI-controller, but that seems to work okay, although it had
some problems aborting a command (I copied a 400MB file and pressed CTRL+C
after about 230MB). Here is the output:
Apr 25 19:49:34 [kernel] ISOFS: changing to secondary root
Apr 25 19:52:43 [kernel] scsi1:0:4:0: Attempting to queue an ABORT message
- Last output repeated 3 times -
Apr 25 19:53:28 [kernel] Recovery code awake
Apr 25 19:53:28 [kernel] scsi1 (4:0): rejecting I/O to offline device
> Re: TV station change freezes system.
> Does it also freeze the system if you boot with "noapic"?
>
I have booted the system without specifying apic (Seems to be noapic, because
of XT-PIC in /proc/interrupts) and with lapic. In both cases, TV is working
without any problems. Only specifying apic explicitly, freezes the system.
Regards
Christian
next prev parent reply other threads:[~2004-04-25 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F9864@hdsmsx403.hd.intel.com>
2004-04-25 3:07 ` APIC probs with kernel 2.6.6-rc1-bk2 and usb, bttv Len Brown
2004-04-25 18:13 ` Roessner Christian [this message]
2004-04-21 17:26 Roessner Christian
2004-04-23 15:51 ` Roessner Christian
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=200404252013.34704.info@roessner-net.com \
--to=info@roessner-net.com \
--cc=len.brown@intel.com \
--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