WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] 3.0.0: tg3 & sata_sil crashes

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] 3.0.0: tg3 & sata_sil crashes
From: Molle Bestefich <molle.bestefich@xxxxxxxxx>
Date: Fri, 6 Jan 2006 03:29:47 +0100
Delivery-date: Fri, 06 Jan 2006 02:36:00 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Gbz8dhrF5v4MNNrptPbhRmy3Aj6TpiQS4KM4r5/X7erpjcAWeL8F1MW89X5Q7TNqR5XTTbLD7xcviZXGT4VIKrREM95BmOJGg9wGTsd+hKXI4P67DP1geaEj+mjryfL0RdBGFapSy8gSnB2ASD9V/nnZ4ODCYFD3zdgZUPUsZrU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

I get the following in dmesg when booting dom0 under xen-3.0.0.
If someone could explain why I'd very much appreciate it :-).

1.)
Looks bad enough, but the SATA disks are usable, so apparently not critical:

kobject_register failed for sata_sil (-17)

Call Trace:
<ffffffff801ef976>{kobject_register+70}
<ffffffff80243dab>{bus_add_driver+107}
<ffffffff801fc063>{pci_register_driver+131}
<ffffffff80151915>{sys_init_module+325}
<ffffffff80112406>{system_call+134}
<ffffffff80112380>{system_call+0}


2.)
Not sure why tg3 is mentioned below - when I cat /proc/interrupts,
only ohci_hcd seems to be using irq 19.  In fact, tg3 (tigon3) doesn't
seem to have any interrupts assigned, but then again the network
adapter seems to be working fine anyway.

irq 19: nobody cared!

Call Trace:
<ffffffff80155250>{__report_bad_irq+48}
<ffffffff80155329>{note_interrupt+89}
<ffffffff80154b5c>{__do_IRQ+252}
<ffffffff80115f04>{do_IRQ+52}
<ffffffff8010db65>{evtchn_do_upcall+197}
<ffffffff880349b0>{:bridge:br_handle_frame_finish+0}
<ffffffff80112cf1>{do_hypervisor_callback+17}
<ffffffff8010da2c>{force_evtchn_callback+12}
<ffffffff8010da2c>{force_evtchn_callback+12}
<ffffffff8800cfe1>{:tg3:tg3_interrupt_tagged+417}
<ffffffff80154a0c>{handle_IRQ_event+76}
<ffffffff80154b3c>{__do_IRQ+220}
<ffffffff80115f04>{do_IRQ+52}
<ffffffff8011a5fe>{monotonic_clock+78}
<ffffffff8010db65>{evtchn_do_upcall+197}<ffffffff80112cf1>{do_hypervisor_callback+17}
<ffffffff8011035a>{xen_idle+106}
<ffffffff8011035a>{xen_idle+106}
<ffffffff801103aa>{cpu_idle+58}
<ffffffff804c871a>{start_kernel+490}
<ffffffff804c819a>{_sinittext+410}

handlers:
[<ffffffff802a80e0>] (usb_hcd_irq+0x0/0x70)
[<ffffffff802a80e0>] (usb_hcd_irq+0x0/0x70)

Disabling IRQ #19


Hope that someone can bring me up to date.

Btw, out of curiosity, I'm wondering what the "+100" etc. numbers above mean.
Is it a byte offset into my particular compilation of the source code?
If that's the case, is that actually useful to anyone?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>