Is there a known issue with recent -CURRENT (between September 10, 2003 and
today) where
you can't get a panic dump?
I have a kernel from yesterday's sources (modulo a reversion of
ata-lowlevel to version
1.10 because 1.11 won't boot), and some debugging code from Nate Lawson to
debug my
ACPI
It seems Larry Rosenman wrote:
Also, when coming back up after the Panic on the same kernel, we get
unexpected soft-update
inconsistencies, cannot write block type errors from FSCK.
Going back to my September 9, 2003 kernel, fsck deals with the same exact
filesystem just fine.
What if
--On Sunday, September 14, 2003 18:46:19 +0200 Soren Schmidt
[EMAIL PROTECTED] wrote:
It seems Larry Rosenman wrote:
Also, when coming back up after the Panic on the same kernel, we get
unexpected soft-update
inconsistencies, cannot write block type errors from FSCK.
Going back to my September
--On Sunday, September 14, 2003 18:46:19 +0200 Soren Schmidt
[EMAIL PROTECTED] wrote:
It seems Larry Rosenman wrote:
Also, when coming back up after the Panic on the same kernel, we get
unexpected soft-update
inconsistencies, cannot write block type errors from FSCK.
Going back to my September
