glyph,
@glyph@mastodon.social avatar

I saw someone ask the other day what the kernel panic screen looks like on Apple Silicon, and I realized that I wasn't sure I'd seen a panic at all on my M1; a far cry from my frequent acquaintance with the "You need to restart your computer" screen. Felt good, for a moment, about the improvements to reliability.

Today I achieved a kernel panic by accidentally appending to a BytesIO in Python unit test in a loop. (What this looks like is "full-screen magenta flash for one frame, then reboot.)

froztbyte,

@glyph I get to see this extremely frequently unfortunately: my 2020-series m1 has the blitting touchbar problem, and it frequently triggers panics and boot lockups :(

glyph,
@glyph@mastodon.social avatar

@froztbyte :-( what a strange, sad moment in time the touchbar was

froztbyte,

@glyph I'm one of those people who unironically like the idea (a dynamically programmable status display with interactivity? yespls), but the execution left so much to be desired

and then I'm double screwed because getting it fixed here is (because of a confluence of a few parts of local bullshit) likely to cost me at least a third of the original purchase price of the device

not v. happy about it

acsawdey,
@acsawdey@fosstodon.org avatar

@glyph I’ve been getting watchdog timeout panics on my M1 but they’re not very interesting to look at .. everything grinds to a halt and then after about 90 seconds, black screen and reboot.

glyph,
@glyph@mastodon.social avatar

@acsawdey yep, that's the exact backtrace I was seeing. Perhaps a similar cause, a memory-leaking process?

jacob,
@jacob@jacobian.org avatar

@glyph oh wow you’re right — it’s been YEARS since I’ve seen a kernel panic. Impressive.

glyph,
@glyph@mastodon.social avatar

@jacob apparently I can help you out with that, since I can do it in 2 lines of python now

hynek,
@hynek@mastodon.social avatar

@glyph @jacob is there anything Python CAN’T do!?

vathpela,
@vathpela@better.boston avatar

@hynek @glyph @jacob maintain compatibility for more than a month?

nedbat,
@nedbat@hachyderm.io avatar

@vathpela I'm sure people would be willing to help you with the problems you are seeing. This sounds like an extreme exaggeration, or a misunderstanding, but we can help.

vathpela,
@vathpela@better.boston avatar

@nedbat thankfully not my issue any more, but I worked on a fairly major python project for ~13 years and the one thing I'm sure of is that keeping a project working in /current/ python for a long time is an effort of constant, pointless churn, and nobody involved in the language sees that as a problem at all.

nedbat,
@nedbat@hachyderm.io avatar

@vathpela Every month was surely an exaggeration. Python tries very hard to be explicit about its compatibility guarantees which are basically, your code will keep working. There are exceptions, but they are visible and slowly rolled out. Perhaps the problems you had were with third-party libraries? In any case, let us know if you run into problems again.

cyberlyra,
@cyberlyra@hachyderm.io avatar

@glyph you are right. I think I’ve only seen that once or twice ever on the M1 chips. A long way from the ever-looming experience of those Blue Screens of Death.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • GTA5RPClips
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • tacticalgear
  • cubers
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • osvaldo12
  • ngwrru68w68
  • kavyap
  • InstantRegret
  • JUstTest
  • everett
  • Durango
  • cisconetworking
  • khanakhh
  • ethstaker
  • tester
  • anitta
  • Leos
  • normalnudes
  • modclub
  • megavids
  • provamag3
  • lostlight
  • All magazines