Hi,
clean 2.4.22-ac1, load of usb-uhci.o locks my machine hard :-(
it was working OK with 2.4.22-rc2-ac2! machine is on KT133 chipset.
I cant use plain 2.4.22 because of trouble of compiling it with XFS
support (unofficial patch has no .config entries).
any suggestions? regards, P
--
Pawel Dziekonski <pawel.dziekonski|@|pwr.wroc.pl>, KDM WCSS avatar:0:0:
Wroclaw Networking & Supercomputing Center, HPC Department
-> See message headers for privacy policy info.
On nie, 31 sie 2003 at 04:11:25 +0200, Pawel Dziekonski wrote:
> Hi,
>
> clean 2.4.22-ac1, load of usb-uhci.o locks my machine hard :-(
> it was working OK with 2.4.22-rc2-ac2! machine is on KT133 chipset.
> I cant use plain 2.4.22 because of trouble of compiling it with XFS
> support (unofficial patch has no .config entries).
update: i have compiled usbcore and usb-uhci into the kernel
and now it hangs with:
spurious 8259A interrupt: IRQ7
anybody?
--
Pawel Dziekonski <pawel.dziekonski|@|pwr.wroc.pl>, KDM WCSS avatar:0:0:
Wroclaw Networking & Supercomputing Center, HPC Department
-> See message headers for privacy policy info.
Can you try the following patch that I sent out the other day? I saw
this message when I was debugging, and it's gone with the patch. I
assume you have ACPI enabled.
Thanks,
Jun
> -----Original Message-----
> From: Pawel Dziekonski [mailto:[email protected]]
> Sent: Monday, September 01, 2003 8:36 AM
> To: [email protected]
> Subject: Re: 2.4.22-ac1 -- loading of usb-uhci gives hard lockup
>
> On nie, 31 sie 2003 at 04:11:25 +0200, Pawel Dziekonski wrote:
> > Hi,
> >
> > clean 2.4.22-ac1, load of usb-uhci.o locks my machine hard :-(
> > it was working OK with 2.4.22-rc2-ac2! machine is on KT133 chipset.
> > I cant use plain 2.4.22 because of trouble of compiling it with XFS
> > support (unofficial patch has no .config entries).
>
> update: i have compiled usbcore and usb-uhci into the kernel
> and now it hangs with:
> spurious 8259A interrupt: IRQ7
>
> anybody?
> --
> Pawel Dziekonski <pawel.dziekonski|@|pwr.wroc.pl>, KDM WCSS
avatar:0:0:
> Wroclaw Networking & Supercomputing Center, HPC Department
> -> See message headers for privacy policy info.
> -
---
diff -ru /build/orig/linux-2.4.23-pre1/drivers/acpi/pci_link.c
linux-2.4.23-pre1/drivers/acpi/pci_link.c
--- /build/orig/linux-2.4.23-pre1/drivers/acpi/pci_link.c
2003-08-25 04:44:41.000000000 -0700
+++ linux-2.4.23-pre1/drivers/acpi/pci_link.c 2003-08-29
20:21:13.000000000 -0700
@@ -216,7 +216,6 @@
return AE_CTRL_TERMINATE;
}
-
static int
acpi_pci_link_get_current (
struct acpi_pci_link *link)
@@ -275,6 +274,26 @@
return_VALUE(result);
}
+static int
+acpi_pci_link_try_get_current (
+ struct acpi_pci_link *link,
+ int irq)
+{
+ int result;
+
+ result = acpi_pci_link_get_current(link);
+ if (result && link->irq.active) {
+ return_VALUE(result);
+ }
+
+ if (!link->irq.active) {
+ ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "No active IRQ resource
found\n"));
+ printk(KERN_WARNING "_CRS returns NULL! Using IRQ %d for
device (%s [%s]).\n", irq, acpi_device_name(link->device),
acpi_device_bid(link->device));
+ link->irq.active = irq;
+ }
+
+ return 0;
+}
static int
acpi_pci_link_set (
@@ -359,7 +378,7 @@
}
/* Make sure the active IRQ is the one we requested. */
- result = acpi_pci_link_get_current(link);
+ result = acpi_pci_link_try_get_current(link, irq);
if (result) {
return_VALUE(result);
}
@@ -573,10 +592,6 @@
else
printk(" %d", link->irq.possible[i]);
}
- if (!link->irq.active)
- printk(", disabled");
- else if (!found)
- printk(", enabled at IRQ %d", link->irq.active);
printk(")\n");
/* TBD: Acquire/release lock */
On pon, 01 wrz 2003 at 07:07:32 -0700, Nakajima, Jun wrote:
> Can you try the following patch that I sent out the other day? I saw
> this message when I was debugging, and it's gone with the patch. I
> assume you have ACPI enabled.
I'm gonna try that tonight. And indeed, I had acpi enabled. Disabling it
"fixes" the problem immediately.
thanks, P
> > -----Original Message-----
> > From: Pawel Dziekonski [mailto:[email protected]]
> > Sent: Monday, September 01, 2003 8:36 AM
> > To: [email protected]
> > Subject: Re: 2.4.22-ac1 -- loading of usb-uhci gives hard lockup
> >
> > On nie, 31 sie 2003 at 04:11:25 +0200, Pawel Dziekonski wrote:
> > > Hi,
> > >
> > > clean 2.4.22-ac1, load of usb-uhci.o locks my machine hard :-(
> > > it was working OK with 2.4.22-rc2-ac2! machine is on KT133 chipset.
> > > I cant use plain 2.4.22 because of trouble of compiling it with XFS
> > > support (unofficial patch has no .config entries).
> >
> > update: i have compiled usbcore and usb-uhci into the kernel
> > and now it hangs with:
> > spurious 8259A interrupt: IRQ7
> >
> > anybody?
--
Pawel Dziekonski <pawel.dziekonski|@|pwr.wroc.pl>, KDM WCSS avatar:0:0:
Wroclaw Networking & Supercomputing Center, HPC Department
-> See message headers for privacy policy info.
On wto, 02 wrz 2003 at 08:19:59 +0200, Pawel Dziekonski wrote:
> On pon, 01 wrz 2003 at 07:07:32 -0700, Nakajima, Jun wrote:
> > Can you try the following patch that I sent out the other day? I saw
> > this message when I was debugging, and it's gone with the patch. I
> > assume you have ACPI enabled.
works! thanks, P
--
Pawel Dziekonski <pawel.dziekonski|@|pwr.wroc.pl>, KDM WCSS avatar:0:0:
Wroclaw Networking & Supercomputing Center, HPC Department
-> See message headers for privacy policy info.
Hello, I tried the patch you wrote (and noticed it is now in 2.4.22-ac3)
but I still have the same hard lockup Pawel Dziekonski has -- and, like
him, everything works when I don't compile ACPI into the kernel. My mobo is
a Soyo K7VTA-PRO, Athlon 950 Mhz, chipset VIA82Csomething.
Is there a piece of information I could send you that would help (BIOS
settings, /proc listings)? Please CC to me at j[CUBAN-DICTATOR'S-SURNAME]
@vialink.com.br, I'm not subscribed to LKML (but could be since I'm getting
broadband today. Yay!) :)
Cheers all,
Juan Carlos Castro y Castro
VIVO - Diretoria de Processos de Neg?cio - Projetos
Tel.: 55 (21) 2574-3506 - Cel.: 55 (21) 9603-7440
[email protected]
[email protected]
Marcelo released Linux 2.4.23-pre5, and it has more bug fixes. Can you please try that? It would provide more data.
Thanks,
Jun
---
<len.brown:intel.com>:
o Extended IRQ resource type for nForce (Andrew de Quincey) Handle BIOS with _CRS that fails (Jun Nakajima)
o Fix ACPI oops on ThinkPad T32/T40 (Shaohua David Li)
o support non ACPI compliant SCI over-ride specs (Jun Nakajima)
o remove ASUS A7V BIOS version 1011 from blacklist (Eric Valette)
o fix off-by-one error in ioremap() fixes kernel crash in acpi mode: http://bugzilla.kernel.org/show_bug.cgi?id=1085
o ACPI_CA_VERSION 0x20030916
o tables.c.diff
o from 2.6 acpi_pci_link_get_irq() returns 0 on error, not -ENODEV. (Christophe Saout)
o exclude acpitable.[ch] from the CONFIG_ACPI_HT_ONLY build
o [ACPI] delete acpitable.[ch], which used to be just for CONFIG_ACPI_HT_ONLY
o [ACPI] Fix SCI storm on out of spec boards like Tyan http://bugzilla.kernel.org/show_bug.cgi?id=774
o [ACPI] acpi_disabled is used after __initdata is freed
o [ACPI] fix IO-APIC mode SCI storm due to sharing with PCI device (David Shaohua Li) http://bugzilla.kernel.org/show_bug.cgi?id=1165
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Monday, September 22, 2003 7:10 AM
> To: Nakajima, Jun
> Cc: [email protected]; [email protected];
> [email protected]
> Subject: RE: 2.4.22-ac1 -- loading of usb-uhci gives hard lockup
>
> Hello, I tried the patch you wrote (and noticed it is now in 2.4.22-ac3)
> but I still have the same hard lockup Pawel Dziekonski has -- and, like
> him, everything works when I don't compile ACPI into the kernel. My mobo
> is
> a Soyo K7VTA-PRO, Athlon 950 Mhz, chipset VIA82Csomething.
>
> Is there a piece of information I could send you that would help (BIOS
> settings, /proc listings)? Please CC to me at j[CUBAN-DICTATOR'S-SURNAME]
> @vialink.com.br, I'm not subscribed to LKML (but could be since I'm
> getting
> broadband today. Yay!) :)
>
> Cheers all,
>
> Juan Carlos Castro y Castro
> VIVO - Diretoria de Processos de Neg?cio - Projetos
> Tel.: 55 (21) 2574-3506 - Cel.: 55 (21) 9603-7440
> [email protected]
> [email protected]
>
>
>
>