Scrum Master Behavior

I’m a new Product Owner and I’m curious if my scrum master’s behavior is fairly standard.

First, I notice he’ll cut someone off if they are trying to explain something, for example: “Yeah, yeah, yeah, enough about that, we are running out of time.” - Like I get there’s a time limit, but cutting someone off like that to stay within the time limit and potentially miss information/knowledge transfer seems to contrary to effective team work and agile.

Second, He randomly missed a DSU and didn’t give a heads up, so I ran the DSU and took 2 pages of notes in a word document. I called him about it and he said - “I’m just testing to see if the team could function without me and grow as a team.” He didn’t even thank me for the notes. A week later he was 5 minutes late, and this week (on my day off) he texted me 10 minutes before the DSU telling me I need to help him run it because he wasn’t home yet.

Third, He misses meetings that he sets, and randomly reschedules them without recommending new times or considering my calendar. So I’ll be in back to back meetings on the product side and get a message from him asking why I’m not in his meeting. One day he rescheduled the same meeting 4 different times.

Since I’m fairly new to scrum, I’m wondering, is normal scrum master behavior?