Opened 15 years ago
Last modified 6 weeks ago
#4901 new bug
Block notifier/writer KDL'es while checkin out Webkit source code on a USB stick BFS formatted
Reported by: | emitrax | Owned by: | mmlr |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/USB/UHCI | Version: | R1/alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #4940 | |
Platform: | All |
Description
Backtrace attached.
Attachments (2)
Change History (12)
by , 15 years ago
Attachment: | block notifier writer.png added |
---|
comment:1 by , 15 years ago
Component: | - General → Drivers/USB |
---|---|
Owner: | changed from | to
comment:2 by , 15 years ago
Does reboot sync's automatically ?
I got other crash after reboot. I tried continuing with git checkout and git crashed itself, then after continuing, media checker KDL'ed on get_cache_blocked, but I don't know if all this is related so I'm not sure opening another bug is correct.
My worries is that all this crashes and KDL somehow corrupted the BFS partition on the stick, and they are causing all the other bugs. I'll run checkbfs if it's in the image.
BTW: this bug was on vmware one of the last revision (last checkout was yestarday 4th November).
follow-up: 4 comment:3 by , 15 years ago
No matter how corrupted the BFS image would be, it wouldn't cause these errors (only different ones ;-)).
Besides that, BFS is a journaled file system, and shouldn't corrupt due to KDLs.
follow-up: 5 comment:4 by , 15 years ago
Replying to axeld:
No matter how corrupted the BFS image would be, it wouldn't cause these errors (only different ones ;-)).
I also run the test and found not error (only a suggestion of three blocks that could be deleted, but how?)
Besides that, BFS is a journaled file system, and shouldn't corrupt due to KDLs.
Then new bug it is. :-)
comment:5 by , 15 years ago
Replying to emitrax:
I also run the test and found not error (only a suggestion of three blocks that could be deleted, but how?)
It's not a suggestion, it's the simple past.
comment:6 by , 15 years ago
Blocking: | 4940 added |
---|
comment:7 by , 15 years ago
Happened again. Serial output follow.
PMA: found no free slot to store 512 bytes (4991 tries left) heap_add_area: area 3453 added to small heap 0x80f9c000 - usable range 0x90407000 - 0x90800000 PMA: found no free slot to store 512 bytes (4999 tries left) bfs: _RemoveDuplicate:1486: No such file or directory bfs: Could not find value in index "size"! bfs: Update:291: No such file or directory heap_add_area: area 11400 added to large heap 0x81c68ccc - usable range 0xa1c01000 - 0xa2000000 usb error uhci 0: td (0x036eca40) error: status: 0x004407ff; token: 0x3fe082e1; usb_disk: sending or receiving of the data failed usb_disk: write fails with 0xffffffff bfs: could not write log area: General system error! usb error uhci 0: td (0x036ee3c0) error: status: 0x004407ff; token: 0x3fe082e1; usb_disk: sending or receiving of the data failed usb_disk: write fails with 0xffffffff bfs: could not write log area: General system error! usb error uhci 0: td (0x036f0440) error: status: 0x004407ff; token: 0x3fe882e1; usb_disk: sending or receiving of the data failed usb_disk: write fails with 0xffffffff PANIC: could not write back block 6177 (General system error)
comment:8 by , 15 years ago
Had a similar problem, also happened again while linking some part I can't remember.
Hopefully no typos in attachment (writing it all into notepad was painstaking!) :)
comment:9 by , 6 years ago
Component: | Drivers/USB → Drivers/USB/UHCI |
---|
Supposedly a USB problem. Please attach a syslog (be sure to continue and sync before rebooting).
Other than that, in a production release the block notifier/writer shouldn't panic(), of course.