Opened 11 years ago
Closed 11 years ago
#9929 closed bug (duplicate)
kernel regression: recent nightlies fail to boot on Toshiba Satellite L505D
Reported by: | tidux | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
R1A4.1 boots on this laptop. GPU, ethernet, and sound all work properly. The RTL8187SE wifi appears in listdev but not ifconfig. The most recent nightly, hrev45954, KDLs on the bootsplash screen with the message "page fault, but interrupts were disabled" and a kernel stack trace which seems to indicate the PCI subsystem is at fault. The prior two nightly builds, hrev45952 and hrev45951, simply stall forever at the bootsplash screen with none of the icons illuminated. Attached is a zipfile containing the syslog and listdev and listimage output for the machine.
Attachments (1)
Change History (9)
by , 11 years ago
Attachment: | toshiba-satellite-L505D.zip added |
---|
comment:1 by , 11 years ago
After trying a bunch of different nightlies on the L505D, this persists as far back as a nightly built in February (hrev45824).
follow-up: 4 comment:2 by , 11 years ago
Replying to tidux:
The most recent nightly, hrev45954, KDLs on the bootsplash screen with the message "page fault, but interrupts were disabled" and a kernel stack trace which seems to indicate the PCI subsystem is at fault.
Is the stack crawl similar to the one in #9930 (look on attached screenshot)?
comment:3 by , 11 years ago
"page fault, but interrupts were disabled" - my laptop died during boot to Haiku, and I've seen something like that before it died...
http://echelog.com/logs/browse/haiku/1376258400 - 23:29:40 http://echelog.com/logs/browse/haiku/1376604000 - 22:57:18
My laptop is under warranty and I sent it for repair.
comment:4 by , 11 years ago
comment:5 by , 11 years ago
comment:6 by , 11 years ago
comment:7 by , 11 years ago
Both the L505D and the HP Pavilion I was able to produce this bug on have died. The hardware is physically unable to boot anymore. I can no longer test this bug on the hardware on which I reported it.
comment:8 by , 11 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Really bad luck then, two laptops dying in a row :/ C
Possibly fixed anyway in hrev45976.
contains listdev, listimage, and syslog