From: Mathieu Taillefumier <mathieu.taillefumier@free.fr>
To: linux-kernel@vger.kernel.org
Subject: [Bug] pci allocation resources problems on x86_64
Date: Fri, 24 Oct 2008 12:13:56 +0200 [thread overview]
Message-ID: <49019FE4.50001@free.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
Hi,
The kernel does not seems to allocate the pci resources correctly on
sony laptop (VGN-SZ71 series) when pcmcia slot is used.
I track down this bug for long now and I was able to identify where it
is probably coming from. The laptop I am using possess a pcmcia card
slot that I am using for a tvcard. The kernel is a x86_64 bits kernel
(2.6.27.2) and the laptop has 4G of memory. In this case the
initialization of the tv-card is pure garbage and the kernel oops after
that. Now if I start the laptop with 2G and the same kernel then
everything works fine. From that I can assume that the problem does not
come from the tvcard driver and maybe not from the pcmcia driver
(although I am not completely sure). After discussing on the dvb
mailling list we arrive to the conclusion that the problem is probably
coming from pci allocation ressources.
additional informations :
Configurations that work
- x86_64 kernels with 2G of memory
- x86 kernels with 4G of memory without PAE activated nor 64 bits
resources allocations option activated.
Config that do not work
- x86_64 kernels with 4G of memory
- x86 kernels with 4G of memory with 64bits resources allocation
activated (without PAE).
The problem can be reproduced with kernel-next and the kernel-git so far
and probably with earlier kernels although I have try this
cat /proc/version
Linux version 2.6.27.2-intel-nogem (root@coesite) (gcc version 4.3.1
(GCC) ) #4 SMP Wed Oct 22 12:05:55 CEST 2008
the lspci output are in one of the files and different dmesg are
included. the dmesg-diff give the differences between the working one
and the buggy one.
I would like to help debugging this
Regards
Mathieu
[-- Attachment #2: dmesg-64-doesnotwork.bz2 --]
[-- Type: application/octet-stream, Size: 11657 bytes --]
[-- Attachment #3: dmesg-64-work.bz2 --]
[-- Type: application/octet-stream, Size: 10505 bytes --]
[-- Attachment #4: dmesg-diff.bz2 --]
[-- Type: application/octet-stream, Size: 11280 bytes --]
[-- Attachment #5: config.gz --]
[-- Type: application/gzip, Size: 11605 bytes --]
[-- Attachment #6: lspci.output.gz --]
[-- Type: application/gzip, Size: 3806 bytes --]
[-- Attachment #7: cpuinfo.gz --]
[-- Type: application/gzip, Size: 501 bytes --]
[-- Attachment #8: iomem.gz --]
[-- Type: application/gzip, Size: 583 bytes --]
[-- Attachment #9: ioports.gz --]
[-- Type: application/gzip, Size: 609 bytes --]
next reply other threads:[~2008-10-24 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 10:13 Mathieu Taillefumier [this message]
2008-10-24 10:34 ` [Bug] pci allocation resources problems on x86_64 Mathieu Taillefumier
2008-10-24 18:31 ` Jesse Barnes
2008-10-24 20:10 ` mathieu.taillefumier
2008-10-25 8:45 ` Yinghai Lu
2008-10-25 9:04 ` Yinghai Lu
2008-10-25 12:43 ` mathieu.taillefumier
2008-10-25 19:55 ` Yinghai Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49019FE4.50001@free.fr \
--to=mathieu.taillefumier@free.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox