Alan Cox wrote:
On Fri, 30 Nov 2007 14:34:11 +0200 (EET)
Meelis Roos <[EMAIL PROTECTED]> wrote:
Can you stick a stack trace in at that point ? That would help diagnose
it a great deal quicker.
Finally done - found out hard way that BUG() is too bad and
dump_st5ack() suits me better.
Thanks.
> Thanks. This should fix the real cause, and also allow for port start to
> fail politely with -ENODEV.
Works fine here - no more strange messages. Thank you!
--
Meelis Roos ([EMAIL PROTECTED])
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Thanks. This should fix the real cause, and also allow for port start to
fail politely with -ENODEV.
Works fine here - no more strange messages. Thank you!
--
Meelis Roos ([EMAIL PROTECTED])
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Alan Cox wrote:
On Fri, 30 Nov 2007 14:34:11 +0200 (EET)
Meelis Roos [EMAIL PROTECTED] wrote:
Can you stick a stack trace in at that point ? That would help diagnose
it a great deal quicker.
Finally done - found out hard way that BUG() is too bad and
dump_st5ack() suits me better.
Thanks.
x90
> [] sys_init_module+0x121/0x1550
> [] vma_prio_tree_insert+0x1f/0x50
> [] ata_std_prereset+0x0/0x160 [libata]
> [] do_mmap_pgoff+0x298/0x320
> [] syscall_call+0x7/0xb
> [] packet_setsockopt+0xf0/0x3b0
> ===
> ata4294967295: failed to start port (errno=-19)
Mine
On Fri, 30 Nov 2007 14:34:11 +0200 (EET)
Meelis Roos <[EMAIL PROTECTED]> wrote:
> > Can you stick a stack trace in at that point ? That would help diagnose
> > it a great deal quicker.
>
> Finally done - found out hard way that BUG() is too bad and
> dump_st5ack() suits me better.
Thanks. This
/0x3b0
===
ata4294967295: failed to start port (errno=-19)
--
Meelis Roos ([EMAIL PROTECTED])
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/maj
rrupt :00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device :00:1f.1 to 64
ata4294967295: failed to start port (errno=-19)
ACPI: PCI interrupt for device :00:1f.1 disabled
ata_piix :00:1f.1: version 2.12
ACPI: PCI Interrupt :00:1f.1[A] -> GSI 16
===
ata4294967295: failed to start port (errno=-19)
--alessandro
Damaged people are dangerous. They know they can survive.
(Anna Barton/Juliette Binoche, 'Damage')
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Fri, 30 Nov 2007 14:34:11 +0200 (EET)
Meelis Roos [EMAIL PROTECTED] wrote:
Can you stick a stack trace in at that point ? That would help diagnose
it a great deal quicker.
Finally done - found out hard way that BUG() is too bad and
dump_st5ack() suits me better.
Thanks. This should
[d48d12f0] ata_std_prereset+0x0/0x160 [libata]
[c0155648] do_mmap_pgoff+0x298/0x320
[c0104086] syscall_call+0x7/0xb
[c02b] packet_setsockopt+0xf0/0x3b0
===
ata4294967295: failed to start port (errno=-19)
--
Meelis Roos ([EMAIL PROTECTED])
-
To unsubscribe from this list: send
to 64
ata4294967295: failed to start port (errno=-19)
ACPI: PCI interrupt for device :00:1f.1 disabled
ata_piix :00:1f.1: version 2.12
ACPI: PCI Interrupt :00:1f.1[A] - GSI 16 (level, low) - IRQ 16
PCI: Setting latency timer of device :00:1f.1 to 64
scsi0 : ata_piix
scsi1 : ata_piix
On Nov 28, 2007 9:07 PM, Alan Cox <[EMAIL PROTECTED]> wrote:
> > This message comes from 2.6.24-rc3 + todays git, version
> > a531a141089714efe39eca89593524fdf05104f2. I did grep the logs and found
> > that it first appeared in 2.6.24-rc1 (+ some git mayve) on Nov 3.
> > I used 2.6.23 before that
On Nov 28, 2007 9:07 PM, Alan Cox [EMAIL PROTECTED] wrote:
This message comes from 2.6.24-rc3 + todays git, version
a531a141089714efe39eca89593524fdf05104f2. I did grep the logs and found
that it first appeared in 2.6.24-rc1 (+ some git mayve) on Nov 3.
I used 2.6.23 before that and it did
> This message comes from 2.6.24-rc3 + todays git, version
> a531a141089714efe39eca89593524fdf05104f2. I did grep the logs and found
> that it first appeared in 2.6.24-rc1 (+ some git mayve) on Nov 3.
> I used 2.6.23 before that and it did not show this message.
Can you stick a stack trace in
b1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
libata version 3.00 loaded.
ata4294967295: failed to start port (errno=-19)
ata_piix :00:07.1: version 2.12
Floppy drive(s): fd0 is 1.44M
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/33 cm
libata version 3.00 loaded.
ata4294967295: failed to start port (errno=-19)
ata_piix :00:07.1: version 2.12
Floppy drive(s): fd0 is 1.44M
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1800 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1808 irq 15
This message comes from 2.6.24-rc3 + todays git, version
a531a141089714efe39eca89593524fdf05104f2. I did grep the logs and found
that it first appeared in 2.6.24-rc1 (+ some git mayve) on Nov 3.
I used 2.6.23 before that and it did not show this message.
Can you stick a stack trace in at
18 matches
Mail list logo