linux-kernel - 2.6.20-git10 (and -git13): BUG at drivers/pci/pci.c:817 during resume from disk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 17 Feb 2007 11:00:38 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	linux-ide@...r.kernel.org
Cc:	Andrew Morton <akpm@...l.org>, Jeff Garzik <jeff@...zik.org>,
	Alan <alan@...rguk.ukuu.org.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: 2.6.20-git10 (and -git13): BUG at drivers/pci/pci.c:817 during resume from disk

Update:

I get the same BUG with 2.6.20-git13 100% of the time during the resume.
The system seems to be fully functional nonetheless.

On Thursday, 15 February 2007 12:23, Rafael J. Wysocki wrote:
> Update:
> 
> On Thursday, 15 February 2007 00:16, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > I've got this in the resume-during-suspend phase of suspend to disk with
> > 2.6.20-git10 on HPC nx6325:
> > 
> > PCI: Setting latency timer of device 0000:00:06.0 to 64
> > sata_sil 0000:00:12.0: resuming
> > BUG: at drivers/pci/pci.c:817 pcim_enable_device()
> > 
> > Call Trace:
> >  [<ffffffff8031c05e>] pcim_enable_device+0x93/0xb3
> >  [<ffffffff8039a74c>] ata_pci_device_do_resume+0x21/0x5e
> >  [<ffffffff803a5f8a>] sil_pci_device_resume+0x1c/0x51
> >  [<ffffffff8031e072>] pci_device_resume+0x22/0x53
> >  [<ffffffff8038bea4>] resume_device+0xca/0x131
> >  [<ffffffff8038bf8c>] dpm_resume+0x81/0xd3
> >  [<ffffffff8038c00e>] device_resume+0x30/0x45
> >  [<ffffffff802a0d8c>] snapshot_ioctl+0x245/0x63e
> >  [<ffffffff8023f7f2>] do_ioctl+0x5e/0x77
> >  [<ffffffff8022dab2>] vfs_ioctl+0x25c/0x279
> >  [<ffffffff8024948a>] sys_ioctl+0x5f/0x82
> >  [<ffffffff8021555d>] sys_write+0x47/0x70
> >  [<ffffffff8025911e>] system_call+0x7e/0x83
> > 
> > The box has survived the entire suspend-resume cycle, though, and seems to be
> > fully functional.
> 
> I get this 100% of the time, but the box suspends and behaves normally after
> the resume.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/