Compaq 1700, 2.4.18, acpi-7,24 - SUCCESS (I think)
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi HK,
I'm using a 1700T, 2.4.18 and acpi-20020726. When I boot, the laptop locks up early on, after two "PCI Interrupt Link [LNKC] enabled" messages (with ACPI debug messages turned on). I'm new to linux ACPI, but understand the 1700 series ACPI firmware may be buggy. Can you provide some details on what you did to make things work with your 1700? Which ACPI features work for you?
Thanks very much,
Graham
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
A message that is not in the archive (sent off-list or not yet received): 15706.48376.457358.298696-+pt9qS7RU9EeNw9RxQLXc5Vzexx5G7lz@public.gmane.org
Hi list,
Graham, nice to see that I am not all alone :) I too have the same status with the acpi-20020726 patch on a similar model (mine is 1720US).
However, my kernel just keeps repeating "schedule_task(): kevent has not started" after the alleged two "PCI Interrupt Link enabled" statements. It never freezes.
Just before these statements I used to get an error:
"pci_bind_0191[22] acpi_pci_bind device 00:00:1d.02 not present in PCI namespace".
Hawkins, pointed out that my DSDT had a USB entry at that ID. However, physically I have just two USB ports. So I decided to re-modify my dsdt.asl by removing that particular entry in my namespace. This modification did help to remove the above error (only).
Just out of curiosity I did check the asl files of couple of other members (Faye and Sourov -- Compaq presario 27xx/28xx). To my surprise I did find similar kind of extra USB entries in their DSDT namespace (but their kernel boot fine).
I ain't sure whatelse to do. Tght that it might be a good idea to get familiar with ACPI specs. So after 20 kernel compiles I decided to spend my next few days on reading ACPI 2.0 specs (www.acpi.info). Hope to find something which can help me fix my "buggy" ACPI tables.
regards
Signature · 23 lines
*******************************--------------********************************** GVS Prabhakar Reddy Research Assistant Model Analysis Lab (GIS Lab) Dept. of Biological Resources Engineering University of Maryland College Park, MD, 20742. tel: 301-405-0109 (o) : 301-982-7148 (r) fax: 301-314-9023 email: reddyg-0KJXeWapumv2fBVCVOL8/[email protected] **************************--------------------********************************* ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31
A message that is not in the archive (sent off-list or not yet received): Pine.GSO.4.21.0208142004370.16304-100000-Bq+f90TzBY23n+kRt3O4EA@public.gmane.org
Quoted 6 lines · Prabhakar Reddy Gudla Venkata Siva [reddyg-3+M4TpyeDAP2fBVCVOL8/[email protected].…
Graham, nice to see that I am not all alone :) I too have the same status with the acpi-20020726 patch on a similar model (mine is 1720US).
However, my kernel just keeps repeating "
schedule_task(): kevent has not started" after the alleged two "PCI Interrupt Link enabled" statements. It never freezes.
My kernel would freeze if I enabled Local APIC on Uniprocessor. Since ACPI does the IRQ routing this is probably what is confusing things. It would be useful if the one could override the other if it's being used. I make mention of this on my website and my kernel patch's default configuration has these options disabled.
Other people have mentioned a problem with losing interrupts on some models of Compaq - I haven't suffered from this and there is a patch for this which someone has made (which since I don't use it hasn't stuck in my memory I'm afraid).
I do get the warning about the unknown device, but I ignored it as I knew I didn't have the device. I will remove it from my DSDT now I know what's causing it ;)
Faye
Signature · 12 lines
Faye Pearson, Software Development Manager, ClaraNET Ltd. Tel 020 7903 3000 Even God lends a hand to honest boldness. -- Menander ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
Quoted 8 lines · Prabhakar Reddy Gudla Venkata Siva
Hi list,
Graham, nice to see that I am not all alone :) I too have the same status with the acpi-20020726 patch on a similar model (mine is 1720US).
However, my kernel just keeps repeating "
schedule_task(): kevent has not started" after the alleged two "PCI Interrupt Link enabled" statements. It never freezes.
The only case I see for such bug (the schedule_task(): kevent...) is to call osl::acpi_os_queue_for_execution(), but keventd is not started at this stage. I think that one _STA function, or one _INI function did a 'Notify', so that osl::acpi_os_queue_for_execution() is called.
Signature · 9 lines
Ducrot Bruno http://www.poupinou.org Page profaissionelle http://toto.tu-me-saoules.com Haume page ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
A message that is not in the archive (sent off-list or not yet received): 20020816085840.GD10248-j6u/t2rXLliUoIHC/UFpr9i2O/[email protected]
Hi Bruno,
So what is the solution for the problem ? Do u have any ?
<snip>
Quoted 3 lines
Quoted 3 lines
However, my kernel just keeps repeating "
schedule_task(): kevent has not started" after the alleged two "PCI Interrupt Link enabled" statements. It never freezes.
<snip>
Quoted 5 lines
The only case I see for such bug (the
schedule_task(): kevent...) is to callosl::acpi_os_queue_for_execution(), but keventd is not started at this stage. I think that one_STAfunction, or one_INIfunction did a 'Notify', so thatosl::acpi_os_queue_for_execution()is called.
Signature · 8 lines
Reddy ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
A message that is not in the archive (sent off-list or not yet received): Pine.GSO.4.21.0208161730480.24869-100000-Bq+f90TzBY23n+kRt3O4EA@public.gmane.org
Quoted 3 lines · Prabhakar Reddy Gudla Venkata Siva
Hi Bruno,
So what is the solution for the problem ? Do u have any ?
I have no time to search a solution for this problem: I have
a job that take me all my time (even the parse one...), but I think that I can work for something for this trouble when I will have more sparse time to spend in one or two week.
Quoted 18 lines
<snip>
Quoted 3 lines
Quoted 3 lines
However, my kernel just keeps repeating "
schedule_task(): kevent has not started" after the alleged two "PCI Interrupt Link enabled" statements. It never freezes.<snip>
Quoted 5 lines
The only case I see for such bug (the
schedule_task(): kevent...) is to callosl::acpi_os_queue_for_execution(), but keventd is not started at this stage. I think that one_STAfunction, or one_INIfunction did a 'Notify', so thatosl::acpi_os_queue_for_execution()is called.Signature · 1 line
Reddy
Signature · 9 lines
Ducrot Bruno http://www.poupinou.org Page profaissionelle http://toto.tu-me-saoules.com Haume page ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390