Re: kernel panic while copying files

From: Gary Jennejohn <gljennjohn_at_gmail.com>
Date: Tue, 08 Jun 2021 11:34:21 UTC 
On Tue, 8 Jun 2021 11:20:37 +0200
Hans Petter Selasky <hps@selasky.org> wrote:

> On 6/8/21 11:04 AM, Mateusz Guzik wrote:
> > Apparently caused by recent changes to CAM.
> > 
> > Let me know if you want more information.  
> 
> Maybe you can print the *ccb being freed and figure out which device
> it belongs to.
> 

I'm now running a kernel without INVARIANTS, so I can check:

Jun  8 13:23:52 ernst kernel: ugen2.4: <ASMedia asm1153e> at usbus2
Jun  8 13:23:52 ernst kernel: umass0 on uhub5
Jun  8 13:23:52 ernst kernel: umass0: <ASMedia asm1153e, class 0/0, rev 3.00/1.00, addr 3> on usbus2
Jun  8 13:23:52 ernst kernel: umass0:  SCSI over Bulk-Only; quirks = 0xc101
Jun  8 13:23:52 ernst kernel: umass0:6:0: Attached to scbus6
Jun  8 13:24:37 ernst kernel: da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
Jun  8 13:24:37 ernst kernel: da0: <ASMedia asm1153e 0> Fixed Direct Access SPC-4 SCSI device
Jun  8 13:24:37 ernst kernel: da0: Serial Number 000000000001
Jun  8 13:24:37 ernst kernel: da0: 400.000MB/s transfers
Jun  8 13:24:37 ernst kernel: da0: 7630885MB (15628053168 512 byte sectors)
Jun  8 13:24:37 ernst kernel: da0: quirks=0x2<NO_6_BYTE>

The only USB device which I turned on.

Fields in the ccb like periph_name, unit_number and dev_name are filled
with zeroes.

The ccb is enormous and really hard to parse.

-- 
Gary Jennejohn