From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f51.google.com ([209.85.210.51]) by ewsd; Sat Sep 28 21:15:35 EDT 2019 Received: by mail-ot1-f51.google.com with SMTP id 41so5426572oti.12 for <9front@9front.org>; Sat, 28 Sep 2019 18:15:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:to:subject:date:mime-version :content-transfer-encoding; bh=pdd3mdD7BtEoH0uIkpASf8/GxA/i0D0Tn95/GzCqJIA=; b=u5D3vXLnzr/XptTxtLiestJoOMYTqAEB41h5JMPHbSlt0PLkkSKW20N2lkUL2g5fIR YU5KuP1K7UFKCpRxCNzZ4Z8U620tRHccKO6NhgE915SLbgyYvWf3iWC84ScPiXghCwr5 kjNjtEsc4X2vxza9cj9UvIECIHaeUvj8oMMrNNvnTongDKaUtYS0VsNvdce84Om5Ma9q Y9uNPlB0/a4DDbVvd3JqE4bmoXn3yc8w8dXGyZraSvJrphQQMFpsRAeAoQwEUnOCCeuc IqH0UrLgAJEtpI6p6HGK1Wo98W6UzGLX8Bm/Ckg3zRjnj3PEU15kmXHo5groNCbfWoaW 5E2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:to:subject:date:mime-version :content-transfer-encoding; bh=pdd3mdD7BtEoH0uIkpASf8/GxA/i0D0Tn95/GzCqJIA=; b=ddIv0Wh2gA3OS1Dlx7bh39EpcVkIEOAnrxF+QFuim1zDCb1ftYGJaU6yI0X1swUiNM JC3+VNK5GnK3Q1H86N0AT7jUTRpZ04l9qnUsb3voFfWc/5ntm9HxpG2B8Rrv9FjFAb2M 023kMxPhhs1lM8OJ9SNB/MhNmCD3f9f4AdsioC/vwSP6KeqP9cbhwRlV2yI9AuMvXxnq pTvVEv2iM8X77Lknvw5S/beGDXeeF7ghoS3mnF7wBN8o3C7H8Dwo9f3NDQfUEcAatfQI 5kzzzq+9m3xTPgi8wG+6ReZIO4Mb5fDSXsZfJyVcIt3CLfeuMA3DeWuZuviv5748Ugbt uDMw== X-Gm-Message-State: APjAAAXLGhgjg1JL8aFJmEbuCpGjhujmj65ucAKxY3GDjWgjOZ5IKhVN 3HACepfMsG3c2J5e+2kZwyj1L6pkcGM= X-Google-Smtp-Source: APXvYqyw/0V8w5bJk2KtjdJXDM9/BKWwlERUqYOlk9qcCoJ3PD5qBC2XV7syPKT9l50CkSL1SLRQ8Q== X-Received: by 2002:a9d:7450:: with SMTP id p16mr8399723otk.141.1569719732230; Sat, 28 Sep 2019 18:15:32 -0700 (PDT) Return-Path: Received: from toshiba9term.covert9net (67-198-106-217.dyn.grandenetworks.net. [67.198.106.217]) by smtp.gmail.com with ESMTPSA id t30sm2553642otj.40.2019.09.28.18.15.31 for <9front@9front.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 28 Sep 2019 18:15:31 -0700 (PDT) From: covertusername967@gmail.com X-Google-Original-From: glenda@gmail.com Message-ID: <4917D3F7013C68C4954F2DDCF94874DE@gmail.com> To: 9front@9front.org Subject: Kernel panic when setting screen resolution on machine with i810 chipset Date: Sat, 28 Sep 2019 20:15:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: shared non-blocking component browser cloud session just-in-time interface What I did: I added an entry to /lib/vgadb to match the monitor I was using, then attempted to set the screen resolution using this new entry. I also tried using the regular 'lcd' setting in /lib/vgadb, and got a similar panic. What I expected to happen: I expected a 1024x768x24 framebuffer to become visible. What happened instead: The kernel panicked. Panic screen is here: http://okturing.com/src/6959/body Make and model: Gateway Profile 3. I would send it back to the manufacturer to have a VESA bios installed, but as the machine is 20 years old I don't think that will work. % sysinfo -p: Panic when retreiving the VGA information. Partial output recovered from serial console is here: http://okturing.com/src/6963/body I do not know why the kernel did not output a stack trace this time. Additional details: I am using the kernel i810 driver, as this machine does not have a VESA bios. This kernel is not quite stock Skin of Evil on 386, as I have updated to the latest hg sources as well as adding a minor change to the sdiahci driver to support the SATA controller I am using in my file server. I can provide the kernel binary and driver source if needed, though I do not believe that is the cause of this error as a similar panic occurs when using the unmodified Skin of Evil iso.