Bug #429: BLAST error descriptors lacks details - Linux Driver Verification - Open-Source Projects

Custom queries

Composite Backlog
LDV+BLAST
LDV-Git bugs

Actions

Copy link

Bug #429

closed

BLAST error descriptors lacks details

Added by Alexey Khoroshilov about 14 years ago. Updated over 13 years ago.

Status:

Closed

Priority:

High

Assignee:

Vadim Mutilin

Category:

Infrastructure

Start date:

09/09/2010

Due date:

% Done:

Estimated time:

Detected in build:

7e62c9a9

Platform:

Published in build:

Description

For example, [rule: 08_1; drivers: lgs8gxx.ko, specialix.ko, stv0299.ko, tc1100-wmi.ko, usbnet.ko; environment model: ldv_main0_plain_sorted_withcheck]

Descriptor is "empty":

=========== Launch information ===========
Verifier: BLAST ()
Time Limit: 5000 sec
Memory Limit: 3000000 Kb
Additional options: -enable-recursion -fdepth 5
Solver: default
=========== Launch inform ends ===========

Another example, [rule: 32_1; drivers: a800.ko, at76c50x-usb.ko, and 105 more; environment model: ldv_main0_plain_sorted_withcheck]

ZZZ: Exception: Errormsg.Error
=========== Launch information ===========
Verifier: BLAST ()
Time Limit: 5000 sec
Memory Limit: 2000000 Kb
Additional options: -enable-recursion -fdepth 5
Solver: default
=========== Launch inform ends ===========

Related issues 1 (0 open — 1 closed)

Has duplicate Linux Driver Verification - Bug #493: Incomplete BLAST bug descriptors

Closed

Pavel Shved

10/18/2010

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Evgeny Novikov almost 14 years ago

Priority changed from Normal to High

I think that it's rather important issue, since we lose statistics about problems gathered by BLAST and must have to see files by hand to understand where is the problem.

Actions

Copy link

Updated by Pavel Shved almost 14 years ago

Category set to Infrastructure

I agree that it's important.

Actions

Copy link

Updated by Alexey Khoroshilov over 13 years ago

Detection of "OCaml exception: Fatal error: out of memory." has been fixed.

Now, I have another example of uninformative Errormsg.Error descriptor coming from the following BLAST trace:

...32_7/drivers/isdn/hisax/config.c:1988: Warning: .../32_7/drivers/isdn/hisax/config.c:1988: CIL only supports attribute((alias)) for functions.

Bug: Visitor's instruction queue is not empty.
  You should only use queueInstr inside a function body!
Exception in Simplemem.simplemem: Errormsg.Error
Timings:
TOTAL                          0.960 s (1)
  Parse:                         0.960 s (1)
Ack! The gremlins again!: Errormsg.Error
Ack! The gremlins again!: Errormsg.Error
Fatal error: exception Errormsg.Error

The trace is generated by the following command:

ldv-git --rule=32_7 --filter=isdn/hardware/avm/b1pcmcia check

Actions

Copy link

Updated by Evgeny Novikov over 13 years ago

In processing of all 2.6.31.6 drivers against 32_1 model I found following error descriptors lacks (* may be require some reference to the problem description):

Parsing errors
acpi/battery.ko
acpi/sbs.ko
infiniband/core/ib_core.ko
infiniband/core/ib_sa.ko
input/misc/yealink.ko
input/mouse/psmouse.ko
isdn/capi/kernelcapi.ko
net/benet/be2net.ko
net/e1000e/e1000e.ko
net/igb/igb.ko
net/igbvf/igbvf.ko
net/ixgb/ixgb.ko
net/ixgbe/ixgbe.ko
net/netxen/netxen_nic.ko
net/sfc/sfc.ko
net/wireless/b43/b43.ko
net/wireless/b43legacy/b43legacy.ko
net/wireless/libertas/libertas.ko
scsi/initio.ko
uwb/i1480/i1480-est.ko
uwb/uwb.ko
video/matrox/matroxfb_g450.ko
video/matrox/matroxfb_maven.ko
Exception
block/xen-blkfront.ko
cdrom/cdrom.ko
firewire/firewire-core.ko*
firewire/firewire-ohci.ko
hid/hid-apple.ko
ieee1394/ieee1394.ko
isdn/hisax/hfc_usb.ko
md/raid6_pq.ko
media/dvb/dvb-usb/dvb-usb-m920x.ko
mmc/host/mmc_spi.ko
mtd/devices/m25p80.ko
mtd/devices/mtd_dataflash.ko
mtd/mtd.ko
mtd/nand/alauda.ko
net/sis190.ko*
net/wan/farsync.ko
net/wireless/ath/ar9170/ar9170usb.ko
net/wireless/zd1211rw/zd1211rw.ko
net/xen-netfront.ko
platform/x86/asus-laptop.ko
platform/x86/eeepc-laptop.ko

Exception descriptions sometimes are incomplete ('XXX should be implemented', 'Not found', 'See above' and so on) but sometimes have a corresponding problem. Parsing errors don't point out a particular place and construction that leads to it ('Errormsg.Error').

Actions

Copy link

Updated by Alexey Khoroshilov over 13 years ago

Also it would be very helpful if blast instead of suicide with message:

BLAST couldn't find entry point/error location at .../bin/../dscv/rcv/blast line 343.

prepares useful descriptor that can be matched later.

Actions

Copy link

Updated by Vadim Mutilin over 13 years ago

Status changed from New to Open

Fixed most of the problem in commit=b6a9a03
Now error description contains last 100 lines of the error log (printing of statistics is redirected to stdout).

The problem of useful descriptor for

BLAST couldn't find entry point/error location at .../bin/../dscv/rcv/blast line 343.

still remains. But here is the problem with general logging and discovering intergation errors and not with blast error description, because the statistics server shows nothing in this case.

Actions

Copy link