Re: panic: make_dev_alias_v: bad si_name

2022-06-04 Thread Alan Somers 
On Sat, Jun 4, 2022 at 1:04 PM Warner Losh  wrote:
>
>
>
> On Sat, Jun 4, 2022, 11:13 AM Yuri  wrote:
>>
>> Getting the following panic on HPE system with HPE enclosure:
>>
>> panic: make_dev_alias_v: bad si_name (error=22,
>> si_name=enc@n../type@0/slot@1/elmdesc@{"Name":"DriveBay1"}/pass4)
>>
>> db_trace_self_wrapper()
>> vpanic()
>> panic()
>> make_dev_alias_v()
>> make_dev_alias_p()
>> make_dev_physpath_alias()
>> pass_add_physpath()
>> taskqueue_run_locked()
>> taskqueue_thread_loop()
>> fork_exit()
>> fork_trampoline()
>>
>> I have skipped typing all the frame information as the cause of panic
>> seems to be apparent -- enclosure replies with "Name":"DriveBay1" via
>> ses (it does the same weirdness for sensors and other elements), and
>> make_dev_alias_v() does not like the double quotes.  Probably we need to
>> sanitize the input somewhere?
>
>
>
> Likely.  I'll take a look. Can you file a bug, include CAM in the title and 
> cc imp@ please?
>
> Warner

Also, it would help to include the output of "sg_ses -p7 /dev/sesXXX",
where sg_ses comes from sysutils/sg3_utils.

Re: panic: make_dev_alias_v: bad si_name

2022-06-04 Thread Warner Losh 
On Sat, Jun 4, 2022, 11:13 AM Yuri  wrote:

> Getting the following panic on HPE system with HPE enclosure:
>
> panic: make_dev_alias_v: bad si_name (error=22,
> si_name=enc@n../type@0/slot@1/elmdesc@{"Name":"DriveBay1"}/pass4)
>
> db_trace_self_wrapper()
> vpanic()
> panic()
> make_dev_alias_v()
> make_dev_alias_p()
> make_dev_physpath_alias()
> pass_add_physpath()
> taskqueue_run_locked()
> taskqueue_thread_loop()
> fork_exit()
> fork_trampoline()
>
> I have skipped typing all the frame information as the cause of panic
> seems to be apparent -- enclosure replies with "Name":"DriveBay1" via
> ses (it does the same weirdness for sensors and other elements), and
> make_dev_alias_v() does not like the double quotes.  Probably we need to
> sanitize the input somewhere?
>


Likely.  I'll take a look. Can you file a bug, include CAM in the title and
cc imp@ please?

Warner

>

panic: make_dev_alias_v: bad si_name

2022-06-04 Thread Yuri 
Getting the following panic on HPE system with HPE enclosure:

panic: make_dev_alias_v: bad si_name (error=22,
si_name=enc@n../type@0/slot@1/elmdesc@{"Name":"DriveBay1"}/pass4)

db_trace_self_wrapper()
vpanic()
panic()
make_dev_alias_v()
make_dev_alias_p()
make_dev_physpath_alias()
pass_add_physpath()
taskqueue_run_locked()
taskqueue_thread_loop()
fork_exit()
fork_trampoline()

I have skipped typing all the frame information as the cause of panic
seems to be apparent -- enclosure replies with "Name":"DriveBay1" via
ses (it does the same weirdness for sensors and other elements), and
make_dev_alias_v() does not like the double quotes.  Probably we need to
sanitize the input somewhere?

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

2017-11-15 Thread Conrad Meyer 
Hi Wolfram,

I believe r305900 broke it.  I don't have any patch or workaround,
sorry.  It wouldn't be too hard for someone interested in
virtualization to fix the issue.  Please follow up in the bug :-).

Best,
Conrad

On Wed, Nov 15, 2017 at 7:16 AM, Wolfram Schneider  wrote:
> Hi Conrad,
>
> thanks for the hint. Do you know which commit may broke the driver? Is
> there any patch or workaround?
>
> I do not have access to the physical machine, only full root access to
> the guest. I don't want to bother with the cloud provider, I'm happy
> that they offer FreeBSD at all as a default installation.
>
> -Wolfram
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

2017-11-15 Thread Wolfram Schneider 
On 15 November 2017 at 10:58, Conrad Meyer  wrote:
> Hi Wolfram,
>
> Looks like the same issue as
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 .

Hi Conrad,

thanks for the hint. Do you know which commit may broke the driver? Is
there any patch or workaround?

I do not have access to the physical machine, only full root access to
the guest. I don't want to bother with the cloud provider, I'm happy
that they offer FreeBSD at all as a default installation.

-Wolfram


> Best,
> Conrad
>
> On Wed, Nov 15, 2017 at 1:31 AM, Wolfram Schneider  wrote:
>> Hi,
>>
>> I have a virtual machine running with FreeBSD 11-stable at a cloud
>> provider. It runs fine. I tried to upgrade to FreeBSD 12-current and
>> the kernel panics at boot time with:
>>
>> make_dev_alias_v bad si_name (error=22) si_name=vtcon/ 
>> org.qemu.guest_agent.0)
>>
>> and hangs. Lucky, I still can boot from kernel.old and bring the machine up.
>>
>> any idea whats wrong here?
>>
>> -Wolfram
-- 
Wolfram Schneider  https://wolfram.schneider.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

2017-11-15 Thread Conrad Meyer 
Hi Wolfram,

Looks like the same issue as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 .

Best,
Conrad

On Wed, Nov 15, 2017 at 1:31 AM, Wolfram Schneider  wrote:
> Hi,
>
> I have a virtual machine running with FreeBSD 11-stable at a cloud
> provider. It runs fine. I tried to upgrade to FreeBSD 12-current and
> the kernel panics at boot time with:
>
> make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)
>
> and hangs. Lucky, I still can boot from kernel.old and bring the machine up.
>
> any idea whats wrong here?
>
> -Wolfram
>
> --
> Wolfram Schneider  https://wolfram.schneider.org
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

2017-11-15 Thread Wolfram Schneider 
Hi,

I have a virtual machine running with FreeBSD 11-stable at a cloud
provider. It runs fine. I tried to upgrade to FreeBSD 12-current and
the kernel panics at boot time with:

make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

and hangs. Lucky, I still can boot from kernel.old and bring the machine up.

any idea whats wrong here?

-Wolfram

-- 
Wolfram Schneider  https://wolfram.schneider.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"