Opened 14 years ago

Closed 6 years ago

#6463 closed bug (not reproducible)

BFS vm_page_fault: unhanded page fault in kernel space

Reported by: kallisti5 Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Looks syslog triggered a bfs related page fault while I was doing an svn update.

notify_transaction_listeners was the cause?

See attached KDL output

hrev38062 gcc4/hybrid

didn't see any other bugs open with BFS page faults.

Attachments (6)

IMG_20100817_144119.jpg (271.2 KB ) - added by kallisti5 14 years ago.
page fault trace
KDL_Capture.jpg (164.0 KB ) - added by kran 14 years ago.
KDL_Capture.2.jpg (164.0 KB ) - added by kran 14 years ago.
KDL Output Capture (Kran)
listdev.output.txt (2.6 KB ) - added by kran 14 years ago.
listdev output - Kran
listimagedriver.output.txt (1.6 KB ) - added by kran 14 years ago.
listimage driver output - Kran
listusb.output.txt (356 bytes ) - added by kran 14 years ago.
listusb output - Kran

Download all attachments as: .zip

Change History (10)

by kallisti5, 14 years ago

Attachment: IMG_20100817_144119.jpg added

page fault trace

by kran, 14 years ago

Attachment: KDL_Capture.jpg added

by kran, 14 years ago

Attachment: KDL_Capture.2.jpg added

KDL Output Capture (Kran)

by kran, 14 years ago

Attachment: listdev.output.txt added

listdev output - Kran

by kran, 14 years ago

Attachment: listimagedriver.output.txt added

listimage driver output - Kran

by kran, 14 years ago

Attachment: listusb.output.txt added

listusb output - Kran

comment:1 by kran, 14 years ago

I am encountering this issue on every installation attempt for gcc4hybrid nightly installs of hrev38062, hrev38209, and hrev38259. I am also hitting this on LiveCD runs from these nightlies as well. I suspect it is related to a specific hardware configuration, so I have attached hardware logs as well as the KDL output on my system.

comment:2 by axeld, 14 years ago

Component: File Systems/BFSSystem/Kernel

Only the first KDL is block cache related, the rest might indeed be a specfic hardware issue. The block cache problem is already tracked elsewhere I believe.

comment:3 by waddlesplash, 6 years ago

Still an issue?

comment:4 by kallisti5, 6 years ago

Resolution: not reproducible
Status: newclosed

If it is, i've likely opened duplicates much more recently with more relevant backtraces :-)

Note: See TracTickets for help on using tickets.