Opened 10 years ago

Closed 9 years ago

#3793 closed bug (junk)

checkfs crashes to KDL when finding error in BFS-partitioned USB stick

Reported by: haiqu Owned by: mmlr
Priority: normal Milestone: R1
Component: Drivers/USB Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Initialized and partitioned a 2Gb USB memory stick under BeOS 5.0.3 then populated it with the repository's source files. I had a lockup that required a reboot while copying, so ran checkfs on the drive to fix it prior to continuing.

checkfs found an error, but then immediately threw me into KDL and locked the machine. I have also had this happen under the conditions of doing an `svn up' from that drive, and when svn can't access a file properly.

Change History (6)

comment:1 Changed 10 years ago by mmlr

You do realize that there is not only one single reason for a KDL? Please provide necessary info like the KDL message and a back trace. I also take it that you only used R5 to initialize the stick and then did the rest under Haiku?

comment:2 Changed 10 years ago by haiqu

Yes, BeOS was only used to init/partition the stick, which was necessary due to Haiku's DriveSetup being incomplete (see #3766).

Unfortunately the information available at KDL isn't very useful. It failed to read an inode and didn't have a handler for the error from what I could gather. The machine locked so I couldn't do much else, and I don't have a serial debug terminal attached.

comment:3 Changed 10 years ago by haiqu

OK, here's a crash message for you. Not related to checkfs at all, it was encountered during a bulk copy to the stick with nothing much else happening at the time:

{{ PANIC: Could not write back block 467461 (Operation timed out)

Welcome to Kernel Debugging Land...

Thread 209 "Move Task running on CPU0 kdebug> }}}

Hope that gives you some idea of where to look. It seems to me as if this should do several retries and, on failing to write, mark the block as faulty and move on. Instead we're getting a total crash because the system doesn't quite know what to do under the circumstances.

comment:4 Changed 10 years ago by mmadia

mmlr said:

Please provide necessary info like the KDL message and a back trace.

Once inside KDL, type bt without quotes to run the backtrace command. That information is standard when reporting KDL error messages.

comment:5 Changed 10 years ago by haiqu

From two messages back:

"The machine locked so I couldn't do much else, and I don't have a serial debug terminal attached."

Please read the entire log before replying.

comment:6 Changed 9 years ago by mmadia

Resolution: junk
Status: newclosed

Closing as junk due to not being able to provide useful information. Please re-open if you can reproduce this bug *and* provide information. For some time now, KDL will output a default bt without the need for user-intervention.

Note: See TracTickets for help on using tickets.