Your message dated Tue, 01 Aug 2023 01:09:37 +0200 with message-id <6531216.tM3a2QDmDi@bagend> and subject line Re: Debian's BTS is not for regular user questions has caused the Debian Bug report #1041195, regarding resource sanity check: requesting [mem …-…], which spans more than PCI Bus 0000:00 [mem …-… window] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1041195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041195 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: resource sanity check: requesting [mem …-…], which spans more than PCI Bus 0000:00 [mem …-… window]
- From: AlMa <AlMa0@ro.ru>
- Date: Sat, 15 Jul 2023 16:39:17 +0200
- Message-id: <[🔎] e73afe71-a846-7cbe-2fe9-cdf26932dbe1@ro.ru>
Package: linux-image-6.1.0-10-amd64 Version: 6.1.37-1In the depths of my journal I discover the following two warnings (last two lines are marked orange):Jul 15 15:21:43 AnonymizedMachineName kernel: radeon 0000:01:00.0: vgaarb: deactivate vga console Jul 15 15:21:43 AnonymizedMachineName kernel: sd 2:0:0:0: [sdb] Attached SCSI disk Jul 15 15:21:43 AnonymizedMachineName kernel: [drm] initializing kernel modesetting (VERDE 0x1002:0x6825 0x1028:0x053F 0x00). Jul 15 15:21:43 AnonymizedMachineName kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000e7fff window] Jul 15 15:21:43 AnonymizedMachineName kernel: caller pci_map_rom+0x65/0x180 mapping multiple BARslspci tells us this (hopefully this is the right place to look):00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)Subsystem: Dell 3rd Gen Core processor DRAM ControllerControl: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-Latency: 0 IOMMU group: 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> Kernel driver in use: ivb_uncoreWhat are the extent and the implications of the warnings "resource sanity check: requesting …, which spans more than PCI Bus 0000:00 …" and “caller pci_map_rom+0x65/0x180 mapping multiple BARs”? Any misconfiguration? Any adjustment options the kernel might need? The machine is a Dell Mobile Precision M6700 with the processor Intel Core i7-3720QM, 32 GB RAM, and AMD FirePro M6000 Mobility Pro graphic chip with 2GB GDDR5.Gratefully, AlMa
--- End Message ---
--- Begin Message ---
- To: 1041140-done@bugs.debian.org, 1041142-done@bugs.debian.org, 1041143-done@bugs.debian.org, 1041144-done@bugs.debian.org, 1041191-done@bugs.debian.org, 1041195-done@bugs.debian.org, 1041197-done@bugs.debian.org, 1041678-done@bugs.debian.org
- Subject: Re: Debian's BTS is not for regular user questions
- From: Diederik de Haas <didi.debian@cknow.org>
- Date: Tue, 01 Aug 2023 01:09:37 +0200
- Message-id: <6531216.tM3a2QDmDi@bagend>
- In-reply-to: <[🔎] 3303bd38-dd6d-9b88-2ed4-9b7f148f20a1@ro.ru>
On Sat, 15 Jul 2023 03:13:51 +0200 AlMa <AlMa0@ro.ru> wrote: > In the journal I see two yellow lines (which, probably, constitute > warnings) directly following one another: > … > Later in the journal we see a white line > … > > As the machine (Dell Mobile Precision M6700) experiences various > high-level issues later in the boot process, I'm unsure about the > contribution of the two issues in the log. Which software or hardware > problems do these warnings inform us about? Any fix or remedy? You filed various bugs talking about yellow and white lines of which you suspect that yellow may be a warning (which you should be able to find out by yourself if that's the case). The Debian BTS is not meant to ask questions like "what could this message tell us?". Put it in a search engine or use one of the MANY user support options for that. Computers/Linux put various debug/informational/warning msgs in various logs, which _could_ be helpful in case there's an actual ERROR. But the only *potential* error I see here is "various high-level issues", which is so vague so that's completely useless and inactionable. So I'm going to close this and similar vague bug reports, which aren't actually bug reports, but just questions. And all those ACPI errors? Contact the machine vendor as they're the only ones who could resolve such issue. Linux is only reporting that there are issues. "If we believe Jean Delvare" ... and Jean Delvare response in that bug report: "This is not a support forum, sorry. If you need help, use support forums and mailing lists." ... From 'bug' #1041191: "Will the fingerprint sensor not work?" I _assume_ you have the device/machine, so why don't you try it out? *IF* it turns out it doesn't work then you first use a search engine to see if you can make it work yourself by trying out various hints you'll undoubtedly find and if that doesn't make it work, *THEN* you have something to file a bug about. You filed *8* different 'bugs' which (almost?) all are about a Dell Mobile Precision M6700 ... and not once did you say what actual problem you experienced?!? If you file a bug, you're (basically) asking (several) people to read about a problem you're having and then subsequently (potentially) spend time to fix that/those problem(s). Please be more considerate with other people's time and only file bugs for *actual* problems and then provide enough information/context so that they can actually (potentially) act upon it and help you fix that problem. I initially intended to respond to some actual problems you (also) reported, but I've already spend way too much time on these non-issues, so I'm done.Attachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---