#3134 closed bug (fixed)
KDL (page daemon) when booting on Lenovo S9
Reported by: | mr. Noisy | Owned by: | marcusoverhagen |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Disk | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #2488, #3988 | |
Platform: | x86 |
Description
Boot hangs up with KDL after 4th (disk with leaf) icon: PANIC: page fault, but interrupts were disabled Touching address 0xccccccd8 from eip 0x8004992d
Thread 8 "page daemon" (in some cases "Thread 7 page write" Running on CPU 0
Happens with hrev28641 (pre-alpha image) Hardware specs: Intel Atom N270 1.6GHz, 1GB RAM, HDD 120GB Boot media: USB Flash Drive Kingston DataTraveler 2GB
Change History (14)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
You should be able to replace the "ide" bus_manager with the newer (yet, incomplete and slower) "ata" bus_manager to get past this error (see ticket #2349 where I was able to get past this same problem that way). You'll need to modify a jamfile and compile a new image to do this.
The ide bus_manager has known issues and it is planned to be replaced by the ata bus_manager (hopefully before alpha).
comment:3 by , 16 years ago
Component: | - General → Drivers/Disk |
---|---|
Owner: | changed from | to
comment:4 by , 16 years ago
Just noted your KDL was in a different thread, but still I wouldn't be surprised if it was related to the bus_manager.
comment:5 by , 16 years ago
Blocking: | 3988 added |
---|
comment:6 by , 16 years ago
Blocking: | 2488 added |
---|
comment:7 by , 16 years ago
I have this error too: PANIC: page fault, but interrupts were disabled. Touching address 0xccccccd8 from eip 0x8004ed91
Changing in BIOS SATA mode from IDE to AHCI was resolved this problem on my system: Core2Duo E4500 / 2 GB RAM / Asus P5B (P965, ICH8) / Radeon X1950Pro / 2 SATA HDD / PATA DVD+RW
comment:8 by , 16 years ago
In my case, this change also solves the problem, but after that the hard disk is not detected by BIOS. Certainly Windows does not boot after that. Hauku couldn't find it in DriveSetup.
comment:10 by , 14 years ago
Can you recheck this with a recent Haiku build? It may have been fixed recently.
comment:11 by , 14 years ago
Blocking: | 7665 added |
---|
comment:14 by , 6 years ago
Blocking: | 7665 removed |
---|
Enabling AHCI Compliant mode solves the problem.