Opened 10 years ago

Last modified 10 months 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
Has a Patch: no Platform: All

Description

Backtrace attached.

Attachments (2)

block notifier writer.png (24.3 KB ) - added by emitrax 10 years ago.
block-notifier-kdl.txt (1.4 KB ) - added by jessicah 10 years ago.
kdl backtrace

Download all attachments as: .zip

Change History (11)

by emitrax, 10 years ago

Attachment: block notifier writer.png added

comment:1 by bonefish, 10 years ago

Component: - GeneralDrivers/USB
Owner: changed from nobody to mmlr

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.

comment:2 by emitrax, 10 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).

comment:3 by axeld, 10 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.

in reply to:  3 ; comment:4 by emitrax, 10 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. :-)

in reply to:  4 comment:5 by axeld, 10 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 axeld, 10 years ago

Blocking: 4940 added

(In #4940) Obviously the same as #4901. The NULL pointer stuff is also obviously not true, or else the error would look differently.

comment:7 by emitrax, 10 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)

by jessicah, 10 years ago

Attachment: block-notifier-kdl.txt added

kdl backtrace

comment:8 by jessicah, 10 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 waddlesplash, 10 months ago

Component: Drivers/USBDrivers/USB/UHCI
Note: See TracTickets for help on using tickets.