Debian Configuration :: Two Different Boot Symptoms?

Warning: NooB typing this. Two days ago I replaced an old version of Kubuntu with Squeeze. (This is not the computer/system I've written about in two recent threads.) Installation went smoothly, but one very early boot (I think the very first after installation) halted very early on, with:Waiting for /dev to be fully populated... [    4.051267]ACPI: I/O resource 0000:00:1f.3 [0x1c00:0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f]I stared at that for a very long time, used another computer to google for clues on what to do about it, couldn't find any text that I could understand -- I don't have a degree in anything computer-related, I'm just Joe Blow who wants to get things done on a computer without malware scares -- and eventually gave up and rebooted.

The reboot went well and I hoped there'd just been some kind of fluke. Just now, however, booting -- for perhaps the second or third time since the frozen mis-boot -- brought an elegant message telling me of a kernel failure and asking me if I wanted to inform whoever of it. (Yes, I responded.) The computer seems to be working fine: I haven't rebooted it since that error message, yet here I am browsing and posting away.Unlike this person, for example, I don't know what the hell I'm doing. (Well, I do know that he's using SuSE, I'm using Debian Squeeze, and they're not the same.)The computer's a circa-two-year-old laptop; I doubt that it's flaky because I there were no (visible) boot problems with Kubuntu just last week. I haven't installed anything other than from debian.org's squeeze repository. The mouse that's plugged in now isn't the same as the trackball plugged in yesterday, but that's the extent of any "hardware changes".If this computer fails to boot one time in four and at other times gives scary error messages that I can safely ignore -- well, I can live with that. But my guess is that it's more like an oil pressure warning light in a car: that I ignore this stuff at my peril.