Bug 5587
Summary: | Toshiba M200 PCI fails to allocate memory hence no PCI power related stuff works | ||
---|---|---|---|
Product: | Drivers | Reporter: | Alireza Ali (alireza.ali) |
Component: | PCI | Assignee: | Greg Kroah-Hartman (greg) |
Status: | REJECTED WILL_NOT_FIX | ||
Severity: | high | CC: | acpi-bugzilla |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.14 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 5829 | ||
Attachments: | dmesg dump after boot |
Description
Alireza Ali
2005-11-10 11:10:55 UTC
Created attachment 6527 [details]
dmesg dump after boot
punting this over to the PCI sub-system. IIR they had some regressions recently and this may be a duplicate. It would be interesting to test 2.6.13.stable to isolate if the regression happened before or after 2.6.13. I compiled and installed 2.6.13 and the same issue was happened again. Can you please try 2.6.16-rc3, or at the least, 2.6.15. This should be fixed by now. Please let us know. I installed 2.6.15.4 but the problem is this time when i try to reboot using the reboot command. the computer does not restart. it seem the goes successfullt to shutdown stage but it wont go back up. After more investigation it looks like that kernel can't initilize the ipw2100 after a reboot. I dont know if this helps but after a reboot , If i go to windows same thing happens on windows and it hangs on slpash scree. rather than something in start up it seems something is not getting shut down properly. As Windows has the same issues, I would really blame your hardware/BIOS here. Make sure you have the latest BIOS update from your manufacturer. So I'm going to close this for now, if there's anything that we can help out with, please reopen this. The problem is why this situation does not happen when I'm restarting the Windows? I never had any problem like this with windows and my BIOS. Moreover, I always keep the BIOS to the latest version. Now I am running BIOS 1.70 for Toshiba M200. I think there is something in linux kernel rather than BIOS. But as this does not cause any problems with your machine, I'm just going to close it out. Sorry, I don't know what else to do. If this does cause a problem with it working properly, please feel free to reopen. |