mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Admar Schoonen <admar@luon.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.8-rc4 on sparc64 oopses at boot and no working XFree86
Date: Fri, 13 Aug 2004 13:43:21 +0200	[thread overview]
Message-ID: <20040813114320.GJ21828@azrael.luon.net> (raw)

Hi

I'm running 2.6.8-rc4 on a sun blade 100 (ultra sparc IIe) with 2 PGX64
(Ati mach64) framebuffers, running Debian unstable. When the kernel boots,
it looks like it produces an oops in the very beginning. This is not
visible on the console, but dmesg shows some traces:

  0053c3d0] class_device_add+0x50/0x140
   [0000000000514ce8] pci_scan_bus_parented+0xe8/0x180
   (...)
  bad: scheduling while atomic!
  Call Trace:
    [000000000045bc4c] call_usermodehelper+0xac/0xc0
    (...)
    (this goes on for over 200 lines and continues with:)
  PCI-IRQ: Routing bus[ 0] slot[ 8] map[0] to INO[23]
    (...)
  PCI-IRQ: Routing bus[ 1] slot[ 1] map[0] to INO[0a]
  PCI0(PBMA): Bus running at 33MHz
  isa0: [dma -> (floppy) (parallel)] [power] [serial] [serial]
  ebus0: [flashprom] [eeprom] [idprom]
  
This also happens with 2.6.8-rc1, but it doesn't with 2.6.7 and older.
On 2.6.6, it looks like this:

  NET: Registered protocol family 16
  PCI: Probing for controllers.
  PCI: Found SABRE, main regs at 000001fe00000000, wsync at 000001fe00001c20
  SABRE: Shared PCI config space at 000001fe01000000
  SABRE: DVMA at c0000000 [20000000]
  PCI-IRQ: Routing bus[ 0] slot[ 8] map[0] to INO[23]
    (...)
  PCI-IRQ: Routing bus[ 1] slot[ 1] map[0] to INO[0a]
  PCI0(PBMA): Bus running at 33MHz
  isa0: [dma -> (floppy) (parallel)] [power] [serial] [serial]
  ebus0: [flashprom] [eeprom] [idprom]
  
so perhaps something is changed in the pci / sabre code?

Furthermore, with 2.4.x, I could use both framebuffers on the console
and in X. With 2.6.x (x <= 7), I could only use the primary framebuffer;
secondary was always black on console and X. But with 2.6.8-rc1 and up,
I can use the secondary framebuffer (con2fbmap works), but X (configured
for only my primary framebuffer) gets a signal 11 before it can display
it's famouse black & white dots. X -configure also gets a signal 11.

I've put up my .config, dmesg log's and XFree86.0.log at
http://people.spacelabs.nl/~admar/2.6.8-rc4-sparc64/

Could anybody pleasse help me out with these problems?

Pleasse CC any replies to me, as I'm not subscribed to this list.

Regards

Admar Schoonen

             reply	other threads:[~2004-08-13 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 11:43 Admar Schoonen [this message]
2004-08-13 16:03 ` David S. Miller

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=20040813114320.GJ21828@azrael.luon.net \
    --to=admar@luon.net \
    --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

all inboxes | Powered by JetHome®